licensing

I would like to configure my VS2010 so that, every time a new source file is created, a comment preamble (which will contain a license) is included. Our immediate need is for C#, but it would be nice to predefine different comment blocks for different languages (which may be needed because of different comment syntaxes). Is there a 3rd-party plugin for that? Example: /* * This software is licensed under the terms of Blah. * Use of this software is conditional to saying "Blah". */ using System; using System.Collections.Generic; using System.Linq; using System.Text; namespace ConsoleApplication1

I am creating an image containing standard recipes and my owns. I wanted to list the licenses I use in all of the included packages and later check if I can use them for commercial application for example. I had the bad surprise packagegroups have a LICENSE flag already. I noticed it doing: bitbake -e -n -v core-image-minimal | grep "LICENSE" It returns LICENSE=MIT since it is defined in the bb file. But I have no information about all the included packages. This MIT has been put manually in the core-image-minimal.bb, but I'd be interested in all dependencies. I have the same issue for my .bb

I'm currently struggling to understand the Ms-RL (Microsoft Reciprocal License). I read the license four times now, but still I am unsure of the following things: (Regarding especially 3A and 3E of the license) If I use the library, without ANY change, do I have to publish the source code of my application? Is it enough to add the Ms-RL to my own license, mentioning its validity for the used library? UPDATE: Do I have to publish my whole application then under the Ms-RL? From Wikipedia: This Microsoft license allows for distribution of derived code so long as the modified source files are

I have asked similar question for Linux RPM ( Adding License Agreement in RPM package ). Now i have same query for Solaris package. I could not get any helpful link / details if it is possible. But I have found a package which does exactly the same thing but how it has been implemented, its not mentioned. $pkgadd -d . SUNWsamfsr SUNWsamfsu Processing package instance from Sun SAM and Sun SAM-QFS software Solaris 10 (root)(i386) 4.6.5,REV=5.10.2007.03.12 Sun SAMFS - Storage & Archiving Management File System Copyright (c) 2007 Sun Microsystems, Inc. All Rights Reserved. ------------------------

I have a friend who has released code under the GPLv3 and CDDL licenses. I have also heard from someone else that these licenses conflict and invalidate each other. I was wondering if people had any opinion or idea of what that means for a user of this code. (Yes, I know, ask a lawyer; but I'm curious if people have any clues). The problem with dual licensing, either with two open source licenses or with one proprietary and one open source, is the issue of re-merging downstream changes. The other answers are correct. When you download something and it has two license you can choose which one

I have developed an information management system for the company I work for. Now I would like to make a type of licensing system to help prevent anyone from just taking a copy and setting it up on their own home server and using it for whatever purpose. I know perhaps the easiest way to do it is to include a reference to a key stored in a remote file on every single page of the system or something like that, but I think that could be easy to get around with some effort. What is the best way to protect my work? Rory Alsop From the security perspective, the general consensus is that you can't

I would like to know if the Nexus repository manager includes a License manager like Artifactory (with this plugin : http://wiki.jfrog.org/confluence/display/RTF/License+Control ). If there is no way to do that in Nexus via a plugin, how do you manage the licenses of the dependencies of your project (with maven) ? e.g. for a commercial project, I can't include a GPL library into the final artifact (.jar, .war, etc.). The Artifactory functionality can be emulated using the Maven license validator plugin http://code.google.com/p/maven-license-validator-plugin/ The practical problem with both