Skip to content

Latest commit

 

History

History
22 lines (19 loc) · 2.63 KB

CONTRIBUTING.md

File metadata and controls

22 lines (19 loc) · 2.63 KB
Raw

Contributing Guidelines

Welcome to contributing in AnitaB Forms!

  • You can join us on AnitaB.org Open Source Zulip. Each active repo has its own stream. OSP stream is #open-source-progs.
  • To ensure a safe, positive environment for all contributors, go through the full Code of Conduct
  • Make your Commit Message descriptive including all the changes or additions you have made.
  • Please consider raising an issue before submitting a Pull Request (PR) to solve a problem, if not present in the issues list.
  • When submitting a PR, make your PR as descriptive as possible, follow the template, add screenshots and relevant information.
  • When you are finished with your work, please squash your commits otherwise we will squash them on your PR. This will help maintain a clean commit history.
  • For in-code documentation, follow this guide.
  • The full guidelines for python can be found here.

General Guidelines

  • If you’re just getting started to work on an issue labeled “First Timers Only” in any project, You can refer to additional resources available on our website.
  • In an active repository (not an archived one), choose an open issue from the issue list, claim it in the comments section or discuss it in their respective #questions stream on zulip and the maintainer will assign the issue to you.
  • After approval, you must make continuous notes on your progress in the issue while working. Remember to update your progress through comments after every 3 days, otherwise, the maintainer can reassign the issue.
  • You can't submit a PR from the base branch on your fork. Create a branch specific to the issue you're working on and send a PR from that branch.
  • Remember to follow the PR template while sending PR.
  • If you’d like to create a new issue, please go through our issue list first (open as well as closed) and make sure the issues you are reporting do not replicate the existing issues.
  • Follow the issue template while reporting new issues. Have a short description of what has gone wrong (like a root cause analysis and description of the fix), if that information is not already present in the issue.
  • If you have issues on multiple pages, report them separately. Do not combine them into a single issue.