Incubator components would make sense.
Having to recreate the project structure, even if it is the same people, is
where I have issues. Also the façade that they are two separate projects is
misleading to the community since operationally they are not. Projects in my
mind are organizational things, i.e. the people. Is it the code that’s
incubating or the people?
If all we’re trying to achieve is
the ability to do releases for code that hasn’t gone through the IP
process. Maybe having an incubator area in the CVS/SVN repository and a tagging
of bits in the downloads area as incubating would be enough.
I’m just worried that people might
be abusing the Incubator process as a workaround for going through the proper
IP process.
From: Bjorn Freeman-Benson
[mailto:bjorn.freeman-benson@xxxxxxxxxxx]
Sent: Monday, October 22, 2007
10:49 AM
To: Doug Schaefer
Cc: pombredanne@xxxxxxxxx; Tools
PMC mailing list
Subject: Re: [tools-pmc] RE:
[ve-dev] Contribution on VE with XML editor
Doug,
What mechanism do you suggest instead (instead of creating incubator projects)?
Incubator components? (I ask in all seriousness because I'd like to simplify
things, but I'd also like to simplify things in a way that other people find
simple and not just me :-)
- Bjorn
Doug Schaefer wrote:
I am not in favor of creating projects
just for incubating parts of another project. (BTW, that applies to projects at
Eclipse that have already done that). If that is necessary to get work done,
then there is something broken with the Eclipse process.