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

MAINTAINED FORK OF SPRINT! 💡 #32

Open
kitten opened this issue May 29, 2015 · 17 comments
Open

MAINTAINED FORK OF SPRINT! 💡 #32

kitten opened this issue May 29, 2015 · 17 comments

Comments

@kitten
Copy link

kitten commented May 29, 2015

Edit: I've set up a fork and will maintain it a.k.a. actually accepting PRs. https://github.com/philplckthun/sprint

I want to keep this short: sprint is a nice experiment to push the limits of DOM manipulation through lighter methods and new browser JavaScript APIs. It's great to have seen this project progress and 3842 stars just can't lie as well.

But contribution to this project will decline (like right now) and eventually stop, when no progress is happening. Like no issues are resolved, no pull requests are merged etc.

If you haven't got the time to maintain this project anymore, @bendc, please consider to add more maintainers.

sad cat

@stephnr
Copy link

stephnr commented May 29, 2015

@philplckthun @bendc , hes right. Some of us want this project to continue. I am still waiting for my PR to be accepted.

@kitten
Copy link
Author

kitten commented May 29, 2015

@Stephn-R I'd also say that we introduced PRs that are crucial for production usage. If sprint wants to be used in real world projects, then we need both testing #31 and npm / cross module support #21

Those PRs are as of now unmerged since nearly a month.

@stephnr
Copy link

stephnr commented May 29, 2015

A month...? Yes, I totally agree on the severity of this.

On Fri, May 29, 2015 at 9:26 AM Phil Plückthun [email protected]
wrote:

@Stephn-R https://github.com/Stephn-R I'd also say that we introduced
PRs that are crucial for production usage. If sprint wants to be used in
real world projects, then we need both testing #31
#31 and npm / cross module support
#21 #21

Those PRs are as of now unmerged since nearly a month.


Reply to this email directly or view it on GitHub
#32 (comment).

@tgabi333
Copy link

tgabi333 commented Jun 4, 2015

+1

@krzksz
Copy link

krzksz commented Jun 4, 2015

How about we move developent to some fork and than merge it if @bendc shows
willingness to continue this repo?
4 cze 2015 13:58 "Gábor Tóth" [email protected] napisał(a):

+1


Reply to this email directly or view it on GitHub
#32 (comment).

@stephnr
Copy link

stephnr commented Jun 4, 2015

I like your idea @krzksz

I volunteer as tribute. Either myself or the top contributor to the project second to @bendc

@far0s
Copy link

far0s commented Jun 4, 2015

I'm probably not skilled enough to help you guys, but I like the idea of Sprint and definitely want to see its development continue ! 👍

@jdcauley
Copy link

jdcauley commented Jun 4, 2015

Agreed

@kofalt
Copy link

kofalt commented Jun 4, 2015

Thoughts on making a sprint org on github, adding interested parties (including @bendc) as org owners?

@generalandrew
Copy link

This is a great idea my body is willing but unfortunately, my javascript mind is weak! Would like to help out where I can.

@kitten
Copy link
Author

kitten commented Jun 5, 2015

Okay, so forking until we can merge it back? Sounds okay to me

I volunteer to do it.

@rossPatton
Copy link

I've been working on an alternative that's modular and npm friendly because I saw how nothing was happening with the issues here. Don't see a point in contributing if nothing gets merged. Pretty rough at this moment though.

But if @philplckthun is willing to fork (and actually accept PRs), i'm more than willing to contribute to sprint instead.

@kitten
Copy link
Author

kitten commented Jun 7, 2015

@rossPatton @generalandrew @Stephn-R @krzksz

I've set up a fork and will maintain it a.k.a. actually accepting PRs. https://github.com/philplckthun/sprint

@kitten kitten closed this as completed Jun 7, 2015
@rossPatton
Copy link

awesome!

@kofalt
Copy link

kofalt commented Jul 15, 2015

@philplckthun Request that you reopen this ticket & rename to "Sprint's new location" or maybe something louder / more obvious / CAPS LOCK.

Motivation is to provide incoming users with context & information when they're looking at filing a ticket.
For example, #36 was opened after this ticket was closed.

Makes sense to leave a sign with an arrow on it, yes? 😄

@kitten kitten reopened this Jul 15, 2015
@kitten kitten changed the title Sprint is dying Maintained fork of Sprint! 💡 Jul 15, 2015
@kitten
Copy link
Author

kitten commented Jul 15, 2015

@kofalt Nice idea, though I thought it was a bit harsh to consider "new location" as the designation of the fork. ;)

@kofalt
Copy link

kofalt commented Jul 15, 2015

👍

@kitten kitten changed the title Maintained fork of Sprint! 💡 MAINTAINED FORK OF SPRINT! 💡 Jul 15, 2015
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

9 participants