Hola, > I like having QA and docs as committers on projects. QA should be > putting test cases into the code base
Yes, but > and the only alternative is to have a separate project for QA. No. They can submit test cases via JIRA. > Similarly, docs are a very important part of a project and having the > docs right there with the code is a plus for me. For me too, but that has nothing to do with commit access. > Both QA and docs as proposed committers means to me that this project > already has mature processes in place that will be good for the > community. You're more trusting than I am. I still feel like commit access is something to be earned, and I get worried when we have more than a handful of people wanting commit access for these reasons when there are maybe that many total in the entire ASF (>1000 committers) who got commit access for doing just QA or just documentation. I don't mean to come off as overly harsh or serious on this. It seemed strange, I wanted to do a bit of due diligence and satisfy my curiosity. If the project team really feels like the only way these people can help the project is by having commit access, and no one else from the incubator PMC expresses a -1, then it's fine with me as well. -- Yoav Shapira Senior Architect Nimalex LLC 1 Mifflin Place, Suite 310 Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
