Editing Meeting Minutes/2020-06-08 Regular Meeting (section)

== Agenda ==

* hellos and checkin
* value priorities
** Dario thinks it better to wait until Noah is around, postponed for now.
* summary of renaming tribes videocall /Martin
** Summary of https://codi.kanthaus.online/s/renamingtribes#
** Three new name suggestions, mockup available both on pad and in Slack channel.
* sexual abuse case - Support issue transparancy
** summary: /dario
*** someone reported another member of sexual abuse, years ago, unrelated to TR
*** problems:
**** believing the victim and protecting them and the community vs wrongly excluding someone (much less likely, we think)
**** looking into the messages only with consent vs. not making the victim feel as if we wouldn't believe them
** input / feedback:
*** simply "believing the victim" doesn't scale – but whats the alternative?
*** suggestion to only act upon a police report
**** keep in mind that most sexual abuse cases are not reported to police out of fear /dario
*** vouching feature
* update from the mobile side of things /Michael
** we had a code introduction meeting yesterday
*** https://codi.kanthaus.online/trustroots-mobile?view
** smoothly going forward
** Android & iOS public betas approved
*** https://play.google.com/apps/testing/org.trustroots.beta
*** https://testflight.apple.com/join/sCBEMC71
** Design is being worked on - happy for any input!
** Still confident to bring a viable beta to live in ~2 weeks :)
** can we add the app to our existing fdroid repo? /dario
* pick facilitator for next meeting
* random question
* integrate riot? integrate the matrix protocol without riot? /chagai
** proposal to simply set up a matrix instance on trustroots servers now
** later on:
*** integrate matrix protocol in trustroots, at first without federation
*** advantages:
**** instant messaging instead of waiting 15 mins for cronjob
**** include matrix's messaging features like "liking a message", "answering to specific messages"
** cons:
*** how to handle safety stuff then?
** action points:
*** bring it up again in a more tech-y meeting, also when Mikael is present who implemented messages