FreeBSD Core Team

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The FreeBSD Core Team would be the equivalent of a board of directors, if the FreeBSD Project were a company.

The FreeBSD Project is run by FreeBSD committers, or developers who have SVN commit access.[1] The Core Team exists to provide direction and is responsible for setting goals for the FreeBSD Project and to provide mediation in the event of disputes, and also takes the final decision in case of disagreement between individuals and teams involved in the project.[2] The Core Team is also responsible for selecting individuals for other teams related to the development and ongoing maintenance of FreeBSD, such as the Security Officer, the Release Engineering team, and the Port Manager team.[1] Finally, the Core Team also vote on nominations for new committers. In the event of a breach of internal rules of conduct, it falls to the core team to decide on sanctions.[2]

The FreeBSD Core Team is the equivalent of a similar body in the NetBSD Project called the Core Group.

Current members[3]

History and purpose

The FreeBSD Core Team began as an unofficial group of programmers, mainly consisting of those that initiated the FreeBSD Project itself.[2] There were eleven members, and new members could only join through invitation.

As the FreeBSD project grew, so did the Core Team. By the year 2000, there were over 200 active committers, and the Core Team had expanded to 18 people. Some Core members were completely inactive, others far less active than many non-members, and there were even accusations of cronyism. The old, informal structure was no longer considered viable, and in early 2000 discussions were had regarding the future of the organisation.[2] A set of bylaws were formulated by Jonathan Lemon, Warner Losh and Wes Peters.[2] In a general vote by active committers on August 28, 2000, these bylaws passed by 117 votes to 5 against.

The FreeBSD Core Team is now an elected body comprising nine members from the pool of project developers with rights to directly change the Project repositories (committers). Committers are entitled to vote in Core elections if they have made at least one change to one of the Project's repositories in the past 12 months.

The first election took place in September 2000.[4] Seventeen candidates stood for election, including eight of the existing Core Team. Five were re-elected, alongside four new members.[4] Elections have taken place every two years since, the most recent election results being announced on July 6, 2016.[5] Elections shall be held two years after the last vote, even if the previous election was early.[6] Elections may be held early if the membership of the Core Team fall below seven,[6] or if petitioned for by 1/3 of active developers.[6] The bylaws may be changed by a 2/3 majority of committers if at least 50% of active committers participate in the vote.[6]

The Core Team appoints a secretary at its own discretion. This non-voting position exists to provide a central point of contact between external parties and the group, for keeping track of the agenda, and for acting as the interface between Core and other internal groups such as the Account Creation team. The Core Team Secretary is also responsible for writing and distributing monthly status reports to the FreeBSD developer community.

Election procedure

The election lasts for five weeks. During the first week, committers who wish to run for election announce their intention to do so. In the four weeks that follow the application period, active committers vote for up to nine candidates.[1]

After the voting period closes, votes are counted. Ties are resolved by unambiguously elected candidates; for instance, if there is a tie for ninth place, the first eight decide which of the tied candidates will join the team.[1] The results are announced within one week of the end of the voting period, and the newly elected team enters office one week after the announcement.[1]

List of members

Name 2000[4] 2002[7] 2004[8] 2006[9] 2008[10] 2010[11] 2012[12] 2014[13] 2016[5] 2018[3]
Allan Jude YesY YesY
Andrey A. Chernov (Wikidata) YesY
Attilio Rao YesY
Baptiste Daroussin YesY YesY
Benedict Reuschling YesY YesY
Benno Rice YesY
Brooks Davis YesY YesY YesY YesY
Colin Percival YesY
David Chisnall YesY YesY
David Greenman YesY
Doug Rabson YesY
Ed Maste YesY YesY
Gavin Atkinson YesY YesY
George V. Neville-Neil YesY YesY YesY YesY
Giorgos Keramidas YesY YesY
Gleb Smirnoff YesY
Greg Lehey YesY YesY
Hiroki Sato YesY YesY YesY YesY YesY YesY YesY
Jeff Roberson YesY
John Baldwin YesY YesY YesY YesY YesY YesY
Jordan Hubbard YesY
Jun Kuriyama YesY YesY
Konstantin Belousov YesY YesY
Kris Kennaway YesY
Kris Moore YesY YesY
Mark Murray YesY YesY
Martin Wilke YesY
Mike Smith YesY
Murray Stokely YesY YesY YesY YesY
Pav Lucistnik YesY
Peter Wemm YesY YesY YesY YesY YesY YesY
Robert Watson YesY YesY YesY YesY YesY YesY YesY
Satoshi Asami YesY
Scott Long YesY
Sean Chittenden YesY
Thomas Abthorpe YesY
Warner Losh YesY YesY YesY YesY YesY YesY
Wes Peters YesY YesY YesY
Wilko Bulte YesY YesY YesY

See also

References

  1. 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.; Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.

External links