openstack/nova-specs - nova-specs - OpenDev: Free Software Needs Free Tools

Added a section to capture perfomance considertaions that
should be considered at design time
Change-Id: I079bcd396ac263ed14276e6fb5f4b5eec92781ad

Add prompts to help a deployer understand if the change will
take immediate effect, or is something that has to be explicitly
configured into the system. Generally a change that has
immediate effect would be of more concerns for both updates
and folks on the CI path than a change that is in effect dormant
until configured.
This also of course prompts for the BP submitter to also
consider the same issue, which is a topic that should be addressed
at design time.
Change-Id: I7e78ffcaec800bbfe09135d90069158dc6e58923

Changes which require modifications to the data model
often have a wider impact on the system. The community
often has strong opinions on how the data model should
be evolved, from both a functional and performance
perspective, and disagreements and/or rework late in the
implemetaion stage are vrey disruptive and tiem consuming.
It is therefore important to capture and gain agreement
as early as possible on any proposed changes to the data
model.
Change-Id: I071043c7ce29bb8a47a9da9fb458befe91f6a609

Change-Id: If936d23c481402d53467a057b5de141ee64f864b

Change-Id: I1f7da3f854c8317e8a344f43237176e1295e4048

For more detail, see the following discussion:
http://lists.openstack.org/pipermail/openstack-dev/2014-March/030886.html
Change-Id: I5c138f1fc3eafea00c810da183b4d74c06e8d210

Update the nova-specs project to use sphinx. This will allow us to
still write our specs using rst, but also have a nice framework for
rendering and publishing the specs if we choose to.
Change-Id: Ib92231acb28bba44abafb7dd554404f542da13a7

I asked on the legal-discuss mailing list which license should be used
and the direction given was to use CC-BY for new documentation.
http://lists.openstack.org/pipermail/legal-discuss/2014-March/000201.html
Change-Id: I24a5f0e6de048ef643f42dc7efe5e4cdc35772ba

Added an extra section about notifications, asking the template author
to specify any changes to notifications.
Change-Id: I1a752df3b9cab6a0c08c9f82d1d34de43eeb79b8

The current reST parser link will throw a bunch of python errors that may
be hard to read.
The new link adds http://rst.ninjs.org/ to allow the developers watch
in-place current formatting errors.
It's a full reST online editor.
Change-Id: I6ab5fbcbda7939736591d327dd2d03da66120ead

This change adds a line to the deployer section of the blueprint template
to remind submitters to note expected database migrations.
Change-Id: I277df6ec96573cae21cf756a049a353db83bbf3f

The important part is the Apache2 header not who holds the copyright.
These copyright holder lines are often inaccurate and misleading, so
don't require one by default.
Note: Some companies require there employees to use these, so if someone
adds this line in there spec, we should allow it. We just don't want to
require one by default.
Change-Id: Ifd82752d4e220360ab1d8a6bcd3fc27cb10b7d65

Adds more detail for the requirements where REST API
additions or changes are being planned.
Change-Id: Id98d80520acc4d085ae64acee70a420c769fd549

Add a link to a helpful reference on rst formatting and a site that
will render rst to html to see if you've made any mistakes.
Change-Id: I24b6dca69324a50e7c0eda2dc50a25cad4a8e20b

Template should be easier to use with a little more structure
between the sections. Added a comment that people can add None instead
of deleting a section. This should help keep the use of the template
more consistent.
The sub-headings in implementation are renamed to match the existing
fields in launchpad. Should make parsing these easier at some point in
the future.
Tweaked the order so its closer to the current launchpad ordering.
Partly to ease the transition, party because I like the order they have
chosen.
Made a distinction between end-users, deployers and developers. This
has created much confusion in the past.
To reduce the text we force people to delete, trying out adding some
instructions as a comment block.
Change-Id: I28fae5c03da6939471109de7177ac7d2440e7680

Add a template for specs. This covers the general formatting we
expect, as well as the level of detail we are looking for.
Change-Id: I03fcb6ad178bb0099612b0e19b3f4c1a209a94bd

Like everything else in OpenStack this is under the Apache 2 License.
Change-Id: I4ca18a62c92da61660f064f7dbdb99ad029490f6

This commit introduces the proposed layout for this repository. The
next step after this will be to start defining the expected layout of
a spec and provide some templates.
Change-Id: I4b38d75802f3c7feef98639dfddd1898e564145f