Commit 21203100 authored by Marvin Scholz's avatar Marvin Scholz
Browse files

Update links to bugtracker

parent 777ce104
......@@ -8,7 +8,8 @@ permalink: /contribute/
## Reporting bugs
If you find a bug in Icecast, you can report it on our [Bugtracker](https://trac.xiph.org/newticket) (make sure it's not a duplicate).
If you find a bug in Icecast, you can report it on our [Bugtracker](https://gitlab.xiph.org/xiph/icecast-server/issues)
(make sure it's not a duplicate).
Please make sure that you include all necessary information for us to reproduce the bug and describe it as
good a possible. If relevant please attach the `error.log` and your `icecast.xml` (without passwords), so we
......@@ -30,8 +31,8 @@ of general nature and not something that only you might need.
You can contribute to the Icecast development by sending us patches that fix bugs or implement new features. Note that
new features should be discussed before you start working on them (read above).
You can either send us patches through the [Bugtracker](https://trac.xiph.org/newticket), just create a ticket that describes what your patchs adds/fixes and
attach the patch to it.
You can either send us patches through the [Bugtracker](https://gitlab.xiph.org/xiph/icecast-server/issues), just create
a ticket that describes what your patchs adds/fixes and attach the patch to it.
If you prefer you can also send us the patch to our [icecast-dev](/contact#mailing-list) mailinglist.
## Guidelines for patches
......@@ -39,4 +40,4 @@ When submitting patches, you should send a separate patch for each bugfix/featur
## GitHub Pull Requests
While we have a [GitHub repository](https://github.com/xiph/Icecast-Server) and it is possible to send us pull requests there, it may take a long time until we notice them, since GitHub is just used as a mirror. Therefore we strongly advise that you send us your patches as a Bugtracker ticket attachment or on the mailinglist.
</div>
\ No newline at end of file
</div>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment