Difference between revisions of "Talk:RBE10K/Plan/Action list"
From MediaWiki
(Created page with "== Individual Proposals == == Ziggy == * Stick to technologies that are readily available (technologies that would require research, or that are not sufficiently well establi...") |
(→Ziggy) |
||
| Line 1: | Line 1: | ||
== Individual Proposals == | == Individual Proposals == | ||
| + | |||
| + | === Wiki === | ||
== Ziggy == | == Ziggy == | ||
| − | * Stick to technologies that are readily available (technologies that would require research, or that are not sufficiently well established) | + | |
| + | * Stick to technologies that are readily available (don't use technologies that would require research, or that are not sufficiently well established) | ||
* Avoid discussion as much as practicable | * Avoid discussion as much as practicable | ||
| − | * Keep it real, keep it focused (this is the planning for the wiki, not for strategising for the project, or documenting how to implement the project | + | * Keep it real, keep it focused (this is the planning for the wiki, not for strategising for the project, or documenting how to implement the project) |
* Rely on field experts for each field. We're the wiki field experts, keep it within our expertise | * Rely on field experts for each field. We're the wiki field experts, keep it within our expertise | ||
* Focus our work on elements where there is consensus between us, leaving contentious areas to be dealt with later | * Focus our work on elements where there is consensus between us, leaving contentious areas to be dealt with later | ||
| Line 12: | Line 15: | ||
# Prioritise actions to take based on the priorities established on Need | # Prioritise actions to take based on the priorities established on Need | ||
# Create templates for the teams required for working on satisfying Needs, by priority, so that we can invite people to join them | # Create templates for the teams required for working on satisfying Needs, by priority, so that we can invite people to join them | ||
| + | |||
| + | |||
| + | == Wouter Drucker == | ||
| + | |||
| + | I feel I need some more clarity. I'm not used to working with wiki's but I would be glad to help. How does converting to tree structure work? Same for templates? Where is the community based (other than 'likes')? Same for admin team. | ||
| + | Things will probably get clearer soon anyway, but it won't hurt to let you know what I think. | ||
Revision as of 05:55, 23 February 2013
Contents |
Individual Proposals
Wiki
Ziggy
- Stick to technologies that are readily available (don't use technologies that would require research, or that are not sufficiently well established)
- Avoid discussion as much as practicable
- Keep it real, keep it focused (this is the planning for the wiki, not for strategising for the project, or documenting how to implement the project)
- Rely on field experts for each field. We're the wiki field experts, keep it within our expertise
- Focus our work on elements where there is consensus between us, leaving contentious areas to be dealt with later
- Establish if tree-like is desirable for our wiki
- Work on Needs, and prioritise them (request help from the community for this, through the admin team)
- Prioritise actions to take based on the priorities established on Need
- Create templates for the teams required for working on satisfying Needs, by priority, so that we can invite people to join them
Wouter Drucker
I feel I need some more clarity. I'm not used to working with wiki's but I would be glad to help. How does converting to tree structure work? Same for templates? Where is the community based (other than 'likes')? Same for admin team. Things will probably get clearer soon anyway, but it won't hurt to let you know what I think.
