bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Martin <>
Subject Re: Access to issue tracker (Was: Re: Relaxing access control to the Bloodhound source)
Date Thu, 10 Jan 2013 09:21:10 GMT
I think that we should be attempting to roughly replicate the 
permissions for users of the rest of On jira, the 
introduction currently states:

    Anyone is free to find issues. You must register and login if you
    want to create, comment, vote, or watch issues. Only developers can
    edit, prioritize, schedule and resolve issues.

If we take developers to mean apache committers, strict adherence to 
that could result in a downgrade of some existing accounts but the 
restriction does not seem completely unreasonable.


On 10/01/13 09:06, Peter Koz(elj wrote:
> That is a good idea. The question is what permissions should be granted?
> They should probably at least have right to post comments and put issues in
> review state.
> Peter
> On 9 January 2013 17:32, Gary Martin <> wrote:
>> Given the aim of removing technical barriers to contributions from apache
>> committers, I was wondering if we could also do something to lower the
>> barriers for committers to our issue tracker.
>> I am not yet sure what is currently technically possible between
>> Bloodhound and infrastructure, but it strikes me that it would be nice to
>> be able to either automatically allow committers to have access or to have
>> common authentication with the rest of
>> Obviously we would need to make sure that the existing non-apache
>> committers can continue to contribute and I suspect that we would also
>> continue to look after permissions.
>> Any thoughts?
>> Cheers,
>>      Gary

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message