...
Action item for next week to issue a CFP
Licensing
Botimer
Armintor and Botimer discussed this earlier on Slack
Looking into details for ASF...operating and treating documentation of copyright
Operate similarly to how Samvera does
CLA's was borrowed heavily with a preamble specific to Samvera
We do not assign copyright
Authors to code retain copyright
Group retains the composite
Combination itself is a work in its own right
ASF: One copyright statement for derivative work (combined thing)
There is an open question...can we make a copyright statement for the collective work
There are examples would lead us to believe that "Samvera Community" would be okay with a separate list of authors
There is a challenge with existing practices...commit log uses an e-mail address
Might resolve cleanly in terms of GitHub...good tracking for CLAs and their employers
Contributions are work-for-hire
But, still not clear
There are two courses
Check with Michael Klein as product owner who is in the copyright statement for MIT on BE
Change to ASF
Theoretically could change the licenses without including MIT, but best to include the MIT license and specify that this exclusively covers previous releases
Ensure that this is consistent with other Gems in Samvera
Other action
Concise summary of what we are seeing...and work we are seeing to get to a simple practice towards evaluating projects as following guidelines
Ensuring that file contents (e. g. the top portion of a notice document is the same line)
List of institutions who want specific adjustments for the notice file (e. g. Trustees of...)
This way the guidelines are simple, can be readily checked
Provide a single file where additional copyright holders are specified
Pendragon:
How are we all over the board now?
Botimer:
Nobody has challenged the current copyright statement
Headers in certain files might still have copyright ownership information (e. g. jQuery plugin files with this information)
Would like to have one formula...for structuring this content and placing it within specific files
We should have one descriptive file...without consulting an external source (e. g. the git history)
Notes that the tarball won't have that
Get BE over to Apache license
Summarize the inconsistency, make a proposal for better consistency to vet amongst ourselves and take to the Partners