Introduction

You are a developer at Spacely Sprockets. You have developed a Plone product called plockets. Your company is using it internally for its sprocket inventory. You are still sane, so apparently you have used a code repository. We assume that it is subversion. You have told some others about your product. You even gave them read access to your repository. Some are now making patches and are asking for write access. You decide that you do not want to deal with that, so you want to move your code to the Plone Collective. Resistance is after all still futile. (This tutorial assumes that you have write access to the Collective, if not, read the instructions for how to get access to the Collective) The Plone Collective is a unique, open code repository that contains hundreds of add-on Products for Plone from over 250 developers. Some of the coolest, most exciting stuff in the world of Plone is happening the Collective, and it's the lab for most of what eventually makes it into the Plone Core. Access to the Plone Collective is (almost) wide-open.