RBE10K/Teams
Teamwork is an essential component of The RBE10K Project. RBE10K is a community project, and therefore it is not owned by anyone, but the result of the concerted effort of everyone. Teams allow for self-governance and make participation easier, as participants are then able to rely on each other's skills and experience. Whilst Teams have freedom to work on any subject, their intended purpose is addressing the specific needs of the project.
Teams are ideally more than one person, however they are likely to all begin as a single person effort. Participants are encouraged to engage with each other requesting participation on teams, and working together. Teams are also encouraged to be small enough to enable a satisfactory level of self-governance and familiarity, a number of people not greater than what can be handled by online meeting software such as Skype or Google+ Hangouts. Teams are also encouraged to be local whenever possible, and get to know each other in person, and ideally share activities such as picnics or camping together.
Contents |
Purpose
A Team is nothing but a public record and acknowledgement that a group of contributors is working together in a particular task, related to The RBE10K Project. A team has full autonomy and freedom, and can use its Team page for recording any information they consider appropriate or convenient. However, Team pages, like User pages, are not considered part of the Main wiki, but a sort of transient or scrapbook.
Information in Teams is intended to be private to the team, and therefore it can be in any language. This is a convenience for international teams who want to participate, and they can record information in their Team page in their own language. An international team can request a translation team to implement an article or section in their Team page, in English in a given location.
Creating or joining a Team
Any contributor can create a new team, and work as a unipersonal team. Should anyone be interested in a particular team, they can request joining it, and the request may be granted by the team, or denied. Rules of courtesy apply in both cases, explaining reasons for joining in, and should the request be denied, reasons for the denial. Teams are free to accept or reject new members by whichever reasons they consider suitable, and their decision is final.
Offers and Requests
Teams make requests through the RBE10K_Requests table. In the same light, teams offer different kinds of assistance through the RBE10K_Offers table.
List
The list of teams can be seen here.
Bettermeans
The software Bettermeans is recommended for use by all participants. In certain cases it may seem unnecessary, however it does provide for convenient and organised horizontal governance.
Registration
Teams register in the wiki in many ways similar to just like users do. Whilst users have a wiki prefix User:, teams have a prefix Team:. So, for example, the team that is managing this wiki is called Team:Wiki.
Let's say a registered contributor wants to create a team to research and document on systems of food production, for example permaculture. Typing in the search box (top right of the page) Team:Permaculture and clicking go, it may lead to the actual team called Permaculture, or to a failed search, offering to Create the page "Team:Permaculture" on this wiki!. If the team doesn't exist, clicking on that link will lead to an empty page. The following template can be copy/pasted on the empty page to have it started (replace all the fields between double angled brackets, e.g. <<Name>> with John - remember to remove the angled brackets!):
This is the [[RBE10K/Teams|Team]] page for [[The RBE10K Project]]'s <<Team name>> Wiki.
== Team ==
<data table="RBE10K_Teams" template="Infobox RBE10K_Teams">
Coordinators=<<names of the coordinators of the team>>
Activities=<<specify a list of activities, like areas of research or goals>>
</data>
[{{canonicalurl:Table:RBE10K_Teams|action=viewdata}} See all teams].
== Members ==
{{RBE10K_Team_MyMembers}}<div style="height: 0px">
<!-- Copy the structure below for each member, so that each member is represented once, one after another, before the ending </div> -->
<data table="RBE10K_Team_Members">
Name=<< member name>>
User=<< member's user page, e.g. [[User:JohnDoe]], between double square brackets>>
Activities=<< list all the activities this member does in/with/for the team >>
</data>
</div>
== Requests ==
{{RBE10K_Team_MyRequests}}<div style="height: 0px">
<!-- Copy the structure below for each request the team makes to the rest of the teams or to any other contributors </div> -->
<data table="RBE10K_Team_Requests">
Name=<< name, or brief description, of the request, e.g. Help wanted researching plants >>
Ref=<< link to usernames (e.g. [[User:JohnDoe]] of people in the project making this request, and who are willing to be contacted by email by anyone offering to help.
Description=<< A more detailed description of what is needed, such as the skills required, an explanation of what is being intended, etc.
</data>
</div>
== Offers ==
{{RBE10K_Team_MyOffers}}<div style="height: 0px">
<!-- Copy the structure below for each request the team makes to the rest of the teams or to any other contributors </div> -->
<data table="RBE10K_Team_Offers">
Name=<< name, or brief description, of the request, e.g. Help offered researching plants >>
Ref=<< link to usernames (e.g. [[User:JohnDoe]] of people in the project willing to help, and who are willing to be contacted by email by anyone requesting help in this area.
Description=<< A more detailed description of what is needed, such as the skills required, an explanation of what is being intended, etc.
</data>
</div>
