<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>As I understood from the
<a class="moz-txt-link-freetext" href="https://wiki.haskell.org/Library_submissions">https://wiki.haskell.org/Library_submissions</a> page (to which GHC
wiki links from
<a class="moz-txt-link-freetext" href="https://gitlab.haskell.org/ghc/ghc/-/wikis/contributing#contributing-to-ghc">https://gitlab.haskell.org/ghc/ghc/-/wikis/contributing#contributing-to-ghc</a>),
this job of elevating issue to the CLC is the job of a library
maintainer. So I repeat my question: who are the current
maintainer(s) of base library to make these calls.<br>
<br>
I'd like to know whom comments I can and cannot ignore when
proposing changes, as everyone has an opinion on how base should
be (myself including).<br>
<br>
- Oleg<br>
</p>
<div class="moz-cite-prefix">On 7.7.2021 20.35, Carter Schonwald
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHYVw0wPh5d=SOQhMRnO-VxMC=R-KQN5_GdE0D7dm0jexOiqLQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Respectfully: some of us like mailing lists for
complicated discussions :) </div>
<div dir="auto"><br>
</div>
<div dir="auto">The issue here is deviation from processs that
support a wider range of participants with different
accessibility needs and varying levels of volunteer time. </div>
<div dir="auto"><br>
</div>
<div dir="auto">More over, a mailing list is easier for curious
parties to subscribe to and filter to a dedicated inbox. Have
you ever tried doing robust mailbox filters for GitHub or
gitlab? It’s pretty tricky without creating a firehose of all
repo events unless you’re in a group that’s always tagged. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Any ticket tagged core libraries on gitlab needs
to have a corresponding email to this list for folks who aren’t
administratively in that notification group. Or needs to link to
a thread here motivating it. </div>
<div dir="auto"><br>
</div>
<div dir="auto">I’m on that notification list for gitlab because
current clc folks wanted me to continue helping out, but that’s
not a scalable open participation model. </div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jul 7, 2021 at 12:41
PM Sandy Maguire <<a href="mailto:sandy@sandymaguire.me"
moz-do-not-send="true">sandy@sandymaguire.me</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div dir="ltr">At risk of being the messenger who gets
shot.... <br>
<br>
As an outsider, it seems very reasonable to me to file a
bug against the issue tracker for a project whose code I
think should be changed. For better or worse, this is the
way that 99% of software projects work. Expecting everyone
in the community to know that they _shouldn't_ be filing
bugs against the issue tracker is a losing battle. I'm
more hooked in than most, and even I didn't know this.<br>
<div><br>
</div>
<div>I can empathize with things not being done the way
you'd like to be, but the claim that things happening on
the GHC tracker are done "in private" is silly. The
gitlab tracker is 10x more accessible, and the lack of
community engagement on the mailing lists speaks
volumes.<br>
<br>
And besides, nobody wants to be on a mailing list
anyway. It's a terrible experience with weird branching
and no persistence, and while there are archives, it's
an extremely unpleasant thing to try to spelunk through.<br>
<br>
Best,<br>
Sandy</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jul 7, 2021 at
8:52 AM Henning Thielemann <<a
href="mailto:lemming@henning-thielemann.de"
target="_blank" moz-do-not-send="true">lemming@henning-thielemann.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><br>
On Wed, 7 Jul 2021, Oleg Grenrus wrote:<br>
<br>
> For example<br>
><br>
> - <a
href="https://gitlab.haskell.org/ghc/ghc/-/issues/20044"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://gitlab.haskell.org/ghc/ghc/-/issues/20044</a>
ByteArray migration<br>
> from primitive to base<br>
> - <a
href="https://gitlab.haskell.org/ghc/ghc/-/issues/20027"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://gitlab.haskell.org/ghc/ghc/-/issues/20027</a>
Changing Show String<br>
> behavior<br>
><br>
> Why they are discussed "in private", I thought
libraries@ list is where<br>
> such changes should be discussed.<br>
<br>
I think so, too, and I missed them as well.<br>
_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org" target="_blank"
moz-do-not-send="true">Libraries@haskell.org</a><br>
<a
href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries</a><br>
</blockquote>
</div>
_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org" target="_blank"
moz-do-not-send="true">Libraries@haskell.org</a><br>
<a
href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Libraries mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Libraries@haskell.org">Libraries@haskell.org</a>
<a class="moz-txt-link-freetext" href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries">http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries</a>
</pre>
</blockquote>
</body>
</html>