Skip to main content

Interesting Stand by RedHat

When "Big-Wigs" (read Microsoft and Apple) began patenting their software/products, apart from triggering a proxy war - it effected end user who had to suffer in general. However it was the way software was developed as a whole that got hit.

Come Open Source, These things have changed quite a bit. Innovations are now not proprietary. Look at Linux, Andriod, Eclipse, Prototype and YUI. These revolutionalised the current state of Internet and software. But the question is how can the so called patent holders pretend not to ashamed of using these components/their derivative innovations in their own space?

I am amused by how redhat handles this. They have their own patent policy. And promise to keep the Open world safe from it.


Red Hat has consistently taken the position that software patents generally impede innovation in software development and that software patents are inconsistent with open source/free software. ... Red Hat is also a signatory to a petition to the European Union encouraging the EU not to adopt a policy of permitting software patents.
At the same time, we are forced to live in the world as it is, and that world currently permits software patents. A relatively small number of very large companies have amassed large numbers of software patents.
One defense against such misuse is to develop a corresponding portfolio of software patents for defensive purposes. Many software companies, both open source and proprietary, pursue this strategy.
..any party exercises a Patent Right with respect to Open Source/Free Software which reads on any claim of any patent held by Red Hat, Red Hat agrees to refrain from enforcing the infringed patent against such party for such exercise ("Our Promise")..
Our Promise does not extend to any software which is not Open Source/Free Software, and any party exercising a Patent Right with respect to non-Open Source/Free Software which reads on any claims of any patent held by Red Hat must obtain a license for the exercise of such rights from Red Hat


I love that. Eat that Microsoft ;)

Leave comments in Guestbook

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.
Read More >>

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.
Read More >>

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>
Read More >>