Sections that make up a charter
Patricia, Thanks so much for your thoughts. The discussion has been quite far-ranging. You have some good ideas that I don't think have been brought up yet. Here are my thoughts on various points:
"Listing participants skills pertaining to the tasks of working groups..."
- I think we are all in agreement on this.
"I think we need a "Workgroup Buddy" kind of person who takes up the task to make the transition for the newcomer easier"
- Good idea. Some of the Workgroups will (I think) require substantial effort with no end date. They may begin with the task of creating a policy, and then take on the role of implementation (e.g., the group that creates the policy to deal with spam morphs into group that implements the policy, including a portion that has day-to-day tasks). We will need a system to bring new people into a workgroup and get them up to speed. I will add this idea to the sustaining workgroups section of the guidelines.
"If we are talking about participants skills in general, maybe a short paragraph at the top..."
- I think we've got this in the charter.
"...we should decentralise our efforts..." and share the work among many.
- Totally agree. I'm hopeful that the implementation of Workgroups will do this -- 1-2 facilitators per group, without much overlap across groups (although likely overlap of members).
"I think we need a catalogue of distribution of tasks to be done when facilitating online..."
- Not sure what you mean, probably because this is my first time facilitating online. Anything to help newcomers get up to speed on this would be very helpful.
"Boundaries"..."not pulling "your" weight ...WE guidelines. For me flexibility is the key word,..."
- I suspect these sections of the charter were originally designed for paid employees forced to work together to achieve some objective. WE are here by choice, which certainly changes things, but I'm not sure exactly how. Will be interesting to see how these sections are used by different groups.
"...harness the power of the user page..."
- I think we should revamp the participant section on our first draft charter to drop the skills table and maybe also the user statements -- we could suggest that users include a brief bio statement at the top of the user page for quick review when determining if a group's participants cover the needed skills. I think I'll put this issue into a separate thread.
"Maybe another type of working group is required, for instance, for the compilation of expertises ... WE community Improvement working groups. Two ideas.
- Two good examples of possible future Workgroups.
- Let's think how to create a communication method for this group that does not depend on email notification. Should we set up an alternative to the talk page?
- I suspect that evaluation will be another learning process. Hopefully we can benefit from what others have learned on this already.
I think the group is largely on the same page, conceptually....just need to work out the details.
Thanks again for taking the time to write out your thoughts. Appreciate your checking in.
--Alison Snieckus 01:40, 16 July 2009 (UTC)
Thanks, Alison for your full response. Just starting to wrap my head around all.
Re If we are talking about participants skills in general, maybe a short paragraph at the top..." I think we've got this in the charter. I like your template idea at the top of the user pages to obtain the most important information and i know Wayne talked about infoboxes that assign some of these things as well, but I meant professional categorisations, so we can go back to a professional category WE page to look for a certain expertise. I am not just thinking about participants information.
by the same talking, maybe we should keep professional resumes on WE, people with OS expertises - Pooling the information by category.
One other thought came to mind: WE clean up. there are quite a number of pages that have no relevant content, maybe a line "Hi, I am ..." how do people feel about deleting those, or separating them into a subfolder, archive?? kind of thing. With 10,000 user accounts now, it can only get bigger. Maybe a Wiki "Maintainance working group" to help with these issues???
I've also suggested a permanent workgroup for "enforcing" (I don't like the connotation of the word, though the definition is correct) the future style guidelines. You can see the thread here. I think the two purposes we've both come up with are nicely combined in a single group. It may seem like a lot of work, now, but the guidelines will be a while, and the workload would severely calm down once the initial cleanup phases are over. I've seen this implemented in WoWWiki as the "watchdogs" and I thought Wikipedia used to have a group called "the cleaners" or something like that, but I'm only finding smaller focus groups. They may have changed to that due to the much higher volume of work.
You are right, words like "watchdogs" and "cleaners" sound a lot like the Wiki Mafia to me (smile!) Maybe we can find a friendlier professional designation (;-))) I agree with your comments.
Something remnant of "help desk" or containing the word "assistant" would be good. We should try to get across that they are there to guide the authors, helping them create better content.
I've noted this team as a specified output of the style guide workgroup. I'm not sure we're ready to do that now, but it sounds to me like it's something should be collaborated on by wider range of people.
Help desk might be too general, because where does it start and end? so I think we need to be more specific. I think "Workgroup Buddy" isn't too bad and Assistant, not sure because it offers the suggestion of a subordinate role while in fact, they are taking the lead until a person is up to speed. What do you think?
I like "buddy" but I also like the idea of giving the impression that the author is in charge, making the decisions. If you take a look at the "Thoughts on related issues..." thread here, you may agree with us that making the contributors feel forced into following the guidelines is not a good idea, because then it becomes another hurdle for them to jump in order to share with us. I think Wayne's point (please correct me if this is isn't the case, Wayne :P) is that we want them to share first, then to conform to the guidelines. It would be the team's duty to guide them through the process.
What about "guide"?