<div dir="ltr">Hi cafe,<div><br></div><div>It's been for quite a while and there's no version upgrade of this package, may I ask to take maintainer ship of this package?</div><div><br></div><div>Regards</div><div>baojun</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, May 16, 2014 at 2:04 AM Markus Läll <<a href="mailto:markus.l2ll@gmail.com">markus.l2ll@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">I would argue *for* forking. Hackage is big and consists of many packages which have only a few users, or maybe just one -- the author. I don't see all these packages if I don't go on the page and look. But when I do, I will be looking for *them*. If some popular package stops working then I would be happy to find a fork, because now I can just tell cabal about it. And if the original gets fixed, I can go back. I don't think people who fork are looking for aquiring yet another package to maintain forever, or to take it over. <div class="gmail_msg">
<br class="gmail_msg"></div></div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"></div></div><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg">On Thu, May 15, 2014 at 11:18 AM, Sven Panne <span dir="ltr" class="gmail_msg"><<a href="mailto:svenpanne@gmail.com" class="gmail_msg" target="_blank">svenpanne@gmail.com</a>></span> wrote:<br class="gmail_msg">
</div></div><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2014-05-15 9:30 GMT+02:00 Roman Cheplyaka <<a href="mailto:roma@ro-che.info" class="gmail_msg" target="_blank">roma@ro-che.info</a>>:<br class="gmail_msg">
<div class="gmail_msg">> If there's no response, then you have two choices:<br class="gmail_msg">
<br class="gmail_msg">
</div>Actually three: Fix things locally until the "official" package is fixed.<br class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
> * request package maintainership, which will take several weeks<br class="gmail_msg">
<br class="gmail_msg">
</div>I really hope that this will take months, not weeks, see the other discussion<br class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
> * fork the package (i.e. upload your patched version to hackage under a<br class="gmail_msg">
> different name)<br class="gmail_msg">
<br class="gmail_msg">
</div>This proposal worries me quite a bit, because if everybody follows<br class="gmail_msg">
that advice, it will turn Hackage into a chaotic collection of<br class="gmail_msg">
packages with various degrees of being fixed/maintained/etc. Imagine a<br class="gmail_msg">
package 'foo', which needs a fix, and several pepole think it's a good<br class="gmail_msg">
idea to fork and fix the issue at hand. Now we have 'foo', 'foo-XY',<br class="gmail_msg">
'foo-my-cool-acronym', ... Of course people normally have no incentive<br class="gmail_msg">
to really take over maintainership for 'foo', they just want a working<br class="gmail_msg">
'foo' right now for their own project. Later the real maintainer<br class="gmail_msg">
re-appears after vacation/sabbatical/whatever, fixes 'foo', and<br class="gmail_msg">
continues to work on it, adding new features. Now somebody new comes<br class="gmail_msg">
to Hackage to see if there is already a package for some use case, and<br class="gmail_msg">
finds 'foo', 'foo-XY', 'foo-my-cool-acronym', ... Then it takes some<br class="gmail_msg">
non-trivial detective work to find out which packages are actually<br class="gmail_msg">
dead (again) and which is the real one. => Chaos IMHO.<br class="gmail_msg">
<br class="gmail_msg">
In a nutshell: If you are really in a hurry, fix things locally.<br class="gmail_msg">
Hackage is not the place to fork like hell.<br class="gmail_msg"></blockquote></div></div><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
_______________________________________________<br class="gmail_msg">
Haskell-Cafe mailing list<br class="gmail_msg">
<a href="mailto:Haskell-Cafe@haskell.org" class="gmail_msg" target="_blank">Haskell-Cafe@haskell.org</a><br class="gmail_msg">
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" class="gmail_msg" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br class="gmail_msg">
</blockquote></div></div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><br clear="all" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div>-- <br class="gmail_msg">Markus Läll<br class="gmail_msg">
</div>
_______________________________________________<br class="gmail_msg">
Haskell-Cafe mailing list<br class="gmail_msg">
<a href="mailto:Haskell-Cafe@haskell.org" class="gmail_msg" target="_blank">Haskell-Cafe@haskell.org</a><br class="gmail_msg">
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" rel="noreferrer" class="gmail_msg" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br class="gmail_msg">
</blockquote></div>