microsoft / microsoft/vscode-loc
Should README be updated about contributing?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 750
- Forks
- 398
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 3
Description
Considering the string from Readme's Contributing section mentions only contribution can be made via Microsoft's now decommisioned platform. (decommissioned according to the MLCP website and microsoft/Localization being either fully removed or private to github org)
I haven't seen anything about progress on a new platform, whether building it or moving to another existing platform, but as one can see from the commit history, the project is still being translated.
-
Is there any plans about allowing community translations again? Is it an invite only community now or is it now fully internal to Microsoft?
-
If there is no current plan on allowing community translations, how should the community help on mistranslations and typos?
Is the current method of opening PRs and issues allowed considering the exception of the current situation? -
Shouldn't the README get updated about those points I mentioned?
Feel free to add more questions you'd like to get answered, provided it's within topic.
If there is non-vague answers about those questions, I also would like the README to get updated with those answers.
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.
Research direction
Start with the Contributing section in README.md and review the linked MLCP website and the project's recent commit history. Confirm the current policy for community translations, typo or mistranslation reports, and pull requests with maintainers; done means updating README.md with those agreed answers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100