Page History

...

Contributing Code Changes

This section to help anyone who want to involve and contribute code to eagle project. Apache site have great documentation on how apache build the community and help the open source project. If one wants to know more detail on how apache works, he/she might want to check http://community.apache.org/.

...

• Search the user@eagle.incubator.apache.org and dev@eagle.incubator.apache.org mailing list archives for related discussions
  
• Search JIRA for existing issues: https://issues.apache.org/jira/browse/EAGLE
• Proposing a JIRA and pull request is appropriate only when a clear problem or change has been identified.

Pull Request

...

...

When you contribute code, you affirm that the contribution is your original work and that you license the work to the project under the project's open source license. Whether or not you state this explicitly, by submitting any copyrighted material via pull request, email, or other means you agree to license the material under the project's open source license and warrant that you have the legal authority to do so.

If you are ready to contribute code change. Here in this page we just focus on a consistent dev process to keep the project run smoothly. 

1. Find the existing Eagle JIRA that the change pertains to. If confirmed the change is new, create a new JIRA ticket if required with required fields
   • Issue Type
     
   • Priority
   • Affects Version
2. Fork one's own feature branch from eagle official github (https://github.com/apache/incubator-eagle/)
3. Fix bug / Develop feature in the feature branch. One might have multiple
4. After development is done, send a github pull request. Like https://github.com/apache/incubator-eagle/pull/19. NOTE: Please make sure the pull request title is in format of EAGLE-${ticket_number} ${ticket_title}, so that ASF bot could help sync the pull request comments to JIRA automatically.

...