[Haskell-cafe] Looking for maintainers or comaintainers on my Haskell projects

Wojciech Danilo wojciech.danilo at gmail.com
Wed Mar 1 02:29:17 UTC 2017

Chris, first of all, I'm sorry to hear about your problems and I hope 
you'll be getting better. Thank you for your input in Haskell community, we 
all know your libraries.
I'd love to be co-maintainer of path package. I use it extensively and was 
already planning to make some pull requests (allowing for example for env 
variables expansion).

All the best and thank you once again!

W dniu wtorek, 28 lutego 2017 18:21:18 UTC+1 użytkownik Christopher Done 
> Hi all,
> The short version is: I’ve been battling RSI in my fingers for some years. 
> I’m doing various things to mitigate that problem, but I have very limited 
> finger bandwidth these days; enough to work at my usual pace at my job, but 
> not much in the evenings and weekends, and so I can’t manage to do much on 
> my hobby projects. I’m also not as motivated these days to work on my set 
> of open source projects, and am turning my attention to different things. 
> It’s not great, but that’s life.
> I don’t think that the users of my packages are getting the best 
> maintainership deal. Rather than be “the absentee maintainer”, I’d prefer a 
> straight-forward transition of maintainership or ownership to someone who 
> can put the right energy and time in.
> In terms of packages, there are really two that have a significant 
> maintenance burden and users aren’t being served very well:
>    - HIndent <https://github.com/chrisdone/hindent> has a significant 
>    amount of issues opened for it regularly, and many of them require 
>    discussion and debate. If someone would like to become a co-maintainer, let 
>    me know. It may (eventually) make sense to move it to a more general GitHub 
>    organization like commercialhaskell or haskell. 
>    - Intero <https://github.com/commercialhaskell/intero/issues>, which 
>    seems to have been a success, has a pretty big maintenance burden on “this 
>    doesn’t work” kind of issues which require investigation. There’s some 
>    Emacs Lisp work to do on it, and some Haskell work on the intero binary, 
>    and a whole lot of platform-specific problems or tooling not working 
>    together. On the other hand people really like this project, and there’s a 
>    lot of tooling potential. 
> If you want to take xeno <https://github.com/chrisdone/xeno> and make it 
> into a publishable package, please do so.
> The rest of my projects that are on Stackage are: labels 
> <https://hackage.haskell.org/package/labels>, ace 
> <https://hackage.haskell.org/package/ace>, ical 
> <https://hackage.haskell.org/package/ical>, check-email 
> <https://hackage.haskell.org/package/check-email>, freenect 
> <https://hackage.haskell.org/package/freenect>, frisby 
> <https://hackage.haskell.org/package/frisby>, gd 
> <https://hackage.haskell.org/package/gd>, ini 
> <https://hackage.haskell.org/package/ini>, lucid 
> <https://hackage.haskell.org/package/lucid>, osdkeys 
> <https://hackage.haskell.org/package/osdkeys>, pdfinfo 
> <https://hackage.haskell.org/package/pdfinfo>, present 
> <https://hackage.haskell.org/package/present>, pure-io 
> <https://hackage.haskell.org/package/pure-io>, scrobble 
> <https://hackage.haskell.org/package/scrobble>, shell-conduit 
> <https://hackage.haskell.org/package/shell-conduit>, sourcemap 
> <https://hackage.haskell.org/package/sourcemap>, descriptive 
> <https://hackage.haskell.org/package/descriptive>, wrap 
> <https://hackage.haskell.org/package/wrap>, path 
> <https://hackage.haskell.org/package/path>, weigh 
> <https://hackage.haskell.org/package/weigh>, haskell-docs 
> <https://hackage.haskell.org/package/haskell-docs>, and 
> structured-haskell-mode 
> <https://hackage.haskell.org/package/structured-haskell-mode>. If you’re 
> interested in taking over or co-maintaining any of them, let me know. Some 
> are interesting, others are boring, some are trivial.
> I have other packages on Hackage, but they’re mostly dead or experiments 
> that don’t need maintenance anyway.
> I’ve started the process of adding or changing maintainers on my public 
> services:
>    - Haskell News <https://github.com/haskellnews> is now a GitHub 
>    organization. Luke Murphy is a co-owner, and has full access to the 
>    DigitalOcean account that is running the service. So if you want to work on 
>    that project, I’m not in the way. 
>    - lpaste <https://github.com/lpaste/lpaste> has been moved to its own 
>    DigitalOcean account too. If anyone is interested in taking over the 
>    project or co-running it, let me know. 
>    - tryhaskell <https://github.com/chrisdone/tryhaskell> doesn’t really 
>    require any maintenance, but it’s also on its own DigitalOcean account now 
>    too. 
>    - IRCBrowse <https://github.com/chrisdone/ircbrowse> is now on its own 
>    DigitalOcean account too. It requires maintenance once in a while. If 
>    anyone is interested in taking over the project or co-running it, let me 
>    know. 
> Cheers!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20170228/8e4fe19e/attachment.html>

More information about the Haskell-Cafe mailing list