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

Transfer sensu-metrics-relay/WizardVan into sensu-extensions organisation? #73

Open
Evesy opened this issue Nov 16, 2017 · 6 comments
Open

Comments

@Evesy
Copy link

Evesy commented Nov 16, 2017

If possible I think it'd be good idea to transfer the sensu-metrics-relay/WizardVan extension into the sensu-plugins organisation; this'd provide:

  • Better visibility of its existence for new users
  • Hopefully improve its chances of being maintained and kept up to date in line with any Sensu releases

It's currently floating about in a couple of places:
https://github.com/opinionlab/sensu-metrics-relay
https://github.com/grepory/wizardvan

@mbbroberg
Copy link
Contributor

Really glad you brought this up @Evesy. Greg (@grepory) and I are catching up tomorrow and I'll ask about what's best for him. That should cover the wizardvan front. Seems @majormoses is the only committer on the OpinionLab side. Ben, is that something you want to keep around as well?

Playing out one scenario, say we migrate grepory/wizardvan to Sensu Extensions, would we then deprecate opinionlab/sensu-metrics-relay? Or would you prefer to do the other way of migrating the relay and deprecating wizardvan?

cc'ing @luisdavim as the lead on Extensions as an FYI!

@majormoses
Copy link
Member

majormoses commented Nov 17, 2017

So I actually had a discussion with greg about this a while back in slack:

Thursday, September 14th 

majormoses [10:43] 
actually been meaning to ask you if at some point you wanted to transfer that over to plugins so it has a perm home

[10:43] 
since even sensu-inc does not really control the sensu-plugins project


[10:44] 
even with acquisition it would live on (until someone stopped paying the bill)

[10:44] 
not that I think now is the time...just bring it up to discuss at some point


grepory [10:45 AM] 
happy to transfer it

 
majormoses [10:47 AM] 
biggest concern I have doing that is how many people it will break, maybe we transfer and then fork it so that at least it will be there for people to pull


grepory [10:53 AM] 
ya

[10:53] 
i think we can also do something to have github redirect?


[10:53] 
i can’t remember how it works


[10:53] 
that might only be repo renamse


majormoses [10:54 AM] 
I think it works for the ui but not http based stuff from what I remember


[10:57] 
to be clear I mean it should work for http based requests but I don't think the git protocol will support the redirect


[11:00] 
looks like it's possible with extra git config...but that does not really help us...


[11:02] 
since its pretty unlikely anyone has it set

One thing we could do is to transfer it and fork it to still enable folks to have it cloned to keep working and then update the repo to point to the new home.

@mbbroberg
Copy link
Contributor

Bumping this one. I like @majormoses's idea of:

  • Transfer to org
  • Fork back to original path for continuity
  • Maintain from org (no porting after that)

Question that still stands: which repo is the right one to move?

https://github.com/opinionlab/sensu-metrics-relay
https://github.com/grepory/wizardvan

wdyt @Evesy?

@Evesy
Copy link
Author

Evesy commented Jan 8, 2018

Sounds good to me!

I suppose https://github.com/grepory/wizardvan is the original... or original copy after opower got taken over at least

@majormoses
Copy link
Member

So looking through my emails and doing a bit of sleuthing this is what I came up with as far as timeline:

The original was https://github.com/grepory/wizardvan, I think at some point it was transferred to https://github.com/opinionlab/sensu-metrics-relay (might have still been called wizardvan) or was at least renamed and updated the history. On 3/14 someone deleted the repo so I ended up copying the content (no history) from one of my sensu servers to a repo on https://github.com/CloudCruiser and served that up to unblock my immediate needs. I then reached out to Greg via email and we re-created the history on 3/20 from someones fork and restored it to https://github.com/grepory/wizardvan after that I deleted my repo to avoid confusion but it looks like https://github.com/opinionlab/sensu-metrics-relay is likely a fork of my repo on CloudCruiser org (which no longer exists) as it only has a single commit from me.

@majormoses
Copy link
Member

One thing I would like to propose is that after we break the fork we rename the repo to match sensu-metrics-relay as while it does have a cool name I bet more people would find it if it had a more easily understood name. Feel free to make the argument that having a repo named wizardvan piques interest. The other question is where should it be forked to? I vote sensu-extensions as that is what it is. While sensu and sensu-plugins do have maturity they do not seem like the correct home.

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

No branches or pull requests

3 participants