Ahumm.. I'm not sure whether you are familiar with the Apache way here. Apache never puts hard and fast rules on the community saying that every query in the mailing list should be answered. Infact the CLA (Contributors Licence Agreement) section 6 specifially states that a committer is not obliged to provide support unless he desires to do so. BTW if you look at the committers page at http://www.apache.org/dev/committers.html, it says that the committers responsibility list is not authoritative. In other words commiters are not forced upon to do what they do by Apache in anyway. I agree that an opensource community should be having timelines. But these timelines are not decided by the need of anyone in particular but by the community in consensus. it does not happen in a formal manner like in a commercial setting where there are rigorous timelines. So in short whatever happens in Apache happens with whatever the community thinks as suitable.
> [Soumadeep] An open source community doesn't mean that it's doesn't share > any time lines or responsibilities, I completely disagree with your > statement as above > No matter what your other obligation may be if you take a responsibility > being a committer you should see to it that it's done ASAP. I thing the > moderator/release manager should take note of this. Someone has to be > answerable no matter what. As community members we all are answerable. > -- Ajith Ranabahu
