-
Notifications
You must be signed in to change notification settings - Fork 41
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
Reach out to orgs to take responsibility for plugins #546
Comments
@jawache when could you realistically start this? 🙏 |
@jawache do you feel up for this one this week or should we move to next? There is a strong desire to launch the plugin registry with most of the plugins cleaned up and ownership clarified 🙏 |
@jmcook1186 and @zanete so I think realistically this will have to be me perhaps making introductions but then @jmcook1186 following up. I'd suggest we set up a 1hr working call next week where we just go through these, craft some emails together and send out, @jmcook1186 wanna try and find some time next Thursday? |
yes - fantastic. I'll suggest a time. |
great, thanks both! I will leave it to you to organise (and moving this to next week so it doesn't mess with with the board) |
@jawache how's this going? who have you contacted and what's new? |
Emails all sent @zanete |
all third parties have been contacted |
Sub of #656
what
Reach out to organizations that could take ownership of specific plugins in our
if-plugins
andif-unofficial-plugins
repositories to support later external migration of the plugins.rationale
We want to gradually deprecate the
if-unofficial-plugins
repository by passing responsibility for specific plugins to the orgs best positioned to maintain them. The first step is to identify and then reach out to those orgs.acceptance criteria
cloud-metadata
fromif-plugins
teads-curve
fromif-unofficial-plugins
and replace with generics pipeline #727grafana-exporter
azure-importer
fromif-unofficial-plugins
boavizta
fromif-unofficial-plugins
if-unofficial-plugins
watt-time
fromif-unofficial-plugins
ccf
tdp-finder
csvs to its own repo #728Implementation details
@jawache to instigate majority of these conversations as he has open dialogues with many of the target organizations already.
The text was updated successfully, but these errors were encountered: