Commit Graph

9 Commits

Author SHA1 Message Date
Radosław Piliszek b7f45e2266 Remove the tags framework (part 1)
This change enacts the first steps of the TC's decision to remove
the tags framework. [1]

This change does not remove all the parts to avoid breaking
the releases tooling as well as to preserve useful information
as discussed under this change and during one of the TC meetings.
[2]

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.html
[2] https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-20-15.00.log.html

Change-Id: Iab4a136905a9c7a61530ff7576a216d229f717a0
2022-02-03 18:32:27 +00:00
Sean McGinnis 8a1078bc28
Remove source license from generated doc output
The tag documentation included the license in the generated output as a
code block. This switches the code block to a comment so that is not
emitted in the generated HTML.

Change-Id: I9ae61d50310936554ff85c818d44473e0cd85945
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-05-15 10:32:54 -05:00
Thierry Carrez 75fed0dd31 Tags are applied to deliverables, or teams
Clarify confusing language in tag descriptions around "projects".
Tags are either applied to project deliverables, or to the project
team.

Also move status:maintenance-mode to the "Team tags" section in
the index since that is how it is currently applied.

Change-Id: I0b63b3d65be64c572f2247dc9070245e78790db4
2017-11-29 15:34:39 +01:00
Thierry Carrez dcad1bc921 No longer support attributes in tags
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
2015-07-15 12:20:47 +02:00
Doug Hellmann 4ec9e54ed6 update tag template with link anchor
All tag pages need to have a link anchor with a specific name, so update
the template to describe how to make that work.

Change-Id: I39622fc1c6adae6dcac19c0966e78f268365bcc8
2015-06-15 16:13:21 +00:00
Joe Gordon 57e0cefc36 Move application to current projects up in tag page
Feedback from operators in a user committee session pointed out which
projects a tag is applied to is one of the most useful things on each
tag's page.  So move the 'application to current projects' section up in
the page so it is easier to find.

Change-Id: Ib7b0aa250f950398e0abd20d35a1ea252b057d4c
2015-05-20 11:34:29 -07:00
Doug Hellmann 72b8b9a74d Build list of teams from YAML file
Render the YAML file contents as the list of official teams and create a
directive to render the list of projects with a given tag to avoid
having to update that data in two places.

Change-Id: I7c6effe6e440f2147f8c68df090152e716c38fba
2015-02-24 18:15:04 -05:00
Thierry Carrez fcded3feee Introduce tag attributes
Tags may have attributes to further describe what they mean or to store
pointers to extra information. This change modifies the tag template and
the "integrated-release" tag definition (to introduce the "since"
attribute).

Change-Id: I0d6b30f9d47d5ff70330d422ae67bb288118f25c
2015-01-28 09:57:41 -06:00
Thierry Carrez 52e235491c Add template for project taxonomy tags definition
A template for proposing new tags in the project taxonomy. See next
change in the patchseries for a practical example.

Change-Id: If843e0166583aa9709c19ef4825f3a851a20ede4
2015-01-16 11:06:24 +01:00