Archive for the 'Community' Category

DataFlow new release

As mentioned in an earlier postDataFlow is an Oxford-based project in the JISC UMF programme building a data management infrastructure to help researchers manage their research data.

OSS Watch, in collaboration with Open Directive, are providing licensing, development, community and sustainability support to the project, which is now getting very close to a new release.

Developers have frozen the code and are preparing beta versions of DataStage and DataBank, which will be available for testing as virtual machines. Please keep an eye on the project website and twitter channel for updates on when and where you will be able to access them.

We will hold a launch workshop in Oxford on 2 March with colleagues from the VIDaaS project, who are building an exciting cloud-deployable Database as a Service system.

Attendance is free but places are filling quickly, so book early to avoid disappointment.

Star pupils

Google has been in the news repeatedly over the last six months for closing down some of its many, many side projects. In general these are being mothballed in perpetuity, but in some cases, there is a transition plan. This is the case for Google Sky Map, and for our community it’s an interesting variation on the more traditional ‘open source it and hope it takes off’ approach that industry players like Nokia have tried in the past, and HP seem about to try again.

Sky Map is an application for Android mobile devices that was born out of the so-called 20% time that Google grants its engineers for the pursuing of personal projects. Back in 2009 when Sky Map was launched, one of the few hardware advantages that the few Android phone then on the market had over the iPhone was a hardware sensor compass. The ‘wow’ moment of the first public display of Google’s Android hardware (the G1) was a demonstration of how the Streetview service could be used in combination with the device’s compass to display information relevant to the direction you are facing. To build on this brief window of competitive advantage (the iPhone acquired a compass in its next hardware iteration) Google’s Pittsburgh office (then based on the campus at Carnegie Mellon University) developed and released Sky Map. The functionality – showing information about the night sky in the direction you were looking – was useful and educative and spawned tens of imitators over the next few years.

Given that the software no longer promoted a competitive advantage of Android hardware, and that the competition for apps of this kind has been getting tougher and tougher, it’s not entirely surprising that in Larry Page’s seemingly endless round of belt-tightening the project has been let go. Sky Map is returning to its roots on the Carnegie Mellon Campus:

“Today, we are delighted to announce that we are going to share Sky Map in a different way: we are donating Sky Map to the community. We are collaborating with Carnegie Mellon University in an exciting partnership that will see further development of Sky Map as a series of student projects. Sky Map’s development will now be driven by the students, with Google engineers remaining closely involved as advisors. Additionally, we have open-sourced the app so that other astronomy enthusiasts can take the code and augment it as they wish.”

This is an interesting approach. Although it’s not clear yet exactly what kind of student projects will be invited (computer science? astronomy? both? neither?) the idea of taking end-of-life, production code and open sourcing it to facilitate learning and teaching is a model I would like to see more generally adopted, for a few reasons.

Firstly, it is likely to teach open development methodologies to student software authors, something which is still notable by its absence in too many academic primary and secondary software development programmes. Secondly, it provides a compelling means of community engagement for the academic institution, opening a window into their teaching for the outside world and inviting collaboration. Thirdly, it advertises the skills of the students with a directness and accessibility that mere CV distribution cannot really match.

Although I’m not thrilled by Google’s year of the long knives (goodbye Google Sets *sniff*) solutions like the one proposed for Sky Map are genuinely exciting, and I’ll be watching for the resulting academic projects with interest.

An open approach for the benefit of our ICT education

Last week, Education Secretary Michael Gove announced that the current ICT curriculum, characterised as ‘demotivating and dull’, is to be replaced by a computer science programme. Gove said that the Programme of Study will be withdrawn and teachers are given freedom over what and how to teach.

Later that week, the Royal Society published the study on Computing in Schools, named ‘Shut down or restart?’. The main recommendation of the study is to restructure ICT education and make a clear distinction between these three main components of ICT education:

Continue reading ‘An open approach for the benefit of our ICT education’

Version 2.0 of the Mozilla Public License

Following a two-year revision process based on feedback from Mozilla and the broader open source legal community, version 2.0 of the Mozilla Public License (MPL) was recently released. The licence encourage contributors to share modifications they make to MPL-licensed code, while still allowing them to create projects that combine MPL-licensed code with code under other licenses (either open or proprietary).

Like its previous version, MPL2 has been acknowledged as a free software license by the Free Software Foundation and as an Open Source license by the Open Software Initiative.

The most important changes from the previous version include:

  • MPL2 is simpler and shorter;
  • addresses the recent changes in copyright law and incorporates feedback from lawyers outside the United States;
  • offer patent protections aligned with other open source licenses, which allow communities to protect contributors if these are sued;
  • provides compatibility with the Apache and GPL licenses, making code reuse and redistribution easier.

Nginx and the Open Core model

For years now the Apache HTTP Server has been by far the most widely used web server on the internet. Netcraft publish statistics on web server usage monthly, using a variety of metrics, and this month’s stats show an interesting change. While Apache HTTP Server is still miles in the lead, second place in the ‘active sites’ metric (meaning sites which are not just mothballed domain names) has transferred from closed source Microsoft web server IIS (Internet Information Server) to open source upstart Nginx (pronounced ‘Engine X’), released under the two-clause BSD license. Nginx has developed a reputation for speed and low resource requirements that has made it popular in a relatively short time.

So the fact that the top two slots in one of Netcraft’s surveys are now filled by open source web servers is interesting in itself, but there’s something more to this. Unlike Apache HTTP Server which is developed under the supervision of a US not-for-profit foundation, Nginx has recently become a commercial company offering paid support and successfully raising $3m in series A venture capital funding. As well as paid support, Nginx has announced that the intend to implement an Open Core model for their business going forward.

Now the Open Core model is what we used to call ‘proprietary extensions’, meaning that the open source code is supplemented with closed source paid add-ons for those that want them. In a way it is similar to the shareware model that did so much for PC gaming during the 1990s, bringing games like Doom to offices everywhere. One often cited problem with the Open Core model is, however, that users of the open source ‘core’ are at liberty to build competing open source versions of your proprietary extensions. Indeed you can find that ideological opponents of the partial freedom that Open Core embodies may be motivated to compete simply because of that ideological opposition, essentially enforcedly ‘opening’ the parts of the project functionality that you wish to keep closed. The only really effective defence against this risk is to be the best-resourced and most skilled team working on the code, thereby ensuring that your extensions cannot be easily replicated by competitors. So Open Core is an interesting strategy, in that it has drawbacks from both the purely ‘open’ point of view and the more traditional closed source approaches to software exploitation. In the past it has been accused of attempting to benefit from the ‘Halo Effect’ of open source while in fact leveraging closed methodologies for value realisation, but the fact that Nginx has managed to achieve so much in such a short period makes it a technology and a company to watch.

Why collaboration is worth the investment

Collaborating in an open source project might take time, but is worth the investment. Especially when bootstrapping a project and with a small community, the overhead projects need to put into the collaboration can be significant. But the rewards can make this worth the effort, even when having as few as 3 collaborators. At TransferSummit, I presented on this topic and the primary slide from that presentation was this one:

Continue reading ‘Why collaboration is worth the investment’

Reusable widgets demonstrating the potential of open innovation

OSS Watch is currently leading a small development project called Rave in Context. This project is developing templates to easily write W3C widgets that encompass best-practices in ussability and accessibility out-of-the-box. It is not feasible or useful for small projects like this one to try and develop a completely new community around the software. Instead, we looked for an existing project that would be a good home for the software and found that in Apache Wookie (Incubating). However, the project is also closely related to Apache Rave (also Incubating), because this project also supports the W3C widget standard and a few people involved with that project have shown an interest in what we’re doing.

Because of the close connection with these Apache projects and for the benefit of wider uptake of our project code, we thought it would be good to present about the Rave in Context project at ApacheCon 2011 in Vancouver. I was happy to be allocated a session in the ‘Fast Feather’ track, a track that focuses on latest developments and upcoming technologies.

The widgets that are being developed by the Rave in Context project will conform to the W3C widget standard. This allows for deployment in a W3C widget container such as Wookie. However, there are many other standards in the widgets and gadgets space. Another popular one is the OpenSocial gadget specification, which defines not only social concepts but also the packaging and specification of the gadgets themselves. Because of the big overlap between W3C widgets and OpenSocial gadgets, it has been relatively easy for the Rave project, that started of as an OpenSocial container, to also support W3C widgets. This makes the Rave in Context widget templates useful for that community as well.

During the presentation and some of the other talks and meetups at ApacheCon, it became clear that there is a lot of interest in the gadget/widget portal functionality that is being developed by the Rave project. Also the gadgets and widgets that are being developed may themselves be interesting to the wider community. We talked to a few people, for example, that have worked with portals based on the Java portlet specification, and are finding that this is not a specification that is suiting their needs anymore. They are looking to use a different technology for their front-end portals and the Rave portal is an option they’re considering. Also a project like Sakai OAE (f.k.a. Sakai 3) are working with gadgets and gadget repositories on their front-end. They are currently not working with a gadget standard, but moving to OpenSocial and using Rave as their front-end is something they are interested in.

The code of all the gadgets and widgets are currently scattered around the different projects, and this is not usually the best place for this kind of code. Hence, there is a clear need for a separate project to host the gadgets and widgets created, and this can also include the widgets created as part of the Rave in Context project. We will set one up at the Apache Extras site, which is a code hosting site specifically for Apache-related projects. This will enable anyone to reuse widgets and/or gadgets generated in any of the projects, thereby delivering on the promise of open innovation in software.

Meritocratic project governance in action

At OSS Watch we work with projects that develop software within and for academia. When these projects use the open development approach, they have the opportunity to engage third parties with the project and receive contributions from people with an interest in the project. In order to be able to do that, the project needs a governance model that makes it clear for external parties how to engage with the project. An example of how such a governance model would work in practice is the Cocoon project at the Apache Software Foundation (ASF), which is a classic example of how a meritocratic governance model works in practice. In this post, I will highlight bits of a case study that Andrew Savory has written about the project. It will demonstrate how the project governance at the ASF is organised and can help you when considering a governance model for your own project.

Continue reading ‘Meritocratic project governance in action’

Cross-sector engagement at TransferSummit

Many inspiring conversations made the TransferSummit conference, last week at Keble College in Oxford, a great success. The conference was chaired by OSS Watch alumnus Ross Gardler, now OpenDirective, who was responsible for putting together a excellent programme with a diverse range of sessions on open innovation in software. OSS Watch is a Silver Sponsor of TransferSummit and co-organised the conference. The programme was carefully crafted and the sessions followed on each other very nicely, telling the story of how open innovation can be successfully applied to software. We set up virtual tracks on specific topics to help delegates find their way through all the sessions. Still, an often-heard comment was that attendees found it difficult to choose which session out of the three tracks to attend, because so many appealed to them.

An addition to the overall programme this year was the Open Gadget Playtme. This showcased a number of open source hardware, or innovative hardware running open source software. For example, a RepRap printer was shown in action, an open source 3D printer that can print many of its own parts. Another example is the Rasperry Pi project, who aim to develop an ARM Linux box for $25, specifically aimed for use in teaching computer programming to children. This led to many interesting discussions about other applications of this technology, for example as part of a media streaming network.

Sessions were being presented by experts from diverse backgrounds, ranging from the academic sector, the business sector, and the public sector. This led to many interesting conversations about sharing experiences and the challenges in open innovation.

One compelling example of the kind of cross-sector discussions and engagement that TransferSummit facilitated was found in a session about the Apache Rave (Incubating) project . Matt Franklink of Mitre, with help from Ate Douma of Hippo, gave an presentation on how the project came about as a result of an initiative from six organisations, combining three code bases. In the audience was John Pybus of Oxford’s OeRC, who are working on the Bamboo project, an international collaborative research project that is developing tools and infrastructure for humanities researchers. As part of that project they are developing a Virtual Research Environment (VRE) platform, and they are already working together with one of the project partners on the Rave project. However, there is a compelling argument to move from reusing their isolated code base towards using and engaging with the Rave project. That would enable them to benefit from the programming efforts put in by all organisations involved. For Bamboo, it is important to know that they can build on a code base that will be sufficiently mature and supports the main features they need to build on. For Rave, it is an excellent opportunity to have another academic partner be involved with the project and with Bamboo’s input they can support a wider range of use cases.

This conversation and many others started at TransferSummit will hopefully lead to interesting new fruitful collaborations. OSS Watch will continue to play a facilitating role to connect people and projects relevant to the Higher Education sector to help foster open innovation. Do let us know about inspiring conversations you had at TransferSummit in the comments.

Open Source Junction 2 – video feedback

We asked a few speakers and participants at Open Source Junction 2 about the benefits they saw in building a community of industry and academic folks interested in mobile technologies.

The answers varied, but people seemed to perceive the diversity of points of view involved in this cross-cultural exercise as beneficial. The delegates with an industry background praised the deep thinking and creativity of researchers, while academics were impressed with the down-to-earth revenue-generating mindset of their industry colleagues.

The early feedback we got from the first event of the series was equally positive.

Open Source Junction 3, due later this year, will continue to facilitate the encounter between the academic and business cultures focused on open development in the mobile sector.

Watch this space.

———————————-

Camille Baldock, Softwire

YouTube Preview Image

—————————————————–

Steven Gray, University College London

YouTube Preview Image

————————

Julian Harty, ebay

YouTube Preview Image

——————————

Samuel Carlyle, Sukey

YouTube Preview Image

————————————

Nick Allott, NquiringMinds

YouTube Preview Image

———————————————-

Tim Fernando, University of Oxford

YouTube Preview Image

————————————————

Philipp Breuss-Schneeweis, Wikitude

YouTube Preview Image

——————————————

Yuwei Lin, University of Salford

YouTube Preview Image

————————–

Dave Raggett, W3C

YouTube Preview Image

—————————————

Gabriel Hanganu, OSS Watch

YouTube Preview Image