From: "naruse (Yui NARUSE)" <naruse@...>
Date: 2013-12-05T20:36:18+09:00
Subject: [ruby-core:58874] [ruby-trunk - misc #9218] Branch Maintainer	Appointment / Discharge Process


Issue #9218 has been updated by naruse (Yui NARUSE).


I think this should be follow http://bugs.ruby-lang.org/projects/ruby/wiki/MaintainerDischargingProcess

> when someone offers to maintain a branch, they must also declare how long they are maintaining it for.

I doubt anyone can commit such period, and I don't believe such commitment.

Therefor the important one is discharge process or emergency release process.
----------------------------------------
misc #9218: Branch Maintainer Appointment / Discharge Process
https://bugs.ruby-lang.org/issues/9218#change-43425

Author: hone (Terence Lee)
Status: Open
Priority: Normal
Assignee: 
Category: Project
Target version: 


There's a library appointment / discharge policy see ruby-core:25764 (http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/25764). There should be a similar policy for branch maintainership.

A. candidacy process
when someone offers to maintain a branch, they must also declare how long they are maintaining it for.
B. election process
looking at the candidates and recommending someone on ruby-core/ruby-dev. When elected, the new maintainer must decide and announce how long they will maintain it for.
C. discharge process
1a. declared they are not maintaining it anymore
1b. is inactive for 1+ month and a discussion takes place on ruby-core/dev
2. a new person needs to be elected like described above.


-- 
http://bugs.ruby-lang.org/