<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 28 Jul 2016, at 15:00, Martin Malina <<a href="mailto:mmalina@redhat.com" class="">mmalina@redhat.com</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. </div></div></div></blockquote><br class=""></div><div>Just a minor correction:</div><div><br class=""></div><div>We use different URL prefixes for reviewers and reporters. If a “reporter" accesses a “reviewer" url, he/she gets an "access denied”. That’s what you got when clicking on a JIRA link.</div><div><br class=""></div><div>The different url prefixes were required in previous versions of AERI. We could, however, change the current system to use only one url and so that <b class="">*all* reporters</b> get a <b class="">public/anonymized view of a problem</b>. Please note the word anonymized. Problems may contain senstive information like email addresses, error messages etc. We thus cannot make them public available to everyone as-is.</div><div><br class=""></div><div>However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we could do the same here.</div><div><br class=""></div><div>Max, Alexey, Fred,</div><div>what do you think?</div><div><br class=""></div><div><br class=""></div><div><br class=""></div><div><br class=""></div><div><br class=""></div></body></html>