Open Educational Resources (OER) Hackday
A two day event hacking content, systems and services for open
educational resources
Manchester Conference Centre,
Weston Building,
Sackville Street,
Manchester,
M1 3BB,
UK,
Thursday, 31st of March and Friday 1st April 2011.
Main Page | Programme | How to book | Venue | Delegate List | Evaluation Form
We are inviting developers and 'users' to work together in a unique event where teams of people will work with OER resources, systems and services. Events like these are sometimes called 'Hack Days'. We will be encouraging developers to talk about the systems and resources they have created and how they can be discovered, disaggregated, presented, remixed and tracked. We hope these teams will come up with some imaginative and innovative ideas. The event will culminate in a series of presentations from the teams about the work they have carried out.
Tag for event
#oerhack and #devcsi
Mailing list to discuss ideas before, during and after the event
You may also like to discuss what you might be doing at the
event and even joining into teams by subscribing to the: oer-discuss@jiscmail.ac.uk
(https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=OER-DISCUSS)
list
which
has
recently
been
started.
Google Group
We have also created a google group which you can join:
https://groups.google.com/forum/?hl=en#!forum/oer-hack
and start discussing your ideas
Wiki
We have now created a wiki to start putting ideas together for the
event: http://wiki.cetis.ac.uk/OER_Hack_Days
, please use this to put up your ideas for the event.
Twitter
You will be able to follow announcements about the event via twitter (as well as feeds from blogs and websites etc) by searching for the above tag. If you are new to twitter, please visit, http://www.twitter.com and create an account for yourself. We will be using technologies like this frequently, before, during and after the event.
If you require a twitter client (software to keep up to date with the latest twitters), several can be found at http://www.twitstat.com/twitterclientusers.html.