It is warmly welcomed if you have interest to hack on Dragonfly. First, we encourage this kind of willing very much. And here is a list of contributing guide for you.
- Reporting security issues
- Reporting general issues
- Code and doc contribution
- Engage to help anything
Security issues are always treated seriously. As our usual principle, we discourage anyone to spread security issues. If you find a security issue of Dragonfly, please do not discuss it in public and even do not open a public issue. Instead we encourage you to send us a private email to [email protected] to report this.
To be honest, we regard every user of Dragonfly as a very kind contributor. After experiencing Dragonfly, you may have some feedback for the project. Then feel free to open an issue via NEW ISSUE.
Since we collaborate project Dragonfly in a distributed way, we appreciate WELL-WRITTEN, DETAILED, EXPLICIT issue reports. To make the communication more efficient, we wish everyone could search if your issue is an existing one in the searching list. If you find it existing, please add your details in comments under the existing issue instead of opening a brand new one.
To make the issue details as standard as possible, we setup an ISSUE TEMPLATE for issue reporters. You can find three kinds of issue templates there: question, bug report and feature request. Please BE SURE to follow the instructions to fill fields in template.
There are lot of cases when you could open an issue:
- bug report
- feature request
- performance issues
- feature proposal
- feature design
- help wanted
- doc incomplete
- test improvement
- any questions on project
- and so on
Also we must remind that when filing a new issue, please remember to remove the sensitive data from your post. Sensitive data could be password, secret key, network locations, private business data and so on.
Every action to make project Dragonfly better is encouraged. On GitHub, every improvement for Dragonfly could be via a PR (short for pull request).
- If you find a typo, try to fix it!
- If you find a bug, try to fix it!
- If you find some redundant codes, try to remove them!
- If you find some test cases missing, try to add them!
- If you could enhance a feature, please DO NOT hesitate!
- If you find code implicit, try to add comments to make it clear!
- If you find code ugly, try to refactor that!
- If you can help to improve documents, it could not be better!
- If you find document incorrect, just do it and fix that!
- ...
Actually it is impossible to list them completely. Just remember one princinple:
WE ARE LOOKING FORWARD TO ANY PR FROM YOU.
Since you are ready to improve Dragonfly with a PR, we suggest you could take a look at the PR rules here.
- Workspace Preparation
- Branch Definition
- Commit Rules
- PR Description
- Developing Environment
- Golang Package Vendoring Mechanism
To put forward a PR, we assume you have registered a GitHub ID. Then you could finish the preparation in the following steps:
-
FORK Dragonfly to your repository. To make this work, you just need to click the button Fork in right-left of dragonflyoss/Dragonfly main page. Then you will end up with your repository in
https://github.com/<your-username>/Dragonfly, in whichyour-usernameis your GitHub username. -
CLONE your own repository to develop locally. Use
git clone https://github.com/<your-username>/Dragonfly.gitto clone repository to your local machine. Then you can create new branches to finish the change you wish to make. -
Set Remote upstream to be
https://github.com/dragonflyoss/Dragonfly.gitusing the following two commands:
git remote add upstream https://github.com/dragonflyoss/Dragonfly.git
git remote set-url --push upstream no-pushing
With this remote setting, you can check your git remote configuration like this:
$ git remote -v
origin https://github.com/<your-username>/Dragonfly.git (fetch)
origin https://github.com/<your-username>/Dragonfly.git (push)
upstream https://github.com/dragonflyoss/Dragonfly.git (fetch)
upstream no-pushing (push)
Adding this, we can easily synchronize local branches with upstream branches.
Right now we assume every contribution via pull request is for branch master in Dragonfly. Before contributing, be aware of branch definition would help a lot.
As a contributor, keep in mind again that every contribution via pull request is for branch master. While in project Dragonfly, there are several other branches, we generally call them rc branches, release branches and backport branches.
Before officially releasing a version, we will checkout a rc(release candidate) branch. In this branch, we will test more than branch master.
When officially releasing a version, there will be a release branch before tagging. After tagging, we will delete the release branch.
When backporting some fixes to existing released version, we will checkout backport branches. After backporting, the backporting effects will be in PATCH number in MAJOR.MINOR.PATCH of SemVer.
Actually in Dragonfly, we take two rules serious when committing:
Commit message could help reviewers better understand what is the purpose of submitted PR. It could help accelerate the code review procedure as well. We encourage contributors to use EXPLICIT commit message rather than ambiguous message. In general, we advocate the following commit message type:
- docs: xxxx. For example, "docs: add docs about storage installation".
- feature: xxxx.For example, "feature: make result show in sorted order".
- bugfix: xxxx. For example, "bugfix: fix panic when input nil parameter".
- style: xxxx. For example, "style: format the code style of Constants.java".
- refactor: xxxx. For example, "refactor: simplify to make codes more readable".
- test: xxx. For example, "test: add unit test case for func InsertIntoArray".
- chore: xxx. For example, "chore: integrate travis-ci". It's the type of mantainance change.
- other readable and explicit expression ways.
On the other side, we discourage contributors from committing message like the following ways:
fix bugupdateadd doc
Commit content represents all content changes included in one commit. We had better include things in one single commit which could support reviewer's complete review without any other commits' help. In another word, contents in one single commit can pass the CI to avoid code mess. In brief, there are two minor rules for us to keep in mind:
- avoid very large change in a commit;
- complete and reviewable for each commit.
No matter commit message, or commit content, we do take more emphasis on code review.
PR is the only way to make change to Dragonfly project files. To help reviewers better get your purpose, PR description could not be too detailed. We encourage contributors to follow the PR template to finish the pull request.
As a contributor, if you want to make any contribution to Dragonfly project, we should reach an agreement on the version of tools used in the development environment. Here are some dependents with specific version:
- golang : v1.10.4
- swagger : 0.17.1
- markdownlint : v0.5.0
- misspell : latest
- shellCheck : latest
- docker: latest
When you develop the Dragonfly project at the local environment, you should use subcommands of Makefile to help yourself to check and build the latest version of Dragonfly. For the convenience of developers， we use the docker to build Dragonfly. It can reduce problems of the developing environment.
Dragonfly uses tool govendor to vendor packages in its own repository. When hacking Dragonfly's code, any developer can use the common way to install govendor, and here the community suggest to use govendor v1.0.8 to collaborate:
go get -u github.com/kardianos/govendorHere are three cases to manage vendored packages with govendor:
In Dragonfly, when vendoring a package, we take the version of it very seriously. Therefore, almostly every time we use govendor, we explicitly pick the specified commit ID or tag.
As a result, we seldom use the command govendor add github.com/a/b. Instead, we always make use of govendor add github.com/a/b@8ac97434144a8b58bd39576fc65be42d90257b04 or govendor add github.com/a/[email protected].
When using govendor, there are still some tiny tips for us:
- If you pick commit id
8ac97434144a8b58bd39576fc65be42d90257b04of packagegovendor add github.com/a/b, then for this package in yourGOPATH, you have to checkout to this specified commit ID before usinggovendor. - When there are go files and directories which are all you need to vendor under the root path of package
govendor add github.com/a/b, you have to use flag^to include them all using commandgovendor add github.com/a/b/^@8ac97434144a8b58bd39576fc65be42d90257b04. - Assuming that package
github.com/a/balso has a directoryvendor, so-called nesting vendor, in most cases we remain these packages.
Removal of vendored package will take no effort. Just execute the following the command:
govendor remove github.com/a/bUpdate of vendored packages will take a little bit more effort than removal. Although you could execute govendor update github.com/a/b@a4bbce9fcae005b22ae5443f6af064d80a6f5a55 in which a4bbce9fcae005b22ae5443f6af064d80a6f5a55 is the new commit ID, you should still keep it in mind that for this package in your GOPATH, you have to checkout to this specified commit ID before using govendor update.
We choose GitHub as the primary place for Dragonfly to collaborate. So the latest updates of Dragonfly are always here. Although contributions via PR is an explicit way to help, we still call for any other ways.
- reply to other's issues if you could;
- help solve other user's problems;
- help review other's PR design;
- help review other's codes in PR;
- discuss about Dragonfly to make things clearer;
- advocate Dragonfly technology beyond GitHub;
- write blogs on Dragonfly and so on.
In a word, ANY HELP IS CONTRIBUTION.