-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project alive? #33
Comments
Only slightly. We have been taking pull requests, but development has stopped. I'm considering re-coding it in Python, when I get the chance. |
I am willing to contribute to the project. I've tried all the other major bots out there, but love the small code base of the bot! I've just implemented IDENTIFY to identify the bot to Freenode and I am planning on to implement more (personal) features in the coming weeks. Why rewriting it to Pyton? PHP is simple and effective enough imo. |
The changes myself and Hosh made still haven't been pulled into this version so I would say that on pogo's end the project is dead, however my repository contains newer code and locally I have completely changed the way the bot runs. On my end it now runs as two PHP processes which communicate via a UNIX socket. Once I get round to tidying my code up (and sorting out a couple of issues to do with state transfer) I will push my changes as a new branch onto my repo. |
@ElvenSpellmaker, right. I have forked pogo's repo but maybe I should fork yours then? |
Yeah, if @super3 is going to be recoding it in python then it's probably best you did fork mine instead. My code fixes a few bugs and oddities some of them mentioned on this repo, has a method that allows plug-ins to serialise/unserialise all at once (the serialisation and unserialisation (remember) need to be implemented by you in the Command or Listener), the bot also contains some re-factoring (although not all we'd like), a new way of accessing data for commands and listeners (with the old methods still being there for the time being), passwords for channels and server password and a couple of other bits and pieces. I'd say you'd get more updates from mine, although recently I've been slacking on its development because of my Master's exams and then after that I have my dissertation to do, but the project is definitely not dead from my perspective. (I think it's a good idea and I don't want it to die!) |
Did you fix the injection bug? |
What is the best way to implement plugins? |
Do we have an IRC channel in which we can discuss further about the bot? |
#wildphp on freenode? |
yeah, was empty yesterday :) |
And now it has two people. |
Yeah I used to be in the room for a while, nothing much was said at the time and so after I accidentally killed my screen session I didn't re-join. I can re-join again if needed. =) @super3 Which injection bug is this? I'll take a look if it's still there. |
See #10 |
Yeah sorry this project was a "fork" of @super3 IRC-Bot on http://wildphp.com/wildphp-irc-bot I wrote the Bot to learn the principles of OOP and Namespaces and to learn how to write a small "Framework". I hope I find some more time in the near future, but no promises. I've some more projects so I try to put all into the small time box I've. There are some forks with further development like @ElvenSpellmaker wrote. Here is an overview: https://github.com/pogosheep/IRC-Bot/network Perhaps someone can help me to do the pull requests? Cause I'm not familiar with this stuff and even Git is not my main skill. (I prefer Mercurial) |
@pogosheep See this. https://help.github.com/articles/using-pull-requests |
Is this project still being maintained?
The text was updated successfully, but these errors were encountered: