[
https://issues.apache.org/jira/browse/CONNECTORS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920568#action_12920568
]
Jack Krupansky commented on CONNECTORS-116:
-------------------------------------------
It would be nice to see a comment about what would be required to add Memex
support back.
I note the following statement in the original incubation submission:
"It is unlikely that EMC, OpenText, Memex, or IBM would grant
Apache-license-compatible use of these client libraries. Thus, the expectation
is that users of these connectors obtain the necessary client libraries from
the owners prior to building or using the corresponding connector. An
alternative would be to undertake a clean-room implementation of the client
API's, which may well yield suitable results in some cases (LiveLink, Memex,
FileNet), while being out of reach in others (Documentum). Conditional
compilation, for the short term, is thus likely to be a necessity."
Is it only the Memex connector that now has this problem?
Do we need do a clean-room implementation for Memex? For any of the others?
FWIW, I don't see a Google Connector for Memex.
> Possibly remove memex connector depending upon legal resolution
> ---------------------------------------------------------------
>
> Key: CONNECTORS-116
> URL: https://issues.apache.org/jira/browse/CONNECTORS-116
> Project: ManifoldCF
> Issue Type: Task
> Components: Memex connector
> Reporter: Robert Muir
> Assignee: Robert Muir
>
> Apparently there is an IP problem with the memex connector code.
> Depending upon what apache legal says, we will take any action under this
> issue publicly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
