links for 2008-01-07

Posted in Journal. Tags: , . Comments Off »

SCALE08

SCALE LogoThe Sixth Annual SoCal Linux Expo is February 8th-10th, 2008. The Expo has expanded to included specialized conferences on the Friday prior to SCALE including the Women in Open Source conference, DOHCS–Demonstrating Open Source Health Care Systems, and newly added “Open Source in Education” which focuses on opportunities for Open Source in the field of education.

If you have any experience in any of the above-mentioned areas, please consider sharing it with the Open Source community at SCALE. All of the calls are open for submittal through November 30th.

http://www.socallinuxexpo.org/scale6x/conference-info/calls-for-papers/

links for 2007-11-22

Posted in Journal. Tags: , . Comments Off »

links for 2007-11-16

links for 2007-10-08

Posted in Journal. Tags: . Comments Off »

links for 2007-10-01

Posted in Journal. Tags: . Comments Off »

links for 2007-09-24

Posted in Journal. Tags: . Comments Off »

links for 2007-09-20

Posted in Journal. Tags: , . Comments Off »

links for 2007-09-14

Posted in Journal. Tags: . Comments Off »

Open Letter to OSI

Cross Post

Mike Tiemann, President of OSI and CTO of Redhat says he's putting his foot down. In a recent blog post he states:

Enough is enough. Open Source has grown up. Now it is time for us to stand up. I believe that when we do, the vendors who ignore our norms will suddenly recognize that they really do need to make a choice: to label their software correctly and honestly, or to license it with an OSI-approved license that matches their open source label.

If you read my personal blog regularly you know I’ve been outspoken about companies claiming to be open source, but not adhering to the OSD or licensing with an OSI approved license. In fact, I’ve been so outspoken I’ve offended some well connected people, I have even been called infantile names, and in some circles marginalized. I’ve blogged about the dilution of open source and the confusion created by new pseudo-open source licenses and I’ve left lengthy comments at OSI. Moreover, I spoke directly with Mike Tiemann about the need for OSI to put their foot down and take a stand for open source. I've even provided some ideas about how this can be accomplished.

In Mike's aforementioned post he specifies a few CRM companies that have been waving the open source banner, but do not license with an OSI approved license. The most well known being SugarCRM. I've blogged about SugarCRM and it's CEO John Roberts previously (the last bit of this post). Let me say, I really like John and I think SugarCRM is a quality product. Previously I stated I wasn't certain if attribution licenses were "bad", but that they were definitely unnecessary and placed unfair restrictions on others because the authors don't provide similar concessions to projects they use in their development. I now believe attribution is bad. If an open source project/product requires prominently displayed attribution shouldn't they also do this for all their components? Won't this escalate? Will applications end up looking like NASCAR? Take MindTouch's DekiWiki for example. What if it had the requirement that logos for MindTouch, MySQL, PHP, Mono, ImageMagick, Debian, Apache, on and on…were prominently displayed? Wouldn't this diminish reusability and begin to infringe on the freedoms of others? Isn't reusability, at least partially, the point of open source? I believe it is. We want people to reuse MindTouch's software and do great things with it. I'm certain a growing use of attribution would diminish the reusability of open source.

Those who use an attribution license do so with the intent of protecting their intellectual property. First of all, it should be understood copyright does this already. Secondly, I've often heard from companies who use an attribution license that they don't want a competitor incorporating their work into a competing proprietary product or stealing their work and rebranding it as their own. This is mostly solved by using GPL because of the nature of its copyleft clause. Eben Moglen gives a wonderful talk on not being another's free lunch that explains this brilliantly. All the attribution licenses I've seen are modified MPL licenses, which doesn't offer the same protection as GPL. Finally, the notion that someone will come along, steal your code, and be able to out-innovate you on your own code is a spurious claim. And quite frankly, if you can be out-innovated on your own codebase..well, you've got bigger problems. Free and open source software, is about freedom and freedom (and more choices) is always what's best for the market (users, developers, etc). For those who assert: "It's their work, they should receive attribution." or "I want to be attributed for my work." Well, so do I. MindTouch receives attribution thanks to copyright. It's wonderful to receive attribution, but restricting users or developers by requiring a prominently displayed logo and link is wrong and potentially harmful for reasons that should become clear when you understand the significance of free and open source software, which I will go into in a moment. For additional historical perspective on this topic review the UC Berkeley advertising clause.

An even more toxic misuse of open source that seems to be growing more prevalent and brazen is when a company successfully wields the banner of open source for years, but doesn't release a line of code. There is a difference between using open source and being open source. I suspect the Free Software Foundation would claim there is a difference between being free and using free software and would draw this line between free software and open source. I don't agree with this, but I do believe “open source is a development methodology; free software is a social movement.” And open source is a development methodology inspired by free software. At any rate, the ignorance of analysts and journalists has assisted offenders in spreading their deceptions intentional and otherwise. And OSI is partially guilty for this by not being more aggressive to stop it, but before I constructively criticize OSI I want to address why open source is so very important to all of mankind.

So what is the significance of free and open source software (FOSS)? If you don't understand why open source matters then this is a pointless conversation. Therefore, just to make sure we're all on the same page let's address this first. The reason why open source matters is the same reason why open standards matter. The Internet revolution and perhaps the very dawn of the Information Age has been fueled almost entirely by FOSS and open standards. Without FOSS and open standards there simply would not be the Internet you know and love today. The current boom in the technology industry is due almost entirely to FOSS and open standards. The first .COM boom also owes itself to FOSS and open standards. How so? So as to not dig too deeply into history let's just examine the current Web 2.0 boom. Because there are huge repositories of open source applications, libraries, and components developers are able to very quickly build interesting things at very low costs. Most often these applications are then released for others to create derivatives of and build on. Or, thanks to open standards and increasingly this is true with SOA, one can provide an API for others to incorporate functionality into their own projects, but let's just focus on FOSS. In short, open source projects like Apache, Linux. MySQL, Perl, PHP, and many other thousands of projects are building blocks for engineers to construct wonderful things for all of mankind.

Having, I hope, now sufficiently established the importance of open source I suppose it's important to answer the question: so what, if others don't adhere to OSI'

s vision of open source? Who cares other than OSI, right? OSI is a community appointed board that is tasked with ensuring the building blocks, that are open source components, fit together cleanly. What if there were no standards body for licensing and defining open source? The result would be a chaotic landscape that would be very difficult to navigate and that would require an army of lawyers. It would not be clear what one license means relative to another, if they fit together, or how they would fit with proprietary software systems. Each license would have to be carefully examined by the individual wishing to use the component. I surely do not want to be responsible for this legal bill. FOSS would quickly become too expensive to be worth using. Clearly, only the lawyers win in this reality. I want to rely on OSI. They should make my life simpler and require less legal expense on all our parts. Moreover, I want them (and FSF) to be the umbrella that polices offenders who misuse the title of open source by not paying forward the benefits they reap from FOSS.

This brings me to my most unfortunate conclusion that OSI, in my opinion, has been remiss with its responsibilities. First and foremost there needs to be a membership, member involvement, and some transparency in how the board is appointed. I think a portion of the board should be elected. More importantly I think OSI should be more aggressive in policing our community. This can be done with very little overhead by using a "wall of shame", which I proposed previously. The wall of shame could be structured such that offenders are warned of their offenses and then ultimately ostracized by listing their offenses on a public website, namely www.opensource.org. This is a low cost solution that will undoubtedly prove to be effective.

 I believe that the folks at OSI are well intentioned hard working people who probably give far more than they receive. With a membership, perhaps paid, I believe the board can afford to give more and expect more in return. I know there is already a move underway to put in place a membership and I'm quite thankful for this. Moreover, it seems with Mike's most recent post there will be an increase in the aggressiveness of the organization in protecting open source. This too is wonderful news. I think open source is experiencing some growing pains as the community tests boundaries; however, if OSI doesn't reign the problem children I believe we'll all suffer.

Poster Child

Cross Post

I promised previously to highlight a developer a month. This month I'm highlighting Pete Erickson. I guess this makes Pete our developer of the month. Roy told me he was unwilling to peaceably relinquish his crown. Too bad Roy. It's Pete's turn to shine because he's a superstar and you're old news.

First a little background on Pete. Pete was born and grew up in a teeny tiny village in way northern Minnesota called Roseau.. He attended college at Bethel and then NDSU. He was hired by Great Plains software after school. Pete tells the story of his first week at work. He was informed the company was purchased by Microsoft. He was sufficiently pissed he considered quitting. He didn't though and he continued to work with Microsoft for a couple of years in and out of Redmond, WA. PeteE (as I call him) is passionate about open source and open standards. He enjoys participating in triathlons, biking, hiking, camping, and long walks on the beach with pina coladas. Ok, the last two items I manufactured, but the rest is true.

Open Source Developer Poster Child
 Open Source Developer Poster Child

Pete manages most of our infrastructure stuff. He's probably the best Linux guy we have other than Geoff. He codes mostly in C# although he's recently become adept in PHP. He manages the NOC, all our software packaging, install guides, and upgrade scripts. Mostly recently he's done a lot of work in Hayes on Lucene with search indexing, he wrote the RSS API, and he even wrote a Drupal authentication service for DekiWiki.

Pete was actually the first engineer hired by MindTouch. He was a contractor even before Roy came on as a full time employee. He was introduced to me by his now girlfriend Marianne who was doing some business administration work for MindTouch. Pete literally worked with me out of my windowless basement for a couple of months off and on. Unfortunately Pete still lives in MN. Hopefully his recent surfing expedition in Pacific Beach with Max will entice him to move to San Diego very soon.

Pete blogs on rare occasions too. He's done a nice write-up about the upcoming Hayes Beta2 release. Specifically he highlights:

  • Hayes has a web installer! No @#!t! And PeteE wrote it too.
  • New parser
  • Live data services
  • External Authentication services
  • Extensible storage provider model
  • New indexing service
  • Nicer UI, but I think he means improved presentation layer

Pete's post is a useful read for all you interested Gardeners. Enjoy! Oh, and be sure to click on the photos in this post so you can see the witty Flickr notes I placed on the photos. ;-)

Pete Erickson at OSCON2006

Another belated summary: Web 2.0 Expo

I attended the Web2.0Expo last week. MindTouch was exhibiting and Ken spoke about wikis in the enterprise. I had an interesting and pleasant conversation about badgeware with John Roberts. I made it to the AllThingsD launch party. And I spoke so much to so many people I ended up losing my voice for a couple days. I believe this was the largest trade show/conference I have ever been to. I was told there were over 10,000 people in attendance and the exhibit floor had more than sixty exhibitors.

I spent most of my time at the conference on the exhibit floor working the MindTouch booth with Patrick (our newest addition–a very competent and pleasant sales dude) and Corey. I have to mention I love demoing our software! I'm not trying to gloat, but when we show people our work we regularly receive unanimous praise from the crowd. Or should I say from the merry mob? We had a lot of traffic. Those who gave us positive feedback included customers of competitors and even a couple competitors who stopped by to see, our enterprise software, MindTouch Deki in action. Every once in a while I spoke with someone who wanted to know if MindTouch Deki could part the Red Sea, end world hunger, or make their ex-spouse love them again all for under $5,000. However in general, folks understood Deki for what it is: a very powerful, highly usable, incredibly affordable collaboration platform that MindTouch has managed to make ridiculously easy to install (15 minutes including download), remarkably easy to use, and it's delivered with a dramatically lower total cost of ownership because Deki automatically updates and patches itself.

I had the distinct pleasure of speaking with some current customers of MindTouch who stopped by our booth too. One had come all the way from Salisbury, North Carolina. The city of Salisbury uses MindTouch Deki for sharing information and team collaboration. I wish I could remember the fellow's name. It was nice chatting with him. I asked him how the software was working out for them and he said: "It's great, we love it!" Sweet! (I said 'sweet' not him). I really enjoy connecting with folks, talking tech, and showing off MindTouch products. MindTouch gets most of our inspiration from feedback we get through in person encounters or by way of our community at OpenGarden.org.  

Unfortunately I only managed to make it to a few sessions. I caught a couple sessions on identity and missed a couple others I would have liked to had made it to. If you read this blog regularly you know I'm keenly interested in an Open Web Initiative (OWI) by which we users could have an extended YADIS or just use XRDS to describe a person's identity; e.g.- OPML file for feeds, and podcasts, URIs to personal resources (Flickr, Jaiku/Twitter, personal and work blog), a URI to a personal Atom repository, a FOAF, etc. This isn't for any commercial interest, but is really spurred by my (and SteveB's) personal interest in having more sophisticated privacy controls and mobility of profile, content, contacts, ect…i.e.- identity. Anyway, it was great to meet the folks who are driving OpenID, The first OpenID talk I attended was Kaliya's (talk here). She's wonderful and fun. She's also a powerful Connector in the OpenID space and an information Maven, which is remarkable because she isn't an engineer. At one point I participated in her talk because the audience didn't seem to understand the significance of OpenID beyond a single sign-on. So, I gave a 60 second monologue (at her invitation) about how it can and almost certainly will enable things like OWI. Later I attended Brian Ellin and David Recordan's talk, which was a rudimentary technical talk about how to implement and consume OpenID. It was useful and well attended. They also passed out a fancy OpenID tools CD

I attended a session on Open Source Business Models for Web 2.0 with John Roberts, Co-Founder and CEO, SugarCRM  and Mårten Mickos, CEO, MySQL AB. I met Mårten previously at OSCON06 along with Monty Widenius (co-founder MySQL) who graciously attended our OpenGarden.org launch party. I asked John a few pointed questions about badgeware during the question/answer section of the session that got him a tad on the defensive. Turns out badgeware is a dirty word to folks with an attribution clause in their software license. One of the questions I asked was: "do you think that if all the components and libraries you use in your stack required similar attribution it would adversely effect your business." I didn't really get an answer from John on this. After the session I spoke briefly with Mårten and tried to pin him down on whether he thought the recent badgeware licenses were good, bad, or otherwise for open source. I also asked him if he thought the recent flood of cash from venture captialists to "open source" companies was going to positively, negatively, or at all effect open source and the software industry as a whole. The VC backed open source companies are primarily the folks spawning new licenses with attribution clauses. Mårten was very diplomatic and unwilling to voice any opinion other than suggesting companies with attribution clauses were trying to prevent closed source competitors from stealing all our portions of their source code. I suggested using a GPL style license would prevent this from happening.

After the crowd of job hunters cleared from around John I spoke with him about badgeware, open source, and OSI. He seemed defensive initially, but as soon as I convinced him I wasn't out to 'get him' and that I was only interested in understanding his position he lightened up considerably and we had a friendly chat for about thirty minutes. He described his point of view and I described mine regarding attribution licenses. John wants to protect his and his team's work. He feels attribution is the right way to do this. I feel attribution is unnecessary and I reiterate my original question, which I never did get a good answer to, what if every open source project required attribution? For example, PHP, Linux, MySQL, etc. How would this impact companies like SugarCRM or MindTouch? It seems ridiculous, but I think it's a valid question. The fact is the forces driving innovation today in technology on the web, you know this thing we call Web2.0, is open source and open standards. Period. Developers can very quickly create compelling applications because there is a wealth of open source components available to us. Also, thanks to open standards you can throw an API or two into the mix and you have something pretty cool. If it's not particularly useful it will likely become a component of something that is useful at a later date. What if all these components had attribution licenses? Even trivial applications would end up looking like NASCAR race cars. I suppose that's not the worst thing in the wor
ld.

John suggested attribution is similar to what open source packagers like RedHat are doing when they bundle software and brand with the RedHat logo. I disagreed because removing RedHat branding is trivial and there is not a licensing requirement that the RedHat logo be present. At least, not to my knowledge. The conversation with John was friendly, but at times I felt like I was talking to Ari Fleishcer because so many of my questions were being deflected or were met with canned responses that didn't quite answer the question and were barely applicable. John was warm to note that the entire SugarCRM application was developed by his team and it's not a fork of something or a repackaging. I'm sure this is true, but it's still using a lot of additional open source components and libraries. There are many people who are passionate about open source who believe John thinks open source is whatever helps him to make money. I told John this and he sincerely informed me that he and his team are engineers who believe in open source and are simply trying to protect their hard work.

The final point I pressed John on was OSI. I think OSI performs a useful service to us as open source developers. They educate the public and attempt to ensure standardization of licensing, which prevents confusion. Also, they're a useful resource and community that can be tapped when people have questions about copyright and software licensing. By SugarCRM not seeking OSI certification of their license they're, in effect, turning their back on what is widely accepted to be the organization that is the keeper of the open source definition. John said he had tried to engage with OSI and had not gotten anywhere. He was interested in participating and claimed that some of the people he had spoken with had unfairly labeled the SugarCRM license as being a rehash of the Berkeley advertising clause (I'm recalling from memory), which personally I don't think is an incorrect assessment. John also posited that OSI is non-inclusive and difficult to work with. Moreover, John asked who are these guys and who voted them into office? How do they vote? Why are they the keepers of open source? Who appointed them? Can I participate? How do I? These are valid questions. Some, but not all are answered by the bylaws and there is an, albeit slow, movement underfoot to create membership, which in my opinion is long overdue. I'm glad to be able to point out the board is now posting their minutes too. The very interesting point John made was that the FSF was being especially helpful and inclusive in approving his attribution license. This surprised me because of the previously linked to article put out by GNU on the Berkeley advertising clause (re-link), which describes a history identical to my aforementioned NASCAR example.

For the record I think John is a good guy who is trying to do what he thinks is right for him, his team of engineers, and his company. Also, I think SugarCRM is a good product worth buying. I'm not sure yet if attribution licenses are bad. I think they're unnecessary. I am suspicious of this new crop of licenses because more licenses means there is more to be confused about. Moreover,  it seems strange to me that an application should be given special concessions that other components required by it are not given. In other words, what makes SugarCRM or one of the other twenty applications with an attribution clause different from the more than dozen open source components they're building on? Should they honor these components and libraries similarly to how they're demanding by prominently displaying all their logos on their application's interface?

The last bit worth covering regarding my attendance at  Web 2.0 Expo is the AllThingsD launch party thrown by Walt Mossberg and Kara Swisher of The Wall Street Journal that Graeme and I attended. It was held at the Mountain View Computer History Museum. There was great food and good drink. Graeme blogs about my driving. Also, the Web2Open party was fun, but I'm afraid I had quite a lot to drink there.

One final note. Ross Mayfield attended Ken's wiki session. If you read my blog you know he had some harsh words for me at the Gilbane conference in San Francisco a month ago. Granted, I've been critical in the past of Socialtext espousing open source. When Ross saw me he came over and shook my hand and said: "Hi, my name is Ross. We got off to a bad start previously. Let's drink a beer some time and chat." That was nice of him. We bumped into each other throughout the event and we were friendly. I had planned to take him up on that beer offer and discuss with him badgeware, to get his opinion as I did John Roberts, and my opinion his company has approached open source incorrectly. However, the fact is his team has helped define open standards, adheres to them, and has helped several other open source projects monetarily and otherwise. Nonetheless, I don't agree with his approach to licensing or that Socialtext claimed for several years to be open source, but didn't release any source code.  

"Adding a Wiki Twist to Business Sites"

Ken Liu
Linux News

MindTouch specializes in providing enterprise wikis. “Wikis are perfect for bottoms-up and ad-hoc cooperations,” said MindTouch CEO Ken Liu. “It is a very viral tool, meaning it is a light word processor inside a Web browser. Using a wiki avoids buying a big application from a vendor. One key aspect is the collaboration feature that allows multiple users to share written information at the same time.”

This is a somewhat belated post. I just realized Ken was interviewed by LinuxInsider.

Posted in MindTouch, Technology. Tags: , , , . Comments Off »

The Cell

SteveB recently installed a distributed computing client on his Playstation3 and earlier today shared this wonderful story with me:

The Folding@Home project…uses software programs to simulate the way proteins change shape – the way they fold – within the human body. Correct folding is necessary for proteins to perform their many functions, such as carrying oxygen from lungs, while misfolding can lead to conditions such as Alzheimer’s.

The complex software simulations… require so much computer time that some segments of research can’t be completed within a graduate student’s years at the university. But when the simulations can be downloaded to a PS3, the speed of the research will be multiplied, depending on how many people participate. Pande expects, for example, to shorten the time for some simulations from a year to two weeks.

“It’s a big deal,” said Pande. “Even starting small, the PS3 means a dramatic increase.”

Here’s one scenario: Sony says there are about 1 million PS3 owners in the United States and Canada. If just 10,000 of them (1 percent) download the simulations and run them to completion, the project estimates it will double the computing help it already gets from personal computers around the globe. – San Jose Mercury News

The client for running Folding@Home was released earlier this week and holy crap!

OS Type Current TFLOPS* Active CPUs Total CPUs
Windows 151 159144 1624849
Mac OS X/PowerPC 7 8713 95337
Mac OS X/Intel 7 2716 7204
Linux 35 24959 215690
GPU 41 697 2185
PLAYSTATION®3 346 14138 15079
Total 587 210367 1960344

Folding@Home Client Stats

Yes, you heard me correctly. It was just released earlier this week! Already PS3′s are providing more than twice the processing power of Windows PCs. How is this possible, you might ask, when there are far less active Sony PS3 CPUs? I won’t claim to know a whole lot about the Cell’s CPU arch, which is what powers the Sony PS3. I haven’t taken the time to read up on it, but I have a basic understanding after a quick read. The Cell is really designed to allow CPUs to federate to work cooperatively and share processing, it’s all about distributing processing. Partially this is achieved by processing being sent to hardware cells in the form of software cells that consist of data and programs (known as jobs or apulets). The processing is completed without caching. In the case of the PS3 the Cell consists of a PowerPC chip, which plays the role of the Power Processor Element (PPE) a kind of master CPU and eight Synergistic Processor Elements (SPE) that act as slave processors. Each SPE has a 256 Kbyte “local stores”. These are like are like cache because they are on-chip memory, but behave more like CPU registers. The local stores access main memory in blocks of 1Kb minimum (16Kb maximum), but the SPEs can only operate on local stores and not directly on main memory. This approach is a means of minimizing contention and complexity in order to facilitate distribution of processing and scaling (adding more "cells"). As usual, everything old is new again. A similar architecture was employed with the Cray 2 in 1985, what’s new is 21 years of Moore’s law and how bloody cheap chips are now.

The Cell will almost certainly find its way into a variety of devices, such as PDAs and other consumer goods. Imagine for a moment what this means. We’ll be able to create very powerful distributed computing arrays. My PDA will be capable of supercomputing processing power by distributing. Also think about what the PS3 is going to do for number crunching with projects like Folding@Home. Very, very cool stuff. This is going to dramatically change things. It is important to note that programming to a system that employs an architecture like the Cell is pretty hard. We need an abstraction to improve this. This is actually what I was recruited to help work on at Microsoft back in 2003 when I met SteveB. I surely don’t claim to be an adept on this topic, but SteveB surely is.

Wik.is and more…

I thought I should point out that migrating Wiki.com to Wik.is, which has been a monumental undertaking given the number of users and very short notice, isn’t the only thing MindTouch has been up to recently. Take a look at the new web site. And dig the launch of a new product, MindTouch Deki. It’s just coming out of closed beta. It’s very slick and free for the first 5 users. It installs on Windows or Linux in minutes. And as one enthusiastic beta user who leaked a few days ago pointed out: you can carry it with you on a USB memory key if you like. It’s so easy my mom could deploy it. :-) Pretty damn cool if I don’t say so myself.

Posted in Journal, Technology. Tags: . Comments Off »