Date

at 11am CET.

Either face-to-face in the Amsterdam office or via VC. 

 task-force-SIG on Lifesize.

Connect over video
   Join with your web browser (Chrome, IE11): https://call.lifesizecloud.com/call/2573142
   Other ways to call: https://call.lifesizecloud.com/otherways/2573142

Connecting from a Lifesize conference room system? Just dial 2573142 with the keypad.

Attendees

Apologies:

Goals

  • To decide on the agenda of the 9th GCC meeting.
  • To review current activities.
  • To assess current processes for assigning secretaries to groups.
  • To review communication planning for Task Fores and SIGs. 

Discussion items

TimeItemWhoAction
General Round Table Updates on all groups

SIG-ISM: going well, on target.  Meetings are well attended.  2 working groups set up last year and these are moving forward well.  3rd WG (threat awareness). 

SIG-TNE: having some issues with defining the scope of the group. Haven't met the KPIs.  There are people on the mailing list but there is no discussion.  SC calls are productive but not enough follow-up.  Over dependent on the secretary.  Not enabling participation of european SIGs at meetings in APAN and I2GS.

SIG-NGN: needs to be kicked-started. Problem that discussions are happening on the "NREN" slack - this hasn't been well advertised and is a bit of a clique.

SIG-CISS: going well - April meeting in the office and follow up at TNC.  Coordinating well with JRA4.

SIG-Multimedia: stalling.  Now understand that it might shut down.  Not much of a mandate left.  No meetings planned.  

SIG-Marcomms: just had a meeting.  Well attended, good feedback.  15th anniversary of the group in September!  Joined up cybersecurity communications plan?

SIG-MSP: good meetings for the last couple.  Making sure we are not too focused on non-GÉANT stuff.    Getting a good focus for each meeting, hit the KPIs. 

TF-DPR:

SIG-NOC:

TF-RED:

TF-CSIRT:

SIG-Greenhouse:

SIG-PMV: very specific.

Sigita


Sigita


Brook


Peter

Peter


Laura

Annabel


  • ACTION: All make sure that your KPIs are up to date. 
  • ACTION: present the red tagged groups to the GCC.
Role of TF and SIG secretary / changing nature of requests for TFs and SIGs

Can we have a slightly different function?

Define lack of interest.  Expectation management?

Make this a discussion between GCC and GPPC: need to take this out

Role of the secretary: this needs to be funded at a higher level.

Where we are not the defacto place to go, the TF and SIG tends not to be successful.

 
  • ACTION:  look at secretary support function within GN4-3 and resourcing.  Clear internal message on effort required. 
Reviewing or Exiting a GCP Activity

Brook: Would like to ask how "standarisation" group engagemnet is handled? Currently co-ordinated within the GÉANT project by Richard Hughes-Jones but maybe there is a need to make this more publicly visible? (willing to take on an action to look at X "standardisation groups" and the past X meetings of "standardisation groups" (where their attendance is public to determine whether we turn up).


  • ACTION: Summary of Standardisation Group participation by the Community (for Brook).
Agenda for 9th GCC meeting: 10th April 2018

  • ACTION: add a Comms update to the agenda. 
  • ACTION: add standardisation bodies discussion. 

Communications and SIGs / TFs

 - Slack

 - Trello

  - Blogging

NREN.slack.com ← allows registration with an @geant.org email address.

GEANTcommunity.slack.com

Creating a micro-site for CLAW to help promote better.

All the TFs and SIG pages have been updated.

How do people outside the group know what is going on? Overview on all the groups aimed at senior management? 

Problem with people not internally communicating when they go back to their own NRENs


  • ACTION: Profiles in CONNECT magazine on the active chairs.
  • ACTION: Add a tag for the Community Programme to the blog platform.
  • ACTION: All to promote PeaR at TFs and SIGs.
Metadata tagging for SIGs and TFsBigger problem - need to be able to find presentations and output.
  • ACTION: set up a separate meeting on a repository for outputs.