From m at jaspervdj.be  Thu Oct 29 15:22:57 2020
From: m at jaspervdj.be (Jasper Van der Jeugt)
Date: Thu, 29 Oct 2020 16:22:57 +0100
Subject: [Haskell-community] Haskell.org committee proposals & GRC
Message-ID: <20201029152257.GC4755@kakigori>

Hi all,

The Haskell.org committee would like to adopt a new proposal format,
inspired by the GHC Steering Committee.  We have created a repository
with proposals here:

   https://github.com/haskell-org/committee

I would like to call the members of the committee to vote on these
proposals, but we also value community feedback.  The two proposals
are:

 -  0001: Establish the proposal process
    https://github.com/haskell-org/committee/pull/1
 -  0002: Adopt the GRC code of conduct
    https://github.com/haskell-org/committee/pull/2

For posterity and archival, I am including the full text of the
proposals here.  For the record, I am in favor of accepting both
proposals.

# Proposal 0001: Haskell.org proposals

In an effort to make the work of Haskell.org committee more
transparent, we would like to adopt a proposal process similar to the
[GHC Steering Committee].

The proposed process is fairly light:

1.  New proposals are created as pull requests with a single file,
    following a `proposals/XYZW-some-title.extention` naming scheme.
    A template is available in `proposals/0000-template.md`.

2.  Proposals must have an author set who is responsible for driving
    the discussion.  If the author is not a member of the Haskell.org
    committee, we may additionally appoint a shepherd from the
    committee to help with this.  It is the responsibility of the
    author and the shepherd to notify any communities that may be
    interested in the proposal, so we can gather community feedback.

3.  The proposal must have a link to the PR discussion, so readers can
    easily find the full discussion once the PR is merged.

4.  We strive to make unanimous decisions, but we can use a majority
    vote (the committee has an odd number of members) to move forward.

5.  What happens next depends on whether or not the proposal is
    accepted:

     -  If the proposal is accepted, `date-accepted` is set and the
        proposal is merged into the repository.  A summary with a link
        to the full PR discussion is sent out to
        `community at haskell.org`.

     -  If the proposal is not accepted, the proposal is also merged
        for posterity, but a section is ammended to explain why it was
        rejected.

# Proposal 0002: Guidelines for Respectful Communication

The Haskell.org committee adopts the [Guidelines for Respectful
Communication][grc].

This applies only to members of the board, in in all our public
interactions in the Haskell sphere, including email, social media,
discussion forums, and so on.

We may later adopt a stricter Code of Conduct, or set a Code of
Conduct for platforms we manage (e.g. Discourse, mailing lists), but
that is out of scope for this proposal.

[grc]: https://github.com/ghc-proposals/ghc-proposals/blob/master/GRC.rst
[GHC Steering Committee]: https://github.com/ghc-proposals/ghc-proposals

Warm regards
Jasper

From alexgrcol at hotmail.com  Thu Oct 29 17:06:29 2020
From: alexgrcol at hotmail.com (Alexandre ...)
Date: Thu, 29 Oct 2020 17:06:29 +0000
Subject: [Haskell-community] Haskell.org committee proposals & GRC
In-Reply-To: <20201029152257.GC4755@kakigori>
References: <20201029152257.GC4755@kakigori>
Message-ID: <ROAP284MB0688FBECD00DA242A1C18A0AAA140@ROAP284MB0688.BRAP284.PROD.OUTLOOK.COM>

Hi Jasper,

My vote is:


  *   Proposal 1: Yes (probably a deadline for voting any proposals should be fixed);
  *   Proposal 2: Also yes.

All the best,
Alexandre.

________________________________
De: Jasper Van der Jeugt <jaspervdj at gmail.com> em nome de Jasper Van der Jeugt <m at jaspervdj.be>
Enviado: quinta-feira, 29 de outubro de 2020 12:22
Para: haskell-community at haskell.org <haskell-community at haskell.org>
Cc: committee at haskell.org <committee at haskell.org>
Assunto: Haskell.org committee proposals & GRC

Hi all,

The Haskell.org committee would like to adopt a new proposal format,
inspired by the GHC Steering Committee.  We have created a repository
with proposals here:

   https://github.com/haskell-org/committee

I would like to call the members of the committee to vote on these
proposals, but we also value community feedback.  The two proposals
are:

 -  0001: Establish the proposal process
    https://github.com/haskell-org/committee/pull/1
 -  0002: Adopt the GRC code of conduct
    https://github.com/haskell-org/committee/pull/2

For posterity and archival, I am including the full text of the
proposals here.  For the record, I am in favor of accepting both
proposals.

# Proposal 0001: Haskell.org proposals

In an effort to make the work of Haskell.org committee more
transparent, we would like to adopt a proposal process similar to the
[GHC Steering Committee].

The proposed process is fairly light:

1.  New proposals are created as pull requests with a single file,
    following a `proposals/XYZW-some-title.extention` naming scheme.
    A template is available in `proposals/0000-template.md`.

2.  Proposals must have an author set who is responsible for driving
    the discussion.  If the author is not a member of the Haskell.org
    committee, we may additionally appoint a shepherd from the
    committee to help with this.  It is the responsibility of the
    author and the shepherd to notify any communities that may be
    interested in the proposal, so we can gather community feedback.

3.  The proposal must have a link to the PR discussion, so readers can
    easily find the full discussion once the PR is merged.

4.  We strive to make unanimous decisions, but we can use a majority
    vote (the committee has an odd number of members) to move forward.

5.  What happens next depends on whether or not the proposal is
    accepted:

     -  If the proposal is accepted, `date-accepted` is set and the
        proposal is merged into the repository.  A summary with a link
        to the full PR discussion is sent out to
        `community at haskell.org`.

     -  If the proposal is not accepted, the proposal is also merged
        for posterity, but a section is ammended to explain why it was
        rejected.

# Proposal 0002: Guidelines for Respectful Communication

The Haskell.org committee adopts the [Guidelines for Respectful
Communication][grc].

This applies only to members of the board, in in all our public
interactions in the Haskell sphere, including email, social media,
discussion forums, and so on.

We may later adopt a stricter Code of Conduct, or set a Code of
Conduct for platforms we manage (e.g. Discourse, mailing lists), but
that is out of scope for this proposal.

[grc]: https://github.com/ghc-proposals/ghc-proposals/blob/master/GRC.rst
[GHC Steering Committee]: https://github.com/ghc-proposals/ghc-proposals

Warm regards
Jasper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-community/attachments/20201029/3841b4f1/attachment.html>

From m at jaspervdj.be  Thu Oct 29 20:30:40 2020
From: m at jaspervdj.be (Jasper Van der Jeugt)
Date: Thu, 29 Oct 2020 21:30:40 +0100
Subject: [Haskell-community] Haskell.org committee proposals & GRC
In-Reply-To: <CAKA2Jg+10w_cfB1u+zJ0CkyCy+F5+F+q66oAY4OwhXXctADCYQ@mail.gmail.com>
References: <20201029152257.GC4755@kakigori>
 <CAKA2Jg+10w_cfB1u+zJ0CkyCy+F5+F+q66oAY4OwhXXctADCYQ@mail.gmail.com>
Message-ID: <20201029203040.GE4755@kakigori>

Hi Michael,

Thanks for the feedback.  You're completely right: that sort of
documentation is sorely lacking.  I'll update the proposal and/or
repository to more explicit about this.

Warm regards
Jasper

On Thu, Oct 29, 2020 at 05:40:19PM +0200, Michael Snoyman wrote:
> Maybe this is just me, but I think it would be useful to have documented in
> that repository as well what items fall under the purview of the haskell.org
> committee, and therefore what kinds of proposals would be appropriate.
> Maybe this is just me, but I'm not certain where the line would be drawn
> between different groups and committees within the wider Haskell ecosystem.
> If this is already documented somewhere, a link from the README.md would
> IMO be very helpful.
> 
> On Thu, Oct 29, 2020 at 5:23 PM Jasper Van der Jeugt <m at jaspervdj.be> wrote:
> 
> > Hi all,
> >
> > The Haskell.org committee would like to adopt a new proposal format,
> > inspired by the GHC Steering Committee.  We have created a repository
> > with proposals here:
> >
> >    https://github.com/haskell-org/committee
> >
> > I would like to call the members of the committee to vote on these
> > proposals, but we also value community feedback.  The two proposals
> > are:
> >
> >  -  0001: Establish the proposal process
> >     https://github.com/haskell-org/committee/pull/1
> >  -  0002: Adopt the GRC code of conduct
> >     https://github.com/haskell-org/committee/pull/2
> >
> > For posterity and archival, I am including the full text of the
> > proposals here.  For the record, I am in favor of accepting both
> > proposals.
> >
> > # Proposal 0001: Haskell.org proposals
> >
> > In an effort to make the work of Haskell.org committee more
> > transparent, we would like to adopt a proposal process similar to the
> > [GHC Steering Committee].
> >
> > The proposed process is fairly light:
> >
> > 1.  New proposals are created as pull requests with a single file,
> >     following a `proposals/XYZW-some-title.extention` naming scheme.
> >     A template is available in `proposals/0000-template.md`.
> >
> > 2.  Proposals must have an author set who is responsible for driving
> >     the discussion.  If the author is not a member of the Haskell.org
> >     committee, we may additionally appoint a shepherd from the
> >     committee to help with this.  It is the responsibility of the
> >     author and the shepherd to notify any communities that may be
> >     interested in the proposal, so we can gather community feedback.
> >
> > 3.  The proposal must have a link to the PR discussion, so readers can
> >     easily find the full discussion once the PR is merged.
> >
> > 4.  We strive to make unanimous decisions, but we can use a majority
> >     vote (the committee has an odd number of members) to move forward.
> >
> > 5.  What happens next depends on whether or not the proposal is
> >     accepted:
> >
> >      -  If the proposal is accepted, `date-accepted` is set and the
> >         proposal is merged into the repository.  A summary with a link
> >         to the full PR discussion is sent out to
> >         `community at haskell.org`.
> >
> >      -  If the proposal is not accepted, the proposal is also merged
> >         for posterity, but a section is ammended to explain why it was
> >         rejected.
> >
> > # Proposal 0002: Guidelines for Respectful Communication
> >
> > The Haskell.org committee adopts the [Guidelines for Respectful
> > Communication][grc].
> >
> > This applies only to members of the board, in in all our public
> > interactions in the Haskell sphere, including email, social media,
> > discussion forums, and so on.
> >
> > We may later adopt a stricter Code of Conduct, or set a Code of
> > Conduct for platforms we manage (e.g. Discourse, mailing lists), but
> > that is out of scope for this proposal.
> >
> > [grc]: https://github.com/ghc-proposals/ghc-proposals/blob/master/GRC.rst
> > [GHC Steering Committee]: https://github.com/ghc-proposals/ghc-proposals
> >
> > Warm regards
> > Jasper
> > _______________________________________________
> > Haskell-community mailing list
> > Haskell-community at haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community
> >