18th June 2020

From Online Meeting Coop Wiki
Jump to navigation Jump to search

Attendents: Mike, Chris, Luke, Oli, Wouter from femProcomuns, Henning from Unicode coop in Germany, ColloCall, Gunnar, Aspiration Tech in SF, Ben, Yurko, and Elon from Hypha, Yasu, from Japan.

Discourse forum thread

Contents

Agenda

  • 3pm CET https://ca.meet.coop/b/wou-cyy-wpt
    • Attendance round
    • Agree on agenda (see the notes from the last meeting)
    • Immediate tasks on ca.meet.coop:
      • Registration policy, this was set to invite only but currently is open, was it set this was intentionally or by accident?
      • Who, from which organisatons needs accounts (all membership orgs shoiuld have a admin account to create other accounts)?
      • What else?
    • ColloCall presentation from hng
    • Logo design, see the forum thread and the Visual Design Inputs wiki page
    • Summary/feedback from the OPEN2020 conference
      • Session video recording - protocols needed? A: for sys admin. B: for room/meeting admin.
      • Multi-stakeholder nature of the BBB instance/meet.coop service.
      • Etc
    • Fund raising/contributions
      • potential/new members
      • upcoming events
      • potential grants
      • other income streams, reseller options?
    • Governance model (commons - cooperativism - grassroots)
      • Mike volunteering to bring a proposal next week, arising from Open2020 discussion? Who else to collaborate on this? Wouter/Petter/Oli were in the session.
    • On Frontends (Greenlight, Moodle, Canvas, NextCloud, WordPress...): draft systems architecture
      • Further elaboration of the presentation front-end? Provision of map tools?
    • Communication
    • Action items
    • Any other issue
      • demo rooms?
      • explaining membership to new ppl

Notes

- registration policy (invite only vs. open)

  • - oli: greenlight doesn't work for us, have to email someone, then the have to enter email again, then they have to receive an email again #friction: onboard
  • - chris: disabled email verification, password resets now work again
    • - we need to decide, pay to use vs. open reg
    • - oli: should capitalize on the commercial op now

- admin acc for members?

  • - chris: mayfirst paid 250 euro, what account?
  • - ben: need policy and current access levels of orgs / ppl published on website (scary to users if access is widespread)
  • - mike: yes, access levels, ppl shouldn't be able to affect other users
  • - #todo (next few days) define roles on wiki and write current ppl's access level
    • - SSH access chris, luke, koumbit has
    • - admin roles access: Wouter
    • - org admin access: Oli and Mike are open 2020 admins
  • - what is an org member vs. individual user

- chris: re-enabled email verification so ppl can reset their passwords

- henning on collocall

  • - started in april, small tech coop in germany, 20 BBB servers running baremetal
  • - focus on german market
  • - dedi bare metal: 200 EUR
  • - shared accounts: forked greenlight instances (added env var to set max participants) but still points to the same BBB back-end (nice!)
  • - can set how many rooms user can create, admin settings, with fair use
  • - building cluster for shared accounts, have shared accounts point to that
  • - also sell to individual persons
  • - no automated ordering, ppl email us to get an account
  • - I think greenlight isn't sufficient to do the role model that meet.coop wants
  • - wouter: how many orgs have joined?
    • - (breaking up)
  • - chris: we should copy what you've done
    • - do they each need a postgres database
    • - running multiple greenlights
  • - chris: forks of greenlight?
    • - they are public
  • - ben: mix of users?
    • - chris: simple accounts for day to day meetings, NGOs, team meetings
    • - conferences over wkends up to 400 participants (lots of work!) - 2 servers for one conference on diff tracks
    • - wordpress plugin vs. links to greenlight meetings
    • - two dedicated conf servers, remove all data give to conf for a week
    • - give admin and BBB secrets to organizers, they decide how to manage access
    • - recordings, deactivated recordings bc of privacy laws and GDPR (currently not GDPR - everything is recorded even if not pressing recording button (but automatically deleted later if recording wasn't requested)
      • - if people want to record, we tell them about GDPR
      • - some conf, we export recordings for them, not great not a downloadable recording
        • - script 1: server side that generate downloadable files (slide + audio, no video)
        • - script 2: locally run
    • - scripts stitch together the different files, or clients use raw and make own video
    • - twitch /youtube stream videos
    • - publish a data policy, privacy contract, etc. (all in German :)
  • - Branch with max participants in ENV: https://github.com/hng/greenlight/tree/feature/maxParticipants_duration
  • - henning on our IRC
  • - Wouter to move ongoing convo to forum

- logo

  • - https://forum.meet.coop/t/meet-coop-logo-design/48/5
  • - wait for Mel next call

- OPEN 2020

  • - videos, oli needs to manually edit, learning experience
  • - oli: how do we pay?
  • - wouter: great conference
  • - mike: certain recordings, two protocols:
    • - sysadmin protocol: how scripts are organized
    • - meeting chair protocol: how BBB works, when to press recording, etc. (how to use rooms)
  • - mike: mismatch between the two groups on "how to use rooms"
  • - mike: very multistakeholder, need to work on governance of meet.coop

- sustainability

  • - Gunner: happy to involve in budgeting, financial planning... but next week! hard stop to another meeting
  • - oli: why focus on grants? how shall we make these decisions
  • - any procedures in place for how things should be decided
  • - wouter: there are financial custodians for contributions
  • - oli: types of stakeholders... want to bring on new members
  • - work out plans for our users that are easy to understand
    • - chris: make enough money before incorporating, disagree with working out roles and payment things
    • - copy what hennings have done
    • - mike: need to work out marketing plan
  • - ben: why does anyone want to use meet.coop instead?
    • - wouter: collo German focused, meet.coop -> cooperatives
    • - ben: we need to highlight these
    • - chris/wouter: plenty of room for doing BBB hosting like wordpress hosting

- mike: like 3 other ppl to work with governance model #todo

  • - wouter: ok to do a prep meeting tuesday next week
  • - ben: me too for Tues

- LDAP connect to other services we alrdy have

  • - wouter: member orgs can use their own nextcloud, etc.
  • - ben: this is also a differentiator we have

- Greenlight containers: 1) for individuals, 2) for orgs, 3) for events.

- First test out the Greenlight fork by ColloCall

  • - any other?
  • - mostly greenlight
  • - henning may do more features on top of it

- demo room?

  • - demo.meet.coop (open and unmanged, probably needs to change :) now anyone can make an account and play with it
  • - dev.meet.coop (for dev)
  • - https://wiki.meet.coop/wiki/Servers

- wouter: ansible for Mailtrain ?

- yasu: what sort of customer go with colloco instead of Zoom?

  • - quiet across... schools (not state schools), social academia, educational, NGOs, unions, lawyers, architects
  • - privacy concerns... in the end it's a privately run company that routes thru China

#todo