REST API Review scheduling tool should make onboarding meeting a prerequisite
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
We had an API review meeting today where the service team used public TypeSpec instead of TypeSpec Azure Core. I asked if they had had an onboarding meeting with the SDK team, where they should have gotten clear direction on how to use TypeSpec, and they said they had not.
I think we should make the onboarding meeting a required prerequisite for a REST API review meeting, and the scheduling tool should verify this prereq before allowing a meeting to be scheduled.
Contributor guide
Research direction
Start by locating the scheduling tool's REST API review flow and determine how it currently represents or checks prerequisites. Confirm with maintainers how an onboarding meeting is recorded; done means the tool verifies that prerequisite before allowing scheduling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100