Looking for new maintainer #197

Open
j15e opened this Issue Apr 15, 2015 · 12 comments

Projects

None yet

6 participants

@j15e
Collaborator
j15e commented Apr 15, 2015

Hello everyone,

I have seen new issues & pull requests since the start of 2015, but had not time to look at it.

I have maintain this gem for a quite a while (since 2013), but I must say I am not using it anymore and do not have the time to maintain it properly now. In most case, sprockets and other new frontend build tools (ex. broccoli) do an excellent job for my needs. Still, I am cool with diversity and keeping sinatra-assetpack alive too, but I do not have personally the time to manage it and keep it up to date.

So I would gladly give the maintainer responsibilities to someone else (with @rstacruz agreement).

Thanks everyone

@evoloshchuk @dgmstuart @Thermatix @idoo @ravicious @aslakhellesoy @FernE97 @rzhou186 @natesalisbury @dhananjaysathe @franzk @Rendez @leoc

@idoo
idoo commented Apr 15, 2015

💪

@odigity
odigity commented Oct 1, 2015

Can I ask you a personal question?

As a newcomer to Sinatra (one week, having a great time so far), should I use this gem, or is sprockets a better choice? (In light of the current availability of maintainers for each.)

@j15e
Collaborator
j15e commented Oct 1, 2015

@odigity I would personally use Sprocket as there is now a few good integrations with Sinatra.

@idoo
idoo commented Oct 1, 2015

@j15e I agree.

@rstacruz
Owner
rstacruz commented Oct 2, 2015

I vote for eventual deprecation of this gem and making a note to migrate to sprockets.

@Thermatix

I think sprockets a little more involved but ultimately worth doing, and many of the more modern gems make use of it like opal for example.
I agree with @rstacruz.

@odigity
odigity commented Oct 13, 2015

I'm no expert, but I'm guessing that can be accomplished by:

  1. Adding an all-caps note in the README and repo title.
  2. Adding a puts statement to the gemspec with a deprecation warning that people will see whenever the gemspec is evaluated (when the gem is installed).
  3. Bumping the version and pushing to rubygems.

Right?

@Thermatix

@odigity prettymuch.

@j15e
Collaborator
j15e commented Dec 3, 2015

I found 2 gems that could replace assetpack for a sinatra project :

https://github.com/kalasjocke/sinatra-asset-pipeline
https://github.com/petebrowne/sprockets-helpers

I do not think one of them is a clear winner as one is supporting sprocket 3.0 but the other is more popular & simpler to use. We could refer to both alternatives in the deprecation notice.

I'll try to ask Sinatra maintainers what they think about it on their slack maybe they would have other suggestions.

@j15e
Collaborator
j15e commented Dec 3, 2015

@odigity I just made a final release with a post install notice as you suggest (thanks).

capture d ecran 2015-12-03 a 11 48 20

@rstacruz
Owner
rstacruz commented Dec 3, 2015

Thank you so much, @j15e.

@allomov
allomov commented Feb 7, 2016

I would also like adding note about deprecation to the recipes.sinatrarb.com post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment