Thanks Chip. I thought what is the point in submitting half-cooked stuff ? I waited for almost a month before reverting my earlier commit and deciding to go ahead with Review Board!
My life as a writer is of course troublesome if the concerned has no time (max 30 min - 1 hour !!!) to look at the doc/ reply to the queries/ explain features/ reviews. Any penalties for people who BLOCK documentation development ? -----Original Message----- From: Chip Childers [mailto:chip.child...@sungard.com] Sent: Thursday, April 11, 2013 6:35 PM To: dev@cloudstack.apache.org Cc: Radhika Puthiyetath Subject: [DOCS] Documentation focused committers, and review processes Hi all, I've observed Radhika struggling to get reviews of her feature docs, and having to work to provide patch after patch for reviewboard submissions. I have a proposal (which I think Joe hinted at in another thread): Doc writers with commit rights shouldn't use reviewboard to elicit reviews from feature developers. They have access to the repo directly. Instead, commit away anything that would have previously been posted to reviewboard. There's a reason that we try to move folks from contributor to committer on the project, right? ;-) Radhika, perhaps you just commit what you have for review if you feel that it's close enough to publish. Point people to jenkins.cs.o jobs to review the content if required. Questions that block even the initial doc authoring process obviously continue to be raised on this list. Would this make life easier for you Radhika? -chip
