From peter.musgrave@magorcorp.com  Fri Oct  1 05:39:38 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F7263A6F0F; Fri,  1 Oct 2010 05:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.857
X-Spam-Level: 
X-Spam-Status: No, score=-101.857 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tv6MidnvtFt5; Fri,  1 Oct 2010 05:39:37 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 30E863A6FE1; Fri,  1 Oct 2010 05:38:57 -0700 (PDT)
Received: by qyk2 with SMTP id 2so3783987qyk.10 for <multiple recipients>; Fri, 01 Oct 2010 05:39:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.47.85 with SMTP id m21mr3705131qaf.270.1285936784922; Fri, 01 Oct 2010 05:39:44 -0700 (PDT)
Received: by 10.229.68.39 with HTTP; Fri, 1 Oct 2010 05:39:44 -0700 (PDT)
In-Reply-To: <058D772C-A8A6-4150-8005-D46377CBC538@nostrum.com>
References: <058D772C-A8A6-4150-8005-D46377CBC538@nostrum.com>
Date: Fri, 1 Oct 2010 08:39:44 -0400
Message-ID: <AANLkTi=EBZedgJkmZKn5rwhW-aw=WsCakC1nZBEqQksv@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "tools-development@ietf.org Development" <tools-development@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Setting codesprint goals for IETF79
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Oct 2010 12:39:38 -0000

Hi Robert,

w.r.t.: "* Add a new tab for IPR disclosures (probably showing how
many there are in
   the tab title: e.g. "IPR disclosures (2)").

Are you asking for an IPR column in the WG page display of WG docs,
individual drafts and RFCs? If so - I can take a swing at that in
Beijing - since I was messing around there last time.

Peter Musgrave

On Fri, Sep 24, 2010 at 5:01 PM, Robert Sparks <rjsparks@nostrum.com> wrote=
:
> We have several things to accomplish during the upcoming codesprint.
>
> There are two new tools that should be ready for additional testing
> and polish - the liaison management tool and the ID submissions tool.
>
> We have a growing list of small things to work on that would have
> high impact for the people that have requested them. The full list is
> at <http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas>.
> Here are a few examples that look addressable at the codesprint. (This
> is not at all comprehensive:)
>
> =A0* Periodically email the list of addresses on any given tools alias (l=
ike
> =A0 =A0rai-ads@ or draft-foo-bar@) to that alias to improve the chances t=
hat lists
> =A0 =A0that are wrong get corrected.
>
> =A0* Add a new tab for IPR disclosures (probably showing how many there a=
re in
> =A0 =A0the tab title: e.g. "IPR disclosures (2)").
>
> =A0* Make it possible for an IESG member to add a comment (for the docume=
nt
> =A0 =A0history) in the "change document state" dialog.
>
> =A0* Show the date of last change to the various writeups on the page dis=
played
> =A0 =A0on the IESG writeups tab.
>
> =A0* The Atom feed should include everything in the history tab, not just=
 the
> =A0 =A0document_comments table.
>
> =A0* Allowing search by position: "any AD/AD name" has position
> =A0 =A0"any/Yes/NoObj/Discuss/..."
>
> =A0* Show "has IPR disclosures" flag in search result list.
>
> There are a few medium sized projects out there that I think could be don=
e
> during the sprint, but would have a higher chance of success with a littl=
e
> bit of exploration/analysis before we get there. Please look through the =
list
> and see if there's something there that would solve a problem you are hav=
ing.
>
> If you know of something that the sprinters should be working on, but don=
't see it
> on the EnhancementIdeas list, please add it, or send me a quick note and =
I'll make
> sure it gets there.
>
> Remember that you can download a current snapshot of the database at any =
time.
> Now might be a good time to bring your local development environment back=
 into
> action. If you're new to the sprint or haven't set up a local environment=
 before,
> these links will help:
> =A0<http://trac.tools.ietf.org/tools/ietfdb/wiki/SprintCoderSetup>
> =A0<http://trac.tools.ietf.org/tools/ietfdb/wiki/SprintDatabase>
>
> If you're able to sprint, but haven't signed up yet, please do so now
> at <http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF79SprintSignUp>
>
>
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
>

From housley@vigilsec.com  Fri Oct  1 08:09:06 2010
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1DA23A6F40 for <codesprints@core3.amsl.com>; Fri,  1 Oct 2010 08:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45++BRZubdP1 for <codesprints@core3.amsl.com>; Fri,  1 Oct 2010 08:09:06 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 2DADE3A6F10 for <codesprints@ietf.org>; Fri,  1 Oct 2010 08:09:03 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 07EC9F2401D for <codesprints@ietf.org>; Fri,  1 Oct 2010 11:10:07 -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 yI1O22URgtcj for <codesprints@ietf.org>; Fri,  1 Oct 2010 11:09:33 -0400 (EDT)
Received: from [192.168.27.112] (mail.pir.org [72.44.190.134]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2A22CF24018 for <codesprints@ietf.org>; Fri,  1 Oct 2010 11:10:06 -0400 (EDT)
Message-ID: <4CA5F9C0.4000108@vigilsec.com>
Date: Fri, 01 Oct 2010 11:09:52 -0400
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: codesprints@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [codesprints] Suggestion for enhancement
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Oct 2010 15:09:07 -0000

This page: https://datatracker.ietf.org/idtracker/help/state/

There is a way to get to this help from the page that an AD uses to set
the state, but there does not appear to be an easy way to get this
information without being an AD.  Consider a new author.  They need a
simple way to learn what the states mean, and what to expect next.

From housley@vigilsec.com  Fri Oct  1 09:17:33 2010
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F10D3A6F28; Fri,  1 Oct 2010 09:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lq6SSK+6ScNE; Fri,  1 Oct 2010 09:17:32 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 6C8393A6E86; Fri,  1 Oct 2010 09:17:32 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 51A05F24026; Fri,  1 Oct 2010 12:18:24 -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 93nY7i9IIo2Q; Fri,  1 Oct 2010 12:18:17 -0400 (EDT)
Received: from [192.168.27.112] (mail.pir.org [72.44.190.134]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 8A5A6F2401C; Fri,  1 Oct 2010 12:18:23 -0400 (EDT)
Message-ID: <4CA609CE.4010704@vigilsec.com>
Date: Fri, 01 Oct 2010 12:18:22 -0400
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: codesprints@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>
Subject: [codesprints] URGENT NEED: Protocol Action and Document Action
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 01 Oct 2010 16:17:33 -0000

Not so long ago, the IESG asked for a change to the subject line to
include the I-D file name.  This was done, and it have been very helpful
to all ADs.

Protocol Action and Document Action messages still do not include the
I-D file name.  Both IANA and the RFC Editor (and the new mail list
search that was just finished by Glen) would be greatly helped by having
the I-D file name in the Protocol Action and Document Action message
subject line.

Please make this a high priority action for the code sprint in Beijing.

Russ

From rjsparks@nostrum.com  Fri Oct  8 09:00:08 2010
Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A97333A689E; Fri,  8 Oct 2010 09:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlOU6x9H0vn4; Fri,  8 Oct 2010 09:00:05 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id C3FBE3A686B; Fri,  8 Oct 2010 09:00:03 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-71-48-4.dllstx.fios.verizon.net [173.71.48.4]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o98G153L036915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Oct 2010 11:01:05 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <AANLkTi=EBZedgJkmZKn5rwhW-aw=WsCakC1nZBEqQksv@mail.gmail.com>
Date: Fri, 8 Oct 2010 11:01:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E94BFA3-0C9A-4028-A0F1-1E1B0A8C2DA3@nostrum.com>
References: <058D772C-A8A6-4150-8005-D46377CBC538@nostrum.com> <AANLkTi=EBZedgJkmZKn5rwhW-aw=WsCakC1nZBEqQksv@mail.gmail.com>
To: Peter Musgrave <peter.musgrave@magorcorp.com>
X-Mailer: Apple Mail (2.1081)
Cc: "tools-development@ietf.org Development" <tools-development@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Setting codesprint goals for IETF79
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 08 Oct 2010 16:00:08 -0000

I don't think that's what the person originally suggesting that had in =
mind, but it sounds like a good idea!

My read of the suggestion below was to add a tab to the main document =
view. There has been work done in the
meantime that probably obviates the suggestion (at least the tab part) - =
there is a link on the document's main page.
It might be reasonable to include the # of disclosures in the text of =
that link.

RjS

On Oct 1, 2010, at 7:39 AM, Peter Musgrave wrote:

> Hi Robert,
>=20
> w.r.t.: "* Add a new tab for IPR disclosures (probably showing how
> many there are in
>   the tab title: e.g. "IPR disclosures (2)").
>=20
> Are you asking for an IPR column in the WG page display of WG docs,
> individual drafts and RFCs? If so - I can take a swing at that in
> Beijing - since I was messing around there last time.
>=20
> Peter Musgrave
>=20
> On Fri, Sep 24, 2010 at 5:01 PM, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>> We have several things to accomplish during the upcoming codesprint.
>>=20
>> There are two new tools that should be ready for additional testing
>> and polish - the liaison management tool and the ID submissions tool.
>>=20
>> We have a growing list of small things to work on that would have
>> high impact for the people that have requested them. The full list is
>> at <http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas>.
>> Here are a few examples that look addressable at the codesprint. =
(This
>> is not at all comprehensive:)
>>=20
>>  * Periodically email the list of addresses on any given tools alias =
(like
>>    rai-ads@ or draft-foo-bar@) to that alias to improve the chances =
that lists
>>    that are wrong get corrected.
>>=20
>>  * Add a new tab for IPR disclosures (probably showing how many there =
are in
>>    the tab title: e.g. "IPR disclosures (2)").
>>=20
>>  * Make it possible for an IESG member to add a comment (for the =
document
>>    history) in the "change document state" dialog.
>>=20
>>  * Show the date of last change to the various writeups on the page =
displayed
>>    on the IESG writeups tab.
>>=20
>>  * The Atom feed should include everything in the history tab, not =
just the
>>    document_comments table.
>>=20
>>  * Allowing search by position: "any AD/AD name" has position
>>    "any/Yes/NoObj/Discuss/..."
>>=20
>>  * Show "has IPR disclosures" flag in search result list.
>>=20
>> There are a few medium sized projects out there that I think could be =
done
>> during the sprint, but would have a higher chance of success with a =
little
>> bit of exploration/analysis before we get there. Please look through =
the list
>> and see if there's something there that would solve a problem you are =
having.
>>=20
>> If you know of something that the sprinters should be working on, but =
don't see it
>> on the EnhancementIdeas list, please add it, or send me a quick note =
and I'll make
>> sure it gets there.
>>=20
>> Remember that you can download a current snapshot of the database at =
any time.
>> Now might be a good time to bring your local development environment =
back into
>> action. If you're new to the sprint or haven't set up a local =
environment before,
>> these links will help:
>>  <http://trac.tools.ietf.org/tools/ietfdb/wiki/SprintCoderSetup>
>>  <http://trac.tools.ietf.org/tools/ietfdb/wiki/SprintDatabase>
>>=20
>> If you're able to sprint, but haven't signed up yet, please do so now
>> at <http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF79SprintSignUp>
>>=20
>>=20
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints
>>=20


From housley@vigilsec.com  Mon Oct 11 09:41:42 2010
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B22B3A6B39; Mon, 11 Oct 2010 09:41:42 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LoI3LE5-xXC4; Mon, 11 Oct 2010 09:41:39 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 133663A6B4A; Mon, 11 Oct 2010 09:41:38 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 6F65CF2403C; Mon, 11 Oct 2010 12:43:02 -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 bRZ5Y12hfib2; Mon, 11 Oct 2010 12:42:44 -0400 (EDT)
Received: from [192.168.2.107] (pool-96-231-149-87.washdc.fios.verizon.net [96.231.149.87]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 91C25F24011; Mon, 11 Oct 2010 12:43:01 -0400 (EDT)
Message-ID: <4CB33E93.6030506@vigilsec.com>
Date: Mon, 11 Oct 2010 12:42:59 -0400
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: codesprints@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>
Subject: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 11 Oct 2010 16:41:43 -0000

AMS has set up a tool to search the IETF mail list, the announce mail
list, and the IESG mail list for messages with a particular draft name
in the subject name.  This will be a big help when looking for Last Call
comments.

An ARO account is being set up for each AD to use the tool.  Accounts
are needed to keep the IESG mail list messages private.

Please add a button or tab or some other appropriate widget to the
Datatracker to make it easy for the AD to find these messages.  This
must only be available to Datatracker users with the AD role.

Here is the URL for the search:

   https://www.iesg.org/bin/c5i?mid=6&rid=77&target=draft-name

Thanks,
  Russ

From julian.reschke@gmx.de  Mon Oct 11 09:52:24 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FDCE3A6A97 for <codesprints@core3.amsl.com>; Mon, 11 Oct 2010 09:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.889
X-Spam-Level: 
X-Spam-Status: No, score=-104.889 tagged_above=-999 required=5 tests=[AWL=-2.290, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-xkv0eVzLkH for <codesprints@core3.amsl.com>; Mon, 11 Oct 2010 09:52:24 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 9B81C3A6A7C for <codesprints@ietf.org>; Mon, 11 Oct 2010 09:52:20 -0700 (PDT)
Received: (qmail invoked by alias); 11 Oct 2010 16:53:31 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.131]) [217.91.35.233] by mail.gmx.net (mp001) with SMTP; 11 Oct 2010 18:53:31 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/k42V6pjjkx1AzRLq0IMDk/4XMr6YD+uGRAlNZmU qK+3A7VlYqTTpP
Message-ID: <4CB34108.2080507@gmx.de>
Date: Mon, 11 Oct 2010 18:53:28 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <4CB33E93.6030506@vigilsec.com>
In-Reply-To: <4CB33E93.6030506@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IESG <iesg@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 11 Oct 2010 16:52:24 -0000

On 11.10.2010 18:42, Russ Housley wrote:
> AMS has set up a tool to search the IETF mail list, the announce mail
> list, and the IESG mail list for messages with a particular draft name
> in the subject name.  This will be a big help when looking for Last Call
> comments.
>
> An ARO account is being set up for each AD to use the tool.  Accounts
> are needed to keep the IESG mail list messages private.
>
> Please add a button or tab or some other appropriate widget to the
> Datatracker to make it easy for the AD to find these messages.  This
> must only be available to Datatracker users with the AD role.
>
> Here is the URL for the search:
>
>     https://www.iesg.org/bin/c5i?mid=6&rid=77&target=draft-name
> ...

It would be cool if the same information, minus the view into the IESG 
mailing list, would be available to the public.

Best regards, Julian

From glen@amsl.com  Mon Oct 11 16:01:16 2010
Return-Path: <glen@amsl.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 752B13A685B; Mon, 11 Oct 2010 16:01:16 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6IkYgbTMV7AY; Mon, 11 Oct 2010 16:01:15 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id A89CB3A684F; Mon, 11 Oct 2010 16:01:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id CBF81E08BD; Mon, 11 Oct 2010 16:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEcuvGtsdaM9; Mon, 11 Oct 2010 16:02:28 -0700 (PDT)
Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id 82705E0716; Mon, 11 Oct 2010 16:02:28 -0700 (PDT)
Message-ID: <4CB39782.5000808@amsl.com>
Date: Mon, 11 Oct 2010 16:02:26 -0700
From: Glen Barney <glen@amsl.com>
Organization: AMS
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de>
In-Reply-To: <4CB34108.2080507@gmx.de>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 11 Oct 2010 23:01:16 -0000

Julian -

Your wish is granted.  :-)

Enter this way for the authenticated 3-list search, as before:

https://www.iesg.org/bin/c5i?mid=6&rid=77&target=draft-name

Enter THIS way for the unauthenticated 2-list search:

https://www.iesg.org/ibin/c5i?mid=6&rid=77&target=draft-name

The difference is the "bin" vs. "ibin".

Enjoy!

Glen

On 10/11/2010 9:53 AM, Julian Reschke wrote:
> On 11.10.2010 18:42, Russ Housley wrote:
>> AMS has set up a tool to search the IETF mail list, the announce mail
>> list, and the IESG mail list for messages with a particular draft name
>> in the subject name.  This will be a big help when looking for Last Call
>> comments.
>>
>> An ARO account is being set up for each AD to use the tool.  Accounts
>> are needed to keep the IESG mail list messages private.
>>
>> Please add a button or tab or some other appropriate widget to the
>> Datatracker to make it easy for the AD to find these messages.  This
>> must only be available to Datatracker users with the AD role.
>>
>> Here is the URL for the search:
>>
>>     https://www.iesg.org/bin/c5i?mid=6&rid=77&target=draft-name
>> ...
> 
> It would be cool if the same information, minus the view into the IESG
> mailing list, would be available to the public.
> 
> Best regards, Julian
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
> 

From julian.reschke@gmx.de  Mon Oct 11 23:21:34 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB8653A6782 for <codesprints@core3.amsl.com>; Mon, 11 Oct 2010 23:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.141
X-Spam-Level: 
X-Spam-Status: No, score=-104.141 tagged_above=-999 required=5 tests=[AWL=-1.542, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kSkMkkFCtOk for <codesprints@core3.amsl.com>; Mon, 11 Oct 2010 23:21:34 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 94EE63A63D3 for <codesprints@ietf.org>; Mon, 11 Oct 2010 23:21:33 -0700 (PDT)
Received: (qmail invoked by alias); 12 Oct 2010 06:22:45 -0000
Received: from p508FAE73.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.174.115] by mail.gmx.net (mp056) with SMTP; 12 Oct 2010 08:22:45 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+1y8VT2Cm178jItOJ9BeByEOZxMoUYEne2EgXJQf fA1EAsSdfwNIUH
Message-ID: <4CB3FEB1.1080603@gmx.de>
Date: Tue, 12 Oct 2010 08:22:41 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Glen Barney <glen@amsl.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com>
In-Reply-To: <4CB39782.5000808@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IESG <iesg@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 06:21:34 -0000

On 12.10.2010 01:02, Glen Barney wrote:
> Julian -
>
> Your wish is granted.  :-)
> ...

Thanks a lot!

Best regards, Julian

From peter.musgrave@magorcorp.com  Tue Oct 12 03:16:20 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9153D3A692D; Tue, 12 Oct 2010 03:16:20 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfDOYucD419h; Tue, 12 Oct 2010 03:16:17 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 48B723A692E; Tue, 12 Oct 2010 03:16:16 -0700 (PDT)
Received: by iwn10 with SMTP id 10so6061705iwn.31 for <multiple recipients>; Tue, 12 Oct 2010 03:17:30 -0700 (PDT)
Received: by 10.231.190.149 with SMTP id di21mr5505733ibb.166.1286878649868; Tue, 12 Oct 2010 03:17:29 -0700 (PDT)
Received: from [192.168.1.103] ([204.237.32.134]) by mx.google.com with ESMTPS id d40sm6203110ibc.1.2010.10.12.03.17.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 12 Oct 2010 03:17:28 -0700 (PDT)
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com>
Message-Id: <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Glen Barney <glen@amsl.com>
In-Reply-To: <4CB39782.5000808@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (7B500)
Mime-Version: 1.0 (iPad Mail 7B500)
Date: Tue, 12 Oct 2010 06:18:46 -0400
Cc: IESG <iesg@ietf.org>, "codesprints@ietf.org" <codesprints@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 10:16:21 -0000

Very cool.

Is there a way this same approach could be used to search just a =
specific WG list?

I'd love to add a link in the table of drafts on the WG page to search =
for threads on the draft.

(I'm ok to add the wg web part at the next sprint if I know what command =
to use...)

Regards

Peter Musgrave=20

Sent from my iPad

On 2010-10-11, at 7:02 PM, Glen Barney <glen@amsl.com> wrote:

> Julian -
>=20
> Your wish is granted.  :-)
>=20
> Enter this way for the authenticated 3-list search, as before:
>=20
> https://www.iesg.org/bin/c5i?mid=3D6&rid=3D77&target=3Ddraft-name
>=20
> Enter THIS way for the unauthenticated 2-list search:
>=20
> https://www.iesg.org/ibin/c5i?mid=3D6&rid=3D77&target=3Ddraft-name
>=20
> The difference is the "bin" vs. "ibin".
>=20
> Enjoy!
>=20
> Glen
>=20
> On 10/11/2010 9:53 AM, Julian Reschke wrote:
>> On 11.10.2010 18:42, Russ Housley wrote:
>>> AMS has set up a tool to search the IETF mail list, the announce =
mail
>>> list, and the IESG mail list for messages with a particular draft =
name
>>> in the subject name.  This will be a big help when looking for Last =
Call
>>> comments.
>>>=20
>>> An ARO account is being set up for each AD to use the tool.  =
Accounts
>>> are needed to keep the IESG mail list messages private.
>>>=20
>>> Please add a button or tab or some other appropriate widget to the
>>> Datatracker to make it easy for the AD to find these messages.  This
>>> must only be available to Datatracker users with the AD role.
>>>=20
>>> Here is the URL for the search:
>>>=20
>>>    https://www.iesg.org/bin/c5i?mid=3D6&rid=3D77&target=3Ddraft-name
>>> ...
>>=20
>> It would be cool if the same information, minus the view into the =
IESG
>> mailing list, would be available to the public.
>>=20
>> Best regards, Julian
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints
>>=20
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints

From glen@amsl.com  Tue Oct 12 09:43:14 2010
Return-Path: <glen@amsl.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56DF83A63EB; Tue, 12 Oct 2010 09:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.135
X-Spam-Level: 
X-Spam-Status: No, score=-102.135 tagged_above=-999 required=5 tests=[AWL=0.464, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOi4-ByKT4EN; Tue, 12 Oct 2010 09:43:13 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 92FD83A6916; Tue, 12 Oct 2010 09:43:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 7A601E08A9; Tue, 12 Oct 2010 09:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5+O-wNb7lrK2; Tue, 12 Oct 2010 09:44:28 -0700 (PDT)
Received: from [64.170.98.101] (dv9000.c5i.net [64.170.98.101]) by c1a.amsl.com (Postfix) with ESMTPSA id 5DE82E0860; Tue, 12 Oct 2010 09:44:28 -0700 (PDT)
Message-ID: <4CB4906A.6050400@amsl.com>
Date: Tue, 12 Oct 2010 09:44:26 -0700
From: Glen Barney <glen@amsl.com>
Organization: AMS
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Peter Musgrave <peter.musgrave@magorcorp.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com> <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com>
In-Reply-To: <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>, "codesprints@ietf.org" <codesprints@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 16:43:14 -0000

On 10/12/2010 3:18 AM, Peter Musgrave wrote:
> Very cool. Is there a way this same approach could be used to search 
> just a specific WG list? I'd love to add a link in the table of 
> drafts on the WG page to search for threads on the draft. (I'm ok to
> add the wg web part at the next sprint if I know what command to
> use...)

Perhaps.  We wrote this functionality into our ARO system because it can
do full text relevance searches across multiple lists.  We could
certainly do that for a single list, but it would mean having ARO
archive and index all of the lists on the system - which seems horribly
redundant to me, but which I'm happy to try to do.

Thoughts, anyone?

Glen

From housley@vigilsec.com  Tue Oct 12 10:22:16 2010
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31E753A69AC; Tue, 12 Oct 2010 10:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2IYC50Z8kI5; Tue, 12 Oct 2010 10:22:15 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 53F7F3A6822; Tue, 12 Oct 2010 10:22:15 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8DF85F24042; Tue, 12 Oct 2010 13:23:33 -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 Z5z2GjyQ5hCZ; Tue, 12 Oct 2010 13:23:27 -0400 (EDT)
Received: from [42.0.5.58] (unknown [129.174.97.34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id EDFBDF24041; Tue, 12 Oct 2010 13:23:32 -0400 (EDT)
Message-ID: <4CB4999C.2020604@vigilsec.com>
Date: Tue, 12 Oct 2010 13:23:40 -0400
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: codesprints@ietf.org
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de>	<4CB39782.5000808@amsl.com>	<7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com> <4CB4906A.6050400@amsl.com>
In-Reply-To: <4CB4906A.6050400@amsl.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 17:22:16 -0000

This is something that deserves a lot of discussion first.  I am aware
of discussions about other alternatives.

Russ

On 10/12/2010 12:44 PM, Glen Barney wrote:
> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>> Very cool. Is there a way this same approach could be used to search 
>> just a specific WG list? I'd love to add a link in the table of 
>> drafts on the WG page to search for threads on the draft. (I'm ok to
>> add the wg web part at the next sprint if I know what command to
>> use...)
> 
> Perhaps.  We wrote this functionality into our ARO system because it can
> do full text relevance searches across multiple lists.  We could
> certainly do that for a single list, but it would mean having ARO
> archive and index all of the lists on the system - which seems horribly
> redundant to me, but which I'm happy to try to do.
> 
> Thoughts, anyone?
> 
> Glen

From peter.musgrave@magorcorp.com  Tue Oct 12 10:29:34 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 457E93A696B; Tue, 12 Oct 2010 10:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.854
X-Spam-Level: 
X-Spam-Status: No, score=-101.854 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A551qWviKGit; Tue, 12 Oct 2010 10:29:33 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 52D9C3A69AC; Tue, 12 Oct 2010 10:29:33 -0700 (PDT)
Received: by qwc9 with SMTP id 9so2522272qwc.31 for <multiple recipients>; Tue, 12 Oct 2010 10:30:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.235.65 with SMTP id kf1mr6576428qcb.42.1286904647627; Tue, 12 Oct 2010 10:30:47 -0700 (PDT)
Received: by 10.229.42.196 with HTTP; Tue, 12 Oct 2010 10:30:47 -0700 (PDT)
In-Reply-To: <4CB4999C.2020604@vigilsec.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com> <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com> <4CB4906A.6050400@amsl.com> <4CB4999C.2020604@vigilsec.com>
Date: Tue, 12 Oct 2010 13:30:47 -0400
Message-ID: <AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IESG <iesg@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 17:29:34 -0000

Agreed. I did not realize that it involved a big component of backend
indexing....but that is not surprising given that the base web access
to the mailing list lacks a search.

First and foremost searchable mail lists would be useful.

Thanks,

Peter

On Tue, Oct 12, 2010 at 1:23 PM, Russ Housley <housley@vigilsec.com> wrote:
> This is something that deserves a lot of discussion first. =A0I am aware
> of discussions about other alternatives.
>
> Russ
>
> On 10/12/2010 12:44 PM, Glen Barney wrote:
>> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>>> Very cool. Is there a way this same approach could be used to search
>>> just a specific WG list? I'd love to add a link in the table of
>>> drafts on the WG page to search for threads on the draft. (I'm ok to
>>> add the wg web part at the next sprint if I know what command to
>>> use...)
>>
>> Perhaps. =A0We wrote this functionality into our ARO system because it c=
an
>> do full text relevance searches across multiple lists. =A0We could
>> certainly do that for a single list, but it would mean having ARO
>> archive and index all of the lists on the system - which seems horribly
>> redundant to me, but which I'm happy to try to do.
>>
>> Thoughts, anyone?
>>
>> Glen
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
>

From glen@amsl.com  Tue Oct 12 10:35:54 2010
Return-Path: <glen@amsl.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53B293A68E0; Tue, 12 Oct 2010 10:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.155
X-Spam-Level: 
X-Spam-Status: No, score=-102.155 tagged_above=-999 required=5 tests=[AWL=0.444, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohKva3maFdDA; Tue, 12 Oct 2010 10:35:52 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id DB5E23A6931; Tue, 12 Oct 2010 10:35:51 -0700 (PDT)
Received: by c1a.amsl.com (Postfix, from userid 1000) id DAE80E08BF; Tue, 12 Oct 2010 10:37:06 -0700 (PDT)
Date: Tue, 12 Oct 2010 10:37:06 -0700
From: "Glen Barney (AMS)" <glen@amsl.com>
To: Russ Housley <housley@vigilsec.com>
Message-ID: <20101012173706.GC23524@amsl.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com> <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com> <4CB4906A.6050400@amsl.com> <4CB4999C.2020604@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CB4999C.2020604@vigilsec.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: IESG <iesg@ietf.org>, codesprints@ietf.org
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 17:35:54 -0000

On Tue, Oct 12, 2010 at 01:23:40PM -0400, Russ Housley wrote:
> This is something that deserves a lot of discussion first.  I am aware
> of discussions about other alternatives.

Discuss away!  I'll be here if needed!  :-)

Glen

From suresh.krishnan@ericsson.com  Tue Oct 12 10:50:48 2010
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 401D63A69DF; Tue, 12 Oct 2010 10:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id di2LLMssZz2l; Tue, 12 Oct 2010 10:50:47 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id C53493A6910; Tue, 12 Oct 2010 10:50:46 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o9CI8oOf022408; Tue, 12 Oct 2010 13:08:51 -0500
Received: from [142.133.10.113] (147.117.20.213) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.2.234.1; Tue, 12 Oct 2010 13:51:56 -0400
Message-ID: <4CB49FF9.9030900@ericsson.com>
Date: Tue, 12 Oct 2010 13:50:49 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Peter Musgrave <peter.musgrave@magorcorp.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de>	<4CB39782.5000808@amsl.com>	<7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com>	<4CB4906A.6050400@amsl.com> <4CB4999C.2020604@vigilsec.com> <AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com>
In-Reply-To: <AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>, "codesprints@ietf.org" <codesprints@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 17:50:48 -0000

Hi Peter,
   Have you tried out this search engine for searching IETF mailing 
lists. It is not an official search engine but it gives me pretty good 
results.

http://www.google.com/cse/home?cx=006728497408158459967%3Aybxjdw-bjjw

Thanks
Suresh

On 10-10-12 01:30 PM, Peter Musgrave wrote:
> Agreed. I did not realize that it involved a big component of backend
> indexing....but that is not surprising given that the base web access
> to the mailing list lacks a search.
> 
> First and foremost searchable mail lists would be useful.
> 
> Thanks,
> 
> Peter
> 
> On Tue, Oct 12, 2010 at 1:23 PM, Russ Housley <housley@vigilsec.com> wrote:
>> This is something that deserves a lot of discussion first.  I am aware
>> of discussions about other alternatives.
>>
>> Russ
>>
>> On 10/12/2010 12:44 PM, Glen Barney wrote:
>>> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>>>> Very cool. Is there a way this same approach could be used to search
>>>> just a specific WG list? I'd love to add a link in the table of
>>>> drafts on the WG page to search for threads on the draft. (I'm ok to
>>>> add the wg web part at the next sprint if I know what command to
>>>> use...)
>>> Perhaps.  We wrote this functionality into our ARO system because it can
>>> do full text relevance searches across multiple lists.  We could
>>> certainly do that for a single list, but it would mean having ARO
>>> archive and index all of the lists on the system - which seems horribly
>>> redundant to me, but which I'm happy to try to do.
>>>
>>> Thoughts, anyone?
>>>
>>> Glen
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints
>>
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints


From peter.musgrave@magorcorp.com  Tue Oct 12 11:11:48 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 835463A6964; Tue, 12 Oct 2010 11:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.856
X-Spam-Level: 
X-Spam-Status: No, score=-101.856 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDNj9ZsMwKwe; Tue, 12 Oct 2010 11:11:45 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id A52343A67EB; Tue, 12 Oct 2010 11:11:27 -0700 (PDT)
Received: by qyk36 with SMTP id 36so2799410qyk.10 for <multiple recipients>; Tue, 12 Oct 2010 11:12:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.66.26 with SMTP id l26mr5901682qai.240.1286907162043; Tue, 12 Oct 2010 11:12:42 -0700 (PDT)
Received: by 10.229.42.196 with HTTP; Tue, 12 Oct 2010 11:12:41 -0700 (PDT)
In-Reply-To: <4CB49FF9.9030900@ericsson.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com> <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com> <4CB4906A.6050400@amsl.com> <4CB4999C.2020604@vigilsec.com> <AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com> <4CB49FF9.9030900@ericsson.com>
Date: Tue, 12 Oct 2010 14:12:41 -0400
Message-ID: <AANLkTinyTSXhw1OakZvr5eKh6xS5D9RwnYpWAvUMgJah@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IESG <iesg@ietf.org>, "codesprints@ietf.org" <codesprints@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Oct 2010 18:11:48 -0000

Cool site - I was hopeful....

Then I searched on draft-ietf-sipclf-problem-statement

and got two irrelevant hits.

(A web search reveals a lot more - but it's cluttered up with agenda
hits and WG pages etc.)

Peter

On Tue, Oct 12, 2010 at 1:50 PM, Suresh Krishnan
<suresh.krishnan@ericsson.com> wrote:
> Hi Peter,
> =A0Have you tried out this search engine for searching IETF mailing lists=
. It
> is not an official search engine but it gives me pretty good results.
>
> http://www.google.com/cse/home?cx=3D006728497408158459967%3Aybxjdw-bjjw
>
> Thanks
> Suresh
>
> On 10-10-12 01:30 PM, Peter Musgrave wrote:
>>
>> Agreed. I did not realize that it involved a big component of backend
>> indexing....but that is not surprising given that the base web access
>> to the mailing list lacks a search.
>>
>> First and foremost searchable mail lists would be useful.
>>
>> Thanks,
>>
>> Peter
>>
>> On Tue, Oct 12, 2010 at 1:23 PM, Russ Housley <housley@vigilsec.com>
>> wrote:
>>>
>>> This is something that deserves a lot of discussion first. =A0I am awar=
e
>>> of discussions about other alternatives.
>>>
>>> Russ
>>>
>>> On 10/12/2010 12:44 PM, Glen Barney wrote:
>>>>
>>>> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>>>>>
>>>>> Very cool. Is there a way this same approach could be used to search
>>>>> just a specific WG list? I'd love to add a link in the table of
>>>>> drafts on the WG page to search for threads on the draft. (I'm ok to
>>>>> add the wg web part at the next sprint if I know what command to
>>>>> use...)
>>>>
>>>> Perhaps. =A0We wrote this functionality into our ARO system because it=
 can
>>>> do full text relevance searches across multiple lists. =A0We could
>>>> certainly do that for a single list, but it would mean having ARO
>>>> archive and index all of the lists on the system - which seems horribl=
y
>>>> redundant to me, but which I'm happy to try to do.
>>>>
>>>> Thoughts, anyone?
>>>>
>>>> Glen
>>>
>>> _______________________________________________
>>> codesprints mailing list
>>> codesprints@ietf.org
>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints
>
>

From henrik@levkowetz.com  Wed Oct 13 03:11:25 2010
Return-Path: <henrik@levkowetz.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56FD93A68E9; Wed, 13 Oct 2010 03:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7G6EFFzEuMp4; Wed, 13 Oct 2010 03:11:19 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 1E8143A6976; Wed, 13 Oct 2010 03:11:04 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:52210 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1P5yJ8-0004Q4-Kd; Wed, 13 Oct 2010 12:11:46 +0200
Message-ID: <4CB585DA.20109@levkowetz.com>
Date: Wed, 13 Oct 2010 12:11:38 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Peter Musgrave <peter.musgrave@magorcorp.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de>	<4CB39782.5000808@amsl.com>	<7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com>	<4CB4906A.6050400@amsl.com> <4CB4999C.2020604@vigilsec.com>	<AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com>	<4CB49FF9.9030900@ericsson.com> <AANLkTinyTSXhw1OakZvr5eKh6xS5D9RwnYpWAvUMgJah@mail.gmail.com>
In-Reply-To: <AANLkTinyTSXhw1OakZvr5eKh6xS5D9RwnYpWAvUMgJah@mail.gmail.com>
X-Enigmail-Version: 1.1.1
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: peter.musgrave@magorcorp.com, suresh.krishnan@ericsson.com, iesg@ietf.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, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: "codesprints@ietf.org" <codesprints@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 13 Oct 2010 10:11:25 -0000

Hi Peter,

At the top of the sipclf status page on tools.ietf.org, there's a search
box for the sip-clf mailing list, which uses google to provide the search
result.  I just tried a search for "draft-ietf-sipclf-problem-statement"
there, and got what seems to be relevant results.

I note, though, that the results would have been better if the draft name
had been quoted, but I can't add quotes routinely around the search term
as that would be less good in other situations.  Maybe I should add a
mailing list search link for each draft specifically on the status display?


Best,

	Henrik

On 2010-10-12 20:12 Peter Musgrave said:
> Cool site - I was hopeful....
> 
> Then I searched on draft-ietf-sipclf-problem-statement
> 
> and got two irrelevant hits.
> 
> (A web search reveals a lot more - but it's cluttered up with agenda
> hits and WG pages etc.)
> 
> Peter
> 
> On Tue, Oct 12, 2010 at 1:50 PM, Suresh Krishnan
> <suresh.krishnan@ericsson.com> wrote:
>> Hi Peter,
>>  Have you tried out this search engine for searching IETF mailing lists. It
>> is not an official search engine but it gives me pretty good results.
>>
>> http://www.google.com/cse/home?cx=006728497408158459967%3Aybxjdw-bjjw
>>
>> Thanks
>> Suresh
>>
>> On 10-10-12 01:30 PM, Peter Musgrave wrote:
>>>
>>> Agreed. I did not realize that it involved a big component of backend
>>> indexing....but that is not surprising given that the base web access
>>> to the mailing list lacks a search.
>>>
>>> First and foremost searchable mail lists would be useful.
>>>
>>> Thanks,
>>>
>>> Peter
>>>
>>> On Tue, Oct 12, 2010 at 1:23 PM, Russ Housley <housley@vigilsec.com>
>>> wrote:
>>>>
>>>> This is something that deserves a lot of discussion first.  I am aware
>>>> of discussions about other alternatives.
>>>>
>>>> Russ
>>>>
>>>> On 10/12/2010 12:44 PM, Glen Barney wrote:
>>>>>
>>>>> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>>>>>>
>>>>>> Very cool. Is there a way this same approach could be used to search
>>>>>> just a specific WG list? I'd love to add a link in the table of
>>>>>> drafts on the WG page to search for threads on the draft. (I'm ok to
>>>>>> add the wg web part at the next sprint if I know what command to
>>>>>> use...)
>>>>>
>>>>> Perhaps.  We wrote this functionality into our ARO system because it can
>>>>> do full text relevance searches across multiple lists.  We could
>>>>> certainly do that for a single list, but it would mean having ARO
>>>>> archive and index all of the lists on the system - which seems horribly
>>>>> redundant to me, but which I'm happy to try to do.
>>>>>
>>>>> Thoughts, anyone?
>>>>>
>>>>> Glen
>>>>
>>>> _______________________________________________
>>>> codesprints mailing list
>>>> codesprints@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>>
>>> _______________________________________________
>>> codesprints mailing list
>>> codesprints@ietf.org
>>> https://www.ietf.org/mailman/listinfo/codesprints
>>
>>
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
> 

From peter.musgrave@magorcorp.com  Wed Oct 13 03:23:20 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53E9A3A68ED; Wed, 13 Oct 2010 03:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.857
X-Spam-Level: 
X-Spam-Status: No, score=-101.857 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eA6jk43cvbgR; Wed, 13 Oct 2010 03:23:19 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 335D23A68EC; Wed, 13 Oct 2010 03:23:19 -0700 (PDT)
Received: by qwc9 with SMTP id 9so3033260qwc.31 for <multiple recipients>; Wed, 13 Oct 2010 03:24:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.215.76 with SMTP id hd12mr7415605qcb.44.1286965473281; Wed, 13 Oct 2010 03:24:33 -0700 (PDT)
Received: by 10.229.42.196 with HTTP; Wed, 13 Oct 2010 03:24:33 -0700 (PDT)
In-Reply-To: <4CB585DA.20109@levkowetz.com>
References: <4CB33E93.6030506@vigilsec.com> <4CB34108.2080507@gmx.de> <4CB39782.5000808@amsl.com> <7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com> <4CB4906A.6050400@amsl.com> <4CB4999C.2020604@vigilsec.com> <AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com> <4CB49FF9.9030900@ericsson.com> <AANLkTinyTSXhw1OakZvr5eKh6xS5D9RwnYpWAvUMgJah@mail.gmail.com> <4CB585DA.20109@levkowetz.com>
Date: Wed, 13 Oct 2010 06:24:33 -0400
Message-ID: <AANLkTi=bynjVTyJnK2B3+gByYzi1WVc0GXVS1HJP+Gyj@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "codesprints@ietf.org" <codesprints@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 13 Oct 2010 10:23:20 -0000

Excellent. That's useful - and I never noticed it before.

How do people feel about adding some kind of search icon as a column
in the active drafts table on the WG page?

It would launch the same search that Henrick describes below.

(I was also planning on adding a column for an ipr link - which is
greyed out if there are no ipr statements for the draft/RFC).

Opinions?

Peter Musgrave

On Wed, Oct 13, 2010 at 6:11 AM, Henrik Levkowetz <henrik@levkowetz.com> wr=
ote:
> Hi Peter,
>
> At the top of the sipclf status page on tools.ietf.org, there's a search
> box for the sip-clf mailing list, which uses google to provide the search
> result. =A0I just tried a search for "draft-ietf-sipclf-problem-statement=
"
> there, and got what seems to be relevant results.
>
> I note, though, that the results would have been better if the draft name
> had been quoted, but I can't add quotes routinely around the search term
> as that would be less good in other situations. =A0Maybe I should add a
> mailing list search link for each draft specifically on the status displa=
y?
>
>
> Best,
>
> =A0 =A0 =A0 =A0Henrik
>
> On 2010-10-12 20:12 Peter Musgrave said:
>> Cool site - I was hopeful....
>>
>> Then I searched on draft-ietf-sipclf-problem-statement
>>
>> and got two irrelevant hits.
>>
>> (A web search reveals a lot more - but it's cluttered up with agenda
>> hits and WG pages etc.)
>>
>> Peter
>>
>> On Tue, Oct 12, 2010 at 1:50 PM, Suresh Krishnan
>> <suresh.krishnan@ericsson.com> wrote:
>>> Hi Peter,
>>> =A0Have you tried out this search engine for searching IETF mailing lis=
ts. It
>>> is not an official search engine but it gives me pretty good results.
>>>
>>> http://www.google.com/cse/home?cx=3D006728497408158459967%3Aybxjdw-bjjw
>>>
>>> Thanks
>>> Suresh
>>>
>>> On 10-10-12 01:30 PM, Peter Musgrave wrote:
>>>>
>>>> Agreed. I did not realize that it involved a big component of backend
>>>> indexing....but that is not surprising given that the base web access
>>>> to the mailing list lacks a search.
>>>>
>>>> First and foremost searchable mail lists would be useful.
>>>>
>>>> Thanks,
>>>>
>>>> Peter
>>>>
>>>> On Tue, Oct 12, 2010 at 1:23 PM, Russ Housley <housley@vigilsec.com>
>>>> wrote:
>>>>>
>>>>> This is something that deserves a lot of discussion first. =A0I am aw=
are
>>>>> of discussions about other alternatives.
>>>>>
>>>>> Russ
>>>>>
>>>>> On 10/12/2010 12:44 PM, Glen Barney wrote:
>>>>>>
>>>>>> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>>>>>>>
>>>>>>> Very cool. Is there a way this same approach could be used to searc=
h
>>>>>>> just a specific WG list? I'd love to add a link in the table of
>>>>>>> drafts on the WG page to search for threads on the draft. (I'm ok t=
o
>>>>>>> add the wg web part at the next sprint if I know what command to
>>>>>>> use...)
>>>>>>
>>>>>> Perhaps. =A0We wrote this functionality into our ARO system because =
it can
>>>>>> do full text relevance searches across multiple lists. =A0We could
>>>>>> certainly do that for a single list, but it would mean having ARO
>>>>>> archive and index all of the lists on the system - which seems horri=
bly
>>>>>> redundant to me, but which I'm happy to try to do.
>>>>>>
>>>>>> Thoughts, anyone?
>>>>>>
>>>>>> Glen
>>>>>
>>>>> _______________________________________________
>>>>> codesprints mailing list
>>>>> codesprints@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>>>
>>>> _______________________________________________
>>>> codesprints mailing list
>>>> codesprints@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>
>>>
>> _______________________________________________
>> codesprints mailing list
>> codesprints@ietf.org
>> https://www.ietf.org/mailman/listinfo/codesprints
>>
>

From henrik@levkowetz.com  Fri Oct 15 14:24:46 2010
Return-Path: <henrik@levkowetz.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9580E3A6B94; Fri, 15 Oct 2010 14:24:46 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mICPrMAci6Ss; Fri, 15 Oct 2010 14:24:45 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id C9FBD3A6D29; Fri, 15 Oct 2010 14:24:44 -0700 (PDT)
Received: from 90-230-136-60-no45.tbcn.telia.com ([90.230.136.60]:60064 helo=[192.168.1.65]) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1P6rmX-0002hJ-24; Fri, 15 Oct 2010 23:25:42 +0200
Message-ID: <4CB8C6CE.1040807@levkowetz.com>
Date: Fri, 15 Oct 2010 23:25:34 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Peter Musgrave <peter.musgrave@magorcorp.com>
References: <4CB33E93.6030506@vigilsec.com>	<4CB34108.2080507@gmx.de>	<4CB39782.5000808@amsl.com>	<7476C9E7-0942-4AD5-97D2-27E086094A7A@magorcorp.com>	<4CB4906A.6050400@amsl.com>	<4CB4999C.2020604@vigilsec.com>	<AANLkTi=i9557Z7HUT83WYaVdZgBWD0XcR7Eq8z29JBKp@mail.gmail.com>	<4CB49FF9.9030900@ericsson.com>	<AANLkTinyTSXhw1OakZvr5eKh6xS5D9RwnYpWAvUMgJah@mail.gmail.com>	<4CB585DA.20109@levkowetz.com> <AANLkTi=bynjVTyJnK2B3+gByYzi1WVc0GXVS1HJP+Gyj@mail.gmail.com>
In-Reply-To: <AANLkTi=bynjVTyJnK2B3+gByYzi1WVc0GXVS1HJP+Gyj@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 90.230.136.60
X-SA-Exim-Rcpt-To: peter.musgrave@magorcorp.com, suresh.krishnan@ericsson.com, iesg@ietf.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, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: "codesprints@ietf.org" <codesprints@ietf.org>, IESG <iesg@ietf.org>
Subject: Re: [codesprints] Search URL added to IESG Datatracker
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 15 Oct 2010 21:24:46 -0000

Hi Peter,

On 2010-10-13 12:24 Peter Musgrave said the following:
> Excellent. That's useful - and I never noticed it before.
> 
> How do people feel about adding some kind of search icon as a column
> in the active drafts table on the WG page?
> 
> It would launch the same search that Henrick describes below.
> 
> (I was also planning on adding a column for an ipr link - which is
> greyed out if there are no ipr statements for the draft/RFC).

Sounds like the datatracker WG pages will soon be catching up with the
tools pages :-)

I've added a spyglass next to the draft name on the WG status page on
tools.ietf.org, linked to a google search for that particular draft on
the WG mailing list.


Best,

	Henrik

> Opinions?
> 
> Peter Musgrave
> 
> On Wed, Oct 13, 2010 at 6:11 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>> Hi Peter,
>>
>> At the top of the sipclf status page on tools.ietf.org, there's a search
>> box for the sip-clf mailing list, which uses google to provide the search
>> result.  I just tried a search for "draft-ietf-sipclf-problem-statement"
>> there, and got what seems to be relevant results.
>>
>> I note, though, that the results would have been better if the draft name
>> had been quoted, but I can't add quotes routinely around the search term
>> as that would be less good in other situations.  Maybe I should add a
>> mailing list search link for each draft specifically on the status display?
>>
>>
>> Best,
>>
>>        Henrik
>>
>> On 2010-10-12 20:12 Peter Musgrave said:
>>> Cool site - I was hopeful....
>>>
>>> Then I searched on draft-ietf-sipclf-problem-statement
>>>
>>> and got two irrelevant hits.
>>>
>>> (A web search reveals a lot more - but it's cluttered up with agenda
>>> hits and WG pages etc.)
>>>
>>> Peter
>>>
>>> On Tue, Oct 12, 2010 at 1:50 PM, Suresh Krishnan
>>> <suresh.krishnan@ericsson.com> wrote:
>>>> Hi Peter,
>>>>  Have you tried out this search engine for searching IETF mailing lists. It
>>>> is not an official search engine but it gives me pretty good results.
>>>>
>>>> http://www.google.com/cse/home?cx=006728497408158459967%3Aybxjdw-bjjw
>>>>
>>>> Thanks
>>>> Suresh
>>>>
>>>> On 10-10-12 01:30 PM, Peter Musgrave wrote:
>>>>>
>>>>> Agreed. I did not realize that it involved a big component of backend
>>>>> indexing....but that is not surprising given that the base web access
>>>>> to the mailing list lacks a search.
>>>>>
>>>>> First and foremost searchable mail lists would be useful.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Peter
>>>>>
>>>>> On Tue, Oct 12, 2010 at 1:23 PM, Russ Housley <housley@vigilsec.com>
>>>>> wrote:
>>>>>>
>>>>>> This is something that deserves a lot of discussion first.  I am aware
>>>>>> of discussions about other alternatives.
>>>>>>
>>>>>> Russ
>>>>>>
>>>>>> On 10/12/2010 12:44 PM, Glen Barney wrote:
>>>>>>>
>>>>>>> On 10/12/2010 3:18 AM, Peter Musgrave wrote:
>>>>>>>>
>>>>>>>> Very cool. Is there a way this same approach could be used to search
>>>>>>>> just a specific WG list? I'd love to add a link in the table of
>>>>>>>> drafts on the WG page to search for threads on the draft. (I'm ok to
>>>>>>>> add the wg web part at the next sprint if I know what command to
>>>>>>>> use...)
>>>>>>>
>>>>>>> Perhaps.  We wrote this functionality into our ARO system because it can
>>>>>>> do full text relevance searches across multiple lists.  We could
>>>>>>> certainly do that for a single list, but it would mean having ARO
>>>>>>> archive and index all of the lists on the system - which seems horribly
>>>>>>> redundant to me, but which I'm happy to try to do.
>>>>>>>
>>>>>>> Thoughts, anyone?
>>>>>>>
>>>>>>> Glen
>>>>>>
>>>>>> _______________________________________________
>>>>>> codesprints mailing list
>>>>>> codesprints@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>>>>
>>>>> _______________________________________________
>>>>> codesprints mailing list
>>>>> codesprints@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>>
>>>>
>>> _______________________________________________
>>> codesprints mailing list
>>> codesprints@ietf.org
>>> https://www.ietf.org/mailman/listinfo/codesprints
>>>
>>
> 

From rjsparks@nostrum.com  Wed Oct 20 10:15:20 2010
Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A06663A68A4 for <codesprints@core3.amsl.com>; Wed, 20 Oct 2010 10:15:20 -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=[AWL=0.000,  BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDvjoUiee7bV for <codesprints@core3.amsl.com>; Wed, 20 Oct 2010 10:15:18 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 1CB6D3A68F7 for <codesprints@ietf.org>; Wed, 20 Oct 2010 10:15:15 -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 o9KHGjiL009573 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <codesprints@ietf.org>; Wed, 20 Oct 2010 12:16:48 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
From: Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Oct 2010 12:16:43 -0500
Message-Id: <2536DB89-FD85-4FC8-95C9-BE9E8A915260@nostrum.com>
To: codesprints@ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: [codesprints] Grooming and prioritizing the items on EnhancementIdeas
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Oct 2010 17:15:20 -0000

Folks -

The list of things on the EnhancementIdeas page has gotten pretty long, =
and it would benefit from an editing/restructuring pass.
While we're doing that, I'd like to capture some sense of priority for =
each of the items there. It would help to know what each of you=20
find the most important.

Please take a moment to skim the list an choose the 3 most important =
things from your perspective (those that you think we should
focus on earlier rather than later) and reply with that to this list. =
Don't worry about how hard/easy they might be, and don't feel like=20
you're volunteering to make them happen by responding to this question. =
(You should be volunteering for things on the Sprint page at=20
<http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF79Sprint>, and now is =
also a good time to do that).

For your convenience, the EnhancementIdeas page is at
<http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas>

Thanks for your help!

RjS=

From housley@vigilsec.com  Wed Oct 20 11:14:50 2010
Return-Path: <housley@vigilsec.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B2283A6822 for <codesprints@core3.amsl.com>; Wed, 20 Oct 2010 11:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6rddNiU986jl for <codesprints@core3.amsl.com>; Wed, 20 Oct 2010 11:14:45 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 9EB533A689B for <codesprints@ietf.org>; Wed, 20 Oct 2010 11:14:44 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 24830F24069; Wed, 20 Oct 2010 14:16:20 -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 ma0yc6og4keB; Wed, 20 Oct 2010 14:16:16 -0400 (EDT)
Received: from [192.168.2.107] (pool-96-231-149-87.washdc.fios.verizon.net [96.231.149.87]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 0DDB7F2405D; Wed, 20 Oct 2010 14:16:19 -0400 (EDT)
Message-ID: <4CBF31FE.2070809@vigilsec.com>
Date: Wed, 20 Oct 2010 14:16:30 -0400
From: Russ Housley <housley@vigilsec.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: codesprints@ietf.org
References: <2536DB89-FD85-4FC8-95C9-BE9E8A915260@nostrum.com>
In-Reply-To: <2536DB89-FD85-4FC8-95C9-BE9E8A915260@nostrum.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: [codesprints] Grooming and prioritizing the items on EnhancementIdeas
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 20 Oct 2010 18:14:51 -0000

Add a button to invoke the ARO email list search functions to the main
document page. -- This one is the highest priority to the IESG, and
other have expressed interest too.  Please put this on the top of the
priority list.

****

Complete the new Django-based ID submission tool.  -- Done under
contract, and is almost finished.

Rewrite draft expiration script in Python.
Rewrite IETF last call ending script in Python. -- both of these are
under contract, and they should be done fairly soon.

Better email archive search. For example, "show all emails from
(ietf,iesg,secdir,gen-art,mib-doctors) that have draft-ietf-foo-bar in
the subject line". -- A start was made at this.  It might be good to
have a thread on the tools mail list to figure out where to go next.

Better tools for developing/discussing working group charters -- The
contract was just awarded to develop the specifications.  Wen the
specifications are done, the tool will be developed under contract.

****

Remember search results when clicking "Sign In". -- I find this one
annoying every day!

****

Add IPR information to IETF Last Call announcements automatically --
This is very important for everyone.

Add document names to the Subject line of Protocol Action and Document
Action messages (see <
http://www.ietf.org/mail-archive/web/codesprints/current/msg00136.html>
-- Many people have expressed a desire for the Internet-Draft name in
the subject line.




On 10/20/2010 1:16 PM, Robert Sparks wrote:
> Folks -
> 
> The list of things on the EnhancementIdeas page has gotten pretty long, and it would benefit from an editing/restructuring pass.
> While we're doing that, I'd like to capture some sense of priority for each of the items there. It would help to know what each of you 
> find the most important.
> 
> Please take a moment to skim the list an choose the 3 most important things from your perspective (those that you think we should
> focus on earlier rather than later) and reply with that to this list. Don't worry about how hard/easy they might be, and don't feel like 
> you're volunteering to make them happen by responding to this question. (You should be volunteering for things on the Sprint page at 
> <http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF79Sprint>, and now is also a good time to do that).
> 
> For your convenience, the EnhancementIdeas page is at
> <http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas>
> 
> Thanks for your help!
> 
> RjS
> _______________________________________________
> codesprints mailing list
> codesprints@ietf.org
> https://www.ietf.org/mailman/listinfo/codesprints
> 

From henrik@levkowetz.com  Fri Oct 22 07:38:53 2010
Return-Path: <henrik@levkowetz.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B55E3A6863 for <codesprints@core3.amsl.com>; Fri, 22 Oct 2010 07:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZd590NmMOiV for <codesprints@core3.amsl.com>; Fri, 22 Oct 2010 07:38:50 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id B50C23A66B4 for <codesprints@ietf.org>; Fri, 22 Oct 2010 07:38:49 -0700 (PDT)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:51465 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1P9Imt-0003Ym-Oq; Fri, 22 Oct 2010 16:40:09 +0200
Message-ID: <4CC1A245.5040400@levkowetz.com>
Date: Fri, 22 Oct 2010 16:40:05 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <2536DB89-FD85-4FC8-95C9-BE9E8A915260@nostrum.com> <4CBF31FE.2070809@vigilsec.com>
In-Reply-To: <4CBF31FE.2070809@vigilsec.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig31D31AD8A9B614D53231E463"
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: housley@vigilsec.com, codesprints@ietf.org, rpelletier@isoc.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: Ray Pelletier <rpelletier@isoc.org>, codesprints@ietf.org
Subject: Re: [codesprints] Grooming and prioritizing the items on	EnhancementIdeas
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 22 Oct 2010 14:38:53 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig31D31AD8A9B614D53231E463
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Russ,

On 2010-10-20 20:16 Russ Housley said:
> Add a button to invoke the ARO email list search functions to the main
> document page. -- This one is the highest priority to the IESG, and
> other have expressed interest too.  Please put this on the top of the
> priority list.

Done, as reflected on the EnhancementIdeas page now:

  http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas

> ****
>=20
> Complete the new Django-based ID submission tool.  -- Done under
> contract, and is almost finished.

Ack.  Taken off the sprint issue list.

> Rewrite draft expiration script in Python.
> Rewrite IETF last call ending script in Python. -- both of these are
> under contract, and they should be done fairly soon.

Ack.  Taken off the sprint issue list

> Better email archive search. For example, "show all emails from
> (ietf,iesg,secdir,gen-art,mib-doctors) that have draft-ietf-foo-bar in
> the subject line". -- A start was made at this.  It might be good to
> have a thread on the tools mail list to figure out where to go next.

Prioritized (but below your first priority)

> Better tools for developing/discussing working group charters -- The
> contract was just awarded to develop the specifications.  Wen the
> specifications are done, the tool will be developed under contract.

Ack.  Taken off the sprint issue list, with an explanatory note.

> ****
>=20
> Remember search results when clicking "Sign In". -- I find this one
> annoying every day!

Added to priority list.

> ****
>=20
> Add IPR information to IETF Last Call announcements automatically --
> This is very important for everyone.

Added to priority list

> Add document names to the Subject line of Protocol Action and Document
> Action messages (see <
> http://www.ietf.org/mail-archive/web/codesprints/current/msg00136.html>=

> -- Many people have expressed a desire for the Internet-Draft name in
> the subject line.

Added to priority list.


Best,

	Henrik


--------------enig31D31AD8A9B614D53231E463
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkzBokYACgkQeVhrtTJkXCNZOgCg/aTVMXDtKzWaCI4G3T4b/Q6d
HygAoI6PnBCOcJAzpQKy+4N70lk0WMmV
=ZP0d
-----END PGP SIGNATURE-----

--------------enig31D31AD8A9B614D53231E463--

From henrik@merlot.tools.ietf.org  Tue Oct 26 07:11:43 2010
Return-Path: <henrik@merlot.tools.ietf.org>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2EDB3A6964 for <codesprints@core3.amsl.com>; Tue, 26 Oct 2010 07:11:43 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eH8A2xF7a3Hk for <codesprints@core3.amsl.com>; Tue, 26 Oct 2010 07:11:41 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 295973A6969 for <codesprints@ietf.org>; Tue, 26 Oct 2010 07:11:41 -0700 (PDT)
Received: from henrik by merlot.tools.ietf.org with local (Exim 4.72) (envelope-from <henrik@merlot.tools.ietf.org>) id 1PAkGo-0008Q0-4G; Tue, 26 Oct 2010 16:12:58 +0200
Date: Tue, 26 Oct 2010 16:12:58 +0200
Message-Id: <E1PAkGo-0008Q0-4G@merlot.tools.ietf.org>
To: codesprints@ietf.org
From: Henrik Levkowetz <henrik@merlot.tools.ietf.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: amorris@amsl.com, avezza@amsl.com, cmorgan@amsl.com, codesprints@ietf.org, fenner@fenron.net, glen@amsl.com, henrik@levkowetz.com, housley@vigilsec.com, rjs@nostrum.com
X-SA-Exim-Mail-From: henrik@merlot.tools.ietf.org
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
Cc: rjs@nostrum.com, avezza@amsl.com, fenner@fenron.net, amorris@amsl.com, cmorgan@amsl.com
Subject: [codesprints] New datatracker release: v3.07
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 26 Oct 2010 14:11:43 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v3.07, generated when running the mkrelease script.

Release notes:

ietfdb (3.07)
  From esanchez@yaco.es:
  * Merged in Yaco's Liaison Management Tool Port & Rewrite.  Enjoy!
  Note: Deploying this release requires additional steps; to verify
  that liaison related settings in settings.py are correct, and to create
  new tables and update existing tables and table content.  The latter
  is done as South migrations (see http://south.aeracode.org/ for more
  info on the South app).  More extensiive documentation about the actions
  needed are provided in the user manual (doc/LSMT_user_manual.pdf in
  the release).  The brief version follows:
    # 8<----------
    # First the regular checkout and prepare:
       cd /a/www/ietf-datatracker
       svn co http://svn.tools.ietf.org/svn/tools/ietfdb/tags/3.07
       cp web/ietf/settings_local.py 3.07/ietf/
       cd 3.07
    # Verify that the new variables in settings.py are correct; if not,
    # add the correct settings in settings_local.py and inform the release
    # manager of the correct settings so they can be incorporated in the
    # next release.  The variables in question are (as set in the release):
    #
    # # The email address from wich all liaison emails come:
    # LIAISON_UNIVERSAL_FROM = 'Liaison Statement Management Tool <lsmt@' + IETF_DOMAIN + '>'
    #
    # # The filesystem path where the liaison attachments will be saved:
    # LIAISON_ATTACH_PATH = '/a/www/ietf-datatracker/documents/LIAISON/'
    #
    # # The url from where the webserver serves the liaison attachments
    # LIAISON_ATTACH_URL = '/documents/LIAISON/'
    # Next, the changes to the MySQL tables will be done.
    # You can list the table migrations which will be applied if desired,
    # this should list migrations from 0001_... to 0009_... under liaisons:
       PYTHONPATH=$PWD ietf/manage.py migrate --list
    # Apply the migrations:
 
       PYTHONPATH=$PWD ietf/manage.py migrate
    # Add the static/doc location as statically served files to the apache
    # configuration.  Fix line 6 in etc/apache2/vhoosts.d/ietf-datatracker.common
    # to read:
    #  <LocationMatch "^/(?!(cgi-bin|css|documents|error|idst|images|js|media|doc|private)/|robots.txt).*$">
    # (i.e., add '|doc' to the exception list).
    # Then carry on with the usual actions:
       cd ../
       rm ./web; ln -s 3.07 web
       sudo /etc/init.d/apache restart
    # 8<----------
  Once the datatracker is up and running with the new liaison tool in
  place, liaison role assignments have to be done as described in
  the LSMT user manual (in doc/LSMT_user_manual.pdf) page 14, summarized
  by Patrik on the yaco-liaison-tool mailing list:
    1. Add the IAB and IETF chairs, wg chairs, area directors etc as
    apropriate (as described in the document).
    2. Add the liaisons in the IETF assigned and named on the IAB list of
    liaisons.

The new version is available through SVN checkout, with
  'svn checkout http://svn.tools.ietf.org/svn/tools/ietfdb/tags/3.07'

Regards,

	Henrik
	(via the mkrelease script)


From henrik@merlot.tools.ietf.org  Wed Oct 27 04:52:14 2010
Return-Path: <henrik@merlot.tools.ietf.org>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E35C3A69CE for <codesprints@core3.amsl.com>; Wed, 27 Oct 2010 04:52:14 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7crP9Gp5smXP for <codesprints@core3.amsl.com>; Wed, 27 Oct 2010 04:52:13 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 51C4A3A69D5 for <codesprints@ietf.org>; Wed, 27 Oct 2010 04:52:13 -0700 (PDT)
Received: from henrik by merlot.tools.ietf.org with local (Exim 4.72) (envelope-from <henrik@merlot.tools.ietf.org>) id 1PB4ZB-0007VY-2k; Wed, 27 Oct 2010 13:53:17 +0200
Date: Wed, 27 Oct 2010 13:53:17 +0200
Message-Id: <E1PB4ZB-0007VY-2k@merlot.tools.ietf.org>
To: codesprints@ietf.org
From: Henrik Levkowetz <henrik@merlot.tools.ietf.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Rcpt-To: amorris@amsl.com, avezza@amsl.com, cmorgan@amsl.com, codesprints@ietf.org, fenner@fenron.net, glen@amsl.com, henrik@levkowetz.com, housley@vigilsec.com, rjs@nostrum.com
X-SA-Exim-Mail-From: henrik@merlot.tools.ietf.org
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
Cc: rjs@nostrum.com, avezza@amsl.com, fenner@fenron.net, amorris@amsl.com, cmorgan@amsl.com
Subject: [codesprints] New datatracker release: v3.08
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Oct 2010 11:52:14 -0000

Hi,

This is an automatic notification about a new datatracker release, 
v3.08, generated when running the mkrelease script.

Release notes:

ietfdb (3.08)
  From olau@iola.dk:
  * Ported scripts for expiration of drafts and last-calls, and sending
    scheduled announcements.
    The command-line front-ends are in bin/ as expire-ids, expire-last-calls
    and send-scheduled-mail. The last one already existed with some code, but
    it's not certain it actually worked. The new one accepts the same arguments
    as the Perl script (there's a little bit of help if you run it).
    All three log to syslog.  They need to be started from cron with
    PYTHONPATH=/a/www/ietf-datatracker/web , in the same manner as other
    scripts which use the django models to interact with the database.

The new version is available through SVN checkout, with
  'svn checkout http://svn.tools.ietf.org/svn/tools/ietfdb/tags/3.08'

Regards,

	Henrik
	(via the mkrelease script)


From glen@amsl.com  Wed Oct 27 09:39:55 2010
Return-Path: <glen@amsl.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3E4E3A680A for <codesprints@core3.amsl.com>; Wed, 27 Oct 2010 09:39:55 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZWBPDOxIUej5 for <codesprints@core3.amsl.com>; Wed, 27 Oct 2010 09:39:54 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 90F103A6A68 for <codesprints@ietf.org>; Wed, 27 Oct 2010 09:39:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 32C17E08C2; Wed, 27 Oct 2010 09:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmb1bXNj+bcd; Wed, 27 Oct 2010 09:41:07 -0700 (PDT)
Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id BBEC1E08A3; Wed, 27 Oct 2010 09:41:06 -0700 (PDT)
Message-ID: <4CC85620.3020405@amsl.com>
Date: Wed, 27 Oct 2010 09:41:04 -0700
From: Glen Barney <glen@amsl.com>
Organization: AMS
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@merlot.tools.ietf.org>
References: <E1PAkGo-0008Q0-4G@merlot.tools.ietf.org>
In-Reply-To: <E1PAkGo-0008Q0-4G@merlot.tools.ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: rjs@nostrum.com, codesprints@ietf.org, avezza@amsl.com, fenner@fenron.net, amorris@amsl.com, cmorgan@amsl.com
Subject: Re: [codesprints] New datatracker release: v3.07
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Oct 2010 16:39:56 -0000

An attempt to install 3.07 has failed.  I am communicating with Henrik
offline to determine what is needed.  More information to follow.

Glen

On 10/26/2010 7:12 AM, Henrik Levkowetz wrote:
> Hi,
> 
> This is an automatic notification about a new datatracker release, 
> v3.07, generated when running the mkrelease script.
> 
> Release notes:
> 
> ietfdb (3.07)
>   From esanchez@yaco.es:
>   * Merged in Yaco's Liaison Management Tool Port & Rewrite.  Enjoy!
>   Note: Deploying this release requires additional steps; to verify
>   that liaison related settings in settings.py are correct, and to create
>   new tables and update existing tables and table content.  The latter
>   is done as South migrations (see http://south.aeracode.org/ for more
>   info on the South app).  More extensiive documentation about the actions
>   needed are provided in the user manual (doc/LSMT_user_manual.pdf in
>   the release).  The brief version follows:
>     # 8<----------
>     # First the regular checkout and prepare:
>        cd /a/www/ietf-datatracker
>        svn co http://svn.tools.ietf.org/svn/tools/ietfdb/tags/3.07
>        cp web/ietf/settings_local.py 3.07/ietf/
>        cd 3.07
>     # Verify that the new variables in settings.py are correct; if not,
>     # add the correct settings in settings_local.py and inform the release
>     # manager of the correct settings so they can be incorporated in the
>     # next release.  The variables in question are (as set in the release):
>     #
>     # # The email address from wich all liaison emails come:
>     # LIAISON_UNIVERSAL_FROM = 'Liaison Statement Management Tool <lsmt@' + IETF_DOMAIN + '>'
>     #
>     # # The filesystem path where the liaison attachments will be saved:
>     # LIAISON_ATTACH_PATH = '/a/www/ietf-datatracker/documents/LIAISON/'
>     #
>     # # The url from where the webserver serves the liaison attachments
>     # LIAISON_ATTACH_URL = '/documents/LIAISON/'
>     # Next, the changes to the MySQL tables will be done.
>     # You can list the table migrations which will be applied if desired,
>     # this should list migrations from 0001_... to 0009_... under liaisons:
>        PYTHONPATH=$PWD ietf/manage.py migrate --list
>     # Apply the migrations:
>  
>        PYTHONPATH=$PWD ietf/manage.py migrate
>     # Add the static/doc location as statically served files to the apache
>     # configuration.  Fix line 6 in etc/apache2/vhoosts.d/ietf-datatracker.common
>     # to read:
>     #  <LocationMatch "^/(?!(cgi-bin|css|documents|error|idst|images|js|media|doc|private)/|robots.txt).*$">
>     # (i.e., add '|doc' to the exception list).
>     # Then carry on with the usual actions:
>        cd ../
>        rm ./web; ln -s 3.07 web
>        sudo /etc/init.d/apache restart
>     # 8<----------
>   Once the datatracker is up and running with the new liaison tool in
>   place, liaison role assignments have to be done as described in
>   the LSMT user manual (in doc/LSMT_user_manual.pdf) page 14, summarized
>   by Patrik on the yaco-liaison-tool mailing list:
>     1. Add the IAB and IETF chairs, wg chairs, area directors etc as
>     apropriate (as described in the document).
>     2. Add the liaisons in the IETF assigned and named on the IAB list of
>     liaisons.
> 
> The new version is available through SVN checkout, with
>   'svn checkout http://svn.tools.ietf.org/svn/tools/ietfdb/tags/3.07'
> 
> Regards,
> 
> 	Henrik
> 	(via the mkrelease script)
> 

From glen@amsl.com  Wed Oct 27 12:42:24 2010
Return-Path: <glen@amsl.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36DFF3A69EF for <codesprints@core3.amsl.com>; Wed, 27 Oct 2010 12:42:24 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+o8wOcPPAki for <codesprints@core3.amsl.com>; Wed, 27 Oct 2010 12:42:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 523813A69C8 for <codesprints@ietf.org>; Wed, 27 Oct 2010 12:42:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 007FAE08C6; Wed, 27 Oct 2010 12:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8L7FLz9BIru; Wed, 27 Oct 2010 12:44:09 -0700 (PDT)
Received: from [192.168.1.100] (173-8-133-91-SFBA.hfc.comcastbusiness.net [173.8.133.91]) by c1a.amsl.com (Postfix) with ESMTPSA id 92FD1E070F; Wed, 27 Oct 2010 12:44:09 -0700 (PDT)
Message-ID: <4CC88108.4030603@amsl.com>
Date: Wed, 27 Oct 2010 12:44:08 -0700
From: Glen Barney <glen@amsl.com>
Organization: AMS
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: henrik@levkowetz.com
References: <E1PB4ZB-0007VY-2k@merlot.tools.ietf.org>
In-Reply-To: <E1PB4ZB-0007VY-2k@merlot.tools.ietf.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: rjs@nostrum.com, codesprints@ietf.org, avezza@amsl.com, fenner@fenron.net, amorris@amsl.com, cmorgan@amsl.com
Subject: Re: [codesprints] New datatracker release: v3.08
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Oct 2010 19:42:24 -0000

All the fixes for 3.07 and 3.08 have been applied, and Datatracker 3.08
is now released.

Glen

On 10/27/2010 4:53 AM, Henrik Levkowetz wrote:
> Hi,
> 
> This is an automatic notification about a new datatracker release, 
> v3.08, generated when running the mkrelease script.
> 
> Release notes:
> 
> ietfdb (3.08)
>   From olau@iola.dk:
>   * Ported scripts for expiration of drafts and last-calls, and sending
>     scheduled announcements.
>     The command-line front-ends are in bin/ as expire-ids, expire-last-calls
>     and send-scheduled-mail. The last one already existed with some code, but
>     it's not certain it actually worked. The new one accepts the same arguments
>     as the Perl script (there's a little bit of help if you run it).
>     All three log to syslog.  They need to be started from cron with
>     PYTHONPATH=/a/www/ietf-datatracker/web , in the same manner as other
>     scripts which use the django models to interact with the database.
> 
> The new version is available through SVN checkout, with
>   'svn checkout http://svn.tools.ietf.org/svn/tools/ietfdb/tags/3.08'
> 
> Regards,
> 
> 	Henrik
> 	(via the mkrelease script)
> 

From rjsparks@nostrum.com  Fri Oct 29 08:13:29 2010
Return-Path: <rjsparks@nostrum.com>
X-Original-To: codesprints@core3.amsl.com
Delivered-To: codesprints@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D897A3A6A79 for <codesprints@core3.amsl.com>; Fri, 29 Oct 2010 08:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3piBA2Intzgu for <codesprints@core3.amsl.com>; Fri, 29 Oct 2010 08:13:28 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id AD7ED3A6A21 for <codesprints@ietf.org>; Fri, 29 Oct 2010 08:13:27 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-71-48-4.dllstx.fios.verizon.net [173.71.48.4]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o9TFFLmD005611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <codesprints@ietf.org>; Fri, 29 Oct 2010 10:15:21 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
From: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-13-820475832
Date: Fri, 29 Oct 2010 10:15:20 -0500
References: <5812B0B6-287E-4B79-8F9F-B6A6ED833EF0@frobbit.se>
To: codesprints@ietf.org
Message-Id: <B530A274-A9E2-47B2-888C-7DDC53CB0484@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Received-SPF: pass (nostrum.com: 173.71.48.4 is authenticated by a trusted mechanism)
Subject: [codesprints] Fwd: New version of the liaison tool
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 29 Oct 2010 15:13:30 -0000

--Apple-Mail-13-820475832
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Sprinters -

One of the things we've been asked to help with is putting some extra =
pressure on finding rough-spots in the
new liaison management tool. The information below should help the group =
that decides to take this on.

Thanks!

RjS

Begin forwarded message:

> From: Patrik F=E4ltstr=F6m <patrik@frobbit.se>
> Date: October 29, 2010 10:08:08 AM CDT
> To: Robert Sparks <rjsparks@nostrum.com>
> Cc: ITU-T Liaison coordination <itu-t-liaisons@iab.org>, IAB IAB =
<iab@iab.org>, The IESG <iesg@ietf.org>, Henrik Levkowetz =
<henrik@levkowetz.com>
> Subject: Re: New version of the liaison tool
>=20
> Please!
>=20
> At the moment, those are the functions I think are the most important =
ones.
>=20
> This is not a secret, but people getting the message below should know =
the data in the tool is not in shape yet, and there might be bugs...as =
long as that is known, it is better the more people try it so we can =
iron out problems.
>=20
>   Patrik
>=20
> On 29 okt 2010, at 17.06, Robert Sparks wrote:
>=20
>> Patrik -
>>=20
>> We've been planning to ask some of the code sprinters to provide some =
additional testing on a non-production=20
>> instance of this tool. May I share this message with that group? Are =
there any new features you think would benefit
>> from the extra stressing more than others?
>>=20
>> RjS
>>=20
>> On Oct 29, 2010, at 8:10 AM, Patrik F=E4ltstr=F6m wrote:
>>=20
>>> Hi,
>>>=20
>>> We have since a few days a new version of the liaison tool. You =
might not see so many changes in the tool itself:
>>>=20
>>> https://datatracker.ietf.org/liaison/
>>>=20
>>> But there are four very important changes that hopefully will help =
future management of liaison statements:
>>>=20
>>> - One liaison statement can be linked to another one (i.e. one =
outgoing liaison is often a response to an incoming -- and the other way =
around).
>>>=20
>>> - It is possible for non-secretariat people to add incoming liaison =
statements to the tool (and not only outgoing).
>>>=20
>>> - We have the ability to have a "deadline" on some action on a =
liaison statement. And the ability to set the "responsible person" for =
that action.
>>>=20
>>> - A multitude of access rights have been added so we even can let =
liaisons *TO* us in external organisations add things directly into/with =
the tool.
>>>=20
>>> At the moment the "raw" data is added to the tool, but over time we =
are now working with converting data, add people to the tool etc. But =
given the upcoming IETF people are so busy that I think the actual clean =
up of data in the toll might take a month or longer.
>>>=20
>>> Because of this, I made the choice of NOT announcing this to the =
general public/ietf mailing list yet. I will do another announcement =
when we have a bit more updated data and an example of the fact things =
actually work.
>>>=20
>>> But please continue to use the tool as much as possible!
>>>=20
>>>=20
>>> I would like to thank Henrik and ask him to pass my thanks to the =
rest of the team for efficient work, and say that I think the (new) way =
of developing things in the tool-set we have worked well.
>>>=20
>>>  Regards, Patrik F=E4ltstr=F6m
>>>  Liaison from IETF to ITU-T
>>>=20
>>=20
>>=20
>=20


--Apple-Mail-13-820475832
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Sprinters -<div><br></div><div>One of the things we've been asked to =
help with is putting some extra pressure on finding rough-spots in =
the</div><div>new liaison management tool. The information below should =
help the group that decides to take this =
on.</div><div><br></div><div>Thanks!</div><div><br></div><div>RjS<br><div>=
<br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">Patrik F=E4ltstr=F6m =
&lt;<a =
href=3D"mailto:patrik@frobbit.se">patrik@frobbit.se</a>&gt;<br></span></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">October 29, 2010 =
10:08:08 AM CDT<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">Robert Sparks &lt;<a =
href=3D"mailto:rjsparks@nostrum.com">rjsparks@nostrum.com</a>&gt;<br></spa=
n></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">ITU-T Liaison =
coordination &lt;<a =
href=3D"mailto:itu-t-liaisons@iab.org">itu-t-liaisons@iab.org</a>&gt;, =
IAB IAB &lt;<a href=3D"mailto:iab@iab.org">iab@iab.org</a>&gt;, The IESG =
&lt;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;, Henrik =
Levkowetz &lt;<a =
href=3D"mailto:henrik@levkowetz.com">henrik@levkowetz.com</a>&gt;<br></spa=
n></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>Re: New version =
of the liaison tool</b><br></span></div><br><div>Please!<br><br>At the =
moment, those are the functions I think are the most important =
ones.<br><br>This is not a secret, but people getting the message below =
should know the data in the tool is not in shape yet, and there might be =
bugs...as long as that is known, it is better the more people try it so =
we can iron out problems.<br><br> &nbsp;&nbsp;Patrik<br><br>On 29 okt =
2010, at 17.06, Robert Sparks wrote:<br><br><blockquote =
type=3D"cite">Patrik -<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">We've been =
planning to ask some of the code sprinters to provide some additional =
testing on a non-production <br></blockquote><blockquote =
type=3D"cite">instance of this tool. May I share this message with that =
group? Are there any new features you think would =
benefit<br></blockquote><blockquote type=3D"cite">from the extra =
stressing more than others?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">RjS<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Oct 29, =
2010, at 8:10 AM, Patrik F=E4ltstr=F6m =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Hi,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">We have since a few days a new =
version of the liaison tool. You might not see so many changes in the =
tool itself:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://datatracker.ietf.org/liaison/">https://datatracker.ietf.or=
g/liaison/</a><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">But there are four very =
important changes that hopefully will help future management of liaison =
statements:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">- One liaison statement can be =
linked to another one (i.e. one outgoing liaison is often a response to =
an incoming -- and the other way =
around).<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">- It is possible for =
non-secretariat people to add incoming liaison statements to the tool =
(and not only outgoing).<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">- We have the ability to have a =
"deadline" on some action on a liaison statement. And the ability to set =
the "responsible person" for that =
action.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">- A multitude of access rights =
have been added so we even can let liaisons *TO* us in external =
organisations add things directly into/with the =
tool.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">At the moment the "raw" data is =
added to the tool, but over time we are now working with converting =
data, add people to the tool etc. But given the upcoming IETF people are =
so busy that I think the actual clean up of data in the toll might take =
a month or longer.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Because of this, I made the =
choice of NOT announcing this to the general public/ietf mailing list =
yet. I will do another announcement when we have a bit more updated data =
and an example of the fact things actually =
work.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">But please continue to use the =
tool as much as possible!<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I would like to thank Henrik and =
ask him to pass my thanks to the rest of the team for efficient work, =
and say that I think the (new) way of developing things in the tool-set =
we have worked well.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"> &nbsp;Regards, Patrik =
F=E4ltstr=F6m<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"> &nbsp;Liaison from IETF to =
ITU-T<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br></div></blockquote></div><br></div></bo=
dy></html>=

--Apple-Mail-13-820475832--