Looking for maintainers or comaintainers on my Haskell projects

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!

I'm interested in co-maintaining path and ini
On Tue, Feb 28, 2017 at 9:18 AM, 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 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, 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels, ace, ical, check-email, freenect, frisby, gd, ini, lucid, osdkeys, pdfinfo, present, pure-io, scrobble, shell-conduit, sourcemap, descriptive, wrap, path, weigh, haskell-docs, and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Hi!
I'd like to become co-maintainer of "path" which I already know a bit. I
have also started watching a few of your other packages on GitHub.
I'm also in favour of moving "hindent" into the "commercialhaskell"
organization.
Thanks for creating all these packages in the first place!
Simon
2017-02-28 18:18 GMT+01:00 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Thanks for making all there libraries! I use lucid extensively and could help maintaining it
On 28 Feb 2017, at 19.18, Christopher Done
wrote: 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 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, 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels, ace, ical, check-email, freenect, frisby, gd, ini, lucid, osdkeys, pdfinfo, present, pure-io, scrobble, shell-conduit, sourcemap, descriptive, wrap, path, weigh, haskell-docs, and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

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! Wojciech W dniu wtorek, 28 lutego 2017 18:21:18 UTC+1 użytkownik Christopher Done napisał:
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!

Thanks for your effort. I'm interested in co-maintaining "shell-conduit"
and "check-email".
Regards,
Sibi
On Tue, Feb 28, 2017 at 10:48 PM, 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
-- Sibi, sibi@psibi.in Software Engineer @ Inkmonk, Twitter/github/identi.ca: psibi GPG Fingerpint: A241 B3D6 F4FD D40D D7DE B1C6 D19E 3E0E BB55 7613 Registered Linux User ID: 534664

And here I was thinking I was already the maintainer of haskell-docs... ;-)
I'd like to help with structured-haskell-mode, but my elisp-fu is
unsufficient :(
On 1 March 2017 at 04:18, 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 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, 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels, ace, ical, check-email, freenect, frisby, gd, ini, lucid, osdkeys, pdfinfo, present, pure-io, scrobble, shell-conduit, sourcemap, descriptive, wrap, path, weigh, haskell-docs, and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com

Thank you everyone for the support! I've received a number of offers of
help which I'll be pursuing immediately. :-)
On 28 February 2017 at 17:18, 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!

On March 1, 2017 at 5:17:21 AM, Christopher Done (chrisdone@gmail.com) wrote:
Thank you everyone for the support! I've received a number of offers of help which I'll be pursuing immediately. :-)
Has anyone offered to help with tryhaskell.org? And, if not, would anyone like to? :-) There are a few tickets in the haskell repo pertaining to it, so it would probably be good to share the work around a bit to keep the machine humming in decent shape. Thanks for your work on all these resources for all these years Chris, and thanks for being proactive about transition of maintainership. Cheers, Gershom
On 28 February 2017 at 17:18, Christopher Done wrote:
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 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 , 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels , ace , ical , check-email , freenect , frisby , gd , ini , lucid , osdkeys , pdfinfo , present , pure-io , scrobble , shell-conduit , sourcemap , descriptive , wrap , path , weigh , haskell-docs , and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. - 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Two people offered to help on tryhaskell maintenance. They now have ssh
access and commit access! =)
On 14 March 2017 at 20:51, Gershom B
On March 1, 2017 at 5:17:21 AM, Christopher Done (chrisdone@gmail.com) wrote:
Thank you everyone for the support! I've received a number of offers of help which I'll be pursuing immediately. :-)
Has anyone offered to help with tryhaskell.org? And, if not, would anyone like to? :-)
There are a few tickets in the haskell repo pertaining to it, so it would probably be good to share the work around a bit to keep the machine humming in decent shape.
Thanks for your work on all these resources for all these years Chris, and thanks for being proactive about transition of maintainership.
Cheers, Gershom
On 28 February 2017 at 17:18, Christopher Done wrote:
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 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 , 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels , ace , ical , check-email , freenect , frisby , gd , ini , lucid , osdkeys , pdfinfo , present , pure-io , scrobble , shell-conduit , sourcemap , descriptive , wrap , path , weigh , haskell-docs , and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. - 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Great!
It seems that the issue tracker on
https://github.com/tryhaskell/tryhaskell is disabled? I wanted to
create a ticket to reference
https://github.com/haskell-infra/hl/issues/203
but couldn't see how.
Cheers,
Gershom
On Wed, Mar 15, 2017 at 10:32 AM, Christopher Done
Two people offered to help on tryhaskell maintenance. They now have ssh access and commit access! =)
On 14 March 2017 at 20:51, Gershom B
wrote: On March 1, 2017 at 5:17:21 AM, Christopher Done (chrisdone@gmail.com) wrote:
Thank you everyone for the support! I've received a number of offers of help which I'll be pursuing immediately. :-)
Has anyone offered to help with tryhaskell.org? And, if not, would anyone like to? :-)
There are a few tickets in the haskell repo pertaining to it, so it would probably be good to share the work around a bit to keep the machine humming in decent shape.
Thanks for your work on all these resources for all these years Chris, and thanks for being proactive about transition of maintainership.
Cheers, Gershom
On 28 February 2017 at 17:18, Christopher Done wrote:
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 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 , 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels , ace , ical , check-email , freenect , frisby , gd , ini , lucid , osdkeys , pdfinfo , present , pure-io , scrobble , shell-conduit , sourcemap , descriptive , wrap , path , weigh , haskell-docs , and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. - 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

I'm happy taking over freenect for now.
Ivan
On 1 March 2017 at 10:13, Christopher Done
Thank you everyone for the support! I've received a number of offers of help which I'll be pursuing immediately. :-)
On 28 February 2017 at 17:18, Christopher Done
wrote: 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Hi Christopher,
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.
Sorry to read that. Thank you for all of your contributions!
I have other packages on Hackage, but they’re mostly dead or experiments that don’t need maintenance anyway.
As a heavy user of the foreign-store package I wouldn't mind comaintaining or even maintaining it. It's the key dependency of Rapid. My Hackage username is 'esz', my GitHub username is 'esoeylemez'. Greets ertes

I'm willing to take over the maintenance of frisby, as I already have some experience with parser combinator libraries. On 2017-02-28 12:18 PM, Christopher Done wrote:
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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Am 02.03.2017 um 23:15 schrieb Mario Blažević:
I'm willing to take over the maintenance of frisby, as I already have some experience with parser combinator libraries.
It has been a while since I looked at frisby. I do remember that I had several issues with it and found that the code was pretty hard to understand, due to numerous unsafe optimization hacks. I'd be glad if someone cleaned that up, so that it becomes easier to fix errors but I guess that would be a piece of work, probably amounting to a re-write of sorts. (To be clear, none of this is Chris' fault, of course, he just updated cabal stuff.) Cheers Ben

On 04/03/17 01:04 PM, Ben Franksen wrote:
Am 02.03.2017 um 23:15 schrieb Mario Blažević:
I'm willing to take over the maintenance of frisby, as I already have some experience with parser combinator libraries.
It has been a while since I looked at frisby. I do remember that I had several issues with it and found that the code was pretty hard to understand, due to numerous unsafe optimization hacks. I'd be glad if someone cleaned that up, so that it becomes easier to fix errors but I guess that would be a piece of work, probably amounting to a re-write of sorts. (To be clear, none of this is Chris' fault, of course, he just updated cabal stuff.)
I suppose the first order of business would then be to write a test and benchmark suite, to make sure that the modifications don't break something. Mind you, there are no dependencies for the library (apart from acme-everything of course). Is anybody using it privately?

I'm not sure that anyone's using it. I originally found it on John
Meacham's web site and offered to push it to Hackage. It hasn't been
touched since. I once decided to sit down and modernize it, but realized I
don't actually understand any of the laziness tricks in it.
Anybody's welcome to pick it up and take it to the cleaners!
On 5 March 2017 at 23:29, Mario Blažević
On 04/03/17 01:04 PM, Ben Franksen wrote:
Am 02.03.2017 um 23:15 schrieb Mario Blažević:
I'm willing to take over the maintenance of frisby, as I already have some experience with parser combinator libraries.
It has been a while since I looked at frisby. I do remember that I had several issues with it and found that the code was pretty hard to understand, due to numerous unsafe optimization hacks. I'd be glad if someone cleaned that up, so that it becomes easier to fix errors but I guess that would be a piece of work, probably amounting to a re-write of sorts. (To be clear, none of this is Chris' fault, of course, he just updated cabal stuff.)
I suppose the first order of business would then be to write a test and benchmark suite, to make sure that the modifications don't break something. Mind you, there are no dependencies for the library (apart from acme-everything of course). Is anybody using it privately?
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

On 2017-03-15 10:20 AM, Christopher Done wrote:
I'm not sure that anyone's using it. I originally found it on John Meacham's web site and offered to push it to Hackage. It hasn't been touched since. I once decided to sit down and modernize it, but realized I don't actually understand any of the laziness tricks in it.
I'm comfortable with laziness tricks, somewhat less so with "numerous unsafe optimization hacks".
Anybody's welcome to pick it up and take it to the cleaners!
Ok, I'll take it. My GitHub account is blamario. I don't suppose John Meacham would be interested?
On 5 March 2017 at 23:29, Mario Blažević
mailto:blamario@ciktel.net> wrote: On 04/03/17 01:04 PM, Ben Franksen wrote:
Am 02.03.2017 tel:02.03.2017 um 23:15 schrieb Mario Blažević:
I'm willing to take over the maintenance of frisby, as I already have some experience with parser combinator libraries.
It has been a while since I looked at frisby. I do remember that I had several issues with it and found that the code was pretty hard to understand, due to numerous unsafe optimization hacks. I'd be glad if someone cleaned that up, so that it becomes easier to fix errors but I guess that would be a piece of work, probably amounting to a re-write of sorts. (To be clear, none of this is Chris' fault, of course, he just updated cabal stuff.)
I suppose the first order of business would then be to write a test and benchmark suite, to make sure that the modifications don't break something. Mind you, there are no dependencies for the library (apart from acme-everything of course). Is anybody using it privately?
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

Am 15.03.2017 um 17:15 schrieb Mario Blažević:
On 2017-03-15 10:20 AM, Christopher Done wrote:
I'm not sure that anyone's using it. I originally found it on John Meacham's web site and offered to push it to Hackage. It hasn't been touched since. I once decided to sit down and modernize it, but realized I don't actually understand any of the laziness tricks in it.
I'm comfortable with laziness tricks, somewhat less so with "numerous unsafe optimization hacks".
Anybody's welcome to pick it up and take it to the cleaners!
Ok, I'll take it. My GitHub account is blamario. I don't suppose John Meacham would be interested?
I am glad my remark didn't scare you off, in retrospect my wording was perhaps a bit strong. Yes, John did a lot to make things as lazy as possible to avoid excessive memory consumption (cool to say that, isn't it). There is also some ugly type casting (unsafeCoerce) going on, since the parser keeps the alternatives in an array (remember that this is a packrat parser). Unfortunately I can't spare the time to work on this ATM. But I would be glad if you would revive the project. PEGs offer some unique advantages for day-to-day parsing tasks, where you can't be bothered to write a separate lexer or mess around with 'try' until your harmless looking grammar actually accepts the source language. A fair portion of these can nowadays be handled nicely with regex-applicative (many file formats are actually regular) but now and again there is one where you need the power of a CFG. Cheers Ben

On 2017-03-16 05:26 PM, Ben Franksen wrote:
I am glad my remark didn't scare you off, in retrospect my wording was perhaps a bit strong. Yes, John did a lot to make things as lazy as possible to avoid excessive memory consumption (cool to say that, isn't it). There is also some ugly type casting (unsafeCoerce) going on, since the parser keeps the alternatives in an array (remember that this is a packrat parser).
I should be able to replace the array with a user-defined record, I submitted a paper to this year's ICFP demonstrating this. The only problem would be backward compatibility, but if there are no current users there's no problem.
Unfortunately I can't spare the time to work on this ATM. But I would be glad if you would revive the project. PEGs offer some unique advantages for day-to-day parsing tasks, where you can't be bothered to write a separate lexer or mess around with 'try' until your harmless looking grammar actually accepts the source language. A fair portion of these can nowadays be handled nicely with regex-applicative (many file formats are actually regular) but now and again there is one where you need the power of a CFG.
We're on the same page here. I have a solution in mind that would allow one to choose a parsing algorithm, from Parsec-style to Packrat to parallel-parsing CFGs, and apply it to a single grammar specification written with little syntactic overhead compared to Parsec. Some of it is written up, some half-implemented.

Am 17.03.2017 um 15:27 schrieb Mario Blažević:
On 2017-03-16 05:26 PM, Ben Franksen wrote:
I am glad my remark didn't scare you off, in retrospect my wording was perhaps a bit strong. Yes, John did a lot to make things as lazy as possible to avoid excessive memory consumption (cool to say that, isn't it). There is also some ugly type casting (unsafeCoerce) going on, since the parser keeps the alternatives in an array (remember that this is a packrat parser).
I should be able to replace the array with a user-defined record, I submitted a paper to this year's ICFP demonstrating this.
That sounds interesting. Looking forward to read that.
The only problem would be backward compatibility, but if there are no current users there's no problem.
Unfortunately I can't spare the time to work on this ATM. But I would be glad if you would revive the project. PEGs offer some unique advantages for day-to-day parsing tasks, where you can't be bothered to write a separate lexer or mess around with 'try' until your harmless looking grammar actually accepts the source language. A fair portion of these can nowadays be handled nicely with regex-applicative (many file formats are actually regular) but now and again there is one where you need the power of a CFG.
We're on the same page here. I have a solution in mind that would allow one to choose a parsing algorithm, from Parsec-style to Packrat to parallel-parsing CFGs, and apply it to a single grammar specification written with little syntactic overhead compared to Parsec. Some of it is written up, some half-implemented.
My gut feeling would be so say that this can't work because they all build on a different (though /almost/ the same) set of primitives. For instance, IIRC the semantics of 'many' differs in subtle ways between implementations (greedy vs. maximum munch -- but don't ask me about the details its been a while since I studied these things). Cheers Ben

Did anyone offer to take over ircbrowse? its currently failing as per: https://github.com/chrisdone/ircbrowse/issues/27 Cheers, Gershom On February 28, 2017 at 12:22:26 PM, Christopher Done (chrisdone@gmail.com) wrote:
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 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 , 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 and make it into a publishable package, please do so.
The rest of my projects that are on Stackage are: labels , ace , ical , check-email , freenect , frisby , gd , ini , lucid , osdkeys , pdfinfo , present , pure-io , scrobble , shell-conduit , sourcemap , descriptive , wrap , path , weigh , haskell-docs , and 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 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 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 doesn’t really require any maintenance, but it’s also on its own DigitalOcean account now too. - 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!
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.
participants (13)
-
Ben Franksen
-
Christopher Done
-
Ertugrul Söylemez
-
Gershom B
-
Ivan Lazar Miljenovic
-
Ivan Perez
-
Joe Hillenbrand
-
Mario Blažević
-
Mario Blažević
-
Oleg Grenrus
-
Sibi
-
Simon Jakobi
-
Wojciech Danilo