Any chance you'd be willing to change licensing to Apache 2.0?

[tballison]

We'd like to add a parser to handle hwp files over on Apache Tika (https://issues.apache.org/jira/browse/TIKA-1731). LGPL is incompatible with a Apache's license and we can't bundle java-hwp as it is currently licensed. Any interest in moving to Apache 2.0? If so, do you have any interest in ongoing support for this library?

[mungeol]

I have sent a e-mail to the author about steps of changing licensing which you mentioned.

[mungeol]

Tim Allison, I have a question.
Is it OK that submitting a license grant without taking care of the LGPL license?
We just ignore it?

[tballison]

I'm not sure exactly what you mean by "taking care of the LGPL license"?

If you mean, "let's just leave it in the file source headers", no. All the source files need to have the Apache license and nothing else, well, except for copyright.

Or, do you mean something else?

[tballison]

I guess the first question...who "owns" this software?

As I look through the headers a bit more carefully with the help of google translate :), it looks like part of java-hwp is a port of https://github.com/cogniti/ruby-hwp/ and https://github.com/cogniti/libghwp/. If so, we'd have to ask @cogniti, if he'd be willing to change his license to Apache.

The other question about "who owns it" is: did @ddoleye put this together on his own time or was he working for a company that "owns it". If a company owns it, then they'll have to sign the license grant...I think.

See http://www.apache.org/legal/resolved.html#category-x for some background.

[ghost]

I confirmed this issue.
For your information, https://github.com/cogniti/libghwp moved https://github.com/cogniti/libhwp
Rendering of the libhwp depends on poppler(GPL), so the license of the libhwp is GPL v2+.
But you can use many files of libhwp(libghwp) under the LGPL expecting rendering parts using poppler. Please copyright notice inside files.
And I agree that java-hwp is licensed under the LGPL or Apache.
@ddoleye, What do you think?

[tballison]

@cogniti, thank you for looking into this, and thank you for libhwp!

I think in order for us to put java-hwp into an Apache project, we'd need to have an Apache license in java-hwp and whatever it was ported from. So, we'd have to ask you to change your licenses on the classes that @ddoleye ported. I realize this would be a pain... Let me check with my colleagues over in Tika-land...

@chrismattmann, is this right?

[chrismattmann]

hey @tballison and everyone. We would just need java-hwp to be a Category A or B license (A preferred) as specified here: http://www.apache.org/legal/resolved.html#category-a

[tballison]

@chrismattmann, thank you!

Two questions:

1. Really, even though java-hwp has components that are a port of code that is LPGL?
2. Do we need a software grant, or is a change of headers sufficient?

For the record, I very much like your answer above. :)

[chrismattmann]

@tballison java-hwp is likely a collective work, which means it can be licensed using any collective work license. As for the portion of the code that is LGPL, that could be stubbed out downstream, or simply removed or turned into an optional dependency. As for #2, no need for an SGA unless the code is to be moved into Tika. Is that the goal? Or are we just trying to depend on this code?

[tballison]

1. If we stubbed out the code that was ported from @cogniti's LGPL code, I don't think we'd have anything left. (@ddoleye, please confirm). Possible ways ahead?
   a) humbly ask cogniti to change his headers to ASL for the classes that are required for java-hwp and then change the headers on java-hwp.
   b) leave everything as is and write a Tika parser that depends on an optional LGPL...I thought we didn't want to do this...
   c) other options?

2. K, no grant necessary because I don't think we'll be moving this into Tika. That's great news. Thank you!

[ghost]

1-a) I will consider it positively.

[ddoleye]

Thank you all for your interest on java-hwp.
Also, sorry for the delayed response.

Frankly speaking, I don't know much about the license issues.
And I couldn't know cogniti's thought on this issue.
So I hesitated showing my opinion.

The code was developed as my company's business.
However, my company has agreed to change to ASL.

If cogniti changes libhwp license to the ASL, then I'll change the license of java-hwp to ASL.

Thank you.

[ghost]

https://github.com/cogniti/libhwp is still under the GPL license. Because I have no time, I can't replace rendering parts using poppler (GPL).
So, I will recover https://github.com/cogniti/libghwp, then I will change its license(LGPL) to dual license (LGPL or ASL). Please wait a few weeks.

[chrismattmann]

thank you @cogniti !

[tballison]

Fantastic! Thank you, @cogniti!

[mungeol]

+1

[ghost]

Now, https://github.com/cogniti/libghwp is dual licensed under the LGPL v3+ or Apache License 2.0
https://github.com/cogniti/libghwp/commit/9b0a7ba2ceaf8f940f95171328875f02a8e23507

Now, https://github.com/cogniti/ruby-hwp is dual licensed under the LGPL v3+ or Apache License 2.0
https://github.com/cogniti/ruby-hwp/commit/f191dd9e6bc779f30518f3f95f1766a1cb93a819

Thank you.

[chrismattmann]

thank you @cogniti !

[tballison]

w00t! Thank you @cogniti !

[ddoleye]

I finally changed the license.
This change correct?

[tballison]

Will take a look. Thank you!

[ghost]

Forget libghwp, ruby-hwp.
Now, the libhwp is dual licensed under the LGPL v3+ or Apache License 2.0.
https://github.com/cogniti/libhwp/commit/92549e4692f3ba1382a3863b899556a9916923e7