[ https://issues.apache.org/jira/browse/TIKA-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738660#comment-14738660 ]
Tim Allison edited comment on TIKA-1731 at 9/10/15 12:26 PM: ------------------------------------------------------------- Great. Thank you so much! It would be helpful to keep this discussion in the open via the issue I opened [here|https://github.com/ddoleye/java-hwp/issues/2]. If ddoleye is willing to offer ongoing support for java-hwp, then we can move ahead with the following. The lack of response to [this|https://github.com/ddoleye/java-hwp/issues/2] and [this|https://github.com/ddoleye/java-hwp/issues/3] has not been encouraging...I know, we're all busy, though. [~gagravarr] and [~chrismattmann], let me know if I'm missing any steps. # The owner of the software can submit a [license grant|https://www.apache.org/licenses/software-grant.txt] to secret...@apache.org and cc dev@tika.apache.org. If ddoleye wrote the software on his own time, then he owns it. If he was working for a company while writing the software, then the company needs to sign the software grant. # ddoleye then changes all headers and other license information in the source code to [ASL 2.0|http://www.apache.org/licenses/LICENSE-2.0.txt]. # ddoleye then pushes his code to maven central. See Nick's links [here|https://issues.apache.org/jira/browse/TIKA-1513?focusedCommentId=14278678&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14278678] # We at Tika wrap the parsers. We'll need help with test docs and unit tests. We may also have some push requests to java-hwp to make the integration easier on our end. # We'll need help with ongoing maintenance and test docs. Wait, [~chrismattmann], do we need a software grant if we aren't taking over the code...just importing from Maven? Would a change of headers be sufficient _if_ ddoleye is the sole contributor and a company doesn't _own_ the software? was (Author: talli...@mitre.org): Great. Thank you so much! It would be helpful to keep this discussion in the open via the issue I opened [here|https://github.com/ddoleye/java-hwp/issues/2]. If ddoleye is willing to offer ongoing support for java-hwp, then we can move ahead with the following. The lack of response to [this|https://github.com/ddoleye/java-hwp/issues/2] and [this|https://github.com/ddoleye/java-hwp/issues/3] has not been encouraging...I know, we're all busy, though. [~gagravarr] and [~chrismattmann], let me know if I'm missing any steps. #. The owner of the software can submit a [license grant|https://www.apache.org/licenses/software-grant.txt] to secret...@apache.org and cc dev@tika.apache.org. If ddoleye wrote the software on his own time, then he owns it. If he was working for a company while writing the software, then the company needs to sign the software grant. #. ddoleye then changes all headers and other license information in the source code to [ASL 2.0|http://www.apache.org/licenses/LICENSE-2.0.txt]. #. ddoleye then pushes his code to maven central. See Nick's links [here|https://issues.apache.org/jira/browse/TIKA-1513?focusedCommentId=14278678&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14278678] #. We at Tika wrap the parsers. We'll need help with test docs and unit tests. We may also have some push requests to java-hwp to make the integration easier on our end. Wait, [~chrismattmann], do we need a software grant if we aren't taking over the code...just importing from Maven? Would a change of headers be sufficient _if_ ddoleye is the sole contributor and a company doesn't _own_ the software? We'll need help with ongoing maintenance and test docs. > Try to integrate java-hwp into Tika > ----------------------------------- > > Key: TIKA-1731 > URL: https://issues.apache.org/jira/browse/TIKA-1731 > Project: Tika > Issue Type: New Feature > Reporter: Tim Allison > Priority: Minor > > Now that we have detection working for hwp files, it would be great to add a > parser. > [java-hwp|https://github.com/ddoleye/java-hwp] looks like a promising > candidate. We'd need to ask ddoleye about a potential change in license and > then interest in maintenance + pushing to maven. > Any other candidates? -- This message was sent by Atlassian JIRA (v6.3.4#6332)