For what it's worth, I also have a fork of lambdabot[1] I've been using for quite a while now, which may provide a cleaner starting point. In particular, it updates the plugin and command API to be (IMO) quite a bit cleaner and easier to use and understand. It could probably use some attention to security in the eval module (I've relaxed it quite a bit because I only run it on a private IRC server), but it also includes a lot of fixes and updates to other modules.
[1] https://github.com/mokus0/lambdabot
On Feb 19, 2013, at 2:00 AM, Jan Stolarek
I'm happy to hear your approval.
I've spent some time yesterday cleaning up the code and writing down all things that do not work. The list I made is avaliable on github:
https://github.com/killy9999/lambdabot/issues
There are 17 open issues at the moment and I know I will not have enough time to resolve all of them on my own. There are a few blockers, so the current code is definitely not yet suitable for any kind of release.
With all that said I would appreciate help of the community :-) There's a lot to do and the tasks vary in difficulty: from updating documentation and fixing unused imports to fixing exceptions. If anyone is willing to help please contact me via email or comments on github.
Janek
P.S. The development is done in the 'upstream' branch
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe