[MDSAL-123] A request to add a license header to yang-tool-generated files (binding spec. v1) Created: 15/Dec/15  Updated: 16/Mar/19

Status: Confirmed
Project: mdsal
Component/s: Binding codegen
Affects Version/s: None
Fix Version/s: None

Type: New Feature
Reporter: Phil Robb Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
blocks MDSAL-138 A request to add a license header to ... Resolved

 Description   

Hello:

Would it be possible for you to add a Copyright & License headers to the top of the files that YangTools generates? This will be very helpful to our end users. Remember that a file that contains code and no license does not allow a recipient of such a file to anything with it. The license gives them written permission to do something. Right now, it is implied that, since the file came from ODL, that it is Eclipse licensed. It would be much better to make it so that it was explicit.

I would leave implementation details to you, but I can see the following possible scenarios:

  • At a minimum, it would be nice to have a command line flag to turn on license generation. With that flag on you could designate the copyright to "OpenDaylight Project" and the standard "Eclipse Public License" header.
  • A more advance implementation would allow the user to include the copyright holder (Cisco, HP, Red Hat, etc) instead of, or in addition to a default of "OpenDaylight Project".
  • A further advanced implementation would allow for different license banner text (other than the Eclipse Public License text) in the event folks want to use YangTools for code generation outside of the scope of the OpenDaylight Project.

Is this possible to do at some point in the not-too-distant future?... Maybe a feature request for Boron?



 Comments   
Comment by Ryan Goulding [ 06/Jul/16 ]

https://git.opendaylight.org/gerrit/#/c/41438/

Comment by Martin Ciglan [ 17/Oct/16 ]

Could you please update status of this bug? Many thanks.

Generated at Wed Feb 07 20:08:42 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.