Thanks, you see, I'm not a committer for code, I have very little programming experience other than scripts/automation.
I'm more a marketing/evangelist/teaching/support kind of guy. So if asked to review code, I would not be a good choice. If asked to review policy/procedure/compliance/design/architecture(non-code), than I am your guy. That brings me to a question, how does one use the review board? Is there a how-to/guidelines wiki article you can point me too? Thanks -kelcey >-----Original Message----- >From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >Sent: Friday, February 15, 2013 4:26 PM >To: cloudstack-dev@incubator.apache.org >Subject: RE: [ACS41] Yet another reviewboard reminder... for both >committers and contributors. > >Well the submitter of the review https://reviews.apache.org/r/9336/ listed >you as one of the reviewers and I was calling out based on that. > >Ok so what should one do if someone lists you as a reviewer? If you cannot or >not qualified to review you can respond saying that you cannot do that >review and submitter can ask another reviewer. > >I will update the review board guidelines. > >Animesh > > >> -----Original Message----- >> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com] >> Sent: Friday, February 15, 2013 3:05 PM >> To: cloudstack-dev@incubator.apache.org >> Subject: RE: [ACS41] Yet another reviewboard reminder... for both >> committers and contributors. >> >> My name got attached to 1180, and I'm not sure why. I am not what you >> would call capable of reviewing the submission other then from a >> legal/compliance perspective. >> >> Thanks >> >> -Kelcey >> >> >-----Original Message----- >> >From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >> >Sent: Friday, February 15, 2013 12:05 PM >> >To: cloudstack-dev@incubator.apache.org >> >Subject: RE: [ACS41] Yet another reviewboard reminder... for both >> >committers and contributors. >> > >> >Folks >> > >> >I have sent emails on over 30 issues from review board this week and >> >as community we responded to 2/3 rd of them which is good but can be >better. >> >We were able to knock off only a handful of them. Out of the ones >> >that were responded to many of them are awaiting action from >> >reviewers. If you were called out please respond to your reviews and >> >help us close pending >> reviews. >> > >> >We have 33 pending reviews in review board at this time >> > >> >Animesh >> > >> > >> > >> >> -----Original Message----- >> >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] >> >> Sent: Monday, February 11, 2013 11:24 PM >> >> To: cloudstack-dev@incubator.apache.org >> >> Subject: RE: [ACS41] Yet another reviewboard reminder... for both >> >> committers and contributors. >> >> >> >> Folks >> >> >> >> I have sent a number of reminder emails for some of the review >> >> board items that have been pending for a while. Please attend to >> >> them at the earliest . We are running at 50+ items in review board. >> >> If you are a committer I request you knock off 1-2 reviews per week >> >> >> >> Animesh >> >> >> >> > -----Original Message----- >> >> > From: Chip Childers [mailto:chip.child...@sungard.com] >> >> > Sent: Tuesday, January 29, 2013 9:18 AM >> >> > To: cloudstack-dev@incubator.apache.org >> >> > Subject: [ACS41] Yet another reviewboard reminder... for both >> >> > committers and contributors. >> >> > >> >> > Hi all (and specifically people that were listed as "maintainers" >> >> > of certain code modules), >> >> > >> >> > We need committer help in getting the community contributions >> >> > currently in reviewboard (as well as some that we expect to show >> >> > up in the next day or so) reviewed and committed as soon as possible. >> >> > >> >> > If you are a "maintainer", or simply feel that you have enough >> >> > knowledge to get through one or more of these reviews, PLEASE >> >> > take some time to help clear out the board. >> >> > >> >> > Based on our agreed upon schedule, we need everything into master >> >> > (or >> >> > javelin) by EOD Thursday. >> >> > >> >> > For those of you that have code you want to be reviewed, but have >> >> > not yet submitted, it needs to get in ASAP. Otherwise, there's >> >> > no chance that someone will have the time to review and commit >> >> > before we cut the >> >> release branch. >> >> > >> >> > -chip
