Re: Agenda development support

["Adam W. Montville" <[e-mail]>]

Perfect, thanks!

> On Nov 15, 2015, at 12:17 AM, Christian Hopps <[e-mail]> wrote:
> 
> Hi Adam,
> 
> Sorry I had some old code left around for direct invocation. I've fixed that so everything should work now that way.
> 
> Note: if you want to install locally you can cd to the git clone and enter: "pip install -e ."
> 
> I've also uploaded to pypi so you can also install directly with "pip install wgstatus".
> 
> Thanks,
> Chris.
> 
>> On Nov 14, 2015, at 10:15 AM, Adam W. Montville <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> 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 <[e-mail] <mailto:[e-mail]>> 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) <[e-mail] <mailto:[e-mail]>> 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>
>>> 
>> 
>