Geronimo Project Policies
Skip to end of metadata
Go to start of metadata

Apache Geronimo Project Policies

Although not easy, here we try to convey some policies of how the Apache Geronimo project tackles different processes and every day decision making situations. This is clearly not an extensive list but we are working to make it more complete every day.

Contributing to Geronimo Docs

Before you can be given write access to the documentation wiki spaces (like GMOxDOC21, GMOxDOC22, GMOxSAMPLES), but not areas restricted to committers (like GMOxPMGT and GMOxSITE), you will need to submit an ICLA to the ASF and show up on the following page of received CLAs.

Security Vulnerabilities

The process for submitting known problems is on the Geronimo website under Security Reports.

The suggested process for handling submitted vulnerabilities:

  1. Team ACKs security report.
  2. Team investigates report and either rejects it or accepts it.
  3. If rejected, write to submitter and explain why.
  4. If accepted, write to submitter and let them know it is accepted and we are working on a fix.
  5. Request a CVE number from security@a.o
  6. Agree on a fix on our private@ list.
  7. Provide the submitter with a copy of the fix and a draft vulnerability announcement for comment.
  8. Reach an agreement for the fix, announcement and release schedule with the submitter.
  9. Create a JIRA and commit the fix in all actively maintained releases.
  10. Announce the vulnerability (users, dev, security@a.o, bugtraq at securityfocus.com, full-disclosure at lists.grok.org.uk and project security pages)
  11. Update the JIRA and svn log to include the CVE number.
  12. Roll a release for each actively maintained branch (unreleased trunk can wait.)

Access to Geronimo TCK Test Harness

Apache committers can request access to the TCK following this process:

  1. Requester should send a note to jcp-open@apache.org requesting access to the JCP TCKs
  2. Requester should also send a note to the PMC list requesting access to the Geronimo Test Harness with a quick summary of their goals.
  3. PMC member acknowledges receipt of the request back to the user.
  4. PMC member confirms that requester has submitted an NDA:
    • ASF members can confirm by inspecting the contents of https://svn.apache.org/repos/private/foundation/Correspondence/JCP/tck-nda-list.txt or
    • Non-member can send a note to the appropriate keeper of NDAs on jcp-open and the Geronimo PMC with a subject of:

      **[TCK] Request for TCK access for Apache Geronimo TCK materials. Please verify NDA is on file.

      and includes relevant information about the committer and their request.

    • Waiting period:
      • Geronimo committers will be granted r/w access to svn, TCK wiki and accounts on selene, phoebe and tck01-tck08 upon confirmation of the NDA being on file.
      • Other Apache committers will be granted read-only access to svn and TCK wiki (but no access to selene, phoebe, tck01-08) upon confirmation of the NDA being on file.

The chair or authorized member will update the SVN authorization file, provide access to other resources as appropriate and notify the user of the URL and current relevant information. Geronimo committers are given r/w access and others are given read-only and they can start earning karma.

Labels
  • No labels