-
Notifications
You must be signed in to change notification settings - Fork 78
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 of import-in-the-middle #634
Comments
+1 |
+1 from me |
The current active contributor base (which we hope will grow!) for @bengl It would be good if these folks were involved in maintainership going forward. Under the assumption that this WG will assume maintainership of import-in-the-middle, should they all be members of (or seek membership in) this WG? |
I am currently discussing with the Node team at New Relic to determine what we are up for (I don't see why we wouldn't want to be maintainers, but still need to go through the process). |
No particular time commitment expected or anything like that, of course. Just want to make sure the keys to the project aren't held exclusively by Datadog. Other vendors sometimes encounter issues to be fixed and shouldn't be blocked on someone else landing and releasing those changes, especially given we're all depending on this project for our own products customers are paying for and expecting quick responses to issues on. |
@nodejs/diagnostics please note the questions I asked in nodejs/admin#858. In particular, it would be great the first question (i.e. is maintainership going to be handled by this WG? or some new team perhaps?) can be answered. I'm happy to initiate the transfer after that. |
We have discussed it a bit in today's meeting (#637) an it seems there are a significant number of contributors who would like to support the maintenance of this module as well as participate in other working group initiatives Recording: https://www.youtube.com/watch?v=Q6snsixbu9o&ab_channel=node.js |
We are proposing to donate the import-in-the-middle project to the Node.js organization to better open it up to shared collaboration with other APM vendors. There's an admin repo issue for this already, creating this one for our own reference and to add it to the working group agenda.
nodejs/admin#858
The text was updated successfully, but these errors were encountered: