Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Contributing Guidelines #1422

Merged
merged 8 commits into from
Jun 30, 2018
Merged

Add Contributing Guidelines #1422

merged 8 commits into from
Jun 30, 2018

Conversation

rigelrozanski
Copy link
Contributor

@rigelrozanski rigelrozanski commented Jun 28, 2018

Adapted from Tendermint figured we want this with all the external contributors coming around

  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)
  • Updated CHANGELOG.md

N/A:

  • Updated all relevant documentation in docs
  • Updated all code comments where relevant
  • Wrote tests
  • Updated Gaia/Examples

@rigelrozanski rigelrozanski added T:Docs Changes and features related to documentation. ready-for-review labels Jun 28, 2018
@rigelrozanski rigelrozanski requested a review from cwgoes June 28, 2018 00:11
@rigelrozanski rigelrozanski requested a review from ebuchman as a code owner June 28, 2018 00:11
@rigelrozanski rigelrozanski force-pushed the rigel/contributing_guide branch from 004e678 to e1fbc24 Compare June 28, 2018 00:15
CONTRIBUTING.md Outdated

Please follow standard github best practices: fork the repo, branch from the tip of develop, make some commits, and submit a pull request to develop. See the [open issues](https://github.com/cosmos/cosmos-sdk/issues) for things we need help with!

Please make sure to use `gofmt` before every commit - the easiest way to do this is have your editor run it for you upon saving a file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add make test_lint here too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed

@rigelrozanski rigelrozanski force-pushed the rigel/contributing_guide branch from e1fbc24 to 696a308 Compare June 28, 2018 00:20

Thank you for considering making contributions to Cosmos-SDK and related repositories! Start by taking a look at this [coding repo](https://github.com/tendermint/coding) for overall information on repository workflow and standards.

Please follow standard github best practices: fork the repo, branch from the tip of develop, make some commits, and submit a pull request to develop. See the [open issues](https://github.com/cosmos/cosmos-sdk/issues) for things we need help with!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we link to issues tagged with "help-wanted" (and do a better job at tagging issues "help-wanted")?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

totally

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed


We use [dep](https://github.com/golang/dep) to manage dependencies.

That said, the master branch of every Cosmos repository should just build
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we promise this can we test it automatically somehow?

Copy link
Contributor

@ValarDragon ValarDragon Jun 29, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't circle ci have to run make install in order to run the cli tests, so this already would be checked as long as master is passing tests. (Which it always should)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure we can not sure we need to though?

CONTRIBUTING.md Outdated
- the latest state of development is on `develop`
- `develop` must never fail `make test`
- no --force onto `develop` (except when reverting a broken commit, which should seldom happen)
- create a development branch either on github.com/cosmos/cosmos-sdk, or your fork (using `git add origin`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

git remote add origin?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I think so - addressed

CONTRIBUTING.md Outdated

### Pull Merge Procedure:
- ensure pull branch is rebased on develop
- run `make test` to ensure that all tests pass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make test test_cli, at least at the moment, they can also just run make

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks added

CONTRIBUTING.md Outdated
- ensure pull branch is rebased on develop
- run `make test` to ensure that all tests pass
- merge pull request
- the `unstable` branch may be used to aggregate pull merges before testing once
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting; do we have an unstable branch?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we used too - I'm deleting for now

CONTRIBUTING.md Outdated

### Release Procedure:
- start on `develop`
- run integration tests (see `test_integrations` in Makefile)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We definitely do not have a test_integrations command

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed

@codecov
Copy link

codecov bot commented Jun 29, 2018

Codecov Report

Merging #1422 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop   #1422   +/-   ##
=======================================
  Coverage       63%     63%           
=======================================
  Files          118     118           
  Lines         6573    6573           
=======================================
  Hits          4141    4141           
  Misses        2161    2161           
  Partials       271     271

cwgoes
cwgoes previously approved these changes Jun 29, 2018
Copy link
Contributor

@cwgoes cwgoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK, looks like CI is failing (strangely) though

@ValarDragon ValarDragon mentioned this pull request Jun 29, 2018
7 tasks
@cwgoes
Copy link
Contributor

cwgoes commented Jun 29, 2018

Also let's add make format - ref #1455 (comment)

Copy link
Contributor

@alexanderbez alexanderbez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few remarks, but otherwise 👍 .

- start on `develop`
- prepare changelog/release issue
- bump versions
- push to release-vX.X.X to run CI
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to elaborate on versioning conventions (especially for hotfixes)?

Copy link
Contributor

@cwgoes cwgoes Jun 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added link to https://semver.org

- before submitting a pull request, begin `git rebase` on top of `develop`

### Pull Merge Procedure:
- ensure pull branch is rebased on develop
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop* 👍

CONTRIBUTING.md Outdated

Libraries need not follow the model strictly, but would be wise to

### Development Procedure:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's implicit that the contributed work adheres to our linting standards correct (e.g. formatting, vet, imports, etc...)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a reference to make test_lint.

@cwgoes cwgoes force-pushed the rigel/contributing_guide branch from c9ee621 to c4f9d87 Compare June 30, 2018 01:51
Copy link
Contributor

@cwgoes cwgoes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@cwgoes cwgoes merged commit 2f508f5 into develop Jun 30, 2018
@cwgoes cwgoes deleted the rigel/contributing_guide branch June 30, 2018 02:04
adrianbrink pushed a commit that referenced this pull request Jul 2, 2018
* Merge pull request #1422: Add Contributing Guidelines
* cwgoes comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T:Docs Changes and features related to documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants