• Draft guidelines moved to http://pad.p2pu.org/p/school-of-open-guidelines.??????????

=== Molly: Measure Openly (building, publishing, documenting) ===

I'm imagining here a researcher, Anna Van Deventer, who studies weather patterns in North America. Based at the University of Minnesota, she focuses on the fluctuation of average temperatures, comparing historical records with contemporary weather data. Her work is deeply enmeshed with the ongoing act of measuring. 

Tools: While much of the weather data that our researcher collects comes from third parties, she does a substantial amount of first-hand data collection. She uses highly sensitive thermometers.  To measure more openly, she would use thermometers built with both open hardware and open software. If like many scientists she builds her instruments and creates custom software to run them, she would share the schematics and methods for the instruments, and both share and license the software so that other people could both use and build on her work.
Software for data processing/analysis: using R instead of Stata. Otherwise, the software may not be available to all of her students, or collaborators at other institutions. 

Content: The results of our researcher's measurements are data. To measure more openly, she would share that data publicly and accessibly in open formats and with good documentation (which itself is available under an open license), and make clear that she does not claim any proprietary rights in the data, possibly through a data license (depending on her jurisdiction).
She publishes articles on the results of her research, and either publishes in OA journals or publishes her articles in traditional journals and deposits the final versions in her university's institutional repository.

Processes: Processes govern both our researcher's use of tools and the production and management of data. To measure more openly, our researcher would share, perhaps on a blog or a discipline-specific open science website, her methods for creating and using her tools, the assumptions implicit in her research, and the statistical processes she uses to analyze her data. (See how other researchers use open lab-books, and how they benefit from working "in the open")

4 open practices

1. use and build on: The researcher uses large amounts of public and government produced weather data, combines it with the data she has collected herself, and produces large comprehensive datasets of temperature data in the United States.
2. facilitate sharing: She shares her data publicly, in open formats, with clear documentation. 
3. enable reuse and adaptation: She shares her data publicly, in open formats, with clear, openly licensed documentation. 
4. support transparency: She writes about her processes publicly, and welcomes both scrutiny and contributions from her colleagues. 

=== Pieter ===

Teaching, writing, editing, collaborating, learning

Franzie volunteers as a tutor to students at 826 Valencia. Last week he was working with a 10th grade girl, Shashona, on a writing project. She was struggling to round out the conclusion of her short story. Franzie had an idea that Shashona should get her classmates to help her end the story. This seems like a more open way to do things that could really benefit everyone. Shashona can get helpful feedback and tips, her peers get the experience of helping with editing and the writing. How can Franzie use the School of Open to help Shashona share her work with her peers?

Using/building on //

• - content: Shashona could go through the web looking for short stories and getting ideas for how to end hers; even better, she could limit her reading to only CC licensed blogs/sites
• - tools: lots of open source software tools exist for publishing writing on the web, like Wordpress, which is free and has lots of interesting/useful plugins (and can also be built upon in the future)
• - processes: Shashona might find some helpful writing/brainstorming processes on the web
• 
  

Enabling use, adaptation and sharing of //

• - content: to encourage more adaptation of her work, Shashona can attach a CC license that enables derivatives; 
  • Q: are there spaces where you can list CC only materials that create more exposure? link between "encourage more adaption" and CC
• - tools: the platform Shashona uses for publishing could also allow for multiple authors to edit the story - an etherpad, for example; she could also allow for commenting directly on her story, creating a public record of suggestions and ideas
• - processes: 
• 
  

Supporting transparency in //

• - content
• - tools
• - processes: Shashona could publish a description of her writing process along with the story - this might inspire comments from people about how to spark some new creative ideas to finish the story

Things to think about in openness //

• - examples of people who do this (Cory D.)
• - online communities where she can submit content for review/help
• - what are the downsides to using a CC license in this scenario? (other FAQs for this?)
• 
  

**
how does openness help?
how might it hurt?
FAQs
what open practices fit best?
why does openness matter here?
what questions might the person ask in the scenario?
- how do we answer those questions by framing it in openness?
**
next up?
- refine and standardize scenarios
++ list actions for each
++ describe scenario and people
++ indicate audience and domain area
++ choose one or more questions for an individual in the scenario to ask
++ answer the questions by describing attributes of openness that can help and how they can help

• - break up each attribute into tools, content and processes that might apply

++ see what lessons fall out and what learning resources we can point people to


=== Philipp (finding, licensing, creating, publishing, earning cash) ===

Till Melchior is a professional photographer. He sells most of his work to advertising agencies. One of his specialities is the mashing-up of different images (using Photoshop). He not only uses his own photos to creates these collages, but often includes photos he finds on the web or in old magazines. He wants to know what the legal regulations are that govern the use of this content - he doesn't want to get in trouble or have to pay royalties. He is also interested in sharing his work with more people online, to increase his audience and find more customers, but he is concerned that someone may take one of his photos and use it commercially without compensating him. He wants to better understand what tools & practices otehr photographers use and how openly sharing affects his business model. 

How can I find photos that can be re-used / adapted?
- content: photo hosting sites that let you search by license
- tools: open source photo editing tools (although I think the reality is that most professional image editors are NOT using gimp)
- processes: search strategies

What are the legal regulations I have to follow? How do I attribute the authors? What if I made a mistake?
- content: what are the legal restrictions that apply to content I find online? 
- tools
- processes

How can I share my work (both unique photos or mash-ups) openly with others? What's the best place to host them? How do I engage with my community? What are the file formats and resolutions I should use? 
- content
- tools
- processes

How can I make a (good) living as a photographer, when everyone already has access to my work for free online? 
- content
- tools
- processes


= Jane =
Lead (School of Open) openly  (communicating, planning, documenting, decision-making, managing,  imagining, collecting, writing, reading, learning, debating, thinking,  collaborating)

by incorporating

4 open practices

1. use and build on
2. facilitate sharing
3. enable reuse and adaptation
4. support transparency

using

3 types of resources

• tools
• content
• processses

1) use and build on

• Find  and read existing resources about open leadership, some academic  publicatoins (theory), some examplesc/case studies of practice. Blog  about what you are reading and your reactions. CC license your blog and  any other writings that come from this exploration.
• Find  others leading similar initiatives such as yours and share blogs.  Discuss readings with your peers. Debate about which methods work and  don't work. Share resources you find.
• Decide  to come up with some open leadership guidelines together, building on  readings and what's already out there (under open licenses).
• Share rough open leadership guidelines with world and invite feedback (under open license).
• For all of the above, use open source platforms wherever it is possible and appropriate.

2) facilitate sharing 
3) enable reuse and adaptation

• Draft  description of project in collaboration with community -- by drafting  with volunteers and then sending it back out to community for feedback.  And continuing evolution of document over time. 
• Provide  communications channels/tools where people can discuss project and give  feedback, eg. School of Open discussion list/google group.
• Create  your own content and share it to set an example, eg. course on CC  licenses. Ask for feedback on course and help building. Build on  existing CC license educational resources and give credit to original  authors; invite authors to help adapt to new course at p2pu.
• Openly  license as much documentation related to running the project as  possible (leadership resources above). Host it openly w/proper license  marking, etc.
• Openly license the project's /about and related resources.
  • Make sure the open license is marked properly, machine-readable, etc.
  • Upload resources as relevant to as many different CC enabled platforms as possible.
• Openly license the project's courses on p2pu.org (by default CC BY-SA).

4) support transparency

• Communicate what you are going to do before you do it. (transparency?) (gunner's 3 step process -> (1) tell them what you'll tell them, (2) tell them, (3) tell them what you told them)
• Get   community buy-in to project by holding virtual sprints, offline   workshops where possible, and using open communication tools to create   pieces of the project. (transparency?)
• Document everything and share it on website/blog under open license.
• Clearly  outline at what points I am welcoming feedback and how that feedback  will be incorporated/received. Provide place for that feedback, eg.  listserv, pad, etc. eg. map of feedback loop?
• Expose process for what is and is not an "open" course, and provide way to get feedback.
• Clearly  explain CC and P2PU's roles/collaboration to community, and other  volunteers' roles. How this all relates to each org's mission, etc. 
• Encourage others to do the same in terms of sharing their own process of building an "open" course. (Advocate for open)

Some additional topic suggestions:

• How do I facilitate collective decision making in open communities?
• What are legal limits to openness in formal organizations?
• Communicating openly and effectively
• Building values & culture

NOTES:

* more about community around a question than a factsheet/resource in a course
* a place for Q&A between peers/facilitators at different points of course
* ask people at end to add new content for next course (pay it forward)
** update resources with each iteration

next up?
- refine and standardize scenarios
++ list actions for each
++ describe scenario and people
++ indicate audience and domain area
++ choose one or more questions for an individual in the scenario to ask
++ answer the questions by describing attributes of openness that can help and how they can help

• - break up each attribute into tools, content and processes that might apply

++ see what lessons fall out and what learning resources we can point people to