tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-06-26 14:39:25 +02:00
Code Issues Projects Releases Wiki Activity

Change SilverStripe to Silverstripe CMS

Browse Source 
Correct Silverstripe to Silverstripe CMS (#9992)
This commit is contained in:
Michael Pritchard (HEIW) 2021-08-06 11:50:27 +01:00
parent e0548b208e
commit 6e8a390561
5 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/en/01_Lessons/index.md
View File

@ -1,10 +1,10 @@
---
title: Lessons
introduction: The lessons take a step by step look at how to build a Silverstripe application.
introduction: The lessons take a step by step look at how to build a Silverstripe CMS application.
icon: graduation-cap
---
* [How to set up a local development environment in Silverstripe](https://www.silverstripe.org/learn/lessons/v4/up-and-running-setting-up-a-local-silverstripe-dev-environment-1)
* [How to set up a local development environment in Silverstripe CMS](https://www.silverstripe.org/learn/lessons/v4/up-and-running-setting-up-a-local-silverstripe-dev-environment-1)
* [Lesson 1: Creating your first project](https://www.silverstripe.org/learn/lessons/v4/creating-your-first-project)
* [Lesson 2: Migrating static templates into your theme](https://www.silverstripe.org/learn/lessons/v4/migrating-static-templates-into-your-theme-1)
* [Lesson 3: Adding dynamic content](https://www.silverstripe.org/learn/lessons/v4/adding-dynamic-content-1)
@ -30,5 +30,5 @@ icon: graduation-cap
## Help: If you get stuck
* [The Tips & Tricks forum](https://forum.silverstripe.org/c/tips): Review some existing solutions to common problems.
* [Silverstripe Community](http://www.silverstripe.org/community/): Join our community chat via Slack, or ask a question
* [Silverstripe CMS Community](http://www.silverstripe.org/community/): Join our community chat via Slack, or ask a question
on Stack Overflow.

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

@ -73,7 +73,7 @@ from the [wider module ecosystem](https://addons.silverstripe.org).
In order to only show issues and pull requests relevant to your project,
we've written a little [composer utility](https://github.com/silverstripe/silverstripe-github-issue-search-composer-util)
which inspects your own `composer.lock` file dependencies,
and searches across all Silverstripe modules in there.
and searches across all Silverstripe CMS modules in there.
After [installing the composer utility](https://github.com/silverstripe/silverstripe-github-issue-search-composer-util),
use this command to pass through a lock file, and get a URL to open in your favourite browser.
@ -83,4 +83,4 @@ cat /my/project/composer.lock | ss-issue-search get-url
```
Protip: You can further filter to certain [issue labels](code#labels)
such as `label:impact/high` to make the results more relevant.
such as `label:impact/high` to make the results more relevant.

22
docs/en/05_Contributing/01_Code.md
View File

@ -1,15 +1,15 @@
---
title: Contributing Code
summary: Fix bugs and add new features to help make SilverStripe better.
summary: Fix bugs and add new features to help make Silverstripe CMS better.
icon: code
---
# Contributing Code - Submitting Bugfixes and Enhancements
SilverStripe will never be finished, and we need your help to keep making it better. If you're a developer a great way to get involved is to contribute patches to our modules and core codebase, fixing bugs or adding features.
Silverstripe CMS will never be finished, and we need your help to keep making it better. If you're a developer a great way to get involved is to contribute patches to our modules and core codebase, fixing bugs or adding features.
The SilverStripe core modules (`framework` and `cms`), as well as some of the more popular modules are in
git version control. SilverStripe hosts its modules on [github.com/silverstripe](https://github.com/silverstripe/). After [installing git](https://help.github.com/articles/set-up-git/) and creating a [free github.com account](https://github.com/join/), you can "fork" a module,
The Silverstripe CMS core modules (`framework` and `cms`), as well as some of the more popular modules are in
git version control. Silverstripe CMS hosts its modules on [github.com/silverstripe](https://github.com/silverstripe/). After [installing git](https://help.github.com/articles/set-up-git/) and creating a [free github.com account](https://github.com/join/), you can "fork" a module,
which creates a copy that you can commit to (see github's [guide to "forking"](https://help.github.com/articles/fork-a-repo/)).
For other modules, our [add-ons site](https://addons.silverstripe.org/add-ons/) lists the repository locations, typically using the version control system like "git".
@ -18,7 +18,7 @@ If you are modifying CSS or JavaScript files in core modules, you'll need to reg
Please check out our [client-side build tooling](build_tooling) guide for details.
[hint]
Note: By supplying code to the SilverStripe core team in patches, tickets and pull requests, you agree to assign copyright of that code to SilverStripe Limited, on the condition that SilverStripe Limited releases that code under the BSD license.
Note: By supplying code to the Silverstripe CMS core team in patches, tickets and pull requests, you agree to assign copyright of that code to Silverstripe Limited, on the condition that Silverstripe Limited releases that code under the BSD license.
We ask for this so that the ownership in the license is clear and unambiguous, and so that community involvement doesn't stop us from being able to continue supporting these projects. By releasing this code under a permissive license, this copyright assignment won't prevent you from using the code in any way you see fit.
[/hint]
@ -26,7 +26,7 @@ We ask for this so that the ownership in the license is clear and unambiguous, a
## Step-by-step: From forking to sending the pull request
[notice]
**Note:** Please adjust the commands below to the version of SilverStripe that you're targeting.
**Note:** Please adjust the commands below to the version of Silverstripe CMS that you're targeting.
[/notice]
1. Create a [fork](https://help.github.com/articles/about-forks/) of the module you want to contribute to (listed on [github.com/silverstripe/](https://github.com/silverstripe/)).
@ -79,7 +79,7 @@ there are any problems they will follow up with you, so please ensure they have
### Picking the right version
The SilverStripe project follows the [Semantic Versioning](http://semver.org) (SemVer) specification for releases.
The Silverstripe CMS project follows the [Semantic Versioning](http://semver.org) (SemVer) specification for releases.
It clarifies what to expect from different releases, and also guides you in choosing the right branch to base your pull request on.
If you are unsure what branch your pull request should go to, consider asking in the GitHub issue that you address with your patch, or
@ -141,9 +141,9 @@ The current GitHub labels are grouped into five sections:
| impact/high | Broken functionality/experience with no obvious workarounds available, or an enhancement that provides a clear benefit to users. Typically affecting major usage flows or core interactions |
| impact/medium | Unexpected behaviour, or broken functionality on less common usage flows |
| impact/low | A nuisance but doesn't break any functionality (typos, etc) |
| effort/easy | Someone with limited SilverStripe experience could resolve |
| effort/medium | Someone with a good understanding of SilverStripe could resolve |
| effort/hard | Only an expert with SilverStripe could resolve |
| effort/easy | Someone with limited Silverstripe CMS experience could resolve |
| effort/medium | Someone with a good understanding of Silverstripe CMS could resolve |
| effort/hard | Only an expert with Silverstripe CMS could resolve |
| type/docs | A docs change |
| type/bug | Does not function as intended, or is inadequate for the purpose it was created for |
| type/frontend | A change to front-end (CSS, HTML, etc) |
@ -180,7 +180,7 @@ After you have edited the file, GitHub will offer to create a pull request for y
## Check List
* Adhere to our [coding conventions](/contributing/coding_conventions)
* If your patch is extensive, discuss it first on the [SilverStripe Forums](https://forum.silverstripe.org/c/feature-ideas) (ideally before doing any serious coding)
* If your patch is extensive, discuss it first on the [Silverstripe CMS Forums](https://forum.silverstripe.org/c/feature-ideas) (ideally before doing any serious coding)
* When working on existing tickets, provide status updates through ticket comments
* Check your patches against the "master" branch, as well as the latest release branch
* Write [unit tests](../developer_guides/testing/unit_testing)

12
docs/en/05_Contributing/10_Code_of_conduct.md
View File

@ -3,11 +3,11 @@ title: Code of conduct
summary: How to be a high-performing, helpful member of our community
icon: handshake
---
# SilverStripe community code of conduct
# Silverstripe CMS community code of conduct
These guidelines aim to be an aspirational ideal for how we should behave when interacting in the SilverStripe developer community and to aid in building great open source software.
These guidelines aim to be an aspirational ideal for how we should behave when interacting in the Silverstripe CMS developer community and to aid in building great open source software.
This code of conduct should be applied to all discussions and interactions involving SilverStripe and its related resources.
This code of conduct should be applied to all discussions and interactions involving Silverstripe CMS and its related resources.
Honour the code of conduct whenever you participate formally and informally in our community and follow it in spirit as much as in letter.
@ -35,7 +35,7 @@ Honour the code of conduct whenever you participate formally and informally in o
* All contributors and core committers, module maintainers and knowledge sharers are participating in the community in a voluntary nature. Have respect for them and their time when making requests. You may need to exercise some patience.
* Whenever possible, reference your comments to others with example code or links to documentation. This helps people learn and become more experienced community members and developers.
* If you manage to solve your own problem, tell others how you solved it. This will help people in the future who have to solve similar problems.
* If you are reducing your input, and potentially stepping away from the community, please remember that others might be relying on your contributions. Be prepared to ensure your contributions remain open and available to the community. Spend some time handing your contributions over to another community member or core contributor to help with the continuity of SilverStripe open source development.
* If you are reducing your input, and potentially stepping away from the community, please remember that others might be relying on your contributions. Be prepared to ensure your contributions remain open and available to the community. Spend some time handing your contributions over to another community member or core contributor to help with the continuity of Silverstripe CMS open source development.
## Resolve conflicts directly
* Conflict may eventuate from time to time. We should all try to view it as a constructive process. Understanding others' positions, without descending into ad hominem attacks, is valuable and may lead to better solutions to problems.
@ -49,12 +49,12 @@ Honour the code of conduct whenever you participate formally and informally in o
## A living document
* This is a living document. As core committers, we know we don't have all the answers so we want to make the community an innovative and valuable space for everyone that wishes to contribute.
* If you would like to improve the wording, add additional items, or simply fix typos, each contribution to the code of conduct will be considered on it's merit and agreed upon unanimously by the core committers. Any changes will be included in future revisions of the SilverStripe code of conduct.
* If you would like to improve the wording, add additional items, or simply fix typos, each contribution to the code of conduct will be considered on it's merit and agreed upon unanimously by the core committers. Any changes will be included in future revisions of the Silverstripe CMS code of conduct.
## Core committers house rules
Core committers are also bound by their [own set of house rules](core_committers#house_rules_for_the_core_committer_team).
_The SilverStripe code of conduct has been adapted from the following sources:_
_The Silverstripe CMS code of conduct has been adapted from the following sources:_
http://www.apache.org/foundation/policies/conduct.html

6
docs/en/05_Contributing/16_Maintainer_Guidelines.md
View File

@ -50,7 +50,7 @@ See the details on the [Core Committers](./core_committers) page.
### Contributing Committers
Beyond the Core Committer role, there can be individuals which
focus on core development work - typically sponsored through full-time product development roles by SilverStripe Ltd.
focus on core development work - typically sponsored through full-time product development roles by Silverstripe Ltd.
These Contributing Committers require write access to core repositories to maintain their pace,
often working alongside Core Committers. They are guided by additional rules:
@ -94,10 +94,10 @@ First and foremost rule of a maintainer is to collaborate with other maintainers
* Follow [Semantic Versioning](code/#picking-the-right-version) by putting any changes into the correct branch
* API changes and non-trivial features should not be merged into release branches.
* API changes on master should not be merged until they have the buy-in of at least two Core Committers (or better, through the [core mailing list](https://groups.google.com/forum/#!forum/silverstripe-dev))
* Be inclusive. Ensure a wide range of SilverStripe developers can obtain an understanding of your code and docs, and you're not the only one who can maintain it.
* Be inclusive. Ensure a wide range of Silverstripe CMS developers can obtain an understanding of your code and docs, and you're not the only one who can maintain it.
* Avoid `git push --force`, and be careful with your git remotes (no accidental pushes)
* Use your own forks to create feature branches
* We release using the standard process. See the [Making a SilverStripe Core Release](making_a_silverstripe_core_release)
* We release using the standard process. See the [Making a Silverstripe CMS Core Release](making_a_silverstripe_core_release)
### How to triage