Skip to content

Latest commit

 

History

History
40 lines (32 loc) · 2.81 KB

CONTRIBUTING_EN.md

File metadata and controls

40 lines (32 loc) · 2.81 KB

How to contribute

Contributors, thank you for participating in this project!

I'm Seki, the development manager. If you have any questions, feel free to ask me on Slack etc.

This page shows how you can contribute to the development of this site.

Comments on Issues and Pull Requests

  • Feel free to comment on any Issues! Questions and suggestions are also welcome.
  • Please search existing issues to make sure there is no similar issues before making a new issue.
  • When you send a new Pull Request, please specify a related issue ID. We don't accept Pull Requests which has no issue ID.
  • Note that Issues for improvement suggestions (labeled with improve) may not be always accepted (especially ones for UI)
  • All issues and Pull requests including major content changes such as language expression or the UI are subject to the organizer's review. They may not necessarily be always accepted.
  • The Issue with waiting label is under review by the organizer. The implementation should be refrained until the requirement is fixed.
  • We appreciate if you give priority to the issues labelled [good first issue / help wanted / bug]

How to participate in communications

  • If you do not have a "Code for Japan" Slack account, please register here
  • Join #covid19 Channel

For participation

  • Please read Principle / Code of Conduct before participating in development.
  • For communication, please also check Code for Japan's Code of Conduct.
  • If you plan to work on an issue, please leave a comment behind to give a heads-up.
  • good first issue label is recommended for beginners.
  • If you can't make any progress for more than half a day, make sure that others can take over your work.
  • If an issue is not updated for more than one day, we may remove the assignment.
  • A Draft Pull Request is recommended for any work in progress, so that everyone understands the situation.
  • Please discuss questions related to an Issue in the Issue comments instead of on Slack.
  • We also accept suggestions! Please feel free to create new issues.

Development information

Updates to this document are also welcome!