From Fedora Project Wiki

(Add note that no re-approval is needed for updates to an existing spin)
(board -> council)
 
Line 1: Line 1:
The [[Board]] will appoint [[SIGs]] that they think are appropriate for various [[Legal:Trademark_guidelines|trademark approvals]].
The [[Council]] will appoint [[SIGs]] that they think are appropriate for various [[Legal:Trademark_guidelines|trademark approvals]].


# Each appointed SIG should create a checklist or SOP for Item approval
# Each appointed SIG should create a checklist or SOP for Item approval
# When an appointed SIG gives its approval for a Item, it should do so in a public and transparent manner. The SIG can decide the exact manner of approval but who and where the approval is granted should be specified in the SOP.
# When an appointed SIG gives its approval for a Item, it should do so in a public and transparent manner. The SIG can decide the exact manner of approval but who and where the approval is granted should be specified in the SOP.
# Once approvals from appointed SIGS are done, the Item will be submitted to the Board (via a ticket) for trademark approval.
# Once approvals from appointed SIGS are done, the Item will be submitted to the Council (via a ticket) for trademark approval.
# The Board can appoint a specific SIG to keep track of "trademarked" Items and that SIG will set schedules and/or reasons for re-approval
# The Council can appoint a specific SIG to keep track of "trademarked" Items and that SIG will set schedules and/or reasons for re-approval
# No reapproval of a spin for trademark is needed when an existing spin is updated (for instance, for a new Fedora release).  Spins SIG can still approve or veto an updated spin but that's outside of trademark approval.
# No reapproval of a spin for trademark is needed when an existing spin is updated (for instance, for a new Fedora release).  Spins SIG can still approve or veto an updated spin but that's outside of trademark approval.
# The Board will be the final arbitrator in disputes between various SIGs or perceived problems of process.
# The Council will be the final arbitrator in disputes between various SIGs or perceived problems of process.


This will be voted on next board meeting after one week of input.
This will be voted on next council meeting after one week of input.


This policy was [https://lists.fedoraproject.org/pipermail/advisory-board/2011-April/010634.html proposed by Stephen John Smoogen] and [http://meetbot.fedoraproject.org/fedora-board-meeting/2011-04-26/fedora_board.2011-04-26-16.00.log.html#l-32 approved in the Board's meeting on 2011-04-26].
This policy was [https://lists.fedoraproject.org/pipermail/advisory-board/2011-April/010634.html proposed by Stephen John Smoogen] and [http://meetbot.fedoraproject.org/fedora-board-meeting/2011-04-26/fedora_board.2011-04-26-16.00.log.html#l-32 approved in the Board's meeting on 2011-04-26].

Latest revision as of 20:52, 12 March 2015

The Council will appoint SIGs that they think are appropriate for various trademark approvals.

  1. Each appointed SIG should create a checklist or SOP for Item approval
  2. When an appointed SIG gives its approval for a Item, it should do so in a public and transparent manner. The SIG can decide the exact manner of approval but who and where the approval is granted should be specified in the SOP.
  3. Once approvals from appointed SIGS are done, the Item will be submitted to the Council (via a ticket) for trademark approval.
  4. The Council can appoint a specific SIG to keep track of "trademarked" Items and that SIG will set schedules and/or reasons for re-approval
  5. No reapproval of a spin for trademark is needed when an existing spin is updated (for instance, for a new Fedora release). Spins SIG can still approve or veto an updated spin but that's outside of trademark approval.
  6. The Council will be the final arbitrator in disputes between various SIGs or perceived problems of process.

This will be voted on next council meeting after one week of input.

This policy was proposed by Stephen John Smoogen and approved in the Board's meeting on 2011-04-26.