Hi Simon, hi everyone, I'll find the time to contribute. In general, I feel that we at SC should participate more in the Haskell community. On the other hand, I'll completely understand if you decide that someone who (unfortunately) hasn't been actively involved in GHC development in the last couple of years shouldn't be on the committee. So no pressure! Roman

On 3 Feb 2017, at 11:36, Simon Peyton Jones wrote:

I'd be fine with that, if Roman feels he has enough time to contribute pro-actively. (Hi Roman!)

You are quite right to raise this Atze; it's not good having members who are, in practice, unable to contribute. One just ends up with guilt all round :-). So, thank you!

Simon

| -----Original Message----- | From: ghc-steering-committee [mailto:ghc-steering-committee- | bounces@haskell.org] On Behalf Of Atze Dijkstra | Sent: 03 February 2017 11:00 | To: ghc-steering-committee@haskell.org | Cc: Donald Stewart ; rleshchinskiy@gmail.com | Subject: [ghc-steering-committee] GHC steering committee participation | | Dear committee members, | | as you may have noticed I have not actively participated in proposal | reviewing. I can wrap this in a long or short story, but at the core lies | lack of time combined with my role at Standard Chartered (SC) evolving in a | direction less involved with GHC and Haskell language design/implementation | than I originally thought it might be. Privately, outside of SC, I also see | little time and energy left for committee activities. The work on proposals | seems to have started actively and vigorously and I'd rather not be this | silent non-contributing participant. I feel it is important to have somebody | from what can likely be called the largest Haskell based industrial | development group be in contact with and contribute to what by definition is | an important tool for us. After some consultation with colleagues I found | Roman Leshchinskiy (rleshchinskiy@gmail.com) to be willing to replace me in | the committee. For most of the committee members I guess he is already known | from the FP community so I leave further introduction up to himself. Within | SC Roman is responsible for GHC related supporting infrastructure and as | such is more than I am involved in and confronted with GHC intricacies, | which places him at a better position to contribute to the GHC steering | committee from an industrial perspective. I am aware that stepping down | might cause inconvenience, but also feel that this better can be done now | than later when the committee is already on farther on its way in dealing | with proposals. I am also aware that it is not really up to me to decide | what to do next after me stepping down, but I feel the proposed replacement | by Roman is the best option from my perspective. | | all the best, | Atze | | | _______________________________________________ | ghc-steering-committee mailing list | ghc-steering-committee@haskell.org | https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskel | l.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering- | committee&data=02%7C01%7Csimonpj%40microsoft.com%7Cc3d7e811a8c6496eb0d808d44 | c23c313%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636217163861446855&sdat | a=eeW9ValuhSlOb5O9u1Wv76%2FGPNefIHMiyXhs6vl5l98%3D&reserved=0

Usually, I would agree with what you are writing. However, this is a special situation as Atze never actually started to participate as a member of this committee. The situation is the same as when he had declined Simon and Simon’s original request. In that case, Simon and Simon would just have picked somebody else. Hence, if both Simons are in favour of replacing Atze by Roman, I think, we should just do this and, if they want to pick somebody else, the same applies. Personally, I would love to have somebody from SC involved as they are one of the biggest commercial users of Haskell. That is a very valuable perspective to tap into. Manuel

Joachim Breitner :

Hi Committee,

it is very thoughtful of Atze to suggest a replacement as he steps down, and I have no reasons to doubt Roman’s qualification. But given that one purpose of instantiating the committee is to make governance a bit more transparent, I think it would be nice to publicly announce that we have a spot to fill and solicit nominations.

We can mention that we try to maintain our existing nice balance between academics, industry users etc, and surely selecting Roman is a possible, maybe likely, outcome. Nevertheless it would not hurt doing so publicly.

Although it would look better if we actually accepted some proposal first, to show that the committee is doing more than just filling seats :-)

We had no objections to Simon’s suggestion to adopt

- Update levity polymorphism - Constraint vs type

so I take that as “the committee agrees”. Ben, as the committee’s de- facto secretary, would you merge and label these proposals?

Greetings, Joachim

-- -- Joachim “nomeata” Breitner mail@joachim-breitner.de • https://www.joachim-breitner.de/ XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

Simon and I discussed this, and while we see merit in Joachim's point, we're happy to just replacing Adze with Roman forthwith, for the reasons Manual sets out below. Life is short -- we should concentrate on progressing proposals rather than more nomination cycles. There'll be time for that later! OK? Let's just go for it. Simon | -----Original Message----- | From: ghc-steering-committee [mailto:ghc-steering-committee- | bounces@haskell.org] On Behalf Of Manuel M T Chakravarty | Sent: 04 February 2017 02:33 | To: Joachim Breitner | Cc: ghc-steering-committee@haskell.org | Subject: Re: [ghc-steering-committee] GHC steering committee participation | | Usually, I would agree with what you are writing. However, this is a special | situation as Atze never actually started to participate as a member of this | committee. The situation is the same as when he had declined Simon and | Simon’s original request. In that case, Simon and Simon would just have | picked somebody else. Hence, if both Simons are in favour of replacing Atze | by Roman, I think, we should just do this and, if they want to pick somebody | else, the same applies. | | Personally, I would love to have somebody from SC involved as they are one | of the biggest commercial users of Haskell. That is a very valuable | perspective to tap into. | | Manuel | | > Joachim Breitner : | > | > Hi Committee, | > | > it is very thoughtful of Atze to suggest a replacement as he steps | > down, and I have no reasons to doubt Roman’s qualification. But given | > that one purpose of instantiating the committee is to make governance | > a bit more transparent, I think it would be nice to publicly announce | > that we have a spot to fill and solicit nominations. | > | > We can mention that we try to maintain our existing nice balance | > between academics, industry users etc, and surely selecting Roman is a | > possible, maybe likely, outcome. Nevertheless it would not hurt doing | > so publicly. | > | > Although it would look better if we actually accepted some proposal | > first, to show that the committee is doing more than just filling | > seats | > :-) | > | > We had no objections to Simon’s suggestion to adopt | > | > - Update levity polymorphism | > - Constraint vs type | > | > so I take that as “the committee agrees”. Ben, as the committee’s de- | > facto secretary, would you merge and label these proposals? | > | > Greetings, | > Joachim | > | > -- | > -- | > Joachim “nomeata” Breitner | > mail@joachim-breitner.de • | https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.joachim | - | breitner.de%2F&data=02%7C01%7Csimonpj%40microsoft.com%7C39f082e6eee748e18899 | 08d44ca638d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636217724186010688 | &sdata=EB09eNHo90RmsLaul9P9AlByVmFI9uHnTgvG5N9RyS8%3D&reserved=0 | > XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F | > Debian Developer: | > nomeata@debian.org_______________________________________________ | > ghc-steering-committee mailing list | > ghc-steering-committee@haskell.org | > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail. | > haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&da | > ta=02%7C01%7Csimonpj%40microsoft.com%7C39f082e6eee748e1889908d44ca638d | > 3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636217724186010688&sdat | > a=dpAsFCFqBSnb8fCAVYtJAcB6wMF9FngwY68eWhwS0O4%3D&reserved=0 | | _______________________________________________ | ghc-steering-committee mailing list | ghc-steering-committee@haskell.org | https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskel | l.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering- | committee&data=02%7C01%7Csimonpj%40microsoft.com%7C39f082e6eee748e1889908d44 | ca638d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636217724186010688&sdat | a=dpAsFCFqBSnb8fCAVYtJAcB6wMF9FngwY68eWhwS0O4%3D&reserved=0

So that community members understand what happened, I believe this wiki page should be updated to reflect the change in committee membership: https://ghc.haskell.org/trac/ghc/wiki/SteeringCommittee On Wed, Feb 8, 2017 at 11:51 AM, Ben Gamari wrote:

Simon Peyton Jones writes:

...

Simon and I discussed this, and while we see merit in Joachim's point, we're happy to just replacing Adze with Roman forthwith, for the reasons Manual sets out below.

Life is short -- we should concentrate on progressing proposals rather than more nomination cycles. There'll be time for that later!

OK? Let's just go for it.

Yes, I can see the argument for this. Given how stretched we all are already, I suppose this is the pragmatic way forward. No objection here.

Cheers,

- Ben

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- Chris Allen Currently working on http://haskellbook.com

Thank you for the rapid (and permanent, since you deduplicated the information) fix! On Sun, Oct 22, 2017 at 10:49 PM, Joachim Breitner wrote:

Hi,

well spotted and fixed.

Joachim

Am Sonntag, den 22.10.2017, 22:47 -0500 schrieb Christopher Allen:

...

So that community members understand what happened, I believe this wiki page should be updated to reflect the change in committee membership:

https://ghc.haskell.org/trac/ghc/wiki/SteeringCommittee

On Wed, Feb 8, 2017 at 11:51 AM, Ben Gamari wrote:

...

Simon Peyton Jones writes:

...

Simon and I discussed this, and while we see merit in Joachim's point, we're happy to just replacing Adze with Roman forthwith, for the reasons Manual sets out below.

Life is short -- we should concentrate on progressing proposals rather than more nomination cycles. There'll be time for that later!

OK? Let's just go for it.

Yes, I can see the argument for this. Given how stretched we all are already, I suppose this is the pragmatic way forward. No objection here.

Cheers,

- Ben

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- Joachim Breitner mail@joachim-breitner.de http://www.joachim-breitner.de/

_______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

-- Chris Allen Currently working on http://haskellbook.com