Follow-up Comment #36, sr #110199 (project administration):
First, it isn't clear to me from your comment if you checked all files in your
tarball. When I say 'all' I mean a procedure like find . -type f -print0 |
xargs -o0 $EDITOR and so on, and I implied that you would run it. You should
be able to identify licensing issues without help of Savannah admins in order
to maintain software on Savannah.
Then, I must apologize. I tried to explain one point, but didn't do that
satisfactorily. The point is, there are two classes of license notices: the
notices that refer to the full text of the license, and the notices that _are_
the full text of the license. The former are used for longer licenses like GPL
and Apache 2.0; the latter are used for short lax permissive licenses,
including the Modified BSD license, and in that case, no separate copy of the
license in a dedicated file is needed. As a circumstance that could excuse me
to a degree, I can point out that this is documented on our
[//savannah.gnu.org/maintenance/ValidNotices/ page describing copyright and
license notices] that had already shown up in this support request.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/support/?110199>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
