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

Meet Roy Kim

Cross Post
Roy Kim

The photo you see to the right is Roy Kim. I just finished reading a blog post at Roy's personal blog about DekiWiki, the Hayes release, and the future of our user interface. Read Roy's post. Initially I only planned to mention his post here for all interested Gardeners to read, but then I got to thinking maybe I should give you all a little background on Roy. Roy can be the MindTouch highlighted developer this month! :-)

Roy was MindTouch's first hire. He joined MindTouch in January, 2005 when we were just starting as a company. I met Roy virtually through mutual friends at UNC and it wasn't until more than six months later that Steve and I met Roy in meat space. Roy graduated with a degree in Chemistry and Economics from UNC and three friends of mine that I knew from the Computer Science program at UNC knew Roy from High School. Roy recently moved to San Diego when we merged our offices here. Roy is the author of Tabulas and several other interesting online tools. Tabulas is a very nice blogging community that boasts more than 100,000 blogs and a rapidly growing community. The odd thing about Roy's right-brained education is that he is quite a good designer. His designs are thoughtful and simple…kind of like him. ;-) Roy helps with design (feature and otherwise) and lives mostly in PHP. For more information on Roy subscribe to his blog.

UPDATE:
Roy Kim

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.  

Alfresco Opens, What's Open?

Matt Asay.Weblogs.Infoworld

Alfresco just released their source under GPL with a FLOSS exception.

This move is about choice, in other words. Choice for our customers (Freedom of access to the world’s best content management system). Choice for our partners. Choice for our competitors (join us or get run over :-) . Choice for the community.

…The GPL is open source’s best business license. It is open source capitalism – the free market at its finest.

Freedom pays great dividends.

…the proprietary software companies we compete with have a limited shelf life. :-)

Welcome Alfresco and kudos. Enough of this non-OSI-approved modified MPL bullshit. If your license is not approved by OSI then you’re not open source. Real simple. Worse yet you have companies like Socialtext. I think I’ve remained silent about these guys too long. Socialtext has claimed to be open source and fervently waved this banner since their founding in 2002. However, they didn’t release a stitch of source code until July, 2006. Four years later. WTF? When they did release their source they did so under a non-OSI-approved modified MPL license. WTF? Most recently Mayfield suggested that because they’ve allegedly "supported Kwiki for years" this makes Socialtext open source. I’ve been using Kwiki at every O’Reilly event (I love O’Reilly) and to the best of my knowledge Kwiki hasn’t changed in three years! I’ve kept my mouth shut because they’re competitors and I assumed others would have cried foul over their behavior long ago. Oddly, no one has. Then a few months ago (around Thanksgiving 2006) murmuring started about attribution licenses, which really is of lesser concern as far as Socialtext is concerned. Berlind blogged about how he can see it either way blah blah. In the end he called for "disclosure" as to whether the license is OSI approved or not. If you’re not, you’re not open source! What’s there to disclose? I responded here. Shortly thereafter Berlind sent me an email titled: "Laughable." It may have been a tad condescending, but in general he stated that disclosure is a good thing he didn’t see how anyone could disagree. Sure, I was a tad harsh, but I didn’t get the impression he was saying anything of use and I was also a tad offended by his statement: "the supposed keeper of the official definition of ‘open source’ and the consortium to which open source license authors typically turn to have their licenses ratified as adhering to that definition". Supposed? Typically turn? Read his post, read my response, you be the judge. As a side note, isn’t Berlind on the advisory board for Socialtext? I know one of those ZDNet blogger dudes is and I thought it was him. I’m not certain. UPDATE: I don’t think it’s Berlind, but I know there is a ZDNet journalist/blogger guy who is on Socialtext’s advisory board. Update’: My bad, it’s Mitch Ratcliffe.

Nat Torkington while organizing OSCON (which I love and is where we launched www.opengarden.org, OSCON06) recently asked: "Is ‘Open Source’ Now Completely Meaningless?" Well, if we continue down this road I don’t see how it couldn’t become meaningless. By the way Nat, I don’t think you should make a hard and fast rule as to whether you should disallow closed source companies to participate in OSCON. Do it on a case by case basis because surely there will be some worthy exceptions. Anyway, back on subject. What I propose is that OSI manages a wall of shame for companies that behave inappropriately with respect to use of the term "open source". It could work something like this. 1). The accused company receives a public warning via email and it’s also published online (posted on a wiki perhaps). Along with the warming the company is asked to cease their inappropriate use of the term open source and provided clear steps for complying with OSI. 2). The accused follows the steps for compliance in the provided timframe or they receive public censure, which starts with a public admonishment of their actions and could be escalated. All this is archived (hence the wiki suggestion) and indexed. Perhaps OSI could work with SourceForge.net and other sites to create a coalition that could perfrom the censure.

Why is this better than the current process? Well right now it’s very ad hoc. Only geeks know what’s going on because we’re the only ones willing to participate in a rabid discussion list. Ultimately OSI has no stick to wield and everything is pretty quiet outside geek circles. Even within geeky circles people are confused and it’s unclear if someone is violating the will of OSI. Also, this way when someone performs a web search for the aformentioned accused company the warning and censure would be found in the search result set. Thus providing a monetary incentive for compliance with OSI’s will. I very recently emailed these thoughts (mostly) to Tiemann. UPDATE: Michael and I spoke. I talk about it in this blog post. Something needs to be corrected though because this is a growing trend that seems to be spurred on by the flood of cash resulting from the venture capitalists’ interest in open source. And to compound the problem you have very media savvy folks with deep deep pockets that are very clearly manipulating public perception by injecting their will into journalism (mostly bloggers).

Anyway, enough soap-boxing. Back to Alfresco. What’s the intent of the Alfresco FLOSS exception (also employed by MySQL and others)? It’s meant, as far as I can tell, to maximize freedom in extending and integrating with dissimilarly licensed FLOSS software. Meaning, whatever you extend or integrate can continue to maintain it’s own licensing as long as it’s OSI approved (or on a list of OSI approved licenses that Alfresco provides). We achieved the same end result at MindTouch by providing DREAM under LGPL. DREAM is our Distributed REST Application Manager and what we’re building MindTouch DekiWiki on top of. In fact, we’re slowly discarding MediaWiki PHP logic for C# on Mono/Net 2.0 in the form of DREAM services. And as you would imagine DREAM is also powering our API. It will should be technically feasible that ultimately one could install just a PHP layer on their shared server and have a very sophisticated Service Oriented Distributed Architecture (SODA) powered by DREAM providing all the business logic. Think about that for a moment. It has huge benefits and enormous ramifications. Anyway enough about us. Is this FLOSS exception OSI approved? I saw one reference to it being an OSI approved exception, but I really don’t know if it is. It’s exception is only for other OSI approved licenses, it’s got to be.

Big Blue backs PHP for Web development

CNET News.com

IBM is putting its corporate heft behind a popular open-source Web development technology called PHP, in a move meant to reach out to a broader set of developers.

On Friday, the tech giant is expected to announce a partnership with Zend Technologies to create a bundle called ZendCore, which includes IBM’s Cloudscape-embedded database and Zend’s PHP development tools. Zend sells tools built on the open-source edition of PHP and offers related services.

IBM also plans to establish an area dedicated to PHP on its developer Web site, which will include technical resources such as white papers.