Skip to content

Latest commit

 

History

History
82 lines (58 loc) · 3.25 KB

CONTRIBUTING.md

File metadata and controls

82 lines (58 loc) · 3.25 KB
Raw

Contributing to Devo

There are many ways to contribute to Devo. Here are some of them:

  1. Report bugs or request features in the issue tracker.
  2. Submit patches for bug fixes and/or new features.

Reporting bugs

Please report security issues only to support@devo.com.
This is a private email only open to Devo developers.

Well-written bug reports are very helpful, keep in mind this guideline when reporting a new bug.

  • Check the open issues to see if it has already been reported.
  • Write complete, reproducible, specific bug reports: the smaller the test case, better.
  • Includes the output of the library with all the error information

Submit patch

To be able to make a fork and the corresponding MR you have to accept Devo's CLA The process to modify one package or script is the next:

  1. Create your fork from master git branch.
  2. Add to the CHANGELOG.md, in Unreleased the tasks that you are going to take or are carrying out to be able to review at a quick glance the objective of the branch.
  3. Make your awesome code
  4. Never forget to change the changelog. 4.1 Keep a Changelog
  5. Create a Pull Request to master with correct version and tests passed.

Keep a CHANGELOG

What's a change log

A change log is a file which contains a curated, chronologically ordered list of notable changes for each version of a project.

What's the point of a change log?

To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project.

Why should I care?

Because software tools are for people. If you don't care, why are you contributing? Right, Logtrust pay you for it, but surely, there must be a kernel (ha!) of care somewhere in that lovely little brain of yours.

What makes a good change log?

A good change log sticks to these principles:

  • It's made for humans, not machines, so legibility is crucial.
  • Easy to link to any section (hence Markdown over plain text).
  • One sub-section per version.
  • List releases in reverse-chronological order (newest on top).
  • Write all dates in YYYY-MM-DD format. (Example: 2012-06-02 for June 2nd, 2012.) It's international, sensible, and language-independent.
  • Explicitly mention whether the project follows Semantic Versioning.
  • Each version should:
    • List its release date in the above format.
    • Group changes to describe their impact on the project, as follows:
    • Added for new features.
    • Changed for changes in existing functionality.
    • Deprecated for once-stable features removed in upcoming releases.
    • Removed for deprecated features removed in this release.
    • Fixed for any bug fixes.
    • Security to invite users to upgrade in case of vulnerabilities.

How can I minimize the effort required

Always have an Unreleased section at the top for keeping track of any changes.

This serves two purposes:

  • People can see what changes they might expect in upcoming releases
  • At release time, you just have to change "Unreleased" to the version number and add a new "Unreleased" header at the top.

Feel free for update and improve this document content or format.