The specific case (covered heavily - check Techdirt for one) in question has actually brought in a much larger problem to light. How should students treat code written as part of assignments or as part of their course-work in terms of licensing? Is there a precedent for licensing? Most research activities conducted by universities have already adopted licensing framework. Here's an example. There has been debate whether such licensing should be free. Just check Medical Research and you can open Pandora's box. One more example is Singapore's A-Star which is more of a group focused on preparing research for industry adoption including licensing and legal usage terms.

How about code released in books on Data Structures, Algorithms, Fundamental C programming? To my knowledge (do correct me if I am wrong), the code is usually licensed under the same copyright notice as the book itself. In some cases, the author changes this licensing and makes it available. One example is "Numerical Recipes in C" where the licensing terms of the code from the author(s) of the book is explicit and can be found on a google search.

When it comes to university assignments, it is no news that the same template (if not the same course material itself) tends to get recirculated over a periodic basis. In some cases this period is annual and in others, the frequency is different. The debate raised is ages old. For most data structure or standard assignments of programming, you could find most of the code online. You could use this as a starting point or choose to write your own and learn your fundamentals. That's up to the student and the professor who is teaching and grading.

There is some truth in the statement (IMHO) that the Academia is shielded from the real commercial world. It works positive in some cases and is counterproductive in fields like Engineering (not Theoretical Computer Science.) In this specific case, if the University were to read all the fine print they have on students sharing course material (for which they pay for) and lecture notes and assignments, they would find the right solution. Bringing this (issue between a student and the professor) out to Open forums seems more of a publicity stunt that is going to get someone infamous for some and noticeable for a few others.

Focusing on the larger issue, a Varsity must be clear on how course-work and assignments from the students will be licensed and treated. They already have set legal precedents for most research work (which in some cases is funded by commercial bodies.) Hopefully this issue raises a flag and lets varsities understand and embrace Open Source, encourage students to use it particularly in programming assignments. At the very least they should at least reserve procedures to let a student obtain due permission for displaying his/her works online under appropriate licensing. In the absence of a precedent and clear guidelines, such confusion and unnecessary nerve wracking experiences between a Professor and a Student are more likely to surface. I hope not.

I read through the article and a lot of blogs covering Riversimple. Here's what it looks like under the hood. It seems too early and preliminary for adoption. "Open Source" seems to have been employed purely as a buzzword to generate interest. Most of the detail is actually at the 40 Fires foundation website which will probably release design schematics. Their FAQ answers questions I had in mind and is a good place for a starting read. The codename for this car is Hybran. The EU welcomes Hydrogen cars as a strong "Green" alternative.

If you do compare it to other initiatives like OSCar, you would find this option from Riversimple probably at a better stage of adoption. But until they unveil their prototypes (16-Jun-2009 is not far) and manufacturing goals (however they intend to go about it,) consumers will be skeptical about adoption. They first have to hit a note on consumers _wanting_ it or _needing_ it before proposing an attractive business model. Most of the prior comments reflect that we are not yet ready. Design momentum on OSCar seems to have stalled in the year 2006.

In contrast another vehicle release earlier this year happened in India with a lot of buzz about a $2,500 car, the Nano from India. This car _can_ do more than 56 mpg on Gasoline. It isn't green, but you can grab one, drive one and feel much safer than the electric counterparts that roam about the cities. This car went through at least 2 yrs of testing because the average consumer was scared about safety. The adoption was further slowed down by slow manufacturing response from Tata Motors.

India has allowed an Electric car (REVA) to be used within City limits (for road safety and range concerns) manufactured by Reva. The vehicle (a modest 4 wheeler) which comes in multiple flavors has low adoption rates in cities which allow it. This car through evolution has been heavier than India's top selling gasoline small-car the Maruti Suzuki 800cc 4 seater, and offers lesser range within a city. It has a very short range of 80-100km and requires battery packs to be replaced every two years (or depending on usage.) From June, 2001 the adoption has been very slow. During July, 2008 at least 260 Reva's (multiple models) were sold which is a record high. The Reva is priced at a one time price tag of close to $6,500 with an installed set of batteries. These have to be replaced at about $1000 every year. There's some comprehensive information and links on the Wikipedia Article (Reva). The cost has been a factor in slowing down adoption added to the fact that electric charges are required almost on a nightly basis. India has welcomed the car with reduced parking charges and several cuts. The G-Whiz model sold outside India is far too pricey ($12000 in Chile) and does not enjoy these environment friendly regulatory benefits.

For crowded cities in India where pollution is a heavy problem, Electrical cars with limited range for office commuters who'd prefer some shade (where public transport is a little inconvenient with timings) has received early adoption. i would presume that countries facing rapid development and growth rates will have to take this more seriously. Scaling public transport infrastructure has always been a challenge in many developing countries owing to a myriad of reasons. The basis for creating indices to track air pollution is outlined quite well in this paper (PDF) from IOP.

As many earlier comments point out accurately, adoption of such alternatives will require regulatory laws from the government (Road taxation, Commercial tax holidays, Green Credits and a lot more.) The working business model for Leasing automobiles is already here. The period being talked about (20yrs) might need to be tweaked which is presumably because of high manufacturing and deployment costs on low initial volume.

There are some pitfalls of lightweight cars at an early stage. Their ride heights are incredibly low that restricts markets in which they can be adopted. It might even keep them out of developing countries until the designs are tested. IMHO coming up with a disruptive solution to personal transport and tagging it with another 20yr lease agreement without the support of an auto major who's made it over a decade selling small cars or energy efficient cars is asking too much from the consumer. The "Open Source" tag means too little unless auto manufacturers see this as the best way to go forward.

Here is the Scanning Device being tested at 19 U.S. airports.

I did check out Hyperspace quite some time back when they were looking for developers to extend it further. It seems to be a remix of the Xen hypervisor, though heavily modified and possibly derived from a Citrix license. The idea is to provide what Borland managed to do with Sidekick and it isn't a product that is meant to just sit in the BIOS. Phoenix's Download page clearly shows that Hyperspace is an individual software product that can be bought. I'd certainly love to have a Sidekick like option today and an in-built paravirtualization module to switch between different kernels or Operating Systems without a reboot. This seems promising, although consumer adoption will probably be kicked in through OEMs more than Software Box sales.

What remains to be patented is a method for granting patents, such as it is now. We could then charge the USPTO for each patent granted or better still deny them the rights. Gawsh!!