checklist
[http://flosscom.net/templates/xplike.plesk.blue.2/images/logo.jpg]
FLOSS / Open Source like learning checklist
Let’s start here with the basics and let us provide a brief overview on the key characteristics of learning in FLOSS / Open Source. Just to make sure that we know what we are talking about.
All of the characteristics below are taken from the information that is provided at the [http://wiki.ubuntu.com/flosscom#head-4a6a0140fa1aff2e64ad25230456974b1bb7d210 set of questions] and the various documents at the [http://www.flosscom.net FLOSSCom website].
Level |
Characteristics |
Comments |
Link to further information |
||
Fundamentals |
Freedom to access information from the commons |
For a better understanding about the fundamentals please see also Tim O'Reilly's interview at the link section |
[http://www.stevehargadon.com/2007/05/tim-oreilly-on-web-20-and-education.html Tim O'Reilly's interview] |
||
|
Freedom to analyse and edit the information |
|
|
||
|
Freedom to co-operate |
|
|
||
|
Freedom to synthesis new information and contribute it to the commons |
Emphasises that learning is about interacting with people and emotional intelligence as much as cognitive development |
|
||
|
|
|
|
||
Learning Environment |
|
|
|
||
|
Not one, but various spaces |
|
|
||
|
Relatively simple tools and structures |
|
|
||
|
Open and transparent |
Regarding information and communication flow |
|
||
|
User input based |
Every one can contribute, though some limitations on code |
|
||
|
Voluntary based |
Though a software might be backed through company funding / HR |
|
||
|
|
|
|
||
Tools |
|
|
|
||
|
Revision control system |
|
|
||
|
Mailing lists |
Developer focus |
|
||
|
Forums |
Targets the community at large |
|
||
|
Knowledge Base |
|
|
||
|
FAQs |
|
|
||
|
Wikis |
|
|
||
|
Blogs |
|
|
||
|
Chats |
|
|
||
|
Demos |
|
|
||
|
|
|
|
||
Learning Materials & Content |
|
|
|
||
|
Code at repositories |
|
|
||
|
Manuals |
|
|
||
|
Guides |
|
|
||
|
Demos |
|
|
||
|
FAQs |
|
|
||
|
Use cases |
|
|
||
|
Forum posts |
|
|
||
|
Mailing list archive |
|
|
||
|
Blogs |
|
|
||
|
News |
|
|
||
|
|
|
|
||
Support |
|
|
|
||
|
Community based / peers |
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
Roles |
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
Types of Learning |
|
|
|
||
|
Learner |
|
|
||
|
Support provider |
|
|
||
|
Content creator |
|
|
||
|
Peer |
|
|
||
|
Mentor |
|
|
||
|
|
|
|
||
|
Types of Learning |
|
|
||
|
Self-studying |
|
|
||
|
Collaborative learning |
Interacting with others |
|
||
|
Problem / practice based learning |
Learning through solving real problems, working on real cases |
|
||
|
Experiential learning |
E.g. the try and error method |
|
||
|
Re-experience |
Learning through re-experience what others experienced |
|
||
|
|
|
|
||
Learning Activities |
|
|
|
||
|
Fix bugs |
|
|
||
|
Other self-study |
|
|
||
|
Reading source code of programs and patches |
|
|
||
|
Reading other developers' feedback to my patches / bug-reports / bug-fixes |
|
|
||
|
Checking programs' for errors and their causes |
|
|
||
|
Reading books or articles on programming |
|
|
||
|
Participate in the discussions within the FLOSS / open source communities |
|
|
||
|
Reading bug reports |
|
|
||
|
Participate in workshops or congresses |
|
|
||
|
Learning by participating in training courses |
|
|
||
|
|
|
|
||
Skills acquired |
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
Recognition of acquired skills through |
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
|
|
|
|
||
[wiki:flosscom Back to mainpage]