From jsquyres at cisco.com  Fri Sep  9 04:15:41 2016
From: jsquyres at cisco.com (Jeff Squyres (jsquyres))
Date: Fri, 9 Sep 2016 10:15:41 +0000
Subject: [OMPI contributors] Fwd: Open MPI contributions
References: <SN2PR15MB0957ACAFCDDF9536582A4539C0FA0@SN2PR15MB0957.namprd15.prod.outlook.com>
Message-ID: <A5B8B277-3736-4D6A-9B07-795C872B5918@cisco.com>

FYI.  I have filed a copy of the PDF in the Google Drive.


Begin forwarded message:

From: Pieter Noordhuis <pietern at fb.com<mailto:pietern at fb.com>>
Subject: Re: Open MPI contributions
Date: September 9, 2016 at 2:24:41 AM EDT
To: "Jeff Squyres (jsquyres)" <jsquyres at cisco.com<mailto:jsquyres at cisco.com>>
Cc: Andrew Tulloch <tulloch at fb.com<mailto:tulloch at fb.com>>, Hussein Mehanna <hussein at fb.com<mailto:hussein at fb.com>>

Hi Jeff,

You can find the signed agreement attached. Both Andrew and myself are listed as contributors for now, we can expand as needed.

Next step for me is to find some time and rebase and split the patches on top of master. Then we can work our way back one after the other on top of 2.x and 1.x where we deem fit.

You mentioned an OpenMPI contributors mailing list earlier. Is there a list in particular you recommend I join?

Thanks,
Pieter
________________________________
From: Jeff Squyres (jsquyres) <jsquyres at cisco.com<mailto:jsquyres at cisco.com>>
Sent: Wednesday, September 7, 2016 12:01:31 PM
To: Pieter Noordhuis
Cc: andrew at tullo.ch<mailto:andrew at tullo.ch>
Subject: Re: Open MPI contributions

That would be perfect; thank you!

> On Sep 7, 2016, at 2:59 PM, Pieter Noordhuis <pietern at fb.com<mailto:pietern at fb.com>> wrote:
>
> Hi Jeff,
>
> We're very close. Likely have it for you by EOW. Can I just email the PDF to you?
>
> Cheers,
> Pieter
> From: Jeff Squyres (jsquyres) <jsquyres at cisco.com<mailto:jsquyres at cisco.com>>
> Sent: Tuesday, September 6, 2016 6:19:27 AM
> To: Pieter Noordhuis
> Cc: andrew at tullo.ch<mailto:andrew at tullo.ch>
> Subject: Re: Open MPI contributions
>
> Hey guys --
>
> Any word on this, perchance?  In a perfect world, you could get the agreement signed in the near future.  If that's not going to be easy, we'd like at least a nod from you that your employer is aware that you're contributing to Open MPI and is ok with it.
>
> Thank you!
>
>
> > On Aug 29, 2016, at 4:14 PM, Jeff Squyres (jsquyres) <jsquyres at cisco.com<mailto:jsquyres at cisco.com>> wrote:
> >
> > On Aug 29, 2016, at 12:13 PM, Pieter Noordhuis <pietern at fb.com<mailto:pietern at fb.com>> wrote:
> >>
> >> Thanks for your note. Glad to help out here. We're running IPv6 at Facebook so needed this patch to run OpenMPI.
> >>
> >> We do a lot of open source and definitely would like these patches to land upstream. You mention the Apache CLA, but I thought OpenMPI was BSD licensed. Is the agreement only used for copyright assignment, or patent license, or...?
> >
> > Yes, it's basically the Apache CLA, but with s/Apache/Open MPI/g.  IANAL and this is not legal advice, so have your own legal people look at it.  There's no copyright assignment -- it's yours, you're just essentially agreeing that we can distribute it under the BSD license.
> >
> > That being said, we stole the language from the Apache CLA about 10 years ago, and I don't remember if we also s/Apache license/BSD license/g.  Regardless, our license is BSD -- not Apache.
> >
> >> Let me check in with some folks and ping back. Once this is cleared I can rebase the patches on top of master, send a PR, and then work on backporting them (or a subset) to the 1.x and 2.x trees.
> >
> > Great -- thank you!
> >
> > BTW, the reference I made on the issue about the conversation we're having on the core mailing list was inspired by your contributions.  We've had a fuzzy "we'll take 'small' patches from people without paperwork" before this, but the definition of "small" was fairly vague / subjective.  That being said, as I mentioned above, our CLA was setup a long time ago -- and nowadays, "signed-off-by" notices in commit that implicitly agree to redistribution terms are somewhat common.  Your contributions have inspired a re-evaluation of whether we need the formal CLA, or whether the "signed-off-by" notices are sufficient (or perhaps some kind of blend of the two to handle habitual contributors and occasional contributors).
> >
> > --
> > Jeff Squyres
> > jsquyres at cisco.com<mailto:jsquyres at cisco.com>
> > For corporate legal information go to: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cisco.com_web_about_doing-5Fbusiness_legal_cri_&d=DQIFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=tuQ8EqTFx1hLmZlGmHhKyQ&m=tAZqTa-aFA1ha4FZBfVvpslxSecouJXdF96VYStpkqs&s=RiZccUhusoNN6Whsj8BNZpYMzaedafgiwPbkmvYY6tk&e=
> >
>
>
> --
> Jeff Squyres
> jsquyres at cisco.com<mailto:jsquyres at cisco.com>
> For corporate legal information go to: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cisco.com_web_about_doing-5Fbusiness_legal_cri_&d=DQIFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=tuQ8EqTFx1hLmZlGmHhKyQ&m=tAZqTa-aFA1ha4FZBfVvpslxSecouJXdF96VYStpkqs&s=RiZccUhusoNN6Whsj8BNZpYMzaedafgiwPbkmvYY6tk&e=
>


--
Jeff Squyres
jsquyres at cisco.com<mailto:jsquyres at cisco.com>
For corporate legal information go to: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cisco.com_web_about_doing-5Fbusiness_legal_cri_&d=DQIFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=tuQ8EqTFx1hLmZlGmHhKyQ&m=hcEpKgvnfme_V38t1osSKFK6muKp5gUglMAQSrayhXc&s=qjppGTdqiT4iMoLYuPhMLfXYrOP7QYa9bUatXGSGzgw&e=

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rfd.newmexicoconsortium.org/pipermail/ompi-contributors/attachments/20160909/356fed6a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4665_001.pdf
Type: application/pdf
Size: 3402250 bytes
Desc: 4665_001.pdf
URL: <http://rfd.newmexicoconsortium.org/pipermail/ompi-contributors/attachments/20160909/356fed6a/attachment-0001.pdf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rfd.newmexicoconsortium.org/pipermail/ompi-contributors/attachments/20160909/356fed6a/attachment-0001.htm>