Workgroup:Code of Conduct/Issue Tracker

From WikiEducator
Jump to: navigation, search

Draft 1 beta

Here we discuss issues arising on the draft Code of Conduct. For lengthy discussions use the "discussion" tab.

Start by writing free format into the sections and feel free to try the following template Template:DIssue to keep track of progress with identified issues.

Heading prefixes:

  • "@@": unresolved issues therein
  • ">>": all issues therein are resolved
  • none: no issues identified.
Colours of issue headers indicate:

Effort: none trivial easy routine tricky difficult unknown done

Priority: high medium low


not started on hold ahead on track behind in trouble

The colour behind the title matches the progress colour.



Cover Fair Dealings (etc.)?

Should the scope of the document be expanded to cover fair use/ fair dealingsProgress: done Effort: tricky Priority: medium

Submitted by: Kim Tucker 01:39, 14 January 2011 (UTC)
Status: Decision: No, these are separate policy issues. - Kim Tucker 02:31, 2 April 2011 (UTC)

Support (+1) or not (-1) the following:

  • incorporate aspects of fair use/ fair dealings (+1:Yes, -1:No, separate from this document)
    • -1 - Kim Tucker 01:39, 14 January 2011 (UTC) Personally, I'd prefer a separate document on fair use/ fair dealings. Following the Code of Conduct would lead one to careful consideration of fair use[1].
    • -1 - Hi Kim, I see fair use/dealing as a copyright issue. We should expand on WikiEducator:Copyright and we have the advantage now of drawing on the tutorials from the open content licensing for educators. Wayne Mackintosh 22:02, 14 January 2011.
    • not sure if my vote is +1 or -1, given question: Alison Snieckus 02:53, 8 March 2011 (UTC). I agree that we should explicate fair use/fair dealings in a separate document, but I think it would be useful to include some principle related to copyright in this general code....maybe something along the lines of good faith effort to use original material and to appropriately source adapted works...with a link to the fuller policy.
      • This seems to span several issues and adding to the suggestion below for additional clauses. Under Scope/ Anything Missing? the word "integrity" occurs. This could be added and/or the related issues covered as we synthesise and merge the "leadership" items (e.g "being respectful" could include crediting the team, acknowledging collaborators and sources, etc.). - Kim Tucker 08:51, 8 March 2011 (UTC)


Separate Code of Conduct for Leaders?

One Code of Conduct or two (another for Leaders)Progress: done Effort: medium Priority: medium

Submitted by: Kim Tucker 12:49, 14 January 2011 (UTC)
Status: Decision: one (for version 1.0) with a section on Leadership - but easy to separate.


  • Do we need more than one code of conduct? E.g. one for educators using WikiEducator (including discussions and mailing lists), another for council members and others in leadership positions, another for learners and certain sub-cultures (they could define their own), ....
The current draft is mostly about how we like to work together as a community, and it seems applicable to everyone. Would it make sense to extract the Leadership section into a separate Code of Conduct (as did Ubuntu)? If so, would we need to add clauses on (e.g.) compliance with the law, academic and business integrity, communication, advertising, lobbying, ... (please add)? - Kim Tucker 12:49, 14 January 2011 (UTC)
Reading the draft code, I think its appropriate to separate the leadership code from the community code. I'm not sure that we need separate codes for educators and learners. I'm simultaneously and an educator in the community. Perhaps in time we will to separate out a learner code of conduct, but not sure if we need one yet. I agree with your suggestions for additional clauses - -cant think of any more just yet but will add as we go along. --Wayne Mackintosh 22:02, 14 January 2011 (UTC)
The rationale for not separating leadership and community codes is that leadership and leaders may emerge from the community at any time at various levels and scales. The behaviours listed under leadership, like the others, apply to anyone - collectively engendering an environment in which people feel comfortable to share their views, cooperate/ collaborate and lead when applicable. An alternative to separate codes of conduct (or having a "leadership" section as it does now) for leaders and the community would be to synthesise and merge the leadership section into the rest (there is some overlap). One of the tricks will be to retain a concise set of sub-headings which capture the essence of the Code of Conduct. Comments anyone? -- Kim Tucker 22:22, 1 March 2011 (UTC)
I like the leadership and community codes combined in one document, and I wonder if we need it allocated to a separate section. Merging the leadership ideas into the rest of the document could be very empowering for community members. In a sense leadership is just an extension of the ideas in collaboration. But on the other hand, I wonder if we should create more sections: Editing etiquette, Collaboration and leadership, Help: asking and offering...sorry to muddy the waters. I agree that the goal should be a concise set of principles, each represented in a sub-heading. Also, I suggest that we encourage formal leadership structures, e.g., WCC, to adopt their own code of conduct. This way we can keep this document applicable to everyone, and yet attend to the needs of a specific group. --Alison Snieckus 02:42, 8 March 2011 (UTC)

For version 1.0 we will keep the two combined but make it easy to separate them if so desired in the next version. - Kim Tucker 02:52, 2 April 2011 (UTC)

Suggestion: Broad scope with 6-10 distinct principles

Suggestion: Broad scope with 6-10 distinct principlesProgress: done Effort: unknown Priority: medium

Submitted by: Alison Snieckus
Status: Agreed on structure. Improving the wording of principles is on-going. Add links to relevant policies.

In thinking about the idea of a code of conduct, it seems to me that the purpose is to provide broad direction for community collaboration and ultimate production of OER and related products. Given that one outcome would be for people to take the time to read the code, to at least look over the headings. If this is a goal it suggests a code that is broadly applicable and concise and to the point. Although I suggested grouping the principles by heading in an earlier comment, I retract that idea in favor of a list of 6-10 distinct principles which describe desired conduct. For example, I suggest that being considerate and respectful are related and we don't need both on the list. I suggest we frame one or two principles related to leadership for inclusion. In addition, I think we should be very clear about the principle that wikieducators either include original content or include appropriately sourced copyrighted content (phrasing needs work). And, I think we should indicate that advertising is not tolerated...will be deleted. And lastly, I suggest s principle to encourage users to participate, e.g., "Just try it, our community will support you". --Alison Snieckus 02:22, 30 March 2011 (UTC)

To me it is about how we as a community like to interact and work together (in general, not only during peer production). - Kim Tucker 20:57, 30 March 2011 (UTC)
I think we are agreed. How we interact/work together as a community is the overriding purpose, but the code should include recognition that individual efforts are part of WE also. --Alison Snieckus 02:35, 31 March 2011 (UTC)
Could the 6-10 principles you suggest be presented as a numbered list with each item linked to text explaining or elaborating on the principle? If so, wiki-generated headings is just one way of doing it. - Kim Tucker 20:57, 30 March 2011 (UTC)
Yes, but I'd also suggest a sentence or two (or a few bulleted points) of explanation on the main page (like in the 1st draft). I think readers are more likely to read the extra stuff if it's on the page in front of them. We can include links to support pages as needed.
I think the headings/principles need some more thought. Some are not quite "right" and there is overlap. For example, the text under "Be considerate" is really about being mindful of the community, the text under "Be respectful" is about being polite and civil in our interactions, which would include being "considerate". Some of the suggestions under "Leadership" fit under "Be respectful". Correct attribution (even for work in the public domain) is also part of being respectful. So, I think we can reduce the number of "principles" to between 6 and 10. - Kim Tucker 20:57, 30 March 2011 (UTC)
OK, so I guess the next step is to try it out. Can we come up with 6-10 broad, yet distinct principles? --Alison Snieckus 02:35, 31 March 2011 (UTC)
In terms of Scope, for me the Code should focus on our behaviour while interacting rather than on policies such as not including advertising and ensuring correct attribution. - Kim Tucker 20:57, 30 March 2011 (UTC)
That's a good point. Might we suggest that the code is a set of guiding principles, which our community agrees to aspire to, and recognize in the intro (or at the end) that there are also policies that govern community behavior? (Maybe we include a list of important policies at the end.) Just some thoughts. --Alison Snieckus 02:47, 31 March 2011 (UTC)
It would be great to include a set of links to relevant policies. I think we are agreed wrt to the structure and can close this issue. The wording of the headings/principles can still be improved. - Kim Tucker 02:37, 2 April 2011 (UTC)


TitleProgress: done Effort: easy Priority: low

Submitted by: Kim Tucker 15:39, 3 February 2011 (UTC)
Status: For version 1.0 stick with "Code of Conduct".

Is "Code of Conduct" the right way of putting it? What other possible titles could we use?

  • Code of Conduct
  • Decorum
  • Etiquette
    • Netiquette
  • Mores
  • Ps and Qs
  • Protocol
  • Guide to Interaction
  • ...
  • Charter and Bye-Laws--Nadia El Borai 14:13, 3 March 2011 (UTC)

Default action: stick with "Code of Conduct".

No strong support or objections at this time, so for version 1.0 we stay with "Code of Conduct". - Kim Tucker 02:39, 2 April 2011 (UTC)

>>Anything Missing?

@@The role of libre software and free file formats

Emphasise the importance of libre software and free file formatsProgress: started Effort: tricky Priority: high

Submitted by: Kim Tucker 09:40, 7 November 2011 (UTC)
Status: Open for discussion

An issue which arose while drafting the 2nd Open Comminity Governance Policy was that of embedding links to third party media which rose issues around free file formats and the requirement that all learning resources be accessible and adaptable with libre software.

On the one hand, a contributor adhering to this code of conduct in the full spirit of its implicit and explicit values would be using libre software and be contributing material in suitable formats.

On the other hand, we cannot be sure that all our participants, especially new contributors, understand this and there is a stream of media being uploaded some of which are not playable with free software.

What is the best way to make this clear?

>>Thoughts on what might be missing?

Clauses to Add/ What's missing?Progress: done Effort: tricky Priority: low

Submitted by: Kim Tucker 16:14, 3 February 2011 (UTC)
Status: For version 1.0 no glaring omissions have been pointed out.

Please comment on the following and add. Some might go without saying or may be implied already (e.g. in an existing section, or in the values expressed in the Introduction). Feel free to suggest wording.

  • compliance with the law
  • academic integrity
  • business integrity
  • communication
  • advertising
  • lobbying
  • ....

Default action: exclude these suggestions.

No comments or suggestions on whether anything is missing. The pre-prepared suggestions have less to do with style of interaction. Some could be covered in relevant policy documents. You can help by finding and linking to them. - Kim Tucker 02:42, 2 April 2011 (UTC)


Managing Multiple Drafts

Developing a 2nd Draft has been suggested (by Alison). Some of its wording has been incorporated already (e.g. in the Introduction). However, I have removed reference to it in the template (the links at the top of the page to 'Charter, 1st Draft, Issues, ....') as it confuses readers about which version is the current working version.

One possibility, if we do want to manage multiple versions (at this stage, so close to the Council meeting) is to change the template's "1st Draft" to "Drafts" and within "Drafts" link to "1st Draft" and to other versions. Among these could be (i) the version Alison started under another name (not "2nd Draft" yet), (ii) a version with the Community and Leadership sections cleverly merged, (iii) a version with the Community and Leadership sections on separate pages, etc.. For now, with the WECC meeting later this month, this approach might generate too many pages to watch and continually synchronise. If we do something like this we will have to be very clear which is the current working version for wording of sections and their headings; the others mentioned (i - iii) would be more to do with structure. Suggestions welcome. - Kim Tucker 10:37, 2 April 2011 (UTC)

Instead, created the "Staging area with a link to it in the template above. - Kim Tucker 08:41, 5 May 2011 (UTC)

WikiEducator Code of Conduct v11.01.00


Add intro text with global cultural appeal?Progress: done Effort: unknown Priority: low

Submitted by: Kim Tucker 01:27, 14 January 2011 (UTC)
Status: Done: no suggestions or strong feelings expressed re the need for this (for version 1.0)

Could we add something of global cultural appeal similar to the introduction to the Ubuntu Code of Conduct?

Closing this issue for version 1.0. - Kim Tucker 02:44, 2 April 2011 (UTC)

>>Be mindful of the community and interdependencies

Simplifying the title to "Be mindful of the community" (removing implicit reference to Steven Covey's "interdependence". - Kim Tucker 09:18, 2 June 2011 (UTC)

Rename Section and reword

Rename to: Be mindful of the community and interdependenciesProgress: done Effort: easy Priority: medium

Submitted by: Kim Tucker 03:47, 2 April 2011 (UTC)
Status: Resolved - Kim Tucker 12:26, 3 May 2011 (UTC)

Questions: Do we need this section? It is about being mindful of the community. Should it go under "Be respectful"?

Proposed wording - Kim Tucker 03:47, 2 April 2011 (UTC)

Be mindful of the community and interdependencies

While WikiEducator may be used freely and effectively by individuals working in isolation, its strength lies in its support for collaboration in the production and sharing of learning resources.

When editing pages or expressing ideas or opinions on WikiEducator fora, or when modifying code or adding features (as a system administrator), or when making decisions, be mindful of the wide and diverse community of educators, learners and other interested and affected parties.

Updated - Kim Tucker 01:16, 5 April 2011 (UTC)
Great improvement to "Be considerate". I had been thinking that we should collapse "considerate" into "respectful" (what I was trying out on the other page), but this is very clear and to the point. As for wording, I suggest listing "editing pages" first, as editing pages is more universally understood than modifying code and features. I think it's good to start with concepts that most everyone understands. --Alison Snieckus 00:14, 3 April 2011 (UTC)
Good point - done (starting with "editing pages"). - Kim Tucker 10:31, 4 April 2011 (UTC)

The next sections "Be consultative" (below) and "Be respectful" follow naturally from this statement, and suggest what being "mindful of the community and interdependencies" means. It would be too involved to enumerate and elaborate on specifics which could include changes to the MediaWiki installation, templates, other people's user pages, official policy pages, project charter pages, pages in use in an on-going course, .... Guidelines for these roles/situations would be useful and for WikiEducator and/or for specific projects (e.g. in a project Charter).

Agree that we should have more detailed guidelines to inform the revision process for these various types of pages. --Alison Snieckus 00:14, 3 April 2011 (UTC)
Proposed wording - Kim Tucker 03:47, 2 April 2011 (UTC)

Be consultative - See "Be collaborative" below.

Interested and affected parties may range from one or two individuals to the entire WikiEducator user base. Decisions affecting the entire WikiEducator user base are reached via an approved collaborative process often facilitated by a Community Workgroup. Sub-communities may establish project workgroups for this purpose with their own styles of leadership and interaction. Whatever the scale, before making a significant change which is likely to affect others, and where practicable, consult them, strive for consensus, and after due consideration proceed accordingly.

Note that in some cases this might involve creating an alternative version of a page, etc. It also covers "When disagreements arise, consult others" which may be removed (check we will not be losing anything).

I'm a bit confused about "Be consultative". "Be mindful..." seems pretty clear to me; I don't think it needs this further clarification. Also, "Be consultative" overlaps with both "Be respectful" and "Be collaborative" to some extent and it gets into more detail than I think is needed in this broad-based code. Just my thoughts. --Alison Snieckus 00:14, 3 April 2011 (UTC)
Agreed. I will try to merge and rearrange a few things in blue above and below. - Kim Tucker 00:11, 5 April 2011 (UTC)
The following replaces "Be consultative" following on from "Be mindful of the community and interdependencies" (elaborating on interested and affected parties) and leading into being respectful below:
Proposed wording - Kim Tucker 01:29, 5 April 2011 (UTC)

Be collaborative

Collaboration is central to WikiEducator and to the wider open education community. Collaboration streamlines the production of learning resources, and improves the quality of our work.

Whatever the scale of the project or activity, seek collaborators at the outset and continue with transparency, inclusivity and continuous communication of intentions and progress. Strive for consensus, and follow due process.

Wonderful concise replacement for previous version. Much improved. I do question, though, if "seek collaborators" is too directive. I think there are situations where an educator just wants to get started on something and doesn't want to take the time to actively seek collaborators. However, if someone came along (eg expressed an interest on the discussion page), they'd be more than welcome. How about " open to collaborators at all points in the process and work with...." There are projects where it is important to "seek collaborators", we could indicate that here, or let the community workgroups guidelines take care of that, which means this statement remains broad-based and applicable to all. --Alison Snieckus 00:54, 7 April 2011 (UTC)
Done. I kept it broad-based and applicable to all. - Kim Tucker 12:24, 3 May 2011 (UTC)

>>Be Collaborative

See above. The suggestion is to remove "Be Considerate" and to place "Be Collaborative" before "Be respectful".

I like the new flow. It's helpful to see how it hangs together in the beta version. I think we are ready to revise the first three in the 1st draft version. --Alison Snieckus 01:05, 7 April 2011 (UTC)
Thanks. Done :-) - Kim Tucker 12:33, 3 May 2011 (UTC)

>>Be Respectful

Proposed change to supporting textProgress: done Effort: easy Priority: medium

Submitted by: Alison Snieckus 00:38, 3 April 2011 (UTC)
Status: Resolved - Kim Tucker 12:28, 3 May 2011 (UTC)

The supporting text in the current version seems a bit redundant.

Proposed wording - Alison Snieckus 00:38, 3 April 2011 (UTC)

Everyone can make a valuable contribution to WikiEducator. We may have very different perspectives and may not always agree, but disagreement is no excuse for disrespectful behaviour. Rather, in a healthy collaboration we use differing viewpoints to advantage the outcome, choosing to share our differing opinions in a professional manner, to resolve disagreements using consensus decisions, and to refrain from personal attacks--play the ball and not the person.

This rewording attempts to keep the essence, as well as use more active, positive language--we value diversity.

I like the more active, positive language. Can we take it slightly further? For example:
Everyone can make a valuable contribution to WikiEducator. We share our differing viewpoints and opinions freely, in a professional manner, while striving for consensus in decision making and for enhanced quality of the learning resources we produce. We may have very different perspectives and may not always agree, but at all times maintain a tone of mutual respect and acknowledge each others' contributions appropriately. - Updated to include attribution as part of being respectful - Kim Tucker 01:36, 5 April 2011 (UTC)
I do like this revision. It includes all of the major points and is positive and encouraging. Good idea to include the bit about acknowledging each others' contributions. --Alison Snieckus 01:00, 7 April 2011 (UTC)

>>When unsure, ask for help

Add section for offering help?Progress: done Effort: unknown Priority: medium

Submitted by: Alison Snieckus 02:08, 8 March 2011 (UTC)
Status: Resolved

In addition to content related to asking for help, this section includes a sentence about offering help. The inclusion of suggestion for how best to offer help seems out of place. I suggest we add a section to cover offering help: "When knowledgeable, offer help"?

Good idea. This may also help improve the section "Be collaborative" which seems different from (e.g.) "Be helpful". One does not have to be knowledgeable to be helpful - we can help each other and learn together. - Kim Tucker 09:01, 8 March 2011 (UTC)
On further reflection, being collaborative is about being open to broader collaboration. Another way to make "offering help" more in place might be to rename the section:
Proposed wording - Kim Tucker 02:24, 2 April 2011 (UTC)

Help each other

Nobody knows everything, and nobody is expected to be perfect in the WikiEducator community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked (or who discover open) questions should be responsive and helpful where possible.

I am not sure the last sentence is necessary? It is too specific and probably covered under being 'respectful', 'considerate' or 'mindful of the community'. - Kim Tucker 11:09, 4 April 2011 (UTC)

Removed it (However, when asking a question, care must be taken to do so in an appropriate forum.)
The retitling is perfect and the supporting text is very clear. I agree that the former last sentence isn't helpful; I've seen many new users ask questions in the wrong forum (eg, his/her own user talk page)--we learn which forum is appropriate/productive with experience:) I suggest that we are ready to put this one into the 1st draft. --Alison Snieckus 01:22, 7 April 2011 (UTC)

>>Assume Good Faith

Concerning the last sentence: "Be civil and strive for consensus or agreement on a constructive way forward for all parties." We've already included this idea in "Be respectful" and "Be collaborative". I think we can safely delete this sentence. --Alison Snieckus 01:52, 7 April 2011 (UTC)

I'm wondering if the statement "...which may become heated when passions run high on some particular topic" is irrelevant to this point. This phrase harks back to be respectful, collaborative. Rather, an aspect that we might consider including here is misplaced or unintentional edits of inexperienced users. In that educators often come to WE with little experience relevant to working in a wiki environment, I think we will continue to experience inappropriate (but not in a bad way), unproductive (eg., replying to a discussion question in the activity box when that is not the intent of the activity), misplaced or unintentional edits. I see them pretty often. Would it be useful to add the concept of "unintentional" (is there a more effective word?) edits to this principle? --Alison Snieckus 01:52, 7 April 2011 (UTC)

Good point. I have updated with the following:
WikiEducator welcomes and encourages newcomers and inexperienced participants who may be unfamiliar with the emergent culture and wiki environment. Occasionally, misplaced edits or comments with unintended implications arise. Most people mean well and contribute with a view to enhancing the resources on WikiEducator. In general, assume good faith unless there is clear evidence of malice.
Okay? - Kim Tucker 12:38, 3 May 2011 (UTC)
The rewording is a great improvement, effectively capturing the WE environment. Well said. --Alison Snieckus 23:47, 4 May 2011 (UTC)

When disagreements arise, consult others

See "Be consultative" above and consider whether this section is still necessary if we already have the principles of being consultative, respectful, ... ?? - Kim Tucker 11:14, 2 April 2011 (UTC)

Default action (i.e. if no objections): retain it (or variation).

I vote for dropping this section. As Kim suggests, the concepts are already included in be consultative, respectful...., and the suggestions in the supporting text for resources to help with a disagreement are insufficient to be helpful. I suggest that this topic be dealt with in a guideline, eg. "How to address a continuing disagreement". --Alison Snieckus 00:08, 5 May 2011 (UTC)
Another good suggestion, with no objections so far. I'll make the change and adapt the "Be collaborative" section slightly to reflect the option of creating alternative resources. - Kim Tucker 08:13, 2 June 2011 (UTC)


IMO some of this section presupposes certain views on leadership which do not apply to all classes of leader which may emerge on WikiEducator. Without adding additional definitions (e.g. virtuoso, visionary leader, team leader, project leader, workgroup leader, catalyst, animator, inspirer, manager, ...), the following eliminates some of this, merges sections and eliminates redundancy (given that Leaders epitomise the rest of the Code of Conduct).

Recommend: write separate guidelines for WikiEducator leaders (and/or link to Leadership courses etc.). See the Resources page.

I suggest that we not organize the leadership principles in a separate heading. I think most educators understand that collaboration will utilise various types of leadership, and given our goal to be concise, even minimalist, we don't need to say it here. (Instead I recommend creating a "Wikieducator:Leadership" page, and move the general text about leadership to that page, with a link from the first use of the term leader in the supporting text. And, I agree with the recommendation to create more specific, detailed guidelines for leaders.) --Alison Snieckus 00:25, 5 May 2011 (UTC)
Hand-in-hand with the idea to drop the leadership section, I suggest we develop one overarching principle on leadership for this code of conduct. As the comments (on the various points below) suggest, there is some overlap in this section with the other principles, and I think the listed principles would be better presented in guidelines. My thought is that the one principle encourage people to take on and share leadership, and not overly defer to leaders--understand that WE are all equals, no matter our role/title. Maybe the principle could be "Encourage leadership", suggesting we help others be leaders, as well as consider leadership roles ourselves. In some ways, I see the principle as similar to the "Be bold" pillar at wp--if you have a good idea, suggest it, try it out, encourage others to join you, help make it happen. --Alison Snieckus 01:11, 5 May 2011 (UTC)
Thanks for the support and suggestions :-). I have created a WikiEducator:Leadership page. For now it has all the text from the Leadership section which I will remove. Below is a suggestion for the one principle for Leadership on WikiEducator (already replacing the previous Leadership section). - Kim Tucker 09:00, 2 June 2011 (UTC)
Leadership principleProgress: done Effort: medium Priority: high

Submitted by: Kim Tucker 09:00, 2 June 2011 (UTC)
Status: No objections after 3+ weeks (suggested change accepted) - Kim Tucker 21:50, 24 June 2011 (UTC)

Alison suggests one Leadership principle for this code of conduct and that we move the text into WikiEducator:Leadership (done).

This issue is to refine and finalise the wording of that one Leadership principle. The following is based on Alison's suggestion.

Proposed wording - Kim Tucker 09:00, 2 June 2011 (UTC)

Encourage leadership

Leadership emerges at multiple levels within the community and our aim is to foster an environment which encourages leadership and innovation.
WikiEducator leaders epitomise this Code of Conduct, lead by example and encourage others likewise to express their ideas, try them out, and in turn encourage others to participate in bringing them to fruition.

>>Lead By Example

Simplify "Lead by example"Progress: done Effort: routine Priority: medium

Submitted by: Kim Tucker 01:03, 5 April 2011 (UTC)
Status: Change accepted (no objections) - Kim Tucker 12:43, 3 May 2011 (UTC)

Leaders "epitomise this Code of Conduct" - so, much of what was previously written in the Leadership section is covered elsewhere.

Proposed wording - Kim Tucker 01:03, 5 April 2011 (UTC)
The Code of Conduct does not only apply to leaders, it applies to leaders more. Leaders show more patience, more respect, more civility than other members of the WikiEducator community, and epitomise this Code of Conduct. Their contributions are sustained, significant, reliable and recognised by their teams, collaborators and the broader open education community.

>>Respect and advance WikiEducator processes and principles

Simplify "Respect WikiEducator processes and principles"Progress: done Effort: routine Priority: medium

Submitted by: Kim Tucker 01:03, 5 April 2011 (UTC)
Status: Change accepted (no objections) - Kim Tucker 12:45, 3 May 2011 (UTC)

Reducing inclusion of principles implicit elsewhere in the Code of Conduct:

Proposed wording - Kim Tucker 01:03, 5 April 2011 (UTC)

Respect and advance WikiEducator processes and principles

Leaders take care to act in accordance with WikiEducator governance principles and structures, and work within the WikiEducator system to change them if required.

Note the change in the title and that some of the previous content of this section has been moved into "Lead by example" above.

>>Inspire and facilitate collaborative action

Reducing inclusion of principles implicit elsewhere in the Code of Conduct:

Redesign "Delegate"Progress: done Effort: routine Priority: medium

Submitted by: Kim Tucker 01:03, 5 April 2011 (UTC)
Status: Change accepted - Kim Tucker 12:47, 3 May 2011 (UTC)

To avoid repeating "lead by example" and other aspects of the general code of conduct (e.g. being respectful and acknowledging each others' constributions):

Proposed wording - Kim Tucker 01:03, 5 April 2011 (UTC)

Inspire and facilitate collaborative action

Leaders know when to ask for help, when to step back and when to take action. Leaders know when not to make a decision but to delegate it to their teams and other collaborators. Leaders have a talent for sharing the work load and inspiring collaborative action in accordance with this code of conduct. Effective leadership results in getting the right things done in the right way, personal growth and empowerment among participants, synergies and collective effectiveness.

>>Credit the contributors

Reword and rename "Credit the team"Progress: done Effort: routine Priority: medium

Submitted by: Kim Tucker 22:20, 5 April 2011 (UTC)
Status: Change accepted - Kim Tucker 12:49, 3 May 2011 (UTC)

This aspect is implicit under in the general Code of Conduct under 'Be respectful' (see new suggested wording above). One option is to delete it from the Leadership section? On the other hand, we could include a variation generalised for Wikieducator where leadership can emerge spontaneously at various levels and groups of participants are not necessarily assembled into teams.

Default action: include the following variation:

Proposed wording - Kim Tucker 22:20, 5 April 2011 (UTC) (UTC)

Credit the contributors

Leaders are highly appreciative of the work of participants. While WikiEducator leaders are frequently more prominent in the open education space, they use their visibility to highlight the great work of their team members and other contributors.


Manage Conflicts of Interest

Keep the Personal Personal

>>Step Down Gracefully

Too long? Perhaps only include the first paragraph (or a variation of it) and relegate the rest to a guideline document for WikiEducator leaders? - Kim Tucker 01:03, 5 April 2011 (UTC)

Default action: include only the first paragraph (or variation of it).

Removed all except that paragraph. - Kim Tucker 12:51, 3 May 2011 (UTC)


>>Mailing lists and web forums

This section is not needed (IMO) - Kim Tucker 03:03, 5 April 2011 (UTC)

Default action (i.e. if no objections): remove it.

Removed - Kim Tucker 12:52, 3 May 2011 (UTC).

References (within this Issues page)

  1. See for example Code of Best Practices in Fair Use for OpenCourseWare.

Issues for Future Versions