To keep the project going we need to make frequent releases.
Plan: At least one release of any kind each month.
Plan2: At least one stable release every 8 months.
For the current plan, see ReleaseSchedule.
Direction for the development
Some important areas are identified:
- Eclipse RCP
Promoting the project
By releasing often, hopefully a lot of buzz is created around the project.
Recruitement of new developers
By releasing often, we show activity and attract developers.
New developer can start by fixing their favorite problem in ArgoUML first. Because there is a lot of code and it is complex they need a lot of determination and resolve to learn enough to be able to do anything.
Discussions start on the dev mailing list. If the cooperating groups discussion is becoming too specific and the topic is within the scope of one of the argouml subprojects, move to the dev list of the subproject. If not, move to private mails, or a new mailing list created for the purpose. It is a good idea if someone would summarize the discussion, weekly, on the dev list.
If mail is not suitable for the discussion, use whatever mean available (netmeeting, irc, skype, phone, ...). Summarize to the dev list.
Create plans and discussion material in this wiki. If document interchange is required either put them up as attachments to the wiki or check them into the ArgoUML subversion repository.
Project Leader to keep the project together.
Appointed developers are leading the work with each subsystem.
Release Responsible manage releases.
Everybody find their own tasks to work with. Preferably from the important areas above. The appointed developers act as guides.