Cees Roele wrote:
Voting as contractual obligation?
No, but voting while also taking some form of responsibility for the
result of the vote.
While it is important to measure wether people WANT it supported, it is
equally important to determine whether it CAN be supported.
Things may change, support may falter, but at least right now, at this
moment, we would have need for enough support to justify making
something a 'community-supported' application.
Numerous reasons may prevent someone from actually maintaining code.
Time, opportunity, etc. But we need to have some people, other than the
original designer, willing - intending - to maintain the code when needed.
Right now, any application can be voted a 'community supported'
application, without anyone committing themselves to it.
People can vote in favor and then lay back waiting for others to
maintain it. While that is a bit black-and-white, and I certainly do
not expect people to vote that way, I think it is beneficial if we can
make 'teams' of developers, darfted from those voting in favor of an
application, on which we can call if maintenance is required.
Plus, such voting prompts teh question: if you do not want to put effort
in an application's maintenance yourself, then why do you expect the
rest of the community to do so?
And if people do not see it as a problem, then what is the problem of
committing yourself?
Gomez
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
