coding style - Common practice to name project directory which hold support scripts, configs, docs, etc for developers -

coding style - Common practice to name project directory which hold support scripts, configs, docs, etc for developers -

i work little set of projects lack of knowledge naming convention directory in software project file hierarchy desired hold project development.

i well-known projects (like firefox, gcc, binutils, linux, emacs, vim, etc) , collect mutual directories (comments written myself don't pretend true...):

examples or samples show practical usage of project in mini-scripts or mini-programs, or mini-configs. scripts, support - wrappers or re-create of missing scripts/utilities provide cross-environment build. tools - utilities profile or debug project. contrib - user supplied scripts, configs, etc... misc, etc - uncategorised files (if don't know right place it). config, extra - don't know...

while src/, test/, build/, dist/, lib/ , other directories naming convention dictated prog-langs/platforms/frameworks etc, directories seems mutual type of projects.

so guide (official or unofficial) naming convention directories hold back upwards files project.

most essential distinct regular project files these file isn't used in project release build, or used in rare cases.

ps. can argue not question. have real task commit several scripts (sql script dump menu db, script dump url mapping web-controllers, etc) , directory name shoud hold these files...

pps. create things right , perform work on field (for task). tips:

http://gavenkoa.users.sourceforge.net/tips-html/devel-proj-files.html

coding-style naming-conventions