[ Charset UTF-8 unsupported, converting... ]
> On Mar 25, 2018 1:09 PM, "Benjamin Kaduk" <bjkf...@gmail.com> wrote:
>
> I am surprised that no one has yet quoted the commit message from r325966
> when the first SPDX tags appear to have been added to base:
>
> We are gradually adopting the specification, noting
> that the tags are considered only advisory and do not, in any way,
> superceed or replace the license texts.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Here a SPDX tag is being used to stand in place, ie replace, the
license text.
> (There was also some internal discussion around the same time, which I of
> course cannot quote here.)
>
>
>
> Right. For cases where both are present, the text controls. But when it's
> just there alone, there is no ambiguity.
There is ambiguity, as your replacing the license text with a tag in
direct conflict with the documented status of SPDX tags.
That is a HUGE ambiguity.
Your also creating a small handful of files that seem to be in conflict
with the projects standard MO for 25 years.
Now, if you want to take this change to @developers as a proposal, and
actually get legal advice on the aspects of this, I am all ears, but please
do not just go making decisions that are contray to current practice
without that.
> It would certainly help with the slightly different wording issue if we did
> this more often. I may do it to all my code in the tree. I'm careful about
> this stuff, and i have at least three variations in the tree for no good
> reason...
>
> Warner
--
Rod Grimes rgri...@freebsd.org
_______________________________________________
svn-src-head@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
