Practically Open

As part of the week 1 of P2PU Why Open? course participants were invited to join David Wiley on a google hangout (Why Open session with David Wiley). I could not make the live stream so have just finished watching the archive.

I’ve also posted the audio ripped from the session, with permission, over at (As usual I find audio easier to access than video).

These are a few of the things that I found interesting in the hangout, not in any order and very much my own interpretation.

David is the founder of, among many other things and a expert on open content and open educational resources.

Throughout the talk David focused on the pragmatic rather than the idealistic, on what would make an impact over what was right or righteous.

He started talking about the difference between the Free Software movement and the Open source movement, and how Richard Stallmam’s Four Freedoms inspired all the openness that followed. David’s view is that Open is less do do with correctness & morality and more practical.

David say Free involves a bit of moral grandstanding, giving no place for proprietary software. Open says open is practical and we can choose not to be open which is not morally bad.

The other side of the argument is laid out here: Why Open Source Misses the Point of Free Software – GNU Project – Free Software Foundation and The Four Freedoms from Matt Mullenweg are worth considering from the pov of the practicality of Free Software.

David talked of the Berne Convention that in 1886 changed the face of copyright:

Under the Convention, copyrights for are automatically in force upon their creation without being asserted or declared. An author need not “register” or “apply for” a copyright in countries adhering to the Convention. As soon as a work is “fixed”, that is, written or recorded on some physical medium, its author is automatically entitled to all copyrights in the work and to any derivative works, unless and until the author explicitly disclaims them or until the copyright expires.

from: Berne Convention – Wikipedia.

This switch the default from you are ok to copy to you are not. If you publish something you need to legally state wish to share. This leads to existing material with unknown copyright is not being published.

David works with the Open Content Definition which uses the 5 Rs the rights to Retain, Reuse, Revise, Remix and Redistribute. The Retain right has been added to address, and highlight, the problem of business models that control access, eg, stream media.

David gave a few examples of the practicality of open, obviously OERs are cheaper than textbooks, but a major gain in moving towards open might be in higher where the movement to competency based course is slowly gaining ground. The argument is that these competencies are slow to develop and the process could be speeded up by opening the competencies. Open assessments would be another area to explore.

Someone in the hangout expressed the worry that publishing in the open would be less useful from an employability angle than publishing to well established (and paywalled) publication. David discussed the idea of the impact of publishing on the open demonstrating with Google Scholar the number of times open publications are cited as compared to paywalled ones. Publishing in open will maximise the number of people reading so giving a better chance of making an impact. Again the outcome was more important than the philosophy.

Exploring another tension, that of Open vs Connected, David proposed that connected is a vice when taken to extremes. For example there are now so many resources in google it is hard to identify the best resources. More nodes and connections becomes noise at some point. Curation and structure needed on top of connected. Curation is biggest value that faculty brings to learning. Neither open or connected should not be their own end.

My own practise of working/blogging/learning in the open is based on a fairly fluffy feel good factor. I’ve found over the years that this has had a positive effect on myself and learners I work with. I covered this in a previous post. I now feel that it will be important to start to try and bring openness more formally into my day to day work and made small steps in that direction today. Instead of looking for good vibes I’ll be trying to introduce open where it can make an impact.


Tom Bennett on Radio Edutalk

A lot of educational research, and I am going to choose my words carefully here, was utterly guff, was utterly, utterly guff, by that I mean, was complete speculation, rhetoric or opinion dressed up as science.

Tom Bennett talking on Radio #EDUtalk.

Radio Edutalk got off to a flying start last night with a great show. I am sure if the fact I was not near a mic had anything to do with this;-)

David talked to Tom Bennett about research in education. Stirring stuff, I nodded along to the trashing of Brain Gym and the like and the podcast gave lots of food for thoughts. A couple of places I really wished I had been near a mic:
One round Tom’s idea that teachers should not be researchers. We have talked to a fair number of folk doing action research on Edutalk and I think their experience is valuable?

The other was picked up from a couple of different sections of the podcast, in one Tom talked about the conferences he is organising being a place teacher could work things out from themselves away from the influence of councils (I am paraphrasing here). Later he suggested that chains of Academies, were big enough to carry out scientific research. My Local Authority hat wanted to asks if he would consider LAs suitable bodies to organise research perhaps in conjunction with nearby Universities. I guess I am knee jerking against Academy chains and there is possibly Tom is not as aware as the Scottish system of Local Authorities.

Glow Blog Migration Notes: e-Portfolios

Lost Puppy

Lost Puppy flickr image by Tim Shields Creative Commons – CC BY-NC 2.0

Here are some notes around the effect that the glow blog migration will have on e-portfolios hosted on the WordPress instances. There are two main things to consider, users/members of blogs and links to access blogs.

User Management Issues

We are currently migrating the blogs, including e-portfolio blogs, to a new WordPress Server initially running the same version of WordPress 2.9.2

The set up will mirror the existing set up, an instance for each Local Authority. The URLs will stay the same.
The permission on the blogs and their private/glow only/ public setting will stay the same.
Only users who have previously visited the blogs while logged onto glow will have the same access.

Going forward the settings for blogs will be handled in the blog rather than Sharepoint. This is partially because the new Sharepoint is cloud based and cannot be customised in the same way as the old glow portal and partially because of the advantages of having blogs stand on their own two feet (see below for details).

Users who were granted roles on a blog though the old glow group in which the blog was created, but have never visited the blog will have to be added again. (There is no trace of these users in WordPress and therefore no way of migrating them). You can mitigate against this providing problems by asking those users to visit the blogs before the switchover. After migration Admin Users will be able to add these (or any other) users in in the blog admin dashboard.

I’ve covered more about User Management in a previous post: Blog Migration Notes: Users.

Finding your e-Portfolio

If users followed the advice on setting up glow blogs as e-Portfolios they would have created a group in the old glow portal to hold links to groups of e-portfolios. After the switch over to the new authentication in early October (3rd) the old portal will not be there.

There will be a need for teacher and pupils to be able to access blogs there are a few possibilities in the short term.

  • Lists created before the portal was migrated to O365 will still be there in your O365 group.They will be buried in the migrated content but can be resurrected.
  • You could copy and paste the list from old glow and paste into a new glow group.
  • You could recreate the lists. This would be my favoured option as I would distribute the work to pupils.

For the third approach you would need to create a space when pupils could add their e-portfolio URLs. This could be a links list in O365 or a share word document in OneDrive. Pupils would need to have permissions set so that they could add to the links or have edit permission on the document.

As a teacher I would not use links like this, too much work. I would bookmark them in my browser and put all the bookmarks in a folder. I could then log on to glow and open the folder of links in tabs. This would after a wee wait give me a set of tabs that I could quickly go through to visit each portfolio without clicks.

Post Migration Development

After migration it intended to move into phase 2 which will be an upgrade of the blog software from 2.9.2 to 3.9

Phase 3 will include improvements to the service, adding plugins and themes to increase functionality.

In Phase 3 it is the intention to improve the setup of e-portfolio blogs by improving the setup, improving how posts are organised and how the profiles are produced from those posts.
It hoped that this work should be completed by March 2015

WordPress only

The main advantages with moving the set up of blogs and e-portfolios away from Sharepoint to the WordPress server itself will be:

  • We will be able to keep the WordPress install a lot more up to date. This will allow users to benefit from new features as these are added to WordPress. With the old glow blogs it seems that it was to hard to upgrade WordPress.
  • The setup of e-portfolios will be shortened. currently I find it takes around an hour to go through the setup with a class of pupils assuming each pupil has access to a computer/device. Removing the Sharepoint element of the blogs will speed things up in the short term.
  • In the medium term the new blogs should let us develop new functionality which will speed things up even more and reduce the opportunities for making mistakes.
  • We should also be able to develop the portfolio functionality of the blogs though plugins. This could make the organisation of posts and production of the profile snapshot simpler.

Please get in touch if you have any questions about the glow blog migration.

Another migration to WordPress

flickr photo by krystian_o Attribution License

43/365 by krystian_o Attribution License

TL:DR I’ve just migrated my blog, please let me know if you find broken things and I’ll try and fix them.

In the midst of the glowblogs migration project I am involved in professional I’ve been working on a wee migration of my own. For the past nine years I’ve been blogging using pivot (later pivotx) this weekend I’ve moved to WordPress.


I started using pivot back in 2004 as my class blog mainy because it did not need a database on the website and then that cost a bit more. I stuck to it as I found it easy to theme, and adapt for various classroom projects. It seemed fairly natural to use the same system myself.

Pivotx seems to be changing but quite slowly, the promise of pivot 4 was from 2012.

I’ve been attracted to several interesting WordPress technologies and plugins and now use it for edutalk, ScotEduBlogs and my ds106 blog. The feedwordpress plugin is of especial interest.

A wish to eat my own dog food given I am promoting WordPress for glow.


Originally I though of turning the whole site/domain to WordPress, to include my ds106 blog: 106 drop in, but that looked a wee bit to tricky at the moment. I also have a bunch of straightforward html pages and experiments which I want to leave in place. Also there are a few challenges to moving the pivot posts to WordPress that seemed enough for now.

There is not a simple pivotx imported for wordpress, I found Migrating your blog from PivotX to WordPress | filmvanalledag which looked as if it was a near fit, but missed out tags and comments. I’ve also been using disqus comments for my blog but wanted to move to standard ones without losing disqus.

That filmvanalledag post gave me a great start with*&n=10000 I used this to download the rss feed for all of my posts (>800).

I decided that the RSS import would lose all my tags and comments so went for another approach. I have a bit of experience with kludging together a standard WordPress import from other things. This is probably of little interest to anyone but myself, but briefly I use SuperCard to creat a simple pseudo database of the rss add in the missing keywords by downloading them directly from the database and then manipulate it into a wordpress friendly format, for example getting the tag list like this:


Directly from the database and turning it into:

<category domain="post_tag" nicename="glowscotland"><![CDATA[glowscotland]]></category>
<category domain="post_tag" nicename="glowscot"><![CDATA[glowscot]]></category>
<category domain="post_tag" nicename="blogging"><![CDATA[blogging]]></category>
<category domain="post_tag" nicename="wordpress"><![CDATA[wordpress]]></category>
<category domain="category" nicename="wwwd"><![CDATA[wwwd]]></category>
<category domain="category" nicename="jj"><![CDATA[jj]]></category>

For each post.

I tested the import of my export on a local version of wordpress and also worked out some htaccess stuff.
My old blog links were like this: and wordpress expects this

It took me a fair bit of googling and testing to get something that worked, although not quite correctly, once I turned on pretty links goes to, not removing the ?e=2464, ?p=2464 works properly. Once tested I created a new WordPress on the site, at /blag, set it up, did a little more testing and have just moved it to /blog after changing the urls in the General Settings Screen.

The other main problem was that I was using disqus for my comments on the old blog and being a packrat I did not want to leave them behind. So I’ve added a bit of logic to this new blog where older posts will display the disqus form and any comments but going forward I’ll use the standard WordPress ones. I can’t see any way to import the old disqus comments into WordPress at this point.

There are more things to fix, and I’ll try to pick these up as I go along. After that I’ll be looking to play around with some wordpress plugins and the like.

What is Openness?

Over on week 1 of P2PU Why Open? course the question is:

What do you think “openness” is? Focusing on your own field or context (if you wish), describe what it means to do work openly, or to make one’s activity or artifacts open. Alternatively, you could talk about what you think “openness” means generally, what sort of definition might fit all open activities or works.

What follows are some rather scrappy notes on my first reactions to the question. I’ve blogged a bit about openness before too.

Blogging in the Open

My own field is education, I am a primary teacher now involved in staff development and ict support. To work openly means to me several things:

  • To be able to publish my thoughts and idea without permission (limited by social norms, employment and the law).
  • To put things in my own space not to be tied down to a silo or format.
  • To be able to sink or swim in the internet ocean, the majority of my posts here sink, a few tweets and then down to the Davy Jones locker of archived posts. But that allows me to write what I like, no one is paying for it.
  • For pupils as well as teachers and everyone else there can be amazing connections made by being out in the open online. Here is a video I made for Alan Levine’s True Stories of Open Sharing to give examples of the benefits of working in the open, where I describe one example of goodness that came to my class of 10 year olds by working in the open.

Apologies for the quality of the video, made in too much of a hurry.

Playing in the Open

To play openly is just as important to me, I learn about my field of interest in education, the digital, by playing. Playing in the open give me the same gains as listed above but emphasises:

  • The ability to play freely with others, sharing ideas, copying, riffing and remixing.
  • Talking across domains, I am learning/playing with psychologists, artists, teachers without worrying too much about labels. Being in the open leads to serendipitous connections that would not be made if we kept our activity or artefacts in walled gardens, or our own hard drives.

I’ve a rather long post lurking in my mind about the learning I’ve being doing around GIF FIGHT!!. On the surface a rather silly game of creating gifs played among people who should know better. It turns out I’ve learned more about manipulating graphics than in numerous unfinished tutorials. In addition I’ve learned a lot about learning through play, interacting online and how I learn myself.

Emblem 1.4

More Seriously

Open education can promote knowledge transfer while at the same time enhancing quality and sustainability, supporting social inclusion, and creating a culture of inter-institutional collaboration and sharing.  In addition, open education can expand access to education, widen participation, create new opportunities for the next generation of teachers and learners and prepare them to become fully engaged digital citizens.

from: Scottish Open Education Declaration seems about right to me.

Recently I’ve been challenged a bit about the idea of open being the preferred mode of working online, I am hoping that if I stick to the Why Open? course I’ll be able t ogive less anecdotal answers.

Blog Migration Notes: Users

The Whole Gang, 50 Days old by Dean Searle Attribution-NonCommercial-NoDerivs License

There is some background to this project in a previous post: Glow Blogs Summer 2014.

Before the migration of the glow portal Education Scotland suggested that schools did some pruning and tidying of their glow groups to make migration easier (less data) and so that users had less to sort through and sort out on the other end.

As the date for migration of blog gets nearer a few folk have been asking me about what is going happen to their blogs, if there is anything that they should be doing and what will change. This post will try and address some of the questions.

You should not need to do any pruning and tidying of your blogs. The intention is to migrate everything as is to the new system. I was always surprised to be asked about tidying up and deleting old posts from school and class blogs. for me a blog is for life, it is a positive that I could dive back into the archive and see some of what I was doing years ago.

The blog only knows about users that have visited already

One of the biggest changes will be the decoupling of the blogs from the old glow groups. In the current, old, system the users and permissions of those users are set inside the glow group that the blog was created in. Those groups will go away. After migration you blog will not be able to refer to the old sharepoint group to find out who has permission do do things (view, post, carry out admin tasks) the only users it will know about are ones who have already visited the blog when logged into glow.

For example:

  • Teacher A has set up a blog in the old glow for herself and 2 colleagues, Teacher B and Teacher C (not their real names) to share links about their subject with pupils.
  • Teacher A is the blog admin and The other two are contributors.
  • The blog is a public blog so anyone in the world can view it.
  • Teacher B has already added a couple of links by creating posts on the blog.
  • Teacher C has yet to log on to the blog.
  • After the switch over to the new authentication system and the blog migration Teacher A and B can log on, Teacher A is still an admin and Teacher B can log on and create posts.
  • When Teacher C tries to log on there is no entry in the WordPress database for him as having a role in this blog. If he has never used any glow blog he will not be in the database at all. Teacher C will not be able to log on or create posts.
  • At that point Teacher A will be able to log on to the dashboard, go to the users screen and add Teacher C as a contributor.

To avoid this scenario Teacher C would need to log on to the blog before the migration.

Japenese Spaniel by Muzik Hounds Attribution-NonCommercial License

New User Management

Going forward on the blog service the user management will be in the WordPress dashboard not in glow groups. This will develop over time. We are trying to have a system that is not dependent on other parts of the system, In the old glow the blogs were very much hooked into sharepoint in a way that made it difficult to upgrade. We ended up using a very out of date version of WordPress. In the future we should be able to keep the blog system up to date.

Unfortunately the standard WordPress user management is not really suitable for use in glow. This is based round email messages to add users to a particular blog. If for example 200 second years add their teachers to their e-portfolio blogs to allow them to see them each teacher added would get an email from each blog and have to click the link in the email to finish the process. It also requires you to add one user at a time. This is not sutiable and will not happen.

For the first stage of the new blog service the developers will add functionality so that if I add a user to my blog with a particular role they will be added but the email message will not be sent and the user will not need to confirm the addition. The interface will be changes so that I can add a list of glow usernames rather than just one at a time.

The main problem in this scenario will be finding out usernames. This is being dealt with by another team in the glow program. It may not be ready in time for the switchover. In that case it may be necessary to gather usernames is a manual way (get them sent in an email, find them in O365 or even get them written down on a bit of paper. Then make a list in a document to paste into the blog admin screen, save the doc).

It is planned that the class set functionality that was present in the old glow groups will be redeveloped. The second stage for the blogs will be that the class sets service will be an area where teachers can search for a class and them copy a list of usernames to paste into the user management screen in the dashboard of their blog.

The third development will be to bring the class set functionality into the user management screen directly. This will happen in the third phase of the blog migration and upgrade.

As the functionality is developed we will be able to make user guides for this process.

Please get in touch if you have any questions about the glow blog migration.

Life in Links 2014-08-11

Chain black&white by yostD7000
Attribution-NonCommercial-ShareAlike License

A few things from my Pinboard bookmarks from the last week.

TeachMeet SLF 2014

Wednesday 24th September 2014 from 5 for 5.30pm start – 8.00pm

At the Scottish Qualifications Authority (SQA)

Third Floor, The Optima Building, 58 Robertson Street, Glasgow, G2 8DQ

Signup to talk or lurk at TeachMeet / TeachMeet SLF 2014

Looking forward to going to this. Edutalk is going to be one of the sponsors and we will be streaming audio live.

#tmslf14 looks like being the hashtag.

Grumble (age related?)

I was as usual a bit disturbed by the state of the TeachMeet Wiki front page when adding the logo, hence the slight snark in the graphic above. There have been a few attempts to improve the organisations of the wiki before and none, as far as I know, have had much success. Personally I think a front page of text links, dates, times locations and short descriptions would be nicer. Logos etc could go onto the signup page.

I wonder if the current exuberant displays of giant graphics and information could be off putting to newcomers who are thinking signing up?

Glow Blogs Summer 2014

One of the biggest frustrations working on the glow projects is the limits it places on open communication. I was expecting to be able to blog ideas and thoughts as I progressed through the blog migration. It turns out that this might have lead to procurement and legal difficulties.

A Very Excited Puppy by edanley Attribution License

I am delighted and excited that the blog migration project, which is what I’ve been spending the majority of my time on since January, is at a point where we can discuss our plans.

After a lot of work and investigation it has been decided that the best way to go forward with the blogging service is to continue to use WordPress for Glow Blogs. This might have seemed to be a no brainer, but we had to be sure we would not run into possible procurement challenges by assuming WordPress was the only solution.

How We Got Here and Why It Is Taking So Long

Current blogs hooked into sharepoint, use a very old version of WordPress.
There has been a lot of investigation on how the old blogs worked and were knitted into the sharepoint system of ‘Old Glow’ we now have a good understanding of the technical architecture and best way to move forward.

Things That Need to Be Done

Authentication, Blog Creation, User Management.

The new blogs will need to authenticate to the new RM Unify project. Blog creation is current done in the ‘Old Glow’ sharepoint portal. The new service will need to include an independent system for creating blogs. Likewise the old system used the old portal for user management, a new system will have to be created inside the WordPress platform. We anticipate that there are many opportunities for improving the blog creating and user management in the new system. We will also, hopefully avoid the problem of being tightly coupled to another service which should make future development of the blogs less problematic than it has been in the past.

We Have a Plan

We now have a full-time WordPress developer in the glow team who will have the role of overseeing the technical aspects of the blog project. We have procured the services of Code for The People to manage the migration process and upgrade to a more recent version of WordPress.

  1. Move: existing 2.9.2 blogs to new home, development of new authentication, blog creation and User management. This will reduce risk of any problems that might arise from trying to move directly to a new and up to date WordPress setup.
  2. Upgrade: to more recent version of WP We will, again to reduce risk, upgrade in stages. This should not be visible to end users.
  3. Improve: Phase Three…

The benefits of the new blog system should become apparent quite quickly.
Firstly here are many features of more recent versions of WordPress that will improve the system without any development. A better editor, better mobile experience, better handling of media.

Going forward into stage three, there should be an opportunity for a wider range of themes and plugins and the development of a system for requesting in installation of these.

We should be able to make pupil profile improvements. For example the creation of the profile blogs current take many many steps. It takes me about an hour to take a class through creation. We should be able to improve that, and perhaps other types of blogs site, by providing a wizard that is build into the system. We have the chance to develop a better system for producing the p7 & S3 profiles.

Aggregation, this could make the following and commenting on pupil profiles by staff much more efficient. Teachers could potentially have a page where they would see any new activity by any group of pupils they interact with.

There Is Always Some Risk

There are few possible risks which may result in extending the planned short freeze on the platform. If these push our migration date past Oct 3 the current blogs will not be accessible. Our current estimates are that we will meet our deadlines.

  • There is a potential period of blogs having a procedural content freeze or outage for a few days in the Summer. Possibly another content freeze in September or October. We will do our best to keep users informed about this. We have not yet identified length of these periods.
  • Things go wrong, exceptionally big project
  • I’d guess this is one of the biggest WordPress setups in the world, we are moving from version 2.9.2 to 3.9 or later this is a challenge.
  • There will be a great deal of testing of all stages in the migration, we will be starting the testing early to maximise benefit while minimising risk to delivery dates.
  • There are a lot of different aspects of Procurement that are hard to fathom before the exercise is complete. It is difficult to estimate times we have still to finalise the procurement of the hosting for the blogging system.

Class Sets, will not be ready for switchover time. RM unify does not currently have a way for the blogs to gather class and curricular groups to help with adding users to a blog and assigning them roles. We will develop interim solutions to assigning roles to multiple users (probably pasting in a list of usernames). This will hopefully be short term and be replaced by a more robust solution when class sets information is available in glow generally.

I managed to avoid ‘blog with two tails’ as the title of this post, but could not the puppy pictures;-)

Although this feels at times as if it is a long drawn out process, it has been (and is being) made enjoyable for me by working with (or mainly watching the the work carried out by) a great team of folk on the blog project. The first time I’ve worked with a Project Manager, Business Analyst, Technical Architect, Tester or Developers in a formal setting has been one of the best things in my secondment so far.

FutureLearn CreativeCoding


FutureLearn is a massive open online course (MOOC) platform founded in December 2012 as a company majority owned by the UK’s Open University. It is the first UK-led massive open online course platform, and as of October 2013 had 26 University partners and – unlike similar platforms – includes three non-university partners: the British Museum, the British Council and the British Library.

from: FutureLearn – Wikipedia, the free encyclopedia

I’ve signed up for and started the Creative Coding course at FutureLearn. It looked like an interesting course and I was interested to try out the FutureLearn platform.

The Platform

Unlike some MOOCs I’ve dipped my toe into FutureLearn is based on its own platform. FutureLearn is in beta and they are developing new features and evolving the offer. They have started with the smallest feature set that they though they could.

The webpages are extremely clear and it is easy to follow the course.

The course I am doing is split into 6 weeks.

Futurelearn Creativecoding Overview

The week view gives an overview of a number of tasks to be carried out in the week.

Futurelearn Weekview

The colour of the wee square letting you know if you have completed the ‘task’.

Futurelearn Tasks Done

Each task is laid out rather like a blog post, with content at the top and a place for participants to comment. On a wide screen computer the comments appear at the side, but on my 1280 macbook they are below.

Futurelearn Post

There are already 100s of comments on most of the week one tasks.

The course encourages you to post your results to Flickr: The Monash Creative Coding Pool and to use #FLcreativecoding. The links to images can then be added in the comments. Folk are also posting images to other places, tumblr, dropbox etc.

Learning Processing

There is a fair bit of interaction going on in the comments and quite a lot of folk helping others. I’ll be interested in seeing any signs of community growing in such a large class.

The course has been very easy to work through so far as far as organization goes. Each task is clearly set out, the videos have be of good quality and very clear. As I have been doing most of this on my commute I’ve had a few problems when the Scot Rail internet connection is poor (Falkirk!). The system works very well on a technical level. If fells like reading and responding to a series of blog posts. I am sure you could do something similar on a smaller scale with a blog. I’ll be interested to see what new features FutureLearn add as time goes on.

This has been quite good fun so far. A fairly gentle introduction to the application and some basic principles in the first week. The videos and handouts have been clear. Some of the folk taking part are obviously experienced coders and it might be a bit daunting to see some of their work others seem to be taking their very first steps in programming/coding. I’ve had enough experience with baby steps to keep me going this week. I expect I might hit a trig wall at some point I had a quick look at the khan videos suggested for getting up to speed with trig but there looked like too many to watch in a reasonable time.

The Course suggests that you need at least three hours a week to keep up, I think that would be a pretty bare minimum I am guessing I have spent five or more hours and could have done with a few more to really get the week one lessons in my head.

The course is certainly not one you could drop in and out of, it seems to be pretty linear and even in the first week you would find it hard to skip many tasks unless you already had some knowledge.

So far it has got me more interested in processing that I have been and I hope I can find the time to keep up for the next few weeks.