Setting Assignee doesn't mean that the ticket is reserved for that
particular person. If anyone wants to participate in that ticket he can
always ask about that in JIRA or on mailing list. In fact, this is how we
deal with tickets that got stuck on a contributor for a long time.
On Wed, Aug 1, 201
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 rep
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, rat
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 Co
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
ti
Vyacheslav,
Thank you! This seems exactly what I was asking about.
On Wed, 1 Aug 2018 at 10:18 Vyacheslav Daradur 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/IGN
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 wrote:
>
> Folks,
>
> I
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\expert
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
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
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
o
11 matches
Mail list logo
