This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
When you post your contributions to the mailing list, after a few months
they are effectively lost to the rest of the community, since it takes a
reasonable amount of effort search the mailing list to find if any
particular patch is just what the user wants. The eCos community has lost
the benefits of your contribution.
I also disagree with the notion that to get better responsiveness, we should enter into a service contract with the eCos maintainers. In the Open Source model, the respository is community property and it's up to the community to maintain it and improve it. Currently the select group of people who have write access to the CVS tree act like a QA team for the rest of us. If they don't have the time to be responsive, we as a community have to help them out or the community has to development a different gatekeeper mechanism to improve responsiveness.
The only thing I can suggest at this time, is how do other successful Open Source projects handle this problem?
Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |