On Tuesday 27 April 2010 17:59:16 Shaver, Michael R wrote: > I think coming up with the overall name will inform how we name the various > processes and components that make up this. An example would be if the > overall name to end users was called "Extras", then for the developer > uploading their source it might be called "Extras Source Repositories". Or > you get the idea.
Yes, but that is about choosing the name of the repository. This discussion is about choosing the name for the working team which will discuss setting up the repositories! I would prefer not to constrain the MeeGo Marketing Working Group (or whatever they end up being called) in what they want to call the repositories this team creates -- we are much better off having a team name which cannot be confused with the repositories we will create. Especially as my view is that we will end up with several different repositories with different names (but that is a discussion for later!). The Team name should be something dull. Personally I would have been happy with the Repositories Team (and for the scope to include the Core repos as well -- I think we will find it is important to have some consistency between the core and the supplemental repos, in things like how many there are, how they relate to releases, how they relate to UX's, etc.). But if others are not happy with a converged team, why don't we call this the "Community Repositories Team". Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
