Project Maintenance

[blakeembrey]

Hi @rs! I noticed you don't have a lot of time to maintain this project. I'd love to step in and help out, I'm currently using it in a work project and would like to make it more re-usable as well as add some new features. Let me know if you want help maintaining pushd and if you're happy for me to help, what sort of changes I should or shouldn't make (e.g. language, new event parameters, etc). You can also get in touch with me via email (on my GitHub profile) if you'd like to chat.

[rs]

Sure let's try this. There is a lot tickets and PR to handle if have the courage. I will add you as a maintainer.

[blakeembrey]

Thanks @rs! When you get the chance can you add me to https://www.npmjs.com/package/pushd too? Here's my list of initial things I'd like to do (let me know if there's something you'd like to change):

• Ability to post to multiple event namespaces (a la Post events #155)
• Create a bin CLI so it can be installed and run from CLI (including config file)
• Export the server from the node module (would allow users to mount the app within another app)
• Publish to NPM as compiled assets
• How do you feel about keeping in CoffeeScript (this one I'm happy to keep and probably wouldn't get to for a long while anyway, but I personally prefer the type safety from TypeScript lately)?
• Consider multiple environment configuration from a single server instance (may be unnecessary if the CLI/exports are improved as you could just mount it multiple times instead)

[rs]

Ok on all points. Regarding CoffeeScript, if I would have to choose it today, I would also prefer TypeScript over it.