Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need help with maintainership? #297

Closed
bf4 opened this issue May 2, 2014 · 8 comments
Closed

Need help with maintainership? #297

bf4 opened this issue May 2, 2014 · 8 comments

Comments

@bf4
Copy link
Collaborator

bf4 commented May 2, 2014

Seems the queue is growing. I'm happy to help. For example, I have a PR from eight months ago #245 that fixes a segfault issue and it hasn't been reviewed...
@mszyndel
Copy link

@colszowka

@bf4
Copy link
Collaborator Author

bf4 commented Jun 10, 2014

I've sent @colszowka emails but no response... sad..

@colszowka
Copy link
Collaborator

Hey @bf4, got your e-mail yesterday but it was a public holiday here in germany and I was busy. I'll get back to you over the week!

@bf4
Copy link
Collaborator Author

bf4 commented Jun 11, 2014

Oh, ok. (That was the second email. The original was 2013-12-11.) Thanks!

@bf4
Copy link
Collaborator Author

bf4 commented Jun 15, 2014

Would it help to move it to a new org like https://github.com/gemhome/simplecov so aid in permission-level management of maintainers? (I'm experimenting with this as a place for either repos moving from a 'personal' account to a 'community' one, or as a good place for development of abandoned repos to continue. Related to rubygems/rubygems.org#429 and the call for a rubygems adoption center

@colszowka
Copy link
Collaborator

@bf4 Added you as a collaborator to the repo, welcome on board! I don't think moving to a separate org is needed at this point, since this is neither an abandoned project nor does it have a multitude of repositories that would make handling collaborators much easier via an org.

Most importantly, if you like it would be great if you could have a browse through the issues, since many of them are stale and might need closing since people frequently fail at setting SimpleCov up correctly, file an issue, then never come back. Quite often these are related to some reloading/preloading test manager like Spork, Zeus etc. - these issues are incredibly hard to reproduce without demo code, so I'd tend to think that after asking for sample code, these issues should just be closed if no sample code becomes available. Some other things I've intended to do for ages but never quite found the time are moving the whole unit test suite to RSpec and removing Ruby 1.8.7 "support" altogether. Issue #281 is fairly urgent.

@mszyndel
Copy link

@colszowka great to see you back!

a little off-topic but I just fixed the build and my fix for #281 passed all tests now, see #302

ping @bf4

@bf4
Copy link
Collaborator Author

bf4 commented Jun 15, 2014

Will do after fathers day. Thanks. For gem push, i'm dev at
benjaminfleischer.con on rubygems.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@colszowka @bf4 @mszyndel