Let's add him to the committers group so he can close tickets. It doesn't grant commit on the project, it just means you can do more in our project with JIRA.
Martin, read this so you can see what we're trying to do with the current permissions: - https://lists.apache.org/thread.html/c43bff671730108ccb347990d9db950bcd4126f5b189c2504f5abff3@1218013764@%3Cdev.tomee.apache.org%3E Fully understand your perspective on lists vs jira. Most would describe that as lists vs pr comments vs jira comments. Either way, Apache is a mailing-list driven ecosystem so ultimately talking here is necessary for anyone to be given commit in the future. The motivation of the permission scheme is to help people embrace it. For those who want to learn more about this aspect of The Apache Way, see this: - http://theapacheway.com/on-list/ The famous quote is "If it didn’t happen on the mailing list, it didn’t happen." -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Nov 30, 2018, at 3:52 PM, Jonathan Gallimore > <[email protected]> wrote: > > Hi Martin > > Can you let me know your JIRA ID and I'll put you in the contributors group. > > Many thanks > > Jon > > On Fri, Nov 30, 2018 at 11:24 PM Jonathan Gallimore < > [email protected]> wrote: > >> Hi Martin! >> >> Thanks for posting, and welcome! I think it would be great to have your >> support on the JIRA side of things - many thanks for offering. I think our >> JIRA titles and descriptions in many cases probably only make sense to the >> developer who filed the ticket and probably doesn't mean too much to folks >> consuming the software. Any help you could give would be fantastic. >> >> I don't know what is involved permissions wise, but @David - perhaps you >> could help? We also have some folks I can assign issues to, and some I >> cannot. I don't have karma to make group changes. Happy to help if I can >> but I might need some more permissions myself :). >> >> Cheers >> >> Jon >> >> On Fri, Nov 30, 2018 at 10:41 PM Wiesner, Martin < >> [email protected]> wrote: >> >>> Hi folks, >>> >>> my name is Martin. @dblevins and I were discussing how individuals could >>> contribute to #TomEE. He convinced me to join the mailing list. >>> In the past, I contributed some user feedback, opened bug reports and >>> proposed improvements in exchange with @rmannibucau and @struberg. >>> >>> Some further background information: >>> I work in the field of Medical Informatics, doing research and teaching >>> for several years now at Heilbronn University (Germany), CS faculty. As >>> Richard (@zowalla) already mentioned in his welcome message, we are using >>> TomEE in software labs in our bachelor / master programmes and in regular >>> projects at our faculty, for instance, managing hardware loans to students >>> and staff members. >>> >>> How I could contribute (atm): >>> @dblevins and I discussed that I can support in keeping TomEE's JIRA >>> instance clean and comprehensible, e.g. by (a) identifying and closing >>> duplicates, (b) clarifying unclear descriptions or affected branches, (c) >>> communicating with reporters on missing details and so on and so forth. >>> Hopefully, other dev guys could benefit. Why? They might better identify >>> relevant topics or enhance existing bug reports... In addition, I could >>> screen discussions on the mailing list for "hidden gems" and open (or edit) >>> JIRA issues to give bugs and/or tasks a unique number within the issue >>> tracker. >>> >>> Why is this so important? >>> From my perspective, as a researcher and as software architect, clarity >>> often improves communication in, and efficiency of a project. I've >>> experienced this in many projects I’ve been involved so far. >>> >>> What do I suggest? >>> Maybe you can grant me elevated permissions within the project’s issue >>> tracker. If approved, I could then manage the aforementioned aspects within >>> TomEE’s JIRA instance. I’m familiar with this tooling as we have JIRA >>> running in our faculty. This instance is actually hosted by Richard and me. >>> >>> If I can help otherwise: feel free to ask. In case I say ’no’: please >>> don’t feel rejected. I’ll try to give an explanation in such a case. >>> >>> Best, >>> mawiesne >>> -- >>> https://twitter.com/mawiesne >>> >>
