Skip to content
Snippets Groups Projects
Commit b76b7051 authored by Martyn Welch's avatar Martyn Welch
Browse files

Remove unused wiki templates


Remove the mediawiki templates that aren't being used or referred to in
the website.

Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
parent 8301d775
No related branches found
No related tags found
1 merge request!1Wip/martyn/t6720
Showing
with 0 additions and 709 deletions
+++
date = "2018-06-13"
weight = 100
title = "Template:Archive"
aliases = [
"/old-wiki/Template:Archive"
]
+++
<includeonly></includeonly> __NOINDEX__
<div style="background-color: #ffc0cb; border: #ff6065 1px solid; padding: 14px; margin: 6px;">
***This page {{\#if: | needs an update | is archived}}. It does not
reflect reality.***
</div>
{{\#if: | [Category:Pages that need
updating]( {{< ref "/category_pages_that_need_updating.md" >}} )[Category:Pages
that need updating on
]( {{< ref "/category_pages_that_need_updating_on_{{{todo}}}.md" >}} )|[Category:Archive]( {{< ref "/category_archive.md" >}} )}}
<noinclude>
You can additional information using the "Extra=" parameter.
For example, {{Template:Archive|Extra=You might be looking for this
other page.}}
Which would turn into…: </noinclude>
\ No newline at end of file
+++
date = "2016-05-13"
weight = 100
title = "Template:Bug"
aliases = [
"/old-wiki/Template:Bug"
]
+++
<noinclude>
## Usage
Use this template to link to the Apertis Bugzilla instance. You should
use Phabricator for issue tracking, not Bugzilla.
For example:
Use {{Template:Bug|1}} to link to bug 1, which will look like this:
## Seealso
[:Template:Bugcomment]( {{< ref "/_template_bugcomment.md" >}} ) <includeonly>
</noinclude>\[<https://bugs.apertis.org/show_bug.cgi?id=>
\#\]</includeonly>
\ No newline at end of file
+++
date = "2016-05-13"
weight = 100
title = "Template:Bugcomment"
aliases = [
"/old-wiki/Template:Bugcomment"
]
+++
<noinclude>
## Usage
Use this template to link to a comment in the Apertis Bugzilla instance.
You should use Phabricator for issue tracking, not Bugzilla.
For example:
Use {{Template:Bugcomment|1|2}} to link to bug 1, comment 2, which will
look like this:
## Seealso
[:Template:Bug]( {{< ref "/_template_bug.md" >}} ) <includeonly>
</noinclude>\[<https://bugs.apertis.org/show_bug.cgi?id=>\#c \#
<small>(comment )</small>\]</includeonly>
\ No newline at end of file
+++
date = "2016-05-13"
weight = 100
title = "Template:CC0 1.0"
aliases = [
"/old-wiki/Template:CC0_1.0"
]
+++
<noinclude>[Category:Licensing]( {{< ref "/category_licensing.md" >}} )
## Usage
This template is used for uploaded file licensing. The content of this
template must not be changed, but the styling can be updated.
## Template
</noinclude>{| id="license" style="width:60%; background:\#f9f9f9;
margin:1em; padding:1em; border:1px solid \#ddd; text-align:center;" |
This work is licensed under the [Creative
Commons]( {{< ref "/wikipedia_creative_commons.md" >}} )
[CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/) License.
|}
\ No newline at end of file
+++
date = "2016-05-13"
weight = 100
title = "Template:CC BY-NC-SA 4.0"
aliases = [
"/old-wiki/Template:CC_BY-NC-SA_4.0"
]
+++
<noinclude>[Category:Licensing]( {{< ref "/category_licensing.md" >}} )
## Usage
This template is used for uploaded file licensing. The content of this
template must not be changed, but the styling can be updated.
## Template
</noinclude>{| id="license" style="width:60%; background:\#f9f9f9;
margin:1em; padding:1em; border:1px solid \#ddd; text-align:center;" |
This work is licensed under the [Creative
Commons]( {{< ref "/wikipedia_creative_commons.md" >}} )
[Attribution-NonCommercial-ShareAlike 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/)
License. |}
\ No newline at end of file
+++
date = "2016-05-13"
weight = 100
title = "Template:CC BY-SA 4.0"
aliases = [
"/old-wiki/Template:CC_BY-SA_4.0"
]
+++
<noinclude>[Category:Licensing]( {{< ref "/category_licensing.md" >}} )
## Usage
This template is used for uploaded file licensing. The content of this
template must not be changed, but the styling can be updated.
## Template
</noinclude>{| id="license" style="width:60%; background:\#f9f9f9;
margin:1em; padding:1em; border:1px solid \#ddd; text-align:center;" |
This work is licensed under the [Creative
Commons]( {{< ref "/wikipedia_creative_commons.md" >}} )
[Attribution-ShareAlike 4.0](http://creativecommons.org/licenses/by-sa/4.0/)
License. |}
\ No newline at end of file
+++
date = "2018-06-25"
weight = 100
title = "Template:ConnmanEnableWifi"
aliases = [
"/old-wiki/Template:ConnmanEnableWifi"
]
+++
<includeonly>**Please note that connman disables wifi by default on a
fresh image.**
1. To enable the device:
-
connmanctl enable wifi
If it's already enabled, connmanctl will give the error "Error wifi:
Already enabled" that may be ignored.</includeonly> <noinclude> Use the
following wiki code to include this template:
{{ ConnmanEnableWifi }}
The template adds steps to enable the wifi device in ConnMan. WiFi
devices are disabled by default in ConnMan
## Result
{{ ConnmanEnableWifi }} </noinclude>
\ No newline at end of file
+++
date = "2016-06-22"
weight = 100
title = "Template:EnableCellular"
aliases = [
"/old-wiki/Template:EnableCellular"
]
+++
<includeonly>**Please note that connman disables cellular by default on
a fresh image.**
Make sure that the 3G USB modem is seen by Connman,
connmanctl technologies
should display a
/net/connman/technology/cellular
technology.
To enable the device:
sudo mount -o remount,rw /
sudo apt-get install connman-tests
/usr/share/connman/test/test-connman enable cellular
If it's already enabled, test-connman will give an "In progress" error
that may be ignored.</includeonly> <noinclude> Use the following wiki
code to include this template:
{{ EnableCellular }}
It adds steps explaining how to enable the Bluetooth interface. It
should be added to most 3G Modem-related tests as a header notice as the
current image ships with the interface disabled by default.
## Result
{{ EnableCellular }} </noinclude>
\ No newline at end of file
+++
date = "2015-11-02"
weight = 100
title = "Template:EnablePackageRepositories"
aliases = [
"/old-wiki/Template:EnablePackageRepositories"
]
+++
<includeonly>
#### Enable Package Repositories
1. Ensure you have the \<\!--
\--\>{{\#if: |{{\#if: |{{\#if: |, {{\#if: |, and repositories |
and repositories }} | and repositories }} | repository }} }} enabled
in your `sources.list` and you have recently run `apt-get
update`.</includeonly> <noinclude> Use the following wiki code to
include this template:
{{ EnablePackageRepositories | repo1 | repo2 | repo3 | repo4 }}
Some packages are not available in default package repositories and need
some other extra ones. This template adds steps explaining how to do
that. Only 4 repositories can be specified as arguments.
Add that template
([Template:InstallDependencies]( {{< ref "/template_installdependencies.md" >}} ))
afterwards to specify the dependencies needed.
## Result
{{ EnablePackageRepositories |repo1|repo2|repo3|repo4 }} </noinclude>
<noinclude>[Category:QA/Test
case/Template]( {{< ref "/category_qa/test_case/template.md" >}} )</noinclude>
\ No newline at end of file
+++
date = "2016-03-09"
weight = 100
title = "Template:InstallDependencies"
aliases = [
"/old-wiki/Template:InstallDependencies"
]
+++
<includeonly> ==== Install Package Dependencies ====
1. Ensure Rootfs is remounted as read/write:
-
sudo mount -o remount,rw /
2. Install dependencies:
-
{{\#tag:pre | sudo apt install }}
3. Restart the system to restore the filesystem state to read-only
before running the test:
-
sudo reboot
</includeonly> \<\!--
\--\><noinclude> Use the following wiki code to include this template:
{{ InstallDependencies | libbar libfoo }}
The template will add steps to install package from repository. It is a
pre-condition for most test cases as not all needed packages are
installed by default on the system.
## Result
{{ InstallDependencies |libbar libfoo}}</noinclude>
<noinclude>[Category:QA/Test
case/Template]( {{< ref "/category_qa/test_case/template.md" >}} )</noinclude>
\ No newline at end of file
+++
date = "2016-05-23"
weight = 100
title = "Template:InstallSDK"
aliases = [
"/old-wiki/Template:InstallSDK"
]
+++
<includeonly>**Remember, we're now requiring VirtualBox 4.2.2 for tests
using Guest Additions.
Please, read
[Docs/VirtualBox_Guest_Additions]( {{< ref "/docs/virtualbox_guest_additions.md" >}} )
to update your setup.**
\# Download the virtual machine image for the latest SDK release from
<https://images.apertis.org/>.</includeonly> <noinclude> Use the
following wiki code to include this template:
{{ InstallSDK }}
This template adds steps to install the latest SDK release in
VirtualBox. It is needed for some test cases that explicitly run in a
virtualized environment.
## Result
{{ InstallSDK }} </noinclude> <noinclude>[Category:QA/Test
case/Template]( {{< ref "/category_qa/test_case/template.md" >}} )</noinclude>
\ No newline at end of file
+++
date = "2016-09-26"
weight = 100
title = "Template:Obsolete"
aliases = [
"/old-wiki/Template:Obsolete"
]
+++
<includeonly>[Category:Obsolete]( {{< ref "/category_obsolete.md" >}} )</includeonly>
<div style="border: 2px dashed #ef2929; background-color: #ffffff; padding: 5px;">
<table style="background-color: #ff593a; border:1px solid #a3b0bf; padding: 5px; width: 100%; color:#ffffff;">
<tr>
<td>
<b>This page is obsolete.</b>
</td>
</tr>
</table>
</div>
<noinclude>
You can additional information using the "Extra=" parameter.
For example, {{Template:WIP|Extra=Look at \[http://example.com/ this
example\] instead}}
Which would turn into..: </noinclude>
\ No newline at end of file
+++
date = "2016-07-13"
weight = 100
title = "Template:Phab"
aliases = [
"/old-wiki/Template:Phab"
]
+++
<noinclude>
## Usage
Use this template to link to the Apertis Phabricator instance.
For example:
Use {{Phab|T1}} to link to T1, which will look like this:
</noinclude><includeonly>\[<https://phabricator.apertis.org/>
}}}\]</includeonly>
\ No newline at end of file
+++
date = "2018-06-28"
weight = 100
title = "Template:TestSuite"
aliases = [
"/old-wiki/Template:TestSuite"
]
+++
<noinclude>
## Usage
Use the following wiki code to include this template:
{{ TestSuite | id =
| type = Unit | Functional | Performance | Reliability | Usability
| priority = Low | Medium | High | Critical
| execution_type = Manual | Automated
| lava = N/A | Integrated | Not Integrated
| image = Any | Development | SDK | Target
| target = Any | VirtualBox | X86 Reference | i.MX6 Sabrelite | i.MX53 | <other specific device>
| state = Final | Devel | <Task number> | Deprecated
| description =
| testcases =
| notes = (optional)
}}
Each test suite contains several pieces of metadata as explained bellow:
- **id**: Identifier of the test suite. Give it a meaningful name in
form of "component-feature" if applicable, and all lower case. E.g.
gstreamer-video.
- **priority**: The importance and therefore frequency of testing for
the test cases in the suite.
- **type**: The type of tests in the suite. (Check possible values.)
- **execution_type**: The test category. "Manual" is for tests run by
hand and "Automated" is for tests run in LAVA or other automated
system.
- **lava**: The status of LAVA integration. If not specified, the
default value is "Not Integrated". (Check possible values)
- **target**: The target system required to run the tests. If not
specified, the default value is "Any". (Check possible values)
- **image**: The image required to run the tests. If not specified,
the default value is "Any". (Check possible values)
- **state**: The state of the test suite. (Check possible values)
- **description**: A well explained description of what will be
tested. Describes which feature is going to be tested and give some
details about it. Ideally begin this section with a short summary
before going into great detail. E.g. Test playback of video files on
a window and fullscreen using GStreamer. For this the script X is
executed first, then run Y and execute steps A-B-C which ensure
feature Z is properly tested.
Values for the "**priority**" parameter include:
- **Critical**: tested at least once a week, would block release if
failing
- **High**: tested at least once a week
- **Medium**: tested at least once every two weeks
- **Low**: tested as best effort
Values for the "**type**" parameter include:
- **Unit**: Testing a unit of code
- **Functional**: Testing a feature or function of the system
- **Performance**: Testing speed/efficiency of the system
- **Reliability**: Testing robustness of the system
- **Usability**: Testing how easy it is to use the system
Values for the "**execution_type**" parameter include:
- **Manual**: The test case has to be run by hand or initiated
manually.
- **Automated**: The test case is automated and can be integrated
inside the automated system.
Values for the "**lava**" parameter include:
- **N/A**: There is no plan to integrate that test with LAVA system.
- **Not Integrated**: The test case is not yet automated or integrated
to LAVA.
- **Integrated**: The test case can be run by LAVA.
Values for the "**target**" parameter include:
- **Any**: The test case is designed to run on any target platform
- **VirtualBox**: The test case is designed to run within the
VirtualBox emulator
- **X86 Reference**: The test case is designed to run on the specified
[Reference Hardware]( {{< ref "/reference_hardware.md" >}} )
- **i.MX6 Sabrelite**: The test case is designed to run on a Sabrelite
board.
- **i.MX53**: The test case is designed to run on a i.MX53 board.
- **<other specific device>**: The test case is designed to run on the
specified hardware passed for this parameter.
Values for the "**image**" parameter include:
- **Any**: The test case is designed to run on any image.
- **Development**: The test case is designed to run on the development
image.
- **SDK**: The test case is designed to run on the SDK image.
- **Target**: The test case is designed to run on target image.
Values for the "**state**" parameter include:
- **Final**: The test case can be used for testing. For all other
values, a message will appear at the top of the page.
- **Devel**: The test case is still under development and should not
be used.
- '''
<Task number>
''': Same as Devel, but there will also be a link pointing to the
bug report tracking the test case development.
- **Deprecated**: The test case is deprecated and should no longer be
used.
**testcases**: A bullet list of links to the test cases in the suite.
For example:
`* `[`gstreamer-video-playback`]( {{< ref "/qa/test_cases/gstreamer-video-playback.md" >}} )
`* `[`gstreamer-video-record`]( {{< ref "/qa/test_cases/gstreamer-video-record.md" >}} )
**notes**: An optional bulleted list of additional notes, references,
links or general information about the test case.
## Template
</noinclude>
<div style="display: none !important;">
{{\#vardefine: ucSTATE | }} {{\#vardefine: ucLAVA | }}
{{\#vardefine: warnMessage1 | This test case is still under development
and should not be executed. For more information, please contact the
page owner}} {{\#vardefine: warnMessage2 | or check ticket
\[<https://phabricator.collabora.co.uk/>{{\#var: ucSTATE}} {{\#var:
ucSTATE}}\] }} {{\#vardefine: warnMessage3 | This test case is
deprecated and should not be executed. For more information, please
contact the page owner}} {{\#vardefine: outMessage | {{\#switch:
{{\#var: ucSTATE}} | = | = {{\#var: warnMessage1}}. | = {{\#var:
warnMessage3}}. | {{\#var: warnMessage1}} {{\#var: warnMessage2}}. }} }}
</div>
<span style="color:red; font-size:14pt; text-align:center;">'''{{\#var:
outMessage}}</span>
## Test Suite
- **Id**:
- **Type**:
- **Priority**:
- **Execution Type**:
- **LAVA Integration**: {{\#if: | | Not Integrated}}
- **Target**: {{\#if: | | Any}}
- **Image Type**: {{\#if: | | Any}}
### Description
<noinclude>
GStreamer playback and record
- Verify the video playback works
- Verify the video recording works
</noinclude> <includeonly>{{\#if: |</includeonly>
### Test cases
<noinclude>\* </noinclude><noinclude> </noinclude><includeonly>|}}
</includeonly>
<includeonly>{{\#if: |</includeonly>
### Notes
- Make sure that you have disconnect the ethernet connection to the
target before you start the tethering process.
<noinclude>\* </noinclude><noinclude>
- Example note</noinclude><includeonly>|}}
</includeonly>
{{\#switch: {{\#var: ucSTATE}} | | = [Category:QA/Test
Suites]( {{< ref "/category_qa/test_suites.md" >}} ) | =
[Category:QA/Deprecated Test
Suites]( {{< ref "/category_qa/deprecated_test_suites.md" >}} ) | =
[Category:QA/Under Development Test
Suites]( {{< ref "/category_qa/under_development_test_suites.md" >}} ) |
\#default = [Category:QA/Test
Suites]( {{< ref "/category_qa/test_suites.md" >}} ) }}
{{\#ifeq: {{\#var: ucSTATE}} | | |
` {{#ifeq: {{#var: ucLAVA}} | `` | `[`Category:QA/Integrated``
``Test``
``Suites`]( {{< ref "/category_qa/integrated_test_suites.md" >}} )` | | }}`
}} <noinclude>[Category:QA/Test
suite/Template]( {{< ref "/category_qa/test_suite/template.md" >}} )</noinclude>
\ No newline at end of file
+++
date = "2015-11-02"
weight = 100
title = "Template:TrackpadPairing"
aliases = [
"/old-wiki/Template:TrackpadPairing"
]
+++
<includeonly>
#### Trackpad Pairing Instructions
**Note:**
\***Currently, we only support magic trackpad using SDK images.**
- **Make sure BT is properly enabled and not blocked by rfkill.**
<!-- end list -->
1. Boot up your device/desktop with some bluetooth adapter/receiver
plugged-in
2. Select VirtualBox-\>Devices-\>Bluetooth Dogle name.
3. In xfce Panel, you should see the bluetooth icon in the right-top
corner.
4. Right-click on that icon and click "Turn Bluetooth on" if it's
currently turned off.
5. Once turned-on, right-click on the bt icon and choose "Devices".
6. At this point, turn on your magic trackpad by simply pressing the
side button.
7. In the bluetooth devices window, search for nearby devices by
clicking on the magnifier
8. You should see the "Apple Wireless trackpad" entry in the list.
9. Add this device to your list of know devices by clicking on the
"plus" icon.
10. Start the pairing operation by clicking on the "key" icon
11. When asked for a pin, enter "0000"
12. Mark this device as trusted by clicking on the "yellow star" icon
13. Setup the device by clicking on the setup icon next to the star
14. In the "bluetooth assistant" window, check "input service" and click
"Forward"
15. You should see "Device added successfully, and connected"
Your magic trackpad should now be working properly. </includeonly>
<noinclude> Use the following wiki code to include this template:
{{ TrackpadPairing }}
This template will include the steps for pairing the magic trackpad.
## Result
{{ TrackpadPairing }} [Category:QA/Test
case/Template]( {{< ref "/category_qa/test_case/template.md" >}} ) </noinclude>
\ No newline at end of file
+++
date = "2015-12-03"
weight = 100
title = "Template:WIP"
aliases = [
"/old-wiki/Template:WIP"
]
+++
<includeonly>[Category:WIP]( {{< ref "/category_wip.md" >}} )</includeonly>
<div style="border: 2px dashed #ef2929; background-color: #ffffff; padding: 5px;">
<table style="background-color: #3a5981; border:1px solid #a3b0bf; padding: 5px; width: 100%; color:#ffffff;">
<tr>
<td>
<b>This page is a work in progress.</b>
</td>
</tr>
</table>
</div>
<noinclude>
You can additional information using the "Extra=" parameter.
For example, {{Template:WIP|Extra=Please feel free to edit as you see
fit\!}}
Which would turn into..: </noinclude>
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment