microsoft / microsoft/api-guidelines
Issue: All down your Review Page is unanswered and unsatisfied Customers.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Description: Was just put snooping around. And went to give the Nearest Location a Review myself. But as I'm noticing with Google as well. Nobody is helping the Little People. CYBER ATTACKS are on the rise, and all your Customers are complaining.
Suggestion: Create a Team to solve all these Problems. With a Major Organization such as yours and Google. Time is of essence, and crucial to save any System.
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.
Research direction
The issue mentions only a screenshot and a general suggestion; it names no repository files, tests, or entry points. Start by reviewing the screenshot and surrounding issue context, but no concrete change or completion criteria are provided.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 5/100