Hi all, I just got an email from Alexander with questions about launchpad teams and subteams, so I just reply here. After I suppress the team stellarium-devel yesterday, the main Launchpad organizational elements are:
* Project "stellarium": the main project owned by team "stellarium". * Team "stellarium": the core Stellarium developers: they have the rights to change meta-data about the Stellarium project (in LP), manage main branches etc.. You can join this team if you are approved by me. * Teams "stellarium-translators" and "stellarium-skyculture": regroup people interested in those 2 subjects. The main use of the team is to get commit rights for the bzr branches owned by the teams. I think a best practice is to have someone volonteering to be the manager of these groups and who can maintain a main branch for them. This person will then take care of integrating all the translation/new sky culture stuff into this branch, which can then be merged by a member of the "stellarium" team into trunk. It is also important to understand that the "stellarium" team is itself a member of the "stellarium-translators" and "stellarium-skyculture" teams, which just means that the members of the "stellarium" team are also members of those teams. * Project "stellarium-website" and team "stellarium-website": Matthew created a subproject "stellarium-website" to manage branches related to translation of the website. After reflexion, I now think it would be better to manage this the same way "stellarium-translators" and "stellarium-skyculture" are managed, i.e. get rid of the "stellarium-website", and just create a master branch of the stellarium project owned by the "stellarium-website" team. What do you think? Fabien On Thu, May 19, 2011 at 23:45, Fabien Chéreau <[email protected]> wrote: > I just suppressed it because it was useless since we never used the > mailing list. > It just simplifies the management. > Fabien > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Stellarium-pubdevel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
