ICANN ICANN Email List Archives

[gnso-workplan-subteam-policyimpl]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-workplan-subteam-policyimpl] RE: MetRep Workplan

  • To: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
  • Subject: Re: [gnso-workplan-subteam-policyimpl] RE: MetRep Workplan
  • From: Cheryl Langdon-Orr <langdonorr@xxxxxxxxx>
  • Date: Fri, 18 Oct 2013 00:08:18 +1100

yup that is the tool BUT it is a specific output/template that  I was
refering to... copy of the sample I refered to has been sent to Marika for
reference...
On Oct 17, 2013 11:40 PM, "Gomes, Chuck" <cgomes@xxxxxxxxxxxx> wrote:

>  AtTask is also being used for the ICANN budget with promises that we
> will be provided access to more detail in the future.****
>
> ** **
>
> Chuck****
>
> ** **
>
> *From:* owner-gnso-workplan-subteam-policyimpl@xxxxxxxxx [mailto:
> owner-gnso-workplan-subteam-policyimpl@xxxxxxxxx] *On Behalf Of *Marika
> Konings
> *Sent:* Thursday, October 17, 2013 7:18 AM
> *To:* gnso-workplan-subteam-policyimpl@xxxxxxxxx
> *Subject:* [gnso-workplan-subteam-policyimpl] FW: MetRep Workplan****
>
> ** **
>
> Hi Cheryl,****
>
> ** **
>
> Is this the document/tool you were referring to (see attached)? If so,
> that is what we currently use for internal purposes to manage projects. It
> is called AtTask. Some of the output can be viewed on myIcann (see for
> example https://myicann.org/plan/project/51cb3f9b0015ee29eecdae77e758390a),
> but the task level is for internal use only at the moment. I could build
> the project plan like Berry has, but the problem is that only staff would
> be able to update / change it and it wouldn't be publicly visible for the
> WG, so I'm not sure how helpful that would be. ****
>
> ** **
>
> Best regards,****
>
> ** **
>
> Marika****
>
>  ****
>
>  ****
>


<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy