Archive for the 'Community' Category

Standard alchemy

One of the questions that comes up over and over again when we talk to software authors about licence choice is: “what is each type of licence especially good for?” Personally, when discussing permissive licences I tend to point to the imperative of pushing an open data standard as a prototypical use case. Luckily for me, computer graphics industry giants (and competitors) Lucasfilm and Sony Pictures Imageworks have just released v1.0 of their 3d scene format Alembic to prove the point.

Anyone who has dabbled in 3d computer graphics, perhaps using the FOSS modeller and renderer Blender, will have noticed just how many competing object and scene description formats there are out there. While this is a minor inconvenience for amateurs like me, it becomes a massive and expensive problem for visual effects production houses and their clients. Complex animated objects and scenes created in one application have to be laboriously exported frame by frame and reconstructed in the target application, often requiring duplicated effort to complete the import. Alembic avoids this by allowing the compression and exportation and importation of entire complex animated sequences.

So for CG professionals there is a clear need for something like Alembic (the name is taken from the piece of chemistry glassware which distills products and delivers them to another container). However for the creators of the individual software packages the idea of a simple interchange format is not a high priority; after all, why should they make it easier for clients to use another company’s software? It’s natural, therefore, that it is the clients themselves who have produced the standard and software which ’scratches this itch’. Indeed there’s a precedent in the same industry. Back in 2003 Industrial Light and Magic release OpenEXR, a data standard and implementing software that allowed the interchange of so-called ‘HDR’ images (images with a greater range of luminance than standard image formats can store). In eight years OpenEXR has become a widely-used standard. With any luck, Alembic will follow in its footsteps.

“Recipe for Rip-Offs”

Here in the UK the Public Administration Select Committee has been looking into the poor record government has in procuring IT systems. The title of their report “Government and IT- “A Recipe For Rip-Offs”: Time For A New Approach“ serves as a neat summary of the content. Stating the problem, the report says

The UK has been described as “a world leader in ineffective IT schemes for government“. There have been a number of high cost IT initiatives which have run late, under-performed or failed over the last 20 years including: the Child Support Agency’s IT system, the IT system that would have underpinned the National ID Card scheme, the Defence Information Infrastructure Programme, the implementation of the Single Payments Scheme by the Rural Payments Agency, and the National Offender Management System (C-Nomis).

The main problem, the report says, is that the Government does not have the internal skills to specify and procure IT systems. As a result they tend to rely on large external contractors to manage the process of developing IT systems (and to subcontract to smaller businesses where necessary) . Naturally this involves handing over very large amounts of both cash and power to the ‘head’ contractors, and it is this complete externalisation of the ‘IT customer’ function that the report points to as the key failing in previous large government IT procurements. The answer, therefore, is to get better IT management skills within departments and take on the management of the smaller subcontractors themselves.

This is not the only failing identified. It seems that Government also tends to ‘gold-plate’ (over-specify) security requirements even on systems that do not require it. The report also criticises the tendency to see IT projects as a distinct kind of problem rather than an exercise in change management like any other. Nevertheless, it is the ‘externalisation’ problem which looms largest in the report’s somewhat gloomy findings, and it is in this context that the issue of open source arises.

Early on the report identifies the creation of ‘a level playing field for open source software’ as one of the approaches to solving the problem of Government IT that had already been suggested. In the recommendations, we find that open source is mentioned in the context of providing an open data platform for Government-held data which could be developed upon by third parties to provide analysis and manipulation applications. While both of these suggestions are sound in themselves, I think it is in the core recommendation that we can see the best opportunity to realise value for the UK taxpayer from open source software and development.

While there are very large scale corporations offering open source solutions, the majority of bidders for Government IT contracts offer closed source solutions, often with the bidder themselves retaining ownership of the IPR in the resultant code and licensing it under very restrictive terms. If the current reforms succeed in getting departments to break down IT procurements into smaller interoperating sections and invite bids for these from smaller, more agile developers, the opportunity for existing successful open source projects to be the bases for Government IT solutions expands. Assuming that the newly-acquired IT experts within departments are able to meaningfully engage with the communities around these projects – both through their hired developers and as users themselves – then huge amounts of value in terms of code, user requirements and expertise which are currently locked into closed, non-functioning projects will be available for the good of the community at large. The projects themselves will learn how to interact with Government clients, and software components of general application will find their way back into the public space to benefit other large-scale users.

All of these benefits, though, depend both on an openness to the use of open source software but also on expertise in managing the relationship with that software’s community. So while I welcome heartily the proposal that Government acquire the IT skills to take a hands-on role in managing their IT procurements, I hope that those IT skills will include expertise in exploiting the unique benefits of joining an open source community.

Open source innovation

In June 2010 I chaired the inaugral TransferSummit Conference (report) in Oxford. The byline for that conference was “Open Source, Open Development, Open Innovation”. In September this year we are running TransferSummit again. The tag line this year is “Open Innovation Everywhere.” I’m proud of the conference we have created.

Jay Lyman, Senior Analyst at The 451 Group recently twittered that the “overwhelming message @ Oscon so far is open source now driven mostly by innovation.” This in turn prompted Brian Proffit of IT World wrote:

if you put yourself in the right mindset, this kind of innovation is easier to spot than ever. Open source isn’t “just” the alternative anymore, it’s becoming the mainstream technology in a lot of areas.

When we created TransferSummit the objective was to highlight the fact that open source is open innovation in software. However, unlike most open source related conferences we are not interestedin preaching to the converted. Open source and the innovation it brings is important to everyone and TransferSummit is designed for everyone, no matter their existing level of open source knowledge.

TransferSummit 2011 has the same goal and has an equally impressive range of speakers for you to engage with and share ideas. We have:

  • 2 days’ trainings
  • 2-day conference across three tracks
  • Mobile focus, virtual track
  • Government summit
  • Hands-on learning and break-out sessions
  • Gadget playtime
  • Gala dinner
  • On-site housing
  • Intimate setting, limited to 300 participants

This is the must attend event for 2011, tickets are selling fact so register now.

OSS Watch Open Source Junction 2, Oxford, 5-6 July 2011

This guest post was written by Sam Jordison, who also wrote the live blog at Open Source Junction 2.

Following on from the platform built at Open Source Junction 1, this two day conference at Wolfson College Oxford developed the theme of industry-academia collaboration on open source mobile technologies. The focus this time was on  context-aware mobile technology.

So what is context-aware mobile technology? Over the course of the two days, there arose a number of interesting definitions taking the notion of context beyond the simple idea of location based services and into the lives of end-users, taking into account such things as their emotional state, habits, patterns of social interaction and the way they use their time.

In a talk entitled ‘Context Aware Applications: Industry Landscape And Commercial Opportunities’, Nick Allott, the founder of Nquiring Minds Ltd, said context was ‘all about probabilities’ and relationships, good examples being Amazon’s suggestions that ‘if you like X then you’ll like Y’ or the idea that if your friend installs a security system, you are more likely to trust it. Julian Harty, ‘tester at large at eBay’, in his talk ‘Smartphones In Context’, asked delegates to think in terms of interaction with the outside world. ‘Do you know how many sensors your smartphone has?’ he asked. The answer he said was almost certainly likely to be more than 10; including a light sensor, a sound sensor, a compass, rotation detection, accelerometers, GPS. All of these sensors work with the context in which they are placed – and can be used to create new contexts. Elsewhere, the idea of context was touched on in talks also encompassing business and academic integration, licensing, best practice in running open source projects, financial issues, dealing with huge amounts of data  – and ensuring that  data sources are reliable.

Context, it seems, is a broad issue – but the over-riding theme was the importance of engagement; whether that be with other programmers and contributors on open source projects through mailing lists, or between developers and the wider public. Such engagements have the power to change the world – and the way we see it. More particularly, the aim of the conference was to foster engagement between industry and academic people, to help them understand each other’s interests in context-aware mobile technologies.

One of the main ways this latter aim was encouraged was in show-casing a diverse range of projects and ideas from both industry and academic speakers through a wide range of presentations. Indeed, the very first presentation from Gabriel Hanganu tackled the idea head on. He acknowledged that there are perceived barriers between the worlds of academia and business, especially relating to the different drivers in each sphere. Profit and practical production motivate business. Ideas, research and journal production push academics. But Gabriel pointed out that academics are not as slack when it comes to entrepreneurial thinking as is often supposed -  while business can really profit from academic thinking. There is plenty of common ground – and when it comes to software development, the practices and procedures relating to open source can help bridge gaps. (More on that later.)

Roland Harwood, co-founder of 100% Open built on this idea of the usefulness of partnerships with his talk about open innovation collaboration. He highlighted a large number of examples of successful collaborations, and showed how even traditionally less open companies like Lego have benefited by enabling a broad community to use their code, and unleash their creativity. Mindstorms, thanks to its fan built ideas, has now become Lego’s best selling product.

As well as generating nifty new revenue streams, new technology can also provide a fascinating new insight into the way the world works. Steven Gray from the UCL Centre for Advanced Spatial Analysis gave a fascinating run through his work on a number of game-changing projects, the most famous of which is Tweet-O-Meter, a program that uses geo-location data from Twitter to show when and where people are sending tweets. The data can be aggregated around maps to show interesting things. So, for instance, in London they can trace where there are roadworks and traffic jams because people are tweeting about them. They have also spotted that people tweet a lot on railway lines and at Heathrow airport as they take off and land and that parks are particularly free of activity during winter. They can see cities waking up and sleeping. CNN used the meter during the Japanese tsunami to show how people reacted to the news (since lots of people in Tokyo used their mobiles as landlines were down). They could also see the news spread to San Francisco.

Another clear demonstration of how mobile technology can be used to trace events in the physical world came in the form of the Nature Locator, described by Mike Jones  from The Institute of Learning and Research Technology at the University of Bristol. This emerged from a JISC-funded project that facilitated development of an Android and iOS apps to support citizen science. The app allows members of the public to submit photographic and geo-location evidence of leaf damage by a non-UK-native moth to the Conker Tree Science project – and has generated masses of important and useful scientific data.

The useful practical applications for such technology were clearly demonstrated by Serge Pawlowicz from the Centre of Geospatial Science in the University of Nottingham and his talk on a Particpatory HealthGIS that uses geospatial data and public participation surveys to help in all kinds of health research, for instance, tracing the sources of viruses. ‘It works!’ he said.

Ben Butchart, an experienced software engineer from EDINA (a JISC-funded national academic data centre providing online data services to academic institutions) continued this theme, explaining that the uses of HTML5 caching technology has opened up all kinds of new possibilities for developing useful technologies for geo-dependent projects (such as geology projects) even in isolated locations where signals are unreliable. At the other end of the spectrum, Tim Fernando gave an overview of how useful context-aware technology can be to residents of Oxford, and the success of Mobile Oxford, a campus-wide mobile service providing information on everything from bus times to library book availability to gigs.

Such projects can also be extended to provide useful information to and further engage with the wider public (end-users) by inviting them to contribute to location-based media platforms. So said Mick Lockwood from Salford University who demonstrated this in his talk about Maxamundo. He explained that using OpenStreetMap and a range of open source software, and getting user contributions helped him become ‘able to fulfil a dream’ even if he was just an ‘amateur hobbyist’. He’s now built up a detailed overview of Manchester and its attractions (a great many of which appear to be pubs) and the Maxamundo platform even becomes the subject of a sociological project. This latter project was run by Yuwei Lin, also from Salford University, who gave a fascinating account of the way it worked against open source development methodologies after Mick had finished speaking, explaining that Maxamundo has started to fulfil many of the functions of social networking sites, contextualise city lives, and re-order personal stories on a map.

The conference even explored the imaginary plane as well as showing so much about mapping the real world. Philipp Breuss-Schneeweis described how Wikitude, an augmented reality app that overlays virtual images and information over the real world (as revealed in, for instance, smartphone camera viewers), has the potential to alter the way we interact with, well, everything. Current uses include navigation devices for driving and 3D gaming, but the potential is limited only by the imagination of the huge community that can be harnessed to create new ‘worlds’ to overlay the context provided by the phone.

Elsewhere, one of the most impressive examples of context-aware engagement came from Samuel Carlisle and his colleague Matt Gaffen and their talk about Sukey. Sukey, we were told, exists to keep demonstrators safe and mobile during protests. It was created in 2010 in the aftermath of the occupation of UCL and most particularly in response to the police tactics used during that winter’s student protests, whereby protestors were ‘kettled’ for long periods of time and had their freedom of movement restricted. (The name comes from the nursery song, ‘Polly put the kettle on, Sukey take it off again’.) Sam said that they started putting out maps of protests that started giving them upwards of 60,000 hits in just a few hours – which inspired them to produce a proper app.

Using information crowd-sourced from the app, alongside information in Twitter streams, Sukey attempts to put out the most relevant and useful material surrounding demonstrations. So, for instance, they show where the police are forming kettles, where streets are blocked and also provide compass directions designed to help people on the ground get out of trouble. It’s run by volunteers in their spare time and it’s not for profit, so the use of community engagement was vital in making it work… And work it did; providing helpful information to thousands of protestors, and even acting as a conduit for advice and information from the police themselves. The application also received widespread media coverage and helped inform the wider ongoing debate about police tactics. A clear demonstration of just how quickly and effectively free-at-point-of-use software can change our society.

Many of these projects are already successful and those in their infancy are already demonstrating real potential, but at Open Source Junction 2 there was no shying away from the challenges they face. Speakers made it clear that taking contributions from large numbers of people – whether they be citizen scientists or developers sharing in an open source project – is not always easy. The team behind Sukey, for instance, have to dedicate a lot of energy to combating spam and false information. The Nature Locator has had to deal with a lot of incorrect data. Checks and balances are going to play an increasingly important role, it seems. W3C fellow Dave Raggett, meanwhile, highlighted the fact that ’simplicity is hard’, explaining the need for good communication paths based on trust relationships, an easier way to manage security and logins across a number of platforms than we have at the moment and suggesting, cleverly, that it would be better if users could check the credentials of the website – as well as the website checking them out and for there to be support for pseudonymous identities that reflect the real world. No easy tasks – although we can at least take solace from the knowledge that he and others are working on them.

It was also emphasised that open innovation isn’t a panacea in every case. It can offer a fantastic way to cut costs, save time and maximise the potential of developers. Ross Gardler outlined a number of open source business models that can help you make sure ‘your company doesn’t go bust because it’s spending so much maintaining software’, ensure long term sustainability for projects and ideas, and open up many opportunities for commodotisation. But it was also emphasised that there are all kinds of procedures to follow and tough decisions to make to ensure the smooth running of projects – and that they remain sustainable in the long term. Just how careful projects have to be to follow the correct processes was clearly demonstrated in talks from Sander van der Waal concerning best practice relating to open source projects (emphasising the need to have a good management structure in place, transparent updates and progress reports via mailing lists) and a look into the complications surrounding patents, licences, Intellectual Property Rights and European law from Rowan Wilson.

In spite of such challenges, another clear advantage of open source development became clear over the course of the two days – how much it can help in academic and business collaborations, just as Gabriel had hinted in his opening talk. Camille Baldock from Softwire explained to me that while there is plenty of desire in the business world to tap into the academic knowledge base and expertise, such collaborations remain rare, thanks to perceptions about the different cultures and priorities found in the two ‘tribes’. But, as Gabriel  repeatedly stressed during the day, in software projects, developers can offer an alternative common ground in the form of the clearly defined work practices associated with open development.

Another thing that wasn’t in doubt at the end of the conference was how much participants did have to give each other. The ’speed dating’ session invited delegates to write down three things they could offer a potential partner  – and three things they wanted in return. Ross Gardler got the ball rolling. He offered: a wide network from working in real open source, guidance on sustainable models, and practical experience on making things happen. He said he wanted: real projects before they go to market, innovation companies to work with, and introductions to more useful people. There followed a fast and furious twenty minutes with a huge array of services offered and requested. Offers included, contacts and development from the London Mobile Developer community, an open invite to hackdays – including organising them, a strong network for industrial partners in the telecoms, students and resources, expertise in security, 3D Printing knowledge and (let’s not forget!) another conference in September – TransferSummit, co-organised by OSS Watch. Wants included, ideas and products to sell, the promotion of open source, partners, funding opportunities, opportunities for future consortia.

These connections were further aided by the format of the event, with numerous other such interactive sessions built in. As well as the ‘offers and wants’ session, delegates were invited to ’self pitch’, giving a 45 second overview of their mobile app’s interests and invite feedback. They also took part in a ‘3 minute joint venture’  session in which they were invited to pair up with someone they hadn’t yet talked to and spend three minutes coming up with an idea for a joint venture. (Highlights included a mashup of eBay and location-based sales, using targeted marketing on people walking down the street, and AID – Am I Dying – a mix of a virtual patient project in St George’s with an intelligent clothing company… ). There was also plenty of space for informal conversations over breaks, drinks and dinner saw many start to form those connections.

In short, there were many successful interactions building from the platform established at the first Open Source Junction. Even the fact that the attempt to put geo-location technology into practice on a country walk resulted in all delegates getting soaked in a rain storm and two chased by a bull didn’t dampen spirits. People were exchanging details, forming links throughout the two days and I’m told many are discussing opportunities in more detail now. There was the feeling that a community was forming. Let’s hope it continues to grow and prosper, and watch out for the next OSJ3 planned for November.

OSS Watch and OpenDirective team up to deliver training

A couple of weeks ago I left OSS Watch as manager. However, I promised
that I would still be around and working closely with OSS Watch for
the foreseeable future. Today we are pleased to announce one of the first
collaborations between OSS Watch and our new company OpenDirective.

In September, at TransferSummit (Oxford) and in November at ApacheCon
(Vancouver) Sander van der Waal (OSS Watch), Steve Lee (OpenDirective)
and myself (OpenDirective) will be delivering a new training course
for people looking to either procure or engage with open source
software. The course is based on work done by OSS Watch on a Software
Sustainability Maturity Model (SSMM), a model which can be used to
formally evaluate both open and closed source software with respect to
its sustainability. The model provides a means of estimating the risks
associated with adopting a given solution. It is a tool for resource
planning and risk management when procuring software solutions for
implementation and/or customisation, as well as for reuse in new
software products. It is also useful for project leaders and
developers, as it enables them to identify areas of concern, with
respect to sustainability, within their projects.

The idea for this tool was the product of a workshop run by OSS Watch
in 2008 called “Levelling the playing field: developing a mixed economy for software procurement”. Attendees at the workshop made it
clear that one of the problems they faced when evaluating open source
software was understanding the difference between a truly viable open
source solution and some code that just happened to have been uploaded
to the web. This sentiment was echoed in the findings of the OSS Watch
national survey in 2008 and 2010. In late 2010 we published the
first outline of our Software Sustainability Maturity Model.

These training days will deliver the first complete version of the
model
, however we don’t intend to stop there. OSS Watch are currently
working on extensions to the model that will help guide Total Cost of
Ownership calculations while OpenDirective continue to refine the
model through practical engagement with customers.

It is through collaborations such as these that OSS Watch and
OpenDirective seek to meet the needs of the academic sector in terms
of both the use of and production of open source software. OSS Watch
remain free at the point of use and look forward to working with you
and your organisation.

Open Source Junction 2 ready to go

Open Source Junction 2 is just a few days away and I’m pleased to say that the event is now fully booked. We have a great mix of speakers and delegates from all sectors and I’m confident that the workshop will be a great success. We will tweet and live blog during the event, so those of you who couldn’t make it to Wolfson feel free to keep an eye on #osjmob11coveritlive, lanyrd.com/cdpxf and other social media activity gathered on posterous.

Exciting times for OSS Watch

A page has been turned in the history of OSS Watch. After four years of strong guidance and excellent leadership, Ross Gardler has left OSS Watch to create a spin-out named OpenDirective with another great OSS Watch alumnus, Steve Lee. Ross has handed an OSS Watch over to me that is in very good health. With clear vision Ross has transformed OSS Watch into a service that is well-equipped to serve the current UK academic sector. I look forward to working with our excellent team to continue our services following on from the successful direction Ross has taken us.
Continue reading ‘Exciting times for OSS Watch’

Open Source Junction 2 – early bird registration ends tomorrow

If you want to hear about industry-academia collaboration and join the newly created open source mobile tech community, then you should plan to be in Oxford on 5-6 July at Open Source Junction 2.

This second event in the Open Source Junction series targets specifically context-aware mobile technologies. Speakers from industry and higher education institutions will present their most recent work and will explore opportunities for collaboration in this area.

For more information about sessions and speakers, and to register, please check the OSS Watch event page. Early bird registration ends tomorrow.

Open Source Junction 2, 5-6 July 2011

OSS Watch, in collaboration with 100% Open, has created Open Source Junction, a series of exciting events connecting industry and academic innovation. These events bring together the best business and academic minds to explore how the two sectors can jointly innovate and exploit open source mobile technologies.

Following the successful Open Source Junction 1 back in March, Open Source Junction 2 will focus on context-aware mobile technologies. In computer science, context-awareness refers to the idea that computers can both sense and react based on their environment. Context includes location (the users’ absolute or relative position, surrounding resources, physical conditions, such as noise or light levels), but is also understood as a broader process involving users themselves (their habits or emotional states, patterns of social interaction, types of activity, etc.).

This two-day workshop, to be held on 5-6 July at Wolfson College in Oxford, will showcase a selection of context-aware mobile projects and provide delegates with key knowledge of open innovation and open development. Participants from both industry and academia will also have a unique opportunity to explore potential partnerships in the field of context-aware mobile technologies. Registration is now open.

I hope to see some of you at the event.

An open letter to OSS developers: thank you!

This guest post is contributed by Donna Reish, who writes on the topic of best universities.

Dear OSS developers,

I wanted to write to say thank you for the work that you do. Thank you for the hours you put into your projects. Thank you for developing them and updating them. Thank you for keeping them free! And thank you for thinking up and creating the tools that make my job easier.

As a freelance writer, I cannot earn a living without having excellent tools: a working computer, pens and paper, internet access, image-editing abilities, and a word processor. The health of my business depends on how well these tools work for me as I complete my projects.

At the same time, I’m appalled by the cost associated with some of the options out there. Adobe InDesign and Microsoft Office Suite are both quite expensive, and I have a hard time justifying diverting my money to pay for those when my income is already squeezed as tightly as it is.

Instead, I have found that products created as openly as possible and provided for free have done wonders for my business. I’m speaking, most specifically of course, about OpenOffice.org, which, as you well know, has a writer program that more than allows me to accomplish all of my basic writing tasks.

I think one of the beautiful things about open source applications, like OpenOffice’s word processor, is that they integrate with other applications almost seamlessly. In the case of word processors, I can save a document that I’m working on in such a way as to allow someone with Microsoft Word to read and edit it just as easily. When I coordinate with my clients, I don’t have to jump through a lot of hoops in order to make the file a certain kind in order to help them read it or edit it. As someone who doesn’t quite know how computer programming works, I treat such compatibility like a miracle on earth!

Another open sourced application that I’ve found incredibly helpful for my freelancing business is GTD-free, an open sourced productivity application that basically helps me implement the ‘getting things done’ method of personal productivity management. When I freelance, I often juggle multiple projects, many of which have different deadlines and requirements. I need to have a great method of keeping all of it tracked in one place. I used to use a Moleskine notebook, but I found that the exercise of constantly writing down things was getting to be a task in and of itself. The switch to this application made my life so much easier.

Finally, I know I owe open source developers a lot, but if you have better suggestions regarding productivity apps, feel free to share your comments! I’ve been really happy so far with the tools I’m using, but I’m always looking for ways to improve.

Anyhow, these are some of the real world benefits for which the work you do is indirectly responsible! Thank you again.

Sincerely,
Donna Reish

Editor’s note: Donna’s letter is an excellent example of someone acting in the evangelising role. The evangelist is an important role within an open source community and is discussed, along with all the other community roles, in the OSS Watch briefing note ‘Roles in open source projects‘.