Re: [Coin] Fwd: [hackathon] IETF 106 Hackathon

<emile.stephan@orange.com> Wed, 18 September 2019 07:56 UTC

Return-Path: <emile.stephan@orange.com>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2D40120098 for <coin@ietfa.amsl.com>; Wed, 18 Sep 2019 00:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEI0_ixnJYgz for <coin@ietfa.amsl.com>; Wed, 18 Sep 2019 00:56:21 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4582C120125 for <coin@irtf.org>; Wed, 18 Sep 2019 00:56:21 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 46YC3R5hF1z8tPB; Wed, 18 Sep 2019 09:56:19 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 46YC3R4k9Tz1xvb; Wed, 18 Sep 2019 09:56:19 +0200 (CEST)
Received: from OPEXCAUBM44.corporate.adroot.infra.ftgroup ([fe80::e8a4:8bb:d7c2:f4e2]) by OPEXCAUBM24.corporate.adroot.infra.ftgroup ([fe80::b43f:9973:861e:42af%21]) with mapi id 14.03.0468.000; Wed, 18 Sep 2019 09:56:19 +0200
From: emile.stephan@orange.com
To: Alessandro Bassi <alessandro@bassiconsulting.eu>, Marie-Jose Montpetit <marie@mjmontpetit.com>
CC: "coin@irtf.org" <coin@irtf.org>
Thread-Topic: [Coin] Fwd: [hackathon] IETF 106 Hackathon
Thread-Index: AQHVbZEdPpdwOipzVk+lT2hLW7A6c6cwKcMAgADoAyA=
Date: Wed, 18 Sep 2019 07:56:19 +0000
Message-ID: <1004_1568793379_5D81E323_1004_262_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931EE3666@OPEXCAUBM44.corporate.adroot.infra.ftgroup>
References: <CAPjWiCSXoRhn36Q0fwmJuJ+xzdYQeTBpijOS_t0SPVMsR=VBDA@mail.gmail.com> <07346901-D75F-4E02-AB52-DE0C291C1FDA@bassiconsulting.eu>
In-Reply-To: <07346901-D75F-4E02-AB52-DE0C291C1FDA@bassiconsulting.eu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: multipart/alternative; boundary="_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931EE3666OPEXCAUBM44corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/yZtX-7jB3cdZyXiA1mH0rodrJDk>
Subject: Re: [Coin] Fwd: [hackathon] IETF 106 Hackathon
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 07:56:25 -0000

+1

De : Coin [mailto:coin-bounces@irtf.org] De la part de Alessandro Bassi
Envoyé : mardi 17 septembre 2019 22:05
À : Marie-Jose Montpetit
Cc : coin@irtf.org
Objet : Re: [Coin] Fwd: [hackathon] IETF 106 Hackathon

I’m not sure if I will be in Singapore but for sure I think it’s worth organising it
Sent from my iPad

On Sep 17, 2019, at 9:49 PM, Marie-Jose Montpetit <marie@mjmontpetit.com<mailto:marie@mjmontpetit.com>> wrote:
Since we had a great success in Montreal I think we should have another version of our hackaton in Singapore. Who will be there?

mjm

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory
mariejose@mjmontpetit.com<mailto:mariejose@mjmontpetit.com>
mariejo@mit.edu<mailto:mariejo@mit.edu>


On September 17, 2019 at 3:26:01 PM, Charles Eckel (eckelcu) (eckelcu@cisco.com<mailto:eckelcu@cisco.com>) wrote:
Hi Folks,

If you have not already, now is a good time to start making your plans for the hackathon.
Registration is free but required, and it is separate from registering for the IETF meeting.
More info and links to register here https://www.ietf.org/how/runningcode/hackathons/106-hackathon/.

You can check the wiki for a growing list of projects. We welcome and encourage champions for new projects, too.
https://trac.ietf.org/trac/ietf/meeting/wiki/106hackathon

Champions should:
- Before the Hackathon:
- Update wiki with details about their project
- Share ideas and any preparation materials or requirements with potential attendees via the hackathon list
- Recruit participants from associated working groups, open source projects, etc.
- At the Hackathon:
- Make themselves available to answer questions and help others
- Hack on things themselves in their copious free time
- Champions will have table signs on their table identifying their project (paper and pens are provided with plastic table top signs). Optionally, champions may create and display posters on flip charts with additional information on their project.

In addition to adding your project to the wiki, please send a note to hackathon@ietf.org<mailto:hackathon@ietf.org> and related IETF working groups, etc., where people might be interested.

Cheers,
Charles



_______________________________________________
hackathon mailing list
hackathon@ietf.org<mailto:hackathon@ietf.org>
https://www.ietf.org/mailman/listinfo/hackathon
--
Coin mailing list
Coin@irtf.org<mailto:Coin@irtf.org>
https://www.irtf.org/mailman/listinfo/coin

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.