Yochai Benkler, others at Harvard map current and future Internet

Harvard's world-renowned Berkman Center for Internet & Society is celebrating its tenth anniversary with a conference called Berkman@10. I'll report here on today's sessions, which were organized as a fairly conventional symposium (although as loosely as one could run it with 450 attendees). Tomorrow will be set up as an unconference, where the audience defines most of the topics and self-organizes into small-group discussions.

• Whither peer production--wither peer production?
• The conscious commons
• What will a Harvard for six billion people look like?
• Designing for cooperation
• Seeding and modeling
• The dilemma of openness
• The Berkman Center broadens

(continue reading)

Disaster Technology for Myanmar/Burma aid workers

There is an ongoing crisis in Myanmar (Burma) in the aftermath of cyclone Nargis. The ruling military junta is finally allowing humanitarian organizations into the region after denying access for almost a week. The situation is grim, and you can help by donating to organizations like: Doctors without Borders, Direct Relief, and UNICEF.

There has been some incredible discussion on the humanitarian tech and Geo lists in the past 24 hours around adapting/improving existing collaboration services to work with the tools in the field. Mikel Maron and I will be speaking about this at Where2.0 next week, and it looks like some exciting work will be happening there and at WhereCamp.

Eduardo Jezierski from InSTEDD is currently working to localize the Sahana Disaster Management System

Jonathan Thompson's organization, Humanlink, has been working on adapting technology for aid workers for some time. You can follow recent developments on the Aid Worker Daily blog.

Update: Paul Currion posted a big list of other projects now underway to the humanitarian.info blog:

• A Sahana instance is being set up for the use of anybody who needs it, with the support of INSTEDD and possible uptake by NetHope members.
• Direct Relief International have done up a KMZ file of health facilities in-country, based on the WHO 2002 Global Health Atlas.
• OCHA are prepping a HIC to support the existing Myanmar Information Management Unit, who have already put out some W3 maps.
• UNOSAT have also got their sat on with a KMZ file of the cyclone path and the usual satellite mapping.
• Ditto ITHACA, who have released a series of satellite maps showing the impact of Nargis.
• ReliefWeb’s info stream on Cyclone Nargis is of course like drinking water from a hose, with their map filter probably most useful.
• The WorldWideHelp blog roars into action with all the news that’s fit to blog.
• A couple of the mailing list discussions that I’m on are talking about ways in which we might leverage cellphone and/or satellite phone communications if they become available, particularly for tracking relief and relief personnel.
• Digital Globe and Geo-Eye have hopped the NASA satellite for an updating KML layer on the cyclone.
• Microsoft apparently have a team on standby to deploy the refugee tracking software that was developed for Kosovo (no reference yet).
• Telecoms sans Frontieres are also on standby out of Bangkok, waiting for access to free up.
• Also Infoworld points out that - with regards to early warning - IT didn’t fail Myanmar, people did.

(continue reading)

Maker Faire mimesis and open speculation

O'Reilly's Make magazine and the Maker Faire that we're hosting today and tomorrow in San Mateo, California have been described in many ways, ranging from a revival of the mid-20th-century love for Popular Mechanics magazine to an exciting new impetus for teaching children about science. During my six hours there today, I noted its strong connections to powerful and fundamental human urges toward creation, mastery, and the reproduction of our own culture.

Some of the Maker Faire centers are devoted to the kind of do-it-yourself projects shown in our magazine. Anyone from a four-year-old to a mechanically adept adult can find challenge and satisfaction at these tables. Projects in another building took a big step up, showcasing the brain children of engineers who devoted their spare time to building games and toys or aiding their communities with research projects. A number of the booths seemed to be run by Renaissance men and women who were making a living from their creative combinations of art and technology.

(continue reading)

Mondrian, Just the First Internal Google Tool Be Released Via App Engine?

Guido van Rossum, creator of Python and Google employee, has released a version of the internal Google code-checking tool Mondrian via the Python mailing list (text after the jump). The new app is called Code Review and was built with almost all new code on the Django framework. Code Review uses a lot of the same concepts and infrastructure that Mondrian does including Big Table.

There are differences. Code Review uses the open source software control system Subversion (also the backend of Google Code) whereas Mondrian works with Perforce, the commercial tool used internally at Google. Code Review will eventually be made open source.

Mondrian first became public at a Google Tech Talk. At the time Niall Kennedy wrote up a great summary of the talk.

It's great that Guido is releasing this and that Google is letting him. I am impressed. Could AppEngine be the way that Google releases its most useful internal tools? I've talked to several Google employees about the amount of code Google open sources and it's always less than they would like. The problem they face is that the code is tied to Google infrastructure and the hours required to de-couple it make the projects a non-starter.

Previous to the release of App Engine (and thus the exposure of Big Table) Code Review would have been one of those non-starters. Since he was able to rely on the Big Table implementation in App Engine the job became a lot easier. What other tools of Google's would you want (any of these)? I wonder if anything new will come out in time for Google I/O.

(via Reddit Programming)

(continue reading)

Missed Twitter Questions from Jonathan Schwartz Interview at Web 2.0 Expo

In the Jonathan Schwartz interview at the Web 2.0 Expo in San Francisco yesterday, I screwed up. After learning we weren't set up for audience Q&A with microphones, I thought, "well then, I'll just suggest to the audience that they twitter questions @timoreilly, and I'll check my phone during the interview." I kept checking, but no questions. Bummer. Not till I heard complaints afterwards that I hadn't asked any of the questions did I do a little digging, and discover that I had twitter set to show me only @ replies from people I'm following. Bad idea.

To all of you in the audience, a big apology for the screwup.

However, I did collect all the questions after the fact, and forward them on to Jonathan to answer by email. The questions and Jonathan's answers are below. I've presented it as if it were a twitter interview, snarfing up the questions from tweetscan, and then getting Jonathan's twitter image from his own feed. [Another big oops: that isn't really Jonathan's twitter feed. Will take out links till I get the correct one. Thanks to Scott Ruthfield for the heads up.] But in reality, he answered the questions by email, after I sent him the whole group in one email message.

triplebsoul : question for Sun " how is sun planning to balance environmental issues with scaling computing needs (power consumption, etc) "
2008-04-25 12:32:48

JonathanSchwartz: Sun's going to stretch the limits of engineering and our collective imagination to make the world's most efficient datacenter infrastructure - from OpenSolaris power management, to Blackbox datacenters. And although that's obviously important to our business, and to the planet, what matters most in managing environmental risk is the world's appetite for power - if that continues along the pace it is, we can slow the growth of power demand through datacenter innovation, but I doubt we can stop it. Every 100,000,000 new PC's in the world creates the need for many, many, many megawatt power plants.

cynthiagentry : ask JIS about the role of academia in the future of Sun, and in the future of Web 2.0
2008-04-25 12:32:46

JonathanSchwartz: It's hugely important. The majority of the world's change agents, media consumers and entrepreneurs graduate from universities every year. There's a reason Sun stands for "Stanford University Network." That's the world from which we spawned, that's the world we focus on with open source technology (you might remember we just concluded an agreement with the People's Republic of China's Ministry of Education to build a national curriculum around OpenSPARC and OpenSolaris - made possible by our IP being free and open...).

Sierralog : Question to Jonathan: Did you ever assess the success of you corporate blogging in terms of "ROI" and if so, how? Thx
2008-04-25 12:31:51

JonathanSchwartz: No. It just seemed like an IQ test. If I talk, people that are interested listen. If I don't speak up, they have nothing to hear.
 

amitc : Q for Jon: Beyond MySQL, Sun boxes and Java, what else does Sun has to offer Web Devs, PMs & Entrepreneurs?
2008-04-25 12:29:44

JonathanSchwartz: Um - that's certainly a good start, isn't it? :) I guess the majority of our focus within the next twelve months will be around our data management and storage offerings - starting with ZFS, and the potential of dual-licensing it under the GPL to see its growth within the Linux environment (alongside MySQL). As you'll see with our rolling out of network.com services, we plan on offering a ton of developer infrastructure as a service, as well.

buildakicker : How can this web2.0 help out or even work within the government?
2008-04-25 12:29:29
 

JonathanSchwartz: Hm - that's up to the government, no? We serve a lot of government customers, and they're very, very interested in network computing. Governments exist to serve the people. The people have internet connections. Put two and two together - you get governments interested in the web.

JesseStay : does he anticipate a fallout of original MySQL users or fork in the mysql code and how will they handle that if it does happen?
2008-04-25 12:26:30

JonathanSchwartz: I'm not anticipating a fork - Marten Mickos (SVP, Database Group at Sun, former CEO, MySQL) made some comments saying he was considering making available certain MySQL add-ons to MySQL Enterprise subscribers only - and as I said on stage, leaders at Sun have the autonomy to do what they think is right to maximize their business value - so long as they remember their responsibility to the corporation and all of its communities (from shareholders to developers). Not just their silo.

I think Marten got some fairly direct and immediate feedback saying the idea was a bad one - and we have no plans whatever of "hiding the ball," of keeping any technology from the community. Everything Sun delivers will be freely available, via a free and open license (either GPL, LGPL or Mozilla/CDDL), to the community.

Everything.

No exception.

coogle : One question I have for him is how the Sun acquisition of MySQL is going to impact the open source space and Sun long-term?
2008-04-25 11:12:36

JonathanSchwartz: It's going to open a flurry of doors for MySQL, and it's going to open a flurry of doors for Sun. It already has - as I said, the MySQL team just closed the single largest deal in the history of MySQL, a $10m deal to a global technology company. I'm pleased as punch with the progress we're making there, and we're deluged with inquiries from traditional enterprises (vs. Web 2.0 companies) wanting to know how to get enterprise support for a product they've used in development, but have, until now, not felt comfortable putting into commercial deployment. Now they feel comfortable deploying it - and we're right there with them to help make it happen.

And we're investing heavily to build a whole spectrum of products optimized for MySQL - stay tuned, you'll start seeing some amazing stuff.

rghanbari : For Jonathan Schwartz: What does Google app engine mean for Sun? Programming/deployment model makes Sun platforms irrelevant
2008-04-25 11:07:50

JonathanSchwartz: You know, one wonders how we can generate nearly $14,000,000,000 in revenue when I keep hearing technology x, y or z makes Sun irrelevant. Microsoft tells me MSN Search makes Google irrelevant. Not sure I buy that. OpenOffice doesn't make Microsoft Office irrelevant, either, it creates competition (that's why we have about 100,000,000 users!).

Competition's a good thing, it creates choice. Rumor has it developers like, and value, choice. Throw a sheep at me when that stops being true.

andrewsavikas : EC2 and AppEngine get a lot more attention that sun's grid (cloud) offerings. why is that? who's using sun's grid?
2008-04-25 11:05:47

JonathanSchwartz: Tons of high performance computing customers use our grid - we never targeted the mass developer. But stay tuned, you're going to see a lot more about network.com within the next 6 months.

GraemeThickins: Please ask Schwartz how much time he spends/day writing for his blog & how that's changed over past year; also, does he Twitter?
2008-04-25 11:03:33

JonathanSchwartz: Yes, I Twitter. No I won't tell you my user ID.

And the amount of time I spent writing my blog depends upon what I have to say, and what's going on in our business. It varies dramatically, unlike the amount of pressure I feel from the imaginary editor that sits on my shoulder telling me it's been two weeks since I've posted anything pithy.

mkrigsman: Ask Jonathan Schwatrz why IT departments are so scared of web 2.0 proliferation. Awkward question for him, but he's a big boy.
2008-04-25 11:02:10

JonathanSchwartz: The companies I talk to aren't scared of innovation, they're in love with it - it's a source of business value and competitive advantage. Companies scared of IT are likely to be buried by their competitors that aren't.

Sun's customers, bluntly put, are those that see IT as a weapon. Those that see it simply as a cost... good news, they'll be able to reduce their costs, given clouds and free services and labor arbitrage, to near zero. But we'll be far more focused on those delivering the network services to them that make that transition possible.

It reminds me of a discussion I had with the CIO of an oil company. He started the meeting by telling me "I don't understand why Sun's still around, IT's a commodity to me, who cares?" Until I reminded him his business just delivered more in quarterly profit than we delivered in annual revenue. And his business was built upon selling a...

Commodity. In his case, oil.

Commodities are where are all the money is, just ask Google, Verizon, Goldman, Sachs or Exxon. But commoidities also require R&D - those that couple the two, R&D and an ability to navigate commodity markets, tend to do rather well.

timoreilly: Thanks a lot for agreeing to take all these extra questions, Jonathan!
 
 

JonathanSchwartz Thanks, again, Tim - it's always a pleasure to hang out.

Call For Open Source Awards 2008 Nominations

For the 4th year running, Google and O'Reilly will present a set of Open Source Awards at OSCON 2008. The awards recognize individual contributors who have demonstrated exceptional leadership, creativity, and collaboration in the development of Open Source Software. Past recipients for 2005-2007 include Doc Searls, Jeff Waugh, Gerv Markham, Julian Seward, David Heinemeier Hansson, Karl Fogel, David Recordon, and Paul Vixie.

The nomination process is open to the entire open source community, closing May 15th, 2008. Send your nominations to osawards AT oreilly DOT com. Nominations should include the name of the recipient, any associated project/org, suggested title for the award ("Best Hacker", "Best Community Builder", etc.), and a description of why you are nominating the individual. Google and O'Reilly employees cannot be nominated.

Book review: "The Future of the Internet (And How to Stop It)"

Most of us in the computer field have heard more than our fill about the free software movement, the copyright wars, the scourge of spyware and SQL injection attacks, the Great Firewall of China, and other battles for the control of our computers and networks. But your education is stifled until you have absorbed the insights offered by comprehensive thinkers such as Jonathan Zittrain, who presents in this brand new book some critical and welcome anchor points for discussions of Internet policy. Now we have a definitive statement from a leading law professor at Harvard and Oxford, who combines a scholar's insight into legal doctrines with a nitty-gritty knowledge of life on the Internet.

You can read Zittrain for cogent discussions of key issues in copyright, filtering, licensing, censorship, and other pressing issues in computing and networking. But you're rewarded even more if you read this book to grasp fundamental questions of law and society, such as:

• What determines the legitimacy of laws and those who make and enforce them?
• What relationship does the law on the books bear to the law as enforced, and how does the gray area between them affect the evolution of society?
• What is the proper attitude of citizens toward law-makers and regulators, and how much power is healthy for either side to have?
• How can community self-organization stave off the need for heavy-handed legislation--and how, in contrast, can premature legislation preclude constructive solutions by self-organized communities?

Core questions such as these power Zittrain's tour of technology and law on today's networks. "The Future of the Internet" takes us briskly down familiar paths, offering valuable summaries of current debates, but Zittrain also tries always to hack away at the brambles that block the end of each path. Thanks to his unusually informed perspective, he usually--although not always--succeeds in pushing us forward a few meticulously footnoted footsteps.

(continue reading)

You Become what You Disrupt - (part two)

Google's GrandCentral (Radar coverage) was down over the weekend resulting in missed calls and other phone problems for its users.

This is very similar to the the two day Skype outage last year where I said that "You Become what You Disrupt". I've spoken about this issue several times, most recently at the Princeton CITP "Computing in the Cloud" workshop.

The problem is that it's not particularly clear at what point a disruptive innovation becomes a utility. As innovators it's important that we recognize that this point will arrive and prepare for it. I believe that we have a responsibility to be good stewards of the technologies we create, and to take responsibility for protecting people who come to rely on those technologies to live their daily lives. When we fail to do that, we may find ourselves being cast as either fools or villains who must be regulated and controlled.

Ultimately, I think we will evolve a set of safety standards very similar to building codes. For instance, it appears that a multi-datacenter strategy would have prevented the GrandCentral outage. (As I've said many times before: Datacenters are a Single Point of Failure!)

Cofounder Craig Walker writes: "I wanted to write a quick note to all the GC users and apologize for the service interruption this morning. We had a power issue at our current colo facility and it knocked us off line for a few hours. Unfortunately I’ve been up in the mountains with the family this weekend and had no cell/internet coverage so couldn’t respond earlier. I did want to let you know that we were able to restore the service by noon today and are working extremely diligently to make sure this won’t occur in the future. We’ll do a better job keeping you informed in the future, not only about service related issues but also about upcoming features, soliciting your feedback, and generally making sure that you, the GC user, is well informed as to what’s going on with the service."

Will better industry standards, best-practices, and independent certifying authorities emerge for these new utilities without innovation-stifling regulation? I hope so.

(continue reading)

Velocity preview at Web2.0 Expo

At the Web2.0 Expo this month we have a small preview of some of the topics and speakers at the Velocity Web Performance & Operations conference.  (Radar readers get a 20% discount by using "vel08js" as a discount code... and yes it works with the $300 early registration discount!).

Failure Happens
Friday @ 11:00 am, Room 2009

Artur Bergman and I will kick off the day with an entertaining/informative/eye-opening review of the year’s biggest failures, disasters, and painful lessons learned.

We'll review incidents by underlying root cause with a focus on what could have been done to prevent it. We promise not to be too harsh on anybody, although we will give special attention to particularly ironic failures or those that are "entertainingly coupled" to absurd marketing claims.

(Hint: Send your boss to this talk if they don't understand why you and your whole team need to go to Velocity.)

Even Faster Web Sites
Friday @ 1:30 pm, Room 2012

Steve Souders is the co-chair of Velocity and author of the bestselling book High Performance Web Sites. At the Expo last year Steve gave an incredibly popular talk on the 14 best practices he developed while working as the Chief Performance Yahoo!.

(continue reading)

Getting the iPhone Open Source Tool Chain Up and Running

Tomorrow at 10 am pacific time, oreilly.com is hosting a free webcast with Jonathan A. Zdziarski, one of the original hackers of the iPhone and author of iPhone Open Application Development. From the announcement:

Jonathan will demonstrate how you can use the iPhone open source tool chain to design third-party software that will run on on both today's iPhones, and on iPhones that will soon be running Apple's next version of firmware based on the official SDK. Jonathan will demonstrate on a Mac running Leopard.

Introducing Jonathan will be Brian Jepson, executive editor for Make Magazine's Make:Books series, co-author of Mac OS X Tiger for Unix Geeks and a number of other geeky books, and iPhone hacker at large.

This is your opportunity to hear expert advice on building applications for the iPhone and ask questions of the experts themselves.

Attendance is limited, so register now. We'll send you a reminder before the webcast.

Date: Thursday, April 3 at 10am PDT (17:00 GMT)
Cost: Free
Duration: 30-45 minutes
Meeting link: oreilly.com/go/webcast-iphone
Teleconference dial-in:
(select the number that is closest to your location)
East Coast US: +1 617 231-0350 and pin 8136507
West Coast US: +1 213-455-0500 and pin 8136507

Some people might wonder why we published a book on the open source toolchain when an official SDK has already been announced. (I wondered that myself :-) We started the book before Apple had learned from the first hackers that people wanted more out of the phone and announced the open API. But why didn't we just hold off on publishing it, modify it for the official API, and release it when the time comes (supposedly sometime in June) when the official API is open for business? The answer is threefold.

1. We believe strongly that hackers mark off the natural paths that official developer programs later pave over and make safe for the less adventurous. Smart companies know this, and pay attention to their hackers. (Google Maps is a great case in point. It became the mapping platform of choice because, rather than shutting down the early mashup hackers, it quickly figured how to pour fuel on the fire that they'd started.) We think that despite the official disapproval, Apple knows that the hacker interest in the iPhone is a great boost to their program and their goals. (Witness the fact that the Apple store in Cambridge MA allowed Jonathan to present on open iPhone development in a meeting at the store.)

2. The open API has a great deal of overlap with the official API. So getting up and running with the open toolchain will help developers get a head start. But it's also more powerful than the official toolchain, and will let developers continue to push Apple in interesting new directions. Jonathan wrote:

   With the introduction of the Apple SDK, developers gauged its functionality based on a comparison to the unofficial, open source SDK released last August. In the process of building this custom, open source compiler for the iPhone, the development community exposed the many low-level APIs (application programming interfaces) available on the device. Using tools such as class-dump, nm, and just plain old trial-and-error gave developers access to the full breadth of functionality available deep within the iPhone's frameworks. It was used to write applications that could look and act just like Apple's preloaded software, so when Apple announced that their SDK was "the same set of tools," many expected that it would look and feel like the open tool chain. Very few had anticipated the many restrictions they've come to find in the official SDK. While roughly 75% of the two SDKs do overlap, the remaining 25% has shown to be very restrictive, removing the developer's ability to do "the real fun stuff" with their application.

3. The demand was there. The number of slots in the official API program is far smaller than the apparent demand. We published the book, and it sold out immediately, indicating that we were right. We do plan to update the book with information about the official API as soon as the Apple NDA is lifted, but for now, we are eager to fuel the fire, since we believe that the iPhone is one of the most important new platforms in the market today, and one that developers should be exploring as deeply (and as soon) as possible.

See also Jonathan's article on the O'Reilly Network about open API development for the iPhone for more information about the difference between the two APIs, and why developers need to know about both. We're also planning to have a strong open mobile development track at OScon.

Open Source "Social App Server" Might Crack Garden Walls?

From right here in Philly's backyard, Ringside Networks came out of stealth mode yesterday to launch the first open source "social application server."

And what is that exactly?

It's the software guts of a social network that you can use behind your own firewall, old school style, to build social networking "stuff" into your own site.

Companies that want to build social applications (for runners sharing times at Runlicious) or socially aware marketing programs (like Jeep owners sharing pictures and videos) will be able to use social servers to develop the whole thing on their own websites. Their brand on their site instead of their brand on Facebook next to the "get help for your gambling problem" advertisement.

Developing a social network will be harder to do this way than it would be using a white label network like Ning, but it will be completely customizable, will integrate neatly into the rest of the site, and all the data will be right there for the application owner to mine.

That's the simple version anyway; use social servers to roll your own social apps and sites. But I also wonder how it might upset the balance of power inside the behemoth walled gardens of Facebook and Myspace.

OpenSocial took the first shot at the garden walls with a goal of empowering users to keep their social data portable (well, portable inside Google anyway). However, while OpenSocial promises developers social apps without servers, Ringside is saying that at least some developers are going to want their own stuff under their control. I think social app servers are going to take shots at the wall too, but with the social networking advertisers and application ecosystem as the core constituency.

By supporting Facebook's API (with other API's to follow), Ringside makes it a lot simpler to take a social application written for Facebook and move it to its own site, or visa versa as shown in this picture. This kind of write once deliver anywhere approach to social applications raises all kinds of interesting possibilities.

Like,... Don't want to have to enter your favorite beers into Beer! in both Facebook and Myspace? If Beer! builds their application on a social server that can tie your Facebook user name to your Myspace user name, you won't have to. Facebook and Myspace just become two points of presence for the application, and they'll be on equal terms with Beer!'s own web site. Wherever you log in, you see your beers and (most of) your beer friends.

Facebook opened up this possibility when they designed their platform to have the developer's servers do the heavy lifting. Doing it this way meant they didn't have to provide all of the servers and gear to run the applications, but it also means that it's easier to stick a social server outside the wall and treat it and other branded networks like distribution shelf space. Once an application can seamlessly span the networks, it can do more than map a user's identity across sites, it may also piece together a social graph that is bigger than any one site's. Sort of an application-specific super graph.

In one possible end state, users own all of "their" social graph and data in OpenSocial, and application providers own all of "their" social graph and data in their own social application servers. Meanwhile, the big branded social networks are still in the game with very large "lily pad graphs," but they no longer see the whole picture for any one user or any single application.

As this evolves we may see developers building first for Facebook and Myspace to get quick viral adoption in a huge audience. However, as soon as they can they may start to drive traffic over to their own sites where they can provide a better or different interface with a more carefully managed brand experience. Imagine if NBC let you show your first YouTube video from a planned series at 7pm on Thursday, for free.

Or, developers may use the write once deliver everywhere strategy to deliver their app as widely as possible. Where Facebook and Myspace were once king, in this scenario they may end up as two of many application points of presence with awareness of only a piece of the associated social graph. The successful application developer with a network-spanning super graph might then be free to monetize it however and wherever they can.

Well, at least until the API wars start in earnest. There is a good reason for the server to be open source, it will spread the load of keeping up with all those inevitable API changes.

To be free, information has to be smart (comments on Chris Anderson's "Free!")

WIRED Magazine's editor in chief Chris Anderson, following up on the popularity of his Long Tail meme, theorizes in the March 2008 issue of WIRED about the modern tendency to put information online at no cost. I'll start this blog with the implications of offering free information in the computer field, and build from there to what I agree and disagree with in Anderson's article.

Anderson's taxonomy of "free" contains six models that justify giving the information away. The idea of "free as in freedom" (that is, open source information in the GPL or Creative Commons style) doesn't enter at all into his article. Is that important, given that the article is economic rationale for business? I think it's a crucial omission.

(continue reading)

Recent Posts

• Penguin's Missed Ebook Opportunity | by Jimmy Guterman on March 18, 2008
• Given Enough Eyeballs - Art Meets Open Source in Philly | by Jim Stogdill on March 14, 2008
• Perl mailing lists added to Markmail archive | by Tim O'Reilly on March 13, 2008
• Free Computers for Local Schools | by Allison Randal on February 28, 2008
• Take the Money and Run? I think not. | by Tim O'Reilly on February 20, 2008
• R.E.M., Open Source, and Staying Alive When an Industry Shifts | by Jimmy Guterman on February 19, 2008
• Interview with Linus Torvalds | by Allison Randal on February 4, 2008
• Stuffing Six Million Pages Down Google's Throat | by Tim O'Reilly on January 21, 2008
• Sun To Acquire MySQL | by Tim O'Reilly on January 16, 2008
• Linux and GPLv3 | by Allison Randal on January 9, 2008
• OSCON 2008 Call for Participation | by Allison Randal on January 7, 2008
• MarkMail Provides Amazing Search Capabilities | by Tim O'Reilly on January 7, 2008