Difference between revisions of "Core Libraries Committee"

From HaskellWiki
Jump to navigation Jump to search
(→‎Current members: Add note about GitHub Team)
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
To contact the Haskell Core Libraries Committee, send email to '''core-libraries-committee [AT] haskell.org'''.
+
To contact the Haskell Core Libraries Committee, send email to '''core-libraries-committee [AT] haskell.org'''. CC [http://www.haskell.org/haskellwiki/Library_submissions#Guidance_for_proposers libraries@haskell.org] if you want to reach a wider audience.
   
 
== Responsibilities ==
 
== Responsibilities ==
   
The [[Core Libraries Committee]] acts as the ''Maintainer'' per the [[Library submissions]] guidelines for many of the core libraries that make up the Haskell Platform.
+
The [[Core Libraries Committee]] acts as the ''Maintainer'' per the [[Library submissions]] guidelines for many of the [http://www.haskell.org/haskellwiki/Library_submissions#The_Core_Libraries core libraries] that make up the Haskell Platform.
   
 
== Current members ==
 
== Current members ==
   
 
* Edward Kmett (chair)
 
* Edward Kmett (chair)
  +
* Eric Mertens (Term ending June 2017)
* Brent Yorgey
 
 
* Dan Doel
 
* Dan Doel
 
* Michael Snoyman
 
* Michael Snoyman
  +
* Luite Stegeman (Term ending June 2017)
* Doug Beardsley
 
 
* Joachim Breitner
 
* Joachim Breitner
* Mark Lentczner (ex-officio as the Haskell Platform Maintainer)
 
   
 
e-mail: core-libraries-committee [AT] haskell.org
 
e-mail: core-libraries-committee [AT] haskell.org
   
GitHub: The [https://github.com/orgs/haskell/teams/core-libraries-committee Core Libraries Committee Team] can be mentioned/notified in GitHub conversations by using the syntax <code>@haskell/core-libraries-committee</code>.
+
GitHub: The [https://github.com/orgs/haskell/teams/core-libraries-committee Core Libraries Committee Team] (link only resolves if you are a member of [https://github.com/haskell github.com/haskell]) can be mentioned/notified in GitHub conversations by using the syntax <code>@haskell/core-libraries-committee</code>.
   
 
== Operation ==
 
== Operation ==
   
The committee consists of 7 members. Members are expected to serve a 3 year term, and terms are staggered so that 2 members step down each year, at the end of June.
+
The committee consists of 9 members. Members are expected to serve a 3 year term, and terms are staggered so that roughly 3 members have their terms end each year, at the end of June. We currently have 3 vacancies as a result of [https://groups.google.com/forum/#!topic/haskell-core-libraries/VHQ4cIClI6A expanding the committee].
   
 
The members will elect one of their number to be chair each year. The chair is responsible for making sure that things keep moving, and to ensure that a conclusion is reached on any issues raised.
 
The members will elect one of their number to be chair each year. The chair is responsible for making sure that things keep moving, and to ensure that a conclusion is reached on any issues raised.
Line 27: Line 26:
 
When a member steps down, either because they have reached the end of their term or because other circumstances require them to step down early, open self-nominations will be sought from the community via the libraries@ mailing list. Previous committee members, including those who have just stepped down, will also be eligible for nomination.
 
When a member steps down, either because they have reached the end of their term or because other circumstances require them to step down early, open self-nominations will be sought from the community via the libraries@ mailing list. Previous committee members, including those who have just stepped down, will also be eligible for nomination.
   
The committee will then select a replacement from amongst those nominated. For the purposes of considering nominations, the committee will include any outgoing members who are not seeking re-appointment.
+
The committee will then select a replacement from amongst those nominated. For the purposes of considering nominations, the committee will include any outgoing members who are seeking re-appointment.
   
 
The committee replacement process is intentionally currently very light. As we get more experience, we may wish to change it, e.g. by having a larger subset of "the community" vote on nominations.
 
The committee replacement process is intentionally currently very light. As we get more experience, we may wish to change it, e.g. by having a larger subset of "the community" vote on nominations.
   
 
It is expected the committee will discuss any matters brought to it amongst themselves, and if they think appropriate, with the wider community via [http://www.haskell.org/pipermail/libraries/ libraries@haskell.org], to try to reach consensus. Ultimately, the committee will make decisions by more than half of the membership voting for a particular outcome. These rules of operation may also be changed in the same way.
If any member of the community wishes to raise any issue with the committee, they may contact it by e-mailing core-libraries-committee [AT] haskell.org.
 
   
  +
== Resources ==
It is expected the committee will discuss any matters brought to it amongst themselves, and if they think appropriate, with the wider community, to try to reach consensus. Ultimately, the committee will make decisions by more than half of the membership voting for a particular outcome. These rules of operation may also be changed in the same way.
 
  +
 
If any member of the community wishes to raise any issue with the committee, they may contact it by e-mailing core-libraries-committee [AT] haskell.org (fairly narrow distribution) ([https://groups.google.com/forum/#!forum/haskell-core-libraries archives]) or libraries@haskell.org ([http://www.haskell.org/pipermail/libraries/ much broader distribution]).
  +
  +
Material related to active proposals, resolutions, meeting minutes, etc. can be found at https://prime.haskell.org/wiki/Libraries
   
 
[[Category:Community]]
 
[[Category:Community]]

Revision as of 21:50, 24 November 2015

To contact the Haskell Core Libraries Committee, send email to core-libraries-committee [AT] haskell.org. CC libraries@haskell.org if you want to reach a wider audience.

Responsibilities

The Core Libraries Committee acts as the Maintainer per the Library submissions guidelines for many of the core libraries that make up the Haskell Platform.

Current members

  • Edward Kmett (chair)
  • Eric Mertens (Term ending June 2017)
  • Dan Doel
  • Michael Snoyman
  • Luite Stegeman (Term ending June 2017)
  • Joachim Breitner

e-mail: core-libraries-committee [AT] haskell.org

GitHub: The Core Libraries Committee Team (link only resolves if you are a member of github.com/haskell) can be mentioned/notified in GitHub conversations by using the syntax @haskell/core-libraries-committee.

Operation

The committee consists of 9 members. Members are expected to serve a 3 year term, and terms are staggered so that roughly 3 members have their terms end each year, at the end of June. We currently have 3 vacancies as a result of expanding the committee.

The members will elect one of their number to be chair each year. The chair is responsible for making sure that things keep moving, and to ensure that a conclusion is reached on any issues raised.

When a member steps down, either because they have reached the end of their term or because other circumstances require them to step down early, open self-nominations will be sought from the community via the libraries@ mailing list. Previous committee members, including those who have just stepped down, will also be eligible for nomination.

The committee will then select a replacement from amongst those nominated. For the purposes of considering nominations, the committee will include any outgoing members who are seeking re-appointment.

The committee replacement process is intentionally currently very light. As we get more experience, we may wish to change it, e.g. by having a larger subset of "the community" vote on nominations.

It is expected the committee will discuss any matters brought to it amongst themselves, and if they think appropriate, with the wider community via libraries@haskell.org, to try to reach consensus. Ultimately, the committee will make decisions by more than half of the membership voting for a particular outcome. These rules of operation may also be changed in the same way.

Resources

If any member of the community wishes to raise any issue with the committee, they may contact it by e-mailing core-libraries-committee [AT] haskell.org (fairly narrow distribution) (archives) or libraries@haskell.org (much broader distribution).

Material related to active proposals, resolutions, meeting minutes, etc. can be found at https://prime.haskell.org/wiki/Libraries