<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="">Hi Marcel,<div class=""><br class=""></div><div class="">Thanks for the details. I don't think the solution is to add devdoc and website teams - there are still many in our QE team who are in neither of these. In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. But as you say, this has to be decided by the org-admins - Alexey and Fred?</div><div class=""><br class=""></div><div class="">-Martin<br class=""><div class=""><div class=""><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 28. 7. 2016, at 14:52, Marcel Bruch <<a href="mailto:marcel.bruch@codetrails.com" class="">marcel.bruch@codetrails.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Max,</span><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></div><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class=""><blockquote type="cite" class=""><div class="">On 28 Jul 2016, at 14:34, Max Rydahl Andersen <<a href="mailto:manderse@redhat.com" class="">manderse@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On 28 Jul 2016, at 14:16, Marcel Bruch wrote:<br class=""><br class=""><blockquote type="cite" class="">Martin,<br class=""><br class="">I just checked your roles. You only got Reporter rights assigned (the default) b/c your teams devdoc and website were not enabled for reviewer access by your org-admins.<br class=""></blockquote><br class="">what does reviewer access mean in this context ?<br class=""></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">There are three roles: reporters, reviewers and org-admins. Reporters can only see public information of a problem while reviewers can edit data, create bugs etc. org-admins can administrate different aspects of the installation.</div><div class=""><br class=""></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class="">Would it be sufficient to add a read-only group that have access to all repos and add everyone without push access to look ?<br class=""></div></blockquote><div class=""><br class=""></div><div class="">I’ve discussed several options with Fred and Alexey last week.</div><div class=""><br class=""></div><div class="">Just repeating them briefly:</div><div class=""><br class=""></div><div class="">1. If all organization members should get reviewer access, simply do no select any team. We’ll then check membership against the organization members.</div><div class=""><br class=""></div><div class="">2. It may make sense to create a group especially for accessing error reports (e.g. aeri). There simply add everyone who needs access to error reports.</div><div class=""><br class=""></div><div class="">3. If some teams should not / do not require access to error reports, simply do not select their teams in the oauth authorization panel - that’s what’s used ATM.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Whatever you decide, just update the configuration - or let me know.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Please note that you still can log in with the previously used username/password.</div><div class=""><br class=""></div><div class=""><div class="">Marcel</div></div><br class=""><blockquote type="cite" class=""><div class=""><br class="">/max<br class=""><blockquote type="cite" class=""><br class="">Org-admins, is this an oversight?<br class=""><br class=""><blockquote type="cite" class="">BTW,<span class="Apple-converted-space"> </span><a href="https://redhat.ctrlflow.com/" class="">https://redhat.ctrlflow.com/</a><span class="Apple-converted-space"> </span><<a href="https://redhat.ctrlflow.com/" class="">https://redhat.ctrlflow.com/</a>> gives this:<br class="">{"timestamp":1469705301444,"status":404,"error":"Not Found","message":"No message available","path":"/"}<br class=""></blockquote><br class="">Agreed, we should make this more meaningful again.<br class=""><br class="">Marcel<br class=""></blockquote><br class=""><br class=""><blockquote type="cite" class="">_______________________________________________<br class="">jbosstools-dev mailing list<br class=""><a href="mailto:jbosstools-dev@lists.jboss.org" class="">jbosstools-dev@lists.jboss.org</a><br class=""><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" class="">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br class=""></blockquote><br class=""><br class="">/max<br class=""><a href="http://about.me/maxandersen" class="">http://about.me/maxandersen</a><br class=""></div></blockquote></div><br class=""><div apple-content-edited="true" class=""><div class="" style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">-- </div>Codetrails GmbH<br class="">The knowledge transfer company<br class=""><br class="">Robert-Bosch-Str. 7, 64293 Darmstadt</div><div class="" style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Phone: +49-6151-276-7092<br class="">Mobile: +49-179-131-7721<br class=""><a href="http://www.codetrails.com/" class="">http://www.codetrails.com/</a></div><div class="" style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br class="">Managing Director: Dr. Marcel Bruch<br class="">Handelsregister: Darmstadt HRB 91940</div></div></div></div></blockquote></div><br class=""></div></div></body></html>