Abandoned project? Any active development?

[theopolis]

Has this gem been abandoned? From the increase in pull requests and lack of merging I'm assuming so.

But I'm still happily using SettingsLogic in my projects. :) I'm curious if anyone is maintaining a replacement or has found a better implementation of the project's features?

[romikoops]

+1

[aysark]

I've been looking around, this gem seems to still be pretty good compared to others, its a shame its seems kinda a dead and there are some bugs that seem pretty basic to fix.

[squiter]

+1

[andywenk]

@aysark why not forking the project and fix the bugs?

[romikoops]

It is not problem with bug fixing, it's problem because it is not supported anymore((((

[andywenk]

@romikoops I am not sure what you mean here: "... it's problem because it is not supported anymore". What is not supported anymore and where?

[romikoops]

@andywenk See topic of issue. Last commit Dec 31, 2012 and 18 opened pull requests. Looks like we need new maintainer to support upstream

[theopolis]

I don't mind forking and merging some of these bug fixes, but my Ruby isn't very strong. If no one wants to take over by the end of the weekend I'll try my hand. I've been using settingslogic for a while and I'd hate to see it become incompatible in the near future due to lack of maintenance.

[andywenk]

@theopolis Great! Thank you. I am happy to review your changes. Unfortunately I will not have the time to work on it by myself. You can get in touch with me via [email protected] ...

[goosetav]

hey guys, I'd be happy to help out with maintenance as well -- I've been using this gem for awhile now.

I setup a fork under settingslogic/settingslogic that could be a new home - anyone else want to pitch in?

@yourewelcome Ben, you cool if the community starts taking over?

[andywenk]

@goosetav this sounds great. I think the proper way would be to take over the repository to the new home and change the README in this repo here ... but this requires @yourewelcome to be happy with this :)

[aysark]

Count me in.

[goosetav]

Count me in.

@aysark - done!

anyone other volunteers? I'll also try pinging @yourewelcome outside of github

[X0nic]

I would love to help also.

/cc @goosetav

[goosetav]

@X0nic I added you to the forked repo -- I still haven't been able to get in touch with @yourewelcome

[chrean]

This is cool. I am using Settingslogic, too, and I like it a lot. Will the gem be hosted on rubygems under a different name?

P.S. If you need some help, count me in as well.

[binarylogic]

I'm working on assigning a new maintainer and will have one by the end of the week. Thanks.

[shlima]

+1

[cofiem]

+1 I use this gem quite heavily, and would probably have some contributions - what's the progress on new maintainer?

[X0nic]

@yourewelcome Can we help you with assigning a new maintainer? Maybe following the Pull Request Hack would also work?

[goosetav]

@cofiem I just added you to the new repo

updates: I have been in touch with @yourewelcome and he's willing to give us access

I could use some help bringing over some of the PR's to settingslogic/settingslogic and submitting a PR to this repo to update the README

Once all that's done, we'd need to have @yourewelcome grant us rights at rubygems.org so we can publish updates

[cofiem]

Cheers @goosetav

What's involved in bringing over PRs? Does this mean re-creating the PR, or can they be re-targeted in some way?

[goosetav]

What's involved in bringing over PRs? Does this mean re-creating the PR, or can they be re-targeted in some way?

I was hoping someone had a smart answer for that question...

[cofiem]

Maybe something along these lines? Pull requests from other forks into my fork

[X0nic]

Great find @cofiem. After playing around with git, and trying those suggestions it looks like this would work. I say we start going through the open PR's and :+1: them. If a PR gets a couple :+1: 's then it is fair game to merge into the new repo.

We will just need some way to keep track of what is merged into the new repo, and what is not.

/cc @goosetav

[cofiem]

Excellent. I've already found 3 PR's that have quite a few existing :+1: . I added my own, just sort the issues by recently updated.

[X0nic]

I merged a couple PR's into https://github.com/settingslogic/settingslogic

[cofiem]

Hello all, where are we at with this? I gather we still need to go through PRs, and get access to publish gem udpates at rubygems.org?

[goosetav]

@cofiem yep, that pretty much sums it up.

any volunteers to put a PR against the README in this repo explaining the shift over?

[cofiem]

PR #73 is the beginnings of that - any other info that needs to be included?

[goosetav]

:+1: didn't see that before

@yourewelcome could you merge #73?

[cofiem]

As to the existing PRs - @X0nic merged some two weeks ago, and there's probably more that could easily be accepted.

[goosetav]

ok, we're all set now to manage the switch now! thanks @yourewelcome

opened settingslogic/settingslogic#1 to start tracking what everyone wants to push into the new repo

[mensfeld]

+1 - thats up with maintenance of this gem?

[shlima]

Rails 4.2.1 has suitable config_for method http://apidock.com/rails/v4.2.1/Rails/Application/config_for + secrets.yml + rails .env.

So this gem has to be dead.

[mensfeld]

@shlima keep in mind that there's a whole interesting world outside of Rails ;)