Domesday: Difference between revisions

Domesday (view source)

Revision as of 09:41, 5 February 2011

697 bytes added , 5 February 2011

→‎Tagging

Gerv

Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti

4,925

edits

@@ Line 210: / Line 210: @@
 So personal tags are for pulling together set of people like "fosdem-invitees". One person may be making the list, but anyone else can see it by querying on domain.com/search?tag=fosdem-invitees&tag_owner=foo@bar.com
-In general, we expect people to maintain their own public tags, but we make it so anyone can edit them because in some cases, keeping data sets current will be much easier if the person caring about the data can fix things rather than contacting everyone concerned.
+Each tag has another tag associated with it, a "bless tag" - which defines who can add or remove that tag. Say tag "sumo" has bless tag "sumo-blessers". Anyone with sumo-blessers can add and remove the sumo tag from any other account. Tags may be their own bless tags, in which case it's an "anyone inside can invite new people in" system. Tags may also have a bless tag of "mozillian", which means that all validated people can add and remove that tag. If a tag has no bless tag, anyone can add or remove it.
-Some tags will have restrictions on who can add/remove them, to make sure particular data sets remain correct. Uses cases for this include "driver", "trusted", "reviewer" or "mozpaid".
-Tags may also be in name:value format, in which case restrictions are defined on the name. (This allows us to have tags like 'module-owner:Places', but have the appointment of module owners restricted to a certain set of people without having to enumerate all the possible modules.)
+Bless tags can be used to restrict changes and so make sure particular data sets remain correct. Uses cases for this include "driver", "trusted", "reviewer" or "mozpaid".
+In general, we expect people to maintain their own public tags, but we make it so anyone can edit them because in some cases, keeping data sets current will be much easier if the person caring about the data can fix things rather than contacting everyone concerned. Bad behaviour in removing or adding tags is dealt with by social rather than technical sanctions.
+Tags may also be in name:value format, in which case restrictions are defined on the name only. This allows us to have tags like 'module-owner:Places', but have the appointment of module owners restricted to a certain set of people without having to enumerate all the possible modules. Perhaps this might be implemented as: "name:value" tag inherits the bless tag from the "name" tag.
 === Schedule ===