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.
> >
>

Reply via email to