| RE: [eclipse.org-planning-council] A suggested topic for Planning Council Discussion |
|
Lol J You win this round Knuckles! The IP issue is a good point and will
grant you that. As for requirements, other than holding up
the IP process I’m not sure what stick the EMO has to enforce projects
meet the requirements. If projects don’t have the resources or the
mandate from the employers of the resources to do the work, it doesn’t
happen. And if you kick projects off the train because of that, that could poison
the community. The best stick still is influencing and that involves good communication
channels open between the requirers and requirees, and, of course, a reasonable
set of requirements. Doug Schaefer, QNX Software Systems From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Gaff, Doug How about this:
Bjorn “Knuckles” Freeman-Benson. It’s shorter and still
conveys the same message. J You know we love
you! From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson Doug, David, et al., Even if you’re a project that does
get removed, you can still release on the same day. Other than getting your
bits mentioned in an over crowded update site, it’s not overly obvious
what the benefits of being in the simultaneous release trains are at the
moment. The major advantage of
being in the train is priority in getting your IP reviewed. Clearly there is
going to be more demand for IP reviews than the legal team will be able to
handle - that's just a fact. As per the Board's desire, the IP team will
prioritize the "on the train" projects higher than the "off the
train but wanting to release on the same date" projects... And, if you
don't have your IP reviewed, you can't release your bits... etc. So if you're a
project that does get removed, you (may or) may not be able to release on the
same day. And in my mind that’s the real
problem with the RC. Their influence in the day to day operations of Eclipse
projects isn’t very strong. Perhaps a better term is
"non-existent" :-) Given that committers are the only ones
that have power on the projects, Unfortunately, that's not true. The Board also has
power over the projects. The Board defines the IP process, for example, and
that has a big effect on the projects. And the Board has passed a unanimous
resolution about the projects (and simultaneous release) being better this
year. So... we (the EMO) need to follow this directive from the Board. And that
means that we need firm requirements that raise the bar. Hence this discussion. -- [end of message] |