What would that achieve beyond the developer putting a LICENSE in the root of their extension?
We normally only put things in the manifest that need to be machine readable by our system. - a On Sat, Nov 28, 2009 at 7:24 AM, Jens Petersen <juhpeter...@gmail.com> wrote: > Perhaps I missed it but I haven't seen any discussion > about licensing of chrome extensions? > > My suggestion would be to have a "license" > field in manifest.json for including a license file. > Are there some plans for that? > > Jens > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
