Robert Sutor's Library tagged → View Popular, Search in Google
"Van Nest told the judge Thursday that former Sun CEO Jonathan Schwartz gave a sworn statement this week that he did not object to Android when it was released and that he still views it as a "positive development" for the Java ecosystem."
"People often ask us what license we recommend they use for their project. We've written about this publicly before, but the information has been scattered around between different essays, FAQ entries, and license commentaries. This article collects all that information into a single source, to make it easier for people to follow and refer back to. The recommendations below are focused on licensing a work that you create—whether that's a modification of an existing work, or a new original work. These recommendations do not address the issue of combining existing material under different licenses. If you're looking for help with that, please check our license FAQ."
"Today I'm happy to share something we've been working on for a little while: “How to choose a license for your own work” is a comprehensive set of license recommendations for new projects. This page explains what factors are important to consider when making licensing decisions, and suggests specific licenses for different scenarios. If you're starting a new project (whether it's software, documentation, or something else related) and unsure what license to use, you just need this one link to find our recommendations."
"Fedora is in the process of retiring our old "Individual Contributor
License Agreement" (also known as the ICLA or CLA) and replacing it with the new Fedora Project Contributor Agreement (FPCA). All Fedora contributors with accounts in the Fedora Account System
(https://admin.fedoraproject.org/accounts) who have agreed to the old CLA *MUST* agree to the new FPCA by June 17, 2011 to continue contributing to Fedora."
"OpenLogic, Inc., the leading provider of enterprise open source software support, scanning and governance solutions, today announced the results of a scan and license compliance assessment of 635 leading mobile applications. Among other findings, the results show that 71% of Android™, iPhone® and iPad® apps containing open source failed to comply with basic open source license requirements."
"A quarter of the projects available on the European Commission's software development site, the OSOR Forge, 47 out of 183 projects, are published using the EUPL. On Sourceforge, a commercial venture for open source software development based in the US, the licence is now selected by 49 projects. One year ago there were none.
The EUPL was written to be used for distributing open source software applications built for or by the European Commission."
"If open source struck you as strange when you first heard of the concept, you don't know the half of it. Developers, exercising their legal right specify their own licensing terms, have come up with some pretty whacky stuff. Fact or fiction? Some software is only legal to use after you are dead."
"Now, more than ten years later, 1.1's number is up — or at least will be going up. According to Baker, 2010 will be the year of the revision, with Mozilla seeking public comment from community members on what the next version of the widely-used license should say. She notes that Mozilla has received a great deal of input on the license in the past decade, and will utilize it, along with preliminary comments from the community, to create a working draft from which further comment will stem."
"Where we do see dual licensing used, it is more often in enabling users that are unwilling or unable to use the GNU GPL to make use of the underlying code. In that way, dual licensing can be used to serve two different user groups, rather than attempting to cross- or up-sell open source users with a commercial version."
"For instance, beyond open source's licensing components is the idea of its community, which in many cases can be the ultimate arbiter of the success or failure of an open source effort: Simply making an application available under an open source license may not necessarily be enough for a project to succeed, nor is adopting an open source license some kind of magic pixie dust that you sprinkle onto a project to make it successful."
"This Webinar, presented by Black Duck Software with Karen Copenhaver, partner at Choate Hall & Stewart and Counsel for the Linux Foundation and Mark Radcliffe, partner at DLA Piper and General Counsel for the Open Source Initiative (OSI), will review the top 10 open source licenses, the commonly used terms, incompatibility issues, and best practices for dealing with them."
"OpenLogic has hundreds of projects in its certified library, and over 225 different licenses. While many of these licenses are custom, most are based, at least loosely, on one of the 20 most commonly used. We’ve laid out for you in table form the common features of these 20 licenses, and how they compare to one another on a variety of different features."
Selected Tags
Related Tags
Top Contributors
Groups interested in license
-
Web 2.0 services' terms-of-use
Items: 19 | Visits: 27
Created by: Pavel Drášil
-
opensource
Items: 1 | Visits: 12
Created by: Kazuo Moriwaka
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo
