Archive for the 'Software' Category

The ÆGIS 1st Pan European open accessibility Workshop

To be honest I’m enthusiastic about the potential of the European ÆGIS project which launched last week. I see the blend of open source and accessibility, open accessibility, as having the potential to provide the most appropriate solutions for users of accessibility and assistive technology. So I’ve spent the last few years developing and promoting the concepts of fair access to all and user engagement whenever I get the opportunity. This has brought be into contact with enthusiastically dedicated  people and projects. The scale and scope of ÆGIS gives the impression open accessibility is now coming of age. The strap line of ‘Open Accessibility Everywhere: Groundwork, Infrastructure, Standards’ indicates the wide scope of the project which aims to use open source, open development and open standards to ‘enable people with disabilities, the elderly and anyone else who is disadvantaged when using Internet services, Desktop PC or Mobile phones’. It will do this by providing developers with a framework, architecture and toolkits, whilst also creating end user applications. 4 pilot studies will inform the subsequent development phases.

The Pan-European Workshop completed the launch week activities at Research In Motion’s Slough Offices and shared the proceedings with Raising The Floor an initiative by Gregg Vanderheiden and Jim Fruchterman to bring together all parties working on web accessibility, again using open practices. Greg has been involved in accessibility for many years and in his Introduction, Peter Korn, technical lead on ÆGIS sited Greg as his primary mentor. Peter in turn has been very active in open accessibility, especially the GNOME desktop which is used in Linux (e.g Ubuntu) and Sun’s Solaris. Peter along with Will Walker has taken a key role in orchestrating the  resources of their employer Sun to bear on making GNOME a focus of much open accessibility work, including infrastructure, the Orca screen reader, GOK on screen keyboard and collaboration with the Firefox web browser accessibility team.

In addition to hearing more about ÆGIS, the workshop offered the opportunity to catch up with some of the collaborators from the Ace Centre, OATSoft.org, aIDEAS & Mozilla as well as being something of a ‘tweatup’ for those who follow each other on Twitter, including Henni of Opera, Steve Faulkener and Gez Lemon of TPG and Davis Sloan of the University of Dundee. There was woefully little time to chat and I completely missed David Banes of AbilityNet and David McKay of Inference Labs, Cambridge (Dasher is an alternative text input program). I did finally meet Jutta Treviranus, director of ATRC at University of Toronto. Jutta is the boss of long term open accessibility developer David Bolter (e.g. GOK, dojo, ARIA), and we also heard the news that David is taking a years break from ATRC to work on Mozilla core accessibility with Maroc and Surkov.

Due to my failure to understand the scale of the map I arrived after the start having wondered up and down the batch road. The first few talks by M Gonzalez-Sancho (EU Commision ICT for inclusion, information and media Directorate General) and E Bekiarias (CERTH-HIT) provided high level views of the EU’s inclusion policies and AEGIS (£12.6M funding) as well as feedback from the previous days user forum.

Peter Korn then gave a technical overview with demos of existing applications including old friends such as the accessibility APIs, GOK, Orca+eSpeak, Dasher and Accerciser. In addition Peter showed an as yet unreleased simulator of visual impairments such as macular degeneration.

Dr Bekiarias then presented the AEGIS use cases which appear to present a reasonably representative and useful range. I was pleased to see symbol support in OpenOffice.org along with synthetic voices. As Simon Judge pointed out the desktop had little for AAC and switch users but  there is more on the mobile platform.

After an all too brief lunch, Dr C Galinski (InfoTerm) gave a presentation on structured content standards. This was followed by a very effective talk by Greg on accessibility overall and Raising the Floor. He made the point that what we do determines if ICT is a blessing or a curse to many users. He provided a clear analysis of the ways of providing accessibility (adjust interface, provide alternative interface, select alternative or download new interface on demand) and asserted that the accessibility API’s are the only real chance for an affordable and lasting strategies for flexible interface options (and I agree). He also considered reducing cost to users and the part OSS plays, seeing this as enabling more direct paths for the transfer of research and allowing the public coverage of costs other than licences. he also suggested we might like to consider free public access (cf public/private schools) and the need to fund more than research - e.g hardening, awareness, support.

Before the panel discussion Peter announced the Open Accessibility Everywhere Group. The desire to bring together all interested parties including developers, researchers and users and so facilitate exchange of ideas it echos the original motivations that underly Oatsoft.org and later Project:Possibility. While Oatsoft’s funding was only for an initial evaluation phase we can hope that OAEG will succesfully fill this important community role and so help us push the open accessibility envelope. There is an overlap here with Raising the floor that will need to be worked out, though AEGIS adds desktop and mobile accessibility to RtF’s focus on web accessibility.

I was pleased to see a place for the open accessibility projects I have been personally active in. In addition to key projects such as Mozilla, GNOME and NVDA I saw some potential for those I have been closely involved in as a developer; Simon Judge thought Maavis has something to offer in many use cases, and the straight-street.com open symbol set has much to offer. Jambu may also be useful as a starting point for some work. I’m not sure about PowerTalk as it relies on MS technologies but at least that is now included in the EduApps USB stick collection. Greg again mentioned his interest in OATSoft.org as providing the master list of projects, though the announcement of the OAEG seem to indicate it would be providing similar functionality after all.

So all-in-all a useful workshop but perhaps too many presentations with too wide a scope; I would have liked more networking time. ÆGIS is an exciting project and a serious opportunity for the benefits of open accessibility to be realised by users and developers alike. There is a lot to be done and good management will be need to ensure it delivers, but building on open development gives it a very good foundation for success. I’m looking forward to being involved as well as watching what happens.

I’m greatful to Ross Gardler (OSS Watch manager) for being so supportive of open accessibility and providing me opportunities to make it part of OSS Watch’s portfolio of experience. My first project was AccessApps and we spent Tuesday in a highly constructive consultation with the Maavis project, working out ways forward by embracing open development.

That reminds me I have an article on open accessibility to take though OSS Watch’s thorough quality control process.

Open Development embraced by OMII-UK projects

Towards the end of April I found myself spending  2 enjoyable days in the company of OMII-UK members at the OMII-UK collaboration Workshop along with others involved in e-Research in various capacities.  Steve Brewer,  project manager of the Engage project, invited me to provide OSS Watch input at the event which included Open Source and Open Development as a key theme. This provided an opportunity for me to learn more about e-Research and meet those working in it, whilst also passing on some of our experience in open development to those project team members wanting to better embrace the techniques. Dr Mario Antonioletti, principle consultant at EPCC and long time OGSA-DAI project team member subsequently requested that I facilitate a session which became the following:

How to invigorate your project with open development: Using an OSI approved open source licence on your project artefacts and putting them on a public server is one thing but how do you nurture a lively community that ensures your project continues to develop and becomes self sustaining?  Open development is the lifeblood of successful open source projects but how does it work, what tools and process make is successful? How does it mesh with the project life cycle and at what stage should it be introduced?  This breakout will explore open development and how it can be applied to individual projects. Come along and share questions, suggestions and experiences from your own projects.

This was a deliberate ploy to concentrate everyone’s energy on understanding open development as opposed to open source, as I explained in both this session and another lead by Steve Brewer on ‘Accelerating the deployment and uptake of open source tools in e-Research’. Working for OSS Watch has help me clarify my understanding of a fundamental principle of open source projects. This is something that, having been active  in several open source projects, I rather take for granted, but that is often not immediately apparent to newcomers to the scene.  The Apache Software Foundation say it well in their policy statement of  ‘community over code’, and back in 1992 the IETF’s phrase ‘We believe in: rough consensus and running code’ puts community decision making first. Having worked with active open source projects such as Mozilla and GNOME it’s clear to me that nurturing a vibrant and diverse community is the vital ingredient for success and sustainability. In contrast there is often a focus of attention on licence issues by those new to open source, and while this is a key part of the picture, OSS Watch now also emphasise  ‘open development’ in order to restore balance. This also helps projects more clearly see why fundamentals such as encouraging participation through the use of well tested collaboration tools and having a clear governance model are critical for their long term health.

Accordingly I was keen to steer discussion towards the issues surrounding open development and how to achieve it, as well as providing recommendations and clearly indicating OSS Watch’s desire to work with projects, providing support from our collective experience.

During the 2 days I chatted with members of at least 4 mature e-Research projects, each at an intermediate stage of practising open development; OGSA-DAI, DIASER, ALADDIN and Portal Access Grid. I encouraged all to go a stage further towards fully embracing open development, so it is exciting to hear announcements from 2 of them that clearly indicate that they heeded some of our recommendations.

Damian Brasher’s DIASER was already practising many of the principles and has now followed our recommendation to make early decisions and design notes available as project memory as these were not originally discussed on the public discussion lists. This involved considerable work but the outcome is that anyone can now find this information archived on public list and can more easily evaluate the project.

OGSA-DAI started as a closed community project though it is now released under an open source licence. During the workshop Mario stated his desire for the project to practice open development as I described it.  Thus it was a pleasure to see an article by Mike Jackson in the June 09 edition of National e-Science Centre news stating they are commited to achieving it.

OGSA-DAI: from open source product to open source project

The OGSA-DAI project has been funded by EPSRC for an additional year, until April 2010. This funding will enable us to evolve OGSA-DAI from an open source product into an open source project.

An international community of users and developers has formed around OGSA-DAI, our unique open source product for access to and integration of distributed heterogeneous data resources. This includes projects and institutions in a myriad of fields including medical research, environmental science, geo-sciences, the arts and humanities and business.

Moving to an open source project will provide the community with a focal point for the evolution, development, use and support of OGSA-DAI and its related components, providing a means by which
members can develop and release their components alongside the core product. It will also provide an avenue to ensure the sustainability of their components. Over the next few months we will set in place the
governance and infrastructure of the OGSA-DAI open source project. This will be done in conjunction with key community members, and will draw upon the expertise of our OMII-UK partners in Manchester and
Southampton and in the Globus Alliance. We aim to roll out our open source project site in October.

Our move to an open source project contributes to OMII-UK’s vision to promote software sustainability, and will guarantee that the lifetime of the OGSA-DAI product will exist out with any single institution or
funding stream. In addition, we will continue to develop the product and engage with international standardisation activities:

[snip]

The OGSA-DAI project -which involves both EPCC and the National e-Science Centre- is funded by EPSRC through OMII-UK.

I’d like to congratulate both projects for taking these important steps toward open development and wish them every success. I’m sure the OSS Watch team will be most interested to hear how they progress, I know I am.

OSS Watch provide many articles about open source development including a guide to participating in an open source community and a review of one of the best books on the subject - Producing Open Source Software by Karl Fogel.

OSS Watch at JISC Conference ‘09

The OSS Watch team will be present at the JISC Conference in Edinburgh on 24 March 09. We will be manning a stand and will be delighted to talk with you about any issues related to open source software in HE and FE.

This year the conference organizers are introducing new facilities to assist participants with setting up f2f meetings.  Once registered, check up the Day Planner service. Feel free to use this opportunity to arrange meetings with us on our stand or in the dedicated networking space.

Looking forward to seeing you in Edinburgh.

FOSS Education is not just about skills development

I recently asserted that we should be educating people about how open source is managed, developed and supported. Without this kind of education we limit our ability to capitalise on the opportunities presented by a maturing open source industry. However, this is not the only reason why we should be providing this kind of education.

Jon Hall, Executive Director of Linux International, a man with plenty of experience as a computer science lecturer, recently wrote an article for Linux Pro Magazine with the title “Seeking the next Einstein: Show me the code“.

In this article Jon observes that access to source code is one of the most valuable educational tools there is for programmers (new or old). He reminds us of the efforts of John Lions who annotated a copy of the complete source of Unix. A work which became one of the most sought after books for computer science students, despite licence changes in Unix preventing its legal use for quite some time.  Jon says that “looking at a good programmer’s code is still a great way to learn the craft.” Personally I would go much further than that.

I discovered open source during my undergraduate computer science degree as a mature student in 1995. Being able to examine and use open source libraries throughout my studies led me to the creation of a final year project that won me a first class honors. However,  it was not just reading peoples code that allowed this, it was the hands on support given to me, in return for my own minor contributions, by the people who wrote that code. These people were real programmers, building full scale applications for use in the real world.

I attended less than 20% of the lectures and tutorials on my course, yet I still managed to get that First Class degree. I do not consider myself to be a gifted computer scientist, my educational success was a direct result of the combination of a well structured theoretical degree and solid practical experience outside of the normal teaching process.

My engagement with open source continued through my early research career, it formed an important part of my materials as a computer science lecturer and it put food on my table when “between jobs”. Today I spend my time trying to help others understand the benefits of open source and open development.

In his article, Jon acknowledges the educational value of free and open source software, but he goes on to turn this on its head. He goes on to observe that the openness of source code “will help us find the next generation of experts”. In other words, as well as helping us round out skills in our workforce, it also ensures that our staff can identify other experts and thought leaders in any given area of expertise.

It is my opinion that open source and open development as a vital part of skills development, if you are interested in such activities please contact us.

Does it take a disaster to understand the power of open development?

The second keynote at ApacheCon US 2008 was from Shahani Markus Weerawarana, Ph.D. who said she had “witnessed the birth of a new global community rising above the depths of despair “. This keynote described what she had witnessed.

Shahani started with the often quoted  “if I have seen farther than others, it is because I was standing on the shoulders of giants” (Isaac Newton). In the scenario to be described the giants were identified as those people in the global open source communities. The people who work together responsibly in transparent collaboration to achieve common goals in efficient and effective ways.

The common goal that drove the people described in this keynote was to alleviate suffering. The outputs of the comunity efforts Shahani witnessd was Sahana, a free and open source disaster management system. Sahana is a web based collaboration tool that addresses the common coordination problems found during a disaster. These include finding missing people, managing aid, managing volunteers and tracking camps. Sahana is a tool to aid communication and coordination between Government groups, the civil society (NGOs) and the victims themselves.

Margaret Mead once said “never doubt that a small group of thoughtful and committed people can change the world”. Sahana is a project that proves just how the open source way of doing things allows those thoughtful and committed people to truly change the world. However, there is a caveat here. We are not talking about the kind of open source that just slaps a licence on some code. We are talking about community led development of open source code, or as many call it, open development.

The Horrific Start of the Sahana Story

The Indian Ocean Tsunami struck on December 26, 2004. The first wave thundered into Sri Lanka at 8.30, a second wave hit 20 mins later. Two thirds of of the Sri Lankan coastline was affected. In Sri Lanka alone 35,000 people died, 100,000 houses were destroyed, a further 50,000 houses were considerably damaged. In total 5% of the Sri Lankan population were instantly homeless, whilst 500+ million kilos of rubble and waste was dumped on the island.

The result was destruction of unimaginable proportions spread across the whole country. Scenes of horror everywhere. For example, a train on a coastal track was stopped due to flooding in the next village.  Villagers, who were running from the first wave, found the train and climbed onto the roof in the hope of escaping the flood. The second wave hit the train. The train was smashed by the wave. Thousands died instantly.

The response from the rest of the world was amazing. We rose up to help within hours, cash started flooding into aid agencies. In the affected regions local people set up refugee camps, aid collection points and medical camps in frenzied, chaotic attempts to alleviate the suffering. Within days foreign aid workers and aid was arriving.

In Sri Lanka a small group of IT gurus stayed behind their computer screens. They suspected they could do more with their keyboards than they could with their shovels. Initial communications with organisations claiming to have disaster management systems turned up blank in terms of suitability for a disaster of this scale. The IT guru’s immediately started communicating the scale of the problem to the open source communities they were a part of. I distinctly remember the despair in those early blog reactions from people who’d seen the affects of the Tsunami first hand and the chaos that followed.

This growing band of IT specialists knew that they could build software to help coordinate the relief efforts. They set to it in the only way they knew how - they created an open development community. It is true that the majority of early work came from Sri Lanka itself, but critical support was forthcoming from other significant players around the world.

At this very early stage, only hours after the Tsunami hit, nobody knew what they needed to build, they just knew they could build something.

The Birth of Sahana

On Dec 29th Sahana (a Sri Lankan word for relief) was born. A call to the Sri Lankan prime minister, with a single question, gave the IT folk the direction they needed. The question was “what is the greatest need right now?”, an answer came immediately - “a missing persons registry,” something to help unite people separated in the evacuation efforts and to help rescue workers identify the dead.

The IT gurus got to work.

Development efforts were frantic. Contributions came in from around the world, there were more than 80 people active on the project. Work continued around the clock and the first useful release was made in about seven days. After that major releases were being made almost daily.

It was quickly realised that Sahana had mobilised enough effort to go beyond the missing person registry. People out in the field had reported that there were refugee camps that had more equipment, food and medical supplies than they needed, whilst other camps needed more supplies. As only true open development allows, individual effort was immediately directed (by the individuals themselves) to areas in which they could make the most impact. Development teams listened to the needs of the users, which were relayed by people on the ground, and simply got on with providing solutions.

Sahana Phase II

Sahana today has been completely rebuilt to provide a more maintainable architecture. Today it has an impressive list of features and continues to receive contributions from across the world. It has been deployed in China, Peru, New York, Indonesia, Philippines, Pakistan, Myanmar and Sri Lanka. Ohloh estimates $4.3M of effort has gone into writing the Sahana application, what Ohloh cannot do is estimate the impact it has had in disaster situations across the world.

The efforts of the Sahana team also spawned a concept and community founded by a humanitarian consultant, Paul Currion, and the Sahana project lead, Chamindra de Silva, based on the more generic ideals of Humanitarian-FOSS.

All this happened because people just wanted to help. The success of Sahana is a result of the fact that the open development model, when applied correctly,  just works. I personally believe that Sahana would not have been possible in the time frames and budgetary restrictions of the real world, if a closed model with tight management structures had been employed. Certainly, the lack of any pre-existing disaster management software would seem to support this.

What was needed was the arrival of just the right leadership and just the right motivation for those willing to help realise the vision (yes, open development is all about strong leadership).

It would appear that the Sri Lankan government also agrees that open source is the way forward. They have seen, first hand, the power of open development. Shahani reported in her keynote that the Sri Lankan government is now working hard to further benefit from the lessons learnt in the Sahana project. In particular the government is examining its procurement policies.

The people of Sri Lanka get it too. The University of Moratuwa had the highest number of successful students in the Google Summer of Code this year, pretty impressive for a country with about a third of the population of the UK. I had the honour of meeting some of these students as a GSoC administrator for The Apache Software Foundation. Let me tell you, these are impressive people.

Does it Take a Disaster?

Does it really take a disaster of the scale of the 2004 Indian Ocean Tsunami to communicate the power of open development to the rest of the world. Certainly, hard facts don’t seem to count a great deal.

A video of the keynote will be available from Linux Pro Magazines archives (at the time of writing the archives were not yet available).