Transfer DataDog/dc-polyfill to the org
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reviewing issue #1019 and the requested transfer details for DataDog/dc-polyfill. Confirm the nodejs organization’s ownership and maintainership process; done means the transfer decision is recorded and, if approved, the repository is moved with the proposed maintainers or an assigned team.
Written by the indexing model from the issue text.
Description
A few years ago, we (Datadog) created dc-polyfill. This package essentially backports features and fixes from the version of diagnostics_channel that ships in newer versions of Node.js so that applications using older versions of Node.js can benefit.
The package was built with the intent that other npm packages would depend on it as well. If the current version of Node.js doesn't have diagnostics_channel built in then it creates a single repository in memory regardless of how many versions of dc-polyfill exist in a user's node_modules directory. If the current version of Node.js has some major bugs or lacks major features then diagnostics_channel is used under the hood but a patched version is exported. And if the current version of Node.js is fully featured then this package is a noop.
Rather than form a separate entity/org to own this, we think that the Node.js org is an ideal place for this library to live. To that end, we're requesting a transfer from the DataDog GitHub org to the nodejs GitHub org. A team can be created for maintainership, or it can be assigned to Diagnostics WG or similar group, but either way we'd like to have the following users as maintainers to start:
- @tlhunter
- @uurien
- @bengl
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 13d 12h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
antfu-collective/icones#398 ·
-
ECmail.com Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wesbos/burner-email-providers#554 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
radiantearth/stac-browser#1023 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#92 ·