[theme-reviewers] First review and I'm lost - font license

[Otto]

In general, the license for all included elements of the package
should be specified in a license.txt file that is included in the root
of the theme, or in the readme.txt file, or both. It's fine to include
license information next to specific pieces in their own folders too,
but for simplicity of finding out what's included and such, having it
all in a single place is a good idea too.

There is no standard on this, as such, but the general rule of thumb
in any open source project is to have a LICENSE or LICENSE.TXT file or
something like that, laying it all out.


-Otto


On Fri, Oct 11, 2013 at 6:10 PM, Daniel <danielx386 at gmail.com> wrote:
> And maybe add a note in the guidelines saying that there should be a
> license.txt file in that folder with details about the license. And +1
> what Emil said.
> Regards,
> Daniel Fenn
>
>
>
>
>
>
> On Sat, Oct 12, 2013 at 10:07 AM, Emil Uzelac <emil at uzelac.me> wrote:
>> For the license sake and to make it easier is it safe to say that we can
>> start recommending /fonts/ when including the fonts? I've been doing that
>> myself as well and it is good practice. Many already do /js/, /css/ anyway
>> :-)
>>
>> On Oct 11, 2013 6:02 PM, "Justin Tadlock" <justin at justintadlock.com> wrote:
>>>
>>> Just as a general rule for myself, whenever I bundle resources like fonts,
>>> I usually do them like the following (Genericons example):
>>>
>>>     /fonts
>>>         /genericons
>>>             /genericons-regular-webfont.eot
>>>             /genericons-regular-webfont.svg
>>>             /genericons-regular-webfont.ttf
>>>             /genericons-regular-webfont.woff
>>>             /license.txt
>>>
>>> It's so much easier to find the appropriate license that way.  Not to
>>> mention, other theme authors can do a direct copy-paste of that entire
>>> folder and have everything they need for their own theme.
>>>
>>> If everyone would follow that, it make life a lot easier.  Of course, I'm
>>> always fine with stating the font/resource license in the theme's
>>> readme.txt, but it'd be nice if we promoted using some sort of standard
>>> convention like the above.
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers