This page describes how you can contribute to source codes of the webOS Open Source Edition (OSE) project.
Who Can Contribute?
In webOS OSE, not only developers with different interests, but also users can participate.
System UI Developers
The webOS user experience is delivered by the System UI, based on Blink and Qt. Developers can add new features and integrate other open source technologies to enhance the user experience.
Our platform portability layer (PPL), code-named Nyx, is the basis for porting webOS OSE to new architectures and hardware.
Developers can work from the Linux kernel on up to the System UI and System Services, including enhancing the PPL itself.
Enthusiast users can help with documentation, help with testing and submit bugs, and discuss features.
Here are a few things to do before jumping into the repositories.
Join the Community
Joining allows you to contribute code, participate in the forums, report and track bugs, and receive updates on the latest webOS OSE developments.
Get Familiar With the Components
Check out our repositories on GitHub to review our components and README files. If you are brand new to coding and/or to GitHub, check the Requirements.
Discuss Your Idea
We strongly suggest you check the Forum and post your ideas before you start updating components. First of all, you can find out if someone else is working on a similar idea. Furthermore, community members can help you refine your concept.
Review the Governance Model
Follow our process for how to get your contribution accepted as detailed under our Governance Model.
How We Accept Contributions
We recommend that you verify your achievement before submitting a contribution. After you are convinced, we will start reviewing your request.
Criteria for Making a Pull Request
Check the following information before you make a pull request.
I have verified that my changes do not break any of the builds.
I have provided or updated unit tests if there is an existing unit test structure for any of the components affected.
If there is no unit test structure, I have thoroughly tested my changes manually and can describe the results.
The code is in the style of the code that surrounds it.