Skip to content

Latest commit

 

History

History
31 lines (20 loc) · 1.65 KB

CONTRIBUTING.md

File metadata and controls

31 lines (20 loc) · 1.65 KB
Raw

Contributing

To contribute and end up in this list:

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Test your changes to the best of your ability
  4. Commit your changes (git commit -am 'Add some feature')
    • Update the draft section of CHANGES.md with your change.
  5. Push to the branch (git push origin my-new-feature)
  6. Create a new Pull Request and await a review by at least two maintainers

EditorConfig

We use EditorConfig to maintain consistent coding styles between various editors and IDEs. You can find our settings in the .editorconfig file in the root of the project.

PR review

PRs can be merged by any member of the Podio Community organization, when the following conditions are met:

  1. All build checks are passing.
  2. At least one member (different than the PR creator) reviewed the PR.
  3. All questions/problems are addressed.

Versioning

Versioning generally follows: https://semver.org/. New versions should be cut as often as necessary. With each release CHANGES.md is updated.

Feature Requests / Issues

New feature requests can be posted as an issue (please search for similar issues first!). Generally, anyone can work on any issue. If you actively work on an issue, please leave a comment on the issue, to avoid duplicate work. Issues are resolved on a best effort basis. As this project only consists of voluntary contributors, there won't be any timelines (except if you commit yourself to one ;-)).