ricardo.larranaga at gmail.com
Sun Jun 11 14:28:32 CDT 2006
On 6/11/06, Legolas <legolas558 at email.it> wrote:
> Ricardo Larrañaga ha scritto:
> > Hi all.
> > i am having trouble following the organization of the development
> > team. Maybe is because i couldn't find the info about how his team is
> > organized, if that is the case, i would like to know if someone could
> > point me to that info.
> Actually I once proposed it (see
> http://sourceforge.net/mailarchive/message.php?msg_id=15656762 ), looks
> like it is the time to write such document.
Ok, i just read it, and i agree. Need Someone to write this?
> 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.
> It was the 4th step in my last email to this group. If we are ready, we
> can start splitting the tasks.
Sorry, i must overlooked it
> 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.
> There are a lots of people contributing, BC, Jeroen, Ali and others that
> I meet less frequently but that luckly spend their time for the s1mp3
I know, but it would be nice to a new member to know that those persons
contribute and in wich areas they work
> 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.
> Agreed. It is exactly what I meant to do once we agreed on the next
> milestone - the simulator.
> > 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 way.
> I have in mind a more organized structure, see the apposite page
> I would also suggest Wladston to create a Dev: namespace on the wiki
Can't get to that page. i get 404 error
> I also think that there should be a link to this info in the welcome
> > message.
> > 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)
> > 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
> > 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.
> I will start working on the article I never written to introduce
> newcoming members
> > So, i think the development teams should be:
> > -API team
> > -ICE team
> > -SIM DEV team
> > -WEB SITE DEV team
> > -BETA TESTING team
> > -DRIVERS DEV team
> > When the api is defined and released, we should add an app-dev team too.
> > Wait for your comments.
> > Ricardo
> s1mp3-dev mailing list
> s1mp3-dev at s1mp3.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the s1mp3-dev