2014 Annual Seminar
PROGRAMME - WITH LINKS TO PRESENTATIONS AND VIDEO
Scott Wilson, OSSWatch, Oxford University.
Niamh Walker Headon, ITT Dublin : Institute of Technology Tallaght
David Kane, Waterford Institute of Technology
Hugh Murphy and Padraic Stack, NUI Maynooth
Jennifer Collery, University College Dublin
Headlines and Highlights
- Infrastructure (physical and virtual)
- Establish how you get your data out in a format that is compatible with other software and is usable.
- Ask yourself will the software be around in 5 years' time. (Consider the long procurement cycle in HE)
- OS data is public
- How many commits to the software per month
- How many contributions to the code per month
- Avoid lock in
How do you account for OS in the procurement process?
- Agnostic: Don't mention open source or closed source in you specification documents.
- Equal consideration: to all options
- Preferential consideration: state preference will be given to OS solutions.
- Should be open
- Open governance
- Business case: doesn't need to create more bureaucracy.
- In practice are there 'people barriers' to the software's acceptance by users?
- Are staff / users aware of the procurement?
- Are those involved in procurement aware of the staff / user needs and abilities?
- Are they all aware of policy, tools and how OS works?
- Understanding is needed
- Capacity is needed to deliver both of the organisation and the staff / users.
- Cultural alignment needs to be attained as there will be differing levels of readiness for software change.