Public repo for Bliss OS bug reports, feature requests etc.
If you encounter a bug, want to suggest a new feature, have any kind of a problem with Bliss OS, this is the only place to report it.
If you came across a bug, we highly encourage that you report it here so we can take a look and fix it.
Before reporting a bug, we highly recommend that you read Before you submit a bug report and How to write a good bug report first.
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 if you have anything to add to it.
We have a few short tips on how to write a good bug report so the developers can have an easy time jumping on it:
- Use a clear and descriptive title for the issue.
- For example, if the issue concerns the kernel, name the issue similiar to this: [Kernel]: Short description
- 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 Bliss OS you were using.
And most important of all, make sure to fulfill as many as fields you can in our bug report template.
The more information you give us, and the more accurate it is, the sooner we'll have a fix for the bug.
- Go to the Issues section
- Click New issue
- Select the Bug report template
- Fill in the template
- Submit
If you'd like to suggest us a feature to add to Bliss OS, we highly encourage that you make a feature request here and we'll consider it.
Before submitting a feature request, we highly recommend you read Before you submit a feature request and How to write a good feature request first.
Before submitting a feature request:
- Make sure the feature isn't already added.
- If the feature you wanted to suggest already exists but you got an idea on how to improve it, make sure to mention that it already exists in the feature request.
We have a few short tips on how to write a good feature request so the developers can have an easy time jumping on it:
- Write a clear and descriptive title for the request.
- Don't hesitate to express your knowledge.
- Explain how the project could benefit of your request.
And most important of all, make sure to fulfill as many as fields you can in our feature request template.
The more information you give us, and the more accurate it is, the higher the chances are that we'll understand what exactly you're requesting.
- GitHub:
- Go to the Issues section
- Click New issue
- Select the Feature request template
- Fill in the fields
- Submit