Archive for the 'Business' Category

UK Government Open Standards Survey

There’s no date on his introductory post, but Francis Maude, Minister for the Cabinet Office and Paymaster General, has provided an opportunity for us to state which open standards for IT we want the UK government to use. This takes the form of an on-line SurveyMonkey survey that is open until 20 May 2011.

Government must be better connected to the people it serves and partners who can work with it – especially small businesses, voluntary and community organisations. Government ICT must play a fundamental role in making life easier and I want to ensure that it does.

One of our first goals is to organise Government data and systems using an agreed set of standards that make our ICT more open, cheaper and better connected.

If you’re a business or community organisation, helping us choose the right standards will make it easier for you to do business with Government.  It will also help us open up data, better informing your decisions, and hopefully prompting innovation.

There’s a lot of detail in the very long list of obtuse standard numbers, but fortunately a mechanism is provided to skip sections you aren’t interested in. Otherwise you can vote on each standard on a scale between mandatory and don’t use. Refreshingly for a survey, there are spaces for you to add your own thoughts (though you can’t add each on a new line as requested).

I spotted couple of typos and more seriously, the Microsoft originated ISO/IEC 29500 Office Open XML is incorrectly called ‘Open Office XML. This is bound to lead to confusion as the alternatively listed ISO/IEC 26300:2006 Open Document Format for Office Applications (OpenDocument) standard was originally implemented in OpenOffice (and is now implemented by LibreOffice).

Open standards play well with open source software developement and we encourage you to take the survey. However do bear in mind the government’s past record in implementing open technology policies. You might also want to look at Glyn Moody’s related post about the Government’s definition of open standards provided in the procurement policy note.

The JCP is Dead to me, Long Live Java

I’m a great believer in community, openness and transparency. I have lived the majority of my life believing in teamwork, collaboration and honesty.

When I was a schoolboy I played Volleyball. My coach taught me the importance of working hard within a team and, as a result, I was lucky enough to be selected for the England Schoolboys Squad. During the final squad selection process I suffered a pretty bad injury that prevented me from participating in the traning sessions. Rather than sit at home sulking I took my coaches advice and helped the remaining players demonstrrate their skills. I worked hard to both hide my frustration and ensure that the team was prepared to play without me.

On the day the final squad was selected I was the first to be called into the Managers office. Naturally I expected to be dropped, I wasn’t fit. Instead of dropping me the Manager explained that a team needed motivators and leaders as well as raw talent. Apparently he had seen two of those three qualities. To my amazement he asked me if I would take the role of Vice-Captain, focussing on team spirit and cohesion.

I was proud and amazed, but more importantly I’d learned a great deal about the importance of teamwork and collaboration.

A few years later my fun seeking took a turn towards some of the less healthy pursuits in life. Music became more important to me than sport and, after a series of false starts, I ended up managing a Dub Reggae band based in the crescents of Hulme in Manchester. This area was a horribly run down and deprived area, but it was a place of wonderful community and togetherness (if anyone cares the ExHulme site is devoted to how the area was back then, there’s even a photo of the band in its early days, with a very flattering although not quite true heading).

The band was called Community Charge, a play on a hated Tory policy of the time and a call to arms for the community to rally and charge against such policy. Through my time building the band and crew to a team of 16 people I learned that a handful of individuals with passion, vision and talent could rally huge numbers of individuals for a cause, entertain, have fun and even earn a living.

Fast forward a few more years and I discovered FidoNet and open source software as a means to reducing costs in organising and managing our tours. I immediately felt at home, the whole idea of people coming together to share skills in order to achieve more just felt “right”.

A few more years later endless touring had taken its toll. I went to University as a mature student in order to reinvent my career. I learned more from open source communities than from my lecturers. I became a committer on my first Apache project and I took an unexpected career move into academic research. My open source mentors helped keep me ahead of the curve. I contributed back and was rewarded with recognition and support that would have been far too expensive otherwise. I became an independent contractor and never looked back.

As a Java weenie I rejoiced when the 1998 creation of the Java Community Process (JCP) promised to allow the future of the language to be openly defined. Whilst the language itself wasn’t open source, at least the process for defining the language was open and reasonably inclusive.

More fast forwarding and Sun Microsystems announced that they were going to open source their Java implementation. The licence they chose was not a license I like to use, but OpenJDK is a free and open source implementation of an openly defined language. What’s not to like?

I’ll tell you what’s not to like – there’s a trap.

A trap that many in the community were not recognising. There are hidden restrictions that mean I (and you) can’t modify OpenJDK to suit our needs. If we do modify it we have to choose between either remaining protected from patent litigation or conforming to the GPL, the chosen licence for OpenJDK.

Similarly you can’t create an independant open source implementation of Java and protect users from patent litigation whilst also conforming to the Four Freedoms and/or the Open Source Definition.

This trap was put in place by Sun Microsystems and The Apache Software Foundation (ASF) fought hard to remove it. The ASF has served on the JCP Executive Committee for the past 10 years, winning the JCP “Member of the Year” award 4 times, and recently was ratified for another term with support from 95% of the voting community. The majority of the EC members, including Oracle, have publicly stated that restrictions on distribution such as those found in the Java SE 7 license have no place in the JCP

Sun did not remove the trap (despite a contractual obligation to do so) but they chose not to trigger it either. instead they chose to keep it primed for a day when it might be sprung.

Today Oracle own Sun Microsystems. One of Oracles first actions was to make it clear that they were not going to change the licencing terms for Java (despite a contractual obligation to do so). Even worse, Oracle sent clear signals about their strategy for Java – they were going to trigger the trap.

Since none of my business activities have ever made me rich I’m not about to tell Oracle how to run their business. However, I do claim to know a thing or two about openness, transparency and fairness.

Oracle are free to play the closed game with Java, but I object to being lied to.

The java specification is not open, OpenJDK is not open – Oracle should stop the lies.

I’ll skip over the fact that Oracle objected to the trap when they might be caught in it, but are willing to use it now they own it.

I’ll also skip over the fact that James Gosling, the creator of Java, has quit Oracle over their handling of the Java language team (Gosling told eWeek that “Oracle is an extremely micromanaged company. So myself and my peers in the Java area were not allowed to decide anything. All of our authority to decide anything evaporated.”)

Instead I’ll just add my support to The Apache Software Foundation who have resigned from the JCP EC. I’ll also add my support to the two distinguished individual members, Doug Lea and Tim Peierls who have resigned in protest over the same issue.

I object in the stongest possible terms, to Oracle claiming that Java is open when in fact it is “proprietary technology that must be licensed directly from the spec lead under whatever terms the spec lead chooses.”

The JCP is dead, will Java continue as a proprietary technology or will the community step up?

Disclosure: I'm a member of the Apache Software Foundation. In this post I speak entirely as an individual, 
not as a member of the Apache Software Foundation or as a member of the OSS Watch team.

The Novell Deal

The web has been aflutter with the news that Novell – owners of the SUSE Linux distribution – have been sold to Attachmate, and that futhermore a bundle of 882 patents belonging to Novell have been sold to CPTN Holding, a somewhat mysterious proxy for a group of tech companies organised by Microsoft. Whenever the words Microsoft and Linux get mentioned together there is extensive internet drama. In this case the concerns raised were chiefly

  1. that Microsoft might somehow use the 882 patents to destroy Linux
  2. that Attachmate might kill the openSUSE project

Point 2 was answered quickly by a statement from Atachmate shortly after the deal was announced:

“The openSUSE project is an important part of the SUSE business… As noted in the agreement announced today, Attachmate plans to operate SUSE as a stand-alone business unit after the transaction closes. If this transaction closes, then after closing, Attachmate Corporation anticipates no change to the relationship between the SUSE business and the openSUSE project as a result of this transaction.”

That leaves the suspicion that CPTN Holding might be a lynching posse for Linux. An interesting post on the FOSSPatents blog argues convincingly against panic on this score, but I think there are also other reasons for delaying any effigy burning or widespread acts of civil disobedience.  Novell was a member of the Open Invention Network, an organisation that holds a group of patents and licences these to tech companies on condition that they commit not to use their own patents against Linux. The OIN is criticised on occasion for seeming to be inert (in fact the blog post I linked above does just that) but it’s quite possible to argue that for a body like the OIN success looks an awful lot like inertia. After all, if it were constantly having to ride to the rescue of Linux, it would be failing in at least its intended deterrent effect.

In any case, OIN is kind enough to publish the standard agreement that tech companies sign up to when joining.  This agreement covers what happens when a signatory wants to sell (assign) the patents that they have agreed not to use against Linux:

5.1 No patents subject to this Agreement shall be assigned or any rights granted hereunder unless such assignment or grant is made subject to the terms of this Agreement. Neither OIN nor You shall assign this Agreement, assign any of its rights under this Agreement, or delegate any of its obligations hereunder, unless otherwise agreed in writing by the other party. Any attempt to do any of the foregoing shall be void.

I am not a lawyer, but my reading of this clause is that – assuming this agreement was in force between them – Novell needed OIN’s agreement to sell their patents and the patents themselves remain subject to the agreement at their new home. If this is the case, it seems extremely unlikely that they can be used against Linux.

Use OSS Watch’s resources within your organisation

Open source software projects can form a perfect example of a level playing field in software development. This is especially true for projects that have a meritocratic governance model in place, which by definition recognises all contributions to the project equally regardless of the person or organisation contributing. This is one of the reasons why we believe open source software projects are the prime example of open innovation in software.

It is therefore of no surprise that a lot of the materials that we write at OSS Watch are not just applicable to the Higher Education and Further Education sector in the UK (which form our remit as defined by our main funding body JISC). On the contrary, many of our documents discuss issues related to open source that apply just as well to the public sector at large, or to the commercial sector for that matter. I will highlight a few of the most relevant documents here.

Suppose you are in an organisation that’s developing software either for itself or collaboratively with other departments or other organisations. If you are considering the longer term sustainability of your software you might want to consider releasing your code under an open source licence. To better understand what software development in open source projects actually entails, our document that deals with getting to grips with the open development method could be of interest.

In many cases it is more beneficial to join an existing project community rather than trying to create your own. Joining an existing project means that you can tap into an existing body of knowledge and benefit from the development efforts of other, potentially myriad, developers. To better understand the mechanisms of contributing to an open source project some of more technical documents, like the one that explains what a software patch is, could be helpful. In any case you will have to make sure that all the provisions are in place to be able to contribute your code to the project.

If you are sure there is no existing project where your code will fit, you could consider starting your own open source project. In that is the case, it is important to consider what the right governance model is for your project. Do you want to go with the benevolent dictator model, which leaves all decision to one person or governing body, or do you want to create a level playing field by choosing a meritocratic governance model? Another important aspect in open source projects is ensuring the Intellectual Property is properly managed, which means that you should consider putting a Contributor Licence Agreement in place.

A completely different use case that we come across often is considering open source in a procurement process. Also then many issues are the same irrespective of whether your an academic institution, some other organisation in the public sector, or a commercial company. Our document on decision factors for open source software procurement could be useful in these circumstances. To get a more detailed and substantial view on existing open source projects, we have developed the Software Sustainability Maturity Model that guides you through the most important issues you should consider as an end-user of open source software.

To summarise, there are many aspects of open source software where our resources may be of use. All OSS Watch documents are available under a Creative Commons Attribution-ShareAlike 2.0 England & Wales licence, so you are free to reuse our content as long as you mention where you got it from and make any derivative work available under a similar licence. These are the documents that were mentioned in this post:

Daniel Pink’s Drive: open source model is key to future development

This guest post is contributed by Alvina Lopez, who writes on the topics of accredited online schools.

What continues to surprise me most about open source software (OSS) development is how the particular mindset OSS embodies has seeped into an incredibly diverse range of discussion that transcends software itself. Daniel Pink’s latest book Drive: The Surprising Truth About What Motivates Us is the latest example of how OSS has served to concretely demonstrate truths about human behavior.

The basic gist of Pink’s book is that business models of the 20th century have it all wrong in terms of what drives employees to perform better. Pink argues that for workers whose jobs require creative skills the kind of work that represents an increasing majority of jobs in America and the UK now that repetitive tasks are being more frequently outsourced, money is a poor motivator. Rather, by delving into the latest research in neuroscience and behavioral science, Pink suggests three things that motivate creative production: autonomy, mastery, and purpose.

Pink defines autonomy as having greater freedom at work. Given the chance to be self-directed, Pink demonstrates, workers will approach tasks they’ve designed themselves with greater enthusiasm. Pink cites the company Google, which requires that all employees spend 20% of their time working on whatever they feel like doing. Google has noted that some of the company’s most innovative ideas have grown out of their 20% rule. Mastery, according to Pink, is the desire to become highly skilled and knowledgeable in a specific skill or set of skills for its own sake. The final piece of the motivation puzzle is purpose: knowing that what you are spending your time doing is reaping tangible benefits for others.

When looking at Pink’s scheme, it comes as no surprise that he offers the open source software revolution as the golden model of true human motivation in action. Those of you in the OSS camp know full well the personal fulfilment derived from working on a project in which you are given an opportunity to join a community, collaborating with others freely and openly, working on your own time to master your craft, and helping others out in the process.

Although many open source software developers subscribe to the open source mindset, Pink points out that few look at the bigger picture. In an interview published on OpenSource.com, Pink noted:

‘I think that people who are involved in open source sometimes don’t realize how extraordinary it is. [...] If you had presented it in business school to some strategy professor saying, “I’ve got this new business model for creating software, and here is how it goes: A bunch of people around the world who don’t know each other get together and work for free. And these are highly skilled, technically able people who decide to do really tough, sophisticated work for free, and they give away their product”, it would have seemed ludicrous. And the fact that it worked and it worked so well, and the fact that it has challenged if not toppled other software products that are created in the more conventional way, ought to give us some hints about how we structure firms, how we organize workers, and I think deep down what really motivates people to do amazing things.’

In the final analysis, Pink’s book about motivation demonstrates why OSS is so successful, and how the model can inspire and inform both businesses and individuals seeking fulfillment through work. It’s an engaging read that will remind you why and how OSS plays such a pivotal role in the development of expanding human capability.

Case studies on open innovation from academic projects

CERN is an organisation with a major track record in terms of openness, going back to the very start. The declaration from the 1953 CERN Convention states: “the results of its experimental and theoretical work shall be (…) made generally available”. Well known is the history of the world wide web and the role of Sir Tim Berners-Lee played, who was working at CERN at that time.

Last week I attended and presented at a workshop on ‘open source software with TT Perspective’, organised by the Technology Transfer Network at CERN. Given their long history of developing and using open source software, the TT network was interested in getting to know more about issues related to the commercial exploitation of open source software.

I presented two case studies of projects that originated from academia and managed to generate a lot of interest from the commercial sector. The first one is Apache Wookie (Incubating), a project OSS Watch is working closely with. Wookie started off as part of the TENCompetence project but the people at Bolton University realised that there was value in the widget server they developed as a separate project. By bringing the project to a foundation and working on a W3C standard it attracted the attention of many new potential partners, both from the academic and the commercial sector. Some of these have resulted in collaboration both on the project itself and in new collaborations with Europe.

The other example I presented was TexGen. By open sourcing this modelling tool, the university of Nottingham found many new collaborators. Commercial partners, for example from the aviation industry, were interested in this tool and in the expertise that Nottingham had developed. The open source project turned out to be a very good marketing tool and as a result new investments were made.

These examples show how open source software projects are an excellent example of bringing open innovation into practice. Cross-collaboration between the academic and commercial sector can thrive in these projects and the examples mentioned show that there is not a single best way of achieving this. Wookie and TexGen are quite different projects: Wookie is centred around widgets, which is a very generally applicable technology, and the project carries a permissive licence. TexGen on the other hand is operating in the niche market of modelling the geometry of textile structures and their licence is GPLv2. But in both cases the commercial sector was interested and willing to invest in the project. Being open and making their work generally available as an open source project was a key factor. This involves much more than just choosing a licence and dumping your code; by using the open development methodology projects can become a true platform for open innovation.

Machine, transformation or cop-out?

After a long, long wait, the Supreme Court of the United States has finally delivered its opinion (pdf) in the so-called ‘Bilski’ appeal. The judgement was eagerly awaited by those who opposed software patents, as it held the potential to change the rules on patentability of software in the US.

Thirteen years ago Bernard L. Bilski and Rand Warsaw applied (pdf) for a patent on a process that sought to allow commodities traders to reduce their risk exposure. The key components of their invention were a list of steps traders could take, and an expression of those steps as a mathematical formula. The patent application was rejected on the basis that it did not describe a specific apparatus, that it manipulated only abstract ideas and that the problem it solves is an exclusively mathematical one.  Bilski et al kept appealing the decision at progressively higher courts, and kept getting knocked back. Finally the en banc court (a kind of grand moot of all the Court of Appeal judges reserved for issues where uniformity of opinion is particularly important) knocked it back while also tearing down one of its previous ‘tests’ for patentability which might otherwise have been interpreted as supporting Bilski et al’s arguments. This test, established in the case of State Street Bank & Trust Co v. Signature Financial Group, Inc. in 1998, held that a process could be patented if it produced a “useful, concrete, and tangible result”. The State Street decision was taken at the time as a green light for patent applications on abstract concepts like business and software processes.

In the light of the Bilski patent claim, the en banc court decided that this was too low a hurdle, and that they needed a new test for patentable processes. Instead they insisted that a process must meet the following two criteria: “(1) it is tied to a particular machine or apparatus, or (2) it transforms a particular article into a different state or thing.” This has become known as the ‘machine or transformation test’. Bilski responded by taking the final throw of the dice and asking the US Supreme Court to review the en banc court’s decision. The Supreme Court agreed.

So what does this have to do with software? Well business processes are frequently embodied in software, and the discussions of where the borderline between invention and abstraction lies is an extremely relevant one in the world of software development. The ‘machine or transformation test’, if affirmed by the Supreme Court, would very likely have made many pure software inventions unpatentable (as general purpose computers are not ‘particular machine[s]‘, and their own internal processes and data unlikely to qualify as ‘particular article[s]‘). After the en banc decision hopes were high in the anti-software-patent community that the Supreme Court would affirm the ‘machine or transformation test’ and make widespread software patenting a thing of the past. On the other side of the argument, groups like the Business Software Alliance and Dolby Labs submitted amicus briefs to the Supreme Court arguing that the machine or transformation test would kill off a large proportion of their livelihoods.

Perhaps inevitably the Supreme Court has chosen a middle path that brings little certainty to anyone except Bilski et al – who now definitely know they’re not getting their patent. The decision finds that the specific Bilski patent is indeed an attempt to own an entirely abstract concept, and so should be disallowed. It does not, however, go as far as to agree with the en banc court that the ‘machine or transformation test’ is the new gold standard for patentability in these worryingly abstract domains:

The Court’s precedents establish that although that test may be a useful and important clue or investigative tool, it is not the sole test for deciding whether an invention is a patent-eligible “process”

A little further on, the decision gives the effect on software patentability as a good reason for not adopting the ‘machine or transformation test’, and in doing so cites a group of software problem domains that – it seems to imply – are very firmly the proper subject matter for patents:

But there are reasons to doubt whether the test should be the sole criterion for determining the patentability of inventions in the Information Age. As numerous amicus briefs argue, the machine-or-transformation test would create uncertainty as to the patentability of software, advanced diagnostic medicine techniques, and inventions based on linear programming, data compression, and the manipulation of digital signals.

Yet a little further on, we get the qualification:

It is important to emphasize that the Court today is not commenting on the patentability of any particular invention, let alone holding that any of the above-mentioned technologies from the Information Age should or should not receive patent protection.

Clearly there is confusion here. There seems to be an anxiety on the part of the Supreme Court that they will ‘break’ innovation whichever way they lean. This is perhaps best expressed in this elegantly-phrased linguistic shrug:

This Age puts the possibility of innovation in the hands of more people and raises new difficulties for the patent law. With ever more people trying to innovate and thus seeking patent protections for their inventions, the patent law faces a great challenge in striking the balance between protecting inventors and not granting monopolies over procedures that others would discover by independent, creative application of general principles. Nothing in this opinion should be read to take a position on where that balance ought to be struck.

True, that.

Is UK research ‘wired for innovation’?

Apparently French research is not ‘wired for innovation’. The reason, according to Presans who reports from a recent Lyon round table, is the low levels French public research score on the Technology Readiness scale. Technology Readiness is a model used in the aerospace and defence sectors to evaluate the maturity level of a new technology. According to this model, levels 1-2 correspond to basic research, 3-6 indicate intermediary stages as the project moves from demonstrator to prototype, and 9 is assigned to a technology ready to be released on the market. According to Florin Paun, Deputy Director for Industrial Innovation at ONERA, technologies produced by public research should reach at least level 4 on the Readiness scale in order to attract industry partners, but most French research units, with some notable exceptions, tend to score below this mark. Research and industry do not speak the same language, the author of the post concludes, therefore there is a need for translation and  reformulation of the needs of businesses and of the solutions provided by research laboratories.

The lack of a common language for all categories of research stakeholders was also identified in studies of UK research infrastructure, as OSS Watch pointed out. Despite an impressive array of online systems and services aimed at helping researchers carry out their research, these technologies are often employed below their full potential. One way to improve this situation is to take stock of some key lessons from open source development, which include providing an open space for expressing the needs and concerns of researchers, software developers, service providers, and indeed all external partners, including businesses, who may wish to join the community.

OSS Watch conceived TransferSummit precisely to address this lack of mutual understanding between the academic and business research stakeholders interested in open development and open innovation. Two of the academic projects we advised recently have started to benefit from collaborating with non-academic partners. TexGen’s decision to make their research software freely available resulted in attracting supplementary grants and facilitating industry collaboration, while Wookie’s choice to join the Apache Software Foundation’s Incubator attracted interest from both the academic and commercial sectors. Both these and other academic projects will feature at TransferSummit, along with key representatives from open source businesses and software foundations, including in no particular order, Red Hat, Sourcesense, Sirius, WSO2, Indiginox, Day, HP, Amazon, Gnome, Apache, Codeplex, Mozilla, LiMo, Wikimedia, who will discuss the challenges and opportunities associated with academic-industry partnerships.

French research may not be ‘wired for innovation’, but is UK ready to reap the benefits of open innovation emerging from the dialogue of the academic and business sectors? Join us at TransferSummit to find out.

Build a better Facebook through open innovation

There is a rapid groundswell of concern about Facebook. The main issue is privacy, or rather Facebook’s attitude to individual privacy and data ownership. Over the years the default settings have relaxed from most items being private, to virtually none being so. Unless the user makes a concerted effort to change settings. Accordingly, there is a lot of talk about creating an alternative to Facebook. As is often the case, many are looking towards a more ‘open’ version, though what they mean by that may not always be clear.

One example that currently stands out is Diaspora*, a project idea to create a distributed system where each person manages their own data rather than trusting it to a central hub run by a business. In a few days the four NYU students behind the project have gained a lot of interest and an awful lot of micro funding pledges. As noted above, it is not surprising that they propose to use open standards, open source and open development in their descriptions. But could there be a better form of ‘open’ to consider here?

As Social Hacking points out, if you are going to build another open Facebook you might as well make sure it is an improvement. While the author makes several points for how to make sure you surpass the existing Facebook, one really stuck out when I read it.

3. Learn from Academic Researchers

Many people in the academic community are producing research that addresses how people interact both offline and online, as well as how people understand concepts of privacy and social networking. As websites continue to reshape the fabric of our society and Facebook in particular affects notions of privacy, you simply can’t afford to ignore these studies.

My interest was piqued not only because we at OSS Watch are based in academia and support research projects. Rather, I was interested as it hints at, but does not make explicit, a powerful opportunity from being ‘open’. Taking it at face value it’s possible to interpret the comment as a suggestion to read papers and be influenced by the ideas they contain. I was struck by a more powerful way to embrace the ideas, namely through open innovation in software, or open development of open source software.

Open Innovation allows companies and developers to directly engage with academics in a collaborative relationship likely to be much more fruitful than just consuming papers. This can lead to a win-win where the project gains from the theory, leading to more profitability, and the academic gets a working implementation of their work, not to mention exposure and validation. Hopefully the Diaspora* project will take steps to actively engage some of the listed academics in their project, and so reap the rewards.

There are some hurdles to overcome on the road to open innovation. Not least are issues of trust and cultural differences, along with the need to find the right people. However there is growing understanding of how to manage these issues, building on the wealth of experience learnt in those open source projects that have successfully crossed boundaries. JISC are also encouraging pilot studies of open innovation through the recent JISC Grant Funding 1/10: Access to Resources and Open Innovation.

On June 24/25/26 in Oxford there is an excellent opportunity to directly explore open innovation with the people who are actively engaged in it. The TransferSummit, provides a forum for business executives and members of the academic and research community to discuss requirements, challenges, and opportunities in the use, development, licensing, and future of Open Source technology. I hope to see you there.

Free academic passes for TransferSummit/UK

We’ve been posting about the importance of open development in sustianble open source projects for a long time. We’ve been running well attended workshops on the topic for almost as long. Now we are stepping up a gear and bringing you a three track, two day conference with a barcamp thrown in.

What’s more, if you are an academic we’re even giving you free tickets (mail us for a discount code).

Showcasing an array of presentations, the two-day conference comprises three content tracksinnovation; development and collaboration – each containing six sessions a day. The Innovation track, aimed at executive-level attendees, provides a top-level immersion into the world of Open Source. Topics cover foundations, infrastructure, licensing, governance, community-building and more.

Sessions on the Innovation track include:

  • Dissemination beyond academic circles: Scott Wilson, Assistant Director, JISC CETIS,looks at how open source has taken work from the University of Bolton well beyond the usual academic circles
  • Are developers important?: Paul Walk, Deputy Director, UKOLN, discusses the important of developers in the innovation cycle
  • Is my community too small for success?: Gianugo Rabellino, CEO Sourcesense, dissects a typical large community and considers the assumption that projects need to be large in order to succeed
  • FOSS business models: Mark Taylor, CEO Sirius IT, examines common strategies for sustaining FOSS and the licensing and community models that support them
  • The economics of innovation in mobile technolgies: Andrew Savory, Open Source Manager LiMO Foundation, evaluates FOSS in the mobile ecosystem

Register now on the conference website (don’t forget to ask for your discount code if you’re working on academic projects)