[Sugar-devel] Re-initiate Packaging Team

[Aleksey Lim]

On Thu, Oct 21, 2010 at 04:28:18PM +0200, Bert Freudenberg wrote:
> 
> On 21.10.2010, at 04:59, Aleksey Lim wrote:
> 
> > On Thu, Oct 21, 2010 at 11:26:49AM +0000, Aleksey Lim wrote:
> >> On Thu, Oct 21, 2010 at 04:31:49PM +0530, Manusheel Gupta wrote:
> >>> On Thu, Oct 21, 2010 at 4:13 PM, Aleksey Lim <alsroot at member.fsf.org> wrote:
> >>> 
> >>>> On Thu, Oct 21, 2010 at 03:45:58PM +0530, Manusheel Gupta wrote:
> >>>>> On Thu, Oct 21, 2010 at 1:32 PM, Aleksey Lim <alsroot at member.fsf.org>
> >>>> wrote:
> >>>>> 
> >>>>>> Hi all,
> >>>>>> 
> >>>>>> This a request to relaunch Packaging Team by giving it a bit another
> >>>>>> meaning that it has before.
> >>>>>> 
> >>>>>> The main idea I see for this new/old team is:
> >>>>>> 
> >>>>>>   Let people start sugar in any environment they have in most
> >>>>>>   convenient way.
> >>>>>> 
> >>>>>> The team will cover not only questions how sugar is packaged for
> >>>>>> major GNU/Linux distribution but also:
> >>>>>> 
> >>>>>> * having Bazaar as a central place of all (out of distro) efforts
> >>>>>> * building packages that are not(yet/well) packaged
> >>>>>> * support distros that don't have packaged sugar
> >>>>>> * run daily snapshot of sugar in as many as possible environments
> >>>>>> * take care of Sugar Platform dependencies (how many, are they packaged
> >>>>>> and make custom build otherwise)
> >>>>>> * support meta sugar distribution ie just a bunch of repositories of
> >>>>>> sugar packages that can be attached to existed system to run sugar
> >>>>>> 
> >>>>>> BTW, maybe "Packaging" is not appropriate name, any ideas?
> >>>>>> 
> >>>>> 
> >>>>> 
> >>>>> Account Services team is the preferred trade name for small size teams
> >>>>> engaged in support work (answering questions, or communicating with the
> >>>>> development team, maintaining builds and their timely releases). Some
> >>>>> companies use "Internal System Architect" nomenclature too. When team
> >>>> sizes
> >>>>> grew bigger, this work comes under the umbrella of Members of Technical
> >>>>> Staff.
> >>>> 
> >>>> Well, I personally prefer something less official/corporate, e.g., Bazaar
> >>>> Team :)
> >>>> 
> >>> 
> >>> 
> >>> Bazaar in Hindi refers to market. Suspect that many people would confuse it
> >>> with the marketing team :-)
> >> 
> >> Though "Bazaar" is referring more to "The Cathedral and the Bazaar" in
> >> FOSS world (afaik) rather to marketing (which sounds, in some meaning, quite
> >> opposite thing :).
> >> 
> >> What about "Sweet Team" then, i.e., "sweet" is an id of packages on
> >> bazaar.sl.o and "sweets" is the main command-line tool.
> > 
> > Of course it might be something neutral like "Distribution Team".
> 
> Working with distro packagers is really important. Getting Sugar to work on distros that do not have current Sugar packages is important, too. And running Sugar in emulation on Macs and Windows machines should also be part of the "Let people start sugar in any environment" mission. Possibly "platform team" would be more appropriate?

+1 for all options

I guess we don't have many options for naming and "Platform Team" sounds
best of all. For example, there is Sugar Platform (and Platform project
on Bazaar for the same purpose) that should be an area of responsibility
for the new team.

I'll start to copy&paste Platform Team (keeping in mind original purpose
I stated in initial email) related resources on wiki to Platform_Team/
sub region on wiki.sl.o.

-- 
Aleksey