Versions Compared

Old Version 4

changes.mady.by.user Peter Szegedi

Saved on

compared with

New Version 5

changes.mady.by.user Peter Szegedi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Workflow and Architecture

Notes

Note
SUMMARY OF ACTIONS

Summary of Actions

  • ACTION 1 on Ilias (WP3) to include the GÉANT TURN Service pilot in the Up2U architecture design as a potential solution.

  • ACTION 2 on Allan (WP4) to investigate what WebRTC-based tool can easily be integrated with the current Moodle platform to provide instant real-time communication option for the users. Think about the example how Trello integrates Google Hangout to each board. We need something similar to each class in Moodle.

  • ACTION 3 on Marco (WP5) to coordinate the surveying exercise not only in Italy but also in the other pilot countries too. Talk to the community managers in the pilot countries, get the surveys translated to local language (if need) and sent them out ASAP!

  • ACTION 4 on Nelson (WP2) and Allan (WP4) to give admin access to Nelson and customize the theme for Up2U.

  • ACTION 5 on Peter (GÉANT), Eli (IUCC), Thodoros (NTUA) to set up a meeting with Moodle.

  • ACTION 6 on Allan (WP4) to build the developers team! There are potential developers at OU, PSNC, IUCC, GRNET, TELTEK, ownCloud, etc.. We should gather them and mobilize!

  • ACTION 7 on Ilias (WP3) to restructure, maintain and make available the Architecture Straw-man document (preferably via the Wiki).

  • ACTION 8 on Allan (WP4) at.al to progress with the federated login solution to Moodle and invite people for testing.

  • ACTION 9 on Vicente (WP8) to design models and define requirements who third-party commercial (full-stack) applications can be integrated to the Up2U platform using it as a "delivery vehicle" towards the users.

  • ACTION 10 on Mary (WP4) to investigate the SiLeCon tool integration details with Moodle.

Note

Public

ACTIONS

list of actions from the closed Up2U Board Meeting


1) Up2U objective and key results (OKRs) must be defined, all work packages should have their own OKRs linked to the Up2U OKRs and also cascaded down to the task level. Progress should be measured.

2) Board should meet face-to-face at least once a year. Board should attend the MT meetings at least quarterly to get some first-hand insight into the work of the MT.

3) The Board encourages the MT and the WP leaders to achieve more cross-pollination between WPs and better communicate downstream. Not only Trello but private Wiki spaces are needed per WP to collect consolidated information.

4) The Board encourages all the partners to comply with the quarterly financial reporting practice.

5) Peter to start the process of reviewing and rearranging budget for partners. Partners' contributions to WPs as well as travel budgets must be fixed.

6) WP5 leaders to organize a meeting with the Board members and explain/clarify the purpose and structure of the SMC.

DETAILED MEETING NOTES

Day 1 - Joint session


1) TURN for Up2U

Misi (NIIF/KIFU) talked about the GÉANT TURN service pilot that is a distributed and federated STUN/TURN server infrastructure for easing firewall and NAT traversal for real-time traffic (audio, video, data).

The GÉANT TURN Service can be configured as externalized functionality to any commercial and community-built WebRTC and Voice/Video Conferencing solution. It's fully maintained by R&E and resides in the R&E networks. We can guarantee SLA and monitoring on the service that is a value-add.

Assuming that Up2U will have an embedded WebRTC-based real time communication component, the GÉANT TURN Service would be an ideal way to solve firewall and NAT traversal issues in various network conditions.

- ACTION 1 on Ilias (WP3) to include the GÉANT TURN Service pilot in the Up2U architecture design as a potential solution.

...