[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [technology-pmc] Technology Project Charter
|
I think we need to revisit the incubator stream concept and all of the
wording that implies that the Technology Project cannot be a home for mature
and stable projects. Since incubators are now scattered everywhere, I
suggest replacing incubator stream with "projects whose scope doesn't fit
under another top-level project". Some of these can be in incubating state,
some in matured, etc.
The scope section needs similar changes. The current charter paints
everything under Technology as not ready for production, which hasn't been
the case for a while now, yet I have heard a number of projects raise
objection at taking dependency on projects located in Technology purely
based on the unstable/experimental perception. We need to fix that.
Statements on process maturity (as in scope section) should be a function of
a given sub-project, rather than inherited from Technology.
Are research and education streams even utilized? Have these been subsumed
by eclipse labs, github, etc?
- Konstantin
-----Original Message-----
From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Friday, April 08, 2011 11:17 AM
To: technology-pmc@xxxxxxxxxxx
Subject: [technology-pmc] Technology Project Charter
It's probably time to update the charter.
http://www.eclipse.org/technology/technology-charter.html
Any initial thoughts, PMC members?
Wayne
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
