|
| 1 | +--- |
| 2 | +title: Contributing to Project Flogo |
| 3 | +weight: 9010 |
| 4 | +--- |
| 5 | + |
| 6 | +Are you interested in contributing to Project Flogo? If so, this doc was created specifically for you! If you’re not ready to start contributing code, no problem, feel free to check out the [documentation issues](https://github.com/TIBCOSoftware/flogo/labels/kind%2Fdocs) and begin my helping enhance the documentation! |
| 7 | + |
| 8 | +Detailed instructions on contributing to the documentation and sharing your projects via the showcase can be found in our documentation, here: |
| 9 | + |
| 10 | +https://tibcosoftware.github.io/flogo/contributing/ |
| 11 | + |
| 12 | +If you’re ready and interested to make code contributions, we’ve tried to make the process as easy as possible. First, an automated contributor license agreement (CLA) has been put in place, after your first pull request, you’ll be prompted to sign the agreement, no hassles, easy and integrated right into GitHub. Also, before you begin, take a look at the general guidelines below for contributing. |
| 13 | + |
| 14 | +## How do I make a contribution? |
| 15 | + |
| 16 | +Never made an open source contribution before? Wondering how contributions work in our project? Here's a quick rundown! |
| 17 | + |
| 18 | +If you have any questions, feel free to post an issue and tag it as a question, email [email protected] or chat with the team and community: |
| 19 | + |
| 20 | +* The [project-flogo/Lobby](https://gitter.im/project-flogo/Lobby?utm_source=share-link&utm_medium=link&utm_campaign=share-link) Gitter channel should be used for general discussions, start here for all things Flogo! |
| 21 | +* The [project-flogo/developers](https://gitter.im/project-flogo/developers?utm_source=share-link&utm_medium=link&utm_campaign=share-link) Gitter channel should be used for developer/contributor focused conversations. |
| 22 | + |
| 23 | +* Find an issue that you are interested in addressing or a feature that you would like to add. Look for issues labeled `good first issue`, `kind/help-wanted` if you’re unsure where to begin. Don’t forget to checkout all of the Flogo repositories: [flogo-contrib](https://github.com/TIBCOSoftware/flogo-contrib), [flogo-lib](https://github.com/TIBCOSoftware/flogo-lib), [flogo-cli](https://github.com/TIBCOSoftware/flogo-cli) & [flogo-services](https://github.com/TIBCOSoftware/flogo-services). |
| 24 | +* Fork the repository associated with the issue to your local GitHub account. This means that you will have a copy of the repository under github-username/repository-name. |
| 25 | +* Clone the repository to your local machine using `git clone https://github.com/github-username/repository-name.git`. |
| 26 | +* Create a new branch for your fix using `git checkout -b branch-name-here`. |
| 27 | +* Make the appropriate changes for the issue you are trying to address or the feature that you want to add. |
| 28 | +* Use `git add insert-paths-of-changed-files-here` to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index. |
| 29 | +* Use `git commit -m "Insert a short message of the changes made here"` to store the contents of the index with a descriptive message. |
| 30 | +* Push the changes to the remote repository using `git push origin branch-name-here`. |
| 31 | +* Submit a pull request to the upstream repository. |
| 32 | +* Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like: "Registering mapper functions as outlined in #4352". |
| 33 | +* In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainers. |
| 34 | +* Sign the CLA if you have not yet done so in the past. |
| 35 | +* Wait for the pull request to be reviewed by a maintainers. |
| 36 | +* Make changes to the pull request if the reviewing maintainer recommends them. |
| 37 | +* Congratulations, you’ve contributed to Project Flogo, a celebration is in order! |
| 38 | + |
| 39 | +## Best Practices for Code Contributions |
| 40 | + |
| 41 | +If you're adding a new feature, such as an activity or trigger, please follow the best practices below: |
| 42 | + |
| 43 | +* Provide test cases for your feature |
| 44 | +* Package name should match your activity dir. For example, if a new activity is placed in activity/awesomeActivity then the go package name should match. |
| 45 | + * Follow Go best practices for package names: https://blog.golang.org/package-names |
| 46 | +* Run gofmt to format your code |
| 47 | +* Leverage activity trigger metadata (activity/trigger.json) |
| 48 | + * Use metadata ‘required’ attribute when the attribute is required |
| 49 | + * Supply a default value in metadata not code (use the value attribute) |
| 50 | +* Activity Eval() should return `true` only when completed successfully & err should be returned when an error occurs |
| 51 | + |
| 52 | +Refer to the [Flogo Documentation](https://tibcosoftware.github.io/flogo/) for more guidence and help. |
| 53 | + |
| 54 | +Don't forget, if you build an awesome Activity or Trigger you can [share your work via the Flogo Showcase](https://tibcosoftware.github.io/flogo/contributing/) rather than contributing to [flogo-contrib](https://github.com/TIBCOSoftware/flogo-contrib). |
0 commit comments