IMHO good practice is that community is unaware of your company policies. There is no gain in enforcing internal policies to external community members.
Adapt. ) -- Carry a towel http://dataved.ru/ +7 916 562 8095 [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings [3] Start using Apache Openmeetings today, http://openmeetings.apache.org/ On Tue, Jul 31, 2018 at 7:06 PM, Dmitriy Pavlov <dpavlov....@gmail.com> wrote: > Dear Mentors, > > I have a question that I have not yet found an answer to. Can community > members assign tasks to other contributor in JIRA. I mean the case that > someone wants a particular contributor to do a task, can he or she assign > it directly to maintainer? > > Or contributor should always assign ticket to him or herself? > > Is this regulated/recommended by the Apache policies? Or it is given to the > community to decide. > > Thank you in advance. > > Sincerely, > Dmitry Pavlov > > P.S. Discussion recently occurred at Apache Ignite community dev. List > http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-jira-Assigned-IGNITE-9113-Allocate-memory-for-a-data-region-when-first-cache-assigned-to-this-red-td33172.html > > And I always believed that it is always necessary that only community > member can assign ticket to him or herself. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
