Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Security

Current Security Officer: Unknown User (danielbeck)
Term: 2016-12-07 to 2017-12-07

The Security Team Lead coordinates the security-related activities in the Jenkins project.

Infrastructure

note:  This position will be filled as part of the 2019 elections. 

The Infrastructure Team lead oversees the Jenkins project infrastructure.

  • Direct triage of issues
  • Direct maintenance of Jenkins project infrastructure ('INFRA' issues)
  • Encourage contributors to INFRA project
  • Communicates maintenance windows and managing the execution of those windows

Events

Current Events Officer: Unknown User (atong)
Term: 2016-02-24 - 2017-02-24

note: This team lead position was approved in the 2015-02-17 governance meeting

The Events Team Lead has an active role in driving and managing Jenkins community events. Such events include Jenkins User Conference, Jenkins Area Meetups, other Jenkins community events (FOSDEM, SCALE), and speaking opportunities. The Events Team Lead is tasked with the following responsibilities:

  • Process in coming events related requests from users, dev, events mailing lists
  • Point of contact for Jenkins community events (mentioned above)
  • Drive communication efforts surrounding Jenkins community events
  • Drive content/agenda for JUC
  • Plan and coordinate logistics as needed for Jenkins community events
  • Oversee and ensure the success of the overall Jenkins Area Meetups:
    • Maintainer of Jenkins Area Meetup account on meetup.com
    • Work with organizers to ensure their success - assist as needed with speaker, sponsors identification
    • Guide new organizers process to start up their local JAM

Release

Current Release Officer: Unknown User (olivergondza)
Term: 2016-03-30 - 2017-03-30

note: This team lead position was approved in the 2015-02-17 governance meeting

  • 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)

Documentation

note:  This team lead position was approved in the 2019-09-11 governance meeting. This position will be filled as part of the 2019 elections. 

The Documentation Team lead oversees the Jenkins project documentation.

  • Enables website/documentation contribution from the community
  • Editor for Jenkins blog
  • Leads or is involved with Documentation Special Interest Group
  • No labels