rfc6087bis

Update to the YANG Guidelines RFC

=======

Internet Draft Template Repository

The contents of this repository can be used to get started with a new internet draft.

Getting Started

This all assumes that you have an account with Github.

Working Group Setup

Make a new organization for your working group. This guide will use the name unicorn-wg for your working group.

New Draft Setup

Make a new repository. This guide will use the name name unicorn-protocol here.

Clone that repository:

$ git clone https://github.com/unicorn-wg/unicorn-protocol.git

Copy the contents of this respository in:

$ cd unicorn-protocol
$ git pull https://github.com/martinthomson/i-d-template.git master

Choose whether you want to use markdown or xml as your input form. If you already have a draft, then that decision is already made for you.

Move the template file into place.

$ git mv template.md draft-ietf-unicorn-protocol.md

Or add an existing file.

$ git add draft-ietf-unicorn-protocol.xml

Edit the draft so that it has the right name. This template uses the -latest suffix in place of the usual number ('-00', or '-08').

   <rfc docName="draft-ietf-unicorn-protocol-latest" category="std">

Or in markdown:

docname: draft-ietf-unicorn-protocol-latest

And add it:

$ git add draft-ietf-unicorn-protocol.md

Remove the unnecessary template files.

$ git rm template.md template.xml

Move the README.md template into place.

$ git rm README.md
$ git mv README-template.md README.md

Edit the README.md and CONTRIBUTING.md files. Note that CONTRIBUTING.md file is just the latter part of README.md.

$ vi README.md CONTRIBUTING.md
# ...
$ git add README.md CONTRIBUTING.md

Commit and push

$ git commit
$ git push

Optional: If you are using markdown, you might like to add the following line to your .gitignore to avoid committing the intermediate XML file that this might create.

draft-*.xml

Setting Up The Editor's Copy

Github uses the gh-pages branch as source for a project web page. This branch needs to be initialized first.

$ git checkout --orphan gh-pages
$ git rm -rf .
$ touch index.html
$ git add index.html
$ git commit
$ git push --set-upstream origin gh-pages
$ git checkout master

You can maintain gh-pages manually by running the following command occasionally.

$ make ghpages

Automatic Update for Editor's Copy

This requires that you sign in with Travis.

While you are there, enable builds for the new repository. (Hit the button with a '+' on it once you are logged in.) Note that Travis can take quite a while to synchronize its view of all the respositories, you might have to wait a day or so for your new repository to show up.

You need the Travis command line tools, which is a Ruby script:

$ sudo gem install travis

WARNING: You might want to use a dummy account for this next part to minimize any problems from accidental leaks. Once you enable pushes from Travis, be very careful accepting pull requests that alter .travis.yml or Makefile. Those files can cause the value of the token to be published for all to see. You don't want that to happen, even though tokens can be revoked easily. Only pushes to the main repository will be able to see the token, so don't worry about pull requests.

Then, you need to get yourself a new Github application token. The application token only needs the public_repo privilege. This will let it push updates to your gh-pages branch.

Then, you update the Travis configuration file with an encrypted copy of that token, as follows:

$ travis encrypt GH_TOKEN=<YOUR TOKEN HERE> -a -p
$ git add .travis.yml
$ git commit
$ git push

As a side benefit, Travis will now also check pull requests for compilation errors, letting you know if things didn't work out.

Submitting Drafts

Occasionally, you will want to submit versions of your draft to the official IETF repository. The following process makes this easy.

Make a submission version of your draft. The makefile uses git tags to work out what version to create.

$ make submit

Submit the .txt and .xml files that this produces.

Then you can tag your repository and upload the tags. The tag you should use is your draft name with the usual number in place of -latest.

$ git tag draft-ietf-unicorn-protocol-03
$ git push --tags

You can setup Travis to produce a release in Github based on tags. See .travis.yml for a template.