Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

How do you organize your software assets (source code and resources), your "active" and "past" projects, and your Software Department processes/work-instructions (including source code conventions, rules, and reviews process)?

For example, one approach would be to use "Trac" with databases for "Software Assets" and "Software Process". Another would be to have databases for "Project A", "Project B", and "Software Process".

Is your source code "by-project", or "by-all-in-department", or "by-product"?

share|improve this question

migrated from stackoverflow.com May 15 '11 at 13:21

This question came from our site for professional and enthusiast programmers.

1 Answer 1

Working in a Fortune 500 company, our source is organized by group (or department) and by product/application. The group layer allows us to maintain security to just those who should have access. Projects for us can span multiple applications (or products) and would be a nightmare to base our source code on.

For any application that has been retired, we move that source code to an archive repository, making our main repository strictly for live applications.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.