|
Hi all,
almost 2 weeks ago I invited to join a little poll about
how much Rules Eclipse needs. The results are in, and quite interesting I'd
think:
35 people participated, the
majority voting for "Guidance" through rules and "Ok to have rules since we all
gain from the train". Looks like the PC is doing the right thing after all.
Thanks, Planning Council!
And for those who're still
not happy with their must-do's, I believe they can still negotiate. If I'm not
mistaken, the process for negotiation is asking your PMC representative at the
PC represent your concerns during the next call (correct,
Richard?)
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Hi Thomas and all,
I find this discussion extremely interesting.
How much Control does Eclipse need to avoid falling apart as
it grows?
I created a little poll for this:
Looking forward to interesting
results,
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management
Project Lead, DSDP PMC Member
I miss the good old days when Open Source communities were based
on the contributions that they got, where the contributors were heroes, and
the quality of the resulting product were the product of their goodwill and
skill. I find that participating in the Eclipse release train nowadays
involves efforts that are somewhat overwhelming and that I, instead of
adding valid functionality to the areas where I contribute, am forced to
implement requirements that brings much less benefit to the intended user
base.
I think that when a central management stipulates this many
requirements for individual projects, there's a high risk that all the fun
is taken out of it. As a contributor, and even as a project manager, I loose
control. I no longer decide what's important in my own domain. I no longer
prioritize what to do with the time I spend on the projects. Someone else
does. A lot of the motivation is thereby lost, replaced with a whip that
forces me to comply with a strict set of rules. Was that the intention? I
don't think so.
Don't get me wrong, I can see that there are benefits
in having a common set of requirements. I just think it's a tad too much
now.
Regards,
Thomas Hallgren
Schaefer, Doug wrote:
It'll be interesting to see what happens when we get
to the Release Review and find few of us actually did all the must dos.
Unfortunately, the must do's didn't come with additional contributions and
I can't seem to pull any out of my, uh, never mind. I see Doom ahead
unless a Christmas miracle happens.
Doug.
Hi Team, with respect to the questioning of the capabilities as a
"must do":
http://ahuntereclipse.blogspot.com/2008/11/i-just-dont-have-any-capabilities.html
and
further comments should go on https://bugs.eclipse.org/bugs/show_bug.cgi?id=252807
Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software
Development Manager: Eclipse Open Source Components
IBM Rational
Software: Aurora / GEF / GMF / Modeling Tools
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
