Currently, [Bradley M. Kuhn](http://ebb.org/bkuhn/) is the editor-in-chief of

this Guide project.  However, many other contributors have given patches and

improvements to the text.  Review the

for more details on who has contributed to the project.

## How Do I Get Involved?

The Guide is maintained in a copylefted distributed version control system called

See the section "Merge Request and Patch Workflow" below for more information

on the details of doing that.

   brought from the other source — more-or-less as it stood in the

   other work.  This is useful for historical archiving purposes.

   contains an example of this specific procedure.

2. In a second commit, by itself, add the following two things only:

   Commit changes as necessary, in the smallest increments reasonably

   possible.

   is an example of the process for the last two steps.

5. Submit a merge request for your branch into 'next'.  In this particular

## Merge Request and Patch Workflow

Currently, the main location for work on this project is

development on the project happens on the

(which is

[auto-published on the copyleft.org/guide-next URL](https://copyleft.org/guide-next/)).

Here is a suggested workflow for submitting patches — first doing so

infrastructure but still using Git, and third avoiding Git altogether.

Merge requests and/or patches against

typically much preferred, and the workflow explanations below assume that.

However, merge requests and/or patches against

are not necessarily rejected.  In fact, if your change is a fix for typo,

spelling, grammar, formatting or anything urgent, submitting a patch against

'master' may make more sense.

replace 'next' everywhere below with 'master'.

First-time contributors may want to do the following four items first:

    Instead of the default, you might call your clone

2. On the command line create a *local* clone of your Clone, by typing:

    (The last part isn't strictly necessary; you just might want to name the

    upstream repository a more descriptive name, since below you'll add the

3. Now, add to your clone a copy of the "real" copyleft.org tutorial

   repository, and make a branch that tracks the official version:

That completes the first-time setup.  Next is a workflow each proposed merge

request.

        $ git checkout master

        $ git branch -D official-next

        $ git checkout official-next

        $ git pull

4. Next, upload and publish those ideas to your own clone on Gitorious.

    That's the end of the command-line part.

   Initiate your merge request with by setting:

6. While it's possible to discuss the details of the merge request via the

   web interface, for larger changes, it may be worthwhile to start a thread