Ticket #8875 (closed Bug: fixed)
Document how one gets Trac access
| Reported by: | gabriellehp | Owned by: | gabriellehp |
|---|---|---|---|
| Priority: | critical | Milestone: | Ongoing |
| Component: | Documentation | Keywords: | maintenance TuneUp13 |
| Cc: |
Description
We run into this problem at every Plone Tune-Up event: people don't have permission to "accept" a ticket. Please document and let gabrielle AT sixfeetup DOT com know about it so I can post a link onto the Plone Tune-Up ning site.
Change History
comment:2 Changed 3 years ago by jluvsu2
- Keywords maintenance added
- Status changed from new to assigned
- Owner changed from doc-editors@… to jluvsu2
comment:3 Changed 3 years ago by gabriellehp
Note that this procedure will grant you access to the collective and archetypes.
However, you will need to sign the contributor agreement to get commit rights to Plone. Without that, if you need to submit an occasional patch to Plone core, you may either put it as a patch into the tracker and find someone to commit it for you at the Plone Tune-Up days or wait until someone commits it.
comment:5 Changed 3 years ago by jluvsu2
- Status changed from assigned to new
- Owner changed from jluvsu2 to gabriellehp
https://dev.plone.org/plone/wiki/ContributeCollective
See if this document meets our needs. It's buried in the wiki but we can link to it in the #plone-tuneup channel and from the ning site.

Apparently, for trac access you need commit rights to the collective. To get that, you need to put a ticket in here https://dev.plone.org/plone.org/newticket, change the component on the ticket to make it commitaccess, and you should be all good then.
Can someone on the doc Team make sure this is information easy to find on the plone.org site?