Staff meeting minutes

CodeRefinery staff meeting

:::info

• Date: 2021-10-25
• Chair: NT
• Minutes taker: all who could
• Present : RB, RD, JH, DI, JL, BL, SN, NT
• When: 12:00 CEST / 13:00 EEST
• Where: https://uit.zoom.us/j/65070953679
• This document: https://hackmd.io/@coderefinery/staff-meeting :::

Next meeting

• Staff meeting in Phase 2 is over. JH will inform the result of Doodle poll about stand-up meetings for the following phase.

About this document

• Visibility:
  • We write so that it can become public.
  • Everybody who has the link during the meeting can edit. Otherwise logged-on users can edit.
  • The minutes need to be reviewed and approved by the end of the meeting.
• All paid staff is invited to this meeting and expected to attend (unless vacation, sick leave, scheduling conflict).
• We use one document (this document) for all meetings instead of creating a new one.
• Newest items on top in each category.
• Most urgent tasks on top.
• 2-3 assigned chairs instead of entire-team-rotation.
• Chair assigns the task to document conclusions for each item before moving on to next.
• Syncing with GitHub:
  • One commit per meeting with "20YY-MM-DD" as version/commit message.
  • 3 dots top right -> "Versions and GitHub Sync"
  • This document is linked to this file.
  • Meeting chair commits after a meeting.

Tasks (in progress or unassigned)

• [ME] Streaming VPS Solution for live stream selection, live production (OBS switchboard, API), compressing and uploading to YouTube
  • there were some discussions with RD and RB about this. We continue this thursday 16.september at 14 CEST, if you want to join let us know
  • 2021-10-11: OBS is not compatible with Managed server infrastructure on AU / UCloud. CHCAA will supply and maintain a dedicated server for this purpose as part of our contributions in CodeRefinery's phase 3.
  • motivation: decentralize video production
• Make CR lessons citable
  • priority 1: Write down JH's knowledge
  • priority 2: Making the lessons citable in practice (having a separate meeting to decide who to be cited as what)

• The followings are dropped for now (by the end of Oct. See Discussion item 2021-22 )

•   - [ ] [JH] GitHub actions generation of pdfs from the lessons 
          - Tried out pdf generation offline. Why the 'Could not import extension sphinx_lesson (exception: No module named 'sphinx_lesson')' error when typing `make html`? Missing something in the sphinx install on my laptop?
          - Clone the present GitHub action `.github/workflows/sphinx.yml` to an action that implement a sphinx `make latexpdf` step?
          -> RD, RB and JH will take a look.
    - [ ] [RB] Draft email/issue to send to all contributors 
      - or on github issue to have it in one place
      - email persons that do not respond on github issues  
    - [ ] Everyone who would like to include his/her ORCID on the Zenodo releases, please register or update personal ORCID.
      - The ORCID will go into the CITATION.cff and/or .zenodo.json for each and every lesson for those author/contributors who would like to have ORCID stated.
      - Seems there is on GitHub no natural place in the user profile / account settings where one can specify ORCID. One can use an ORCID or a GitHub account to log in on Zenodo.
  

• [DI, ME] Workshop, 2021 May - retrospective, document prepared and link shared
  • [DI] transform the lessons learned document into a blog -> send a PR
• [RB (for inititiation)] Draft "lessons learned" document from project
  • produce a lesson's document learned from the project
  • after a draft is produced other members should contribute
  • all comments/ bullet points welcome: https://hackmd.io/XUbSv2NPT6OvTx8FLp1_oQ
• [RB] Celebration event -> See discussion item 2021-20 as well
  • Schedule a 1.5 hour lunch event in November -> RB will send a doodle poll
  • Collect addresses and send gifts
  • Prepare video
  • Postprocess feedback
  • [NT] Prepare slideshow from feedback
  • Encourage others to submit a video
• [NT] Making a draft for the newsletter before unsubscribing everyone -> NT needs help here as she wonders now what is the most appropriate to write including unsubscribe/newly subscribe to newsletter. Draft
  • can write that we don't know what the next plat form is and the readers will be notified when more is fixed and known.
  • can someone send it? -> NT sent on Friday 22nd Oct.
• [RB] Collect governance/bylaws notes and present them at a community call

Decisions

Decisions made in the meeting should be listed with the item-number.

• 2021-10-25: A separate meeting will be set for editing/updating the CodeRefinery homepage, especially top-page, "who we are", training hubs, and funding partners (2021-23)
• 2021-10-25: Regarding the task "making lessons citable", at least know-how so far should be available in text, and a separate discussion will be held on concretize who is cited as what (2021-22)
• 2021-10-25: Indico data prior to 2020 is to be deleted (2021-21)
• 2021-10-25: Celebration event for lunch time on one Monday in November. Doodle poll will be sent by RB (2021-20)

Old decisions are listed in the section at the bottom.

Discussion items

Each new discussion item gets a number. It is OK that the same item may be discussed in several meetings. Please add items that you would like that we discuss.

• 2021-24: Meeting about leadership

  • RB and RD would like to discuss with everybody interested how we take leadership from here
  • It will be good to clarify this before the Nov 5 coordination meeting with the consortium
  • Our goal is to collect the many notes about governance and leadership and prepare for Nov 5 meeting
  • Please add yourself here if you would like to get a doodle poll for a meeting:
  • Anyone wants to can join in the meeting on Nov 5 12-13:30 CEST?
    • Should be possible, RB will raise this with the meeting organizer and share connection details

• 2021-23: coderefinery-staff on GitHub and coderefinery-team mailing list

  • RB will disband the GitHub team "coderefinery-staff" but still keep everybody in the organization. You can remove yourself from the organization if you prefer so.
  • RB will welcome more people who want to be co-admins/owners of the GitHub organization. Please let RB know. There is no barrier to this. It will mean some more work for you.
  • Please inform RB if you would perfer to be removed from coderefinery-team mailing list (which has been used for calendar invites to meetings like this one). Possibly you can also remove yourself but RB is happy to do that.
  • What should we do with https://coderefinery.org/about/who-we-are/? The minimum we probably need to do is to remove the distinction staff or not staff.
    • RB send these points also by email
    • Help needed: what should be on the who-we-are page? How should it be presented? Goal is to present the project as community.
    • In doubt we keep people visible for longer rather than removing them too early.
    • Who we are-page and training-hub pages should be edited accordingly and also aligned with the kickstarter info on the page
    • Also update/align funding partner page with consortium of next phase

• 2021-22: Remaining tasks

  • We should not carry tasks to next month or next year, we will get plenty of new ones as time goes on
  • Some tasks may need to be dropped
  • RB: Citable lessons: this is a lot of work for one person (JH) and my recommendation is that we conclude something with 80% done instead of trying to make it 100%. The conclusion does not need to be that one or all lessons are citable but that we have a write-up on how this can be followed up in 2022 by possibly somebody else. If the pdf export is difficult, my (RB) recommendation is to not do it now. I want to remind that there are two aspects: credit and citability, and the other aspect is preservation. The former does not require pdf export. The latter may not be essential.
  • Blog posts that are in progress: please open a draft pull request. It does not have to be finished but it will be easier to take it from there.

• 2021-21: Indico data

  • What should we do with Indico data?
    • Privacy policy is updated with saying: >we need to prolong this date by the further 3 years to keep it possible to issue certificates of participation in recent enough workshops (2020 and 2021) to be fair. Therefore, we will keep information of the participants who are qualified to certificates (either as learner, helper, expert helper, or team lead) in the currently used platform, Indico, managed by NeIC. The currently participating staff who is also committed to be a part of the CodeRefinery SP have access to the information.
  • Can we delete all events prior to 2020?
    • No objection to do so. RB will delete these events.

• 2021-20: Celebration event

  • 1.5 hour lunch event November, completely voluntary
  • RB kindly asks whether somebody would like to help preparing (especially the feedback/slides but also 2 people make better decisions than 1 person)
  • It was suggested to submit videos but this will only work if more people want to actually do this. So do we want to do this?
  • Date suggestions:
    • Monday Nov 15, 12-13:30 CET, 13-14:30 EET
    • Monday Nov 22, 12-13:30 CET, 13-14:30 EET
    • Monday Nov 29, 12-13:30 CET, 13-14:30 EET
  • Any of these times seem to work well but RB will send Doodle poll to all
  • Suggestion was also made to just have the lunch together

• 2021-19: Future of staff meetings and core team stream

  • RB will from now try to avoid using core team since from now on almost everything is for everybody.
  • We have only one staff meeting left after this one (if we find it useful to have it). But there is also the Python training event.
  • Community calls are left but frequency will be lowered to monthly (or even lower).+1
  • Do we need to schedule any other recurrent meetings at this point or do we leave it to others and to the future?
  • Do we need any private stream on the chat?
  • JH: On the return to on-site work, meetings at 12:00 schedule clash with lunch breaks. For November 2021 and onwards, we could consider to have any new standing times for meetings to avoid 11:00 - 13:00 CET (12:00 - 14:00 EET).
  • SR: We need at least a booked time slot for meeting where we can call meetings without a call. For a formal inkind contribution, personally I need this to keep my focus.
  • RD: proposal: "cabal meetings" (public and somewhat frequent, most people not expected to attend but those that are really pushing CR forward use this as a hacktime/discussion time). Then the general meetings, less frequent, focused on the general interest stuff. There will always me more and less focused people, we should adapt to that.
  • About frequency: it should be fun and motivating to come to this meeting and should not create too much overlap with other work
  • RD: there is basically an internal management team now (not just NeIC management). Maybe this best describes what I think: we need multiple levels of internal meetings to reflect this.
  • RD: why separate staff meeting? staff should be seen as part of the community
  • Decision Nov-Dec; monthly meeting (more open and general) + bi-weekly stand-up like meetings. JH will set up a Doodle with suggestions for a standing day and time for these meetings.
    • Followup (2021-10-25): JH will send a reminder and summarize to 2 possible dates/times for bi-weekly meetings.

Freshdesk Support

RB watching support line until we organise next event.

Information

• Python for scientific computing course
• NeIC survey
• NeIC AHM The AHM22 will be held on 24-27 January 2022

Done tasks

• [RB] Secure some follow-up for GitLab service
  • Planning document: https://hackmd.io/@bast/gitlab-future
  • Discussions ongoing
  • There will probably be some solution (ETAIS or Sigma2)
  • Closed since follow-up needs to happen probably outside of this group
• [NT ,RB, AF] De-Google Drive work
  • work started and data move in progress
  • plan is to move public data to GitHub and to remove outdated text
  • RB will ask input regarding decisions on what to keep and where
  • Move data with names (e.g. who we issued certificates) temporarily (at least) to UiTs OneDrive-based folder (would Metacenter G-suite is an alternative ? )
  • Move anonymized feedback to HackMD/Coderefinery
• [DI, ME] Workshop, 2021 May - retrospective, document prepared and link shared (part of sub-tasks)
  • Richard's notes from the coordination HackMD and Zulip in this HackMD
  • DI fixes categories and polishes the document more. Pls. add any comments/suggestions at the top of the document.
• [RB] Preparation of the next community call (date Oct 4) with the agenda Workshops year 2022 planning document
  • As preparation we could get an inventory of possible workshops and events.
  • As preparation read and fill in the document before October 4
  • announce the commmunity call on Twitter
• Make CR lessons citable (part of sub-tasks)
  • Open house on citable lessons "Workflow to make CR lessons citable via Zenodo"
  • [JH] Testing CITATION.cff again
  • [JH] Making sure the 3 categories we defined still then map to CITATION.cff
    • The 3 categories are
      • "creator": significant contributions
      • "contributor"/Editor: reviewing/approving contributions
      • "contributor"/Other: smaller contributions
    • CITATION.cff has the category 'author'.
    • Zenodo has the categories 'creators' and 'contributors'
    • To keep to the 3 desired categories would involve manual editing of the metadata Zenodo.
  • [JH] Create a demo on a fork+sandbox where this is demonstrated for one lesson - Sandbox Zenodo for Social Coding
  • create an ORCID research community (DI checks how to do it)
    • Seems organizations can obtain ORCID only by becoming ORCID members https://info.orcid.org/about-membership/ . The annual fee for a Basic membership is 5 150 USD, with a 20% discount for non-profits, and 75% discount for small & start-up organizations.
    • Many universities are ORCID members, KTH being one https://orcid.org/members/001G000001EA3k9IAD-kth-royal-institute-of-technology
    • If a membership fee is required, suggestion is that we hold off for the time being.
    • [RB] check with NeIC if one can get an organization account for free
      • This was unfortunately not possible
  • [DI] Check how to create a Zenodo community and link with the ORCID one - Our Zenodo sandbox community https://sandbox.zenodo.org/communities/coderefinery/ - The real Zenodo community could preferably be registered by login in to Zenodo via the Code Refinery organization GitHub account - also find out whether records can be added to communities retroactively - This is possible. "communities" are edited as metadata which is editable after the release/publication as well. The Sandbox Zenodo for Social Coding was created, and its 'community' metadata was added afterwards.
  • [JH] Present progress on the workflow at upcoming CR staff meeting
    • JH gave a brief update Sep 27
• [DI, ME] Workshop, 2021 May - retrospective, document prepared and link shared (Part of sub-tasks)
  • Richard's notes from the coordination HackMD and Zulip in this HackMD
  • DI fixes categories and polishes the document more. Pls. add any comments/suggestions at the top of the document.
• [RB] Make past meeting minutes easier to browse, see: https://github.com/coderefinery/coderefinery.org/issues/570
• [NT] Investigate how Freshdesk treats personal data deleted from "our" Freshdesk.
  • Freshdesk's GDPR-related page
  • Permanent deletion of tickets >A ticket will be present in the spam or trash view only for 30 days, after which Freshdesk will be deleting it permanently.
  • Permanent deletion of contacts

    It will take a few seconds for each contact to be completely purged. During this time, the contact will be inaccessible.

  • Ref. Data processing addendum, chap 12 "Deletion or Return of Personal Data" >Controller may export all Service Data prior to the termination of the Customer’s Account. In any event, following the termination of the Customer’s Account, (i) subject to (ii) and (iii) below and the MSA and/or TermsMSA and/or Terms , Service Data will be retained for a period of 14 days from such termination within which Controller may contact Processor to export Service Data; (ii) where the Controller does not use custom mailbox and uses the e-mail feature, if available within the Service(s), e-mails forming part of Service Data are automatically archived for a period of 3 months; and (iii) logs are archived for a period of thirty (30) days in the log management systems, post which logs are retired to a restricted archived cold storage for a period of eleven (11) months (each a “Data Retention Period”). Beyond each such Data Retention Period, Processor reserves the right to delete all Service Data in the normal course of operation except as necessary to comply with Processor’s legal obligations, maintain accurate financial and other records, resolve disputes, and enforce its agreements. Service Data cannot be recovered once it is deleted.
  • We will delete all tickets that need no follow up and delete all contacts (RB has started doing this)
• [RD] Lead preparation of community call Sep 20 with focus on workshop planning
• [NT, RB] Analyze post-workshop survey
  • Result: https://github.com/coderefinery/post-workshop-survey
  • Follow-up:
    • [NT] Collect results for 2021 workshop
      • invitation draft
    • Create new release/DOI
    • [NT] update coderefinery.org, impact page -> PR, please review and merge, or ask for revisions.
    • -> Revisions are done pre-/post-
• [RB] Schedule 1-1 calls with everybody about tasks to get better balance
  • Ongoing, still a few left for scheduling
• [RB] Ask other PMs how they manage support/request emails
  • either no setup or in one project it is Atlassian service desk (provided by EOSC Nordic)
• [SR] Take initiative for the community call on the 6th Sep (call for setting a theme, dissemination etc.)
  • E.g. Workshop planning,
  • What should CR as an organiztion should do
  • [all, to respective employer/organization] invite in-kind sponsors and other stakeholders to the community call
• [AF] Drafting for Clarify better on website how to become a “client” or “sponsor” -> covered in #566
• [NT AF] Drafting for Clarify current status of workshops and future plans
• [ALL] Go through agenda for;
  • the open house event on the 19th Aug., and
  • the community call on the 23rd Aug.
• [RB] Analyze pre-workshop survey
  • Result: https://github.com/coderefinery/pre-workshop-survey
  • Follow-up:
    • Some data not analyzed yet
• [RB] Assignment of relevant tasks (planning, recruiting of volunteers in the community, dissemination, etc.)
• [JH, RB] organize meeting/open house to finalize the workflow for getting citable lessons in August.
  • Half-day Open House will be held on Aug 19, 12-15 CEST. The event is planned in this HackMD
  • Everyone who contributed (github) will be added as contributor.
  • Then we ask each contributor if they want to be an author.
  • Release “idea”: get both source + rendered in zenodo with one DOI for each release.
  • https://docs.readthedocs.io/en/stable/versions.html
  • Also installation guides and manuals should be released and citable (they are very useful also and were a lot of work and are being reused in places)

Archive of decisions

• 2021-10-11: monthly meeting (more open and general) + bi-weekly stand-up like meetings. JH will set up a Doodle with suggestions for a standing day and time for these meetings. (2021-19)
• 2021-10-11: We will modify the privacy policy to make it in line with the reality in which we don't know yet concrete plans on data-migrations etc (2021-13).
• 2021-09-27: We will continue using tinyletter for newsletters regarding upcoming events (2021-13).
• 2021-09-13: Privacy-policy and communication relevant decisions for transition to a new phase of CR (2021-13)
  • By the 31st Oct, all the sign-up info for workshops stored in Indico and email inquiries in Freshdesk are deleted.
  • We will consolidate communication towards Zulip since it makes it easy to unwatch and also unregister
  • We send an email to all notify-me registrants to inform them that we will discontinue the indico survey solution but encourage to follow updates on Zulip
• 2021-08-30: All team leads get a small gift and we invite expert helpers and volunteers and staff to a common lunch over video where we share a slideshow or videos which people can submit. (2021-08)
• 2021-08-16: We go for online celebration event (both for safety reasons and for better inclusivity), making a doodle for a date and options on what to do but most probably it will be dinner voucher and optional game or something. (2021-08)
• 2021-08-16: We will keep the decisions in this file and not delete with expectation that people will dig into commit history. There are different stakeholders who want to read decisions, not only CR staff. (2021-09)
• 2021-08-16: Regarding 2021-10, NT and AF will take initial drafting for the 2 points (status, and how to become a client or sponsor) (2021-10)
• 2021-08-02: Paid staff will attend "Community calls" as well, as this is to be where we will discuss more big picture and "interesting"-topics in-depth. However, community calls are also open to anyone interested in CodeRefinery. Community call topics will be defined at least two weeks in advance and communicated to the CodeRefinery community (email invitation for paid staff, twitter, website)
• 2021-08-02: Autumn workshop within the phase 2 is not prioritized to setting up the sustainability phase regardless of funding from NeIC or not (2021-11)
• 2021-08-02: Open House for making lessons citable to be held with paid-staff as "supposed to attend" and open to anyone interested (2021-06)
• 2021-07-05: Pre-/post-workshop survey will be processed for the talk on the 30th Aug at RDA Nordic and for the final report (see the task as well) (2021-03)
• 2021-07-05: RB to schedule 1-1 talks with everybody about task assignment and optimal task tracking since everybody prefers different ways to track items and we don't seem to agree on 1 solution that works for everybody. (2021-02)
• 2021-07-05: Meeting minutes for each meeting saved as commit history of a single file in github.com/coderefinery/coderefinery.org (2021-01)

Archive of discussions

• 2021-18: Impressions from steering group meeting: https://wiki.neic.no/wiki/CodeRefinery2-SG-meeting-2021-10-07

  • What remains to be done from the steering group perspective
  • Future of GitLab service: How to organize support.

• 2021-17: Negotiation phase and next steps: What we know after a couple of meetings last week.

  • 5th Nov contact persons in the consortium partners will be meeting and discuss budget, start date, and staffing situation and governance (steering group setup)
  • to be discussed but we will favor that each partner gets the chance to be represented
  • another worry is that there is a too rigid structure for joining
  • project start will be most likely 1st Jan
  • Q. A new member in business expertise is needed?
    • A. Yes, it will be ideal.
    • KTH&Uppsala, there is group called the Innovation Office that help out researchers to start up a small business or put researchers in contact with Industry. They could have some ideas on what kind of [non-]profit organization would be suitable for CR.

• 2021-16: Research Software Hour (RSH) to be adopted as CodeRefinery project?

  • No problem and encourage to use CR twitter and CR website for this but RB considers this to be both CR and Nordic-RSE project and both Twitter accounts can (and should?) be used

• 2021-15: Please help out with Lessons learned document

  • keeping open as todo

• 2021-14: Consider on-site work-meeting to kickstart next phase of Code Refinery. Two to three days in January or February 2022?

  • Decision Now the NeIC funding is approved and the budget covers traveling costs of those for both in-kind contributors and NeIC-paid staff, and there could be a way to fund other individual contributors or persons from new in-kind contributing organizations. The issue is basically for the sustainability phase and the discussion is carried over to the susstainability phase.
  • Open to everyone interested in CR. Most people could get the travel covered by the employer, but it would be good to have the possibility to offer travel support for those that need it.
  • Could be scheduled as an event just before or after to the NeIC all hands meeting (would be in-person, late Jan) as no additional travel would be required if the same location/city is chosen.

• 2021-13: Privacy policy: "How long we store the data" shows "Stored names and email addresses of users will be removed with the end of this project (2021-10-31)"

  • 2021-10-11: the end of the project is extended? If it can be considered in that way, isn't it better to modify the date writtein in the privacy policy, while investigating what the best way is in the future?
    • We can change the end date and be honest to say that nothing relevant to privacy policy in new sustainable phase of the project is yet decided as well as that we inform when things are set.
  • Notification to "users"? (Definition section shows; "Users - people who use and/or contribute to our services including workshops, trainings, events, lesson materials, other materials under on our website and other online resources, newsletters, notification form, and those who send inquiries to support@coderefinery.org. ")
  • Any plan/place to invite those interested for continued involvement? Zulip? (is it possible to keep using Zulip, btw?)
    • We need to delete sign-up data of workshops by the end of the project (31 Oct)
    • Notify-me (this is based on Indico)
    • Newsletter tinyletter.com etc. - we need to inform users
    • Challenge: which tech solution would we move to if we decide to move registrants?
      • Can we off-load this to a third party ? make people use Google account and handle the privacy there
    • Data processor agreements between hosting partners can make this really complicated
    • Freshdesk:
      • we continue using it until we have a better alternative
      • we delete all past conversations
    • Conclusions (written in the Decisions section as well):
      • we will consolidate communication towards Zulip since it makes it easy to unwatch and also unregister
      • we send an email to all notify-me registrants to inform them that we will discontinue the indico survey solution but encourage to follow updates on Zulip
    • we are unsure how to collect email addresses for those who want to be notified but do not want to sign up for chat
    • 2021-09-27: we plan to continue using tinyletter
      • we then need to notify the users and ask them to resubscribe OR change the privacy policy
        • investigate how to do it technically
        • we send a final email to exported list of tinyletter contacts and we ask them via email
        • in the resubscribe letter also describe/encourage how to get involved

• 2021-12: Reassignment of tasks and the plan until the end of the current phase? - are we on track?

  • Yes, we are on track :)

• 2021-11: Planning community call Sep 20

  • One thing I have been asked to do and we have been postponing (for good reasons) is a call where we can do some workshop planning
    • RD will chair this event

• 2021-10: Please help documenting our status and goals

  • Clarify current status of workshops and future plans
  • Clarify better on website how to become a “client” or “sponsor”
  • Basically document very briefly what we know and don't know and what we want to get to at this stage since currently we don't document this to the world at all. One might get the impression that the project is over.

• 2021-09: Proposal of change in format of this agenda/minutes file at every meeting

  • removal of older discussion items which were already discussed and got decisions (as it is in the older minutes)
  • moving older decision items to "archive" section at the bottom
    • RB: is that section getting too long?
    • NT: yes, it can get too long, but the older decisions still should be available in this document, thus moved to "archive" section but not "hidden" in commit history as old minutes.
  • limit the "done tasks" to those which were done between the previous meeting and the current meeting at least when it is commited as a minutes
    • RB: is the document getting too long or why?
    • NT: yes, it can get too long. while decisions are important enough to be kept in this document, outdated done tasks may unnecessarily eats up space before one reaches another section.

• 2021-08: Celebration event:

  • online
  • dinner voucher
  • question: who to invite? (we don't need to discuss names but rather question is whether all ELs also? expert helpers? instructors? how far back?)
  • RB asked NeIC XT to cover dinner voucher for 20 persons (I was tired when being asked that question and didn't think) but perhaps 20 is not enough. happy to re-negotiate.
  • does the dinner need to be then scheduled? (dinner over video is perhaps weird)
  • but still it would be nice to have some event where we can all connect at least for a moment?
  • conclusions:
    • send small gift to all ELs
    • dinner voucher to staff and expert helpers and volunteers who have contributed much
    • slideshow made out of feedback during dinner
    • short videos can be submitted which can be added
    • add something entertaining to watch
    • lunch or dinner? lunch (we could use one of the staff meeting slots)

• 2021-07: Draft for governance document. Very early stage drafty draft. Please comment/edit/ask.

  • This will be a community call topic. Not relevant anymore in this context.
  • 2021-10-11
    • Shouldn't it be taken in the community call where all the committers for the sustainability phase join for futher discussion rather than this staff meeting?
  • 2021-09-13
    • Reflection on the community call on the 6th Sep
    • Plan reflecting the contents written in "Training hubs" page
  • 2021-08-16
    • Discussed with relevance to 2021-10.
    • The governance should come after the vision is set and shared.
    • Community calls should be used as an arena for discussion including those who committed in-kind contributions in sustainability phase.
  • 2021-08-02
    • Who are/to be involved: everybody who is interested. Working group will be formed.
    • Clearly state that the goal is a non-profit organization
    • Clearly define what should be governed
    • Reference book: "AGILE STARTUP BOARDS"
    • Need to define minimum to be able to apply for funding (ex.) and have others join the project in-kind/volunteer.
      • First describe how to continue with in-kind model after 31.10.2021