... | ... | @@ -10,7 +10,7 @@ Issues are useful for developers because they show us what users want, and what |
|
|
## Why should I open an issue?
|
|
|
|
|
|
You can open an issue to:
|
|
|
* Report a bug (*NOTE:* If you have a segfault please read [this](./ReportingSegfault) before reporting).
|
|
|
* Report a bug (*NOTE:* If you have a segfault please read [this](/ReportingSegfault) before reporting).
|
|
|
* Ask for a new feature
|
|
|
* Add a task
|
|
|
|
... | ... | @@ -39,4 +39,4 @@ In a few words, explain why you opened this issue. You can chose from the templa |
|
|
|
|
|
## After that
|
|
|
|
|
|
Wait and hope for some developer to comment on that issue and/or fix your issue. If you do not understand some vocabularies read [that](./GajimDevsSlang). If you've enabled e-mail notifications, you will receive an e-mail when your issue is updated/closed. Off course you can also write a patch yourself and submit a merge request. |
|
|
\ No newline at end of file |
|
|
Wait and hope for some developer to comment on that issue and/or fix your issue. If you do not understand some vocabularies read [this](/development/gajimdevsslang). If you've enabled e-mail notifications, you will receive an e-mail when your issue is updated/closed. Off course you can also write a patch yourself and submit a merge request. |
|
|
\ No newline at end of file |