Organisation
From TremFusion
All the content of this page is only my (DaTosstt) point of view. Maybe someone will not agree with me. Take this content as a proposition, not a decision.
The goal of organisation is everyone know :
- every existing tools used by the team,
- what every tools is use for,
- work in the same direction even if you want work alone
Contents |
The Actions
Globaly we have 3 kind of actions :
"think and decide"
The time to think, debate, define specifications, studing possibilities, etc.
At the end of a discussion when a decision was taking, we need to publish this decision (on a persistent medium).
"put and get"
The time to do.
Time to produce and sharing source code (by diff/patch, tarballs, pastebin, etc.)
Developers like to see what the others do (it's the "get").
Developers like to show that they done (it's the "put") almost the time to diffuse patchsets or commiting in public repository
the rest
The feedback, or information that comes from non developers (that often need to be clean/discuss/... before use) is another process that I don't want think about now.
Our Tools
- the wiki
- url : http://www.tremfusion.net/trac/wiki
- (persistent medium)
- the mailing list
- see the page ...
- the ticket tracker
- (persistent medium)
- url : http://www.tremfusion.net/trac/report
- the svn or mecurial repository
- url : ...
- (persistent medium)
- irc channel
- irc.freenode.org:6667 #tremforges
- (passing/non-persistent medium)
- Web Forum
- have they ?
- (passing/non-persistent medium, yes I don't think forum is a good tools to release decision)
- ... (need to complete the list)
the Team
We need to define:
- who are they (active developers, others people/contributors)
- what we plan to do (features list, roadmap)
- who do what (who devs work on what tasks)
- ...
who
Official devs of the team (I think) :
- Champion
- Ender
- Azrael
- Amanieu
- Kangounator
- Chessguy
- Madtree
- PierreF
- griffon
- DaTosstt
- ...
what
The feature list :
- First release : What we need for the first release ? Brainstorming
- Future releases : Anything you want added that won't go into the first release
when
The roadmap : none yet
who do
The ticket tracker to see who work on what : none yet
UPDATE: the ticket tracker is open.
The developement process
I don't want to wrote how to code, but just remember don't forget to make documentation ;-)
