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

Migrate to statsite 'organisation'? #217

Closed
johnkeates opened this issue Oct 23, 2016 · 13 comments
Closed

Migrate to statsite 'organisation'? #217

johnkeates opened this issue Oct 23, 2016 · 13 comments

Comments

@johnkeates
Copy link
Contributor

It seems the author simply doesn't have the time to keep track of all the issues and PR's (which makes sense, it's a lot of work+time), so maybe it's a good idea to have some sort of group or organisation with more people that can accept PR's?

@filippog
Copy link

Agreed, I think it'd make sense if more contributors could merge PRs and avoid maintaining long-lived forks

@johnkeates
Copy link
Contributor Author

I hope @armon has a few minutes to spare to say something about this. If he is too busy (which does happen, work gets in the way quite often for me as well), we could always just decide to set up an "official" fork.

@theatrus
Copy link

Happy to help with the project if it branches out into an org, and possibly work on moving our long-running fork into the main code base (https://github.com/lyft/statsite)

@johnkeates
Copy link
Contributor Author

Let's see what others (or @armon) have to say for the next 2-3 days, even with 3 volunteers we would have enough people to get an org going.

@kuba--
Copy link
Contributor

kuba-- commented Oct 24, 2016

Make sense, but which repo will be a base fork?

@theatrus
Copy link

I imagine this repo would be the base fork as its the one most people are already running. I can take the multi-sink + built-in HTTP fork (+ critical bug fix to sampling) and merge it back in with all the changes in the upstream later (build system, event system, etc).

@johnkeates
Copy link
Contributor Author

Using this repo would indeed be the best plan, most forks are based on this one and merge back in to this one. Changing that will make it harder for everyone to add their pending PR's.

I'm trying to figure out if I can break down my monster-PR as to make the merging for others easier, the alternative would be me merging first and everyone else merging on top of that.

I've taken the liberty of setting up an org named 'statsite', but it's @armon his call on weather that's okay. It's his name after all, and while I'm not really all that interested in legal aspects, I just don't want an unfriendly break.

@armon
Copy link
Collaborator

armon commented Oct 25, 2016

Hey all! Funny I was just thinking in the shower about emailing contributors to give commit access. Unfortunately my days are dominated by management and I've neglected the project. I would be happy to move it to an organization.

@armon
Copy link
Collaborator

armon commented Oct 25, 2016

@johnkeates Do you want me to just transfer this to that organization?

@armon
Copy link
Collaborator

armon commented Oct 25, 2016

CC: @sleepybishop @melkor217 who have also made contributions.

@johnkeates
Copy link
Contributor Author

johnkeates commented Oct 25, 2016

I suppose it makes sense to transfer it, great minds think alike eh ;-)
@armon I'll start off with adding us four, and you can transfer whenever you feel like it.

@armon
Copy link
Collaborator

armon commented Oct 25, 2016

@johnkeates Transfered! Thanks so much, and many apologies for being slow to do this.

@johnkeates
Copy link
Contributor Author

@armon thanks! and no worries about being busy, we all have jobs taking away our attention and time from stuff like this ;) I think this is a good move, with a bit of luck we'll get a proper community drive behind statsite and your project will go on and grow on it's own!

I'm closing this issue since it's "resolved", thanks for taking the time to make this happen in a neat fashion.

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