<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] Action Item related to Whois Service Requirements
- To: "GNSO Council" <council@xxxxxxxxxxxxxx>
- Subject: RE: [council] Action Item related to Whois Service Requirements
- From: "Tim Ruiz" <tim@xxxxxxxxxxx>
- Date: Wed, 08 Apr 2009 06:43:20 -0700
- List-id: council@xxxxxxxxxxxxxx
- Reply-to: "Tim Ruiz" <tim@xxxxxxxxxxx>
- Sender: owner-council@xxxxxxxxxxxxxx
- User-agent: Web-Based Email 5.0.8
To work well, it would help if we have prioritized our work at the
Council level to begin with.
Tim
-------- Original Message --------
Subject: RE: [council] Action Item related to Whois Service
Requirements
From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
Date: Wed, April 08, 2009 7:57 am
To: "Philip Sheppard" <philip.sheppard@xxxxxx>, "GNSO Council"
<council@xxxxxxxxxxxxxx>
Philip,
Your suggested approach would seem to accomplish what I intended.
Chuck
> -----Original Message-----
> From: owner-council@xxxxxxxxxxxxxx
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Philip Sheppard
> Sent: Wednesday, April 08, 2009 3:24 AM
> To: 'GNSO Council'
> Subject: RE: [council] Action Item related to Whois Service
> Requirements
>
>
> Chuck wrote:
> "Maybe we should start by asking Staff whether they have the
> bandwidth to take this on at this time and if not request an
> estimate as to when they think they would be able to do so".
>
> ---------------------
> Chuck, this seems a little backwards and implies every
> current issue occupying staff time has greater priority than
> future ideas such as this.
> A better way to proceed is for Council to make as many
> requests of staff as we deem necessary.
> Staff management then respond and indicate resource
> constraints. They list the activities they are doing and
> request Council to prioritise the list.
> We prioritise.
> Staff act.
>
> Philip
>
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|