Navigation

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.

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
  • 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

Project Versions

Table Of Contents

  • Introduction
  • STOP!
    • Table of Awesome

Next topic

Contributing to Plone Core

This Page

  • Show Source

Navigation

© Copyright 2012, The Plone Foundation. Created using Sphinx 1.1.3.
TEST Brought to you by Read the Docs
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.