451 CAOS Theory 
A blog for the enterprise open source community
Opening up the Open Source Initiative
Matthew Aslett, May 23, 2011 @ 11:28 am ETOne of the ironies of open source over the years has been that the organisation formed to “educate about and advocate for the benefits of open source”, the Open Source Initiative, was itself *perceived to be* something of a closed shop [see the comments for clarification on this point].
That is set to change as the OSI has publicly launched its plan to encourage greater participation by shifting to a membership model and elected board members. The plan was announced during a session at the Open Source Business Conference (slides) and is part of an effort to focus on the second half of the organisation’s mission statement: “to build bridges among different constituencies in the open source community”.
As OSI director Simon Phipps explains in an interview with The H, the plan is to begin welcoming existing open source-related organisations into an affiliate programme, staring with non-profit open source foundations (hopefully by OSCON), followed by for-profit organisations (but not corporations) and government bodies. There will also be a separate Corporate Advisory Board for corporations, and a Personal Affiliate Scheme for individuals.
The exact plan for voting rights and the board election process is still to be decided but a complex arrangement involving an electoral college formed of delegates from groups of affiliates and the OSI’s working groups has been proposed.
The complexity seems to have been born out of two requirements: a desire to ensure that working group participants are not out-numbered by affiliates, and to ensure that the OSI cannot be subverted by any single affiliate (or more specifically corporation) gaining too much power.
Protecting the OSI from subversion is clearly an important goal, although having read the proposal and discussion it does seem to me that this is receiving more attention than is perhaps strictly necessary (as an aside Henrik Ingo has proposed supermajority voting requirements to shield the Open Source Definition from being unnecessarily tinkered with which to my mind provides the security required without associated complexity).
Arguably, a fate equal to the subversion of the OSI would be irrelevance. Rather than assuming that organisations will seek to over-run the OSI, I believe more attention should be being placed on ensuring that organisations will seek to join. The OSI remains well-respected, but I believe that for many of the different constituencies in the open source community it is not entirely clear what it is that the OSI contributes beyond its traditional role of protecting the Open Source Definition and approving associated licenses.
During the launch presentation Simon Phipps made a good case for the increasing relevance of the OSI (such as its involvement in the investigation of the sale of Novell’s patents to CPTN) but the launch was very sparsely attended, even taking into account the business-focused audience and the fact that it was a late addition to schedule, and media attention for the membership plan has been thin on the ground.
For those already involved in the OSI its importance is self-evident. It is those outside that need to be brought in, however, and I know there are some that will need persuading that the OSI remains relevant if they are to give their time – and also their money – to join.
The expanded membership scheme is likely to require full-time staff that will need to be paid for, and it seems likely that the OSI will need to raise funds either through the affiliate schemes or corporate advisory board.
Deciding the nature and involvement of that Corporate Advisory Board is something that hasn’t been addressed as yet and could pose a significant challenge as different people will have different perspectives about what business entities and strategies are considered acceptable in relation to open source.
For example, during the opening remarks at the OSBC presentation Simon Phipps made reference to companies with “dubious” business strategies attempting to “game” open source.
While I am sure Simon was expressing his own views, rather than those of the OSI, he is clearly not the only person involved in this process with that perspective (hence the concern about subversion).
To be clear, there was no direct suggestion that such companies would not be welcome, but if the new OSI is to “build bridges among different constituencies in the open source community” it will be important to avoid any comments that could be seen to be discriminatory.
Open source means different things to different organisations, such that opening up the membership of the OSI was always going to be a complicated process. The plans for the affiliate programme are well thought out (if arguably overly complex) and it is understandable that corporate involvement has been set aside until the end of the year.
Previous attempts to create a membership/affiliate scheme have floundered, so the OSI board is to be congratulated in its progress so far. Anyone interested in joining the process should start with the slides which include the relevant links and contact details.
Comments (6) Categories: Licensing,Software




“closed shop”? Lemme tell ya, we weren’t exactly having our gates beaten down by the hordes pressing to be on the board and do the work. I was on the board for 12 years, and over that time we probably had five people volunteer to help. You in particular were never one of them.
You’re not exactly a “closed shop” when your door is open and nobody shows up. I’m really TIRED of this “closed shop” slander. I expect that this latest attempt to set up a membership program will fail, but before it fails, as it’s failing, and after it fails, the Open Source Initiative is always happy to entertain your thoughts via email: osi@opensource.org.
Not closed; never.
Thanks for the comment Russ.
No, I have never volunteered to help the OSI. But then I am not an open source software developer, vendor, whatever, I am an independent analyst that covers covers open source. Would you expect analyst that cover Microsoft [or any other vendor for that matter] to offer to help one of the industry initiatives that it is involved with?
Anyway, you are right of course that the door was always open, but my observation is that many people *perceived* the OSI to be a closed shop and that the reason the current membership plan has been proposed is to change that perception. I will adjust my post accordingly.
I’d be interested to hear your thoughts on why the membership plan is doomed.
Matt
I find your question to Russ very interesting.
Would an open source community expect an analyst to offer to help an initiative they are analyzing?
The whole point of open communities is that they would expect this. Generally they are evolved/tribal-trained to impart greater respect to the analyst who is prepared to roll up their sleeves and help out.
I can see that for analysts and journalists this is a problem and conflicts with efforts to appear impartial; but your question does show a gap that exists between cultures.
Good luck to the OSI and their new membership scheme.
Yes it is an interesting question. It depends on the person and the initiative I think: some analysts are very much practitioners, so it would make sense for them to participate in projects of interest to them without conflict.
We might (and do), give our time freely to open source projects and foundations where we might otherwise charge a commercial company for insight. It might not be much, but it is done in the sprit of sharing.
There are cases where the 451 Group has got involved in industry initiatives when asked to do so, and I have considered a greater involvement with open source projects but I have to consider how our actions would be received by all our clients.
Matt
“…it will be important to avoid any comments that could be seen to be discriminatory.”
I submit that this is incorrect, at least in part. After all, the very point of something like the OSI and its license definition is to “discriminate” between those licenses that are actually ‘open source’ and those that are not. Thus, it is quite reasonable for the OSI to take care that the ability so to discriminate not be subverted by particular constituents/constituencies for their ownd ends.
Discriminate against licenses that don’t meet the OSD, absolutely, but if a company is using an OSD approved license it is not for the OSI to decide what business practices are legitimate and dubious – unless it is going to define what business practices are “open source” and which aren’t. See my previous post here: http://blogs.the451group.com/opensource/2011/05/11/time-for-a-new-open-source-definition/