Posted by EclipseGc on June 16, 2009 at 12:08am
HAHA, welcome everyone, been a while since I checked this group. So, here's the basic need to get us going. I'd really like to put our heads together and start to put a list of features that would be needed for this sort of thing, together. Let's get it started, and we'll see where it goes from there.
Obviously we need some serious taxonomy controls to help make code easier to find and categorize. I'd like to start off by asking what sort of scheme you all think might work best here.
Eclipse
PS: Toss in other thoughts as they come to you, we need this to be very loose and free-form until we get some concrete ideas.
Comments
I would say start with the
I would say start with the same categories as on Drupal.org -- where you might put the module when it's eventually released.
But a secondary vocabulary for free tagging would be needed too.
And some way of looking for "all the modules that extend module X" where X might be Views, Ubercart, or anything really: so a 3rd vocab that's freetagging but the tags are expected to be the names of modules on d.org.
For code, I'd like to see some kind of tagging convention for the CVS that's a bit like d.org releases. Except the tags would go like this:
- thismodule-joachim-1 <-- that's my first release
- I make some more commits but they're not tagged as they are work in progress
- thismodule-joachim-2 <-- I've decided that enough work has gone in to say that this is a new snapshot.
- thismodule-EclipseGC-3 <-- you've made some commits and this is your snapshot.
- thismodule-someotherdude-4 ... and so on.
The idea is that you can clearly see a history of sort-of-stable release points. So if I reckon someotherdude's made a mess, I can easily grab the last release I think is OK.