|Re: [cross-project-issues-dev] Galileo Must-do's|
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.
Schaefer, Doug wrote:
Back to the top