Hi Vladimir, please see Code of conduct principles https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofConductforApacheprojects? I would be happy to have a chat with you about Apache and open source principles.
I encourage all Igniters to carefully read thread with ASF fellows replies: https://lists.apache.org/thread.html/c6013b99940de32aae831a0b76e8fd53febe5040e9e0d67abb4f62a5@%3Cdev.community.apache.org%3E (I can't say better). We, as community, has a huge potential of growing. I beleive if someone strongly wants to assign ticket directly , that means other community members can not complete this ticket, - This problems do matter, and it is deeper than mechanical action in JIRA. I would like that 'domain expert' share their knowlege instead completing tickets. Tickets completion is investing into product codebase. Let's invest in community so every contributor will became 'domain expert'. That is my point, and I hope it make sense to you and for every Igniter. Sincerely, Dmitriy Pavlov ср, 1 авг. 2018 г. в 13:11, Vladimir Ozerov <voze...@gridgain.com>: > Dmitry, > > "If something is not happened on mailing list it is not happened" is just > not true. Mailing list is only one of communication channels. I do not see > any reason why I need to discuss assignee on a dev list .This is just spam > for 99% of members. > > Again - lets focus on things that matter, rather than on bureaucracy. I > thought that we overgrown those old days in incubator when we thought that > the only extreme is possible in ASF - to log your every breath on the dev > list. . > > On Wed, Aug 1, 2018 at 12:32 PM Dmitriy Pavlov <dpavlov....@gmail.com> > wrote: > > > Hi Vladimir, > > > > I think I understand your point. I've heard negative feedback. Which is > why > > I would like to speak it up, I hope other Igniters who disagree with this > > assignment will be feeling free to unassign ticket. I would like that > noone > > was trying to adapt commercial company experience to the Comminuty. > > > > It's a pity that I need to continiously remind some of Igniters about > > principle: > > "If something is not happened on mailing list it is not happened." > > > > In you case you can decide who will do ticket on dev.list - (it is > > perfectly ok if only you two of you will communicate) - or tell your > fellow > > to pick up ticket. > > > > Sincerely, > > Dmitriy Pavlov > > > > ср, 1 авг. 2018 г. в 10:58, Vladimir Ozerov <voze...@gridgain.com>: > > > > > In general there is nothing wrong with assigning a ticket to someone if > > you > > > know that this would not cause negative reaction from assignee side. > The > > > thing is that community has a lot of members who knows each other in > > person > > > and in close contact for years. So there is nothing wrong if I assign a > > > ticket to my fellow. Especially if ticket is complex or critically > > > important for the product. These is no "project management" in such an > > > action. > > > > > > On the other hand, we should not overuse this practice, and set > specific > > > assignee only if there is a string reason for this. > > > > > > All in all, remember that community is alive thing built of real > people. > > > The more rules you set without a clear reason, the more uncomfortable > it > > is > > > to be in such a community. > > > > > > On Wed, Aug 1, 2018 at 10:30 AM Maxim Muzafarov <maxmu...@gmail.com> > > > wrote: > > > > > > > Vyacheslav, > > > > > > > > Thank you! This seems exactly what I was asking about. > > > > > > > > > > > > On Wed, 1 Aug 2018 at 10:18 Vyacheslav Daradur <daradu...@gmail.com> > > > > wrote: > > > > > > > > > Hi, Maxim, > > > > > > > > > > There is information about project components maintainers [1], but > > I'm > > > > > not sure if it is actual. > > > > > > > > > > [1] > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers > > > > > On Wed, Aug 1, 2018 at 9:33 AM Maxim Muzafarov <maxmu...@gmail.com > > > > > > wrote: > > > > > > > > > > > > Folks, > > > > > > > > > > > > I don't think we need additional notification for catching > > attention > > > of > > > > > > some community > > > > > > experts. Such notifications can be overused by other > participants. > > > > > > Developer mail list > > > > > > the best place we have for any discussions. > > > > > > > > > > > > What I really would like to have is the list of community > > > > members\experts > > > > > > and their zones > > > > > > of Ignite project code responsibilities. May be such list already > > > > exists, > > > > > > does it? > > > > > > > > > > > > As for me, I think we should pose right the complexity of the > issue > > > at > > > > > the > > > > > > moment > > > > > > of their creation. Ask expert to provide some high level > > > implementation > > > > > > details and > > > > > > keep it unassingned, so anyone can take it. > > > > > > > > > > > > On Wed, 1 Aug 2018 at 01:09 Nikolay Izhikov <nizhi...@apache.org > > > > > > wrote: > > > > > > > > > > > > > How about mention desired expert with some predefined message? > > > > > > > So expert can setup simple email filter and know about tickets > > that > > > > > have > > > > > > > to be done. > > > > > > > > > > > > > > Example: > > > > > > > > > > > > > > "[~dpavlov] TFY" - ticket for you. > > > > > > > > > > > > > > В Вт, 31/07/2018 в 14:04 -0700, Dmitriy Setrakyan пишет: > > > > > > > > Dmitriy, > > > > > > > > > > > > > > > > I would agree with everything you are saying. There are some > > > > tickets, > > > > > > > > however, that cannot be done by just anyone and preferably > have > > > to > > > > be > > > > > > > > looked at by certain domain experts. In those cases only it > > would > > > > be > > > > > OK > > > > > > > to > > > > > > > > assign a ticket explicitly in my view. For all other cases we > > > > should > > > > > > > allow > > > > > > > > the community pick up a ticket they want to work on. > > > > > > > > > > > > > > > > D. > > > > > > > > > > > > > > > > On Tue, Jul 31, 2018 at 10:34 AM, Dmitriy Pavlov < > > > > > dpavlov....@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Igniters, > > > > > > > > > > > > > > > > > > Ignite is complex project and sometimes we know > > > > > > > > > 1. who can solve the issue > > > > > > > > > 2. and we would like that particular contributor would take > > an > > > > > issue. > > > > > > > > > > > > > > > > > > In the same time "in an open source community where > > everything > > > is > > > > > > > > > distributed, asynchronous and volunteer work we should > leave > > > the > > > > > issues > > > > > > > > > open to anyone until someone volunteers to work on it." > > > > > > > > > > > > > > > > > > It seems it is not prohibited by Apache to assign it > > directly, > > > in > > > > > the > > > > > > > same > > > > > > > > > time it is better for community grown to avoid it: > > > > > > > > > "Assigning things to people seems the role of a project > > manager > > > > > that > > > > > > > has > > > > > > > > > some sort of power over the managed team. Speaking from > > > > experience > > > > > I > > > > > > > do not > > > > > > > > > take it nicely when someone that uses the project I am a > > > > volunteer > > > > > at > > > > > > > > > (which I might now know ) "assigns work" to me." > > > > > > > > > > > > > > > > > > Please find Apache mentors' comments on this: > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/c6013b99940de32aae831a0b76e8fd > > > > > > > > > 53febe5040e9e0d67abb4f62a5@%3Cdev.community.apache.org%3E > > > > > > > > > > > > > > > > > > > > > > > > > > > Please share you vision. > > > > > > > > > > > > > > > > > > Sincerely, > > > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > > > > > > > > -- > > > > > > -- > > > > > > Maxim Muzafarov > > > > > > > > > > > > > > > > > > > > -- > > > > > Best Regards, Vyacheslav D. > > > > > > > > > -- > > > > -- > > > > Maxim Muzafarov > > > > > > > > > >
