Re: [yaco-community-tool] Beta testing of upcoming draft tracking service

Henrik Levkowetz <henrik@levkowetz.com> Mon, 05 December 2011 12:15 UTC

Return-Path: <henrik@levkowetz.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 C337521F8B5E; Mon, 5 Dec 2011 04:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V+zD37Q0O+wX; Mon, 5 Dec 2011 04:15:54 -0800 (PST)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by ietfa.amsl.com (Postfix) with ESMTP id 971DA21F8B03; Mon, 5 Dec 2011 04:15:54 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:50842 helo=brunello.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1RXXS2-000799-3G; Mon, 05 Dec 2011 13:15:34 +0100
Message-ID: <4EDCB5CA.7060803@levkowetz.com>
Date: Mon, 05 Dec 2011 13:15:06 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Jim Schaad <ietf@augustcellars.com>
References: <4ED8D28C.3070505@levkowetz.com> <4ED917E0.30403@levkowetz.com> <00b301ccb2d1$1fba16e0$5f2e44a0$@augustcellars.com>
In-Reply-To: <00b301ccb2d1$1fba16e0$5f2e44a0$@augustcellars.com>
X-Enigmail-Version: 1.3.3
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: ietf@augustcellars.com, wgchairs@ietf.org, yaco-community-tool@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: 'WG Chairs' <wgchairs@ietf.org>, yaco-community-tool@ietf.org
Subject: Re: [yaco-community-tool] Beta testing of upcoming draft tracking service
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, 05 Dec 2011 12:15:55 -0000

Hi Jim,

On 2011-12-04 23:07 Jim Schaad said:
> Can we do draft submissions followed by working group acceptance of a
> document?

You should be able to, although I've not tested doing draft submissions
against the beta server.  If anything, there might be a problem with
missing draft repository directories, but we can fix that if there is
a problem.


Best regards,

	Henrik


>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of Henrik Levkowetz
>> Sent: Friday, December 02, 2011 10:25 AM
>> To: WG Chairs
>> Subject: Re: Beta testing of upcoming draft tracking service
>>
>> Hi again,
>>
>> One more point related to this:  When you create a test login, please use
> a
>> throwaway password, not something you'd not care for people seeing.
>>
>> The reason is that although no passwords are stored in database or apache
>> login digest file, passwords will be visible if something goes wrong when
> you
>> set up your account and a crash log including stack dump is created.
>>
>>
>> Best regards,
>>
>> 	Henrik
>>
>> On 2011-12-02 14:28 Henrik Levkowetz said the following:
>>> Hi,
>>>
>>> Introduction
>>> ------------
>>>
>>> We now have an implementation of RFC 6293
>>> (http://tools.ietf.org/html/rfc6293)
>>> "Requirements for Internet-Draft Tracking by the IETF Community in the
>>> Datatracker" ready for some testing.
>>>
>>> It would be much appreciated if you would assist in testing this.
>>>
>>> If you go to http://beta.community.yaco.es/ you'll see a pretty
>>> ordinary datatracker first page; in order to test the new
>>> functionality you'll need to get and use a test login.
>>>
>>> Account Setup
>>> -------------
>>>
>>> You acquire a test login by clicking on the 'New Account' link at the
>>> top of the lefthand menubar, and then follow the 'Request an account'
> link.
>>> Fill in the email address you want to use, and you'll be sent an email
>>> with further instructions.  Once you've completed those, you'll have
>>> an account on the beta server which you can use to test the draft
> tracking
>> service.
>>>
>>> Setting up documents to track
>>> -----------------------------
>>>
>>> Use your account to log in.  You will now see a new link in the
>>> lefthand menubar, under "Community ID lists": "Personal list".  Click
>>> this, and you'll be taken to a page with 5 tabs, where you can set up
>>> the rules for drafts you want to follow, and see the generated status
>>> page which lists all the drafts you've chosen.
>>>
>>> So far, so good -- it would be appreciated if you would test this out,
>>> and send feedback to the yaco-community-tool@ietf.org mailing list
>>> about what you find.
>>>
>>> Triggering notifications
>>> ------------------------
>>>
>>> There is one part of the functionality which is complete, but will
>>> require manual work by the testers in order to manifest:  Normally,
>>> email notifications about changes to the documents you have set up for
>>> tracking will be sent out as soon as an AD, Chair, or someone from the
>>> secretariat goes in and changes status for a document.  As this isn't
>>> happening on the beta server, it is required that you as a tester go
>>> in and make changes in order to see change notifications coming.
>>>
>>> The developer has set up a particular user which has been given
>>> authority to change the state of any draft in any stream:
>>> 'stream_user' with password 'stream_user'.  Please use this to go in
>>> and change the state of documents you have set up tracking for, in order
> to
>> exercise the notification feature.
>>>
>>> We are aware that this is less than ideal, but we don't currently have
>>> any way to trigger changes in the beta server based on actions taken
>>> in the production server.
>>>
>>> Questions, feedback
>>> -------------------
>>>
>>> As mentioned earlier, please send questions and feedback to the
>>> mailing list set up for the project: yaco-community-tool@ietf.org.
>>>
>>>
>>> Best regards,
>>>
>>> 	Henrik
>>>
> 
> 
>