... | @@ -30,19 +30,21 @@ We recommend the following usage: |
... | @@ -30,19 +30,21 @@ We recommend the following usage: |
|
|
|
|
|
1. Use the issues tracker to create issues, tasks, milestones and
|
|
1. Use the issues tracker to create issues, tasks, milestones and
|
|
deadlines for your project, and assign it to your team members.
|
|
deadlines for your project, and assign it to your team members.
|
|
Think of issues as "tickets" they allow you to planify tasks and
|
|
Think of issues as "tickets" they allow you to plan tasks and future
|
|
future features, as well as to be used for bug tracking.
|
|
features, as well as to be used for bug tracking.
|
|
2. The mailing list is the preferred way of communication, but you can
|
|
2. The mailing list is the preferred way of communication, but you can
|
|
also use forums.
|
|
also use forums.
|
|
3. Use subversion primarily as a source code repository, as well as for
|
|
3. Use subversion (SVN) for all kinds of files requiring version
|
|
storing intermediate versions of rapid-changing documents.
|
|
management: HDL and software/firmware, schematics, PCB layout,
|
|
|
|
manufacturing files, etc.
|
|
4. Use the Documents module for providing "release" versions of
|
|
4. Use the Documents module for providing "release" versions of
|
|
Documents; Typically you would show versions 1.0, 2.0 and 3.0 on the
|
|
Documents; Typically you would show versions 1.0, 2.0 and 3.0 on the
|
|
Documents section, and all the intermediate steps (1.1, 2.3.1, etc)
|
|
Documents section, and all the intermediate steps (1.1, 2.3.1, etc)
|
|
would be managed via the SVN.
|
|
would be managed via the SVN.
|
|
5. Similarly, use the Files section for "release" versions of important
|
|
5. Similarly, use the Files section for "release" versions of important
|
|
files, such as binary installation programs, firmware etc. Again,
|
|
files, such as binary installation programs, drivers, schematics,
|
|
intermediate versions of these should be managed via subversion.
|
|
gerber files, firmware etc. Again, intermediate versions of these
|
|
|
|
should be managed via subversion.
|
|
6. Use the wiki for storing the information you want to conserve about
|
|
6. Use the wiki for storing the information you want to conserve about
|
|
your project, but for which you don't have specific documents;
|
|
your project, but for which you don't have specific documents;
|
|
meeting minutes, informal, high-level descriptions, objectives, etc.
|
|
meeting minutes, informal, high-level descriptions, objectives, etc.
|
... | | ... | |