I have recently been on the road so I’ve hadn’t had a chance to address a posting By Dries, founder of the drupal project. Before I do, I think it might be enjoyable to provide some context on my thought about what I think are some important questions.
There are several projects and concepts which I have been working on in my last couple of years of service. One of these it the idea of Open Technology Development and a new approach for governments and public institutions to go about acquiring and participating in the software business ecosystem. Fundamentally these concepts have to do with understanding the nature of “enterprises” and their relationship to better and more sustainable processes. FLOSS and some floss projects represent reference models and potential supply chains for such approaches. But this conversation is one that in many cases is in its infancy and is not particularly well understood.
This is especially the case because another part of my job has been to spec out and design software systems that can leverage and use the web in new ways. Call it what you will, web 2 ohhhhhh or some other marketing term, the idea of using web native architectures inside the enterprise is also part of the equation. Part of what makes the design discussion important is that
- FLOSS enables by dramatically reducing the cost infrastructure
- FLOSS provides design patterns and reference points because of its highly Darwinist nature
- FLOSS projects are communities and are unique yet similar and exist at different levels of maturity and have diffrent cultural practices
- FLOSS projects exist at different states in maturity (i.e apache vs mysql vs cake php)
SO evaluating FLOSS as an enterprise and understanding which FLOSS projects ought be part of your OTD projects are dependent on both the internal factors of a given project, but also a series of economic and external drivers of evaluation that are diffrent than the traditional build vs buy evaluation criteria. Evaluating what you what to “assemble and extend” becomes a matter of asking question like “Can I work with the people in this community?” and “Is community size more important than say prefernce in something like programming language?”
Now the later question immediately will strike many a programmer and participant in FLOSS projects as odd. But the point is that these are decisions about joining communities not being made by programmers or traditional participants but instead by people in charge of the economic considerations, and not just the technical, of acquiring and adopting technology on behalf of enterprises. This is an important thing to understand, especially because these issues are about sustainability and long term return on investment.
And this lead to another part of the work I have been in involved in which is capability building. What does that mean then? Using OTD to build capability for partners that leverages web native approaches to technology? In one sense I think it has to do with this concept of what I call “microinfrastrcuture” - that in a very real sense is concerned with the similar concepts to microlending. In other words the seeding of capabilities of a technological nature that allow for the emergence of the economic connective tissue that results in local capability which in turn can become a participant in a global framework like the web.
There are several very interesting dynamics at play in this type of work and only some of them have to do with technology per say. Many of them actually have to do with the ability to miniaturize and make accessible the social and institutional frameworks that have taken root in other contexts. Microlending for example is a miniaturization that is made locally relevant, of lending and credit institutions that allows for access at almost any level of wealth, to the global financial framework - it gives people a stake. What then constitutes, in terms of features, maturity and community, the sets of capability for entering a similar technological framework - and for which actors?
It is why question of features like internationalization and localization, like the ones Dries is addressing, provide gateways into new kinds of relationships and can begin to introduce and provide access to capabilities that address the very real relationship of globalization to FLOSS communities.
At the same time, features alone are just not enough. The technological abundance that has created the twitters and myspaces and facebooks is too socially disconnected, too economically disconnected, from many of the institutions and places that could most readily take advantage of such capabilities. And while much of this is a natural process of technological and economic dissemination, its also a conscious act of effort and investment to bridge and create access to these types of technology supply networks.
The possibilities to bring together participant actors across enterprises, FLOSS communities and folks such as NGO’s universities, and people in emergent economies, are vast. It is a multifaceted dialog in which technologists and FLOSS communities, in my opinion, ought actively engage.