“UbuntuHelp:Boucft/GettingPermission”的版本间的差异
来自Ubuntu中文
小 （新页面: {{From|https://help.ubuntu.com/community/boucft/GettingPermission}} {{Languages|UbuntuHelp:boucft/GettingPermission}} * '''Launchpad Entry''': https://blueprints.launchpad.net/boucft/+sp...） |
小 |
||
| 第3行： | 第3行： | ||
* '''Launchpad Entry''': https://blueprints.launchpad.net/boucft/+spec/getting-permission | * '''Launchpad Entry''': https://blueprints.launchpad.net/boucft/+spec/getting-permission | ||
* '''Created''':15 Aug 2008 by Old_Soldier | * '''Created''':15 Aug 2008 by Old_Soldier | ||
| − | * '''Contributors''': | + | * '''Contributors''': duanedesign |
* '''Packages affected''':boucft | * '''Packages affected''':boucft | ||
=== Summary === | === Summary === | ||
| − | Standard method for gaining permission to use a UCF tutorial. | + | Standard method for communication with Ubuntu Community Forum tutorial authors. A letter(s) we can use in our correspondence with UCF tutorial authors introducing the project, gaining permission to use a UCF tutorial, and additional follow up letter(s) that might be needed. The letter needs to also remind the author of the importance of "sharing and cooperation that is at the heart of the open source movement. In the Free Software world, we collaborate freely on a volunteer basis to build software (and documentation) for everyone's benefit. We improve on the work of others, which we have been given freely, and then share our improvements on the same basis." * |
| + | *Ubuntu Code of Conduct | ||
=== Release Note === | === Release Note === | ||
| − | Not mandatory due to the licensing of the Ubuntu Community Forums, but it is a good practice. | + | Not mandatory due to the licensing of the Ubuntu Community Forums, but it is a good practice. Also this is an opportunity to potentially get the authors involved in updating their tutorials as new releases come out. |
=== Rationale === | === Rationale === | ||
Although permission is not required to use the tutorials, it is better to gain community support. | Although permission is not required to use the tutorials, it is better to gain community support. | ||
=== Use Cases === | === Use Cases === | ||
| − | 1. Original poster of the tutorial is active on the forums. | + | 1. Original poster of the tutorial is active on the forums.<<BR>> |
| − | 2. Original poster is inactive or unresponsive. | + | 2. Original poster is inactive or unresponsive.<<BR>> |
| − | 3. Original poster has PM's disabled. | + | 3. Original poster has PM's disabled.<<BR>> |
| + | 4. A letter thanking the author for letting us use their tutorial.<<BR>> | ||
| + | 5. New release is coming out soon and we want to contact the author about the possibility of them updating their tutorial.<<BR>> | ||
=== Assumptions === | === Assumptions === | ||
2009年5月12日 (二) 16:06的版本
 |
点击翻译: |
English |
* Launchpad Entry: https://blueprints.launchpad.net/boucft/+spec/getting-permission
- Created:15 Aug 2008 by Old_Soldier
- Contributors: duanedesign
- Packages affected:boucft
目录
Summary
Standard method for communication with Ubuntu Community Forum tutorial authors. A letter(s) we can use in our correspondence with UCF tutorial authors introducing the project, gaining permission to use a UCF tutorial, and additional follow up letter(s) that might be needed. The letter needs to also remind the author of the importance of "sharing and cooperation that is at the heart of the open source movement. In the Free Software world, we collaborate freely on a volunteer basis to build software (and documentation) for everyone's benefit. We improve on the work of others, which we have been given freely, and then share our improvements on the same basis." *
- Ubuntu Code of Conduct
Release Note
Not mandatory due to the licensing of the Ubuntu Community Forums, but it is a good practice. Also this is an opportunity to potentially get the authors involved in updating their tutorials as new releases come out.
Rationale
Although permission is not required to use the tutorials, it is better to gain community support.
Use Cases
1. Original poster of the tutorial is active on the forums.<
>
2. Original poster is inactive or unresponsive.<
>
3. Original poster has PM's disabled.<
>
4. A letter thanking the author for letting us use their tutorial.<
>
5. New release is coming out soon and we want to contact the author about the possibility of them updating their tutorial.<
>
Assumptions
We will assume that the overwhelming majority of tutorial writers will happily approve their inclusion with attribution. If a user does not approve we can rewrite the tutorial or find another.
Design
Templates of messages to be created for team members to use as a guideline.
Implementation
Create | templates page, Team members should use the message or something very similar when contacting tutorial posters.
UI Changes
N/A
Code Changes
n/a
Migration
n/a
Test/Demo Plan
n/a
Outstanding Issues
none
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
