[jbosstools-dev] [aeri] Now supports github logins

[Max Rydahl Andersen]

On 2 Aug 2016, at 14:06, Martin Malina wrote:

> > On 30. 7. 2016, at 2:30, Alexey Kazakov <alkazako at redhat.com> wrote:
>>
>> I think we should grant reviewer access to all members of jbosstools 
>> org. For example QE may not have push access in github but we still 
>> want them be able to create issues based on aeri reports.
>
> I agree :) So can you make it happen please, Marcel?

+1

As long as the possible private sensitive data are not publically 
available
and we know who have access and we can add/remove people we should be 
fine.

And by we I mean JBoss Tools and Developer Studio development team.

/max

>
> Thanks,
> Martin
>
>> Regarding links in jira... Ideally the same link should work for 
>> everyone with optional GitHub authentication. If you do not login or 
>> you are not a jbosstools org member you see a public version of the 
>> report. Otherwise you see what you are supposed to see corresponding 
>> to your role.
>> If it requires significant efforts to implement then can we post a 
>> few links for different roles with clear descriptions as a 
>> workaround?
>>
>> WDYT?
>>
>>
>> On Jul 28, 2016, at 6:32 AM, Marcel Bruch 
>> <marcel.bruch at codetrails.com <mailto:marcel.bruch at codetrails.com>> 
>> wrote:
>>
>>>
>>>> On 28 Jul 2016, at 15:00, Martin Malina <mmalina at redhat.com 
>>>> <mailto:mmalina at redhat.com>> wrote:
>>>> In my opinion, it would make sense to just give the reporter role 
>>>> to the whole jbosstools team on github.
>>>
>>> Just a minor correction:
>>>
>>> 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.
>>>
>>> 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 *all* reporters get a public/anonymized view of a 
>>> problem. 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.
>>>
>>> However, at Eclipse we agreed on showing a anonymized view might be 
>>> perfectly okay. So we could do the same here.
>>>
>>> Max, Alexey, Fred,
>>> what do you think?
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org 
>>> <mailto:jbosstools-dev at lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev 
>>> <https://lists.jboss.org/mailman/listinfo/jbosstools-dev>


> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen