From 9720b4939d144f865581ae4675884a28fe0486f2 Mon Sep 17 00:00:00 2001 From: Cam Findlay Date: Fri, 6 Feb 2015 20:37:50 +1300 Subject: [PATCH] DOCS Fixed link on issues and bugs --- docs/en/05_Contributing/00_Issues_and_Bugs.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/en/05_Contributing/00_Issues_and_Bugs.md b/docs/en/05_Contributing/00_Issues_and_Bugs.md index 3ce05e953..a5d45cdf9 100644 --- a/docs/en/05_Contributing/00_Issues_and_Bugs.md +++ b/docs/en/05_Contributing/00_Issues_and_Bugs.md @@ -16,11 +16,11 @@ well written bug reports can be half of the solution already! Before submitting a bug: - * Ask for assistance on the [forums](http://silverstripe.org/forums), [core mailinglist](http://groups.google.com/group/silverstripe-dev) or on [IRC](http://silverstripe.org/irc) if you're unsure if its really a bug. + * Ask for assistance on the [forums](http://www.silverstripe.org/community/forums/), [core mailinglist](http://groups.google.com/group/silverstripe-dev) or on [IRC](http://irc.silverstripe.org/) if you're unsure if its really a bug. * Search for similar, existing tickets * Is this a security issue? Please follow our separate reporting guidelines below. - * Is this a issue with the core framework or cms? Modules have their own issue trackers (see [silverstripe.org/modules](http://www.silverstripe.org/modules)) - * Try to reproduce your issue on a [clean installation](http://doc.silverstripe.org/framework/en/installation/composer#using-development-versions), maybe the bug has already been fixed on an unreleased branch? + * Is this a issue with the core framework or cms? Modules have their own issue trackers (see [silverstripe.org/modules](http://www.silverstripe.org/modules/)) + * Try to reproduce your issue on a [clean installation](/getting_started/composer#using-development-versions), maybe the bug has already been fixed on an unreleased branch? * The bugtracker is not the place to discuss enhancements, please use the forums or mailinglist. Only log enhancement tickets if they gather a large interest in the community and the enhancement is likely to be implemented in the next couple of months. @@ -30,7 +30,7 @@ If the issue does look like a new bug: * [Create a new ticket](https://github.com/silverstripe/silverstripe-framework/issues/new) * Describe the steps required to reproduce your issue, and the expected outcome. Unit tests, screenshots and screencasts can help here. * Describe your environment as detailed as possible: SilverStripe version, Browser, PHP version, Operating System, any installed SilverStripe modules. - * *(optional)* [Submit a pull request](/misc/contributing/code) which fixes the issue. + * *(optional)* [Submit a pull request](/contributing/code/#step-by-step-from-forking-to-sending-the-pull-request) which fixes the issue. Lastly, don't get your hopes up too high. Unless your issue is a blocker affecting a large number of users, don't expect SilverStripe developers to jump @@ -42,24 +42,24 @@ problem can collaborate with you to develop a fix.
Please don't file "feature requests" as Github issues. If there's a new feature you'd like to see in SilverStripe, you either need to write it yourself (and -[submit a pull request](/misc/contributing/code)) or convince somebody else to +[submit a pull request](/contributing/code/#step-by-step-from-forking-to-sending-the-pull-request) or convince somebody else to write it for you. Any "wishlist" type issues without code attached can be expected to be closed as soon as they're reviewed.
In order to gain interest and feedback in your feature, we encourage you to -present it to the community through the [forums](http://silverstripe.org/forums), +present it to the community through the [forums](http://www.silverstripe.org/community/forums), [core mailinglist](http://groups.google.com/group/silverstripe-dev) or on -[IRC](http://silverstripe.org/irc). +[IRC](http://irc.silverstripe.org/). ## Reporting Security Issues -Report security issues to [security@silverstripe.com](mailto:security@silverstripe.com). -See our "[Release Process](release-process)" documentation for more info, and -read our guide on [how to write secure code](/topics/security). +Report security issues to [security@silverstripe.org](mailto:security@silverstripe.org). +See our "[Release Process](/contributing/release_process/#security-releases)" documentation for more info, and +read our guide on [how to write secure code](/developer_guides/security/secure_coding/). ## Sharing your Opinion -* [silverstripe.org/forums](http://silverstripe.org/forums): Forums on silverstripe.org -* [silverstripe-dev](http://groups.google.com/group/silverstripe-dev): Core development mailinglist -* [silverstripe-documentation](http://groups.google.com/group/silverstripe-translators): Translation team mailing list +* [silverstripe.org/forums](http://www.silverstripe.org/community/forums/): Forums on silverstripe.org +* [silverstripe-dev](http://groups.google.com/group/silverstripe-dev/): Core development mailinglist +* [silverstripe-documentation](http://groups.google.com/group/silverstripe-translators/): Translation team mailing list