Jacek Laskowski wrote:
At last, I've got it! OpenEJB uses Interactive Permissions scheme:
This permissions model differs from the Standard Permissions model in
that people in the Contributor role must interact with the dev list to
get to get issues assigned to them and issues closed. This isn't a
trust issue, more that there are a few benefits. 1. Active
contributors hitting the list to begin and end work shows other people
not yet active how to get involved. 2. Adds more "touch points"
between Contributors and Committers. It should be possible to "see"
the active contributors even if you are not watching the JIRA or SVN
notifications. It's also hoped that the practice of announcing your
intentions on the dev list will persist even when the Contributor
becomes a Committer. 3. Gives Committers the opportunity to help,
mentor or otherwise get the Contributor going in the right direction
before a task is started; potentially resulting in fewer rejected
patches, less waisted Contributor time, and more collaborative
development. 4. Overall brings more communication to the dev list
before all work is done and all decisions made giving more potential
to collaboration.
and Assign Issues and Assignable User are those who are assigned
Committers or Contributors. Contributors are those who can be
Assignable User only. You've got Contributors role so you are not
allowed to assign issues to yourself. I'll have to do it myself (or
other committer) until you've got your svn account set up. Ping
dblevins.
That all sounds good to me, its nice to know the thinking behind the
permissions.
Let us know what issue you'd like to be working on and they'll be yours.
I've done OPENEJB-343 (a added a patch to the issue), and I thought I'd
do OPENEJB-345 next.
Many thanks
Jon
