Process for Plone core's development

Introduction

This documentation describes the process for developing Plone. It is primarily a technical resource for setting up your core developer buildout, fixing bugs, and writing plips.

Warning

STOP!

Legally, you can NOT contribute code unless you have signed the contributor agreement. This means that we can NOT accept pull requests from you unless this is done, so please don't put the code reviewers at risk and do it anyways. Submitting the agreement is easy (and will soon be easier) and if you want quick access and are familiar with the community, go into irc and ask one of the repo admins to give you access with a scanned copy of the agreement. They will get you going as fast as possible!

Table of Awesome

• Contributing to Plone Core
  • Dealing with pull requests on GitHub
• Plone Developer Culture
• How To Commit Fixes to Plone Core
  • Version Support Policy
  • Dependencies
  • Setting up Your Development Environment
  • Checking out Packages for Fixing
  • Testing Locally
  • Updating CHANGES.rst and checkouts.cfg
  • Committing and Pull Requests
  • Committing to Products.CMFPlone
  • Jenkins
  • Finalizing Tickets
  • FAQ
• Writing documentation
  • Documentation of Plone
  • Documenting a package
• Style Guide
  • Naming Conventions
  • File Conventions
  • Concrete Rules
• Implementing PLIPS
  • All about PLIPS
  • Process Overview
  • How to Submit a PLIP
  • Implementing Your PLIP
• Troubleshooting
  • Buildout Issues
  • Other Random Issues
• How to Update these Docs

Others

These are some documents using as reference for this documentation.

• Contributor’s Agreement for Plone Explained
• Mr. Developer
• Reviewing PLIPs