On Wed, 2009-10-14 at 17:36 -0700, Luke Kanies wrote: > How would we manage the list of allowed licenses? The goal is to > provide consistency, right, not just restrict what license people can > use?
It doesn't have to be supported by tooling; a Wiki page similar to the one that Fedora has (or just pointing to that) would be good enough. > So do we just have an array somewhere that we update when we discover > a new license we want to use? Or can we seed it with the valid > licenses in RPM? The fixed license short names are a convention; if you use an unknown license, you can still build the RPM. Some of the rpm checking tools like rpmlint will complain though - I don't think anything like that needs to be there for puppet modules, as long as the convention is followed by people (and the ones not following will get a polite reminder from whoever packages the module as an RPM) > As to the file list, I'm not really ready to do that. I think the > right answer is some easy way to generate it from git or ruby; having > a fixed file list is just fugly. Yeah, I mostly listed that for completeness - it's a very low priority, as long a we can easily tell documentation files from 'normal' files because of their name (again, based on conventions) David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
