We should keep in mind that contributor do not have to do anything, as this is community. Instead, it is responsibility of the community to make sure that contributions are processed in a timely manner, and that contributors have positive experience with us.
So, -1 from my side. On Mon, Jun 5, 2017 at 6:28 PM, Anton Vinogradov <a...@apache.org> wrote: > Igniters, > > Currently, according to > https://cwiki.apache.org/confluence/display/IGNITE/How+ > to+Contribute#HowtoContribute-SubmittingforReview > , > contributor can ask for review by moving ticket to PATCH AVAILABLE state. > > And, as far as I can see, this cause broken tickets issue. > Contributor can wait somebody who'll review his changes for a month or even > more. > > I propose to change workflow and *make contributor responsible to find > reviewer*. > It's pretty easy to find a person able to review changes in most of cases. > > 1) You can check git history of files you modified and find persons with > expertise in this code > 2) In case you have problems with such search you can always use > maintainers list ( > https://cwiki.apache.org/confluence/display/IGNITE/How+ > to+Contribute#HowtoContribute-ReviewProcessandMaintainers > ) > > Thoughts? >
