dLeyna is an open source project where all of our development is done in the open in our mailing lists and github repositories. We encourage you to let us know what you think, submit bugs, and send us your patches!
Please carefully review our 01.org Participation Guidelines before contributing.
- Discussions occur on the email@example.com mailing list.
- Subscribe to the list at https://lists.01.org/mailman/listinfo/dleyna.
- Archives are found at http://lists.01.org/pipermail/dleyna/.
Please note that the mailing list is mainly used for release announcements and queries. Discussions about bugs, patches and new features take place primarily on github. For this reason, the mailing lists are a little quiet and it may seem as though little is happening in the dLeyna projects or that the work is being done behind closed doors. This is far from the truth! If you want to raise bugs, submit patches, suggest enhancements, comment on other people's patches, or simply get detailed information about what has changed, what is changing and why, please checkout the dLeyna issue databases.
- dLeyna-server open issues
- dLeyna-renderer open issues
- dLeyna-core open issues
- cloud-dleyna open issues
- dLeyna-control open issues
- dLeyna-connector-dbus open issues
- When you discover a problem or want to request a new feature, you can file an issue on GitHub.
- Bugs for dLeyna-server can be entered here.
- Bugs for dLeyna-renderer can be entered here.
- Bugs for dLeyna-core can be entered here.
- Bugs for cloud-dLeyna can be entered here.
- Bugs for dLeyna-control can be entered here.
- Bugs for dLeyna-connector-dbus can be entered here.
Clone our github repositories and send pull requests! Code speaks louder than words.
Separate repositories are maintained for each component under the dLeyna project.
When you are ready to send code using github.com pull requests, please follow these guidelines:
- The 01.org Git guidelines.
- Prefix commit summary with " ".
- If fixing a bug, add "Fix : " before the summary but after the component.
- Follow the standard git guidelines on commit message formatting, specifically:
- Begin the commit message with a single short (less than 50 character) line summarizing the change.
- Follow this with a blank line and then a more thorough description.
- Keep the body of the commit message less than 80 characters.
- Follow the Branching Strategy and Forking Guide.
Finally, remember to sign your code, using our Signed-off-by process.