Skip to content

Latest commit

 

History

History
159 lines (117 loc) · 6.14 KB

CONTRIBUTING.md

File metadata and controls

159 lines (117 loc) · 6.14 KB
Raw

Contributing to Rocfor.js

Thanks to 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 (use Stack Overflow or Stack Overflow en español or other resources to this cases).

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

Bug reports

A bug is a probable possibility in the project. Good bug reports are extremely helpful for all end users of the library - thank you for your contribution!

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 development branch in the repository.

  3. Isolate the problem — create a reduced test case and a live example.

A good bug report shouldn't leave others needing to find you up for more information. Please try to be as detailed as possible in your report.

  • What is your environment?
  • What steps will reproduce the issue?
  • What browser(s) and OS experience the problem?
  • What would you expect to be the outcome?

All these details will help people to fix any potential bugs.

Example:

Short and descriptive example bug report title

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

  1. A bug is generated in line #
  2. The bug caused by: ...
  3. Possible solutions : ...
  4. This is the first step
  5. This is the second step
  6. Further steps, etc.

<url> - a link to the reduced test case

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.

Please adhere to the coding conventions used throughout a project (indentation, accurate comments, .editorconfig, etc.) and any other requirements (such as test coverage).

Follow this process if you'd like your work considered for inclusion 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>/rocfor
	# Navigate to the newly cloned directory
	$ cd rocfor
	# Assign the original repo to a remote called "rocfor-<your-username>"
	$ git remote add rocfor-<your-username> https://github.com/roccouu/rocfor
  2. If you cloned a while ago, get the latest changes from rocfor-: 
    	$ git checkout <dev-branch>
	$ git pull rocfor-<your-username> <dev-branch>
  3. The folder where to work is always "project-dev".
  4. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix: 
    	$ git checkout -b <topic-branch-name>
  5. Add relevant tests to cover the change.
  6. Make sure test-suite passes: npm test
  7. 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.
  8. Locally merge (or rebase) the upstream development branch into your topic branch: 
    	$ git pull [--rebase] rocfor-<your-username> <dev-branch>
  9. Push your topic branch up to your fork: 
    	$ git push origin <topic-branch-name>
  10. Open a Pull Request with a clear title and description.

Conventions of commit messages

Addding files on repo

$ git commit -m "Add filename"

Updating files on repo

$ git commit -m "Update filename, filename2, filename3"

Removing files on repo

$ git commit -m "Remove filename"

Renaming files on repo

$ git commit -m "Rename filename"

Fixing errors and issues on repo

$ git commit -m "Fixed #issuenumber Message about this fix"

Adding features on repo

$ git commit -m "Add Feature: nameoffeature Message about this feature"

Updating features on repo

$ git commit -m "Update Feature: nameoffeature Message about this update"

Removing features on repo

$ git commit -m "Remove Feature: nameoffeature Message about this"

IMPORTANT:

  • Please, always respect the elements by default contained in the .gitignore project file.
  • By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by the project.