Collective GitHub Organization For Shared Code Repositories

<!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="chrome=1"> <title>Collective GitHub Organization For Shared Code Repositories</title> <link rel="stylesheet" href="stylesheets/styles.css"> <link rel="stylesheet" href="stylesheets/pygment_trac.css"> <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no"> <link rel="apple-touch-icon" sizes="180x180" href="favicons/apple-touch-icon.png"> <link rel="icon" type="image/png" sizes="32x32" href="favicons/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="16x16" href="favicons/favicon-16x16.png"> <link rel="shortcut icon" type="image/x-icon" href="favicons/favicon.ico"/> <link rel="manifest" href="favicons/site.webmanifest"> <link rel="mask-icon" href="favicons/safari-pinned-tab.svg" color="#ffffff"> <meta name="msapplication-config" content="favicons/browserconfig.xml" /> <meta name="msapplication-TileColor" content="#ffffff"> <meta name="theme-color" content="#ffffff">  </head> <body> <div class="wrapper"> <header> <h1 class="main"> <a href="https://github.com/collective"> <img src="assets/images/plone-icon-collective.png" height="35px" alt="logotype" /> Collective </a> </h1> <p>Plone add-ons shared code repositories</p> <p class="view"><a href="https://github.com/collective">Collective Profile on GitHub.com</a></p> <p class="view"><a href="https://github.com/collective/Collective/issues/new">Request/ Ask Maintainers</a></p> <p class="view"><a href="https://collective.github.io/talks">Collection of Talks</a></p> </header> <section> <h2>Welcome to the Collective.</h2> <p> This is an organization for developers of <a href="http://plone.org">Plone</a> add-ons and related software. It is managed in the spirit of a <a href="https://en.wikipedia.org/wiki/Collective">Collective</a>: <br /> <strong>Every member can contribute to every project.</strong> <br /> Every repository may define own rules how to deal with it. Code ownership is reduced to this rules and the usual legal boundaries. </p> <h3>Join organization</h3> <p> To join the Plone Collective Organization, please <a href="https://github.com/collective/Collective/issues/new?assignees=&labels=Request&template=join-the-collective.md&title=Please+add+me+to+the+collective">open a ticket</a>. Note: you must have a GitHub account to open a ticket (and further actions). You can <a href="https://github.com/signup/free">create one for free here</a>. <h3>New repository</h3> <p> You can create new repositories in the collective as you wish. Keep in mind that you will lose administrator access to them a few minutes later. If you inadvertently create a repository in the Collective, please <a href="https://github.com/collective/Collective/issues/new">open a ticket</a>. <h3>Travis CI and other GitHub hooks</h3> <p> Please <a href="https://github.com/collective/Collective/issues/new">ask</a> one of github.com/collective admins to enable it for you. Administrators should see the page <a href="https://travis-ci.org/profile/collective">travis-ci.org/profile/collective</a>. </p> <h3>Other issues</h3> <p> For all other issues, please <a href="https://github.com/collective/Collective/issues/new">open a ticket</a>. <h3>Disabling notification spam</h3> <p> By default you are subscribed to all new collective github repository notifications. Unless you disable this yourself soon your inbox will contain only GitHub spam. </p> <ul class="simple"> <li>Go to <a class="reference external" href="https://github.com/watching">https://github.com/watching</a></li> <li> Select what to watch or Uncheck <em>Automatically watch</em>. But attention: latter will disable watch for <i>all</i> organizations.</li> </ul> <h3>Transferring repository ownership to Collective</h3> <p> How to move your repository under Collective shared ownership. About transfering the ownership of repositories <a href="https://help.github.com/articles/how-to-transfer-a-repository">see GitHub instructions regarding transfers</a>. You can do this yourself with GitHub's *Transfer Ownership* button 'if the repository belongs to your personal account. </p> <p> For repositories part of any GitHub organization (and organization only) you need the organization admin permissions to perform the transfer. Admin in the third party organization must be also collective member. </p> <h3>Migrating old Subversion repositories to GitHub</h3> <p> Please see notes <a href="https://github.com/collective/Collective/blob/master/old-svn.rst">here</a> </p> </section> <footer> <a href="https://plone.org/"><img src="assets/images/plone-logo-64-white-bg.png" alt="Plone CMS: Open Source Content Management" title="Plone CMS: Open Source Content Management"></a> <p><small>Collective is powered by the awesome Plone community.</small><p> <p><small>Hosted on GitHub Pages — Theme by <a href="https://github.com/orderedlist">orderedlist</a>.</p> </footer> </div> <script src="javascripts/scale.fix.js"></script> </body> </html>

CINXE.COM

Collective GitHub Organization For Shared Code Repositories