Liveblogging like a pro

I’ve written before about the (controversial in some circles) phenomenon of liveblogging: posting notes in near-real-time from a conference.

On Friday, Ethan Zuckerman posted The 5-4-3 double play, or “The Art of Conference Blogging”, including an extensive set of tips on how to do blog from conferences more effectively. As one might expect, it’s a comprehensive list that makes me realize just how underprepared I’ve been in the times I’ve tried to do it.

The highlights:

  • The kit: I come to conferences with my beloved Mac, two charged batteries, a power strip, a digital camera and cables, granola bars and a lap desk. . . .
  • The location: Bloggers rarely sit in the front row to blog conferences. . . . It’s usually better to sit to a side, near the power plugs. . . .
  • Preparation: Conferences usually give you a speaker program ahead of time. Use it. Over breakfast before the day of a conference, I’ll type the names of each speaker and their talk title into a text file. If I’m really good, I’ll do quick Google searches on each of them and link their names to their blogs, research institutions, arrest records, etc. Prepare sufficiently and you’ve got the first paragraph of each post written ahead of time.
  • Macros: . . . This is a way of storing pieces of text that you use frequently and linking them to key combinations. . . . Even if you’re composing online, within your blogging platform, or if you don’t feel comfortable setting up macros, it can be a big help to put some useful snippets of text in a text file and cut and paste them into blogposts.
  • Keeping Up: I have a hard and fast rule for myself – I complete posts on a conference session within fifteen minutes of the end of that session. . . .
  • Hard Talks: . . . Experienced speakers are easy to blog – they follow a narrative path through their talks, speak at a pace the audience can understand, emphasize key points with visuals. . . . It’s much harder to blog inexperienced speakers. . . .
  • Use your commenters: Because I’m blogging ten or more talks a day, I get things wrong. Sometimes I get things egregiously wrong. Comments allow other attendees – and sometimes the speakers themselves – to correct me. . . .
  • Collaborate: . . . My goal in blogging a conference is not to be the sole, authoritative voice of the blogosphere. It’s to do what I enjoy doing: writing detailed summaries of each sessions. . . . It’s a whole lot more fun to blog these events in groups, even if that means sitting next to someone trying to liveblog at the same time as you are, arguing about how to spell a word the speaker has just uttered.
  • Digest: I go to conferences because they give me a wealth of new ideas to wrestle with, sometimes for weeks or months to come. . . . So that I have a chance to wrestle with the big ideas, I’ll often try to write a summary or reactions post a week after a conference. . . .
  • Have Fun: Not everyone enjoys blogging at conferences. I have many friends who’ve tried it and discovered that it stresses them out or detracts from their enjoyment. There’s an easy solution to this: don’t do it. Most people don’t keep score at baseball games. That’s okay, as there’s an official scorekeeper, a scoreboard and at least one journalist in the stands. We don’t need everyone to become a conference liveblogger – just a few more of us.

Although I’m reading these points after OSCON, not before it, I think my approach was much closer to what Zuckerman describes than my own previous liveblogging from Enterprise 2.0.

In a few sessions I took some live notes (see posts tagged OSCON), but in most sessions I just felt like trying to liveblog was getting in the way of enjoyment for me. I posted a few key notes to twitter (as when the OSI announced approval of the CPAL) but didn’t try to keep up with any of the other OSCON twitterers in terms of detail or frequency.

But I did have fun.

Look for some digest / summary / follow up posts over the next few months.

Eben Moglen on the Republic of Open Souce

Notes from Eben Moglen’s talk this morning at OSCON. There’s no way I could really capture all of Moglen’s points – so think of these as rough, raw highlights. All typos, grammatical errors, and other goofs are mine.

Licensing is not where it is going to be at for the next while, and there are other public policy issues where it will be at instead.

Licenses are a part of community building – they are constitutions for communities.

But the words of licenses are just the beginning – just as written constitutions are just the beginning of the republics which they give birth to and organize.

In the 21st century it is no longer factories or individuals which are the units of production and distribution – it is communities. This is the reality of mass culture.

You can’t see a cola ad today, without seeing a reference to a web site associated with that cola, and if you visit that website you will see a community under construction – a community of people who encourage each other to drink more cola.

You can’t be in the syrup business today without a community of syrup-suckers.

Communities experience disruption – both hostile disruption from competitive communities outside but also from internal disruption based on the stresses and strains inherent in social life.

I talk to lots of people about licensing. But the most important conversations are really about public policy and quality of community – the community itself improves the quality of dialog within the community.

The licensing discussions are serious, and are treated as serious public policy discussions to be engaged in with a clear sense that community interests much be preserved – these are public policy issues.

We are now in a position to say that we have turned a corner – we will never go away. That we are seen as powerful competitors to the existing business model is historically significant.

It is true that we are entering a period of contention about patents in particular – the industry’s dominant competitor is seeing it needs to change, and that is disruptive – but are not in any fundamental danger due to the strength of our communities.

GPLv3 – successfully addressed the issue of discriminatory patent pledges – and all the yelling and hand waving from one geographic corner of the IT universe won’t change that.

Most of the work my colleagues do at the Freedom Software Law Center you never even see. Problems that may arise years down the road arise and are discussed and resolved before the become major issues.

Example – paper on wireless drivers due out shortly- unique only in the sense that it is resulting in a public document.

The way that licenses work is that they need preventive care – its not just about fixing holes but strengthening communities.

The global software industry spends tens of billions a year in order to earn tens of billions – and they spend a billion or so on litigation.

We cost nothing, make little, and have zero litigation – even though the companies around us make tons of money.

When the litigation in your town drops to zero, it is time to have a block party, not time to have a name-callign argument about who is and isn’t open source.

The communities are working with a level of smoothness and frictionless operation at a level unheard of in commercial development in any period in the industrial age.

If we have done well – and we have – it is incumbent upon us to understand why, and how to preserve that. . . . we are the best example that the world can show in how the reduction of barbed wire can result in more productivity and less conflict – and we are not getting the reputation for that which is deserved.

We have to be more sensitive that this is, in fact, a political accomplishment. What we have done is to build a good republic, and we need to ensure that we keep it. We need to understand what the commitment to success primarily involves, and we confuse ourselves if we think that is primarily a question of business organization, or how companies are funded, or even how programmers are paid. It isn’t that these questions are not important, but that they are small beer compared to the questions of how we ensure that the community continues to strengthen rather than becoming less free over time.

When we were of no interest to the wealthiest interests in the world, our community was more equal because it was only us in it. When they arrived, the neighborhood got more expensive, and our community now looks more like the world outside, with a full range of wealth. But we have preserved in the midst of this stratification many mechanism of egalitarian impact and intent.

It is good – and fundamentally right and just – for people to begin from a presumed equality – inequality of access to ideas and each other is a fundamental corrosion of community.

Service provision and the GPL – an extraordinarily heated subject about which there is lots of noise and concern – but most of the discussion comes at it from the point of view of business strategy. (Ultimately comes to Google bashing). The problem in my view is that we don’t start in the right place – which is, oddly enough, in that American individual focused question of what we think people’s rights ought to be.

The fundamental right with which Stallman has always begun is anyone’s right to run any program anywhere at any time for any reason – this has to include the right for people to run a program at any time *for anyone* – that is, provision of software as a service for other people. That is an important aspect of sharing. You cannot take that away, and slice off that major aspect of freedom, in order to limit the size of an organism in the republic, or limit competition or whatever, unless you can prove that some more important aspect of freedom is being injured.

It is a key element of the freedom of speech to have the freedom to not speak your thoughts. Thus one of the key freedoms of the ability to share is the right to not share.

If the discussion about service provision is a rights conflict issue, it is critically important to frame that discussion in clear terms based on the rights perceived to be in conflict.

No rights based argument sufficient has been articulated which should compel the release of code which some people choose to run for third parties benefit. That doesn’t mean such an argument doesn’t exist – and the conversation should continue – but the GPLv3 provides a framework in which that experience can happen.

People who want to experiment with this approach will continue to have access to the GPL commons. What will not do is allow people who have made conclusions about service provisioning back into that commons and force those decisions on the commons.

But this is only one public policy issue we need to continue to argue about in order to continue to protect and evolve the republic – not because of some crisis but as a matter of continued maintenance.

In addition there is the patent issue – our neighbor to the north’s patent saber rattling is just a blip in this larger conversation about what patents are and ought to be.

Patent policy needs to be an issue on which there is real public policy debate – in which it is up to us to be involved as citizens. We need to be heard on this – it will not be prominent public debate but we must be heard.

The same is true with respect to ODF and the representation of public data in proprietary formats. All public data ought to be in a format that any citizen can access without purchasing commerical software, obtaining a patent grant from anyone, or relying on software based partially on proprietary algorithms.

We can as citizens of our republic decisively affect this issue on all of our behalfs and for the greater public good.

We need to move as far as we can and as fast as we can in the direction of institutions in which decisions are made through voting and leaders derive their leadership from the consent of those who choose them.

We will do better in our republic if we increase the ability of our leadership to legitimize itself over time.

The republic is not going to be kept strong by speeches made by me – the republic is going to be kept strong by speeches made by you.

O’Reilly OSCON keynote highlights

[Not really liveblogging here – just some nuggets from Tim’s talk. Took a long time to post because the wireless is overloaded. ]

Degrees of Freedom, Open Source in the Web 2.0 Era

How do we preserve freedom when:
– Running the program requires a hundred thousand cpus and terabytes of data
– When open source software increasingly uses services based on proprietary algorithms and proprietary data
– When redistribution is no longer necessary for everyone to have access to the program?
– When “improving the program” is less important than “improving the shared data”?

What Eben [Moglen in yesterday’s interview with O’Reilly] was trying to tell me was to pay attention to freedom and not just the success of businesses. But it is important to remember that businesses shape our culture – but it is important to say that the open source movement has shaped how businesses think about these issues and that needs to be recognized as well.

Influence of the freedoms of open source outside the “pure source code” realm
– Wikipedia
– Freebase
– DabbleDB
– Swivel
– Many Eyes

Web 2.0 – I know people argue about the name but it is a good handle to a group of issues. What’s going to be owned online.

There is a race on to see who will own various aspects of the online experience – therefore there needs to be a corresponding race to keep these things open.

We need to think about the things that need to be open, that need to be free that need to be in the commons – and we need to build software that enables this.

Open Source Success Factors

1. Frictionless software distribution10
– Free as in beer, or SaaS gets you this to
– Source code not needed
– Redistribution matter

2. Collab development

3. Freedom to build on, adapt, or extend
– Source code helps, but not essential [really?]

4. Freedom to fork
– Source code needed

The consumer-reports table – free redistribution, extensibility, network effects, “platform” more important than source code?

Eben Moglen – Putting the F back in FOSS

Eben Moglen’s interview with Tim O’Reilly this morning was certainly eventful. I hope they’ll post video of it somewhere online, and won’t make any attempt to liveblog it.

It started off with Moglen arguing that the whole notion of a “web 2.0 era” is pure “hooey.”

Then it went downhill from there. O’Reilly seemed a bit unprepared for the confrontational nature of Moglen’s discussion.

Moglen challenged O’Reilly, arguing that while the FSF has spent the last 10 years talking about freedom and rights, O’Reilly (and by extension the whole “Open Source” movement as opposed to the “Free Software” movement) was busy making money and talking about who was going to have what IPO.

He basically argued that the FSF has “done the heavy lifting” and “carried your water” for the last decade, and that the era of Web 2.0 distraction (buzz about who is making money, who will get acquired, etc) will need to be replaced by a serious conversation about freedom.

O’Reilly asked him: What would you do with OSCON?:

Scrape the name of the thing, put freedom up there, and start talking about real freedoms- which requires a discussion about public policy and long-term consequences of all this technology we’ve all put into the world. . . . GPLv3 gives us 10 years strategic time to think about this – I’ve just given you 10 years, hope you make better use of it than you had for the last 10 years.

Moglen’s direct (and very deliberate) ad hominem provocations aside, he’s clearly hitting on an issue that is at the heart of O’Reilly’s discussion of freedom, and of what it means to preserve the kinds of freedoms open source makes possible. Where “Open Source” as a term arose at least in part in order to “keep politics out of it” Moglen did a great job this morning reminding us that politics (by which I mean public policy, legal reform, and discussions about competing rights) are exactly at the heart of it.

All this before 11am.

Facebook and Firefox, Platforms, and Freedom

Very interesting set of conversations this morning at the O’Reilly Executive Briefing.

Tim O’Reilly interviewed Dave Morin from Facebook – they’re building on a LAMP stack, and have contributed some things back, but clearly the main core of facebook is not an open source project.

His basic response was that “We will continue to release as much as we can, when it makes sense.”

Two reasons why it might not make sense came up:

  1. The functionality the code offers is so tied to your services as to not be useful to outside folks
  2. The codebase isn’t mature or professional quality enough – not “ready” to be released

For example, he said “we want to make sure that when we release something it is something of value, and something that the community can use.”

Then O’Reilly interviewed Mike Shaver from Mozilla, along with Matt Gertner from AllPeers and Garrett Camp from StumbleUpon, talking about the Firefox platform for extensions.

The Mozilla approach, as I suppose one would expect, is entirely different: release everything.

We don’t provide a tightly controlled API we let people access a lot. If you write an extension, it is as though you were writing code in the browser itself.
What we did was we gave people possibility.
What you get with source access is a very rich, and sometimes messy, set of points of contact with the overall platform.

I wish O’Reilly had gone further down the path of this question. Rather than deciding on behalf of the community which pieces they are likely to find valuable, Firefox takes the approach of allowing the community to determine what is valuable. Rather than waiting for code to be “mature” to release it, they let the community help make it mature.

It’s the difference between a platform designed to be extensible – which really means developers can write applications to run on our platform, as in Facebook, and designing a platform to be an open platform for anyone to do anything.

Is the difference just that the Mozilla foundation is a non-profit community, and Facebook a for-profit company?