, SWITCH Offices, Zurich, Switzerland.
Start 09:30.
Location - Ann/Thomas's office, 3rd floor.
Lunch c. 12:00, leaving the office for fresh air.
eduGAIN map will be SVG not based on Google Map.
Higino to report to Tomasz on all integration work.
Tomasz to be the gatekeeper on integration of new eduGAIN technical tools.
Access to the DB to be provided to these tools in a controlled way via access key.
Higino to answer to Tomasz and deliver additional versions of the map
Create a site for edugain.org that is the service portal for eduGAIN -
Owner Brook:
Platform location - Amsterdam
Backend remains at Torun
Principle of working - rapid prototyping between design and technical implementation.
Mimic look, feel and navigation of GÉANT site but with specialist focussed technical eduGAIN info.
Common info on initial site - map, participating federations, entity list, wiki, policy,profiles & constitution
Technical implementation - Tomasz, higino to report to Tomasz in this context.
Design - Brook
Content - Migrate & enhance
If a tool is in production as an official edugain supported tool in the portal, it migrates to the eduGAIN OT, Tomasz.
Tomasz does not have to wait for design plan to migrate these.
Migration - make code available.
Ops - dev teams run test versions, push to git when ready, then Tomasz pull.
Monitoring & BCP list...see Nicole's notes.
Separate project
Do we need to migrate to GÉANT wiki? Not a priority.
Do we need to restructure/sort info on it better? YES
Owner: Lukas, participant Thomas Baereke
Look and feel - lower priority.
Information structure
Main jump page content
Quick links for federations
Quick links for Service Providers
Plus segmented content
Technical information for federations - migrate as much as possible to edugain.org.
Tools - link trials in wiki under correct sections, then post pilot, freeze and migrate.
How to use side menu more?
FaaS - not to be integrated into edugain.org service portal
Yes to be integrated into PR material on eduGAIN
GN4-2 idea
SA2 - Tomasz & Nicole
JRA3 - Brook & Maja
Dev to be involved in hotfix but Ops own the veto to change
Workflows matching tools need to be developed.
Keep jra and sa linked on service lists.
Roadmap - Operational Practice Statement for SAML (eduGAIN) to be produced.
Brook to investigate if Ian Y available for subcontract.
Representatives must be able to represent the technical profiles.
Votes on profiles restricted to people who do the service.
New profiles - full steering endorses first version of new profile. Adopters get to refine it. ie. new profile is a de facto consitutional change.
Proposal - If Interfederaton e.g. Moonshoot, SAML, OIDC, in scope for eduGAIN technical.
If NOT inter federation, e.g. VO Platform, inform eduGAIN, separate governance aligned with basic principles of eduGAIN constitution - eg. VO Plaform.
Affects branding
Brook Schofield Put MRPS update to SG after the TownHall