Page MenuHome

Licenses: Attribution document
ClosedPublic

Authored by Dalai Felinto (dfelinto) on Dec 9 2020, 4:49 PM.

Details

Summary

Generated using:
https://github.com/amzn/oss-attribution-builder

This is based on the libraries in extern and the svn libraries.

For the libraries in extern the README.blender was used as reference.
For the libraries in svn I used cmake/versions.cmake.

Note that the crediting is a bit of hit and miss. For some projects this
is very clear, while for others I had to do some digging. Either way I
gave my best shot.

The sources to (re-)generate this file is local at the moment. But it
should be moved to our infra-structure at some point.

Diff Detail

Repository
rB Blender

Event Timeline

Dalai Felinto (dfelinto) requested review of this revision.Dec 9 2020, 4:49 PM
Dalai Felinto (dfelinto) created this revision.

@James Monteath (jmonteath) FYI, this is the attribution document that we need to update every release (or even better, everytime a license is updated in svn lib or extern). Even before finding a way to set oss-attribution-builder online, it would be nice to find a way to transfer my local database to somewhere safe since it was a lot of work to fill this in. But I don't even know where is the database file stored

@Dalai Felinto (dfelinto) If you used docker, then it is in a volume.

There are few way to export this. Will need some time to figure it out.

Will put more info in the notion task for the migration details.

The contents of this seems fine.

I guess you'll mention this on:
https://wiki.blender.org/wiki/Process/Release_Checklist

This revision is now accepted and ready to land.Dec 9 2020, 6:15 PM

When committing this, I think it's also good to mention the motivation for doing this.

Right I will add the motivation. And yes, the plan is to mention that this needs to be updated as part of the release checklist. I will commit tomorrow. Thanks for the review Brecht

I was thinking here, I will leave this sitting a bit. I sent this for a rough review, and will wait to hear back before committing it.

@James Monteath (jmonteath) I think perhaps it is overkill to host the service at all times given that we may not need it that often. Another alternative may just be for us to store the database somewhere in blender (e.g., //tools) with a copy of the attribution app, so that developers can update it when needed, and upload the updated database.

I don't know, could use the 2 cents from others: Platforms, Builds, Tests & Devices

We could also just manually update this text file, at least it's not obvious to me that running some service is more convenient.

This revision was automatically updated to reflect the committed changes.

For the records, I also included a README in the //extern about the attribution document: cef5d0923b79.