tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #9224 from open-sausages/pulls/4/docs-uservoice-removal

Browse Source 
DOCS Remove uservoice mentions
This commit is contained in:
Guy Marriott 2019-09-06 16:26:26 +12:00 committed by GitHub
commit 25de735a9f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/05_Contributing/00_Issues_and_Bugs.md
View File

@ -20,7 +20,7 @@ Before submitting a bug:
Note that [documentation issues](https://github.com/silverstripe/silverstripe-framework/issues) are tracked in "framework" as well. Note that [documentation issues](https://github.com/silverstripe/silverstripe-framework/issues) are tracked in "framework" as well.
* 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? * 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 bugtracker is not the place to discuss enhancements, please use
[UserVoice](http://silverstripe.uservoice.com) and our [community channels](https://www.silverstripe.org/community). the ["feature ideas" forum category](https://forum.silverstripe.org/c/feature-ideas) and our [community channels](https://www.silverstripe.org/community).
Only log enhancement tickets if they gather a large interest in the community 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. and the enhancement is likely to be implemented in the next couple of months.

2
docs/en/05_Contributing/03_Request_for_comment.md
View File

@ -39,7 +39,7 @@ Once complete submit the RFC in the prescribed format above as a GitHub issue as
## What next? ## What next?
The RFC will be raised and discussed by the core committers in the monthly Google Hangout sessions, a vote for accepting the RFC will be taken requiring a majority vote (with at least a quorum of more than half of the core committers present). The RFC will be raised and discussed by the core committers in the monthly Google Hangout sessions, a vote for accepting the RFC will be taken requiring a majority vote (with at least a quorum of more than half of the core committers present).
Once approved it will be announced on the [developer list](https://groups.google.com/forum/#!forum/silverstripe-dev) and if relevant, [UserVoice](http://silverstripe.uservoice.com) and [Roadmap](https://www.silverstripe.org/software/roadmap) will be updated. This now means that if a pull request meeting the idea set out in the RFC was raised that it would be merged by the Core Committers (pending the usual code peer review). Once approved it will be announced on the [developer list](https://groups.google.com/forum/#!forum/silverstripe-dev) and if relevant, a related [feature idea](https://forum.silverstripe.org/c/feature-ideas) and [Roadmap](https://www.silverstripe.org/software/roadmap) will be updated. This now means that if a pull request meeting the idea set out in the RFC was raised that it would be merged by the Core Committers (pending the usual code peer review).
## RFC Archives ## RFC Archives

2
docs/en/05_Contributing/04_Release_Process.md
View File

@ -20,7 +20,7 @@ New features and API changes are discussed as
[GitHub issues](https://docs.silverstripe.org/en/contributing/issues_and_bugs/)), [GitHub issues](https://docs.silverstripe.org/en/contributing/issues_and_bugs/)),
as well as the [forum](https://forum.silverstripe.org). as well as the [forum](https://forum.silverstripe.org).
They are prioritised by the core team as tickets on They are prioritised by the core team as tickets on
github.com. In addition, we collect community feedback on [silverstripe.uservoice.com](https://silverstripe.uservoice.com). github.com. In addition, we collect community feedback as [feature ideas](https://forum.silverstripe.org/c/feature-ideas) on the forum.
Any feature ideas we're planning to implement will be flagged there. Any feature ideas we're planning to implement will be flagged there.
Release dates are usually not published prior to the release, but you can get a good idea of the release status by Release dates are usually not published prior to the release, but you can get a good idea of the release status by

2
docs/en/index.md
View File

@ -21,7 +21,7 @@ SilverStripe has an wide range of options for getting support:
* Read the technical reference in our [API Documentation](http://api.silverstripe.org/) * Read the technical reference in our [API Documentation](http://api.silverstripe.org/)
* Get a user-focused overview of the CMS features in our [User Help](http://userhelp.silverstripe.com) * Get a user-focused overview of the CMS features in our [User Help](http://userhelp.silverstripe.com)
* Discuss new features, API changes and the development [roadmap](http://www.silverstripe.org/software/roadmap/) * Discuss new features, API changes and the development [roadmap](http://www.silverstripe.org/software/roadmap/)
on [UserVoice](http://silverstripe.uservoice.com/forums/251266-new-features) on the ["feature ideas" category](https://forum.silverstripe.org/c/feature-ideas) in our forums
## Building your first SilverStripe Web application ## Building your first SilverStripe Web application