Re: [virgo-dev] snaps subproject

[Glyn Normington <gnormington@xxxxxxxxxx>]

Thanks Florian.

All: please provide your nominations for snaps subproject lead. You can nominate yourself.

Regards,
Glyn

On 15 Nov 2010, at 09:38, Florian Waibel wrote:

> After a short enquiry call with a member of the Planning Council I'd like to share my new knowledge here:
> 
> "Every project can have sub-projects"
> 
> "The concept *gentleperson's agreement* isn't known inside eclipse.org by now." (But, there are some rare cases where committers only have access to parts of a project's repository)
> 
> "A proper subproject needs a project lead but should be easy to create. And most noteworthy it would be easy to add new initial committers to an isolated part of an existing code-basis."
> 
> Regards,
>  Florian
> 
> On Nov 13, 2010, at 8:54 AM, Glyn Normington wrote:
> 
>> To those interested in snaps
>> 
>> Since SpringSource cannot fit snaps high in its list of development priorities for Virgo, it may make sense to treat it as a subproject of Virgo and start to promote its contributors into committers. Unfortunately, I *think* a project like Virgo with a code repo cannot have a subproject with a code repo under Eclipse rules, although we should probably check that, so what we could do is to promote the relevant contributors to committer status in Virgo but have a gentleperson's [1] agreement that they restrict their commits to snaps.
>> 
>> If we had a proper subproject, then snaps would get a separate classification in bugzilla and would have its own web site. Plus there may be additional freedom in releasing independently of Virgo.
>> 
>> Thoughts?
>> 
>> Regards,
>> Glyn
>> 
>> _______________________________________________
>> virgo-dev mailing list
>> virgo-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/virgo-dev
> 
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev