I'm looking for someone who would like to maintain Hammer.js. Unfortunately I just don't have enough time left for the project due a new job, and don't have use the library myself these days.
Requirements of a new maintainer should be that he is aware of the impact of the changes, since the project is being used in quite a lot of websites/apps. It has almost 10K stars, so it comes with some responsibility.
Some of the key features of Hammer;
- Speed; Hammer is being called on every mouse/touch-move, so keep the code as simple as possible
- Clean of overhead/sugar; To keep the library small and focused, I dont'want all kinds of small additions to support X feature for some edge cases. Hammer is/should be quite modular so some hooks are fairly easy to implement.
- Small minified filesize.
- No dependencies.
If you are interested, and can find yourself in the points above, please contact me!
https://twitter.com/jorikdelaporik
I'm looking for someone who would like to maintain Hammer.js. Unfortunately I just don't have enough time left for the project due a new job, and don't have use the library myself these days.
Requirements of a new maintainer should be that he is aware of the impact of the changes, since the project is being used in quite a lot of websites/apps. It has almost 10K stars, so it comes with some responsibility.
Some of the key features of Hammer;
If you are interested, and can find yourself in the points above, please contact me!
https://twitter.com/jorikdelaporik