Abstract: Open source software has changed the rules of the game, impacting significantly the economic behavior of stakeholders in the software ecosystem. In this new environment, developers strive to be committers, vendors feel pressure to produce open source products, and system integrators anticipate boosting profits.
Abstract: Today’s wiki engines are not interoperable. The rendering engine is tied to the processing tools which are tied to the wiki editors. This is an unfortunate consequence of the lack of rigorously specified standards. This paper discusses an EBNF-based grammar for Wiki Creole 1.0, a community standard for wiki markup, and demonstrates its benefits. Wiki Creole is being specified using prose, so our grammar revealed several categories of ambiguities, showing the value of a more formal approach to wiki markup specification. The formalization of Wiki Creole using a grammar shows performance problems that today’s regular-expression-based wiki parsers might face when scaling up. We present an implementation of a wiki markup parser and demonstrate our test cases for validating Wiki Creole parsers. We view the work presented in this paper as an important step towards decoupling wiki rendering engines from processing tools and from editing tools by means of a precise and complete wiki markup specification. This decoupling layer will then allow innovation on these different parts to proceed independently and as is expected at a faster pace than before.
Reference: In Proceedings of the 2008 International Symposium on Wikis (WikiSym ’08). ACM Press, 2008: Article No. 21.
In the last few days, I’ve been reading up on author obfuscation. By “author obfuscation” I mean tools and techniques that will ensure an author’s anonymity when posting a blog entry or writing a document. You might think that not giving your name or writing under a pseudonym may be sufficient, but I don’t think this will stand the test of time. Specifically, if you are writing a blog under a pseudonym, you are creating a large corpus of text, all of which is being archived, and ten years from now smart algorithms may be able to correlate those postings with other work by you that identifies you as an author of the blog.
The use of wikis in software engineering dates back to 1995, when Ward Cunningham created the first ever wiki as a platform for discussing patterns and software development efforts. The simplicity and effectiveness of wikis as a medium for collaborative authoring has lead to their vast popularity across many domains.
This workshop aims to bring together researchers, practitioners, and enthusiasts interested in exploring the potential of wikis as an effective tool to support software engineering activities. Specifically, it is an opportunity to:
On their blogs, Matt Asay and Savio Rodrigues are discussing whether IBM is using open source to diminish competitor margins. I think it is obvious that IBM does this, most notably with its Linux engagement, which is squarely directed against Microsoft (Windows). It is what I call a war over the share of customer’s wallet, and open source plays a major role. The graph below shows how it works.
Title: Open Source Businesses and Developer Careers: Who Benefits from Open Source? How and Why?
Presenter: Dirk Riehle
Abstract: Open source is changing how software is built and how money is made. This talk discusses the economics of open source software from the start-up firm, the system integrator, and the software developer perspective. The talk provides a strategy framework and discusses its implementation using the dual-license strategy. It explains how system integrators use open source in the share-of-wallet wars. Finally, open source defines a new developer career. This talk explains this new career and argues that it creates economic value for some while it makes life harder for others.
Agile adoption in the Open Source community ranges from some to none for most successful teams.
Can these communities learn anything from each other?
Are these two communities one in the same?
Do Open Source projects and Agile projects succeed or fail for the same reasons?
The panelists, Dennis Byrne, Dirk Riehle, Christian Robottom Reis and Naresh Jain, will use their collective experience to answer these and many other questions. We’ll also have one empty chair for anyone from the audience to be a part of the panel temporarily.
Community open source is open source that is not owned by any particular company. Rather, ownership is shared among a large number of diverse stakeholders. Given the right (read: permissive) license, commercial companies can provide extensions to the community project, earning a living. Since such extensions are a unique selling point of these companies, one might think that they would prefer to keep the community project small and limited in features to facilitate an easy upsell to their more comprehensive offering. This thought becomes particularly intriguing given that commercial companies typically hire the core developers of such community projects to bring the necessary expertise in-house, and as some argue, to influence the project to their liking.
This upcoming Wikimania 2008 tutorial discusses the three principles of “open collaboration” which I believe are underlying wikis, open source, and other forms of peer production. It is a follow-up to last year’s tutorial about open collaboration at Wikimania 2007.
If the slideshow doesn’t play, please use the PDF file download below.
Reference: Dirk Riehle. “Bringing Wikipedia to Work: Open Collaboration in Corporations.” In Proceedings of Wikimania 2008, forthcoming.
For your information, a workshop on photographing technical conferences.
Photography Workshop at OOPSLA 2008
Photographing a technical conference well is not a matter of point and shoot, nor is it about taking pictures to share with friends and family. The time is ripe for more serious photojournalism to capture our community’s leaders, its activities, and its human face, and for the use of artistry to tell stories and get people thinking.
In this workshop you will learn basic technical and aesthetic techniques for good photography and good conference photography in particular, and you will practice these techniques during OOPSLA. Work will be critiqued using an artists’ workshop process to enable you to continue learning and improving after the workshop. Participants will attend a full-day of lectures and interactive learning activities as well as photograph Monday, Tuesday, and Wednesday with short, early morning artists’ workshops on Tuesday, Wednesday, and Thursday.