www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-253) Apache Beam - Moving Python SDK to Beam
Date Fri, 13 May 2016 20:43:13 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283126#comment-15283126
] 

Sean Busbey commented on LEGAL-253:
-----------------------------------

You should run this through your mentors. Dealing with these kinds of code licensing issues
is one of the things they're present for. (The answer will depend on your particular SGA for
the initial donation.)

> Apache Beam - Moving Python SDK to Beam
> ---------------------------------------
>
>                 Key: LEGAL-253
>                 URL: https://issues.apache.org/jira/browse/LEGAL-253
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: James Malone
>
> Hello,
> When Beam entered incubation we (Google) mentioned we wanted to also include the Dataflow
Python SDK in Beam. We'd like to go ahead and do that now. The Python SDK is currently in
the following repo and ASL2 licenced:
> https://github.com/GoogleCloudPlatform/DataflowPythonSDK
> My question here - when we entered incubation we explicitly noted the repositories for
the code we were pulling in. Since this will be a pretty large inclusion into Beam, do we
need to amend any donation agreements or can we pull this code into the project without additional
legal paperwork?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message