[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [tools-pmc] VE incubator - FOCUS
|
Doug Schaefer wrote:
> Philippe, we are all volunteers here. Patience will get you
> farther than confrontation.
True. You know how an enthusiast I can be.
> We still need to get approval from the EMO that we can have
> components as incubators. Like it or not, VE is the test case
> for this.
That is fine by me. I make a new project proposal and submit it rigt away.
The only thing I would need as an OK is not to have separate newsgroups,
mailing list and top level CVS. The VE incubator would go under an INCUBATOR
submodule in our CVS.
There would be a separate web page and milestones and releases for anything
that is incubating.
> I have to reject all other options though:
> - You can not have a sub-project under VE. VE already is a
> sub-project of Tools and my understanding is that
> sub-projects can't have sub-projects.
> - I will not support an incubator project under Tools where
> the code is actually managed by an existing project. We don't
> have the PMC manpower to keep an eye on it. And it will only
> confuse your efforts to build up the VE community.
That is what I wanted to know.
> At the very least, you can start by getting the contribution
> into Bugzilla so you can start the IP process. People can get
> a copy of it from there. We've done that plenty of times in
> other projects.
This has already been done for a while for one of the two code
contributoins:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=204901
> > -----Original Message-----
> > From: tools-pmc-bounces@xxxxxxxxxxx
> > [mailto:tools-pmc-bounces@xxxxxxxxxxx]
> > On Behalf Of Philippe Ombredanne
> > Sent: Monday, October 22, 2007 2:05 PM
> > To: 'Tools PMC mailing list'
> > Subject: [tools-pmc] VE incubator - FOCUS
> > Importance: High
> >
> > All:
> > At that stage I would appreciate that we keep focused on my initial
> > request. So I am start a new thread.
> > I begin to be utterly confused but not yet hopelessly. VE is an all
> > volunteer project, so have some mercy.
> >
> > The only thing we need (for VE at least) is some flexibility: VE
> > Committers have expressed their whish to keep the current core code
> > base and project as is, not move back to incubation. I
> shall respect
> > that.
> >
> > We have new contributions comming from serious, law-abiding
> > individuals and organizations, and I want to keep up our fledgling
> > momentum.
> >
> > I can do it several ways:
> > -1/ an incubating component (a novel approach) would be
> preferred. -2/
> > an incubating project under VE. -3/ a tools incubator
> > -4/ a complete separate project.
> >
> > I am not asking asking for a discussion, but a simple
> answer on 1, 2,
> > 3 or 4 so I can move on.
> >
> > Cordially
> > --
> > Cheers
> > Philippe
> >
> >
> > --
> > Cheers
> > Philippe
> >
> > philippe ombredanne | 1 650 799 0949 | pombredanne at
> nexb.com nexB -
> > Open by Design (tm) - http://www.nexb.com http://easyeclipse.org -
> > http://phpeclipse.net - http://eclipse.org/atf -
> > http://eclipse.org/vep - http://labs.jboss.org/drools/ -
> > http://developer.mozilla.org/en/docs/XULRunner
> >
> > _______________________________________________
> > tools-pmc mailing list
> > tools-pmc@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/tools-pmc
>
