Microsoft OSS release checklist — complete before public release (growth-ecosystems/scope-core → microsoft/scope)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- release
Research direction
Start by reviewing the Microsoft Open Source release checklist linked in the issue and then open sub-issues #1346, #1350, #1348, #1349, #1351, #1352, and #1347 for their task details and status. The umbrella issue is done when every listed sub-issue is closed.
Written by the indexing model from the issue text.
Description
Original author: @cedricvidal
Umbrella tracking issue for completing the Microsoft Open Source release checklist before moving to github.com/microsoft/scope, per the OSS release review.
Each checklist item is tracked in its own sub-issue below (see the Sub-issues section for live progress). Details, status, and task breakdowns live in each sub-issue.
| # | Item | Sub-issue |
|---|---|---|
| 1 | Project name approval | #1346 |
| 2 | Third-party OSS / NOTICE | #1350 |
| 3 | CONTRIBUTING.md | #1348 |
| 4 | SECURITY.md (V1.0.0) | #1349 |
| 5 | MIT license headers | #1351 |
| 6 | Going public / PoliCheck | #1352 |
| 7 | Responsible AI | #1347 |
This issue is complete when all sub-issues are closed.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 5
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 19
Getting set up
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 microsoft/scope
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
author: JaGord documentation good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
author: cedricvidal bug portal
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
Similar issues
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 68/100
remix-run/react-router#15558 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
solana-foundation/pay-kit#341 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#607 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day