bkinnightskytw
/
ethercat
mirror of https://gitlab.com/bkinnightskytw/ethercat.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ethercat/CONTRIBUTING.md

7.6 KiB
Raw Permalink Blame History

Contributing to the IgH EtherCAT Master

First off, thanks for taking the time to contribute! ❤️

All types of contributions are encouraged and valued. See the
Table of Contents for different ways to help and details
about how this project handles them. Please make sure to read the relevant
section before making your contribution. It will make it a lot easier for us
maintainers and smooth out the experience for all involved. The community looks
forward to your contributions. 🎉

And if you like the project, but just don't have time to contribute, that's
fine. There are other easy ways to support the project and show your
appreciation, which we would also be very happy about:

  • Star the project
  • Write something about it in the social media
  • Refer this project in your project's readme
  • Mention the project at local meetups and tell your friends/colleagues

Table of Contents

I Have a Question

If you want to ask a question, we assume that you have read the available
Documentation.

Before you ask a question, it is best to search for existing
Issues and in the mailing
list archives for posts that
might help you.

In case you have found a suitable issue and still need clarification, you can
write your question in this issue. It is also advisable to search the internet
for answers first.

If you then still feel the need to ask a question and need clarification, we
recommend the following:

  • If it is a question about getting a certain device to work, please ask you
    question on our mailing lists.
  • If f you think the problem lies in the master itself, open an
    Issue.
  • Provide as much context as you can about what you're running into.
  • Provide project and platform versions: EtherCAT master version, Linux Kernel
    version, the Linux distribution and the used Ethernet driver (generic,
    8319too, ccat, ...), depending on what seems relevant.

We will then take care of the issue as soon as possible.

I Want To Contribute

Legal Notice

When contributing to this project, you must agree that you have authored 100%
of the content, that you have the necessary rights to the content and that
the content you contribute may be provided under the project licence.

Reporting Bugs

Before Submitting a Bug Report

A good bug report shouldn't leave others needing to chase you up for more
information. Therefore, we ask you to investigate carefully, collect
information and describe the issue in detail in your report. Please complete
the following steps in advance to help us fix any potential bug as fast as
possible.

  • Make sure that you are using the latest version.
  • Determine if your bug is really a bug and not an error on your side e.g.
    using incompatible environment components/versions (Make sure that you have
    read the documentation. If you are looking for
    support, you might want to check this section).
  • To see if other users have experienced (and potentially already solved) the
    same issue you are having, check if there is not already a bug report
    existing for your bug or error in the
    bug tracker.
  • Also make sure to search the internet to see if
    users outside of the GitLab community have discussed the issue.
  • Collect information about the bug:
    • Stack trace (Traceback)
    • OS, Platform and Version (Linux Kernel, Distribution, x86, ARM, ...)
    • The Ethernet driver use are using (generic, 8139too, ccat, ...)
    • Can you reliably reproduce the issue? And can you also reproduce it with
      older versions?

How Do I Submit a Good Bug Report?

You must never report security related issues, vulnerabilities or bugs
including sensitive information to the issue tracker, or elsewhere in public.
Instead sensitive bugs must be sent by email to fp@igh.de.

We use GitLab issues to track bugs and errors. If you run into an issue with
the project:

  • Open an Issue. (Since
    we can't be sure at this point whether it is a bug or not, we ask you not to
    talk about a bug yet and not to label the issue.)
  • Explain the behavior you would expect and the actual behavior.
  • Please provide as much context as possible and describe the reproduction
    steps     that someone else can follow to recreate the issue on their own. This
    usually includes your code. For good bug reports you should isolate the
    problem and create a reduced test case.
  • Provide the information you collected in the previous section.

Once it's filed:

  • The project team will label the issue accordingly.

Suggesting Enhancements

This section guides you through submitting an enhancement suggestion for IgH
EtherCAT Master, including completely new features and minor improvements to
existing functionality. Following these guidelines will help maintainers and
the community to understand your suggestion and find related suggestions.

Before Submitting an Enhancement

  • Make sure that you are using the latest version.
  • Read the documentation carefully and find out if
    the functionality is already covered, maybe by an individual configuration.
  • Perform a search to see if
    the enhancement has already been suggested. If it has, add a comment to the
    existing issue instead of opening a new one.
  • Find out whether your idea fits with the scope and aims of the project. It's
    up to you to make a strong case to convince the project's developers of the
    merits of this feature. Keep in mind that we want features that will be
    useful to the majority of our users and not just a small subset. If you're
    just targeting a minority of users, consider writing an add-on/plugin
    library.

How Do I Submit a Good Enhancement Suggestion?

Enhancement suggestions are tracked as
GitLab issues.

  • Use a clear and descriptive title for the issue to identify the
    suggestion.
  • Provide a step-by-step description of the suggested enhancement in as
    many details as possible.
  • Describe the current behavior and explain which behavior you expected
    to see instead     and why. At this point you can also tell which alternatives
    do not work for you.
  • You may want to include screenshots or screen recordings which help you
    demonstrate the steps or point out the part which the suggestion is related
    to.
  • Explain why this enhancement would be useful to most IgH EtherCAT Master
    users. You may also want to point out the other projects that solved it
    better and which could serve as inspiration.

Styleguides

There is a coding style document next to this guide.

Attribution

This guide is based on the contributing.md!