From dev-return-3009-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Tue Jun 5 22:10:56 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id AAF85180625 for ; Tue, 5 Jun 2018 22:10:55 +0200 (CEST) Received: (qmail 38592 invoked by uid 500); 5 Jun 2018 20:10:54 -0000 Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mxnet.incubator.apache.org Delivered-To: mailing list dev@mxnet.incubator.apache.org Received: (qmail 38577 invoked by uid 99); 5 Jun 2018 20:10:54 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jun 2018 20:10:54 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A388C180513 for ; Tue, 5 Jun 2018 20:10:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.899 X-Spam-Level: * X-Spam-Status: No, score=1.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WmfV-n14WsOw for ; Tue, 5 Jun 2018 20:10:52 +0000 (UTC) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 1C8B35F11F for ; Tue, 5 Jun 2018 20:10:52 +0000 (UTC) Received: by mail-lf0-f49.google.com with SMTP id q11-v6so5532092lfc.7 for ; Tue, 05 Jun 2018 13:10:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=WFJQR6S3yoo1lsmVqW4Akc3+rSyF4dEdlje3EQ5UcC8=; b=GR8J9ALAfBwUUhss0jrsTKXA0lq9qBAFhQ6W/VdSggBNOwvVxhnS8OquQ9P9NHT3Lg UNPAge2BuiuxGVpfxrtOgE/ZkTDxeBoIl7vJKOumPE89nsHVCKPpkRahCuHzJHHPWkUp GbV0LSOo9zJKe4YPsIw71I3w6wUB31W7QIPajA2ealDaC0DFdnwtI8qMWvqUJL2lVIbY S2vd4dbV4pPITTrPo+IqRNGFT6X55VQodFVERudXUPHYyQmE/WkJJ1zColncZXTdjvxz eXO35R0fXHt6NBGN8FDYSNrHN6tLZgVFCAJGgwJ8k9Ui/MxVsLZl0VA+mbbdYl/tF5xz rOHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=WFJQR6S3yoo1lsmVqW4Akc3+rSyF4dEdlje3EQ5UcC8=; b=XSU8yXPkF9fNSyeSl7gxU/llWPdNHxYdRcRHC9n2il2hziXcnaMGqqbk/ROgo9xmi/ DvcQalTcwi47OXgje9h9IpQHv9lo6f287G0h2Kmm42uUpKKe/AkbHhTWucFhO/+s7Pm9 pXvvlZ+DrBYKzV1BP1m6TcsHgIhTEvoKpS1f12C2fZqziH9I00BYd4oewuDAPytFB13I nELEpr9m0vk72NVu0fX/3WTQflE6Jz+PmxE5qKb3kpI8Mycm7gTaTulWNi79PnOmir7z I2WTVsQOko9gw1T+/q6SA1ikPE/jHF695Qwlp70Gthotr8dCdXHHugRJUg3hXoPCkVr5 rFKA== X-Gm-Message-State: APt69E3uSsl/uu+o8byodm3x9jqnB/hd9fQ0ixTpxtRs/UQsvHWlfCWv wnBNR1mzWqlTqwB8HkIbNGK316HHKHMs1IMLKjI= X-Google-Smtp-Source: ADUXVKK525fGE41VJdbqbB3NTFSAhxkZN1cDyvCCNc9XcodQXdnWqG35vRt49mARurYYl30fER72pYSLFfGCBL/WGvs= X-Received: by 2002:a2e:9b91:: with SMTP id z17-v6mr36031lji.121.1528229451189; Tue, 05 Jun 2018 13:10:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Marco de Abreu Date: Tue, 5 Jun 2018 22:10:39 +0200 Message-ID: Subject: Re: ICLA? To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="00000000000092d18b056deaa529" --00000000000092d18b056deaa529 Content-Type: text/plain; charset="UTF-8" Henry, was this document only related to the migration towards Apache or do we have to keep it up to date? I've heard that sometimes every contributor has to sign it before a PR can be accepted. I have seen other communities that use a bot to keep track of signed ICLA documents, but I don't know if we have to follow that. We know that Nvidia emoloyees, for example, are not allowed to sign these documents. -Marco Steffen Rochel schrieb am Di., 5. Juni 2018, 19:15: > Hi - > is https://cwiki.apache.org/confluence/display/MXNET/ICLA+Progress up to > date? > Can I help? > > Regards, > Steffen > --00000000000092d18b056deaa529--