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

Reach out to orgs to take responsibility for plugins #546

Closed
9 tasks done
Tracked by #656
jmcook1186 opened this issue Mar 19, 2024 · 8 comments
Closed
9 tasks done
Tracked by #656

Reach out to orgs to take responsibility for plugins #546

jmcook1186 opened this issue Mar 19, 2024 · 8 comments
Assignees
Milestone

Comments

@jmcook1186
Copy link
Contributor

jmcook1186 commented Mar 19, 2024

Sub of #656

what

Reach out to organizations that could take ownership of specific plugins in our if-plugins and if-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

  • Real Time Cloud have been approached to take ownership of cloud-metadata from if-plugins
    • Discussion on this has started already, here
  • Remove teads-curve from if-unofficial-plugins and replace with generics pipeline #727
  • Bloomberg (?) to take on grafana-exporter
  • Microsoft have been approached to take ownership of azure-importer from if-unofficial-plugins
  • Boavizta have been approached to take ownership of boavizta from if-unofficial-plugins
  • Green web foundation have been approached to take ownership of CO2js from if-unofficial-plugins
  • Watt-time have been approached to take ownership of watt-time from if-unofficial-plugins
  • Thoughtworks have been approached to take ownership of ccf
  • Move tdp-finder csvs to its own repo #728

Implementation details

@jawache to instigate majority of these conversations as he has open dialogues with many of the target organizations already.

@jmcook1186 jmcook1186 added this to IF Mar 19, 2024
@zanete zanete moved this to Backlog in IF Apr 22, 2024
@zanete zanete moved this from Backlog to In Design in IF Apr 22, 2024
@zanete zanete mentioned this issue Apr 22, 2024
28 tasks
@jmcook1186 jmcook1186 moved this from In Design to In Refinement in IF Apr 24, 2024
@zanete zanete moved this from In Refinement to Ready in IF Apr 29, 2024
@zanete
Copy link

zanete commented Apr 29, 2024

@jawache when could you realistically start this? 🙏

@zanete
Copy link

zanete commented May 8, 2024

@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 🙏
cc @jmcook1186

@jawache
Copy link
Contributor

jawache commented May 8, 2024

@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?

@jmcook1186
Copy link
Contributor Author

yes - fantastic. I'll suggest a time.

@zanete
Copy link

zanete commented May 9, 2024

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)

@zanete zanete moved this from Ready to In Progress in IF May 16, 2024
@zanete
Copy link

zanete commented May 17, 2024

@jawache how's this going? who have you contacted and what's new?

@jawache
Copy link
Contributor

jawache commented May 17, 2024

Emails all sent @zanete

@jmcook1186
Copy link
Contributor Author

all third parties have been contacted

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

No branches or pull requests

3 participants