6:24 a.m.
Let’s change the meet-up time at the GÈANT booth to 12:30.
I originally said noon not realising it clashed with the plenary.
Please pass on the message to any one you see.
See you later if you can.
Dan.
Sent from my iPhone
On 10 Jun 2022, at 10:51 am, Dan Sellars via GREN Mapping WG
<gren-mapping-wg(a)lists.nordu.net> wrote:
Hello all,
I hope that you are well and looking forward to TNC!
We haven’t got a formal meeting planned for the WG, everyone seems so busy and it is hard
to organise a time. It would be a shame not to get as many people as possible together
though.
To that end here are our options:
* Ryan will be hosting a demo/office hours period at the GÉANT booth on Wednesday at
noon, this would be an excellent time to meet up if you can swing it in your schedules.
* Ryan and I will be at the GNA-G meeting on Monday morning.
* One other option that was suggested to me, if the conference dinner on Wednesday
evening is not fixed seating we could socialise and try and sit together then. I
appreciate that many of you will have other plans already.
Don’t forget that Ryan is doing a lightening talk in the Auditorium on Wednesday afternoon
at 15:00 (https://tnc22.geant.org/lightning-talks/#c192) so it would be great to get as
many of you as possible there. Ryan and I will be at the GÉANT booth following that if
anyone wants to chat after his talk.
Let us know what might work for you or if you have another idea that might work. This will
be my first TNC so I am not sure what other opportunities might present themselves.
I look forward to catching up or meeting for the first time as many of you as I can.
Best Regards,
Dan.
From: "Schopf, Jennifer M" <jmschopf(a)indiana.edu>
Date: Wednesday, June 1, 2022 at 7:46 AM
To: Ryan Davies <Ryan.Davies(a)canarie.ca>ca>,
"Gren-mapping-wg(a)lists.nordu.net" <Gren-mapping-wg(a)lists.nordu.net>et>, Tom
Vitez <Tom.Vitez(a)canarie.ca>ca>, "ajay(a)sanren.ac.za"
<ajay(a)sanren.ac.za>za>, "john(a)sanren.ac.za" <john(a)sanren.ac.za>za>,
"ian.galpin(a)geant.org" <ian.galpin(a)geant.org>rg>, Dan Doyle
<daldoyle(a)globalnoc.iu.edu>
Subject: [GREN-Mapping-WG] Re: Actions Requested: GREN Map Initial Release Task List
________________________________
External This email originated from outside the organization. Use caution when following
links as they could open malicious web sites.
________________________________
Hello-
I’ve been out of the office and just catching up now. Did this group find a time to
meet at TNC?
-j
------------------------------------------------
Dr. Jennifer M. Schopf
Director, International Networks
Director, Engagement and Performance Operations Center
Indiana University
From: Ryan Davies <Ryan.Davies(a)canarie.ca>
Date: Tuesday, January 25, 2022 at 1:19 AM
To: Gren-mapping-wg(a)lists.nordu.net <Gren-mapping-wg(a)lists.nordu.net>et>, Tom Vitez
<Tom.Vitez(a)canarie.ca>ca>, ajay(a)sanren.ac.za <ajay(a)sanren.ac.za>za>,
john(a)sanren.ac.za <john(a)sanren.ac.za>za>, ian.galpin(a)geant.org
<ian.galpin(a)geant.org>rg>, Dan Doyle <daldoyle(a)globalnoc.iu.edu>du>, Schopf,
Jennifer M <jmschopf(a)indiana.edu>
Subject: Actions Requested: GREN Map Initial Release Task List
Hello GREN Mappers,
As you may know, we are preparing to release the first public version of the GREN Map
system software this year. At our last meeting, we discussed a draft list of tasks
remaining before we are ready to do so. The list can be found on the Working Group’s
wiki:
https://wiki.geant.org/display/GlobalMap/Version+1.0+Release+Task+List<h…
We are looking for members to participate in two ways:
1. Review the task list. Please let me know if you feel there are any items missing to
get ready for “version one point zero” release, or if you have any other feedback about
the list. (Note that of course we intend for development to continue after v1.0 is
released. There is a long wish list of features still in the backlog, and surely more
will be proposed once this is out in the wild. For the moment, we want to identify what
is required as a bare minimum for the system to function usefully and securely enough to
start assembling real data and publishing some basic maps.)
2. Sign up to oversee tasks. We are looking specifically for names attached to the
“Managed By” field for each task, not the “Assigned To” fields for the subtasks. What
this means is that accepting these responsibilities would not necessarily imply doing any
of the actual work (although we would welcome that too!), but rather to plan the
implementation, recruit people to do the work, supervise the task, ensure it gets done,
and briefly report on progress when appropriate. The task list page may look long, but
don’t be fooled, the tasks are mostly each quite small; many likely involve only a handful
of hours!
Please reach out to me if you have any feedback or questions, or if you’d like to go ahead
and sign up to manage a task! Our imminent meeting is also another great time to bring
anything up.
Ideally, we request your responses by February 1.
Cheers,
Ryan