On Tue, Sep 29, 2009 at 08:32:06PM +1000, Luke Kendall wrote: >As an engineer, it seems inefficient if every company that wants to use >Cygwin first has to spend several days/weeks finding all the licenses >across 2000(?) packages, distilling the license files down into a set, >find any that forbid commercial use, checking that the remaining >licenses are compatible with each other, and *then, finally* checking >each unique license in the usual way.
If this is inconvenient for you, you could always start an effort to develop a tool to check into licenses or you could develop the tool and distribute it yourself. You can't give lip service to understanding that this is a volunteer effort and then talk about inefficiencies. In a volunteer effort, pointing out problems that no one is interested in working on is not apt to make the problems go away. In an open source project, the proven solution for this dilemma is to move from being one of the consumers with a problem to becoming one of the volunteers working towards a solution. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
