<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Re: Short of taking over the package, we would have to ask for an
      emergency Hackage release if the neither maintainer shows up to do
      it in a reasonable time frame.<br>
      <br>
      These are non-maintainer uploads and is a job of Hackage Trustees
      (for all of Hackage, not only some "better" packages).
<a class="moz-txt-link-freetext" href="https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#3-source-changes-simple-patches">https://github.com/haskell-infra/hackage-trustees/blob/master/policy.md#3-source-changes-simple-patches</a><br>
      <br>
      Anyone can prepare the patch.<br>
      <br>
      - Oleg<br>
    </p>
    <div class="moz-cite-prefix">On 12.2.2021 1.54, Emily Pillmore
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:kl1iq8ns.e4c99428-b8ee-4af8-9862-3fb66249772a@we.are.superhuman.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>
        <div>
          <div>Hi All,<br>
          </div>
          <div><br>
          </div>
          <div>Over the past year, two things have become increasingly
            clear to me as I've carried out my CLC duties:<br>
          </div>
          <div><br>
          </div>
          <div><br>
          </div>
          <div>1. The CLC is under-resourced. This is evidenced by the
            fact that several maintainers who are not CLC members have
            been forced to step up to help take on some of the
            maintenance burden for many of the CLC libraries. Namely,
            `vector`, `bytestring`, `random`, `unix`, and more. The
            current CLC head count is not enough to dedicate at least
            one maintainer per package, which is leading to us all being
            spread thin, and the less-loved packages are falling into
            disrepair as a result. Couple this with the fact that
            roughly half the CLC do not have these packages actively
            within their maintenance cycles, and we arrive at the
            current problem.<br>
          </div>
          <div><br>
          </div>
          <div>2. The current set of "core" libraries does not cover
            what is generally considered "core" in the community. From
            now on, I'll refer to "core" packages as "boot" packages,
            and identify core packages to be those that are have proven
            to be incredibly popular tools for building things in
            Haskell. For example `zlib`, `parsec`, `regex-base`,
            `regex-posix`, `network`, etc. In particular, if any of
            these core packages saw their current authors disappear, or
            incapacitated in any sense, it would seriously harm the
            Haskell ecosystem. `cabal-install`, for example, requires
            several of those packages as upstream dependencies.
            Currently, we are dealing with this nightmare situation
            where work is stalled across many packages due to a
            particular set of maintainers being very difficult to reach,
            one of whom having disappeared completely for all
            maintenance intents and purposes.<br>
          </div>
          <div><br>
          </div>
          <div>Ergo, we have a problem. Thankfully, many people have
            stepped up showing renewed interest in maintaining such
            packages with the latest crop of CLC folks, and this poses
            an interesting opportunity.<br>
          </div>
          <div><br>
          </div>
          <div>My proposal is this:<br>
          </div>
          <div><br>
          </div>
          <div>1. We expand the CLC from 9 members to 22 members such
            that we have at least 1 CLC maintainer per boot package.
            There are a large number of fantastic candidates already
            available, who would be perfect for the role. In fact, many
            of the candidates whom we would ask are already maintaining
            these packages. In particular, Andrew Lelechenko, Simon
            Jakobi, Viktor Dukhovni, Dominic Steinitz, Alexey Khuedyakov
            are already serving within this role (and thank you for
            it!). Andreas Abel has also offered to help take on one of
            the core packages.<br>
          </div>
          <div><br>
          </div>
          <div>2. We consider a dedicated "Haskell Action Team" (name
            and idea courtesy of Carter Schonwald) to oversee packages
            in the Haskell github repo that can act as supplementary
            maintainers for many of the core packages contained therein.
            Currently, there are many in need of help. `zlib` comes to
            mind, which is currently blocking `bytestring-0.11`
            migration work due to having no available maintainer with
            the permissions to do a release. This, in turn, is stalling
            `cabal-install`. Short of taking over the package, we would
            have to ask for an emergency Hackage release if the neither
            maintainer shows up to do it in a reasonable time frame.<br>
          </div>
          <div><br>
          </div>
          <div>This is just one step towards helping ease the burden of
            maintenance of so-called core and boot packages. I hope you
            agree that this is a good idea, and if we get enough thumbs
            up, then Chessai and I will draw up the necessary changes to
            the CLC remit and we'll get started!<br>
          </div>
          <div><br>
          </div>
          <div>Cheers,<br>
          </div>
          <div>Emily<br>
          </div>
        </div>
        <div>
          <div style="display: none; border: 0px; width: 0px; height:
            0px; overflow: hidden; visibility: hidden;"><img
src="https://r.superhuman.com/U7KH74R7u-V9iyQnGsldIpSxcbRAMT2Jo_DcUpzixrkPj5PwLKOkDXILUETmGzIi8rjC_ejMHs7kzXTAum8_7pq2tJWtULkJLs2q5QcZdYr9HlorvLsgEa6B3IETytSDpo6YZt0_MrVTWDWIB6LM0v8Ig4cWQf9jkOQY9u8z58_l1jMTpfXCpAw.gif"
              alt=" " style="display: none; border: 0px; width: 0px;
              height: 0px; overflow: hidden; visibility: hidden;"
              moz-do-not-send="true" width="1" height="0"><!--                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                --></div>
          <br>
        </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>