Hi,<br><br>Are there any news how things are going? What remains there to be done to get us to Hackage 2? <br><br>I found this list of tickets: <a href="https://github.com/haskell/cabal/issues?labels=hackage2&page=1&state=open">https://github.com/haskell/cabal/issues?labels=hackage2&page=1&state=open</a><br>
<br>Is there anything more to be done?<br><br>Best regards,<br>Krzysztof Skrzętnicki<br><br><div class="gmail_quote">On Tue, Feb 14, 2012 at 12:44 AM, Ben Gamari <span dir="ltr"><<a href="mailto:bgamari.foss@gmail.com" target="_blank">bgamari.foss@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey all,<br>
<br>
Those of you who follow the Haskell subreddit no doubt saw today's post<br>
regarding the status of Hackage 2. As has been said many times in the<br>
past, the primary blocker at this point to the adoption of Hackage 2<br>
appears to be the lack of an administrator.<br>
<br>
It seems to me this is a poor reason for this effort to be held<br>
up. Having taken a bit of time to consider, I would be willing to put in<br>
some effort to get things moving and would be willing to maintain the<br>
<a href="http://haskell.org" target="_blank">haskell.org</a> Hackage 2.0 instance going forward if necessary.<br>
<br>
I currently have a running installation on my personal machine and<br>
things seem to be working as they should. On the whole, installation was<br>
quite trivial, so it seems likely that the project is indeed at a point<br>
where it can take real use (although a "logout" option in the web<br>
interface would make testing a bit easier).<br>
<br>
That being said, it would in my opinion be silly to proceed without<br>
fixing the Hackage trac. It was taken down earlier this year due to<br>
spamming[1] and it seems the recovery project has been orphaned. I would<br>
be willing to help with this effort, but it seems like the someone more<br>
familiar with the <a href="http://haskel.org" target="_blank">haskel.org</a> infrastructure might be better equipped to<br>
handle the situation.<br>
<br>
It seems that this process will go something like this,<br>
1) Bring Hackage trac back from the dead<br>
2) Bring up a Hackage 2 instance along-side the existing<br>
<a href="http://hackage.haskell.org" target="_blank">hackage.haskell.org</a><br>
3) Enlist testers<br>
4) Let things simmer for a few weeks/months ensuring nothing explodes<br>
5) After it's agreed that things are stable, eventually swap the<br>
Hackage 1 and 2 instances<br>
<br>
This will surely be a non-trivial process but I would be willing to move<br>
things forward.<br>
<br>
Cheers,<br>
<br>
- Ben<br>
<br>
<br>
[1] <a href="http://www.haskell.org/pipermail/cabal-devel/2012-January/008427.html" target="_blank">http://www.haskell.org/pipermail/cabal-devel/2012-January/008427.html</a><br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">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>
</blockquote></div><br>