Quick Search
Browse
Pages
Blog
Labels
Attachments
Mail
Advanced
What’s New
Space Directory
Feed Builder
Keyboard Shortcuts
Confluence Gadgets
Log In
Sign Up
Dashboard
Clojure Documentation
Copy Page
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account. You can also
Sign Up
for a new account.
This page is being edited by
.
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
Colour
More colours
Strikethrough
Subscript
Superscript
Monospace
Clear Formatting
Bullet list
Numbered list
Outdent
Indent
Align left
Align center
Align right
Link
Table
Insert
Insert Content
Image
Link
Attachment
Symbol
Emoticon
Wiki Markup
Horizontal rule
tinymce.confluence.insert_menu.macro_desc
Info
JIRA Issue
Status
Gallery
Tasklist
Table of Contents
Other Macros
Undo
Redo
Keyboard Shortcuts Help
<p>Things you should do if you are a Clojure Contrib committer:</p><ul><li>maintain your library and respond to questions/issues that arise.</li><li>do your work on the master branch, or (if you are working on a significant chunk you want to keep temporarily separate) on a feature-specific branch that you create yourself.</li><li>use the Maven Release option on build.clojure.org to make releases.</li><li>coordinate with other committers before making changes to their libraries.</li><li>accept contributions from others only if they have signed the CA (see <a href="http://clojure.org/contributing">http://clojure.org/contributing</a> for the list) and if they submit a patch. </li></ul><p>Things to avoid:</p><ul><li>please do not push to the release branches (names like 1.2.x). The Clojure/core team uses these to make the official, tested release.</li><li>do not take non-contributor patches.</li><li>please do not take pull requests from contributors. Patches only. Yes, it is inconvenient. Sorry.</li><li>do not change the version number in pom.xml - use the Maven Release process mentioned above.</li><li>do not make a 1.0.0 release without full review and approval from Clojure/core!</li></ul><p>Here's the process outline for what it takes to become a committer:</p><ul><li>Get your CA on file</li><li>Join the <a href="http://groups.google.com/group/clojure-dev">clojure-dev mailing list</a></li><li>Create a JIRA account</li><li>Create a Confluence account as well if necessary (with the same login details; in theory they are linked and creating one <em>should</em> create the other but it practice it doesn't seem to work all the time)</li><li>Let Clojure/core know your github username and JIRA username so they can set up the correct permissions</li><li>Clojure/core need to create your account on build.clojure.org as well - see below</li></ul><p>Setting up a new contrib project:</p><ul><li>Create a new GitHub repo (requires Clojure organization admin privileges):<ul><li>Specify project name (must be approved by Clojure/core)</li><li>Specify description</li><li>Team: <strong>Contrib Commit</strong></li><li>Add Post-Receive URL Service Hook: <strong><a href="http://infolace.dnsalias.net:8080/github-post">http://infolace.dnsalias.net:8080/github-post</a></strong> (for autodoc)</li><li>Disable Issues tab</li></ul></li><li>Create a new JIRA project (requires JIRA admin privileges):<ul><li>Specify name (same as GitHub project name)</li><li>Specify key (approved by Clojure/core, derived from project name)</li><li>Specify project lead's JIRA account</li></ul></li><li>Setting up builds (requires Hudson admin privileges, except step 2):<ul><li>Create Hudson user account for authors</li><li>Edit <strong>ci_data.clj</strong> in the <strong>build.ci</strong> repo add the new project / update authors (so they can run builds / cut releases)</li><li>Run <strong>build.ci</strong> Hudson job</li><li>Force Hudson to reload its configuration files</li></ul></li></ul><p> </p>
Attachments
Labels
Location
< Edit
Preview >
Loading…
Save
Cancel
Next hint
search
attachments
weblink
advanced