opendev
/
publications
Code Issues Proposed changes
OpenStack Infra Team conference presentations and papers
68 Commits 22 Branches 20 Tags 32 MiB
HTML 53%
Python 47%
Go to file
OpenDev Sysadmins e340651370 OpenDev Migration Patch 
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
 		2019-04-19 19:26:00 +00:00
graphics Use higher res logo for talk banner. 2013-07-31 08:34:30 -07:00
help Clear unrelated presentations out of the overview. 2013-06-18 01:06:46 +00:00
images Initial commit for publication template branch. 2013-09-13 14:58:11 -07:00
scripts Initial commit for publication template branch. 2013-09-13 14:58:11 -07:00
styles Remove stray .htaccess files. 2013-07-31 13:55:23 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:00 +00:00
README.rst Add info about adding new branch to gerritbot 2014-12-19 13:40:13 -08:00
index.html Initial commit for publication template branch. 2013-09-13 14:58:11 -07:00

README.rst

Template Branch for new OpenStack Infra Publications

Creating new OpenStack Infra Publications is easy and you have started in the right place.

  1. Clone publications, create and checkout template tracking branch:

    git clone git://git.openstack.org/openstack-infra/publications
cd publications
git review -s
git checkout -b template origin/template

  2. Create a new branch based on this template branch. git checkout -b $BRANCH_NAME.

  3. Edit .gitreview and change the defaultbranch value to $BRANCH_NAME.

  4. Create $BRANCH_NAME in Gerrit. It should be based on the template branch as well to avoid any potential merge conflicts in your first commit. Not everyone has the ability to do this in Gerrit. If you don't, ask an openstack infra core to do it for you.

  5. Now we get to do the fun stuff. Edit index.html editing lines with CHANGEME or changeme in them. You can also add new slides if you like but that isn't necessary in this bootstrapping change. You can follow up with new slides in subsequent changes.

  6. Edit this file, README.rst. The title of this document will be the name used on the root publications index so be sure to update the title. You should also add an Abstract section and general talk info.

  7. At this point you are ready to push your new changes back up to Gerrit. git commit -a && git review

  8. Finally, if you want notifications for subsequent branch updates to be shown in the #openstack-infra channel, add your branch to gerritbot/channels.yaml in the project-config repository.