(Actually from last night during the flight, but then I got home…)

As part of my new position for CampusEAI I’ve had a fairly aggressive travel schedule over the past few weeks (the cost of not relocating). It has however forced me to become much more closely acquainted with the airlines (and Continental in particular) and prompted a few observations:

1. Upgrades: Getting upgraded is nice. The biggest problem? Generally people who travel enough to get upgraded are flying on business — and — hence flying at the same time as others flying on business (who fly even more). It’s almost disheartening to watch half the people waiting for the flight standup when they’re boarding Elite Access. Still, it’s nice when it happens.

2. Delays: So far out of 6 flight segments between Newark (EWR) and Cleveland (CLE) I’ve been delayed 3 times. It doesn’t seem possible to get delayed by less than about an hour either, though so far I’ve been fortunate enough with nothing longer than about 2 1/2. Still, a 50% hit rate is pretty… good? bad?

3. Airline Clubs: Worth every penny. If you travel a lot. Normally I try to cut my arrival at the airport pretty tight with my flight departure, to grab more time at home with the kids, but during those aforementioned delays… There’s a big difference between an hour delay in the concourse fighting it out with other grumpy bench residents, and an hour delay while sitting in the lounge on the wifi, by the bar, munching on an apple.

4. Security: Surprisingly I’ve actually gotten used to security — to the point where someone I was traveling with was like “wow — that’s crazy” and my instinctual response was “eh”. Of course, I no longer travel with belts, a watch, coins in my pocket…

5. Pricing: This is kind of a crazy subject. Right now — a Sun-Wed roundtrip between EWR-CLE is ~ $260. A Sun-Tue roundtrip? ~ $850. Whaaaat!?!?! I’m not sure that there’s any way to explain that other than trying to segment the market into business travelers,since who else would stay less than 3 days? Though, if I book 2 weeks at a time, with 2 weeklong stays that just happen to overlap… hmmm…

In general, business travel (especially regular, sustained travel) has been something to endure. It feels good to vent though

Blackboard Won:This just in

A Texas jury has found Kitchener software company Desire2Learn Inc. guilty of infringing on an American competitor’s patent.The verdict, announced this afternoon, allows Blackboard Inc. to demand a ban on sales of Desire2Learn’s products in the United States.

(Via e-Literate.)Michael F. isn’t the only one who’s speechless at this decision. The precedent this sets is uncomfortable on many levels, despite the fact that both:

1. The patent itself looks to be well on the way to being invalidated
2. I doubt Desire2Learn will have any trouble getting more Amicus motions filed for them at any subsequent trials or appeals.

Desire2Learn has reassured their customers:

With your support and that of the entire educational community, we were able to present a strong case. While we are disappointed that the jury did not agree with our position, we will continue to challenge the patent’s validity and Blackboard’s charges of infringement. We are currently evaluating our next steps.The United States Patent and Trademark office has committed to reviewing the patent. As these activities take place we will provide you updates through our patent blog at www.Desire2Learn.com\Patentinfo.

(Via Desire2Learn)First off, addressing confusion and concerns I’ve heard expressed during conversations with a number of individuals: this decision in no way implies that Sakai infringes on any Blackboard IP. Additionally, both Sakai deployers and any Commercial Affiliate you may contract with for services are explicitly mentioned under Blackboard’s previous commitments not to sue Universities and open-source.So “all” we (the Sakai Community) have directly lost is freedom of choice and a small piece of the spirit of innovation in education. While I don’t live in the right district, drafting Lessig for Congress seems like a better idea all the time. I do wonder however, if Blackboard’s previous “pledge not to sue” open-source products and affiliates might have unexpected implications.Though open-source communities seem unlikely to play the FUD game, does this mean that cautious schools may have only 2 options: Blackboard products or open source? If you’re looking to upgrade an existing LMS or deploy a system for the first time, does this affect your decision making regarding product selection?I should also take the opportunity to point out that this kind of key vulnerability is exactly why the separation of licensing from commercial relationships is such a powerful dynamic. Desire2Learn is by all accounts an excellent company, whose customers are happy. No matter how good the company behind the product, however, choosing D2L as a platform also directly binds you to the fate of a single commercial entity. A company who can fail, be sued, bought (a la WebCT, eCollege), experience a strategy shift (Be Inc.), etc.Participating in a community (or to grab a phrase from Barak Obama “a movement”) like Sakai gives you tremendous long term advantages. You can get competitive bids from multiple vendors due the huge number of commercial affiliates. You can switch vendors if you’re unhappy without having to migrate your service. If Sakai moves in a direction not aligned with local interests you can choose to create your own fork or derivative product. Finally, in the same way that diversified investments allow you to reap the rewards of the stock market while lowering your overall risk — Sakai (and other open source products like Moodle, Atutor, etc.) allow you capitalize on eLearning technology without putting all your eggs in one basket.Update: Michael Korkuska (Sakai Executive Director) blogged about the decision and it’s impact on Sakai and the industry as well.

Well the questions are pouring in (mostly due to my tardiness in writing this kind of announcement) and so, without farther ado…

What Happened?

While it still feels a little strange to say it, as of 2 Fridays ago (2/8) I am no longer employed at Rutgers University. Over the last 9 years as first a student, then staff member, I’ve had the chance to: first study under, and then work with some incredible people. I’ve gotten to watch projects and services grow and evolve into solutions that are used every day by tens of thousands of students, faculty, and staff.

Before addressing my personal situation, I feel the need to speak a bit about the Rutgers Sakai deployment which up until now has occupied so much of my thoughts and energy. I was fortunate enough to see myRutgers grew into a service providing tools and services to every student at Rutgers. Sakai usage is currently somewhere on that curve, with usage growing by leaps and bounds. This Spring’s semester in many ways feels like a qualitative shift in the nature of the service — marked by a huge increase in the number of students asking “where’s my class’s Sakai site.” This semester these questions are particularly significant, as many of them are coming from students in classes where either:

1. Class was not yet in session. This is a big change from the dynamic in previous semesters where students typically visited the first meeting of their class, and were then directed to visit the Sakai site. Now students are looking to visit the Sakai site to see the syllabus, readings, and get a leg up on going to that first class.
2. Their instructor had not created a site. Sakai seems poised to make the jump into ubiquity, as in some students minds it’s already there.

Now to handle the really common question — if the Rutgers Sakai deployment is so clearly poised for greatness, where am I going and why? Well…

Starting this past monday (2/11) I have taken a position with the CampusEAI Consortium, where I will be serving as the Director of Open Source Solutions. Recent years have seen a huge upswing in the popularity, and visibility of open and community source solutions in Higher Education. Sakai, uPortal, CAS, Kuali, and othes have garnered attention, awards, and deployments. Due to significant interest expressed by member institutions, CampusEAI is looking to complement its existing strengths on the Oracle platform with broader offerings in the open-source space.

Answers to some personal-ish questions:

Are you moving to Cleveland?

No, I’m going to be based out of NJ, though Continental is certainly getting a good chunk of my time for the next few months as I schlep back and forth.

What does Lisa think?

She’s excited. Well, more excited when I’ve been gone < 2 days as opposed to > 3 days…

What do the kids think?

The kids are still getting used to not picking me up at Rutgers. They think it’s really funny that daddy works somewhere they can’t see. Sunday nights are hard. Phone calls are bittersweet. Coming back is good.

Aren’t you on the JA-SIG Board?

Yes. When my career change became definite I notified the board at the January video call. JA-SIG has always been a community of volunteers (stellar volunteers more often than not) and particular given my new employer’s willingness to continue backing my involvement in JA-SIG it was felt that there were no significant barriers to my continuing to serve in this capacity. As always, JA-SIG

So… is your Rutgers job open?

Yes. Though (see below) I’m hiring too…

What’ll I be doing?

So what does this mean in concrete terms? My personal definition is pretty simple. We’re looking to help members deploy solutions built on open source software. Given my background, Sakai, uPortal, CAS, and maybe even Kuali are obvious possibilities. I think however, that it’s a broader story than just support for deploying a few specific products. Many institutions have experienced challenges in building around open-source due to shortages in staffing or specific skill-sets. Others have successfully deployed open-source solutions, but been burned trying to deepen integration, or due to staff turnover (a problem which I should note also happens around commercial solutions). So the goal of this new unit is to make deploying solutions built on open-source:

1. Easy
2. Cost Effective
3. Low Risk
4. Sustainable
5. Did I say easy?

Basically the goal is to allow schools to leverage the strengths inherent in the open-source development model:

• Try before buy
• Rational licensing and cost-containment (instead of getting wracked with heavy licensing burdens as you get “too successful”)
• Open implementations, generally of open standards
• Economy of scale versus custom developed institution-specific software
• Freedom from vendor roadmaps and strategy shifts — even to go as far as obtain competitive bids from multiple vendors on the same solutions
• Peer interaction with really bright people working hard to solve the same problems you see

So that’s the goal. Make open-source easier, removing barriers for schools large & small — the kind of topics that have continually been commented on lists, in journals, and at conferences. Reducing installation pain. Helping with patch management. Providing support and training. Taking the pain and risk out of going open-source, all while working to make strategic contributions to enable the production of more good software.

It should be exciting.

P.S. Did I mention we’re hiring? Drop an email talking about your love for open-source, and how you really want to join in making it easier: jason_shao@campuseai.org. Oh, and mention you saw the posting in my blog