You may also want to have a look at how the Apache Software Foundantion works. This is an Apache project, and its structure and procedures are the same than the rest of TLPs in the ASF: http://apache.org/foundation/
On 9 February 2015 at 17:02, Andrew Phillips <aphill...@qrmedia.com> wrote: > Hi Timur > > Just briefly on the tools part: > >> Code repository: GIT Hub + Apache >> Communication tools: E-mail + GIT Hub (are there any others?) >> Documentation: Project Web-site (do you use any other specific >> software for documentation?) > > > * The only and official "home" of the jclouds code is in the ASF Git server. > We mirror these repositories to GitHub to allow people to contribute code > via GitHub's PR process, but it's not a "core repo." > * We also use #jclouds on Freenode IRC for communication (see [1]) and > publish blog posts (see [2]). As is common at the ASF (as far as I > understand), communication via email to the mailing lists is the only > "official" form. > * Alongside the project website, we also have a development Wiki [3] and a > repository of examples [4]. > * We are currently using a hosted CI setup at CloudBees DEV@cloud for > automated PR validation and other CI-related tasks [5]. > > For more information on some of the roles in jclouds, you may want to check > the Bylaws: > > https://cwiki.apache.org/confluence/display/JCLOUDS/Bylaws > > Regards > > ap > > [1] http://jclouds.apache.org/community/ > [2] http://jclouds.apache.org/blog/ > [3] https://cwiki.apache.org/confluence/display/JCLOUDS/Apache+jclouds+Home > [4] https://github.com/jclouds/jclouds-examples > [5] https://jclouds.ci.cloudbees.com/
