Hi Johan and Alexey,
I'll volunteer to be a comaintainer with Alexey on this package. Since the majority of upper bound bug reports will likely come from the Stackage team anyway, I won't mind making those maintenance releases. And I agree completely with keeping this package in an all-but-frozen API state.Does that sound like a reasonable setup to both of you?MichaelOn Wed, Apr 8, 2015 at 12:39 PM Alexey Shmalko <rasen.dubi@gmail.com> wrote:Hi, Johan,I have a little spare time and would be interested in taking over maintenance of network-uri.However I'm not sure if I'm a right person for that. I've never maintained any haskell package before, but would be glad to. I'm experienced with maintenance issues applied to C/C++ but not Haskell. However, I'm sure they are pretty much the same.I looked through github issues; as far as I understand, the maintainer's responsibilities are tracking things work fine with newer versions of dependencies, fixing bugs that doesn't break source-level compatibility and rejecting other proposals. I believe I would handle this.Regards,Alexey_______________________________________________On Wed, Apr 8, 2015 at 12:18 AM, Johan Tibell <johan.tibell@gmail.com> wrote:Hi!I find myself with less time to hack lately and I'm trying to reduce the number of libraries I maintain so I can invest time in new things. Would anyone be interested taking over maintenance of network-uri?It should not be much work at all. Bump a few dependencies and fix a bug or two. The package is very widely used so I suggest that the new maintainer should avoid breaking changes whenever possible*.* In other words, if you want to completely rethink network URI handling, this package is probably not the place for it.-- Johan
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe