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

This repo is active? #80

Open
PikachuEXE opened this issue Oct 28, 2013 · 14 comments
Open

This repo is active? #80

PikachuEXE opened this issue Oct 28, 2013 · 14 comments

Comments

@PikachuEXE
Copy link

If author is too busy please add some maintainers

@PikachuEXE
Copy link
Author

Still no response...

@zamber
Copy link

zamber commented Jan 13, 2014

Yeah, it's dead. Tweeted Keith, maybe we will get a response.

The code is on MIT so with some work we could mockup a new gh page and add the pull requests hanging here to resolve the issues selectivizr has now.

@PikachuEXE
Copy link
Author

Tweeted also.
If no response in 1 week then we can start to figure out how to work on it
But I got a forked library to handle already, not sure if got time as a maintainer (might help reading small PR)

@zamber
Copy link

zamber commented Jan 14, 2014

I'm also unsure if I have enough time for maintaining though I have to support IE8 and in the process figure out what other issues I can hit when using selectivizr.

Nevertheless, despite the circumstances a call for maintainers is not a big commitment as you noted ;).

https://github.com/keithclark/selectivizr/network last activity from 3 days ago so it's pretty much alive.

@brgrz
Copy link

brgrz commented Jan 31, 2014

Was there any kind of reply to your tweets? Since it's not moving on we should consider moving it to a new repo and set up a few maintainers where each one would contribute as much time as one had, it would be a huge improvement to what we have now.

@zamber
Copy link

zamber commented Jan 31, 2014

I didn't get a response but keithclark is alive showed some activity (see the rederenced pull request above).

We can always implement fixes, make pull requests and see how things go.

@brgrz
Copy link

brgrz commented Jan 31, 2014

well apparently the pull request don't get accepted and merged in, there's already quite a few of them, so making more doesn't make sense if they don't get merged

@stevenvachon
Copy link

I tweeted him a short while ago regarding two important PRs. One he ignored and the other he provided a good explanation.

@PikachuEXE
Copy link
Author

@stevenvachon If he going to maintain this project?
That's what I want to know the most. :)

@keithclark
Copy link
Owner

@brgrz I'll happily merge PR's if they contain tests that identify the issue and prove the fix. For almost every open PR I have to checkout the branch and try to recreate the issue locally before I can be confident of merging.

@stevenvachon I answered both your queries on twitter.

@zamber of course you can do that, that's the beauty of open source. If you'd like to create a break-away repo and merge these PR's yourself, please do.

@stevenvachon
Copy link

@keithclark Ah, yes, you're right; I'd forgotten. Have you decided on a package manager?

@PikachuEXE
Copy link
Author

Bower?

@stevenvachon
Copy link

It's probably not going to happen.

@jpdevries
Copy link

What is the objection to bower?

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

6 participants