Sync meeting T5.1 support portal 2023 05 25 - multixscale/meetings GitHub Wiki

Sync meeting 2023-05-25

  • Notes

    • (Thomas) Could raise selection of project for support portal in EESSI update meeting on 1 June 2023

  • Planning meetings

    • 2-step evaluation
      • filter down to 3 alternatives => Fri 2 June 13:30 CEST
      • Detailed comparison with testcases: end june 2023
    • final selection: end of June/early July/Aug?
      • => Thu 29 June 13:30 CEST

  • 2-step evaluation?

    • filter down to ~3 alternatives for detailed comparison
    • Testing 3 alteratives with some example support

  • Categories of aspects for comparison

    • Partner experience
    • Limits
    • cost/resources (open source, cloud instance, maintenance, ...)
      • We could start with e.g. free Jira, and move later if we grow to much. But this incurs a lot of extra work. Better to try and pick one that will last us the whole time.
      • How many ppl will be involved in support? (for SURF: might be 1, might be 4, depending on how happy people are to take the role :))
      • By Friday: have the costs & limits field filled out, so that we can have a discussion on those.
    • major (required) vs minor (nice to have)
      • private issue to major
    • other features
      • Workflow of managing and assigning tickets => This also means having a good dashboard that shows 'what is waiting for me' (as support person), and what is waiting on a user
    • Requirements for customers

  • Partner experience

  • Cost and resources

    • Looking at the near and far future?
    • Are we hosting ourselves?

  • Distinction between required functionalities and the once that are nice to have

  • Clarify account requirement

    • No one filled in that they thought account creation was an issue, but Kenneth mentioned it

  • Comments on spreadsheet with comparison and the questionnaire

    • Adding the results of the form to the one drive?
    • We could add links to where we found certain information (e.g. that tool XYZ supports feature ABC), so we don't have to look for it later when we want to use that feature when implementing the portal
    • Maybe the fields (particularly 'other aspects' fields) that are the same accross all solutions can be greyed out, so that its clear we don't need to focus on those

  • Tasks

    • Lara Finish fields under Cost/Resources and Limits: Jira, GitHub, Bugzilla and Redmine
    • Killian Finish fields under Cost/Resources and Limits: GitLab, RT, OTCR