swagger-api / swagger-api/swagger-ui
Code of Conduct
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Though we haven't had any major issues to date here, it would be a good idea to proactively adopt a Code of Conduct in our JavaScript projects (here, Swagger-Client, and Swagger-Editor) so we can cite it when/if a problem arises.
cc: https://github.com/OAI/OpenAPI-Specification/issues/1412
cc: @webron
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
Start by reading this issue and the linked OpenAPI Specification discussion to understand the proposal and its context. The issue names Swagger UI, Swagger-Client, and Swagger-Editor, but does not identify files or tests. Done would mean adopting a Code of Conduct across the named projects; the issue does not specify which policy to use or how to coordinate that work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100