Open Source Deployment: Lessons from Schools


Published on

Published in: Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Unconference.
  • No licence fees Unrestrictive licences Doing more Control of data Empowering end users - bottom up
  • Whist there are going to be relatively few teachers or students who will have the technical expertise or the inclination to read through the source code, the fact that the opportunity's there might well be important for a few sixth form computing students, and perhaps the members of a programming club lower down the school. Being able to get to the source code potentially gives students a far better understanding of how software works and of how it gets written: something which my own Year 6 pupils got quite excited about. More importantly, access to the source code allows school techies to tailor the software to the specific needs of the school; it's this adaptability of open source software which is its unique, er, selling point. For me, this is at the core of why open source software matters for schools.
  • This is a real benefit for schools. Being able to give students CD-ROMs or memory sticks with copies of all the software used in schools is tremendously liberating - no longer does a teacher need to worry about home computers not having particular programs, having the wrong version, or having pirated copies. Whilst not a complete solution, this also goes a long way to addressing the digital divide. The link between children's informal use of technology at home and formal use inside the school curriculum also becomes a closer, stronger one.
  • Open source software is often developed though a community working together on a project, and it's great when schools that are using open source start participating in that community. A lot of open source programs now have a modular structure, so it's relatively easy for programmers to slot in additional functionality. Sharing these with the other users of a program provides just one way of working in partnership with a worldwide community; other ways of contributing to a project include helping with documentation, spotting or fixing bugs, helping with interface design or suggesting features.
  • Open Source Deployment: Lessons from Schools

    1. 1. Open Source Deployment Lessons from schools <ul><li>Miles Berry </li></ul><ul><li>Open Source Schools </li></ul>
    2. 2. Open Source Schools cc-by-nc-sa MrUsh
    3. 3. CC by-nc Socceraholic Free to run the program
    4. 4. CC by-sa The Master Shake Signal Free to study how the program works
    5. 5. CC by-nc-sa Sarah Parrott Free to redistribute the program
    6. 6. CC by-nc Maggie T Free to improve the program
    7. 7. Use in Schools
    8. 8. Infrastructure
    9. 9. Web based applications
    10. 12. Open Source and Windows
    11. 15. Open Source Operating Systems
    12. 16. Thin Clients
    13. 18. Portable Kit
    14. 19. Lessons Learnt
    15. 20. cc-by-nc Cambodia Trust Participate in the Community
    16. 21. cc-by-nc-sa Grant Mitchell Empower your techies
    17. 22. cc-by-nc-sa Vermin Inc Reliability and Innovation
    18. 23. CC by-nc-sa fatboyke (luc) Freedom and Control
    19. 24. cc-by-nc-sa Adam Mulligan Make the savings visible
    20. 25. cc-by-nc-sa thomas.merton Sustainability
    21. 26. cc-by ansik Start small then scale up
    22. 27. Being Open CC by-nc-nd karenwithak
    23. 28. Some of the Barriers <ul><li>Too much money! </li></ul><ul><li>Managed Services </li></ul><ul><li>Risk aversion </li></ul><ul><li>Perception </li></ul><ul><li>Network managers </li></ul><ul><li>Compatibility </li></ul>
    24. 29. Contact details <ul><li> </li></ul><ul><li>@mberry </li></ul><ul><li>[email_address] </li></ul>