7th May 2020

From Online Meeting Coop Wiki
Jump to navigation Jump to search

Participants: Petter (DigidemLab/Collective.tools), Chris (Webarchitects), Wouter (femProcomuns/CommonsCloud)

  • commitments of each partner:
    • femProcomuns confirms commitment to dedicate 20 - 40 hours of work by paying David Jacovkis and Wouter, interest in 3 key objectives: 1) to use the shared resource, 2) to share knowledge and possibly offer replicas as a service, 3) as a starting point for further collaboration. Expect that contribution costs lower in the second year
    • DigidemLab put in €50-100/month, Feedback from test instance at workshops.collective.tools, Communication etc if needed
    • Webarchitects: Devops, sysadmin, Resources: GitLab, etc
  • When using .coop domain, we should have formal commitments of  each (future) partner to the eligibility criteria as defined here, and in  particular to "Organizations that are committed to the seven  cooperative principles"; I believe that each of our three organisations is in fact a cooperative (please confirm, Petter about Collective Tools...), but possibly FKI wouldn't qualify, as its Founding Principles are not covering 100% the ICA cooperative   principles. In that case we should be ether focusing on a) assuring that the little network we're building is governed  according to the 7 coop principles or b) is majority controlled  by cooperatives. Please do comment. We decide that we see the shared project as complying with the Cooperative Principles. Wouter will formulate these for our project.
  • Name for the group "The Online Meeting Cooperative" online meeting cooperative for learning and conferencing (Working title)
    • select the domain name & register: we choose meet.coop : Chris registers meet.coop as shared costs. Webarchitects takes ownership on behalf of the Online Meeting Cooperative, and it can be transfered to a future shared legal entity
    • we mention the potential confusion with animal "meat" (but meeting.coop also would make sense, we can decide later)
  • meet.coop & www.meet.coop: here comes the BBB install with some intro text (multilingual)
    • learn.meet.coop -> Moodle install
    • org.meet.coop -> intro & roadmap
  • review perspectives of potential partners
    • FKI
    • Remix the Commons
    • Hypha
    • Schools would probably need their own server, they could try our server to demo, or possibly contribute for a small scale pilot
  • agree on server specs for the first months
  • Chris starts developing ansible script testing on a vm
  • then move to a simple bare metal machine
  • then migrate to a stronger machine when needed
  • agree on collaboration and communication channels &  methods
  • keep track of time worked on tasks https://www.kimai.org/ -> Chris could set it up on a subdomain
  • list tasks & assignments
  • Chris registers domain
  • Wouter drafts intro text
  • Chris sets up a git.coop group & Jekyll repo
  • Petter sets up the Jekyll site to work on together
  • Open item: someone to design a logo and visual id
  • Where to host the code
  • potential funding options: Petter has a look on one call