First of all, we appreciate you considering contributing to the dahliaOS project!
To make sure your contributions go as smooth as possible, here are all the things you need to know.
Code of Conduct
dahliaOS' Code of Conduct can be found here.
This project and everyone participating in it is governed by dahliaOS' Code of Conduct and no one is exempt.
By participating, you are expected to respect and value this code.
If you notice any unacceptable behaviour, you can report it to [email protected]
How can I contribute?
Here we've explained how you can contribute to our project on GitHub but there are also many other ways to help us outside of GitHub, if you'd like to find even more ways to help us, you're always free to join our Discord and ask our team.
You can contribute to the project by:
- Reporting a bug.
- Proposing new features.
- Translating to your native language.
- Submitting a fix.
- Discussing the current state of code.
- Becoming a maintainer.
Some repositories also have Projects which contain either a to-do list or a roadmap
There are 2 ways you can report a bug, either in our Discord server by opening a ticket or by creating an issue on GitHub.
Before submitting a bug report
Before submitting a bug report, there are a few things you need to take in consideration:
- Do a bit of research and check if a similar bug has already been reported.
- If it has been reported already, add a comment to the existing one instead of submitting a new one.
How do I write a good bug report?
We have a few short tips for you on how to properly write a bug report so the developers can understand it better:
- Use a clear and descriptive title for the issue.
- Describe the steps to reproduce the bug.
- Describe what behaviour you observed after the bug occured.
- Explain what behaviour you expected to see instead and why.
- If the problem wasn't triggered by a specific action, describe what you were doing before it happened.
- Include screnshots of the bug.
- Write what version of dahliaOS you were using.
And the most important of all, make sure to fulfill all fields in our bug report template.
How do I submit a bug report?
- Go to the Issues section
- Click New issue
- Select the Bug report template
- Fill in the fields
- Go to the #bug-report channel
- Open a ticket and copy the form
- Paste and fill in the form
There are 2 ways you can submit a feature request, either by make a suggestion in our Discord server or by creating an issue with the feature request template on GitHub.
Before submitting a feature request
Before submitting a feature request, here are a few things you need to know:
- Make sure the feature isn't already added.
- Don't hesitate to express your knowledge.
- Write a clear and descriptive title for the request.
- Explain how the project could benefit of your request.
How do I submit a feature request?
- Go to the Issues section
- Click New issue
- Select the Feature request template
- Fill in the fields
- Go to the #bot-commands channel
- Type !suggestion [suggestion]
We aim to provide our software in as many languages as possible so everyone could experience it in their own native language.
For submitting translations, we use Crowdin so please do not edit the files found in the repositories.
If you're interesting in translating our project, click this link
If your language is not added, let us know and we'll add it.
Before making a translation
Before making a translation, please make sure that:
- You're fluent in the language you're translating to.
- You pay close attention to its grammar.
- You read the context (comments) some strings have.
- You used the same punctuation as the source strings.
How to translate
- Make a Crowdin account (if you already don't have one)
- Join our workspace
- Pick a project to translate (Pangolin, one of the applications etc.)
- Apply translations to the available strings
To make sure that the code you want to contribute is up to our standards, here we've written a few do's and don'ts:
- Choose expressive variable, function and class names, make it as obvious as possible of what the code is doing.
- The first line of the commit message should have the format "Category: Brief description of what's being changed". The "category" can be a subdirectory, but also something like "POSIX compliance" or "ClassName".
- Split your changes into separate commits.
- Write your commit messages in proper English, with care and punctuation.
- Submit code that's incompatible with the project licence (Apache 2.0).
- Touch anything outside the stated scope of the PR.
- Use weasel-words like "refactor" or "fix" to avoid explaining what's being changed.
- Include commented-out code.
First code contribution
If you're new to the project, you can look at repositories' issues section and the issues labeled with the "good first issue" label are perfect for your first code contribution.
Apart from code contributions, we also accept any kind of design contributions.
Here are a few repos where you can contribute designs:
- Here you can contribute your own wallpapers, make sure to read the instructions.
- Here you can contribute either modified version of existing icons or new ones.
- Here you can contribute new logos or modified current one for our project.
We also love seeing UI concepts and such designs, you can share any kind of designs in our Discord server.
PRs to our repositories are always welcome and can be a quick way to get your fix or improvement slated for the next release. In general, PRs should:
- Fix an existing issue OR add a new feature.
- Be accompanied by a complete pull request template (loaded automatically when a PR is created).
For changes that address core functionality or would require breaking changes (e.g. a major release), it's best to open an issue to discuss your proposal first. This is not required but can save time creating and reviewing changes.
How to make a proper pull request
- Fork the repository to your own GitHub account
- Clone the project to your machine
- Make your changes
- Push changes to your fork
- Open a PR in our repository and follow the PR template so that we can efficiently review the changes
What do I do after I submitted a PR?
We kindly ask everyone who has submitted a pull request to be patient and that's really all, we notice every singe new pull request so don't worry about it being ignored.
By contributing, you agree that your contributions will be licensed under the Apache 2.0 license