<div dir="auto">It’s probably worth looking at the wiki edit history too. </div><div dir="auto"><br></div><div dir="auto">I’m pretty sure some edits were done to the policy in the past 18 months without community feedback or discussion. </div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 7, 2021 at 1:33 PM Oleg Grenrus <<a href="mailto:oleg.grenrus@iki.fi">oleg.grenrus@iki.fi</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>Thanks for this reply. It made me reread
<a href="https://wiki.haskell.org/Library_submissions" target="_blank">https://wiki.haskell.org/Library_submissions</a> page.<br>
In the Guide to proposers section it says:<br>
<br>
- All library proposals should start on the relevant issue
tracker.<br>
- At this point, the library maintainer is responsible for taking
next steps.<br>
- ... or decide that this is a controversial decision that must be
discussed with the CLC.<br>
<br>
- If the CLC decides that the discussion must be discussed with
the libraries@ mailing list, the original proposer may be asked to
moderate the libraries@ mailing list discussion<br>
<br>
So do I understand right: it's up to the base-library maintainer
to decide whether a change is controversial and must to be
discussed with CLC, which in can elevate it to wider discussion or
not.<br>
<br>
The page however lists Edward Kmett and Ryan Scott as
base-maintainers, which I'm pretty sure is not right.<br>
Who are the base maintainers?<br>
<br>
I'm sorry for my misunderstanding, it seems you are right Sandy,
the issues should be discussed in the issue trackers first, and
only elevated to libraries@ list if CLC decides it needs to!<br>
That is much more reasonable then going to the libraries@ directly
for every issue.</p></div><div><p><br>
<br>
- Oleg<br>
<br>
</p>
<div>On 7.7.2021 19.41, Sandy Maguire wrote:<br>
</div>
<blockquote type="cite">
<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">lemming@henning-thielemann.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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">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">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">Libraries@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries</a><br>
</blockquote>
</div>
</blockquote>
</div>
_______________________________________________<br>
Libraries mailing list<br>
<a href="mailto:Libraries@haskell.org" target="_blank">Libraries@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries</a><br>
</blockquote></div></div>