Thierry Carrez
dcad1bc921
This postulates that tags should be tags, and therefore shouldn't have attributes. Attributes in tags were originally meant to hold additional information on the area described by the tag. However, ideally tags are self-contained units of information, with an opinionated description (and ideally an objective set of application rules). Keeping the option of having attributes in tags adds useless format complexity and steers tags in the direction of structured project metadata. Project structured metadata (like the ops-data) is fine, it's just not the same thing as tags. Continuing to support attributes in tags IMHO encourages the confusion between the two. The integrated-release tag was the only one using attributes, and it's now removed. Change-Id: I1dd5c8090405bd87e8947892d78c62509258e363
This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.
Directory structure:
- reference/
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
- resolutions/
When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.