Fork or PR?

[guyzmo]

Hello,

I have forked your project, and used it as a base for a full blown library that can interact with EPL, using the API (that I have updated for the 1.2.8 API of EPL) or using a Socket.IO client (that I have also hacked). But now, the differences between my fork and your upstream are really important, that's why I'm wondering about the following options:

• would you consider merging my changes with your upstream PyEtherpadLite? Or
• would you prefer to focus your library on API stuff, and let mine exist as a fork and extend this with Socket.IO stuff?
• would you want me to take over PyEtherpadLite development? (and maybe ask the etherpad foundation to host the main repository for this library)

I don't have much preferences on either three options, it mostly depends on how much work you want to put into maintaining that library.