#85 Policy updates for two previously approved items
Merged 4 months ago by sgallagh. Opened 5 months ago by zbyszek.
fesco/ zbyszek/fesco-docs rust-devel-and-voting  into  main

@@ -315,8 +315,9 @@ 

  the classes below, but you think it should be allowed to update more rapidly, propose a new

  exception class to FESCo and/or request an exception for your specific update case.

  

- Note that you should open this dialog BEFORE you build or push updates. In the event that an issue

- is raised in the middle of an update already in progress, make sure you turn off autokarma pushes —

+ Note that you should open this dialog **before** you build or push updates.

+ In the event that an issue is raised in the middle of an update already in progress,

+ make sure you turn off autokarma pushes —

  this can be done while the update is pending in Bodhi.

  

  The following things would be considered in a exception request.
@@ -344,6 +345,12 @@ 

  

  The following packages have been granted exceptions for the following reasons:

  

+ [[rust]]

+ ===== Rust -devel packages

+ This exception covers all Rust -devel packages, i.e. rpms with Rust sources.

+ Those packages are used to build packaged Rust binaries

+ and are not directly usable by users.

+ 

  [[kernel-package]]

  ===== kernel package

  

@@ -25,7 +25,7 @@ 

  * Responsible for what software is offered to end users under what conditions.

  * Oversight and approval of new spins and other media that doesn't fit under a working group.

  

- FESCo has empowered the FPC (Fedora Packaging Comittee) to handle management of packaging guidelines,

+ FESCo has empowered the FPC (Fedora Packaging Committee) to handle management of packaging guidelines,

  so those items are usually deferred to them with occasional FESCo oversight.

  

  Candidates for FESCo should be people who have a wide breadth of knowledge about the Fedora Project as a whole
@@ -100,6 +100,10 @@ 

  the proposal is considered rejected and the status quo will be maintained.

  The submitter may at this time make a new proposal which will be processed following the usual rules.

  

+ Tickets which are labeled as "Fast Track" must be retitled to include "[FastTrack]"

+ and if they have not received enough votes in 48 hours,

+ a FESCo member should send a reminder.

+ 

  [[meeting-votes]]

  == Meeting Votes

  

no initial comment

Thanks, the Rust part looks good to me.

Speling misteak: Should be "reminder"

3 new commits added

  • Fix typo
  • Add requirement to retitle FastTrack requests with [FastTrack]
  • updates policy: add blanket exception for rust -devel packages
4 months ago

Rememinder might be really strong reminder. Why not?

Anyway, updated, with another trivial commit to fix a typo.

Pull-Request has been merged by sgallagh

4 months ago