Add copyright to transformers integration script about mltb HOT 9 CLOSED

Thanks @PhilipMay will submit a PR for this now

from mltb.

Also see here:

from mltb.

As a sidenote, OMLflowCallback extends the transformers MLflowCallback.

As far as I've been able to read, derivative works of an Apache license can be distributed under different license terms, as long as they are compliant with the Apache license terms. BSD-2 appears to be compliant with the Apache terms

from mltb.

This would be a good template:

# Copyright (c) <year> by <name>
# This software is distributed under the terms of the BSD 2-Clause License.
# For details see the LICENSE file in the root directory.

If the contribution was not private but in context of your company add
, <company> after <name>

from mltb.

I am realy not sure when work is an derivative.

Where is the line between derivative and "just using"?
Is inheritance "just using" or derivative ? I dunno...

@twolffpiggott do you have an idea?

I mean when I save a file I use the underlying OS.
Which might be Linux or Windows, and so on...

When is the integration so tight that "using" changes to "derivative work"?

from mltb.

Maybe @RoHech has an idea?

from mltb.

I am realy not sure when work is an derivative.

I am also not sure exactly where to draw this distinction.

I would classify the OMLflowCallback as derivative because it does not just inherit from the TrainerCallback, but exposes an interface modelled directly on the MLflowCallback, extended to work with our class and with some added optionality.

from mltb.

@twolffpiggott this is interesting: https://en.wikipedia.org/wiki/Apache_License#Licensing_conditions

The Apache License is permissive; unlike copyleft licenses, it does not require a derivative work of the software, or modifications to the original, to be distributed using the same license.

from mltb.

done

from mltb.