![\"Weave](\"https:\/\/johnjohnston.info\/blog\/images\/2013-05\/2013-05-19_weave_comp.jpg\")
<\/p>\n <\/p>\n
Teach the Web Week 3: the Open Web<\/a><\/p>\n Plan your makes with your collaborator and then do it! If you\u2019re in a study group<\/a>, you\u2019re encouraged to work together around your topic. Share your makes with the #teachtheweb community<\/a>.<\/span><\/p>\n<\/blockquote>\n Among the suggestions for reflection were:<\/p>\n There are lots more suggested activities and reflections, but that was enough for me<\/p>\n Thinking about my activity in the Mozilla Webmakers – Google+<\/a> group this week gives, I believe, a little insight into some of these questions. I was not actively considering them, just reading and playing.<\/p>\n First Walter Patterson<\/a> a fellow Scot contacted me with an idea of working together on a thimble page about a couple of ‘open’ projects. We have started work on this. The first benefits of open I met were, getting an idea of what to do<\/em>, Walter reminded me that EDUtalk<\/a> was an open project. and then working off Walter’s thimble edits I got to a reasonable page: EDUtalk is Open<\/a> (not as yet finished). I didn’t have an idea where to start until I’d seem Walter’s starting point. So the second benefit of working in the open is finding ideas, they don’t all come from serendipity. <\/p>\n Once I had thought of EDUtalk, I though that it might be a good place for talking about open collaboration. EDUtalk itself is an example of working in the open, part of it consists of a podcast that is open for anyone to contribute to. THe other part is a weekly internet radio broadcast that becomes a podcast, we publish in the open under a CC BY-NC-SA 2.5 SCOTLAND<\/a> license. I invited folk from the Mozilla Webmakers<\/a> community to participate, at very short notice. Chris Lawrence<\/a> and Laura Hilliger<\/a> stepped up and stepped into the skype studio for Radio #EDUtalk 15-05-13 #teachtheweb<\/a>. This is another example of getting great contributors by working in the open. I am constantly amazed at the interesting folk I get to talk to just by running a podcast.<\/p>\n The rest of the week I have had a bundle of fun by getting ideas from other webmaker participants. One of the things I wanted to get out of the MOOC was to improve my webmaking skills. I’ve found it difficult to learn the skills by doing exercises, but often find, time constraints lead me to use less that elegant solutions when working on a ‘real’ web site.<\/p>\n This wek I’ve found that I’ve learnt by doing small things, these have been inspired by the open sharing of ideas and projects by others in the MOOC.<\/p>\n Somewhere in the group a comment by Chad<\/a> lead me to mess around with a little CSS to make A Crown for Chad<\/a> the request for others to mix it up was taken up by a few folk, Pekka Ollikainen<\/a> took it to JavaScript<\/a>, teaching us some canvas animation and showing this using JS Bin<\/a> a great companion to thimble.<\/p>\n I saw a post<\/a> by Heather Angel<\/a> wondering about how to to create a layout that is made to be constantly updated<\/em> in thimble. As I had been wondering how to keep track of thimble edits I though I’d try something. Thimble Chaining<\/a> is a simple thimble page with a google form and the resulting spreadsheet embedded. The idea would be to use the form to add your name and the url of the edit you just saved. Not very elegant, but it does the trick. I believe Mozilla are working on a solution that will track edits and pages spawned from the first page. This will would be a very useful addition to the system.<\/p>\n The last bit of fun this week was sparked by Chad again, he was making an “Open is…” inspirational web app collaboration from the Writing as Making, Making as Writing study group<\/em>. The latest version by Chad is here: #teachtheweb: Open is\u2026<\/a>. As Chad was collecting quotes via twitter, I was thinking of automating that. I tried a couple of approaches, using ifttt.com to collect #open_is tweets to a google spreadsheet<\/a> and then loading that via javascript: open-is – JS Bin<\/a> I also pulled then in directly from a twitter search: Random #open_is tweet<\/a><\/p>\n What I was learning, using JS Bin<\/a> was dealing with json in JavaScript, I got a lot out of this play, more that I do following tutorials or interactive lessons. I believe this increase in learning is due to playing in the open, the open provides the ideas and perhaps an audience. I am not sure if my edits are very useful, compared to human curation in this case but a great learning exercise for me.<\/p>\n Of course it is open for anyone to join in. The Mozilla Webmakers – Google+<\/a> group is open to anyone and valuable for that. But I am struggling to keep up with conversation. The site works well for joining in with the moment, the iOS apps are great, but there is something missing. I can’t keep a record of my activities. I mentioned this in the last post<\/a> too, but if I am learning here, I want to track my progress and wanderings. As a learner by progress is important to me and I am having trouble following it.<\/p>\n Picked up, ironically, via my Google Reader this morning was a post with much better, deeper thinking on this issue:<\/p>\n It seems to me that with Google+, Google is not adopting open syndication standards in two ways: not using it \u201cinternally\u201d, and not making feeds publicly available. There may be good technical reasons for the first, but by the second Google is *not allowing* its community members to participate in a open content syndication network\/system. Google\u2019s choice, but I\u2019m not playing.<\/p>\n<\/blockquote>\n\n
\n
\n
Working with Walter<\/h3>\n
Open Talk<\/h3>\n
Open Learning<\/h3>\n
Crowning Chad<\/h3>\n
Thimble Tracking<\/h3>\n
Open Is…<\/h3>\n
Google + is not Open!<\/h3>\n
\n