Update on bug system for OpenJDK (web-discuss)

[David Herron]

FWIW there is a range of possible permissions or capabilities each authenticated person could have. That is, rather than two authentication systems (bug reports, mercurial checkin rights) what about a single authentication system that handles not just these two access control issues, but potentially others in the future?

Just a thought from someone with no skin in the game. 

David Herron



On May 27, 2011, at 7:08 AM, Volker Simonis <volker.simonis at gmail.com> wrote:

> Yes, that sounds reasonable. But that would still require some sort of
> mechanism which allows "Contributors" to authenticate themselves in
> the new bug tracking system that probably nobody has thought about
> until now..
> 
> On Fri, May 27, 2011 at 2:48 PM, Dr Andrew John Hughes
> <gnu_andrew at member.fsf.org> wrote:
>> On 27 May 2011 13:43, Volker Simonis <volker.simonis at gmail.com> wrote:
>>> Ok, then maybe we have to specify more precise what a "Contributer" is:
>>> 
>>> 1. According to the OpenJDK site (http://openjdk.java.net/contribute/)
>>> it's an individual who has signed the OCA. But currently these
>>> "contributors" don't get any "credentials" they could use to
>>> authenticate. Although that would require a new infrastructure that
>>> would have to be set up this solution would be ok for me because
>>> everybody who is seriously interested in contributing to the OpenJDK
>>> would have a chance to become a "contributor".
>>> 
>>> 2. If you mean "Contributor" in the sense of "somebody who has commit
>>> rights into a Mercurial repository", that would be to rigorous in my
>>> opinion and would prevent many serious contributions.
>>> 
>>> 3.  Somebody who has requested an account trough a "trivial and fast
>>> procedure" as proposed before (and as it is today) would be probably
>>> to lax from you point of view.
>>> 
>>> What do you think?
>>> 
>>> Volker
>>> 
>> 
>> My guess is Mark used "Contributor" (with a capital "C") to refer to
>> the definition
>> in the proposed bylaws:
>> 
>> "A Contributor is a Participant who has signed the Oracle Contributor
>> Agreement (OCA), or who works for an organization that has signed that
>> agreement or its equivalent and makes contributions within the scope
>> of that work and subject to that agreement. Only a Contributor may
>> submit anything larger than a simple patch.
>> 
>> If a Contributor’s employment situation changes such that
>> contributions would no longer be covered by the OCA or its equivalent
>> then the Contributor must relinquish that role by notifying the
>> OpenJDK Lead."
>> 
>> http://openjdk.java.net/groups/gb/bylaws/draft-openjdk-bylaws-09
>> --
>> Andrew :-)
>> 
>> Support Free Java!
>> Contribute to GNU Classpath and IcedTea
>> http://www.gnu.org/software/classpath
>> http://icedtea.classpath.org
>> 
>> PGP Key: F5862A37 (https://keys.indymedia.org/)
>> Fingerprint = EA30 D855 D50F 90CD F54D  0698 0713 C3ED F586 2A37
>>