Fork me on GitHub

Participating

The best place for Oak-related discussions is the oak-dev@ mailing list. To subscribe, send a message to [oak-dev-subscribe@] (mailto:oak-dev-subscribe@jackrabbit.apache.org).

Use the OAK issue tracker to submit issues, comments or patches. To subscribe to issue notifications, send a message to [oak-issues@] (mailto:oak-issues-subscribe@jackrabbit.apache.org).

The latest Oak sources are available for checkout from svn and can also be browsed using the ViewVC interface. You can also fork them on GitHub. To subscribe to commit notifications, send a message to [oak-commits@] (mailto:oak-commits-subscribe@jackrabbit.apache.org).

For more details related to various mailing list have a look at http://jackrabbit.apache.org/mailing-lists.html

We generally follow a CTR policy. However it is up to each individual committer to pro-actively ask for a review of a patch on oak-dev@ or to even call for a RTC. Special care should be taken with backports to maintenance branches. Back ports bear a certain risk of introducing regressions to otherwise stable branches. Each back ported change should be carefully evaluated for its potential impact, risk and possible mitigation. It is the responsibility of each committer to asses these and ask for advise or reviewing on oak-dev@ if uncertain. Whether using RTC or CTR is up to the committer.