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.

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

Keeping the lights on this project #124

Closed
vorburger opened this issue Sep 10, 2018 · 10 comments
Closed

Keeping the lights on this project #124

vorburger opened this issue Sep 10, 2018 · 10 comments

Comments

@vorburger
Copy link
Member

Following up on spotbugs/spotbugs#742 (which I'll close) :

In the interest of open public communication, and for the record:

@ArloL has recently invited me to become a committer on this project.

I don't really have the time to really maintain this code, as I'm already stretched too thin.

But in both the interest of the community and for my own purposes in opendaylight-eclipse-setup where I use this, I will try to find the time to go over the currently 6 open PRs and 13 open issues - hopefully some time next week (I'm AFK at an event this week, may be between things). Before doing that, I'll try to contribute #123.

Beyond that, I'm unlikely to be able to be particularly reactive. This will probably pretty much have to be a "minimal support, figure it out, PRs welcome, best of luck" kind of "keeping the lights on" type involvement.

I would however be happy to invite more people to have commit privilege here. As these things typically go in open source, you would have to have made at least some sort of code contribution via a PR to this project for it to make sense to be promoted to a co-committer. We can set the bar quite low though, and don't have to see 100 PRs before making anyone a contributor. There is always git revert ... 😸 (If anyone is reading this who has previously already contributed to this project via PRs for code, then please comment here and I'll most likely add you ASAP.)

If anyone has any other ideas how to get more active contributors to keep this useful project alive and well maintained, please also comment here. If you just think that it's great that someone is doing this, perhaps just thumbs up.

@victornoel
Copy link
Contributor

@vorburger if you need help reviewing PRs I'm available (just point them to me I will make comments)

@rexhoffman
Copy link

@vorburger would you like a working travis-ci build? I wouldn't mind spending a few days over the next month on tooling, snaptshot p2 repo deploys to github pages, etc. If I get really ambitious full eclipse environment tests.

@pgalbraith
Copy link
Member

Thanks so much for stepping up here @vorburger et al, especially since it doesn't seem like you exactly volunteered for this :-).

I'd love to see the checkstyle plugin working in Photon again, I think there is one (more?) PR for this already. Unfortunately, I'm in no way qualified to review it.

@vorburger
Copy link
Member Author

@rexhoffman Continues Deployment of a "snapshot" p2 repo to GitHub pages just completed, see #123; looking for testers - comment in #123, if anything NOK. New PRs for further tooling related improvements or more ambitious full eclipse environment tests certainly most welcome!

@pgalbraith installing into Photon probably works now (with the version from #123), I've not yet tested it - will you test, and open a new issue with details if it's still NOK on Photon but OK in older, or comment in #123 if OK everywhere?

@vorburger
Copy link
Member Author

I would however be happy to invite more people to have commit privilege here. As these things typically go in open source, you would have to have made at least some sort of code contribution via a PR to this project for it to make sense to be promoted to a co-committer. We can set the bar quite low though, and don't have to see 100 PRs before making anyone a contributor.

@erwint has already raised 6 PRs, and in my book that's sufficient, and what I was hoping for 😃 (above) - I have therefore just invited him as a new co-owner of the m2e-code-quality organization! @ArloL I hope / will assume that is OK with you. Erwin, perhaps we could have the "convention" more than the "hard rule" that we review each other's changes and, typically, don't "self merge" in the very short term, but just in case I get run over by a bus, or can't give this project continued attention (very likely), do feel free to just carry the torch forward, even if I am non-responsive later!

BTW: @belaeroess (Bela Eröss) you are the only other current org member than me and @ArloL .. are you alive, and still have any interest in this project? Last contributions Jan 16, 2014. Without hearing from you within let's say 2 weeks, I'll take the liberty of removing your commit privilege, just as a general security precaution for not having any inactive accounts, hope that's fair? Just reply "I'm alive and would like to keep my commit privilege on this project" if you are, and you'll stay on.

@vorburger
Copy link
Member Author

FTR @belaeroess on private email: "It’s fine, i am not planning to contibute in the near time.", so rm him.

@erwint
Copy link
Member

erwint commented Sep 19, 2018

@vorburger thanks, the "generally don't self merge" rule is okay by me

@victornoel
Copy link
Contributor

@erwint @vorburger thanks for the great work :)
I want to help but can't be as reactive as you are. I will try to tackle #121 tonight!

@vorburger
Copy link
Member Author

I want to help but can't be as reactive as you are.

Never feel guilty or regret! 😄

Just do the best you can in everything you do, and everything else will be fine. Typically.

vorburger added a commit to vorburger/m2e-code-quality that referenced this issue Sep 19, 2018
erwint pushed a commit that referenced this issue Sep 19, 2018
…o make it more of an open community (#144)

for full background,
see also #123
and #124
and #143
@vorburger
Copy link
Member Author

http://blog2.vorburger.ch/2019/02/about-you-and-that-open-source-thing.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants