Skip to content
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

Is this library still actively maintained? #1197

Open
e-e-e opened this issue Sep 19, 2018 · 9 comments
Open

Is this library still actively maintained? #1197

e-e-e opened this issue Sep 19, 2018 · 9 comments

Comments

@e-e-e
Copy link

e-e-e commented Sep 19, 2018

There has not been much activity in this repo for the last few months and there are many open issues. Is it still actively maintained?

@runspired
Copy link
Contributor

@e-e-e unfortunately all the maintainers have been quite busy. I had hopes of releasing a new version a few years ago but work took me away from a focus on mobile. I'm happy to help someone new pick up the banner though!

@runspired
Copy link
Contributor

cc @arjunkathuria @arschmitz @jtangelder for visibility.

@jongmoon
Copy link

jongmoon commented Oct 2, 2018

@runspired I'm very happy to see contributor's comment here. I thought it is not active any more.

I sent email or twitter message to @arjunkathuria @arschmitz @jtangelder for asking library's plan
6months ago. but I could not receive any response because we want to contribute and solve issues unresolved.

As if our team had done the following before

We are using hammer.js very tightly in our component (egjs-axes, egjs-flicking and egjs-view360,...). So we've had plan to manage new hammer.js as fork project(https://github.com/naver/hammer.js).

But if this project has plan to activate again. We want to contribute here.

@DavidPeicho
Copy link

It would be a wonderful idea if we could continue to contribute here. There are more than 2K forks, and I am sure a lot of them, like yours @jongmoon, bring a lot. We would need some maintainers for reviewing the PR, and for merging them.

@runspired
Copy link
Contributor

I would be happy to review things, I would also be happy to discuss the plans I had for Hammer 3.x that I never got a chance to pursue. We spiked them but no one had time to drive it at the time.

@ArtemBernatskyy
Copy link

@SampsonCrowley
Copy link

At the very least, we need to add an ES Module build

@squadette
Copy link

I'm going to spend some time on maintaining Hammer.js. Here is the tracking issue that describes my plan of action: squadette#1

Thank you,

@runspired
Copy link
Contributor

@squadette happy to help bring someone in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants