rms/gns3-gui
1
0
Fork 0
mirror of https://github.com/GNS3/gns3-gui.git synced 2026-05-17 00:46:01 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source
This commit is contained in:
Jeremy Grossmann
2015-11-14 19:59:15 -07:00
parent 7d845c0ef8
commit b1790844f3
1 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
CONTRIBUTING.md
View File

@@ -1,37 +1,36 @@
# Contributing to GNS3
We welcome contributions and bugs reports from everyone.
We are friendly don't be afraid to make a mistake.
We are friendly so don't be afraid to ask questions.
## Bug reports
Before reporting an issue:
* check on the community forum
* check if an issue is opened on https://github.com/GNS3/gns3-gui
* check if an issue is opened on https://github.com/GNS3/gns3-server
* check our community website over at http://community.gns3.com
* check if an issue already exists on https://github.com/GNS3/gns3-gui
* check if an issue already exists on https://github.com/GNS3/gns3-server
If you are not sure it's a bug ask on community you will get a better
and faster support.
Please post on our community website if you are unsure you found a bug,
you will get faster support and be able to exchange with more users.
If you are not sure on which project you should report just report the
issue on https://github.com/GNS3/gns3-gui we will make the triage.
If you are unsure which project you should create an issue for, just do
it on https://github.com/GNS3/gns3-gui we will take care of the triage.
For bug specific to the GNS3 VM report them on:
https://github.com/GNS3/gns3-vm
For bugs specific to the GNS3 VM, please report on https://github.com/GNS3/gns3-vm
## Asking for new features
The best is to start a discussion on the community in order to get feedback
The best is to start a discussion on the community website in order to get feedback
from the whole community.
## Contributing code
We welcome code contribution from everyone including beginners.
Don't be afraid to submit half finished or poor quality we will help you.
Don't be afraid to submit a half finished or mediocre contribution and we will help you.
Don't hesitate to share your plan before starting working on it, we can help
you to find the way.
Don't hesitate to share your plans before starting working on a contribution, we can help
you to find the best approach.
### Contributors License Agreements
@@ -39,12 +38,13 @@ We at GNS3 are eager to work with you. For small changes — little bugfixes
In particular, in order for us to accept any major patches from you, you will have to electronically sign a statement that indicates two things:
You are willingly licensing your contributions under the terms of the open source license of the project that you’re contributing to.
You are legally able to license your contributions as stated.
- You are willingly licensing your contributions under the terms of the open source license of the project that you’re contributing to.
- You are legally able to license your contributions as stated.
The reason we do this is to ensure, to the extent possible, that we don’t “taint” the projects we manage with contributions that turn out to be improper. This protects everyone who wants to use the projects, including you!
More informations here: https://github.com/GNS3/cla
More information there: https://github.com/GNS3/cla
### Pull request
### Pull requests
Pull request is the better way to contributing code. We can easily discuss on the code. Do not hesitate to open the pull request soon in your development in order to get feedback.
Creating a pull request is the easiest way to contribute code. Do not hesitate to create one early when contributing for new feature in order to get our feedback.