
From esanchez@yaco.es  Mon Jan 16 02:35:22 2012
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 627EA21F858E for <yaco-community-tool@ietfa.amsl.com>; Mon, 16 Jan 2012 02:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tp6AoiXY1a0D for <yaco-community-tool@ietfa.amsl.com>; Mon, 16 Jan 2012 02:35:21 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2A021F8591 for <yaco-community-tool@ietf.org>; Mon, 16 Jan 2012 02:35:21 -0800 (PST)
Received: by wgbdq11 with SMTP id dq11so311996wgb.13 for <yaco-community-tool@ietf.org>; Mon, 16 Jan 2012 02:35:20 -0800 (PST)
Received: by 10.180.19.168 with SMTP id g8mr18776267wie.4.1326710120456; Mon, 16 Jan 2012 02:35:20 -0800 (PST)
Received: from [192.168.0.193] ([77.227.215.107]) by mx.google.com with ESMTPS id ex2sm33211018wib.1.2012.01.16.02.35.18 (version=SSLv3 cipher=OTHER); Mon, 16 Jan 2012 02:35:19 -0800 (PST)
Message-ID: <4F13FD65.1080109@yaco.es>
Date: Mon, 16 Jan 2012 11:35:17 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: yaco-community-tool@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [yaco-community-tool] Beta server update
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>,  <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jan 2012 10:35:22 -0000

    Hi all, happy new year :)

    The beta server is updated with all the requests and suggestions 
gathered in this list. I summarize the most important changes:

    Fixes:
    * Fixed a registration bug when the email already exists in the system
    * Fixed the rule that adds drafts that contain certain string.

    Changes:
    * In list views, drafts are shown first and then RFCs
    * RFC number is displayed instead of the original draft filename
    * CSV export files contain all available fields instead of only the 
configured ones in the list display.
    * URLs of public views are changed so now they contain a secret hash 
only know by the owner of the list.

    Server configuration:
    * Configured submission system. Now new drafts and new versions of 
drafts could be submitted to test the notification feature.
    * Fixed permissions of stream_user. Now this user is allowed to 
change the state of any draft.

    Best,

From rjsparks@nostrum.com  Wed Jan 18 11:57:28 2012
Return-Path: <rjsparks@nostrum.com>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEDF1F0C47 for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 11:57:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.423
X-Spam-Level: 
X-Spam-Status: No, score=-102.423 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjyB18H9etyj for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 11:57:27 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 60F1C1F0C40 for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 11:57:27 -0800 (PST)
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 q0IJvQOb033508 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 13:57:26 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F172425.1020309@nostrum.com>
Date: Wed, 18 Jan 2012 13:57:25 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: yaco-community-tool@ietf.org
References: <4F13FD65.1080109@yaco.es>
In-Reply-To: <4F13FD65.1080109@yaco.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: Re: [yaco-community-tool] Beta server update
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>,  <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2012 19:57:28 -0000

Hi Emilio -

<http://beta.community.yaco.es/doc/ad/robert.sparks/> is producing 
incorrect content
(whether logged in or not) - the columns are not right. When logged in 
as an AD (when it's
the "My documents" page), it doesn't make sense for the add/remove from 
my personal list
knobs to be there. It might make sense for them to be there if its 
someone else looking at
the page, but that might not be worth the extra code maintenance.

RjS




On 1/16/12 4:35 AM, "Emilio A. Sánchez" wrote:
>    Hi all, happy new year :)
>
>    The beta server is updated with all the requests and suggestions 
> gathered in this list. I summarize the most important changes:
>
>    Fixes:
>    * Fixed a registration bug when the email already exists in the system
>    * Fixed the rule that adds drafts that contain certain string.
>
>    Changes:
>    * In list views, drafts are shown first and then RFCs
>    * RFC number is displayed instead of the original draft filename
>    * CSV export files contain all available fields instead of only the 
> configured ones in the list display.
>    * URLs of public views are changed so now they contain a secret 
> hash only know by the owner of the list.
>
>    Server configuration:
>    * Configured submission system. Now new drafts and new versions of 
> drafts could be submitted to test the notification feature.
>    * Fixed permissions of stream_user. Now this user is allowed to 
> change the state of any draft.
>
>    Best,
> _______________________________________________
> yaco-community-tool mailing list
> yaco-community-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-community-tool

From esanchez@yaco.es  Wed Jan 18 12:31:33 2012
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C225B21F85E9 for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 12:31:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FvORf0Ddoir for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 12:31:33 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id DFD7F21F85E0 for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 12:31:32 -0800 (PST)
Received: by wgbdq11 with SMTP id dq11so2674421wgb.13 for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 12:31:32 -0800 (PST)
Received: by 10.180.8.103 with SMTP id q7mr16510897wia.1.1326918692024; Wed, 18 Jan 2012 12:31:32 -0800 (PST)
Received: from [192.168.0.193] ([77.227.215.107]) by mx.google.com with ESMTPS id dr5sm58813847wib.0.2012.01.18.12.31.29 (version=SSLv3 cipher=OTHER); Wed, 18 Jan 2012 12:31:30 -0800 (PST)
Message-ID: <4F172C20.3060307@yaco.es>
Date: Wed, 18 Jan 2012 21:31:28 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: yaco-community-tool@ietf.org
References: <4F13FD65.1080109@yaco.es> <4F172425.1020309@nostrum.com>
In-Reply-To: <4F172425.1020309@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-community-tool] Beta server update
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>,  <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2012 20:31:33 -0000

    Hi Robert,

    You are right! I didn't realize that the template that renders each 
row of these tables is used in more than one view.

    I've fixed it, now these links are only displayed when you do a 
draft search.

    Thank you for your report!

    Best,

El 18/01/12 20:57, Robert Sparks escribió:
> Hi Emilio -
>
> <http://beta.community.yaco.es/doc/ad/robert.sparks/> is producing
> incorrect content
> (whether logged in or not) - the columns are not right. When logged in
> as an AD (when it's
> the "My documents" page), it doesn't make sense for the add/remove from
> my personal list
> knobs to be there. It might make sense for them to be there if its
> someone else looking at
> the page, but that might not be worth the extra code maintenance.
>
> RjS
>
>
>
>
> On 1/16/12 4:35 AM, "Emilio A. Sánchez" wrote:
>> Hi all, happy new year :)
>>
>> The beta server is updated with all the requests and suggestions
>> gathered in this list. I summarize the most important changes:
>>
>> Fixes:
>> * Fixed a registration bug when the email already exists in the system
>> * Fixed the rule that adds drafts that contain certain string.
>>
>> Changes:
>> * In list views, drafts are shown first and then RFCs
>> * RFC number is displayed instead of the original draft filename
>> * CSV export files contain all available fields instead of only the
>> configured ones in the list display.
>> * URLs of public views are changed so now they contain a secret hash
>> only know by the owner of the list.
>>
>> Server configuration:
>> * Configured submission system. Now new drafts and new versions of
>> drafts could be submitted to test the notification feature.
>> * Fixed permissions of stream_user. Now this user is allowed to change
>> the state of any draft.
>>
>> Best,
>> _______________________________________________
>> yaco-community-tool mailing list
>> yaco-community-tool@ietf.org
>> https://www.ietf.org/mailman/listinfo/yaco-community-tool
> _______________________________________________
> yaco-community-tool mailing list
> yaco-community-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-community-tool


From rjsparks@nostrum.com  Wed Jan 18 14:37:04 2012
Return-Path: <rjsparks@nostrum.com>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 371A011E80A2 for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 14:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4NQuLCwjhhIy for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 14:37:03 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id ECB0811E807F for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 14:37:02 -0800 (PST)
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 q0IMau0K057151 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 18 Jan 2012 16:36:57 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F174988.3010902@nostrum.com>
Date: Wed, 18 Jan 2012 16:36:56 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: yaco-community-tool@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>
References: <4EE28025.5030307@nostrum.com>
In-Reply-To: <4EE28025.5030307@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Subject: Re: [yaco-community-tool] Observations from my second attempt at using the community tool
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>,  <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2012 22:37:04 -0000

I revisited these with the updated test instance. Comments inline.

On 12/9/11 3:39 PM, Robert Sparks wrote:
> (The first attempt stopped abruptly with a crash).
>
> I spent some time trying to exercise this tool and ran into several 
> problems.
>
> I want to ask about what the expectations of the current 
> implementation and test instance were
> before asserting that these are bugs.
>
> Should the search results be accurate? I set up a rule to search for 
> all documents
> containing the text "location conveyance". It only found seven. There 
> are many, many
> more.
So it looks like rules of the form "All I-Ds that contain a particular 
text string" are
case-sensitive. I added three rules
"location conveyance" found 4 docs
"Location conveyance" found  1 doc
"Location Conveyance" found 8 docs

Now to sanity check that with my copy of the draft repository:
unexplicable:draft rjsparks$ grep -irl "location conveyance" . | perl 
-pe 's/-[0-9]{2}.(txt|xml)//' | sort -u | wc
       77      77    2884

So there are many drafts the search isn't finding.

Now the Documents tab shows only 8 drafts. I hope that's because the 4 
and 1 above are subsets
of the 8. All the docs returned are draft-ietf-geopriv- or 
draft-ietf-ecrit-. There are a slew of
individual submissions that don't get matched.

Some important ones missing include:
draft-ietf-geopriv-policy-uri
draft-ietf-sipcore-location-conveyance

Now I can see the second not being in the set if you are filtering out 
drafts that have become RFCs
(its not obvious that you should do that though), but the first is still 
in IESG evaluation - very much
in the middle of process, so why isn't it being found?

>
> Should sorting work? - I tried the various sort options in the display 
> customization section.
> Alphabetical by title or by filename worked. Publication date didn't. 
> Sorting by change or
> significant change produced results that didn't make sense.
Sorting by Publication date still doesn't work, and the sort by change 
of status still doesn't make sense.
(It might help it make sense if it showed the date of the change of 
status somehow).
>
> I could only subscribe to lists or feeds from the read-only view of 
> the list.
> It is very unintuitive to look there for those options - why aren't 
> they available to me on my regular view?
I see you added links to the export tab. I still find the disparity 
between the read only view page and the modifiable page disconcerting.
>
> The view URL itself is coding the username into the URL - why? I 
> _assume_ you have coded policy
> that doesn't let me look at Adam's list just because I know his login. 
> If that's the case, stopping at
> community/personal or using something like community/personal/mainlist 
> and figuring out which
> list to look at by seeing who was logged in seems a lot safer.
This is fixed.
>
> Similarly, the way this currently constructs the "read only" view 
> necessarily makes all of the lists
> public. The intent of 6293 was that these be private by default and 
> only exposed if the person
> wants to expose them. As it is now, I know I can see Adam's list by 
> looking at
> http://beta.community.yaco.es/community/personal/adam%40nostrum.com/view/
Fixed.
>
> I logged in as stream_user. It does not let me change any state on any 
> documents, so I couldn't
> test the notification features.
I confirmed that this works, at least to the level of making updates in 
the RSS feed.
I supposedly successfully subscribed to the email list for any change, 
but I haven't seen any
email after making changes to one of the matched documents as 
stream_user. There's a chance
that it's caught in grey-listing, but that would be odd given that I 
completed the subscription
email-confirmation dance just a few minutes before. Can you see any 
evidence that it _tried_
to send me email related to the change in a state of one of the 
documents on the list? If so,
please send me the message-id?

You responded to the rest below already - there's nothing there for me 
to retest
> The option to list "changed within 1,2,7 days" as separate columns 
> would be better met with
> just listing a column with the number of days since the last change 
> actually in the column. 

>
> I forgot (and am subsequently surprised) that 6293 restricts users to 
> only one list.
> I don't expect that restriction to survive actual use - I hope the 
> code will be easy to adapt to the notion of
> multiple lists later.
>
> RjS
>
>
>

From esanchez@yaco.es  Wed Jan 18 22:17:05 2012
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B839711E8076 for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 22:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tnv4vfsgGws6 for <yaco-community-tool@ietfa.amsl.com>; Wed, 18 Jan 2012 22:17:05 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id E8BD911E8072 for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 22:17:04 -0800 (PST)
Received: by wibhn9 with SMTP id hn9so801255wib.31 for <yaco-community-tool@ietf.org>; Wed, 18 Jan 2012 22:17:03 -0800 (PST)
Received: by 10.181.13.208 with SMTP id fa16mr41886073wid.12.1326953823705; Wed, 18 Jan 2012 22:17:03 -0800 (PST)
Received: from [192.168.0.193] ([77.227.215.107]) by mx.google.com with ESMTPS id eq5sm15074376wib.2.2012.01.18.22.17.01 (version=SSLv3 cipher=OTHER); Wed, 18 Jan 2012 22:17:02 -0800 (PST)
Message-ID: <4F17B55C.6090302@yaco.es>
Date: Thu, 19 Jan 2012 07:17:00 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: yaco-community-tool@ietf.org, rjsparks@nostrum.com
References: <20120118222836.26888.97857.idtracker@localhost>
In-Reply-To: <20120118222836.26888.97857.idtracker@localhost>
X-Forwarded-Message-Id: <20120118222836.26888.97857.idtracker@localhost>
Content-Type: multipart/mixed; boundary="------------010709010904020904030501"
Subject: [yaco-community-tool] Fwd: [Django test] Personal ID list of rjsparks@nostrum.com notification: Changes on draft-ietf-geopriv-deref-protocol
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>,  <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 06:17:05 -0000

This is a multi-part message in MIME format.
--------------010709010904020904030501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

    Hi Robert,

    I'll have to check the rest of comments in your last emails. But 
there is the email sent as a notification when you did changes in the 
draft draft-ietf-geopriv-deref-protocol.

    You didn't receive it cause the beta server is not in production 
mode so it doesn't send emails to the real destinations. Instead it 
sends the emails to a configured email address, in this case: 
ietf-tracker-dev-emails@googlegroups.com, esanchez@yaco.es, 
yaco-community-tool@ietf.org

    The email was received in my email address. It was sent also to the 
yaco-community-tool list but I think it was blocked cause the from 
address is not subscribed to the list.

-------- Mensaje original --------
Asunto: [Django test] Personal ID list of rjsparks@nostrum.com 
notification: Changes on draft-ietf-geopriv-deref-protocol
Fecha: Wed, 18 Jan 2012 14:28:36 -0800
De: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Para: ietf-tracker-dev-emails@googlegroups.com, esanchez@yaco.es, 
yaco-community-tool@ietf.org

The attached message would have been sent, but the tracker is in test mode.
It was not sent to anybody.



--------------010709010904020904030501
Content-Type: message/rfc822;
 name="ForwardedMessage.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="ForwardedMessage.eml"

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: 
Subject: Personal ID list of rjsparks@nostrum.com notification: Changes on
	draft-ietf-geopriv-deref-protocol
X-Test-IDTracker: yes
X-IETF-IDTracker: 3.65-dev
X-Tracker-Bcc: rjsparks@nostrum.com
Message-ID: <20120118222836.26888.87969.idtracker@localhost>
Date: Wed, 18 Jan 2012 14:28:36 -0800


Hello,

This is a notification from Personal ID list of rjsparks@nostrum.com.

Document: draft-ietf-geopriv-deref-protocol

Change:
State changed to <b>RFC Ed Queue</b> from Approved-announcement sent

Best regards,

        The datatracker login manager service
        (for the IETF Secretariat)



--------------010709010904020904030501--

From esanchez@yaco.es  Thu Jan 19 13:37:47 2012
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11ED221F85E6 for <yaco-community-tool@ietfa.amsl.com>; Thu, 19 Jan 2012 13:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level: 
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o9I1WEijGHrC for <yaco-community-tool@ietfa.amsl.com>; Thu, 19 Jan 2012 13:37:41 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7413B21F859E for <yaco-community-tool@ietf.org>; Thu, 19 Jan 2012 13:37:35 -0800 (PST)
Received: by werp11 with SMTP id p11so400163wer.31 for <yaco-community-tool@ietf.org>; Thu, 19 Jan 2012 13:37:34 -0800 (PST)
Received: by 10.216.132.195 with SMTP id o45mr2636659wei.17.1327009054088; Thu, 19 Jan 2012 13:37:34 -0800 (PST)
Received: from [192.168.0.193] ([77.227.215.107]) by mx.google.com with ESMTPS id l2sm2036785wie.11.2012.01.19.13.37.32 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 13:37:32 -0800 (PST)
Message-ID: <4F188D1A.1080602@yaco.es>
Date: Thu, 19 Jan 2012 22:37:30 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: yaco-community-tool@ietf.org
References: <4EE28025.5030307@nostrum.com> <4F174988.3010902@nostrum.com>
In-Reply-To: <4F174988.3010902@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-community-tool] Observations from my second attempt at using the community tool
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>,  <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 21:37:47 -0000

    Hi Robert,

    See comments inline.

El 18/01/12 23:36, Robert Sparks escribió:
...
>> Should the search results be accurate? I set up a rule to search for
>> all documents
>> containing the text "location conveyance". It only found seven. There
>> are many, many
>> more.
> So it looks like rules of the form "All I-Ds that contain a particular
> text string" are
> case-sensitive. I added three rules
> "location conveyance" found 4 docs
> "Location conveyance" found 1 doc
> "Location Conveyance" found 8 docs
>
> Now to sanity check that with my copy of the draft repository:
> unexplicable:draft rjsparks$ grep -irl "location conveyance" . | perl
> -pe 's/-[0-9]{2}.(txt|xml)//' | sort -u | wc
> 77 77 2884
>
> So there are many drafts the search isn't finding.
>
> Now the Documents tab shows only 8 drafts. I hope that's because the 4
> and 1 above are subsets
> of the 8. All the docs returned are draft-ietf-geopriv- or

    Yes, I have the same results, and the 4 and 1 are subsets of the 8.

> draft-ietf-ecrit-. There are a slew of
> individual submissions that don't get matched.
>
> Some important ones missing include:
> draft-ietf-geopriv-policy-uri
> draft-ietf-sipcore-location-conveyance
>
> Now I can see the second not being in the set if you are filtering out
> drafts that have become RFCs
> (its not obvious that you should do that though), but the first is still
> in IESG evaluation - very much
> in the middle of process, so why isn't it being found?

    I've done the same grep in the draft repository of the beta server 
and I've only got 10 results. I suppose that the difference is because 
the beta server doesn't have all the drafts or because you have more 
than one version of each draft.

    About the RFCs being filtered out, this was a bug and it is fixed now.

    About the draft 'draft-ietf-geopriv-policy-uri': The system doesn't 
found this draft because there is an inconsistency between the draft 
repository and the database. In the database the draft is in revision 03 
but in the draft repository the file is the one for 04 revision. The 
reason is that the database and the repository were updated in different 
dates.

    Of course this will not happen in a production server.

>> Should sorting work? - I tried the various sort options in the display
>> customization section.
>> Alphabetical by title or by filename worked. Publication date didn't.
>> Sorting by change or
>> significant change produced results that didn't make sense.
> Sorting by Publication date still doesn't work, and the sort by change
> of status still doesn't make sense.
> (It might help it make sense if it showed the date of the change of
> status somehow).

    I've run a script that updates the needed dates in the database so 
sorting will work without waiting that future changes in the drafts fill 
this info.

>> I could only subscribe to lists or feeds from the read-only view of
>> the list.
>> It is very unintuitive to look there for those options - why aren't
>> they available to me on my regular view?
> I see you added links to the export tab. I still find the disparity
> between the read only view page and the modifiable page disconcerting.

    The management view is focused to the owner of the list and the read 
only to the other users. So in the read only view you'll find only the 
draft list and the links that an user may require: The ones for the 
mailing subscription and the rss links (they are in the meta of the page 
so your browser should detect them).

>> The view URL itself is coding the username into the URL - why? I
>> _assume_ you have coded policy
>> that doesn't let me look at Adam's list just because I know his login.
>> If that's the case, stopping at
>> community/personal or using something like community/personal/mainlist
>> and figuring out which
>> list to look at by seeing who was logged in seems a lot safer.
> This is fixed.
>>
>> Similarly, the way this currently constructs the "read only" view
>> necessarily makes all of the lists
>> public. The intent of 6293 was that these be private by default and
>> only exposed if the person
>> wants to expose them. As it is now, I know I can see Adam's list by
>> looking at
>> http://beta.community.yaco.es/community/personal/adam%40nostrum.com/view/
> Fixed.
>>
>> I logged in as stream_user. It does not let me change any state on any
>> documents, so I couldn't
>> test the notification features.
> I confirmed that this works, at least to the level of making updates in
> the RSS feed.
> I supposedly successfully subscribed to the email list for any change,
> but I haven't seen any
> email after making changes to one of the matched documents as
> stream_user. There's a chance
> that it's caught in grey-listing, but that would be odd given that I
> completed the subscription
> email-confirmation dance just a few minutes before. Can you see any
> evidence that it _tried_
> to send me email related to the change in a state of one of the
> documents on the list? If so,
> please send me the message-id?

    I resent you the email this morning.

    Best,
