Skip to content

Latest commit

 

History

History
148 lines (106 loc) · 5.17 KB

CONTRIBUTING.md

File metadata and controls

148 lines (106 loc) · 5.17 KB
Raw

Contributing to Glances

Looking to contribute something to Glances ? Here's how you can help.

Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.

Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.

Using the issue tracker

The issue tracker is the preferred channel for bug reports, features requests and submitting pull requests, but please respect the following restrictions:

  • Please do not use the issue tracker for personal support requests. A official Q&A exist. Use it!

  • Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others.

Bug reports

A bug is a demonstrable problem that is caused by the code in the repository. Good bug reports are extremely helpful, so thanks!

Guidelines for bug reports:

  1. Use the GitHub issue search — check if the issue has already been reported.

  2. Check if the issue has been fixed — try to reproduce it using the latest master or develop branch in the repository.

  3. Isolate the problem — ideally create a simple test bed.

  4. Give us your test environment — Operating system name and version Glances version...

Example:

Short and descriptive example bug report title

Glances and PsUtil version used (glances -v)

Operating system description (name and version).

A summary of the issue and the OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.

  1. This is the first step
  2. This is the second step
  3. Further steps, etc.

Screenshot (if usefull)

Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).

Feature requests

Feature requests are welcome. But take a moment to 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. Please provide as much detail and context as possible.

Pull requests

Good pull requests—patches, improvements, new features—are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.

Please ask first before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.

First of all, all pull request should be done on the develop branch.

Glances uses PEP8 compatible code, so use a PEP validator before submitting your pull request. Also uses the unitaries tests scripts (unitest.py).

Similarly, when contributing to Glances's documentation, you should edit the documentation source files in the /doc/ and /man/ directories of the develop branch.

Adhering to the following process is the best way to get your work included in the project:

  1. Fork the project, clone your fork, and configure the remotes:

    # Clone your fork of the repo into the current directory
git clone https://github.com/<your-username>/glances.git
# Navigate to the newly cloned directory
cd glances
# Assign the original repo to a remote called "upstream"
git remote add upstream https://github.com/nicolargo/glances.git

  2. Get the latest changes from upstream:

    git checkout develop
git pull upstream develop

  3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix (best way is to call it issue#xxx):

    git checkout -b <topic-branch-name>

  4. Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your code is unlikely be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public.

  5. Locally merge (or rebase) the upstream development branch into your topic branch:

    git pull [--rebase] upstream develop

  6. Push your topic branch up to your fork:

    git push origin <topic-branch-name>

  7. Open a Pull Request with a clear title and description against the develop branch.

IMPORTANT: By submitting a patch, you agree to allow the project owners to license your work under the terms of the LGPL (if it includes code changes).