MirrorDimension/ocelot-desktop
1
0
Fork 0
mirror of https://gitlab.com/cc-ru/ocelot/ocelot-desktop.git synced 2025-12-19 18:49:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

Correct the weird wording in CONTRIBUTING.md

Browse Source
This commit is contained in:
Fingercomp 2023-10-19 13:12:54 +07:00
parent 2e02af98a3
commit 13b5609b9b
No known key found for this signature in database
GPG Key ID: BBC71CEE45D86E37
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -34,7 +34,7 @@ Don't worry if you make a mistake — we can always move the issue to the approp
### Feature requests
Ocelot Desktop wouldn't become so great if nobody was asking for features!
However, if you'd like to ask for one, keep in mind that we are a small group of developer volunteering our time and attention to this project.
Many issues stayed open for several years before somebody went ahead and finally realized the asked feature.
Many issues stayed open for several years before somebody went ahead and implemented the requested features.
So we'll appreciate it if you tell us why you're requesting a feature and how you would use it if it were added.
Seeing a clear use-case helps us stay on track if we get to implementing it — and it's also a great source of motivation for developers since this shows how, concretely, their efforts can help you. :)
@ -49,8 +49,8 @@ This is, of course, but a hopeless dream, and it does crash sometimes.
**Please do not ignore crashes** (unless you're sure Ocelot is not at fault): we realize this is the most disruptive kind of bug, and we'd like to fix it as soon as possible.
If you're reporting a bug, please **describe your actions** preceding it: was it pressing a button? loading a workspace? or something else?
Ideally (if you can reproduce the issue — that is, trigger it again), you should tell us step-by-step what you did that lead to the problem.
But we understand that it's sometimes just impossible — we'd rather have a report alerting us of the bug than be completely oblivious to it.
Ideally (if you can reproduce the issue — that is, trigger it again), you should tell us step-by-step what you did that led to the problem.
But we understand that it's simply impossible sometimes — still, we'd rather have a report alerting us of the bug than be completely oblivious to it.
Please attach logs if you have them (`%APPDATA%/Ocelot/Logs/Desktop.log` on Windows, `~/.local/share/ocelot/desktop.log` on Linux) — and **especially** if it's a crash.
Logs don't always help us, but when they do, they help tremendously: a crash would have a stack trace pointing to the exact line of code that triggered it, for example.