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

Robert Sparks <> Fri, 02 December 2011 16:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6600421F8BA4 for <>; Fri, 2 Dec 2011 08:43:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id r2uarRtteLEF for <>; Fri, 2 Dec 2011 08:43:47 -0800 (PST)
Received: from ( [IPv6:2001:470:1f03:267::2]) by (Postfix) with ESMTP id 3052A21F8B95 for <>; Fri, 2 Dec 2011 08:43:46 -0800 (PST)
Received: from ( []) (authenticated bits=0) by (8.14.3/8.14.3) with ESMTP id pB2Ghb1i091259 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Dec 2011 10:43:43 -0600 (CST) (envelope-from
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <>
In-Reply-To: <>
Date: Fri, 2 Dec 2011 10:43:36 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Henrik Levkowetz <>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass ( is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 12 Dec 2011 08:13:46 -0800
Cc: Paul Hoffman <>,
Subject: Re: [yaco-community-tool] Beta testing of upcoming draft tracking service
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 02 Dec 2011 16:43:48 -0000

I attempted to create an account - I got a django/python IntegrityError upon setting the initial password.
(Duplicate Key Entry).


On Dec 2, 2011, at 7:28 AM, Henrik Levkowetz wrote:

> Hi,
> Introduction
> ------------
> We now have an implementation of RFC 6293 (
> "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 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 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:
> Best regards,
> 	Henrik