Request for participation: Jenkins Release Officer candidates

[R. Tyler Croy]

Based on the team lead structure
(https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams)
which was previously approved in a project governance meeting, I am asking on
behalf of the Jenkins board[0], for candidates who are willing to act as the
Jenkins Release Officer[1].


The Jenkins Release Officer would play a key role in driving release processes
and the release tooling. The Release Officer would not play an exclusive role
in the Jenkins projects release infrastructure but would be the point person to:

* Manage keys for signing and producing official Jenkins releases (e.g. GPG
signing keys, Windows and Mac OS X certificates)
* Be responsible for release automation to produce LTS and weekly releases
* Operate LTS/weekly releases directly, or name specific release managers to be
responsible for those releases (e.g. "this person is responsible for this LTS
series, backporting, etc")
* Act as a single point of contact for the Security Officer to incorporate
security fixes/backports into releases (this implies membership to Jenkins CERT
team)


The expected term for the Release Officer would be 12 months.

Contributors interested in being considered for the Jenkins Release Officer
position should email the board: jenkins...@googlegroups.com in the next
*seven* days explaining their qualifications for the position.



After that seven day period expires, the board will select a candidate to
appoint to the position who will be able to act on behalf of the Governance
Board on matters pertaining to the position described above.



[0] The current board: <https://wiki.jenkins-ci.org/display/JENKINS/Governance+Board>
[1] https://wiki.jenkins-ci.org/display/JENKINS/Team+Leads#TeamLeads-Release



Cheers,
- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[Oleg Nenashev]

Yay, we need a release manager!
On the other may be a work, which requires a significant amount of time (>8 hours per week I'd guess).

понедельник, 7 марта 2016 г., 20:52:03 UTC+1 пользователь R Tyler Croy написал:

[R. Tyler Croy]

(replies inline)

On Mon, 07 Mar 2016, R. Tyler Croy wrote:

> Based on the team lead structure
> (https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Project+sub-teams)
> which was previously approved in a project governance meeting, I am asking on
> behalf of the Jenkins board[0], for candidates who are willing to act as the
> Jenkins Release Officer[1].
>
>
> The Jenkins Release Officer would play a key role in driving release processes
> and the release tooling. The Release Officer would not play an exclusive role
> in the Jenkins projects release infrastructure but would be the point person to:
>
> * Manage keys for signing and producing official Jenkins releases (e.g. GPG
> signing keys, Windows and Mac OS X certificates)
> * Be responsible for release automation to produce LTS and weekly releases
> * Operate LTS/weekly releases directly, or name specific release managers to be
> responsible for those releases (e.g. "this person is responsible for this LTS
> series, backporting, etc")
> * Act as a single point of contact for the Security Officer to incorporate
> security fixes/backports into releases (this implies membership to Jenkins CERT
> team)

On behalf of the governance board, I'm pleased to announce that Oliver Gondza
has been chosen as the Jenkins Release Officer. If you're a user of Jenkins'
LTS releases, you're already familiar with some of Oliver's work. Personally, I
look forward to Oliver continuing to work with abayer, svanoort and numerous
others to help make Jenkins releases of higher quality and more automated.


For reference on the term of this position and responsibilities, please refer
to the Team Leads page:
<https://wiki.jenkins-ci.org/display/JENKINS/Team+Leads>


Cheers