RE: IETF Hackathon at IETF 92, March 21-22, Dallas, TX

James Gannon <james@cyberinvasion.net> Wed, 25 February 2015 23:34 UTC

Return-Path: <james@cyberinvasion.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922A01A00F9 for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 15:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 NCoOdojf4hpy for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 15:34:51 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0755.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::755]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 270211A0067 for <ietf@ietf.org>; Wed, 25 Feb 2015 15:34:51 -0800 (PST)
Received: from DB3PR06MB219.eurprd06.prod.outlook.com (10.141.2.20) by DB3PR06MB218.eurprd06.prod.outlook.com (10.141.2.19) with Microsoft SMTP Server (TLS) id 15.1.93.16; Wed, 25 Feb 2015 23:34:32 +0000
Received: from DB3PR06MB219.eurprd06.prod.outlook.com ([169.254.14.131]) by DB3PR06MB219.eurprd06.prod.outlook.com ([169.254.14.131]) with mapi id 15.01.0093.004; Wed, 25 Feb 2015 23:34:32 +0000
From: James Gannon <james@cyberinvasion.net>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Dean Bogdanovic <deanb@juniper.net>, "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Subject: RE: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Thread-Topic: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Thread-Index: AQIEMCxN/LT4F0GRHvFvNCsvNr5euQLdDr+zAYF7r5QCZpItWgJs3NhyAizBDpcBxP+OMgCdxsobAlmdY+UCfE5VNAIqwN2fAfxGGGYBs1aQMJvWjJCwgAABwACAAA5PgIAAFn0AgAADvYCAAADh0A==
Date: Wed, 25 Feb 2015 23:34:32 +0000
Message-ID: <DB3PR06MB219BBDB77EFFF77E513807BBF170@DB3PR06MB219.eurprd06.prod.outlook.com>
References: <20150224170152.6224.60832.idtracker@ietfa.amsl.com> <09B0A2B7-7D6B-4365-B58C-AAD97C3BE73D@lucidvision.com> <B32A64D5-0B07-4E01-92B1-DEAF21002EE7@netapp.com> <D1132FAF.3E752%eckelcu@cisco.com> <54EDF486.20000@gmail.com> <D275D180-272B-43C7-BDF0-FE2B438DEB60@lucidvision.com> <4723EB73-47F2-4408-ADAA-EF78A6A14FDA@nominum.com> <54EE0865.4090101@gmail.com> <CAHw9_iKA7bgZH6iJLw1y7=qz6MJDePgUbCeOtHXnaajCKshRnw@mail.gmail.com> <D1136BA7.3E85D%eckelcu@cisco.com> <54EE2DD7.1030408@gmail.com> <D1136F2B.3E87C%eckelcu@cisco.com> <54EE3016.3040106@gmail.com> <DB3PR06MB219F1410E358FF8608F1340BF170@DB3PR06MB219.eurprd06.prod.outlook.com> <54EE389A.3080904@gmail.com> <FE093242-C4C9-4602-B576-50391F3B1437@lucidvision.com> <D656F2B2-E848-4444-96EB-0D67653A4A46@juniper.net> <D1139888.3E952%eckelcu@cisco.com>
In-Reply-To: <D1139888.3E952%eckelcu@cisco.com>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [86.42.132.89]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=james@cyberinvasion.net;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB3PR06MB218;
x-microsoft-antispam-prvs: <DB3PR06MB218ECE5C156E1F434D56E918D170@DB3PR06MB218.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB3PR06MB218;
x-forefront-prvs: 049897979A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(377454003)(13464003)(479174004)(24454002)(51704005)(55674003)(22813001)(16313002)(189002)(76576001)(54356999)(92566002)(105586002)(106116001)(106356001)(19580395003)(2900100001)(19580405001)(2656002)(87936001)(33656002)(97736003)(46102003)(2950100001)(101416001)(15975445007)(64706001)(62966003)(77156002)(50986999)(76176999)(66066001)(86362001)(74316001)(102836002)(93886004)(68736005)(1941001)(122556002)(40100003)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR06MB218; H:DB3PR06MB219.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
received-spf: None (protection.outlook.com: cyberinvasion.net does not designate permitted sender hosts)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: cyberinvasion.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Feb 2015 23:34:32.3330 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d16a191d-a1e2-474f-9523-9f4888345fa6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR06MB218
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Reteg2Im-8dD4hhZnZFsGkIlw00>
X-Mailman-Approved-At: Thu, 26 Feb 2015 08:11:46 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 23:34:53 -0000

Charles,
Don't get me wrong this sounds like an awesome event and I commend you for championing and organizing it but on your post here:

Why are Cisco and Cisco DevNet involved?
>This is just my own opinion, but I see the following reasons behind Cisco involvement.
>Cisco is a big supporter and active member of IETF, with a particular interest in open source development related to IETF standards
>Cisco DevNet is Cisco's developer program, an active community-based program within the industry
>DevNet has managed a number of Hackathons to-date, and has credibility in this space
>DevNet has a large community that may be interested in becoming involved with the Hackthon
>Involvement reinforces Cisco's position as a key industry player and active advocate of standards and open source development
>Involvement in the hackathon increases awareness of DevNet by engaging it actively with the IETF community

It seems like this is an (Awesome) Cisco devnet event that is being collocated at IETF92 rather than an IETF event.
Just my 2c.

-----Original Message-----
From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com] 
Sent: Wednesday, February 25, 2015 11:28 PM
To: Dean Bogdanovic; Thomas D. Nadeau
Cc: ietf@ietf.org; James Gannon
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX

Hi Dean,

I think the short answer to your question is yes. A more complete version of that answer is available at:
https://communities.cisco.com/message/175254#175254

I have verified that you do not need to register with Cisco DevNet to view the content within the community setup for the Hackathon:
https://communities.cisco.com/community/developer/ietf-hackathon

You do need to login to post to it. This requirement could be relaxed, thus allowing anonymous posts, but I don¹t view that as a particularly good solution.

Cheers,
Charles


On 2/25/15, 3:15 PM, "Dean Bogdanovic" <deanb@juniper.net> wrote:

>My biggest issue with this hackathon is requirement to register with 
>Cisco DevNet. This tells me it is a corporate event, not an IETF event 
>and am asking if Cisco DevNet org is trying to increase its membership.
>
>And +1 to Melinda's email
>
>On Feb 25, 2015, at 4:54 PM, Thomas D. Nadeau <tnadeau@lucidvision.com>
>wrote:
>
>> +1
>> 
>>> On Feb 25, 2015:4:03 PM, at 4:03 PM, Melinda Shore 
>>><melinda.shore@gmail.com> wrote:
>>> 
>>> On 2/25/15 11:57 AM, James Gannon wrote:
>>>> Am I the only one who think that a rebranding on this might be the 
>>>>easiest solution for everyone?
>>> 
>>> I think it's by far the best solution.  The expectation that you'd 
>>> need a Cisco login and visit a Cisco web page to see responses to 
>>> questions raised on the IETF mailing list seems unreasonable to me.
>>> 
>>> If it's an IETF event, move the "community" page to an IETF resource.
>>> We've got multiple wikis, and I really can't imagine who thought it 
>>> was a better idea to use an access-controlled Cisco one.
>>> 
>>> In the meantime, thanks to Charles for posting a little more 
>>> information to the mailing list.
>>> 
>>> Melinda
>>> 
>>> 
>> 
>