@Chris: Makes sense. Seems like a lot of overhead processing to parse files on checkin, plus you'd have to constantly check it in case they change their license.
Might be a nice feature to be able to select from a list of licenses (or other) when creating a repo. Having a list of common open-source licenses with short summaries for each. This could be meta on the repo, or maybe even better, have it produce an initial LICENSE file in the repo for the selected license. Then on check in you only need to hook into changes made to the LICENSE file (or removal of it). Still some overhead, but I doubt people would be changing it that often. Seems like a big request though ;). Just thought it would be nice to see some licensing stats, especially with some of the dual licenses like GNU Affero. On Dec 1, 9:45 pm, Paul Miller <jett...@gmail.com> wrote: > On Dec 1, 8:58 pm, Chris Wanstrath <ch...@ozmm.org> wrote: > > > Right now the only way for us to do this would be to figure it out ... > > What if there were some blessed file (like README) that could be > checked? I find a lot of distributions with a LICENSE file. More > without, sure, but I think people would populate it if they knew it > was being checked. You could make some educated guesses if it wasn't > in a standard format. Hey, the languages detected isn't always 100% > accurate, does the license detector need to be? Presumably this > information is mainly for fun... -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to git...@googlegroups.com. To unsubscribe from this group, send email to github+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/github?hl=en.
