Wladston Viana F Filho
wladston at gmail.com
Sun Jun 11 14:11:49 CDT 2006
Agrees completely with your ideas.
i am having trouble following the organization of the development team.
Yeah - i fear that's because we don't have an organisation yet. Can you help
us into making one ? :)
Maybe the workflow of the developers is defined but not lined out anywhere.
> The i would like to propose that the organizational diagram and workflow of
> the developers team should be put down in writing in a web page in the
> techies area of the site, and that the welcome message of the developers
> mail list should have a link to it so new developers can catch up fast about
> how things work in this project.
sure. I would love a proper definition of "workflow of the developers" -
what is the page for, what content shall it have, where can we see a good
example of one. The we'll be able to make one for us and do what you've
Next, i would like to point out that i don't have a very clear idea of who
> does what in the project. I can see that wladston works mostly in the
> developing of the site, and know that legolas works on ICE, and web site to.
> But besides them i can't really say who does what.
Well, take a look on the member's list page ...
the information is there - it just needs more organization.
Again, if i am missing to read some info somewhere, i would like to know,
> but if i am not, and this kind of information is not lined out somewhere or
> simply not defined, i would like to propose to define a basic number of
> sections and divide the developers into those sections.
your suggestion to divide the people into dev-teams will surely help into
finding out what people do.
Everyone agrees with that ??
The fact that a developer is in one section doesn't mean that he can't
> work/help in another area, but it would be easier to work if each developer
> is linked somewhere to the area he is more involved. For that i would
> recommend another field in the active members area that points to wich of
> this defined and finite group of tasks the member is involved. I realize
> that there is a Objectives/Interests in the projects field that is somewhat
> alike, but i think that it would be clearer and easier to follow the other
I also think that there should be a link to this info in the welcome
sure. That would make another new page to be written. - the index of the
i would recomernd also to write down a roadmap (a dateless one, since this
> is volunteer project, and everyone works in it in his free time) but that
> would be neat to know what the priorities are in a certain moment (i also
> recommend to link this to the welcome message)
yeah - tree pages up to now - A roadmap or a todo list.
Finally, i would recommend to merge all this info in a block diagram-like
> chart with blocks representing the teams, active members inside the blocks,
> and finally, the relations between the developer teams.
sure - this will probably fit on the "index of the development teams"
I know that working on this will slow down development, and i do think that
> that is the most important thing, but i also think that all this
> organization is needed to develop in the most efficient way. So, to help not
> slowing down the developement, i would like to propose here the definition
> of the groups , and offer myself to draw the block diagram and then start to
> work on the roadmap.
great dude! Let's see if the other members agree with this idea.
Wladston Viana Ferreira Filho
Belo Horizonte - MG, Brasil
Visit the project: s1mp3.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the s1mp3-dev