Hi Dmitriy, I agree that person is right in that case, but Alex G. is not only one person who can complete the issue.
I agree it is not newbie ticket, but this assigned ticket is locked by assignee (see https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute ) My concern is related not to this ticket, but to our process: I've heard complains from Igniters if someone assigns ticket to person, who are not going to complete it. I would appreciate if you find topic where Apache mentor explain it. I could learn it and can tell other Igniters how it works. Sincerely, Dmitriy Pavlov вт, 31 июл. 2018 г. в 1:33, Dmitriy Setrakyan <dsetrak...@apache.org>: > Dmitriy, > > I am still struggling to understand which portion of the code of conduct is > being violated. BTW, this point was raised during the Ignite incubation > process and the community agreed that it is up to the project community > itself to decide on the best process here. This is not an Apache matter (I > am too lazy to look for the thread now). > > I have been on this project long enough to have a good understanding who in > the community has the best knowledge to fix a certain issue. When an issue > requires strong domain expertise, I will assign a ticket to a certain > domain expert to ensure that he or she are at least aware of it and try to > address it. If they cannot, then they can always unassign it. > > I also use the table at the bottom of this page to find out domain experts > on different sections of the project: > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > BTW, this ticket in particular is absolutely not a casual newbie ticket and > can have dire consequences on the project quality if done wrong. Therefore, > I have picked the best domain expert to implement it or at least to comment > on it. I will assign it back to AG, unless we decide as a community that it > is a wrong process. > > If you disagree with the process, please do not unassign any ticket > yourself. Feel free to start a separate discussion and we can have a PMC or > community decision on it. > > D. > > On Mon, Jul 30, 2018 at 3:22 AM, Dmitriy Pavlov <dpavlov....@gmail.com> > wrote: > > > Hi Dmitriy, Igniters, > > > > I would like to ask an assistance from experienced Ignite contributors > > here. I'm still trying to find clear reference on that. > > > > In the same time I beleive that assignment to other person, who probably > > will not work on issue, confronts at least with Code of conduct > > http://www.apache.org/foundation/policies/conduct.html This policy is to > > be > > followed in spirit as much as in the letter. > > > > Assigning issue means no one else in the community can begin working on > it. > > Let's suppose contributor would like to complete issue, than he or she > will > > have to ask assignee to move issue to unassigned before he or she can > > start. It is not welcoming and discourage people from contribution. > > > > So my proposal is as follows: > > - to encourage particular contibutor to pay attention let's use > > -- direct mention in issue comments (it has almost the same effect: > email > > will be sent) > > -- dev. list and CC to contributor's email > > > > - and keep ticket unassigned > > -- until contributor starts > > -- or going to start actual implementation. > > > > Sincerely, > > Dmitriy Pavlov > > > > сб, 28 июл. 2018 г. в 15:50, Dmitriy Setrakyan <dsetrak...@apache.org>: > > > > > On Sat, Jul 28, 2018 at 2:20 AM, Dmitriy Pavlov <dpavlov....@gmail.com > > > > > wrote: > > > > > > > Hi Dmitriy, > > > > > > > > As far as I know this approach is contlicting with the Apache Way. We > > > > should be absolutely sure that assignee is agree and going to do this > > > task. > > > > But in our case domain expert did not replied to dev list topic. > > > > > > > > > > I do not see any conflict with any Apache rule at all. By assigning a > > > ticket to someone I am suggesting that as a domain expert it is > > preferable > > > that he or she looks at it. If not, these people can un-assign or > > reassign > > > the ticket. > > > > > > If you believe there is a conflict with some Apache principle, please > > > provide a link so we could all learn about it. > > > > > > To solve lost ticket problem I suggest to use dev. list and bumping > > up/ping > > > > messages. > > > > > > > > > > Agree, I do that too. > > > > > > > > > > I hope it makes sense to you. If not, I will do my absolute best to > > find > > > > out corresponding ASF policy. > > > > > > > > > > Please do. > > > > > > > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > сб, 28 июл. 2018 г. в 3:28, Dmitriy Setrakyan <dsetrak...@apache.org > >: > > > > > > > > > On Fri, Jul 27, 2018 at 3:02 PM, Dmitriy Pavlov < > > dpavlov....@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > Hi Igniters, > > > > > > > > > > > > I would discourage all Igniters from direct assigning issues to > > > anyone > > > > > > else. Of cource excepting the case it was directly discussed with > > > > > asignee. > > > > > > Any contributor should be able to assign issue to himself. > > > > > > > > > > > > I left issue unassigned until Alex G would assign it. > > > > > > > > > > > > > > > > Dmitriy, I disagree. If there is a domain expert, then the issue > > should > > > > be > > > > > assigned to him/her whenever possible. If that person is too busy, > > > he/she > > > > > could ask someone else for help. This way the tickets will get > > > attention > > > > > faster and will get resolved faster. > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-9113 > > > > > > > > > > D. > > > > > > > > > > > > > > >
