
From housley@vigilsec.com  Tue Mar  6 08:52:47 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7350B21F86EE; Tue,  6 Mar 2012 08:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R+RBPVpZpi9O; Tue,  6 Mar 2012 08:52:47 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2D321F8704; Tue,  6 Mar 2012 08:52:46 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D17B4F24011; Tue,  6 Mar 2012 11:53:02 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id ASpnj5A6EXYh; Tue,  6 Mar 2012 11:52:28 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DA4C5F24010; Tue,  6 Mar 2012 11:53:01 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Russ Housley <housley@vigilsec.com>
Date: Tue, 6 Mar 2012 11:52:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4EC5D7A-2680-4CC3-9152-975F8326D580@vigilsec.com>
References: <4F55F882.6060600@ieca.com>
To: IETF Tools Development <tools-development@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: codesprints@ietf.org
Subject: [codesprints] Fwd: "Intended RFC Status" drop down menu
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 16:52:47 -0000

Sean is correct.  Please create a tick to have this done at the =
codesprint.  In fact, if someone can point to the right module, I bet I =
can figure this one out.

Russ



Begin forwarded message:

> From: Sean Turner <turners@ieca.com>
> Date: March 6, 2012 6:44:02 AM EST
> To: The IESG <iesg@ietf.org>
> Subject: "Intended RFC Status" drop down menu
>=20
> Just checking that this is on the list of things to do:
>=20
> When adding a document (click the add button) the Intended RFC Status =
down includes the proposed standard, draft standard, and standard.  I =
think "draft standard" needs to be removed.
>=20
> spt


From henrik@levkowetz.com  Tue Mar  6 09:23:43 2012
Return-Path: <henrik@levkowetz.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5988B21F8647; Tue,  6 Mar 2012 09:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.517
X-Spam-Level: 
X-Spam-Status: No, score=-102.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EKnz6gON7RDg; Tue,  6 Mar 2012 09:23:37 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id E5EBA21E807F; Tue,  6 Mar 2012 09:23:32 -0800 (PST)
Received: from localhost ([127.0.0.1]:38857 helo=vigonier.lan ident=henrik) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1S4y6l-0007J6-UM; Tue, 06 Mar 2012 18:23:31 +0100
Message-ID: <4F564813.7030501@levkowetz.com>
Date: Tue, 06 Mar 2012 18:23:31 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <4F55F882.6060600@ieca.com> <C4EC5D7A-2680-4CC3-9152-975F8326D580@vigilsec.com>
In-Reply-To: <C4EC5D7A-2680-4CC3-9152-975F8326D580@vigilsec.com>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: housley@vigilsec.com, tools-development@ietf.org, codesprints@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: IETF Tools Development <tools-development@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Fwd: "Intended RFC Status" drop down menu
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:23:43 -0000

This one actually needed a bit background information to get right.  The
old 'Draft Standard' entry in the IntendedStdLevelName needed to be set
to 'not used', and the form object behind the edit form needed to be told
to use only names in use.  Fixed now.


Best regards,

	Henrik

On 2012-03-06 17:52 Russ Housley said the following:
> Sean is correct.  Please create a tick to have this done at the codesprint.  In fact, if someone can point to the right module, I bet I can figure this one out.

This one actually needed a bit background information to get right.  The
old 'Draft Standard' entry in the IntendedStdLevelName needed to be set
to 'not used', and the form object behind the edit form needed to be told
to use only names in use.  Fixed now.


Best regards,

	Henrik

> Russ
> 
> 
> 
> Begin forwarded message:
> 
>> From: Sean Turner <turners@ieca.com>
>> Date: March 6, 2012 6:44:02 AM EST
>> To: The IESG <iesg@ietf.org>
>> Subject: "Intended RFC Status" drop down menu
>> 
>> Just checking that this is on the list of things to do:
>> 
>> When adding a document (click the add button) the Intended RFC Status down includes the proposed standard, draft standard, and standard.  I think "draft standard" needs to be removed.
>> 
>> spt
> 
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
> 

From york@isoc.org  Wed Mar  7 12:55:45 2012
Return-Path: <york@isoc.org>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB9611E80C0 for <codesprints@ietfa.amsl.com>; Wed,  7 Mar 2012 12:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Level: 
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cXiRKFLDz3Al for <codesprints@ietfa.amsl.com>; Wed,  7 Mar 2012 12:55:44 -0800 (PST)
Received: from smtp177.iad.emailsrvr.com (smtp177.iad.emailsrvr.com [207.97.245.177]) by ietfa.amsl.com (Postfix) with ESMTP id 58CD911E80A1 for <codesprints@ietf.org>; Wed,  7 Mar 2012 12:55:42 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp47.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id BEE293A96F5 for <codesprints@ietf.org>; Wed,  7 Mar 2012 15:55:41 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp47.relay.iad1a.emailsrvr.com (Authenticated sender: york-AT-isoc.org) with ESMTPSA id 78C163A8A75 for <codesprints@ietf.org>; Wed,  7 Mar 2012 15:55:41 -0500 (EST)
From: Dan York <york@isoc.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A5C221CD-D73B-4567-BFD3-B50D178DDA59"
Date: Wed, 7 Mar 2012 15:55:40 -0500
Message-Id: <8ED6D8C4-EA5E-401D-9FBC-1905060FEAA9@isoc.org>
To: codesprints@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Subject: [codesprints] IETF83 code sprint - willing to help with documentation
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 20:55:45 -0000

--Apple-Mail=_A5C221CD-D73B-4567-BFD3-B50D178DDA59
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Since I'm arriving in Paris on Friday evening, I figured I'd help out =
with the code sprint.  While I've worked with python for years and did a =
bit with a few Django-powered sites a few years back, rather than =
hacking on the main code base to add enhancements, I thought a better =
use of my particular skills might be to help with documentation and =
helping explain to people how to better use the IETF tools.  So I'm glad =
to expand the text on various web pages... add new pages related to some =
of the features you expect to be adding... write up some tutorials, edit =
existing pages, whatever...

I took a look at the tickets on =
http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas but =
without really diving into the tickets I can't easily see which might =
need some documentation assistance or not.  Particularly since I've =
never worked with this code base before.

So I'll put the invitation out there - if you have specific ideas for =
pages that could use some editing, new pages that need to be created, or =
some tutorials that could be written, please feel free to assign me =
(york@isoc.org) to new or existing tickets with those tasks on them. =
When I get to the sprint I'll be glad to plug away at them. =20

And if there aren't documentation needs, I'll just join with the rest of =
you on the code.

Regards,
Dan

P.S. A few of you attending know me from my blogging or from my RAI/SIP =
activities - you may or may not be aware of the developer side of my =
background - some info at http://code.danyork.com/ and =
https://github.com/danyork

--
Dan York
Senior Content Strategist, Internet Society
york@isoc.org   +1-802-735-1624=20
Jabber: york@jabber.isoc.org=20
Skype: danyork   http://twitter.com/danyork

http://www.internetsociety.org/deploy360/


--Apple-Mail=_A5C221CD-D73B-4567-BFD3-B50D178DDA59
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>Since I'm arriving in Paris on Friday evening, =
I figured I'd help out with the code sprint. &nbsp;While I've worked =
with python for years and did a bit with a few Django-powered sites a =
few years back, rather than hacking on the main code base to add =
enhancements, I thought a better use of my particular skills might be to =
help with documentation and helping explain to people how to better use =
the IETF tools. &nbsp;So I'm glad to expand the text on various web =
pages... add new pages related to some of the features you expect to be =
adding... write up some tutorials, edit existing pages, =
whatever...</div><div><br></div><div>I took a look at the tickets =
on&nbsp;<a =
href=3D"http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas">htt=
p://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas</a>&nbsp;but =
without really diving into the tickets I can't easily see which might =
need some documentation assistance or not. &nbsp;Particularly since I've =
never worked with this code base before.</div><div><br></div><div>So =
I'll put the invitation out there - if you have specific ideas for pages =
that could use some editing, new pages that need to be created, or some =
tutorials that could be written, please feel free to assign me (<a =
href=3D"mailto:york@isoc.org">york@isoc.org</a>) to new or existing =
tickets with those tasks on them. When I get to the sprint I'll be glad =
to plug away at them. &nbsp;</div><div><br></div><div>And if there =
aren't documentation needs, I'll just join with the rest of you on the =
code.</div><div><br></div><div>Regards,</div><div>Dan</div><div><br></div>=
<div>P.S. A few of you attending know me from my blogging or from my =
RAI/SIP activities - you may or may not be aware of the developer side =
of my background - some info at&nbsp;<a =
href=3D"http://code.danyork.com/">http://code.danyork.com/</a>&nbsp;and&nb=
sp;<a =
href=3D"https://github.com/danyork">https://github.com/danyork</a></div><d=
iv><br><div apple-content-edited=3D"true">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div>--</div><div>Dan York</div><div>Senior =
Content Strategist, Internet Society</div><div><a =
href=3D"mailto:york@isoc.org">york@isoc.org</a> =
&nbsp;&nbsp;+1-802-735-1624&nbsp;</div><div>Jabber: <a =
href=3D"mailto:york@jabber.isoc.org">york@jabber.isoc.org</a>&nbsp;</div><=
div>Skype: danyork &nbsp; <a =
href=3D"http://twitter.com/danyork">http://twitter.com/danyork</a></div><d=
iv><br></div><div><a =
href=3D"http://www.internetsociety.org/deploy360/">http://www.internetsoci=
ety.org/deploy360/</a></div></div></div></div>
</div>
<br></div></body></html>=

--Apple-Mail=_A5C221CD-D73B-4567-BFD3-B50D178DDA59--

From henrik@levkowetz.com  Tue Mar 13 06:52:13 2012
Return-Path: <henrik@levkowetz.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3219D21F885F for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 06:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.525
X-Spam-Level: 
X-Spam-Status: No, score=-103.525 tagged_above=-999 required=5 tests=[AWL=1.075, BAYES_00=-2.599, GB_I_INVITATION=-2, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHTpEdye8f2h for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 06:52:12 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDE521F884C for <codesprints@ietf.org>; Tue, 13 Mar 2012 06:52:12 -0700 (PDT)
Received: from [2a01:3f0:1:0:21e:c2ff:fe13:7e3e] (port=59437 helo=brunello.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1S7S94-0006Ih-Nv; Tue, 13 Mar 2012 14:52:11 +0100
Message-ID: <4F5F510A.8080205@levkowetz.com>
Date: Tue, 13 Mar 2012 14:52:10 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Dan York <york@isoc.org>
References: <8ED6D8C4-EA5E-401D-9FBC-1905060FEAA9@isoc.org>
In-Reply-To: <8ED6D8C4-EA5E-401D-9FBC-1905060FEAA9@isoc.org>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: york@isoc.org, codesprints@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Cc: codesprints@ietf.org
Subject: Re: [codesprints] IETF83 code sprint - willing to help with documentation
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 13:52:13 -0000

Hi Dan,

Sorry for the delay in answering; I was on a short vacation Thursday
to Monday.  Response below:

On 2012-03-07 21:55 Dan York said:
> Hi,
> 
> Since I'm arriving in Paris on Friday evening, I figured I'd help out
> with the code sprint.  While I've worked with python for years and
> did a bit with a few Django-powered sites a few years back, rather
> than hacking on the main code base to add enhancements, I thought a
> better use of my particular skills might be to help with
> documentation and helping explain to people how to better use the
> IETF tools.  So I'm glad to expand the text on various web pages...
> add new pages related to some of the features you expect to be
> adding... write up some tutorials, edit existing pages, whatever...
> 
> I took a look at the tickets on
> http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas but
> without really diving into the tickets I can't easily see which might
> need some documentation assistance or not.  Particularly since I've
> never worked with this code base before.
> 
> So I'll put the invitation out there - if you have specific ideas for
> pages that could use some editing, new pages that need to be created,
> or some tutorials that could be written, please feel free to assign
> me (york@isoc.org) to new or existing tickets with those tasks on
> them. When I get to the sprint I'll be glad to plug away at them.

Thanks for the offer!

> And if there aren't documentation needs, I'll just join with the rest
> of you on the code.

I'm tempted to say that that would probably be the most straightforward
solution, as I don't directly have a documentation issues list which
I can point you to.  I'd be more than happy to have you jump into the
code.

However, thinking some more about this, one thing that might become
very useful for the future is to improve the documentation related
to the new database schema itself, how we've made it work with the
old codebase, and how we should do refactoring of the old codebase
to clean it up to work directly against the new database schema,
instead of going through proxy models.

There are a few pages in the wiki which touches upon this currently,
but I wouldn't call it comprehensive, and I think a lot of people
would benefit from improving on this, if you think that would be a
good fit for you.

These are the pages which give data regarding this currently:
  http://trac.tools.ietf.org/tools/ietfdb/wiki/DatabaseSchemaDescription
  http://trac.tools.ietf.org/tools/ietfdb/wiki/DatabaseSchemaConversion

I expect that you'll have to buttonhole the contractor developer, Ole
Laursen, who will be available over Skype or similar, and myself, quite
a bit in order to gather information needed to flesh out this, but better
have that happen once than multiplied by the number of people who will
(hopefully!) be touching the code as we go forwards.

And if you decide to hack on the code instead, please feel free!


Best regards,

	Henrik

From housley@vigilsec.com  Tue Mar 13 14:20:39 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5DCD21E8012 for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 14:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nc6GvwzWdmnP for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 14:20:39 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id F34C221F863B for <codesprints@ietf.org>; Tue, 13 Mar 2012 14:20:38 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 285F39A471B; Tue, 13 Mar 2012 17:20:41 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id Ge122ywGo48O; Tue, 13 Mar 2012 17:20:36 -0400 (EDT)
Received: from [12.22.58.150] (unknown [12.22.58.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D27AB9A470F; Tue, 13 Mar 2012 17:20:39 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Russ Housley <housley@vigilsec.com>
Date: Tue, 13 Mar 2012 17:20:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FC08FA4-8224-4513-AE7E-7CCCA30DACE3@vigilsec.com>
References: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
To: codesprints@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: Alexa Morris <amorris@amsl.com>
Subject: [codesprints] Using https://datatracker.ietf.org/doc/draft-name/ in i-d-announce mails ?
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 21:20:39 -0000

Can we do this at the codesprint?

Also, when the datatracker sends a New Vesion Notification message, this =
same URL should be provided.

Russ


Begin forwarded message:

> From: Russ Housley <housley@vigilsec.com>
> Date: March 6, 2012 9:12:54 AM EST
> To: Xavier Marjou <xavier.marjou@gmail.com>
> Cc: IETF Discussion <ietf@ietf.org>
> Subject: Re: Add a link to the HTML version in i-d-announce mails ?
>=20
> I would be much happier with a link to the datatracker HTML version:
> https://datatracker.ietf.org/doc/draft-name/
>=20
> Would this meet your needs?
>=20
> Russ
>=20
>=20
> On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:
>=20
>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>> reading the HTML version of the draft rather than the TXT version.
>>=20
>> I thus often need to manually rewrite the TXT link to fetch the HTML
>> version of the draft. I can not believe I'm the only one.
>>=20
>> Hence, would it be possible to also include a link like
>> http://tools.ietf.org/html/draft-name in the mail of the announced
>> draft?
>>=20
>> Cheers,
>> Xavier
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rjsparks@nostrum.com  Tue Mar 13 14:44:56 2012
Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1532721F8610 for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 14:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCtoxwAKA-db for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 14:44:55 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E0CAF21F85FF for <codesprints@ietf.org>; Tue, 13 Mar 2012 14:44:54 -0700 (PDT)
Received: from unexplicable.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q2DLipCO085335 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Mar 2012 16:44:52 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F5FBFD3.5050608@nostrum.com>
Date: Tue, 13 Mar 2012 16:44:51 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <2FC08FA4-8224-4513-AE7E-7CCCA30DACE3@vigilsec.com>
In-Reply-To: <2FC08FA4-8224-4513-AE7E-7CCCA30DACE3@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.170.125.181 is authenticated by a trusted mechanism)
Cc: Alexa Morris <amorris@amsl.com>, codesprints@ietf.org
Subject: Re: [codesprints] Using https://datatracker.ietf.org/doc/draft-name/ in i-d-announce mails ?
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 21:44:56 -0000

Should be able to.

See
<http://trac.tools.ietf.org/tools/ietfdb/ticket/801>
<http://trac.tools.ietf.org/tools/ietfdb/ticket/802>

RjS

On 3/13/12 4:20 PM, Russ Housley wrote:
> Can we do this at the codesprint?
>
> Also, when the datatracker sends a New Vesion Notification message, this same URL should be provided.
>
> Russ
>
>
> Begin forwarded message:
>
>> From: Russ Housley<housley@vigilsec.com>
>> Date: March 6, 2012 9:12:54 AM EST
>> To: Xavier Marjou<xavier.marjou@gmail.com>
>> Cc: IETF Discussion<ietf@ietf.org>
>> Subject: Re: Add a link to the HTML version in i-d-announce mails ?
>>
>> I would be much happier with a link to the datatracker HTML version:
>> https://datatracker.ietf.org/doc/draft-name/
>>
>> Would this meet your needs?
>>
>> Russ
>>
>>
>> On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:
>>
>>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>>> reading the HTML version of the draft rather than the TXT version.
>>>
>>> I thus often need to manually rewrite the TXT link to fetch the HTML
>>> version of the draft. I can not believe I'm the only one.
>>>
>>> Hence, would it be possible to also include a link like
>>> http://tools.ietf.org/html/draft-name in the mail of the announced
>>> draft?
>>>
>>> Cheers,
>>> Xavier
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints

From housley@vigilsec.com  Tue Mar 13 14:58:02 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 702CE21E8028 for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 14:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Pu2haYoOX0S for <codesprints@ietfa.amsl.com>; Tue, 13 Mar 2012 14:58:01 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7A59121E8017 for <codesprints@ietf.org>; Tue, 13 Mar 2012 14:58:01 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 760179A471B; Tue, 13 Mar 2012 17:58:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id B2Dj4GkAbbqS; Tue, 13 Mar 2012 17:57:45 -0400 (EDT)
Received: from [12.22.58.150] (unknown [12.22.58.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7808E9A470F; Tue, 13 Mar 2012 17:58:13 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Mar 2012 17:57:55 -0400
Message-Id: <FA1B1596-1408-416B-8A20-4A231241A7EC@vigilsec.com>
To: codesprints@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Pete Resnick <presnick@qualcomm.com>, Alexa Morris <amorris@amsl.com>
Subject: [codesprints] Avoiding inappropriate email responses
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 21:58:02 -0000

Many messages lead to inappropriate parties being on the response if a =
recipient uses the reply-all.

A reply-all to a Last Call message will include iesg-secretary and =
ietf-announce because they come from:

   From:<iesg-secretary at ietf.org>
   To:<ietf-announce at ietf.org>
   Reply-To:<ietf at ietf.org>

Depending on your mail software, some reply-all functions will put =
whatever is in the =46rom into the To of the reply, and whatever is in =
the To and Cc into the Cc of the reply (despite the the Reply-To field).

So I have a suggestion. Could we make announcements:

   From:<iesg-no-reply at ietf.org>
   Sender:<iesg-secretary at ietf.org>
   To:<ietf-announce at ietf.org>
   Reply-To:<ietf at ietf.org>

Would at least eliminate the messages to the secretariat.

We would need to set things up so that <iesg-no-reply at ietf.org> does =
not deliver any message or cause bounce messages.

Russ


From rjsparks@nostrum.com  Wed Mar 14 08:53:54 2012
Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72C121F85B8; Wed, 14 Mar 2012 08:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zPDcSjpt-PTg; Wed, 14 Mar 2012 08:53:54 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8031D21F85F6; Wed, 14 Mar 2012 08:53:52 -0700 (PDT)
Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q2EFrpam077216 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Mar 2012 10:53:51 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F60BF0F.3030203@nostrum.com>
Date: Wed, 14 Mar 2012 10:53:51 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org, codesprints@ietf.org, wgchairs@ietf.org
References: <68346139-29F8-4B71-9CCA-6AC158C85E6F@ietf.org>
In-Reply-To: <68346139-29F8-4B71-9CCA-6AC158C85E6F@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: Re: [codesprints] Paris IETF Codesprint
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 15:53:54 -0000

If you are planning to join this codesprint, please make sure you've let 
us know by
adding yourself to this page:
<http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF83SprintSignUp>
so we can provision correctly.

If you've not thought about the codesprint, take a couple of minutes now 
to look over
the kinds of things we're planning to work on:
<http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas>
Please add to that list if there's something important to you that you 
see missing.
If see something there you'd really like to have, please join us and 
make it happen.

RjS

On 1/15/12 2:12 PM, IETF Chair wrote:
> Paris IETF Codesprint
>
> When:  Saturday, 24 March 2012, starting at 9:30 AM
>
> Where: IETF Hotel
>
> What:  A bunch of hackers get together to work on code for the IETF.
>      All code will become part of the open source IETF tools.
>
> Who:   Hopefully you can help
>
> Many of the results of previous codesprint activities are being
> used every day by the IETF community.  Shortly before the Paris
> meeting, we will transition from the current database schema to a
> new one.  We believe that the new schema will make many tasks
> much easier.  No doubt, the transition will uncover new bugs.
> Work to polish or improve existing tools, fix bugs, or make new
> tools.  All efforts are appreciated and most welcome.
>
> Steve Conte will be helping with advance planning.  Henrik Levkowetz
> will be coordinating the event in Paris.  You can find more information
> here:
>
>   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF83Sprint
>
> If you are able to participate, please sign up on the wiki at:
>
>   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF83SprintSignUp
>
> Please support the tools development effort,
>   Russ
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From housley@vigilsec.com  Fri Mar 23 05:58:34 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE69D21F853A for <codesprints@ietfa.amsl.com>; Fri, 23 Mar 2012 05:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlH7ot-uoZE4 for <codesprints@ietfa.amsl.com>; Fri, 23 Mar 2012 05:58:34 -0700 (PDT)
Received: from services-1.meeting.ietf.org (unknown [IPv6:2001:df8:0:5::6]) by ietfa.amsl.com (Postfix) with ESMTP id 384C321F8514 for <codesprints@ietf.org>; Fri, 23 Mar 2012 05:58:34 -0700 (PDT)
Received: from [IPv6:2001:df8::32:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:32:6233:4bff:fe20:eb18]) by services-1.meeting.ietf.org (Postfix) with ESMTP id D7915688CE for <codesprints@ietf.org>; Fri, 23 Mar 2012 12:58:32 +0000 (UTC)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 23 Mar 2012 08:58:33 -0400
Message-Id: <AAA89B7B-015E-4089-9938-0DC2F7189B5C@vigilsec.com>
To: codesprints@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [codesprints] Codesprint Location and Food
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codesprints>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 12:58:34 -0000

The codeprint will take place on the second floor of the congress hall =
near the "A" elevators.  The sign should say "Maillot A".

Since breakfast is included at the IETF hotel, please eat before coming =
to the codesprint.  We will have beverages and some cold food available =
in the morning.  Lunch, afternoon snack, and dinner will be provided.

Russ

