migrations and archives...
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- release
Research direction
Start with the unchecked repository links and the referenced W3C mailing-list messages. Verify the archival status of display-override, file-handling, lock-screen, pwa-url-handler, and raw-clipboard-access, including confirmation for pwa-url-handler. Done means the applicable repositories are archived or migrated and every checklist item is resolved.
Written by the indexing model from the issue text.
Description
- * Element Capture migrated from https://github.com/WICG/element-capture to https://github.com/screen-share/element-capture
- * https://github.com/WICG/multicapture/issues/7 (moved)
- * https://github.com/screen-share/capture-all-screens/issues/8 (migrate to another CG)
- * transfer-size can be archived according to https://lists.w3.org/Archives/Public/public-wicg/2023Feb/0009.html
- * floc can be archived according to https://lists.w3.org/Archives/Public/public-wicg/2023Feb/0009.html
- * https://github.com/WICG/display-override can be archived according to https://lists.w3.org/Archives/Public/public-wicg/2023Feb/0016.html
- * https://github.com/WICG/file-handling can be archived as it's https://wicg.github.io/manifest-incubations/#file_handlers-member
- * https://github.com/WICG/lock-screen can be archived according to https://lists.w3.org/Archives/Public/public-wicg/2023Feb/0016.html
- * https://github.com/WICG/pwa-url-handler can be probably be archived as it's moved to https://github.com/WICG/web-app-launch (needs confirmation)
- * https://github.com/WICG/raw-clipboard-access can be archive according to https://lists.w3.org/Archives/Public/public-wicg/2023Feb/0016.html
- Dominant language
- HTML
- Stars
- 60
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 WICG/admin
-
TPAC 2026 Open
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Archive portals? Open
Difficulty 1/5 Under an hour Newbie friendliness 35/100
Similar issues
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·