asset_sync project appears dead

[josephlord]

@davidjrice

There have been no commits to master in nearly 11 months. There are 19 pull requests plus numerous other issues that haven't been properly dealt with.

I think it is time to be clear whether Rumble Labs is still interested in this project and what the intended roadmap is for it or whether the users should be looking to fork and have it maintained by a different maintainer or failing that migrate way to alternative solutions. Asset sync is good and useful software which is why I care about this and I am grateful to Rumble Labs for creating it and there is no problem with them deciding it isn't a priority and allowing a community take over or to let people know that it is no longer maintained so that they can consider if they still want to use it but it is much better to be clear about the plans.

[viktornonov]

+1

[jclusso]

+1

[gretel]

if you want to be a maintainer, be a maintainer. if you want code to change, change the code.

[jclusso]

Well, I've sent Rumble Labs an email and hopefully they'll respond and start maintaining it or give someone else control over the project. It always amazes me how creators of popular github projects just go completely off the record.

[alexch]

👍

@gretel what are you talking about? There are 19 open PRs, the fork tree looks like a massively multiplayer game of Tron, and there has been zero (0) activity from the maintainer in almost a year. We are changing the code and the maintainer is not letting anyone else be one.

[gretel]

so what are you talking about? do i prevent you from forking or what?

[alexbel]

@jclusso 👍

[alexch]

@gretel are you trolling me? I did fork and made a PR #266 and I'd like the rest of the world to be able to get the benefit when they do "gem 'asset_sync'".

[gretel]

you gonna save the world with that. think about who is trolling whom, i'd say you guys are trolling rumble labs.

[jclusso]

If @rumblelabs doesn't respond soon I think it would be best that we create a new fork, setup some maintainers and create a new gem with a similar name like asset_sync_rails. What do you guys think @alexch and @josephlord?

[mbhnyc]

Go go gadget fork!!

[jclusso]

Well is started by making a fork https://github.com/jclusso/asset_sync_rails

Who is interested in helping maintain it?

[josephlord]

I think we should wait until 26th July for a Rumblelabs response before releasing a new Gem, that is a nice round year from the last commit to master. That doesn't mean work and testing on forked code can't start earlier.

I'd be happy to help out a bit for the moment. I'm currently job hunting and depending on how that works out I might not be able to commit much time at all.

I've just set up an asset-sync organisation so we can group asset_sync and a test project together and so the project can be handed on to whoever is interested in maintaining it as time passes without the github URL changing. I've added @jclusso as an owner and others keen to support could be added too.

[jclusso]

We just need some active people to handle merging updates etc. I'm not
looking to get people to start actively building new features. We just
need to maintain it so and keep it up to date so we can ensure this gem can
continue to be available since it's basically an essential for a lot of
rails projects in production.

On Saturday, July 12, 2014, Joseph Lord [email protected] wrote:

I think we should wait until 26th July for a Rumblelabs response before
releasing a new Gem, that is a nice round year from the last commit to
master. That doesn't mean work and testing on forked code can't start
earlier.

I'd be happy to help out a bit for the moment. I'm currently job hunting
and depending on how that works out I might not be able to commit much time
at all.

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

Regards,
Jarrett Lusso

[gretel]

😘

[jclusso]

@josephlord, I've gone ahead and setup the repo and anyone else interested in joining should head over there and get in contact with one of us. I'm not familiar with this, but is there anyway to copy the pull requests from one repository to another since there is 19 of them and we probably shouldn't just blindly merge them all in? At this point the only thing I can see doing would be just manually checking those out and merging them onto the new repo.

[tosbourn]

Hey there - I work at Rumble and I can totally understand the frustration here.

We were chatting late last week about the need to carve out some time to get this repo back up to speed again. I am going to push for that to happen this coming week.

[jclusso]

@tosbourn chiming in at the last minute! If you guys can continue to maintain it that would be awesome! 👍

[josephlord]

@tosbourn Just knowing it is alive and that you are going to get it going enough to get the pull requests is OK for me. It doesn't need to be absolutely this week rather than in a couple of weeks (although this week would be great).

[josephlord]

Closing this issue due to action from @tosbourn. If there is any particular help you want give a shout.

[josephlord]

@tosbourn How are you doing on reopening activity on this project? Thanks for merging my PR but there are other PRs that are probably more important. I'm using #149 in production and others are using #259 and maybe others too. Does this issue need reopening?

[corbt]

I'm looking to adopt this gem in a new rails project and am blocked by a couple issues with existing pull requests (fixing mime types and correct cache control headers that don't expire after a year). What are the chances that this project is revived soon and those can be merged?