[EBOB-DISCUSSION] organizational questions

[Liam M. <lm...@WP...>]

As far as organization and environment is concerned- do we want to 
settle on Eclipse 3.0? I vote yes.

Other *suggestions* that are completely and totally open for discussion:

Eclipse Plug-ins that I use (and maybe you should too?):

    * GEF SDK 3.0.1 (can be downloaded through Help>
    * JDocSearch 0.0.3 http://www.jdocs.com/plugins/eclipse/index.html
      (for searching through Open Source APIs)
    * Log4E 0.7.6 http://log4e.jayefem.de/index.php/Main_Page (haven't
      really investigated this, but it's designed to make logging easier)
    * Any others?

Use Cases 
http://sourceforge.net/tracker/?atid=697946&group_id=123169&func=browse
I've just recently created a new tracker at SourceForge for use cases. I 
didn't know you could create your own trackers until now.. we could 
create new trackers for other things (like user stories) if we wanted 
to. As it is, we can connect features to use cases and vice versa. 
Unfortunately this is one-way linking- we can tell that use case UC1 
addresses feature F1, but we'd also need to edit F1 to say that it's 
addressed by UC1. (Instead of being called F1, SF gives everything 
unique numbers.)

Features 
http://sourceforge.net/tracker/?atid=695629&group_id=123169&func=browse
I've updated the features list on here, it's more or less up-to-date. If 
I'm missing anything, feel free to add it.

Bugs http://sourceforge.net/tracker/?atid=695626&group_id=123169&func=browse

Discussion:
mailing lists:

    * General discussion ebo...@li... (all
      three of us, open list)
    * Development discussion ebo...@li... (just
      Justin and I)

It seems weird to have a mailing list with just two people- the reason I 
made it was because the list gets archived. This will help if we ever 
need to go back and talk about a decision we made months prior over email.

Developer Documentation:
http://sourceforge.net/docman/?group_id=123169 Our vision is already 
here. We might want to discuss what documents we feel are necessary to 
write; do we need a software architecture document, etc., or will use 
cases (which already have a tracker) be sufficient?

User Documentation:
We could keep some user documentation in the same place (under a 
different category) if necessary, but generally we should be able to 
keep everything within the Eclipse Help system.

What's left (discussion points)?
A calendar to keep track of iterations and help plan? Should the 
Dashboard software be used as a group, or should we use it on a more 
individual level?