Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup license headers and mycila #4

Closed
ruebot opened this issue Jul 6, 2017 · 3 comments
Closed

Setup license headers and mycila #4

ruebot opened this issue Jul 6, 2017 · 3 comments
Assignees

Comments

@ruebot
Copy link
Member

ruebot commented Jul 6, 2017

What do we do with the existing license headers that mention warcbase? Also, do we need a header for the LICENSE file? If so, should we add each of our universities, or pull in the entire history of the project, or just our names?

@ruebot ruebot self-assigned this Jul 6, 2017
@ruebot
Copy link
Member Author

ruebot commented Jul 6, 2017

^^ @lintool @ianmilligan1 thoughts?

@ianmilligan1
Copy link
Member

My gut is to just go with our names for now?

@lintool
Copy link
Member

lintool commented Jul 10, 2017

The header I've used for Warcbase is:

/*
 * Warcbase: an open-source platform for managing web archives
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

Let's just change to "Archives Unleashed Toolkit: XXXXXX", where XXXX is a short descriptive phrase.

Let's not worry about assigning copyright to a particular person, university, etc. It's Apache 2 anyway, so it doesn't matter...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants