Alex Barnett blog : community

The Great Bungee Jump

alexbarnett — Thu, 28 Aug 2008 00:21:00 GMT

Well, the great Bungee Jump has come. Martin Plaehn, CEO of Bungee Labs has shared the news of the company the letting go of 15 regular employees and contractors. Unfortunately, I am among this set of affected Bungee Labs employees.

A Voyage of Discovery

As Martin explained in today's post, Bungee Labs has been on a voyage of discovery. There are many lessons for me and the company to take away from the whole experience of the last year or so, but the bottom line is that we were overly optimistic about what it takes to achieve the rate and scale of developer adoption - real traction - and therefore the development of killer apps by the developer community that would drive the platform and the business forward at the velocity that makes a VC-backed venture "interesting".

So where does Bungee Labs go from here? Well, I think Martin eluded to the key clue:

"Over the next several months, Bungee Labs will lay out the course for a business object solution framework for user configurable enterprise-class applications that demonstrate these principles"

It'll be very interesting to see how this manifests and the impetus it will provide to the platform's adoption.

No Regrets

No regrets, none at all. When I considered the opportunity of joining Bungee Labs (and by doing so leave a relatively safe harbor in order to do so) I knew of the risks involved. Bungee Labs' mission was - and still is - of the kind that aims to "change the world". To have been a member of the team tasked with realizing the company's hugely ambitious mission has been nothing short of an entirely worthwhile and educational pursuit.

In my mind at least, Bungee Labs has made its mark in the brave new world of cloud computing. It has opened the eyes to many in the industry about what might be and can be. It has made cloudy ideas and visions more concrete and helped to define the concepts a (Platform as a Service, or PaaS) and memes that are contributing to the next generation of cloud computing platforms.

I've learned a great deal in the past 16 months working closely with a very talented, smart and creative set of teammates. And although it is probably unfair to call out individuals - for it implies those not mentioned weren't of similar caliber (which is not the case) - I do want to thank Martin Plaehn, Bungee Labs' CEO in particular for his mentorship during my tenure at Bungee Labs' and from whom I've learned an enormous amount management and leadership. I'll also miss the inane banter with Ted in those podcasts we put together (and the "Shushee" lunches).

What Next?

And so...on to my next adventure. What will that be exactly? Frankly, I have no idea yet...but whatever it is, I need to know I'll be trying to change the world :-)

I'm open to ideas...so if you have some, please get in touch.

Open Source in a SaaS World

alexbarnett — Fri, 16 May 2008 03:01:00 GMT

About a year ago, I took part in a meeting where the question: "What does open source "mean" in a SaaS world?" came up in conversation.

A year later, that same question is becoming increasingly pertinent as the IT industry's move to Software-as-a-Service (SaaS) and cloud-based computing accelerates.

For Bungee Labs (I work there), where

we provide an entire platform-as-a-service (PaaS)
developers create, share and re-use code and deploy apps in the cloud
developers "consume" and program against third party web apis and will create their own

...the "meaning" of FOSS is central within these different contexts and has many possible answers with many non-trivial implications...Three dimensional chess as it were.

(pic source: Memory Alpha, the Star Trek wiki)

For this post, I want to share some of the considerations relating to # 1) above: the context of open sourcing Bungee Labs' own system (Bungee Connect). Last month we stated that:

"Bungee Labs is evaluating several Free and Open Source Software (FOSS) licenses for the software components that comprise the complete Bungee Connect system. However, the task of reviewing the various FOSS licenses, and then identifying which of them best aligns with the software components and subsystems created by Bungee Labs–as well as ensuring compatibility with third-party components upon which Bungee Connect relies–requires considerable review and source code preparation. And we want to do this right, with the community’s involvement."

Since and before that announcement, Ted Haeger (who runs the Bungee Connect Developer Network) has been discussing some of the issues at hand and some of the options we see before us with some very "FOSS savvy" communities at events such as Socal Linux Expo, LugRadio Live USA and LinuxFest Northwest and of course with Bungee Connect's own growing developer community.

Today there's an interesting conversation going on between Ted and Simon Wardley, ex-COO of Zimki / Fotago who resigned last year over the company's decision not to open source their platform (the video of his announcement at a OSCON 2007 talk he gave "Commoditisation of IT and What the Future Holds" makes for entertaining and informative viewing all of its own...Simon discusses open source in a SaaS context. Update: Simon let me know of this video which also includes the slides

Anyway, back to the thread:

Simon wrote a post this morning providing his thoughts on the some the FOSS options available to Bungee Labs
Ted wrote back responding to Simon sharing his point of view
Then Simon responded to Ted

All three posts (and more to come no doubt) make an informative and interesting read, but I want to highlight one of the key issues in discussion.

The SaaS Loophole

The issue goes back to the question: "What does open source "mean" in a SaaS world?" and specifically the licensing issues. I'm going to quote and edit from Ted's post somewhat liberally (Ted owes me a Sushi, so we're quits now :P ) and isolate an (if not "the") open source licensing issue in the context of SaaS (my emphasis):

"Personally, I think that GPLv3 is the wrong license for freeing any SaaS or PaaS offering. The Free Software Foundation has a better license for this purpose.

GPLv3 is inadequate because it does not mandate that modifications that others make be opened. Originally, GPLv3 was planned to close up the “SaaS Loophole” (a.k.a. the “ASP Loophole”) in GPLv2. However, as I understand it, several large companies pressured the FSF to remove the key clause that would have closed the loophole.

What is the loophole? It’s this: if you take free software and offer it as a hosted service, then you are not conveying the software, and are therefore not obligated to reciprocate your modifications to the original code. In the context of service providers, GPLv3 is effectively the same as the BSD license. Many companies, Google among them, live inside this loophole. (For now, Bungee Labs is also in that camp.) Some remain there deliberately. Others are in it simply as a matter of course…that is, where they are in their business development process."

So that's the "SaaS loophole". Where's the loophole now? Ted explains:

"Perhaps the argument could have been made in the age of GPLv2 that the SaaS Loophole was an oversight, but now that GPLv3 has the loophole by design, it’s really no longer a loophole. The latest version of the license supports the practice. (And just to be clear, I am not advocating this for Bungee Connect.)

...Say Bungee Labs opens Bungee Connect under GPLv3. Is there a danger that small companies could replicate our offering? I don’t think that’s the case. But could a well-funded company do the same, fork the code, and then fund an engineering team to outpace the original inventors?

...The Free Software Foundation also provides the GNU Affero General Public License version 3, or AGPLv3. AGPLv3 specifically closes the SaaS loophole. Instead of being triggered by conveying the software, AGPLv3 is triggered by accessing the service. This helps to reduce the risk that a company could not branch the code and then out-engineer the originators, as the vulture company would be obligated to share-alike terms with their derivations."

So, is the AGPLv3 the right license for Bungee Labs to pursue? Is it the right license for SaaS providers? Is it enough on its own? (back to Simon Wardley's point in his post). Each company has their own unique circumstances and they each need to think through the 3D chess game. We're still working it out at Bungee Labs.

For us at least, I think some of the potential answers are becoming clearer, and others not yet. But it is the kinds of discussions that Ted is having with Simon that are a critical part of Bungee Labs' decision making process around FOSS. It cannot be an insular process.

Designing Web APIs - Twitter Learnings

alexbarnett — Thu, 01 May 2008 11:08:00 GMT

Although I made it to Web 2.0 Expo in San Francisco last week, I didn't make it to a session Matt McAlister blogged about by Twitter’s Alex Payne and Michael Migurski of Stamen Design who presented learnings from the perspective of an API provider.

But I can see the slide deck discussing the Twitter API and so can you:

| View | Upload your own

More Web 2.0 session slides available here. Recommended:

Videos of sessions here. Check out Clay Shirky's session, author of Here Comes Everybody: The Power of Organizing Without Organizations (a good read btw).

Time to Define "Platform as a Service" (or PaaS)

alexbarnett — Tue, 19 Feb 2008 09:27:00 GMT

Before joining Bungee Labs last year, I knew they were on to something big. I mean, really big.

A big idea, an ambitious vision: to provide developers with end-to-end development, testing, deployment and hosting of sophisticated web applications as a service delivered purely in the cloud.

Since we announced our private beta back in May 2007, we've had over 1,500 developers sign up. In January alone we had over 400 developers kicking the tires - not just signing up and disappearing, but 400 returning developers, learning, building and deploying out increasingly sophisticated apps on a fast evolving developer platform, requiring no install of anything on their machine - all through the browser.

And since May 2007, the trend to delivering software as a service (SaaS) has been moving at terrific pace. New web APIs are being made available every month and new announcements by start-ups as well established big players are reinforcing and fueling the acceleration to the inevitable world of cloud computing.

As we announce our move from private to public beta today, we've also tried to articulate the new category of product and service we believe Bungee Connect is at the forefront of defining, the category of Platform as a Service, or PaaS, and our big bet is that PaaS is the next big thing.

So what is a "Platform as a Service"?

In September 2006, Marc Andreessen posted his thought provoking "The three kinds of platforms you meet on the Internet" and it got a fair level attention from the web industry. And we took note. We thought what Marc was describing in his Level 3 definition where:

"A Level 3 platform's apps run inside the platform itself -- the platform provides the "runtime environment" within which the app's code runs.",

...was right, but only partly right. Given Bungee Labs' ambition and vision, we felt there was a lot more to Marc's definition of the highest level definition of an "internet platform", a definition more holistic and comprehensive than a runtime.

But we kept focused, kept working on what we were hearing our developers telling us we needed to fix and improve on Bungee Connect, to give what developers are telling us what they really want - a Platform as a Service - to provide everything required in the lifecycle for the development through hosting of full-on, sophisticated and highly interactive web apps, not just widgets.

As we were readying for our next phase -our public beta - we thought it would be a good time to put a stake in the ground and actually define what we mean when we use the term Platform-as-a-service, and thereby describe the comprehensiveness what Bungee Connect has to offer.

So early this morning, our CTO and Founder of Bungee Labs, Dave Mitchell posted a definition describing PaaS in concrete terms.

What follows is a summary of Dave's post, with a selection of my favorite "soundbites" and ideas, but I suggest you read the whole post for yourself - there's a fair amount to consider:

1) Develop, Test, Deploy, Host and Maintain on the Same Integrated Environment.

"It’s time to stop developing “here” and running “there”. Today, most applications are coded in one environment (usually custom-built for that project by a developer), then tested in another, and redeployed to yet another for production...In a completely-realized PaaS, the entire software lifecycle is supported on the same computing environment, dramatically reducing costs of development and maintenance, time-to-market and project risk. A PaaS should let developers spend their time creating great software, rather than building environments and wrestling with configurations just to make their applications run — let alone testing, tuning and debugging them...Also, an end-to-end PaaS should provide a high productivity Integrated Development Environment (IDE) running on the actual target delivery platform, so that debugging and test scenarios run in the same environment as production deployment.

2) User Experience Without Compromise

"A Platform-as-a-Service must deliver compelling user experiences, with all the richness and live interactivity that consumers have been conditioned to expect....Hiccups like software downloads or plug-in installations, browser dependencies and inconsistencies, or local executables break the web model, and are inherently less secure, less maintainable and less user-friendly. In order to be relevant and popular, PaaS must deliver the best user experience available on the web, comparable to or better than conventional approaches.

3) Built-in Scalability, Reliability, and Security

"Developers should be free to build applications with the comfort that the security of customer data, network traffic, source code (intellectual property) and even server hardware is maintained automatically by the platform through-out application development and delivery."

4) Built-in Integration with Web Services and Databases.

"Applications need to leverage existing software investments in databases, and internal or external third party web services, requiring that the platform offer a wide variety of connectivity options."

5) Support Collaboration

"A PaaS must support both formal and on-demand collaboration throughout the entire software lifecycle (development, testing, documentation and operations), while maintaining security of source code and associated intellectual property."

6) Deep Application Instrumentation

"With instrumentation, organizations can see exactly how users are using the application, the type of performance they are experiencing and any application crashes. This information can also be leveraged to create new business models where costs are tied to actual utilities, rather than flat-rate subscriptions or licenses."

Over the next couple of years we expect to be hearing a lot more about PaaS and how "Y announcement" by "X company" is now providing true a PaaS offering to businesses and developers.

But saying you are providing a Platform as a Service has to mean something, and we think the above definition sets a high but reasonable standard that must be met for any company to claim they are providing a "platform-as-a-service' and legitimately describe themselves as a PaaS player.

The amazing thing is, for me at least, is that Bungee Connect is delivering all of the above, today. From our point of view, delivering PaaS - the real deal - is not statement of Bungee's intent, it's a statement of fact. It's bold, but so is our vision. Yes, we've still a lot to do before we're commercially ready and we think that's coming soon, but so much is already there. Try it out.

Geek Juice

alexbarnett — Wed, 30 Jan 2008 04:36:00 GMT

Yup, I've definitely been missing my feedreader (and now FeedDemon is free I really have no excuses to catch up).

So much good stuff out there, so little time! Here's a sample of the good stuff I've been running into...

MVC, I know what you're thinking...

Haacked shares his MVC joke - "So A Model, A View, and a Controller Walk Into a Bar"...ok, so that's a bad start.

Less of a joke though, more the future...I think therefore I click - Microsoft's investigation into the subconscious, studying thought patterns as part of battle against Apple, Google:

"When a Microsoft Corp. patent application for a method of sorting brain waves surfaced late last year, it drew quips that the company now plans to read PC users' minds, in addition to selling them software."

But that's a while off. I think.

Build it!

In the meantime, back to some semi-reality - here's a good Facebook app primer on How To Build A Facebook Application...and now you can add your own very own virtual realty into Virtual Earth: 3D Models in Mashups. Customize your own Virtual World on your website!

"In this release we added the ability to load custom 3D models as part of a Collection right in your own web applications"

Ship It!

Skyfire has emerged from stealth mode, this video shows the Skyfire mobile browser enabling Flash video through server-side rendering

"While the mobile phone industry scrambles to adopt faster graphics platforms for rendering video, a startup may have bypassed everyone with an approach so simple, you wonder why nobody tried it already"

It looks pretty slick and could well...It just needs to ship! Something else that needs shipping, and pronto...The World Wide Web Consortium releases draft of HTML 5:

"In its final form by 2010, HTML 5 is intended to bring the markup language forward into today's richer Internet environments, with new application programming interfaces to control audio and 2D video content."

And along the shipping theme, Tommy Williams of Microsoft's Data Programmability team describes how he takes a finished software product and gets it up on the Web for people to download.

Trends ~~It!~~

Here's a comment left by a Brian Campbell re: Tim Bray's 2008 Prediction 1: RIA vs. AJAX post.

"Well, one of the big trends is actually getting AJAX to be able to do what the RIA platforms can."

Yup. Lots more to do here.

And what consumer trends to we expect this year? How about the Expectation Economy? I read this, liked it, but thought: Isn't this really describing the experience economy?

A personal trend for me...How about enjoying the NJOY Electronic Cigarette. My wife got me one of these. I haven't got the balls to try this publicly yet...but my time may come.

And this year, how are devs really going make money with Web 2.0? I agree with Phil Wainewright's prediction:

"a groundswell of smart developers are going to use DevPay to make money under the radar screen"

Useful

Subscribed to Steve Gillmor's podcasting series - The Gang » Audio. It includes a fair amount of stuff I'm not really into, but some very good stuff that's right up my street. Just got to be selective about which episodes I'll listen to.

I liked this tool, FlickrDown - download and save your Flickr pics to your hard drive - pics by username, tags or group. Windows only. Sorry! Maybe Mac support in a future release?

Letting your customers know where you're going with your product, what criteria you're using to float some features / improvements to the top of your roadmap is obviously important when you're dealing with developer customer base.

But that's easier said than done. It's a balancing act - on the one hand you don't want to risk over-promising and under-delivering (in fact, you want the opposite) and yet you want provide the best level of visibility you can, so I liked how Ning is carefully introducing its future roadmap to customers in this post - January Product Roadmap - What's Next.

Defining Community

Having clearly defined and agreed term is generally a useful thing (Web 2.0 anyone?)...it gets us all on the same page when we're trying to figure stuff out together. Bob Rebholz of Microsoft's Community team is doing his bit to define the "Community" bit in Social system design part 1: defining terms

"Defining community should be easy right? And it is, sort of."

Podcast interviews - smart people in the world of the web

alexbarnett — Sun, 20 Jan 2008 15:41:00 GMT

One of the fun parts of my job at Bungee Labs is to partner up with Ted and interview some smart people in the world of the web. We publish these as a podcast series (the Bungee Line - podcast feed here) over on the BCDN blog.

If you have ideas about someone you think we should interview, let me know! We're focusing on topics we think web developers might be interested in the worlds of software as a service and web app development, in particular profiling web apis. Related topics are good too.

I've listed out below our most recent podcasts below...plenty more in the works (previous podcasts are listed here). Hope you like :-)

Alan Lewis on eBay Desktop and eBay APIs

"As product manager for eBay Desktop, Alan Lewis relies on the same web APIs that eBay makes available to all developers. In this edition of the Bungee Line, Alan tells us about what the eBay Desktop is, how it came about, and various details about eBay’s developer program and web APIs. We ask Alan about eBay’s position Oauth and on open source."

Toby Segaran on “Programming Collective Intelligence”

"Since the publication of his O’Reilly book Programming Collective Intelligence: Building Smart Web 2.0 Applications, Toby Segaran has become well noted for his ability to explain easily-understandable algorithms for the kind of deeply complex problems involved in social applications. Toby joins Alex and Ted to discuss some of the high-level concepts that he tackles in his book."

Jon Aizen of Dapper.net

"Jon Aizen joins Alex and Ted to explain how Dapper.net provides a no-fee tool for making almost any structured web site data accessible via a REST API. In a past life, Jon was involved in creating The Internet Archive. Jon also helps the Bungee Line introduce romantic intrigue into the podcast.

Punditry Alert! At the end of this show, Ted and Alex speculate a bit about Android, Google’s open source mobile device platform, the Apache License, and whether Robert Love is involved. Please consider this as another demonstration of Ted’s idiocy, brought to you by the Bungee Line."

Jeff Barr on Amazon Web Services (Part 2)

"In part 2 of our interview with Amazon Web Services evangelist Jeff Barr, Alex and Ted ask Jeff about Flexible Payment Service, virtual user group meetings in Second Life, the Startup Project, and pry at Jeff’s views of possible futures of technologies that developers might anticipate."

Jeff Barr on Amazon Web Services (Part 1)

"Developer evangelist for Amazon Web Services, Jeff Barr tells Alex and Ted about how he became a native Amazonian, his recent visit to “The Business of API’s Conference,” and a bunch of stuff on Amazon Web Services, including: Mechanical Turk, EC2, and S3. Additionally, Jeff explains the newly announced S3 Service Level Agreement*."

Microsoft missing out on Community talents

alexbarnett — Thu, 30 Aug 2007 12:58:00 GMT

Todd Bishop at Seattle Post-Intelligencer has picked up on the fact that Korby Parnell, ex-product manager for some of Microsoft's most successful developer community-related projects (e.g. Codeplex, Gotdotnet and Claimspace - but that's another story) has been nabbed by Yahoo's Seattle office (Chad Dickerson's team, who runs the Yahoo Developer Network).

Korby, a good friend and neighbour while I was living in Redmond, WA, didn't make a public song and dance of the move, but when he told me he was on his way I realized Microsoft had lost out on an amazing talent.

Microsoft has recently lost two other good community-oriented people: Josh Ledgard left Visual Studio's product team to join software dev company Telligent - developers of Community Server - in July 2007. Josh was closely involved in the development of the innovative MSDN Product Feedback Center, now Connect. Then Joe Morel left the same VS team to join the same software company two weeks later.

Microsoft has done a great job in recent years to foster a more open and transparent culture with respect to customer engagement and Korby and Josh were there at the beginning of the Microsoft blogging revolution and other community-related initiatives, really challenging the notions of old-style centralized command-and-control corporate communication. It's a shame to see this quality of talent walk out of the Redmond campus, true customer advocates - people with a real passion for customers and their needs.

I wish Korby, Josh and Joe the best of luck in their new adventures!

Update 9/2/07:

An anonymous reader has tipped me off on yet another leaver. Sandy Khaund, another big force in Microsoft's community development, has announced he's off to join a start up. Good luck Sandy!

The Web Standards Fluster Cuck

alexbarnett — Tue, 14 Aug 2007 00:58:00 GMT

Clucking bell, Molly Holzshlag really has kicked the web standards beehive with a blog post expressing her great discontent with the W3C and WaSP.

Ridiculously Inadequate Backgrounder

Now, before you head off and read the post and the 60+ comments, here's a bit of background on why I find this post of interest (and rather depressing):

I've been following Molly's work for a while now. She first came on to my radar when after providing an update on the progress made between the Microsoft IE, VS and .NET teams and the Web Standards Project (WaSP). That was in 2005. Then in January 2007, I noted Molly's announcement that she had left WASP to join the IE team on a contract basis to work on standards and interoperability issues. I was pleased to see the IE team was making a real effort.

Entirely seperately, but not entirely, in October of 2006 Tim Berners-Lee called for the reinvention of HTML. His call to action caused a bit of a hoo-ha at the time. What's that got to do with Molly? Well, as noted, some of the reactions to TBL's post varied from skepticism, to 'About time!' - and here's the connection with Molly's latest post - to what role the WHATWG will play in what presumably could be a competing effort to the HTML 5 (or XHTML5) spec in progress at the time. However, I was pleased to hear TBL's public calling for progress and hoped we might see some of this progrss after HTML's 8-year stagnation. Then in July 2007, we had the news that HTML5 was being considered by the W3C.

Confused? You should be.

So after my ridiculously inadequate backgrounder, you can now go ahead and read Molly's post, along with the contributions be the cast of characters (the commenters), some of whom are affiliated with various competing factions wrestling with the future of web standards and HTML, who somehow manage to converge the various threads (now including a Fear of Air, the Semantic Web, microformats, Silverlight, XML, community, accessibility, transparency and who-knows-what-else) into what looks like a complete political mess (read: fluster cuck).

Yes, it is depressing,, but such is the business of web standards agreement. A messy business indeed...There's even a YouTube video covering the drama - HTML5 trailer - Find your Hero.

Thanks to Thomas Vander Wal for the link to Molly's post.

Back from a short blogging break

alexbarnett — Sat, 23 Jun 2007 13:11:00 GMT

Sorry for my recent silence on the blog - a combination of lots of travel (tomorrow will be my second full weekend in Utah since moving here three months ago) and the usual start-up madness has caused a need for an occasional (and healthy) break from blogging.

Matt Asay's post has motivated me to push one short blog post of my own where he shared thoughts after the first day of a two-day Advisory Group session we're having here at Bungee Labs. Matt pointed out this blog post by eBay's Curtis Gavin where Curtis describes how we meet up with some members of the eBay web services team at the eBay Developer Conference a couple of weeks ago:

"A fun thing happened while I and a couple colleagues were waiting for our next blogging/video taping gig. We stopped by the BungeeLabs booth to check out their web-based on-demand development environment, Bungee Connect. We heard it was cool, so wanted to see what it was all about.

...My colleagues and I suggested they try our new eBay Shopping Web Services. The smaller WSDL and faster, more responsive APIs seemed like a good fit for demo'ing. They were up for the challenge.

...Start to finish, this all took less than 20 minutes. Not bad for working with a new API. And, as Brad pointed out, we never left the web browser!"

It turns out we were the first non-eBayers to try to develop a sample app using the newly launched eBay Shopping Web Services WSDL - and Brad Hintze (our marketing manager) did this in a snap - most of the 20 minutes involved locating the correct URL.

Well there you have it...Nothing earth-shattering I know. My first blog post after a break is always hard work...a kind of "blogger's-block" sets in - the longer I wait, the harder I find it to break the silence...believe it or not I actually get nervous when writing my first blog post after a break...weird. Hopefully I can get back to blogging regularly now.

Update - noticed another post by Matt discussing a point that came up during our Advisory Group session yesterday:

"Cornelius said something that I found brilliant. In terms of developing community, Cornelius suggested that

You have the make the community visible to itself.

In other words, a developer is much more likely to stay with a community if she actually feels like she's not alone.

...One of the primary factors in a community's staying power is the ability of the participants to actually participate meaningfully with others in that community. This seems obvious, but it's surprising at how few companies actually get this right. Most "communities" bowl alone. You go into a project's forum to consume an application or information, and then you leave to go do your real work. For a community to succeed, the "real work" needs to happen on-site, in the community. It's not something you access and then leave to be productive. The productivity has to come while in the midst of the community."

The "Cornelius" mentioned is Cornelius Willis, Microsoft's first Director of Platform Marketing (in the mid-90's) and more recently VP SourceLabs. Cornelius is one of 6 (including Matt) hugely experienced advisors we're lucky enough to have access to as we navigate this early phase of Bungee Lab's public life.

Ted, Korby, Claimspace and trust

alexbarnett — Wed, 23 May 2007 20:55:00 GMT

Korby Parnell, Ted and I me met up and talked about Claimspace.

This is what Ted thought...here's a taster:

"From what Korby showed me, over time Claimspace could solve many of the needs that Alex and I have identified for Bungee Lab’s community infrastructure. In fact, according to Korby, community managers and planners like Alex and me are exactly one of the personas that Claimspace intends to serve. There is just one problem.

It comes from Microsoft."

The Future of Mozilla Matters

alexbarnett — Fri, 11 May 2007 11:20:00 GMT

What does a microformat-aware web browser look like? Richard MacManus has some of the answers, summarizing this presentation made by Alex Faaborg at the Web 2.0 Expo event a couple of weeks back. Cool, eh?

Interesting, but this use of microformats in the browser is only a small fraction of the overall story in the future of the 'interesting' web. The web's possibilities, the web's multiple possible futures and the role the browser has to play in the future of the dynamic web moving forward isn't entirely clear today (the web's future is always somewhat hazy - it's what makes it interesting). There are many paths we could go down, some better than others.

To this point, Richard also points to Chris Messina's vlog post, where Chris shares his thoughts and concerns regarding Mozilla's future, in particular proprietary web tech trends / stacks such as Silverlight, Apollo and the more recently announced JavaFX by Sun - each offering is essentially acting as an alternative to AJAX.

Chris also discusses Mozilla the platform and not Mozilla the browser (see Ryan Stewart's reaction here and Anne Zalenka's thoughts here on this topic), XUL in Mozilla, the spreadfirefox effort, HTML5, Mozilla as a platform (again), the civicforge idea, XForms, HTML5 (again), XHTML2.0, microformats and Mozilla's leadership role with these technologies amongst the web dev community, IE's progress, mobile browsers - minimo vs. webkit, openid and more.

The video provides a great insight into how a key Mozilla community member sees the future of Mozilla as a ~~product~~ platform and the role Mozilla has to play in defining the future of the web. It is also a fairly frank assessment of Mozilla's progress and role the Mozilla community has in its future. Thanks for recording and sharing this Chris, I learnt a lot here.

Map of online communities and related points of interest

alexbarnett — Mon, 07 May 2007 03:45:00 GMT

Map of online communities and related points of interest.

(Geopgraphic area represents estimated size of membership. Do not use for navigation)

Via apophenia.

Announcing Bungee Connect

alexbarnett — Mon, 16 Apr 2007 07:11:00 GMT

At last, I can tell you more about what Bungee Labs has been up to...

We've just announced details about Bungee Connect, a 100% on-demand web development and deployment environment that will be going into Beta phase in May.

Over the next three days at the Web 2.0 Expo 2007 and on bungeeconnect.com we'll be providing a lot more detail on exactly what Bungee Connect is, how it works and why we think it will be a big deal when we go live.

So before I go on, let me quote a couple of people who have already seen Bungee Connect in action behind closed doors. The following are from tonight's two press releases (1 and 2)

First off, Dion Hinchcliffe:

“Ajax is just the beginning of the RIA story and Bungee Labs provides the rest of the solution with a web-based IDE, on-demand scalable deployment, a well-designed community model and a built-in component ecosystem with real-world licensing options,” said Dion Hinchcliffe, ZDNet blogger; President/CTO, Hinchcliffe & Co.; and editor in chief, AjaxWorld Magazine. “Bungee Connect is a surprisingly complete one-stop shop for the RIA development, deployment and operations lifecycle.”

Next, Dana Gardner:

“Given the current disjointed state of tools, testing and deployment models, most developers find creating rich internet applications (RIAs) to be complex, time-consuming and expensive,” said Dana Gardner, Principal Analyst, Interarbor Solutions. “By combining development, testing and deployment functions into an integrated, low-cost-of-entry service approach, Bungee Connect both broadens the numbers of developers that can produce web applications as well as slashes the barriers of entry for creating innovative ecommerce services and web-based businesses."

The Bungee Labs team has been working very closely with the Amazon team (and others API providers) the last few months to make sure Amazon's web services "just work" with Bungee Connect. Jeff Barr, Senior Evangelist for Amazon's Web Services:

“Bungee Labs’ decision to make their development environment integrate seamlessly with Amazon Web Services is great news for our developer community,” said Jeff Barr, Senior Evangelist for Amazon Web Services. “AWS developers can now use Bungee Connect to directly access our services, which means they can build Web-Scale applications in an easy to use, browser-based development environment.”

Another provider of web APIs, Salesforce.com has also been working closely with the Bungee Labs engineers. This time a quote from Adam Gross, Vice President, Developer Marketing, Salesforce.com:

“Salesforce.com has demonstrated that the innovation and ideas of the consumer Internet are at the core of the next generation of business applications. Bungee Connect together with Salesforce.com’s Apex platform makes it easier for developers to create mashups for their businesses, and in doing so hastens the transition from traditional enterprise software to the new on-demand model of building and deploying applications.”

So, what is Bungee Connect? Well, it's a lot of things:

Bungee Connect is a completely web-based integrated development environment (IDE) for building and deploying rich Ajax web applications, from simple web apps to seriously sophisticated Ajax applications. No install for developers, no installation of delivery infrastructure, and no client install for end users.
Bungee Connect is for developers, not for consumers. Yes, it provides a huge amount of automated support for the integration of SOAP and REST-based web services, Ajax app development and state management. You can develop sophisticated apps that integrate powerful (as well as simple) web services plus develop your own logic without having to write a line of code. It massivley reduces complexity. But, nonetheless, it is for developers, not consumers.
Bungee Connect provides a completely integrated means of deploying apps to the live web. No FTP. No separation between your dev, staging, production and live environment. No local set-up on your machine. No bits to install anywhere. No web servers, no app servers, no stacks, nor libraries to install, patch or manage. No 'Yak shaving'. It's all taken care of for you. You develop your app through the browser, then deploy your app through the browser and map the app to your domain / URL (or embed the app in your site) - It's your app. Oh, and you get IE, Firefox and Safari cross-browser compat taken care of too - you build your app once and it just works in these three browsers. Sweet.
Bungee Connect includes a whole code share and team collaboration concept. You can keep your code proprietary, or you can share it with other Bungee Connect developers in your workgroup or with the wider Bungee Connect developer community. There's a lot more to this than I can cover here and I'll be writing a lot more on this soon, but I like how Mat Asay described the community aspect as a 'Sourceforge for the 21st Century'.
Bungee Connect allows developers to leverage the world of web APIs. We've been working with the API engineering and evangelist teams at Amazon, Ebay, Google, Microsoft Windows Live, PayPal, RealNetworks, Salesforce.com and Yahoo! to ensure Bungee Connect works sweetly with the multitude of their rich APIs (both WS* and RESTful). The aim is to ensure Bungee Connect can work with any web service that you choose and by working with these teams and their APIs in developing Bungee Connect, we've got a great test-bed to make sure we can achieve this goal.
Bungee Connect is No Fee for the developer to use in developing and testing Bungee-powered apps. You only pay once you've deployed your app commercially or unrestricted. We expect this to be US$1 per computer-network-interaction-hour, billed monthly. Again, more on this later.

And there's so much more. Tomorrow, anyone attending Web 2.0 Expo will be able to get hands on with Bungee Connect. We've got a booth with PCs (Windows, Macs and Linux) with the browser open (IE, Firefox and Safari) where you run through some tutorials and judge for yourself if you think we're all smoking crack (see pics below - no crack, just the booths). We'll also be updating the site with screencasts and plenty more details and Martin will be presenting and demo'ing with Brad on Wednesday morning. And by then I'm sure David might have something more to say too...

To underline a couple of points here: we're not live yet. We go into Beta in May and are looking for web developers who ideally already have experience in progamming against the APIs of the companies I mentioned earlier. So sign up if that sounds like you...

---

Update:

Dana Gardner has written up his thoughts on Bungee Connect.
Short but sweet mention on Mashable.com by Pete Cashmore.

Update 2 (4/18/07)

Richard MacManus blogged it over at Read/Write Web
Ryan Stewart blogged us too :-)

Wiki risks

alexbarnett — Tue, 10 Apr 2007 22:57:00 GMT

I've not seen this Channel 9 video yet, but plan to - it's a interview (part 2 of 2) with MSDN team members discussing Korby's baby, the MSDN Wiki:

"Don't know about you people, but I look at community involvement as being a great thing for everybody. However, I'm not the one who has to take responsibility for opening up a site to modifications from the general public. When we see these projects, it's easy to forget the kind of risks that are being taken on behalf of the employees who drive the efforts.

This interview reminded me of what those risks can be."

(Example community content here).

Microsoft's MSDN Forums - community building

alexbarnett — Mon, 02 Apr 2007 13:48:00 GMT

Josh Ledgard, a program manager in Microsoft's Developer Division, has posted some details on the challenges in supporting the large number of Microsoft developers. What strikes me here is the 'transparency' of Josh's post in terms of publicly stating the some of the goals set for the team, the specific metrics being tracked across the product groups and the sharing of actual vs. target data:

"The reply rates are around 95%, but our goal with the answer rate is to get to 80% for the seven day rate and 60% for the on day rate. You can see some significant improvements since December. We've also seen more significant uplift in specific technologies where engineers where hired first. Since we haven't hit our goal yet I'll point out that the support engagement is only designed to get us so far."

Josh has also provided snapshots of the internal slides he presented that articulate some of the broader support goals for Dev Div and charts showing the over-time data. Have a look.

The MSDN Forums were launched around two years ago to replace some of (but not all) the traditional support newgroups and have had over 1 millions posts there since. Not everyone was happy when the transition began (for some MVPs, moving from traditional newgroups to web-based Forums was percieved to be a step backwards)

The product teams I used to take care of really had to conciously priotitize forum engagement by actual product group members (PM, dev, test) to meet our targets (response rates). A benefit of this approach is that product teams (and support groups) become aware of the issues customers are facing on a daily basis and this participation creates superb input for future product planning.

But it only takes you so far. For our team at least, the only way to truly scale (while being cost effective) in answering the steady (and increasing volume) of technical questions was to encourage customers themselves to provide the support network and have these answers viewable by all. This is a key concept in the notion of 'community'. If you are interested in this topic, I recommend you subscribe to both Josh Ledgard and Joe Morel who blog frequently and openly on Microsoft's progress and challanges in this area.