Skip to content
This repository has been archived by the owner on Oct 28, 2021. It is now read-only.

aligning README.md and CONTRIBUTING.md to FINOS project blueprint language #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion CONTRIBUTING.md → .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,12 @@ Thanks for your interest in the project! Here is some basic information about ho

# Contributor License Agreement (CLA)
All contributions to [Symphony Software Foundation](https://symphony.foundation/) projects must be made under a [Contributor License Agreement](https://symphonyoss.atlassian.net/wiki/display/FM/Legal+Requirements#LegalRequirements-ContributorLicenseAgreement) that authorizes the Foundation to distribute your code under the Apache License. Contributions must also meet the Foundation's [license and notice requirements](https://symphonyoss.atlassian.net/wiki/display/FM/Legal+Requirements) that must also be met.

_NOTE:_ Commits and pull requests to FINOS repositories will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS. Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS Clabot tool. Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.

Pull requests (PRs) submitted to the project cannot be accepted until you have a CLA in place with the Foundation.

*Need an ICLA? Unsure if you are covered under an existing CCLA? Email [[email protected]](mailto:[email protected])*

# Contributing Issues

Expand All @@ -29,9 +33,15 @@ To make review of PRs easier, please:
* For documentation contributions, follow the general structure, language, and tone of the existing docs.
* Keep PRs small and cohesive - if you have multiple contributions, please submit them as independent PRs.
* Reference issue #s if your PR has anything to do with an issue (even if it doesn't address it).
* Minimize non-functional changes (e.g. whitespace shenanigans).
* Minimize non-functional changes (e.g. whitespace).
* Ensure all new files include a header comment block containing the [Apache License v2.0 and your copyright information](http://www.apache.org/licenses/LICENSE-2.0#apply).
* If necessary (e.g. due to 3rd party dependency licensing requirements), update the NOTICE file with any required attribution or other notices
* If your contribution includes source code for any Category B-licensed dependencies, add an appropriate notice to this CONTRIBUTING file

## Commit and PR Messages

* **Reference issues, wiki pages, and pull requests liberally!**
* Use the present tense ("Add feature" not "Added feature")
* Use the imperative mood ("Move button left..." not "Moves button left...")
* Limit the first line to 72 characters or less

4 changes: 2 additions & 2 deletions NOTICE
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Symphony REST Tools
Copyright 2017 Symphony Communication Services, LLC.
Symphony REST Tools - FINOS
Copyright 2017-2019 Symphony Communication Services, LLC.
http://symphony.com/

========================================================================
Expand Down
13 changes: 13 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -189,4 +189,17 @@ https://symphonyoss.github.io/symphony-rest-tools/GettingStarted
## Contribute
This project was initiated at [Symphony Communication Services, LLC.](https://www.symphony.com) and has been developed as open-source from the very beginning.

1. Fork it (<https://github.com/symphonyoss/symphony-rest-tools/fork>)
2. Create your feature branch (`git checkout -b feature/fooBar`)
3. Read our [contribution guidelines](.github/CONTRIBUTING.md) and [Community Code of Conduct](https://www.finos.org/code-of-conduct)
4. Commit your changes (`git commit -am 'Add some fooBar'`)
5. Push to the branch (`git push origin feature/fooBar`)
6. Create a new Pull Request

Contributions are accepted via GitHub pull requests. All contributors must be covered by contributor license agreements to comply with the [Code Contribution Process](https://symphonyoss.atlassian.net/wiki/display/FM/Code+Contribution+Process).

## License

Copyright 2017-2019 Symphony Communication Services, LLC.

The code in this repository is distributed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0).