Thanks, Frankie for your feedback. I have also found a little hard to navigate across the scenario you describe. it seems we (non committer) don't have enough flexibility to interact and therefore we can't depend on JIRA workflow.
The happy path scenario would be to have JIRA workflow access, but if that is not possible I wonder if, in the same way, we have committers reviewing PRs, we can also have committers performing JIRA administration task. This means that after a non-committer creates a Jira ticket, he/she should ask in the list for a committer to assign the JIRA. About the PR without Jira tickets, I wonder if in the past there are some lessons learned when the project tried to have a "no JIRA, no PR merge" policy. Without that background, my vote would be +1, but I would like to hear more opinions and point of views. El mar., 4 dic. 2018 a las 6:34, Frankie (<[email protected]>) escribió: > Now it has happened the second time to me that I prepared to work on a task > and only by chance noticed in time that someone else has already picked it > up. > It would be frustrating spending time for nothing - or knowing that someone > else did (when I have been faster) > > David said "Most important thing I think is to say what code you'll be > working on before you invest the time, just to make sure someone else is > not > also cleaning the same code (duplication)." > ( > http://tomee-openejb.979440.n4.nabble.com/JIRA-ticket-and-PR-s-td4685790.html > ) > - but I dont't know how to do this. > > The two examples: > > [1] > > http://tomee-openejb.979440.n4.nabble.com/Merging-Old-and-New-Websites-td4685488.html > David worked on this when I wanted to add some notes to the website. There > was no JIRA ticket. So obviously it's not enough to check JIRA before > creating a new ticket ... > > [2] > > https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2316?filter=allopenissues > When I prepared to have a look at this I saw a PR message in the mailing > list. > There was a JIRA ticket but noone seemed to be working on it since it was > unassigned ... > > So I wonder how this is organized in this project. How can I know that a > task is "free" (noone working on it) and how can I tell the community that > I'm gonna work on a task? > When I read throught the mailing list I often found that for every task > there should be a JIRA ticket. But it doesn't seem to happen in real life > reliably. And even when I create a JIRA ticket I have no permission to > assign it to myself to let others know that I will do the task. > > Any hints to help me to feel more comfortable? Is there an "official > workflow"? > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html > -- Atentamente: César Hernández Mendoza.
