Changes between Version 6 and Version 7 of ProjectStructure


Ignore:
Timestamp:
08/25/07 07:26:56 (10 years ago)
Author:
jpr@…>
Comment:

Fix olpc link

Legend:

Unmodified
Added
Removed
Modified
  • ProjectStructure

    v6 v7  
    4848It's interesting to see how differnet projects handle this. [http://projectfortress.sun.com/Projects/Community projectfortress.sun.com] takes the approach I've been using with UABgrid, a different trac/svn set for each sub project.  This has the common shortcoming of having a poor overview of the entire project because Trac doesn't support multi project views. (For example, note the rodemap view for two of the projectfortress trac instances [http://projectfortress.sun.com/Projects/Community/roadmap Community] and [http://projectfortress.sun.com/Projects/AboutThisInstallation/roadmap AboutThisInstallation])  
    4949 
    50 Then there is the [http://dev.olpc.org olpc model] which I'm starting to like.  I also think I'm getting over my aversion to revision number hopping from unrelated changes, after reading about git.  It's just a number and doesn't need to mean anything externally.  If I tag a branch on a subproject, it will still be composed of specific revisions for that project and nothing's gonna change that. having it all in one project will make overviews easier.   
     50Then there is the [http://dev.laptop.org olpc model] which I'm starting to like.  I also think I'm getting over my aversion to revision number hopping from unrelated changes, after reading about git.  It's just a number and doesn't need to mean anything externally.  If I tag a branch on a subproject, it will still be composed of specific revisions for that project and nothing's gonna change that. having it all in one project will make overviews easier.   
    5151 
    5252A slight downside is that having separate projects can isolate dialogs a bit better, ie. a separate email address for each project and the project name in the subject line.  This may be premature noise reduction though, since it could elliminate cross over dialogs due to user confusion of where to talk. Also the component name could probably be fanagled into the the subject as a substitute.