Update on bug system for OpenJDK (web-discuss)

mark.reinhold at oracle.com mark.reinhold at oracle.com
Wed Jun 1 21:46:51 UTC 2011

2011/5/30 16:22 -0700, david.holmes at oracle.com:
> ...
> I think there is some confusion between Group roles and Project Roles here
> (perhaps they have changed between the interim rules and the new proposed
> bylaws). Groups don't have repositories and Group members don't have commit
> rights. The basic proposed hierarchy in the draft-bylaws in terms of code
> submission and review is:
> - OpenJDK Participant
> - OpenJDK Contributor
> - Project Author (must be a Contributor)
> - Project Committer
> - Project Reviewer
> then in addition we have plain old users.


> So my initial categorization would be:
> - Anyone should be able to submit an "incident report".
> - Contributors should be able to submit "bug reports".

Add, per Andrew Haley's suggestion:

  - Contributors should be able to update existing "incident reports"
    so that they can help triage incoming incidents, converting them
    to bugs or closing them as appropriate

> - Contributors should be able to have read access to the code review system
> (they can always report an issue via email).

(I'd actually give everyone read access, insofar as the system can handle
 the load.)

> - Project Authors and above should have write access to the code review system.
> Whether "incident reports" and "bug reports" go into two different systems
> depends on how well the systems can handle the distinction both in terms of
> easy access/use for incidents, and isolation of incidents from bugs.

With the above modification, I think this is a sensible approach.

To what extent can the candidate systems support the separate handling
of untriaged incidents vs. accepted bugs?

We should also allow non-Contributors to add information to existing
incidents and bugs, and to vote on them, but (probably) not make any
other kinds of updates.

- Mark

More information about the discuss mailing list