3. Practicing openly/open practice (cont'd) (Aug. 19-25)

Now let's explore openness a bit further by engaging in open practices. This will also be a way to start getting a good handle on both the benefits of openness, and some of the issues that may come up when practicing openly.

You can earn a badge for engaging in an open practice in your group and writing a blog post about it! See the "Why Open? Practicing Open" badge on the left menu.

There will be a synchronous Google Hangout on Tuesday, August 20, 17:00-18:00 UTC / 1:00-2:00 PM EDT / 8:00-9:00 PM EAT / 5:00-6:00 AM NZST / 10:00-11:00 AM PDT facilitated by Jeannette Lee. Please sign-up on the course etherpad: http://pad.p2pu.org/p/Why_open_course_pad. We had to move this to a Twitter chat, b/c we had technical difficulties during the Google Hangout. Here's the record of this chat: http://storify.com/jeannettemelee/archive-of-week-3-why-open-google-hangout-twitter

We will also have a Twitter chat this week (hashtag: #whyopen), on Friday, August 23, at 19:00-20:00 UTC / 3:00-4:00 PM EDT / 10:00-11:00 PM EAT / 7:00-8:00 AM NZST / 12:00 NOON-1:00 PM PDT. Here's the record of this chat: http://storify.com/jeannettemelee/archive-of-why-open-week-3-twitter-chat

At our first Google Hangout session, we decided to create a couple of collaborative documents. Please contribute to them if you'd like!

A. Open Activities--in groups

This week, your group will be engaging in an open practice--either one of those listed in the discussion area from last week (section 2 on menu at left), or one from the list below. As a group, choose the activity you'd like to do. Then either split it up so members do different parts, or each person try the activity themselves...whatever seems most relevant for what you've chosen.

If you have questions or comments or run into problems, you can work together to discuss and try to address them. You could also ask questions in the discussion area below, if talking about them in your group isn't getting you the answers you need.

It's possible you won't finish the whole activity before the week is finished and you need to write your blog post (see part B, below)! That's okay. Just do what you can.

Choose either one of the activities that groups listed in the discussion area, or one of the following:

B. Blog post and comments, individually

1. Reflective blog post

After your group has completed your chosen activity (or not, as the case may be--it's okay if you don't entirely finish but just get partway!), each person please write a reflective blog post about what you did. You could address one or more of the following questions, or write about some other aspect of the process and how it relates to openness.

  • How was your activity an "open" practice, in your view? You could relate what you did to your earlier blog post on openness, or to something you read from someone else about openness, if you like.

  • What CC license did you choose if you were creating content? Why?

  • Did you run into any problems or barriers? If so, please explain what they were and how you tried to address them (if possible). Were these issues related to openness in some way?

  • Was this process beneficial to you in some way? What benefits can you imagine open practices might bring?

  • What did you learn through this process about openness, or about anything else? What did you learn from your peers in your group?

  • What questions do you have at this point?

2. Commenting on others' blog posts

Just as in previous sections of the course, please choose at least two other participants' blog posts to read and comment on. Once again, try to find people whom you haven't given comments to before! The blog hub can be found here: http://www.whyopencourse.org/bloghub/

You could ask them a question, discuss something in their post that you agree with (and why), or something that made you think differently than you did before, something that was new and interesting to you, or something you disagree with (and why), or whatever else comes to mind.


comments powered by Disqus