I recently reviewed the license documentation applicable to the React JavaScript library. The library provides a web user-interface function allowing views for HTML data. Facebook maintains the library as a project on Github, and it offers licensing documentation for the library on that site. I’m critical of the license approach used by Facebook for React for at least three reasons. More on that below. But since Facebook’s approach is unconventional, I first offer a brief explanation of the history and substance of that approach. I. History and Structure of React Licensing. All I know about React licensing is what I’ve seen on the Internet– notably, on Wikipedia.org. Initially, in May 2014,
Share purchase agreements, technology license agreements, partnership agreements, professional services agreements, and virtually all of the other agreements I draft in my practice include a forum selection clause. A section of an agreement that identifies the particular court or arbitrator that may hear a dispute between the contracting parties. In order to draft these provisions effectively, it’s helpful to examine how the courts interpret them. The following is a discussion of the primary issues that arise when courts consider forum selection clauses. Based on those cases, I’ve come up with a few practice pointers that you may consider when you write a forum selection provision into your