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).
@evoloshchuk @dgmstuart @Thermatix @idoo @ravicious @aslakhellesoy @FernE97 @rzhou186 @natesalisbury @dhananjaysathe @franzk @Rendez @leoc
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.)
@odigity I would personally use Sprocket as there is now a few good integrations with Sinatra.
@j15e I agree.
I vote for eventual deprecation of this gem and making a note to migrate to sprockets.
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.
I'm no expert, but I'm guessing that can be accomplished by:
I found 2 gems that could replace assetpack for a sinatra project :
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.
@odigity I just made a final release with a post install notice as you suggest (thanks).
Thank you so much, @j15e.
I would also like adding note about deprecation to the recipes.sinatrarb.com post.