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

LOC's bagit-java no longer maintained? #166

Open
dmoles opened this issue Dec 4, 2022 · 3 comments
Open

LOC's bagit-java no longer maintained? #166

dmoles opened this issue Dec 4, 2022 · 3 comments

Comments

@dmoles
Copy link

dmoles commented Dec 4, 2022

I ran into this issue while trying to import a BagIt bag containing an accented filename. I notice bagit-java hasn't had a commit since June 2018, and I found it's not that easy to get it building with modern versions of Java.

An alternative, jscancella/bagging, does exist, but as it's GNU AGPL it may be a non-starter for this project. 😕

@mikejritter
Copy link
Contributor

Hi @dmoles, thanks for putting this on our radar. I'm not quite sure what the implications are for this project yet, but I know some previous work I did relied on the LOC bagit library as well and is used by the import-export utility.

@jscancella
Copy link

I ran into this issue while trying to import a BagIt bag containing an accented filename. I notice bagit-java hasn't had a commit since June 2018, and I found it's not that easy to get it building with modern versions of Java.

An alternative, jscancella/bagging, does exist, but as it's GNU AGPL it may be a non-starter for this project. 😕

As I mention in the license for bagging other licenses are available upon request. Just contact me and we can have a conversation about what type of license you need/want.

@whikloj
Copy link
Contributor

whikloj commented Jan 11, 2023

IANAL, so the implications of these two types of licenses co-mingling is not entirely clear to me. Based on this post from the ASF which seems to indicate no GPL licensed code could be distributed as part of an Apache licensed product. But you could distribute a GPL product with Apache licensed code as part of it.

I'll ping @Surfrdan to have the Lyrasis staff have a look, but I am guessing we would need a less-copyleft and more permissive license to avoid altering the existing licensing of Fedora.

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

4 participants