Hi Jon, my JIRA ID simply is: "mawiesne"
Best, mawiesne -- https://twitter.com/mawiesne <https://twitter.com/mawiesne> > Am 01.12.2018 um 00:52 schrieb Jonathan Gallimore > <jonathan.gallim...@gmail.com>: > > 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 < > jonathan.gallim...@gmail.com> 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 < >> martin.wies...@hs-heilbronn.de> 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 >>> >> -- Dipl.-Inform. Med. Martin Wiesner Research Associate Hochschule Heilbronn – University of Applied Sciences Max-Planck-Str. 39 D-74081 Heilbronn phone: +49 (0)7131 - 504 1124 bzw. 504 6947 fax: +49 (0)7131 - 252 470 mail: martin.wies...@hs-heilbronn.de <mailto:martin.wies...@hs-heilbronn.de> web: http://www.mi.hs-heilbronn.de/ <http://www.mi.hs-heilbronn.de/> GMDS-AG Consumer Health Informatics web: https://gmds.de/aktivitaeten/medizinische-informatik/arbeitsgruppenseiten/consumer-health-informatics-chi <https://gmds.de/aktivitaeten/medizinische-informatik/arbeitsgruppenseiten/consumer-health-informatics-chi/>
smime.p7s
Description: S/MIME cryptographic signature
