Hennie and I, on our recent trip to the UK and Europe, were taken by Michael to meet with Dr Mike Rodd , Director of the learned society & external relations for the British Computer Society (BCS), and with Paul Adams, chairman of the open Source Specialist Group of the BCS.
The BCS has approx. 70,000 members from across ICT industry in UK (incl. universities). They work with accredited international universities, including University of Johannesburg and University of Cape Town. They also have links with the Computer Society of South Africa.
Some of the problems that scubuntu will address were discussed and included:
- Researchers not knowing about appropriate OSS tools, and the difficulty of selecting the best software
- Researchers’ technical proficiency to install packages and maintain the system
- Integration of packages into a cohesive whole
A further problem identified with the adoption of OSS in universities in the UK is that their procurement and IT policies make it difficult to use software without a support contract. This is more of a problem in the newer universities that focus more on technology, while older research-focused universities struggle less with this.
There was a discussion about the target audience of scubuntu, and the most appropriate distribution media for each group. In the UK, connectivity is not an issue for research institutions, so a network0based installer is appropriate. In Africa, connectivity is problematic, so a CD-based installer is better.
An important issue was raised around branding and ownership of the project. For the project to be successful as a community-driven initiative, it shouldn’t be seen as a CSIR/Meraka/DST owned project. This is completely in alignment with my goals for the project - I see it as a global, open initiaive, not as being owned by Meraka. It was suggested that a statement stating (for Meraka-paid contributors) that the “CSIR supports my time on this project and acts as a beta test site” would be appropriate.
Paul Adams offered to speak to his contacts at Canonical, to request a formal statement of unofficial support for the project (e.g. a posting on the SABDFL’s weblog). He also offered to help us in finding domain specialists with IT knowledge who can contribute to the project.
A discussion about possible a exchange programme for the project led to the suggestion that we target postdocs for such a programme. The feeling was that in the UK postdocs, who tend to not yet have full time employment, would have fewer immediate demands on their time, and would be more amenable to such an exchange.
Developer sprints were suggested as the most appropriate mechanism for getting developers together and for solving specific technical challenges on scubuntu. Paul Adams has had success in the past in securing financial support from the NLNET foundation in the Netherlands for such developer sprints. Attendance of the six-monthly UDS was identified as critical for the scubuntu project. The next UDS takes place in Decmeber.
Paul Adams is willing, via his employer (Sirius Corporation) to partner with us and lead the application for EU FP7 funding.
There was a suggestion that we contact Tony Roberts, who is involved with Computer Aid in distributing refurbished machines to schools in Africa (not in SA). There may be an opportunity to include scubuntu on their machines.
Possible collaborators that were identified:
- OSSWatch at the University of Oxford
- University of Dundee, who are working on a project based on Ubuntu for home automation for people with disabilities
- University of Southampton who are involved in open access publication, and who may have an interest in open source tools for research
- University of Durham
- University of Lincoln
The OSS specialist group meets monthly, and can be used to spread the word about the project. There was also an invitation to present on the project at a future meeting, and to host a workshop to discuss some specific problem/challenge. In addition, the BCS is willing to send out a one-pager information document to all their members on the project.