Transfer DataDog/dc-polyfill to the org
還沒有人認領這個 Issue。
評估
研究方向
先檢視 issue #1019 以及針對 DataDog/dc-polyfill 所要求的轉移詳細資訊。確認 nodejs 組織的擁有權與維護流程；當轉移決定已記錄，且在獲得核准的情況下，repository 已由提議的 maintainer 或指定的團隊完成移轉時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
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
- 主要語言
- JavaScript
- 星號
- 202
- 分支
- 183
- 平均合併
- 13 天 12 小時
- 30 天內合併 PR
- 2
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
nodejs/admin 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 90/100
-
tsc-agenda
難度 5/5 一週以上 新手友好度 30/100
-
難度 5/5 一週以上 新手友好度 35/100
-
難度 5/5 一週以上 新手友好度 35/100
-
難度 5/5 一週以上 新手友好度 30/100
相似的 Issue
-
factory-active factory-automatic task-bug-reproduction-success task-identify-harness-labels-done task-identify-issue-type-done
難度 2/5 1-3 小時 新手友好度 90/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
status: waiting triage
難度 2/5 1-3 小時 新手友好度 84/100
freeCodeCamp/freeCodeCamp#70412 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
rohitg00/ai-engineering-from-scratch#490 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 6 天內回覆