IETF Logo Mail Archive

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

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 25 February 2015 23:45 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 4F34C1A017E for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 15:45:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=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 29QE0FcFrwTu for <ietf@ietfa.amsl.com>; Wed, 25 Feb 2015 15:45:57 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CBC21A0125 for <ietf@ietf.org>; Wed, 25 Feb 2015 15:45:57 -0800 (PST)
Received: from mx1.yitter.info (unknown [50.189.173.0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E12098A031 for <ietf@ietf.org>; Wed, 25 Feb 2015 23:45:55 +0000 (UTC)
Date: Wed, 25 Feb 2015 18:45:54 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF Hackathon at IETF 92, March 21-22, Dallas, TX
Message-ID: <20150225234554.GK3297@mx1.yitter.info>
References: <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> <D22D1246-CDFD-41ED-B08C-91D8F4401DFD@lucidvision.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D22D1246-CDFD-41ED-B08C-91D8F4401DFD@lucidvision.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/POddqHDiyt89OwNX-rWDqvC6UXg>
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:45:58 -0000

On Wed, Feb 25, 2015 at 06:30:07PM -0500, Thomas D. Nadeau wrote:
> 	A better solution would be to use IETF Infrastructure for this, or at least non-commercial like github.
> 

Last I checked, github was charging my employer for our use, and they
have plenty of offerings on their site to entice you to pay for it.

If one is going to complain about a corporation using their free
offerings in order to entice people to more commercial entanglements,
then one at least ought to be consistent about it.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email