[datatracker-rqmts] Expected user interactions in draft-ietf-genarea-datatracker-community

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 26 October 2010 21:40 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: datatracker-rqmts@core3.amsl.com
Delivered-To: datatracker-rqmts@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 2F5CC3A6951 for <datatracker-rqmts@core3.amsl.com>; Tue, 26 Oct 2010 14:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.429
X-Spam-Status: No, score=-101.429 tagged_above=-999 required=5 tests=[AWL=0.617, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id JDneo6mUo5Zz for <datatracker-rqmts@core3.amsl.com>; Tue, 26 Oct 2010 14:40:32 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM []) by core3.amsl.com (Postfix) with ESMTP id 0E28F3A682C for <datatracker-rqmts@ietf.org>; Tue, 26 Oct 2010 14:40:32 -0700 (PDT)
Received: from [] (75-101-30-90.dsl.dynamic.sonic.net []) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o9QLgIV9002112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <datatracker-rqmts@ietf.org>; Tue, 26 Oct 2010 14:42:19 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240800c8ecfbb84168@[]>
Date: Tue, 26 Oct 2010 14:42:17 -0700
To: datatracker-rqmts@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: [datatracker-rqmts] Expected user interactions in draft-ietf-genarea-datatracker-community
X-BeenThere: datatracker-rqmts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <datatracker-rqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/datatracker-rqmts>
List-Post: <mailto:datatracker-rqmts@ietf.org>
List-Help: <mailto:datatracker-rqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2010 21:40:33 -0000

First off, greetings. Some of you have contacted me off-list, and I'm hoping all of those people are now on-list so we can get the discussion happening here.

One thing that was pointed out to me was that the initial draft didn't include a description of what the expected interaction that a user of the extended Datatracker would be. I propose the following, but am completely open to suggestions for other models of interaction.


When a user wants to follow a group of drafts, he or she goes to the Datatracker and creates a new list. The requirements for lists are given in Section 2.1. After a list is created, the user has three ways that he or she might see when drafts in the list are updated:

- By going to the Datatracker page for the list (see Section 2.3)

- By subscribing to the Atom feed for the list (see Section 2.2.2) in a feed reader that automatically fetches updates

- By subscribing to the mail stream for the list (see Section 2.2.3) and reading the stream in their mail reader


Should I be saying more here, and if so, what?

--Paul Hoffman, Director
--VPN Consortium