Closed bootstraponline closed 9 years ago
From @johnnyshields on December 13, 2013 14:29
@webcracy @jgrevich
From @odino on January 24, 2014 13:5
:+1:
From @webcracy on January 24, 2014 14:52
I've pinged @nu7hatch a while back. Hope he'll find the opportunity to do something about the gem.
From @johnnyshields on January 24, 2014 15:13
A good solution here is to make other trusted people as admins (@webcracy yourself for instance), that way maintenance work is split...
From @maccman on February 14, 2014 0:0
Here here!
From @jgrevich on February 14, 2014 19:7
I can do my part to breath some life back into this. I had a project in line that was going to give me the excuse to do some major work in this gem but it's looking like it's going to be on the icebox a bit longer.
My biggest concern is the lack of test coverage and that would be my first order of business. I will get this hooked into TravisCI and start working to add more tests. It'd be great if someone can go through open issues so they can be correctly labeled (bug?), prioritized, or closed.
@johnnyshields @webcracy and I have admin privs. I thought there may have been one or two others as well.
Cheers!
From @nu7hatch on February 14, 2014 19:57
Hi guys, sorry, but I'm completely out of open source recently and will not find time to contribute to the project any soon :/. Some time ago I took a look around the code and noticed that few pull requests that introduce bugs were merged (I think I pointed out some in few issues), anyway, if anyone else is interested I can give you guys access to the repo. Last thing, I'd recommend you to make some todo list on what's needed in the project (you users probably know way more about it than I do) and get those solved one by one using pull request - I could eventually give code review and give you tips on some stuff, I think I'd have at least a bit of time to help you out this way.
Best, nu7
From @johnnyshields on February 14, 2014 20:7
I'd be glad to contribute my time to review/merge PRs and write specs where needed. As far as I'm aware there's not a whole lot of new development that needs to be done, "maintenance mode" should suffice.
From @webcracy on February 16, 2014 23:40
I believe one of those bugs was introduced by one of my pull requests regarding IMAP extensions, so I stand behind you and we ought to be deliberate in what we're doing and how if you're not going to be reviewing things personally in the future.
I'd done the following roundup in October, and I suggest we take it from here unless there's a another review around.
How about everyone please take a look at the following items and share your comments or, even better, code reviews? Maybe we can figure out a roadmap from this, @nu7hatch, @jgrevich and @johnnyshields ?
There's pull request list that is good enough.
@90seconds has fork that has a lot of features and improvements that we can use. We could also 90seconds to ask him to submit a pull request or we could merge his fork into master.
Available in pull request #66 and/or 90's fork.
Pull request available
Work in progress
Code available in pull requests and/or 90seconds' fork
From @MrOrz on February 27, 2014 18:27
:+1: for maintaining this terrific gem!
From @johnnyshields on April 4, 2014 14:29
@webcracy your plan above looks very good. Would you like me to help with flagging the issues?
From @webcracy on April 4, 2014 14:31
@johnnyshields Yes, please do! (All others are welcome to as well!)
From @johnnyshields on April 4, 2014 14:57
@webcracy (or anybody) can you please give me Collaborator access to this repo?
From @webcracy on April 4, 2014 15:5
@johnnyshields Pinging @jgrevich and @nu7hatch, I actually don't have Collaborator access either.
From @jgrevich on April 4, 2014 18:9
@webcracy I thought we used to have admin access but it doesn't look like that's the case anymore. @nu7hatch, can you add @johnnyshields as a collaborator?
From @kingdonb on April 7, 2014 13:41
I will also vouch for the excellence and overall great workingness of this gem, I would volunteer some time closing issues and reviewing pull requests, or at least reviewing others' hard work merging requests to try and vote for new leadership.
If @nu7hatch is busy with life, too much to manage the github collaborator list, maybe one of us can fork and make a new HEAD, and prepare the next release(s) since it looks like @webcracy has prepared a pretty decent look at what issue belongs in probably the next two releases at least.
There are only 139 forks out there right now, so it should be easy to decide who gets the torch next (grin)! Is there a workflow to fork and start closing PR's like I'm imagining, or is there some part of github that makes porting issues and pulls from one repo to another a big deal? Has someone started on this already?
From @nu7hatch on April 7, 2014 13:49
Yeah, I was pretty busy and off from open source for past year. Next week I'm coming back to Europe and I'll for sure find enough time to wrap all the issues of this gem and release new version. If any of you can help out that would be awesome. @webcracy thanks for preparing nice overview of current status.
Best, Chris
From @webcracy on April 14, 2014 20:10
@nu7hatch excellent news! Let us know where you need help. Cheers!
From @johnnyshields on April 20, 2014 5:53
@nu7hatch can you please make @webcracy and I as repo collaborators so we can help triage issues?
From @jgrevich on October 5, 2014 18:41
I created a discussion at http://help.rubygems.org/discussions/problems/19044-gem-owner-mia . Please comment and show your support so we can get updates pushed to RubyGems.
From @bootstraponline on Dec 3, 2014
:+1:
From @johnnyshields on December 13, 2013 14:27
@nu7hatch this is a great gem and the community has raised some very good PR fixes, but looks like nothing merged in the past year.
It would be a big help if you or someone you designate can help merge some of these PRs. If no one is available I'd be glad to volunteer a bit of my own time though I am new to this particular gem.
Copied from original issue: nu7hatch/gmail#96