<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Fair point.<br><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I wish I could, but the soonest I could start checking it out is in ~3 months.<br>
<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"> - Clark<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 31, 2014 at 11:44 AM, Carter Schonwald <span dir="ltr"><<a href="mailto:carter.schonwald@gmail.com" target="_blank">carter.schonwald@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Problem: no one is really actively working on hackage-server. Are you volunteering? :-)<div class="HOEnZb"><div class="h5">
<span></span><br><br>On Friday, January 31, 2014, Clark Gaebel <<a href="mailto:cgaebel@uwaterloo.ca" target="_blank">cgaebel@uwaterloo.ca</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">We could actually partially automate this:<br>
<br></div><div class="gmail_default" style="font-family:verdana,sans-serif">1) Package maintainership switch is submitted online, with a new replacement package, and perhaps a message.<br>
</div><div class="gmail_default" style="font-family:verdana,sans-serif">2) An email is sent to the maintainer with a link to either:<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"> - delete the replacement package<br>
</div><div class="gmail_default" style="font-family:verdana,sans-serif"> - allow one-time upload<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"> - permanently add the uploader as a maintainer<br>
</div><div class="gmail_default" style="font-family:verdana,sans-serif"> - permanently switch maintaners to the uploader<br></div><div class="gmail_default" style="font-family:verdana,sans-serif">3) While the package is in this limbo state waiting for a response from the maintainer, put a link to the package at the bottom of the hackage page in a new "suggested replacements" section. In this section, each candidate replacement package is listed, along with its message and how long it's been waiting.<br>
</div><div class="gmail_default" style="font-family:verdana,sans-serif">4) After a bikeshed-long amount of time with no response from the maintainer (I'll suggest 1 month), the package is automatically updated to the suggested version and the package uploader is added as a maintainer.<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 31, 2014 at 11:34 AM, Daniil Frumin <span dir="ltr"><<a>difrumin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think the proposed approach is only reasonable. However, I would<br>
like to stress that in any case it would be better to make sure that<br>
we give the maintainer enough time to respond, e.g.: if the maintainer<br>
is unreachable for a couple of weeks at least<br>
<div><div><br>
On Fri, Jan 31, 2014 at 1:04 PM, Erik Hesselink <<a>hesselink@gmail.com</a>> wrote:<br>
> On Fri, Jan 31, 2014 at 3:15 AM, Roman Cheplyaka <<a>roma@ro-che.info</a>> wrote:<br>
>> * Erik de Castro Lopo <<a>mle+hs@mega-nerd.com</a>> [2014-01-31 09:22:36+1100]<br>
>>> I really can understand why you did this; I am frustrated by some of<br>
>>> the same issues. However, I think if any significant number of people<br>
>>> did this, the results could easily be disasterous.<br>
>><br>
>> Agreed. Maybe we need those disasterous results to realize that the<br>
>> current process is bad and come up with a better one. Or maybe it's just<br>
>> me, and everyone else is happy (enough) with the process, so nothing<br>
>> will happen.<br>
><br>
> That's a rather fatalist attitude, and also one that is not warranted<br>
> given the replies in this thread. Let me try to be more constructive<br>
> instead:<br>
><br>
> I propose to make the trustees group able to upload any package, with<br>
> the understanding that they only do so to make packages where the<br>
> maintainer is unreachable compile on more compilers or with more<br>
> versions of dependencies. The newly uploaded version should have a<br>
> public repository of the forked source available and listed in the<br>
> cabal file. The process would then be:<br>
><br>
> * User fixes a package, emails the maintainer.<br>
> * No response: User emails trustees.<br>
> * Trustees check the above conditions, and upload the new version.<br>
><br>
> This is more lightweight that the process to take over maintainership,<br>
> and it can be, because we're not trusting a random user with a random<br>
> package. Instead, we're only trusting a fixed set of maintainers and a<br>
> small, publicly visible change. Because of this, the waiting times for<br>
> non-responsiveness can probably also be shorter than in the maintainer<br>
> take-over process.<br>
><br>
> Would this alleviate the frustration, while at the same time<br>
> maintaining enough security and sense of package ownership?<br>
><br>
> Regards,<br>
><br>
> Erik<br>
> _______________________________________________<br>
> Haskell-Cafe mailing list<br>
> <a>Haskell-Cafe@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
Sincerely yours,<br>
-- Daniil<br>
</font></span><div><div>_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a>Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Clark.<br><br><span style="font-family:courier new,monospace"><span style="color:rgb(153,153,153)"><font size="1">Key ID : 0x78099922<br>Fingerprint: B292 493C 51AE F3AB D016 DD04 E5E3 C36F 5534 F907</font></span></span></div>
</div>
</blockquote>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Clark.<br><br><span style="font-family:courier new,monospace"><span style="color:rgb(153,153,153)"><font size="1">Key ID : 0x78099922<br>Fingerprint: B292 493C 51AE F3AB D016 DD04 E5E3 C36F 5534 F907</font></span></span></div>
</div>