Re: Agenda development support

"Adam W. Montville" <adam.w.montville@gmail.com> Sat, 14 November 2015 15:15 UTC

Return-Path: <adam.w.montville@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B565A1A87EA for <wgchairs@ietfa.amsl.com>; Sat, 14 Nov 2015 07:15:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uwd6eqdhcwQn for <wgchairs@ietfa.amsl.com>; Sat, 14 Nov 2015 07:15:57 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F05F61A87DB for <wgchairs@ietf.org>; Sat, 14 Nov 2015 07:15:56 -0800 (PST)
Received: by oige206 with SMTP id e206so64331592oig.2 for <wgchairs@ietf.org>; Sat, 14 Nov 2015 07:15:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=d9h7gZ9vdbGDetU/KyFJFl3gvIdKjW8NDjKAhknvMIQ=; b=DBfTdWphACNGhVQaslADt/SKLMNQJ3VuCB1mxpx9smCMhFztgcLFAh4Bjr/XqCc8bS PRYgcRmNJfGuO5XgiGY2giAMA7kUSTG8C85QXINbZVgrR47LUSQnQ7slljwapAZkiVwK JJrYo0br3RGUJ+Uk+Ct1AfyJ7j2fJf7o/EgnxQkCi4SG/gFcNKKo4LXvR62h9vYpGxAS uggEbccfOs6TuJ2PufXc5I+HgnUUqoND08d1gJgpwZfw0IiNlYh2O2eE5msTyEHfi1Mz gBuAbGD4u0iwaP6k4T0vPD1apJt/nekLmPzbTA8ScC5T2vdPJEfyGCzepRPBX4p/EcUL zqew==
X-Received: by 10.202.79.137 with SMTP id d131mr15122964oib.20.1447514156399; Sat, 14 Nov 2015 07:15:56 -0800 (PST)
Received: from [192.168.1.72] (99-64-100-131.lightspeed.austtx.sbcglobal.net. [99.64.100.131]) by smtp.gmail.com with ESMTPSA id x131sm8160436oix.27.2015.11.14.07.15.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 14 Nov 2015 07:15:55 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A95EC476-AF5E-4F7F-946F-C21D2D0AEBA8"
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: Agenda development support
From: "Adam W. Montville" <adam.w.montville@gmail.com>
In-Reply-To: <8780D359-9CEE-4A51-9813-80167202F858@chopps.org>
Date: Sat, 14 Nov 2015 09:15:50 -0600
Message-Id: <D4D62421-66AF-4421-946E-C9B0C8526D27@gmail.com>
References: <B6616D7F-0518-44C3-9EF7-F4A9AE013FD4@cisco.com> <8780D359-9CEE-4A51-9813-80167202F858@chopps.org>
To: Christian Hopps <chopps@chopps.org>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/wgchairs/tb93nXjZKGW2TlAkn0IuZKWazNo>
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Nov 2015 15:15:59 -0000

Hi Chris,

I’m having some issues running wgstatus.  I was able to get the tool at least running under python3, but I’m not really a python guy so my environment might be jacked in some way.  What I did was:

1. Update pip3
2. Install requirements (pip3 install -r requirements.txt)
3. Attempt to run “python3 wgstatus/main.py” with arguments

That runs, but even when I provide the “last-meeting” switch, the tool is telling me that I need to supply the last meeting.

Any thoughts on how to properly install your tool?

Kind regards,

Adam

> On Nov 12, 2015, at 2:21 PM, Christian Hopps <chopps@chopps.org> wrote:
> 
> Talk about ships in the night! I wrote something to do something very similar I believe during this IETF.
> 
> https://github.com/choppsv1/wgstatus <https://github.com/choppsv1/wgstatus>
> 
> Chris.
> 
>> On Nov 2, 2015, at 7:13 PM, Fred Baker (fred) <fred@cisco.com <mailto:fred@cisco.com>> wrote:
>> 
>> I have developed a tool for my own amusement, and wonder whether others would find it useful. If appropriate I can get it filed on the tools page or somehow supported in the data tracker. It is based on Henrik's data tracker API, which is to say "not screen scraping". It's in perl.
>> 
>> Here's the problem I'm trying to solve. I can look at https://datatracker.ietf.org/wg/v6ops/documents/ <https://datatracker.ietf.org/wg/v6ops/documents/>, and figure out anything I need to know about my working group's drafts. The information is all there. However, it is somewhat inaccessible, in the sense that it is cluttered with information that, while relevant, isn't particularly useful in agenda analysis, and the sort capability (that used to be there?) isn't there (any more).
>> 
>> What I'm trying to figure out, when planning an agenda, is:
>>  - what working group drafts have been updated since the last meeting
>>    (which I will then do a mail search to determine the latest status of)
>>  - what individual submissions to the working group have come in
>>    (which I will then do a mail search for supporting commentary regarding).
>> 
>> I may also have other drafts I am specifically interested in; this time, we had an invited talk on a technology that Facebook is experimenting with, that is actually in discussion in nvo3 (draft-herbert-nvo3-ila).
>> 
>> So therefore, I enter something like
>> ietf-agenda-analysis.pl --date 2015-07-22 v6ops draft-herbert-nvo3-ila-01.txt
>> or
>> ietf-agenda-analysis.pl --date 2015-07-22 v6ops draft-herbert-nvo3-ila
>> 
>> and get back the following (today). My question is whether other chairs would find this kind of capability useful, and whether I should bring it up with the tools team. If it's useful to you, you're welcome to my script regardless, on an open source basis.
>> 
>> RFC Editor: EDIT
>> 	2015-10-26	draft-ietf-v6ops-siit-dc
>> 	2015-10-26	draft-ietf-v6ops-siit-dc-2xlat
>> 	2015-10-26	draft-ietf-v6ops-siit-eam
>> 	2015-10-19	draft-ietf-v6ops-pmtud-ecmp-problem
>> 
>> WG: In WG Last Call
>> 	2015-11-01	draft-ietf-v6ops-ipv6-ehs-in-real-world
>> 
>> WG: Parked WG Document
>> 	2015-10-14	draft-ietf-v6ops-mobile-device-profile
>> 
>> WG: Submitted to IESG for Publication
>> 	2015-10-30	draft-ietf-v6ops-reducing-ra-energy-consumption
>> 
>> WG: Unupdated WG Document
>> 	2015-07-06	draft-ietf-v6ops-dhcpv6-slaac-problem
>> 	2015-05-03	draft-ietf-v6ops-ula-usage-recommendations
>> 
>> WG: Updated WG Document
>> 	2015-11-01	draft-ietf-v6ops-host-addr-availability
>> 	2015-11-01	draft-ietf-v6ops-unique-ipv6-prefix-per-host
>> 	2015-10-19	draft-ietf-v6ops-design-choices
>> 
>> Individual Submission: Unupdated
>> 	2015-07-06	draft-akira-v6ops-mape-experience
>> 	2015-07-06	draft-xcf-v6ops-chinatelecom-deployment
>> 	2015-07-05	draft-hui-v6ops-ipv6trans-select-nfv
>> 	2015-07-05	draft-xli-v6ops-cernet-deployment
>> 	2015-07-05	draft-yang-v6ops-ipv6tran-select
>> 	2015-06-26	draft-vyncke-v6ops-ipv6-only-thin-clients
>> 	2015-06-25	draft-sun-v6ops-xlat-multi
>> 
>> Individual Submission: Updated
>> 	2015-10-19	draft-jjmb-v6ops-unique-ipv6-prefix-per-host
>> 	2015-10-19	draft-xu-v6ops-dslite-redundancy
>> 	2015-10-15	draft-gont-v6ops-ipv6-ehs-packet-drops
>> 	2015-10-12	draft-herbert-nvo3-ila
>> 	2015-10-10	draft-bao-v6ops-rfc6145bis
>> 	2015-09-21	draft-ybai-v6ops-ipv6-for-openstack
>> <ietf-agenda-analysis.pl>
>