Trustroots Wiki - User contributions [en]

Meeting Minutes/2020-10-12 General Meeting Update

2020-10-12T20:54:12Z

Lemoert: Created page with "=General Meeting Update= Note: due to most active volunteers simultaneously getting rather busy schedules there has been a reduced activity since the last Regular Meeting (28..."

=General Meeting Update=

Note: due to most active volunteers simultaneously getting rather busy schedules there has been a reduced activity since the last Regular Meeting (28 Aug). Some things are moving forward at a slow pace, but nothing specific worth mentioning at the moment. When things get active again the meetings will start up once more.

Over and out.

Trustroots

2020-09-14T18:38:28Z

Lemoert:

'''[https://www.trustroots.org/ Trustroots]''' is a hospitality exchange network run by a UK non-profit foundation. The software is open source.
It was started in December 2014 is being built by a small team of activists who felt that the world of sharing is being taken over by corporations trying to monetize people's willingness to help each other. Same team brought you also [[:hitch:|Hitchwiki]], [[:trash:|Trashwiki]] and [[:nomad:|Nomadwiki]].

{{stub}}

== Circles ==

As of August Trustroots has 42 circles. At the moment these are:

{{tribes}}

== History ==
Trustroots was launched in December 2014 by former volunteers of BeWelcome and Couchsurfing. By the same people who brought you also Hitchwiki, Trashwiki and Nomadwiki.
Read more about Trustroots history [[History_of_Trustroots|here]].

[[Category:Hospitality exchange networks]]
[[Category:Trustroots]]

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:26:11Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-08-28 16:00 UTC
* Facilitator: Martin A.
* Present: Chagai, Hlib, Martin A.

= Agenda =

* Hellos and checking in.
* Last week's Action Points (10 minutes):
** Doodle for new meeting time /Martin A.
*** Meeting time changed to Fridays at 16:00 UTC for now.
** Donate page update /Martin A.
*** Text is ready, next week Martin A. and Chagai will have a look at the layout etc.
** Sent a message to Paula re: her point left on the agenda. /Martin A.
** Shawn will work on blogpost for rollout of Experiences (Formerly known as references)
*** Update is that i have accumulated information from Noahs statements and the converstions on slack and am waiting to see the feature finalized to write the draft. anyone js welcome to edit and help. Any timeline on rolling it out? /Shawn
**** The timeline is unclear at the moment, but the first release might not be all too far into the future. From a couple of weeks to a couple of months :)
**** Probably good to have it ready beforehand anyway.
** Loberto will help facilitate the Anarchist request to describe what Anarchy is all about on the circle page. - Updates?
*** Was this about the text or the image (or both) on the page? /Martin A.
* Your talking point here :)
** Thoughts on P2 /Martin A.
*** Would potentially work well as a tool for semi-permanent documentation. I.e. where things discussed in the volunteer chat is gathered and things then organised and moved along.
**** For most projects there will probably be a need for somebody to take the (unofficial) responsibility as an idea needs to be pushed a bit to get done.
*** Potentially P2 could also be used as a place for permanent documentation.
**** Martin will create mockups on the Wiki and P2 at some stage so we can compare them.
*** Testing P2 simultaneous editing is also needed to see if it would work to replace Codi altogether (for meeting minutes etc.)
**** Is the Codi history function relevant, and does something similar exist in P2?
** Updates on new Code of Conduct
*** Point not really talked about, pushed ahead to next week.
* Additional topics/questions
** Chagai mentions the idea of bridging/creating a WA group etc. As it's something he's interested in he'll likely tip away with it on his freetime and when done we can try and see where it goes.
** Hlib will write Aleksandar to give a bit of a tech welcome and also see if it'd be possible to organise a tech videocall re: experiences next week, preferably organising with Mikael and Noah.

* Pick facilitator for next meeting

---

== Action points and outcomes ==

* '''Next Date:''' September 04th 2020, 16:00 UTC
* '''Next Facilitator:''' TBD

* As relatively evident, the weekly meeting has been shifted to Fridays 16:00 UTC.
* Martin A. and Chagai will have a look at the new donation page layout, hopefully during next week.
* Shawn has prepared things for writing the draft for a blog post re: Experiences. Help and/or reviewing welcome!
* Martin A. will keep exploring P2 and the organisation of permanent documentation/project management. Especially in view of making the process transparent and easy for new volunteers.
* Hlib will write Aleksandar re: tech and see if it's possible to organise a videocall re: experiences with those interested in the tech side (pinging Mikael, Noah and Chagai there).

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:25:37Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-08-28 16:00 UTC
* Facilitator: Martin A.
* Present: Chagai, Hlib, Martin A.

= Agenda =

* Hellos and checking in.
* Last week's Action Points (10 minutes):
** [Doodle for new meeting time (https://doodle.com/poll/t2f4y94p2ubmw9ah)] /Martin A.
*** Meeting time changed to Fridays at 16:00 UTC for now.
** Donate page update /Martin A. ([P2](https://trustroots.p2.blog/2020/08/20/updating-the-donate-page/), [GitHub](https://github.com/Trustroots/community/projects/6/))
*** Text is ready, next week Martin A. and Chagai will have a look at the layout etc.
** Sent a message to Paula re: her point left on the agenda. /Martin A.
** Shawn will work on blogpost for rollout of Experiences (Formerly known as references)
*** Update is that i have accumulated information from Noahs statements and the converstions on slack and am waiting to see the feature finalized to write the draft. anyone js welcome to edit and help. Any timeline on rolling it out? /Shawn
**** The timeline is unclear at the moment, but the first release might not be all too far into the future. From a couple of weeks to a couple of months :)
**** Probably good to have it ready beforehand anyway.
** Loberto will help facilitate the Anarchist request to describe what Anarchy is all about on the circle page. - Updates?
*** Was this about the text or the image (or both) on the page? /Martin A.
* Your talking point here :)
** Thoughts on P2 /Martin A.
*** Would potentially work well as a tool for semi-permanent documentation. I.e. where things discussed in the volunteer chat is gathered and things then organised and moved along.
**** For most projects there will probably be a need for somebody to take the (unofficial) responsibility as an idea needs to be pushed a bit to get done.
*** Potentially P2 could also be used as a place for permanent documentation.
**** Martin will create mockups on the Wiki and P2 at some stage so we can compare them.
*** Testing P2 simultaneous editing is also needed to see if it would work to replace Codi altogether (for meeting minutes etc.)
**** Is the Codi history function relevant, and does something similar exist in P2?
** Updates on new Code of Conduct
*** Point not really talked about, pushed ahead to next week.
* Additional topics/questions
** Chagai mentions the idea of bridging/creating a WA group etc. As it's something he's interested in he'll likely tip away with it on his freetime and when done we can try and see where it goes.
** Hlib will write Aleksandar to give a bit of a tech welcome and also see if it'd be possible to organise a tech videocall re: experiences next week, preferably organising with Mikael and Noah.

* Pick facilitator for next meeting

---

== Action points and outcomes ==

* '''Next Date:''' September 04th 2020, 16:00 UTC
* '''Next Facilitator:''' TBD

* As relatively evident, the weekly meeting has been shifted to Fridays 16:00 UTC.
* Martin A. and Chagai will have a look at the new donation page layout, hopefully during next week.
* Shawn has prepared things for writing the draft for a blog post re: Experiences. Help and/or reviewing welcome!
* Martin A. will keep exploring P2 and the organisation of permanent documentation/project management. Especially in view of making the process transparent and easy for new volunteers.
* Hlib will write Aleksandar re: tech and see if it's possible to organise a videocall re: experiences with those interested in the tech side (pinging Mikael, Noah and Chagai there).

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:25:17Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-08-28 16:00 UTC
* Facilitator: Martin A.
* Present: Chagai, Hlib, Martin A.

= Agenda =

* Hellos and checking in.
* Last week's Action Points (10 minutes):
** [Doodle for new meeting time] (https://doodle.com/poll/t2f4y94p2ubmw9ah) /Martin A.
*** Meeting time changed to Fridays at 16:00 UTC for now.
** Donate page update /Martin A. ([P2](https://trustroots.p2.blog/2020/08/20/updating-the-donate-page/), [GitHub](https://github.com/Trustroots/community/projects/6/))
*** Text is ready, next week Martin A. and Chagai will have a look at the layout etc.
** Sent a message to Paula re: her point left on the agenda. /Martin A.
** Shawn will work on blogpost for rollout of Experiences (Formerly known as references)
*** Update is that i have accumulated information from Noahs statements and the converstions on slack and am waiting to see the feature finalized to write the draft. anyone js welcome to edit and help. Any timeline on rolling it out? /Shawn
**** The timeline is unclear at the moment, but the first release might not be all too far into the future. From a couple of weeks to a couple of months :)
**** Probably good to have it ready beforehand anyway.
** Loberto will help facilitate the Anarchist request to describe what Anarchy is all about on the circle page. - Updates?
*** Was this about the text or the image (or both) on the page? /Martin A.
* Your talking point here :)
** Thoughts on P2 /Martin A.
*** Would potentially work well as a tool for semi-permanent documentation. I.e. where things discussed in the volunteer chat is gathered and things then organised and moved along.
**** For most projects there will probably be a need for somebody to take the (unofficial) responsibility as an idea needs to be pushed a bit to get done.
*** Potentially P2 could also be used as a place for permanent documentation.
**** Martin will create mockups on the Wiki and P2 at some stage so we can compare them.
*** Testing P2 simultaneous editing is also needed to see if it would work to replace Codi altogether (for meeting minutes etc.)
**** Is the Codi history function relevant, and does something similar exist in P2?
** Updates on new Code of Conduct
*** Point not really talked about, pushed ahead to next week.
* Additional topics/questions
** Chagai mentions the idea of bridging/creating a WA group etc. As it's something he's interested in he'll likely tip away with it on his freetime and when done we can try and see where it goes.
** Hlib will write Aleksandar to give a bit of a tech welcome and also see if it'd be possible to organise a tech videocall re: experiences next week, preferably organising with Mikael and Noah.

* Pick facilitator for next meeting

---

== Action points and outcomes ==

* '''Next Date:''' September 04th 2020, 16:00 UTC
* '''Next Facilitator:''' TBD

* As relatively evident, the weekly meeting has been shifted to Fridays 16:00 UTC.
* Martin A. and Chagai will have a look at the new donation page layout, hopefully during next week.
* Shawn has prepared things for writing the draft for a blog post re: Experiences. Help and/or reviewing welcome!
* Martin A. will keep exploring P2 and the organisation of permanent documentation/project management. Especially in view of making the process transparent and easy for new volunteers.
* Hlib will write Aleksandar re: tech and see if it's possible to organise a videocall re: experiences with those interested in the tech side (pinging Mikael, Noah and Chagai there).

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:25:04Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-08-28 16:00 UTC
* Facilitator: Martin A.
* Present: Chagai, Hlib, Martin A.

= Agenda =

* Hellos and checking in.
* Last week's Action Points (10 minutes):
** [Doodle for new meeting time](https://doodle.com/poll/t2f4y94p2ubmw9ah) /Martin A.
*** Meeting time changed to Fridays at 16:00 UTC for now.
** Donate page update /Martin A. ([P2](https://trustroots.p2.blog/2020/08/20/updating-the-donate-page/), [GitHub](https://github.com/Trustroots/community/projects/6/))
*** Text is ready, next week Martin A. and Chagai will have a look at the layout etc.
** Sent a message to Paula re: her point left on the agenda. /Martin A.
** Shawn will work on blogpost for rollout of Experiences (Formerly known as references)
*** Update is that i have accumulated information from Noahs statements and the converstions on slack and am waiting to see the feature finalized to write the draft. anyone js welcome to edit and help. Any timeline on rolling it out? /Shawn
**** The timeline is unclear at the moment, but the first release might not be all too far into the future. From a couple of weeks to a couple of months :)
**** Probably good to have it ready beforehand anyway.
** Loberto will help facilitate the Anarchist request to describe what Anarchy is all about on the circle page. - Updates?
*** Was this about the text or the image (or both) on the page? /Martin A.
* Your talking point here :)
** Thoughts on P2 /Martin A.
*** Would potentially work well as a tool for semi-permanent documentation. I.e. where things discussed in the volunteer chat is gathered and things then organised and moved along.
**** For most projects there will probably be a need for somebody to take the (unofficial) responsibility as an idea needs to be pushed a bit to get done.
*** Potentially P2 could also be used as a place for permanent documentation.
**** Martin will create mockups on the Wiki and P2 at some stage so we can compare them.
*** Testing P2 simultaneous editing is also needed to see if it would work to replace Codi altogether (for meeting minutes etc.)
**** Is the Codi history function relevant, and does something similar exist in P2?
** Updates on new Code of Conduct
*** Point not really talked about, pushed ahead to next week.
* Additional topics/questions
** Chagai mentions the idea of bridging/creating a WA group etc. As it's something he's interested in he'll likely tip away with it on his freetime and when done we can try and see where it goes.
** Hlib will write Aleksandar to give a bit of a tech welcome and also see if it'd be possible to organise a tech videocall re: experiences next week, preferably organising with Mikael and Noah.

* Pick facilitator for next meeting

---

== Action points and outcomes ==

* '''Next Date:''' September 04th 2020, 16:00 UTC
* '''Next Facilitator:''' TBD

* As relatively evident, the weekly meeting has been shifted to Fridays 16:00 UTC.
* Martin A. and Chagai will have a look at the new donation page layout, hopefully during next week.
* Shawn has prepared things for writing the draft for a blog post re: Experiences. Help and/or reviewing welcome!
* Martin A. will keep exploring P2 and the organisation of permanent documentation/project management. Especially in view of making the process transparent and easy for new volunteers.
* Hlib will write Aleksandar re: tech and see if it's possible to organise a videocall re: experiences with those interested in the tech side (pinging Mikael, Noah and Chagai there).

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:24:18Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-08-28 16:00 UTC
* Facilitator: Martin A.
* Present: Chagai, Hlib, Martin A.

= Agenda =

* Hellos and checking in.
* Last week's Action Points (10 minutes):
** <a href="https://doodle.com/poll/t2f4y94p2ubmw9ah">Doodle for new meeting time</a> /Martin A.
*** Meeting time changed to Fridays at 16:00 UTC for now.
** Donate page update /Martin A. ([P2](https://trustroots.p2.blog/2020/08/20/updating-the-donate-page/), [GitHub](https://github.com/Trustroots/community/projects/6/))
*** Text is ready, next week Martin A. and Chagai will have a look at the layout etc.
** Sent a message to Paula re: her point left on the agenda. /Martin A.
** Shawn will work on blogpost for rollout of Experiences (Formerly known as references)
*** Update is that i have accumulated information from Noahs statements and the converstions on slack and am waiting to see the feature finalized to write the draft. anyone js welcome to edit and help. Any timeline on rolling it out? /Shawn
**** The timeline is unclear at the moment, but the first release might not be all too far into the future. From a couple of weeks to a couple of months :)
**** Probably good to have it ready beforehand anyway.
** Loberto will help facilitate the Anarchist request to describe what Anarchy is all about on the circle page. - Updates?
*** Was this about the text or the image (or both) on the page? /Martin A.
* Your talking point here :)
** Thoughts on P2 /Martin A.
*** Would potentially work well as a tool for semi-permanent documentation. I.e. where things discussed in the volunteer chat is gathered and things then organised and moved along.
**** For most projects there will probably be a need for somebody to take the (unofficial) responsibility as an idea needs to be pushed a bit to get done.
*** Potentially P2 could also be used as a place for permanent documentation.
**** Martin will create mockups on the Wiki and P2 at some stage so we can compare them.
*** Testing P2 simultaneous editing is also needed to see if it would work to replace Codi altogether (for meeting minutes etc.)
**** Is the Codi history function relevant, and does something similar exist in P2?
** Updates on new Code of Conduct
*** Point not really talked about, pushed ahead to next week.
* Additional topics/questions
** Chagai mentions the idea of bridging/creating a WA group etc. As it's something he's interested in he'll likely tip away with it on his freetime and when done we can try and see where it goes.
** Hlib will write Aleksandar to give a bit of a tech welcome and also see if it'd be possible to organise a tech videocall re: experiences next week, preferably organising with Mikael and Noah.

* Pick facilitator for next meeting

---

== Action points and outcomes ==

* '''Next Date:''' September 04th 2020, 16:00 UTC
* '''Next Facilitator:''' TBD

* As relatively evident, the weekly meeting has been shifted to Fridays 16:00 UTC.
* Martin A. and Chagai will have a look at the new donation page layout, hopefully during next week.
* Shawn has prepared things for writing the draft for a blog post re: Experiences. Help and/or reviewing welcome!
* Martin A. will keep exploring P2 and the organisation of permanent documentation/project management. Especially in view of making the process transparent and easy for new volunteers.
* Hlib will write Aleksandar re: tech and see if it's possible to organise a videocall re: experiences with those interested in the tech side (pinging Mikael, Noah and Chagai there).

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:07:34Z

Lemoert:

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:05:32Z

Lemoert:

Meeting Minutes/2020-08-28 Regular Meeting

2020-08-28T17:04:33Z

Lemoert: Created page with "= Trustroots Meeting = * Date: 2020-08-28 16:00 UTC * Facilitator: Martin A. * Present: Chagai, Hlib, Martin A. = Agenda = * Hellos and checking in. * Last week's Action Po..."

Meeting Minutes/2020-08-17 Regular Meeting

2020-08-17T18:26:55Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-08-17 16:00 UTC
* Facilitator: Martin
* Present: Martin, Shawn, Chagai, Nikki, Hlib, Loberto

== Agenda ==

*Hellos and checking in.

*Noah asks to move the meeting to another day/time bc. he has choir rehearsal every monday at 5pm UTC and needs to leave home at ~6:15

**Martin will set up a Doodle to check time

*The Support team has been working on a guideline document that includes ethical principles of the platform. Everyone is invited to read through the work in progress and add/comment. Link is here: https://codi.kanthaus.online/7P_XQoCoTCqnSfjdHDrFHw?both

*Paula has said she will take the lead on populating/collecting info for team.trustroots.org page
**Martin will ping Paula for update and clarification on such task.

*Chagai, Martin, Shawn agree that it may be good to show short biographies for the team on the page to present a robust team working on Trustroots currently as part of the public relations.

*Hlib suggests an internal volunteer page for fellow volunteers to get to know each other

**Loberto has referred Hlib to #ahoyparty Codi for this. It exists but needs to be worked on further. Further development of
**/teams might be good

*Trustroots Donation page: It needs to be updated seeing as we don't currently accept donations
**Nikki will explore rearranging and condensing the information on the page.
**Should the donation page be renamed possibly?

*Styleguide for Trustroots: Is there one (Nikki K)
**Will ping Mikael about it and to explore possibly creating one.

*Idea: If we do accept donations, they could go to funding a Trustroots hackathon somewhere and support travel expenses for those coming.

*There is momentum in working on the reference based system (Now known as "Experiences") on the slack. For those interested to participate in the conversation and development, look at the #experiencedesign channel. Shawn is working on a blogpost to explain and announce the rollout.

*One idea to promote good reference usage is to have a proper campaign educating people:
**Start with a good blog post about it, shared on all social media
**Mention it in our next newsletter
**Write in the FAQ “References good practices”
**Write a wiki article about references, why giving a negative reference is not a bad thing
**Additional topics/questions

*Anarchist Circle: Someone contacted support to offer to update the photo and description.
**Loberto can help facilitate the request.

*We did not pick a facilitator for the next meeting. Could it be you?

*Have a good week everyone!

== Action points and outcomes ==

* '''Next Date:''' August 24th 2020, 16:00 UTC
* '''Next Facilitator:''' TBD

*Martin will send out the doodle to explore other times to meet
*Shawn will work on blogpost for rollout of Experiences (Formerly known as references)
*Nikki will contact Mikael about the creation or existence of a styleguide
*Martin will contact Paula about populating the trustroots.team page.
*Loberto will help facilitate the Anarchist request to describe what Anarchy is all about on the circle page.

Meeting Minutes/2020-08-17 Regular Meeting

2020-08-17T17:12:41Z

Lemoert: Created page with "Test"

Test

Do-ocracy

2020-08-02T10:24:13Z

Lemoert:

[[Trustroots]] is organised like a '''do-ocracy''' and we embrace a culture of participation. We encourage each member of the community to use their right to take on responsibilities. We understand that not everyone is comfortable with this way of working right away, but we think it's a good way to move forward in a [[volunteer]]ing environment where no one is forced to do anything.

== Trustroots Foundation and Volunteers ==

Legally, [[Trustroots Foundation]] owns and operates [[Trustroots]], but the actual decisions and work are taken and done by the active volunteers.

* Ideally the foundation does as little as possible, just whatever is legally essential to ensure longevity plus basics of volunteer and member happiness.
* Ideally volunteers do what makes themselves and members happy.
* Some level of discussions and politics are inevitable to avoid creating cliques that exclude others. Meetings and discussions aren’t the goal within itself though, they’re just means to an end.

Organizations that work in similar ways are Burning Man, Rainbow Gatherings etc. It's also a very common way of working for online projects, especially in free open source projects (which Trustroots is as well) and wikis, for example [[:hitch:|Hitchwiki]].

We value an attitude of getting things done. Arguments about minor issues shouldn't get in the way of the work and achieving more important results. Where suitable we believe decisions should be taken by those who do the work.

== Adhocracy ==

Another term that is very much related to do-ocracy but got out of fashion is '''adhocracy'''. Most of the concepts and ideas around adhocracy apply just as well to Trustroots. According to [//en.wikipedia.org/wiki/Adhocracy ''Wikipedia''] <q>Adhocracy is a flexible, adaptable and informal form of organization that is defined by a lack of formal structure. It operates in an opposite fashion to a bureaucracy.</q>

== Consensus ==

We have so far managed to avoid votes and voting. We prefer reaching consensus.

* https://opensource.guide/building-community/#focus-on-the-journey-not-the-destination
* https://en.wikipedia.org/wiki/Rough_consensus

== Not: "I can do whatever I want" ==

It doesn't mean: "I can do whatever I want", it's more like "I can choose how this thing we discussed is done".

It's also important to consider impact and reversibility when you want to do something.
For example, editing the [[Wiki]] is not going to have a huge impact and can in most cases be be done without any discussion. [[Wiki.trustroots.org:Create_account|Check here how to create an account]], log in and [https://wiki.trustroots.org/w/index.php?title=Do-ocracy&action=edit click edit].

At the other end of the spectrum, implementing [[references]] requires advanced coding and UI/UX and is going to impact almost everyone and is almost impossible to revert. In such cases discussions, consensus and collaboration is essential.

== Other organizations ==

Some organizations are using similar principles:
* [https://en.wikipedia.org/wiki/Burning_Man#Principles Burning Man]
* [https://en.wikipedia.org/wiki/Rainbow_Gathering#Social_aspects Rainbow Gathering]

Other hospitality exchange networks have different structures:
* [[Philosophy of BeWelcome|BeWelcome is a democracy]], with regular voting and discussions. Official French non-profit.
* [[CouchSurfing]] was run by a small group in a sort of oligarchy. In 2011 they became for-profit and up for grabs for venture capital.
* [[Hospitality Club]] is probably best described as having been a dictatorship from the start. No official organization, sole proprietor.
* [[WarmShowers]] is a US non-profit with the 501(c)(3) charity status. It's run by a board of 5 members with little clarity about community involvement.

== Further reading ==
* https://github.com/Trustroots/trustroots/blob/master/CONTRIBUTING.md
* https://communitywiki.org/wiki/DoOcracy
* https://en.wikipedia.org/wiki/Adhocracy
* https://en.wikipedia.org/wiki/Future_Shock

[[Category:Concepts]]

Volunteer

2020-08-02T09:46:54Z

Lemoert:

[[Trustroots]] is completely based on '''volunteers'''. You can find [//team.trustroots.org/Volunteering.html ''more information here''].

See [[:trustroots:volunteering]]

{{stub}}

Volunteer

2020-08-02T09:46:01Z

Lemoert:

[[Trustroots]] is completely based on '''volunteers'''. You can find [//https://team.trustroots.org/Volunteering.html ''more information here''].

See [[:trustroots:volunteering]]

{{stub}}

Volunteer

2020-08-02T09:45:26Z

Lemoert:

[[Trustroots]] is completely based on '''volunteers'''. You can find [[//https://team.trustroots.org/Volunteering.html ''more information here'']].

See [[:trustroots:volunteering]]

{{stub}}

Volunteer

2020-08-02T09:43:33Z

Lemoert:

[[Trustroots]] is completely based on '''volunteers'''. You can find [[more information here]].

See [[:trustroots:volunteering]]

{{stub}}

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:23:28Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
*** Currently working on it, ish..
*** Mikael to ping about something he might be able to help it. :-)
*** Use social media to reach out
*** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
*** Chagai is working on it.
*** jitsi instance first up.
*** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
*** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
*** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
*** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
*** No space in next newsletter
*** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date:''' July 20th 2020, 16:00 UTC
* '''Next Facilitator:''' Mariano
* For recording video calls we need to discuss it more to see interest, set up the how-to, and also check for consensus in each call.
* Future weekly meetings will be held on Mondays at 16:00 UTC only (no shifting time).
* Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter. Mikael might ping him in relation to this.
* Chagai will implement a test bridge between Slack and one other platform. Jitsi first up!
* VA will continue with documentation etc. (Martin A. will look into creating a Guide for Guides.)
* If you use Codi, keep an eye out for a Best Practices handout
* Mikael will blast a short blurb to social media for call for developers
* We'll add going through last meeting's action points to the agenda as a standard point.
** Perhaps keeping it around 10 minutes and focussing on what hasn't been done/are blocked.
** If there are updates during the week comments can be added to Codi to speed things up.
* We will need to figure out how to send newsletters. A couple of people should know how to do it to not create dependency/stress.
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts. (+ relevant docs for tools)
* We will try out ClickUp and GitHub for project management and use Loberto as a guinea pig to see what works for a non-tech person.
* Loberto is crowned Slack Police and all are cool with that.
* For people trapped due to lockdown we can refer to the existing projects that work in the area. Bringing it up on social media might be the fastest way of getting it done (seeing as, hopefully, the lockdown will not last all that much more).
* For next week's New Volunteer meeting we should reach out to volunteers that have joined since the CS paywall and also post a note in #general.

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:10:18Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
*** Currently working on it, ish..
*** Mikael to ping about something he might be able to help it. :-)
*** Use social media to reach out
*** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
*** Chagai is working on it.
*** jitsi instance first up.
*** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
*** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
*** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
*** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
*** No space in next newsletter
*** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date:''' July 20th 2020, 16:00 UTC
* '''Next Facilitator:''' Mariano
* For recording video calls we need to discuss it more to see interest, set up the how-to, and also check for consensus in each call.
* Future weekly meetings will be held on Mondays at 16:00 UTC only (no shifting time).
* Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter. Mikael might ping him in relation to this.
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:05:12Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date:''' July 20th 2020, 16:00 UTC
* '''Next Facilitator:''' Mariano
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:04:41Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date: July 20th 2020, 16:00 UTC'''
* ''''Next Facilitator: Mariano''''
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:04:28Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date: July 20th 2020, 16:00 UTC'''
* 'Next Facilitator: Mariano'
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:04:12Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date: July 20th 2020, 16:00 UTC'''
* ''Next Facilitator: Mariano''
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T18:03:49Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* '''Next Date: July 20th 2020, 16:00 UTC
* Next Facilitator: Mariano'''
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T17:57:31Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin A. has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Loberto would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin A.
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* Next Date: July 20th 2020, **16:00** UTC
* Next Facilitator: Mariano
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T17:56:31Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
** Nope, we asked at the call. :-)
** Needs concensus for each call
** Let's keep good notes
** Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
** sticking to 16 UTC for now so that everyone can join
** earlier time is more inclusive for south-america
* Last weeks points:
*** More discussion is needed to see the desire to record meeting
*** We'll keep talking about it in Slack
** Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
** Currently working on it, ish..
** Mikael to ping about something he might be able to help it. :-)
** Use social media to reach out
** Get data on active users
** Chagai will implement a test bridge between Slack and one other platform
** Chagai is working on it.
** jitsi instance first up.
** No chat in jitsi :-( We can use Slack!
** VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
** Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
** If you use Codi, keep an eye out for a Best Practices handout
** pending progress
** Efforts are going towards Documentation, so start documenting things done, changes made, etc
** Martin A. will look into creating a Guide for Guides.
** If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
** Maybe we should make a call for more Devs in the next Newsletter
** No space in next newsletter
** Blast short blurb to social media for call for developers /Mikael
** Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
** Sandboxing the time to 10mins or so might be good?
** Focusing on things that weren't done yet or especially those that are blocked would be good
** Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
** Need help with anything? Need help with actually sending the newsletter.
** Mikael can learn this up and will make it a grou-learning session/record screen.
** NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
** Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
** All docs we have are at https://team.trustroots.org (to update content)
** Martin has a list of non-techie tools, somewhere :)
* Team volunteer documentation
** There's a beginning at https://team.trustroots.org
** Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
** A tool for non-techies :-)
** Unlimited users for free
** Team tested Github a bit for non-tech use
** Loberto could be test person for testing out Github for project management
** Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
** Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
** Martin L. would like public permission to police about threads and using right channels for right topics (reminded about #random)
** Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
** good for PR and chance to promote for media? /Chagai
** Technically reduntant work?
** Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
** As an example Airbnb has similar iniatitive for refugees from two years ago
** We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
** there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
*- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin
*- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
** I'm up /Mariano

== Action points and outcomes ==

* Next Date: July 20th 2020, **16:00** UTC
* Next Facilitator: Mariano
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T17:54:56Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

* Hellos and checkin.
* Do we want to record?
* nope, we asked at the call. :-)
* Needs concensus for each call
* Let's keep good notes
* Chagai brings up Jitsi example where they record videos, publish on youtube and since it's so accessible, it's easier for new folks to join in since they see the energy.
* we haven't really changed time for a few weeks.. should we? /Loberto
* sticking to 16 UTC for now so that everyone can join
* earlier time is more inclusive for south-america
* Last weeks points:
* More discussion is needed to see the desire to record meeting
* We'll keep talking about it in Slack
* Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter
* Currently working on it, ish..
* Mikael to ping about something he might be able to help it. :-)
* Use social media to reach out
* Get data on active users
* Chagai will implement a test bridge between Slack and one other platform
* Chagai is working on it.
* jitsi instance first up.
* No chat in jitsi :-( We can use Slack!
* VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.
* Feeling a bit like forward progress is slow but step by step moving forward nevertheless!
* If you use Codi, keep an eye out for a Best Practices handout
* pending progress
* Efforts are going towards Documentation, so start documenting things done, changes made, etc
* Martin A. will look into creating a Guide for Guides.
* If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)
* Maybe we should make a call for more Devs in the next Newsletter
* No space in next newsletter
* Blast short blurb to social media for call for developers /Mikael
* Could be good to keep "call for volunteers" in each newsletter. Just food for thought!
* Do we want to add a review of last week's action points as a standard meeting point? Keeping up with what has been decided and so on. /Martin A.
* Sandboxing the time to 10mins or so might be good?
* Focusing on things that weren't done yet or especially those that are blocked would be good
* Take notes on Codi first whenever possible and then it's faster to go through it.
* This already happened so we can skip....Chagai wanted to talk about creating a jitsi/riot instance at .trustroots.org. Either briefly here or organising a specific meeting if needed.
*
* Next up going out: newsletter/blog-posts/tribes-rename? /Mikael
* Need help with anything? Need help with actually sending the newsletter.
* Mikael can learn this up and will make it a grou-learning session/record screen.
* NDA needed for the access to email addresses when sending the newsletter.
* Audit on tools and resources we have an where is it documented?/Paula
* Until now knowledge just gets passed from person to person; documenting some tools and routines is of course welcome!
* All docs we have are at https://team.trustroots.org (to update content)
* Martin has a list of non-techie tools, somewhere :)
* Team volunteer documentation
* There's a beginning at https://team.trustroots.org
* Many roles there don't provide enough context for starting
* Using project management tool like ClickUp? /Paula
* A tool for non-techies :-)
* Unlimited users for free
* Team tested Github a bit for non-tech use
* Loberto could be test person for testing out Github for project management
* Mikael recoomends just to experiment with tools — it's better if these are free for starters, but in longer term we can even pay reasonable prices for some tools (like we do for development/servers). We're doing similar experimentation with different call tools right now — each week trying something new. :-)
* Martin A. will be able to have a proper look at GitHub and how to adapt it to non-tech people (workflow etc.) in the next week or two.
* Slack Best Pracices according to Loberto =)
* Martin L. would like public permission to police about threads and using right channels for right topics (reminded about #random)
* Everyone is cool with this :-)
* Unique Safehaven status for hosters during Quarantine? /Mariano
* good for PR and chance to promote for media? /Chagai
* Technically reduntant work?
* Bringing this up via social media might be easiest we can do — connecting folks in groups? easiest small thing we can do
* As an example Airbnb has similar iniatitive for refugees from two years ago
* We might little bit late on this — efforts put on social media and connecting with Argentina nomads could be good?
* there are existing projects that work in this area, let's connect with them and spread their awareness via social media
- There's a call for new volunteers Thu/Fri?
- Should we reach out for recent new volunteers that have been a bit active but then dropped out? /Martin
- Reach out to volunteers all the way up to big changes at CouchSurfing
* Your talking point here :)
* Additional topics/questions
* Pick facilitator for next meeting
* I'm up /Mariano

== Action points and outcomes ==

* Next Date: July 20th 2020, **16:00** UTC
* Next Facilitator: Mariano
*
* VA team will go through Volunteer instructions, improve on them and create a volunteer guide of sorts.
* Two
* Three

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T17:08:41Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

== Action points and outcomes ==

* Next Date: July 20th 2020, **16:00** UTC
* Next Facilitator: Mariano

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T17:08:13Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

== Action points and outcomes ==

Next Date: July 20th 2020, **16:00** UTC
Next Facilitator: Mariano

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T17:00:13Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present: Chagai, Loberto, Mariano, Martin A., Michael, Mikael, Paula, Shawn

== Agenda ==

== Action points and outcomes ==

Next Date: July 20th 2020, **16:00** UTC
Next Facilitator: You?

Meeting Minutes/2020-07-13 Regular Meeting

2020-07-13T16:58:17Z

Lemoert: Created page with "= Trustroots Meeting = * Date: 2020-07-13 '''16:00''' UTC * Facilitator: Loberto * Present: == Agenda == == Action points and outcomes == Next Date: July 20th 2020, **16..."

= Trustroots Meeting =

* Date: 2020-07-13 '''16:00''' UTC
* Facilitator: Loberto
* Present:

== Agenda ==

== Action points and outcomes ==

Next Date: July 20th 2020, **16:00** UTC
Next Facilitator: You?

Meeting Minutes/2020-07-09 AhoyParty v2

2020-07-09T18:12:08Z

Lemoert: Created page with "= Trustroots AhoyParty Meeting = * Date: 2020-07-09 '''15:00''' UTC * Facilitator: Loberto/Martin A. * Notes: Martin A. + Everyone * Present: Chagai, Loberto, Martin A., Shaw..."

= Trustroots AhoyParty Meeting =

* Date: 2020-07-09 '''15:00''' UTC
* Facilitator: Loberto/Martin A.
* Notes: Martin A. + Everyone
* Present: Chagai, Loberto, Martin A., Shawn, Stove, Paula

== Agenda ==

* Review previous Action Points:
** √ Confirm with Mikael which roles needs an NDA
*** We'd want to keep this information (and the welcome message etc.) in a more permanent place than Slack as well. /Martin A.
*** Support, database access, GitHub owners etc. Not all too common.
** √ Welcome message to be copied and pasted by VA for the meantime
*** Confirm with Mikael about Greetbot implementation, work with copy-paste in the meantime if this takes a while.
*** VAs to establish/foster family-like atmosphere
** √ Loberto to write welcome message for support
*** Todo in the near future.
** List down the recurring meeting schedules
*** Currently only weekly and support (+ VA) I think. We could try to help Mikael organise the biweekly tech call. /Martin A.
*** Confirm meeting schedules and create a doc on it
** Ascertain that there is only one channel of joining as volunteer
*** Not sure we can (or want to) prevent people from simply joining the Slack workspace. Sending an email is one extra step that is unnecessary for people who are somewhat tech savvy. /Martin A.
*** How to deal with volunteers that are unfamiliar with Slack to avoid losing them. Perhaps an addition to the support message for those people. Would be good to have a Slack walkthrough in general.
*** There's more or less only one channel as is, at lease in practice
** Include guidelines on proper onboarding for volunteers per area
*** Perhaps a questionnaire to discover volunteer abilities.
*** Might add on more work for VA's than necessary with a PM structure/Martin A.
*** We're already working on it with #AreaChampions, ish /Loberto
*** We can look into implementing a questionnaire while continuing this process.
*** Volunteer database with skills listed
*** Reconnect with inactive volunteers to check on them and give them updates/Shawn
*** Map out volunteers per area for VAs to know / area champion /loberto
*** Volunteer's profile specially for VAs /Loberto
** √ Create separate channel for discussing VA (name to be decided)and for just welcoming volunteers
*** All okay with name. Yes!
** Check for documentation of conventions and tools on different volunteer areas and collate it
*** Wait until PM tool is setup.
*** Decide what are the essential infos that need to be included in Area documentation
* Vol Welcome call: just before Monday call? or Thu/Fri? /Loberto
** Probably better Thu/Fri for now, especially as we want to decide on Monday the 20th :D /Martin A.
* First one Thu/Fri and let's see after. Announce this on Monday Call (write down on the Agenda)
* Mondays could be too Mondays for new volunteers.
* Jitsy etiquette etc. probably a good idea.
* Go Through TO-DO List and name responsible person? /Loberto
** This could be added to the PM tool later, with responsible person etc. Probably easier then than now. /Martin A.
** Migrate to GitHub projects all the ToDo list /Loberto
** Paula (with Loberto) move the To-Do list from the Ahoy's codi, and actions points from this meeting
* Project Mgmt tool (Trello, GutHub project boards, Wiki, ?)
** I could set up a test project so we can see how it looks on the different platforms. Would perhaps avoid Trello to not add a new tool. /Martin A.
*** This would be after publishing the newsletter and relevant blog posts, so second half of the month. If anybody wants to do it sooner, feel free to do so :) /Martin A.
*** Already started project board on Github, needs polishing/Paula
* Thoughts and comments on the Meeting Minutes walk-through (as standard for volunteer docs.) /Martin A.
** Ref: https://codi.kanthaus.online/archivingminutes
*** Martin A. will create a walkthrough for how to create guides based on this and the Translation guide.
* Write minutes, move unresolved action points forward, upload to Wiki.
** We didn't talk about this, but Martin said he would take care of it tonight. =)
* Areas for this Codi: Agenda, Action Points, ADD TO PROJECT BOARD, notes /Lobero

Notes:
* Both retaining volunteers when they start as well as avoiding them to fall away after a month or two.
* Creating a humane side to volunteering important to keep volunteers active and interested.

== Action points and outcomes ==

* NDA's aren't that commonly needed and already requested when needed.
* Ask Mikael again about removing obsolete add-ons on Slack so we can add the Greetbot and then evaluate how it works.
* Loberto will write a welcome message for support.
* Create a document with short information of recurring meetings and a link to the minutes page(s).
* In developing #AreaChampions we may want to create a questionnaire to get a better overview of people's skills.
** Shawn would be happy to take care of this when implemented.
* We would want a system to reconnect with inactive volunteers and see if there's some way we can reactivate them. (Without pushing, of course.)
* When the PM tool is set up we will organise the documents to create as walkthroughs for our different tools.
** For now we will try setting things up on GitHub and see how that works out. Under "Community" for now but might want a name change.
** We will also shift over the current to-do list there and organise things better than in the pad. Paula and Loberto in charge of that.
** Martin A. will create a guide to creating guides.
* We will try a new volunteer welcome call on the week following Monday the 20th of July, announcing it on the Monday meeting.
** Creating a summary of things to mention such as Videocall etiquette etc. a good idea.
* In addition to welcoming new volunteers we will later on want to look into ways to improve volunteer retaining after a month or two.
** An important aspect is to create a humane feeling to volunteering so that people feel connected to the group and the project.

Meeting Minutes/2020-07-02 AhoyParty v1

2020-07-04T14:38:27Z

Lemoert:

= Trustroots AhoyParty Meeting =

* Date: 2020-07-02 '''14:00''' UTC
* Facilitator: Loberto, Martin A. (+others later on?)
* Notes: Martin A. + joint effort
* Present: Loberto, Martin A., Michael, Paula, Stove

== Minutes ==

*New volunteer meeting second half of July, check again on weekly meeting the 20th
**Open for anybody new who wants to join and have questions
**Is there a way to contact recent volunteers
**Create ongoing list of new volunteers to not contact everybody continuously

*Standard message for new people from support when they are added to slack.
**Loberto will have a look at it and bring things forward.

*Divide the Slack channel to have one for welcoming new volunteers and their quesions and another for discussion the role of the VAs.
**AhoyParty for welcoming people
**VA_discussion/VA_channel for discussions (set to #va_secret_lab)

*In the future there will be an async tool which can be used for project management. This should not necessarily affect the progress of VA preparations though as we can do it in pads etc. and then gather everything in the async tool.

== Action points and outcomes ==

*Confirm with Mikael which roles needs an NDA
*Welcome message to be copied and pasted by VA for the meantime
*Loberto to write welcome message for support
*Check for documentation of conventions and tools on different volunteer areas and collate it
*List down the recurring meeting schedules
*Ascertain that there is only one channel of joining as volunteer
*Include guidelines on proper onboarding for volunteers per area
*Create separate channel for discussing VA (name to be decided)and for just welcoming volunteers

Meeting Minutes/2020-07-02 AhoyParty v1

2020-07-04T09:34:06Z

Lemoert:

= Trustroots AhoyParty Meeting =

* Date: 2020-07-02 '''14:00''' UTC
* Facilitator: Loberto, Martin A. (+others later on?)
* Notes: Martin A. + joint effort
* Present: Loberto, Martin A., Matt Stove, Michael, Paula

== Minutes ==

*New volunteer meeting second half of July, check again on weekly meeting the 20th
**Open for anybody new who wants to join and have questions
**Is there a way to contact recent volunteers
**Create ongoing list of new volunteers to not contact everybody continuously

*Standard message for new people from support when they are added to slack.
**Loberto will have a look at it and bring things forward.

*Divide the Slack channel to have one for welcoming new volunteers and their quesions and another for discussion the role of the VAs.
**AhoyParty for welcoming people
**VA_discussion/VA_channel for discussions (set to #va_secret_lab)

*In the future there will be an async tool which can be used for project management. This should not necessarily affect the progress of VA preparations though as we can do it in pads etc. and then gather everything in the async tool.

== Action points and outcomes ==

*Confirm with Mikael which roles needs an NDA
*Welcome message to be copied and pasted by VA for the meantime
*Loberto to write welcome message for support
*Check for documentation of conventions and tools on different volunteer areas and collate it
*List down the recurring meeting schedules
*Ascertain that there is only one channel of joining as volunteer
*Include guidelines on proper onboarding for volunteers per area
*Create separate channel for discussing VA (name to be decided)and for just welcoming volunteers

Meeting Minutes/2020-07-02 AhoyParty v1

2020-07-04T09:30:01Z

Lemoert:

= Trustroots AhoyParty Meeting =

* Date: 2020-07-02 '''14:00''' UTC
* Facilitator:
* Notes:
* Present:

== Minutes ==

*New volunteer meeting second half of July, check again on weekly meeting the 20th
**Open for anybody new who wants to join and have questions
**Is there a way to contact recent volunteers
**Create ongoing list of new volunteers to not contact everybody continuously

*Standard message for new people from support when they are added to slack.
**Loberto will have a look at it and bring things forward.

*Divide the Slack channel to have one for welcoming new volunteers and their quesions and another for discussion the role of the VAs.
**AhoyParty for welcoming people
**VA_discussion/VA_channel for discussions (set to #va_secret_lab)

*In the future there will be an async tool which can be used for project management. This should not necessarily affect the progress of VA preparations though as we can do it in pads etc. and then gather everything in the async tool.

== Action points and outcomes ==

*Confirm with Mikael which roles needs an NDA
*Welcome message to be copied and pasted by VA for the meantime
*Loberto to write welcome message for support
*Check for documentation of conventions and tools on different volunteer areas and collate it
*List down the recurring meeting schedules
*Ascertain that there is only one channel of joining as volunteer
*Include guidelines on proper onboarding for volunteers per area
*Create separate channel for discussing VA (name to be decided)and for just welcoming volunteers

Meeting Minutes/2020-07-02 AhoyParty v1

2020-07-02T12:45:40Z

Lemoert: Created page with "= Trustroots AhoyParty Meeting = * Date: 2020-07-02 '''14:00''' UTC * Facilitator: * Notes: * Present: == Minutes == == Action points and outcomes =="

= Trustroots AhoyParty Meeting =

* Date: 2020-07-02 '''14:00''' UTC
* Facilitator:
* Notes:
* Present:

== Minutes ==

== Action points and outcomes ==

Meeting Minutes/2020-06-29 Regular Meeting

2020-06-29T17:28:04Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-06-29 '''18:00''' UTC+2/CEST
* Facilitator: Martin A.
* Present: Chagai, Laura, Loberto, Mariano, Martin A., Matt, Mikael, Shawn, Paula

== Agenda ==
* Hellos and checkin
* Update on Volunteer Advocate development /Martin A.
** A new role of people who welcome new volunteers joining, explains them Trustroots and different volunteering tasks, helps them to connect.
** New volunteers needed for the role!
** Current volunteering documentation: https://team.trustroots.org/
** First things:
*** Structure and create introductionary docs around volunteering advocate, and other
*** Create document for welcoming protocol: https://codi.kanthaus.online/ahoyparty?both
*** Slack channel link: https://trustroots.slack.com/archives/C0150LWAHCP
** Would be great if there would be group of people who Welcome new volunteers; make them feel like they're part of something, engage them. Little things like that help people commit better in long run.
* Need to change video chat link, perhaps also time? /Martin A.
** Everyone send suggestions to Slack, Martin can pick one, we can try them out some point randomly during Slack. :-)
* Renaming Tribes discussion /Martin A.
** A summary of the issue can be found here: https://codi.kanthaus.online/renamingtribes
** Shortlist already down to: Circles, Families, Rings
** In async conversation over on Slack, everyone seems to agree about Circles, while "Rings" and "Families" have had both cons/pros. Decided we will go for Circles as a replacement term.
** Google+ was using "Circles"
** Changing the term:
*** Blog post to introduce the change a week prior [Martin]
*** Coding [Mikael can get it started, anyone can feel free to help]
*** Changing all texts all at once
*** Let's not change old blog tests but add a note in old posts about Circles, link to new blog post
*** Mariano would like to thank everyone for taking on and doing this change! Some context from Mariano on the context of the term change:
**** https://en.m.wikipedia.org/wiki/Daniel_Munduruku
**** https://medium.com/@desabafos/o-problema-da-palavra-tribo-5c89af4be369
* https://couchspinner.com
** Mikael made a quick tool for CS profile exports
** Feel free to share in different conversations!
** Matt points out that too easy signup flow from CoushSpinner to Trustroots might bring too many wrong kinda people to try out Trustroots, just like Facebook connection did for Couchsurfing.
*** Valid point! Mikael will follow activity numbers first if it even makes sense
** Chagai could help with adding the profile import feature on Trustroots, could screenshare with Mikael to learn how to implement it.
* We talked about inactive users and about work we did to get reply rates up as well bring user quality more up (more filled profiles, better reply rates) :-)

== Action points and outcomes ==

*Next Date: July 06, 16:00 UTC
*Next Facilitator: You?

** The weekly meeting last week (22nd) was not held due to lacking participation.
** Join the #AhoyParty and help us develop the Volunteer Advocate role!
** We will gather options for new video meeting locations in Slack and then decide for next week. Martin will organise if necessary.
** Tribes will become Circles! Mariano and Martin will work on the blog announcement (help welcome), while Mikael will set up the basics for getting the ball rolling on the actual change.
** Have a look at CouchSpinner (https://couchspinner.com/) and spread the word :)

Meeting Minutes/2020-06-29 Regular Meeting

2020-06-29T17:26:17Z

Lemoert: Created page with "= Trustroots Meeting = * Date: 2020-06-29 '''18:00''' UTC+2/CEST * Facilitator: Martin A. * Present: Chagai, Laura, Loberto, Mariano, Martin A., Matt, Mikael, Shawn, Paula =..."

= Trustroots Meeting =

* Date: 2020-06-29 '''18:00''' UTC+2/CEST
* Facilitator: Martin A.
* Present: Chagai, Laura, Loberto, Mariano, Martin A., Matt, Mikael, Shawn, Paula

== Agenda ==
* Hellos and checkin
* Update on Volunteer Advocate development /Martin A.
* A new role of people who welcome new volunteers joining, explains them Trustroots and different volunteering tasks, helps them to connect.
* New volunteers needed for the role!
* Current volunteering documentation: https://team.trustroots.org/
* First things:
* Structure and create introductionary docs around volunteering advocate, and other
* Create document for welcoming protocol: https://codi.kanthaus.online/ahoyparty?both
* Slack channel link: https://trustroots.slack.com/archives/C0150LWAHCP
* Would be great if there would be group of people who Welcome new volunteers; make them feel like they're part of something, engage them. Little things like that help people commit better in long run.
* Need to change video chat link, perhaps also time? /Martin A.
* Everyone send suggestions to Slack, Martin can pick one, we can try them out some point randomly during Slack. :-)
* Renaming Tribes discussion /Martin A.
* A summary of the issue can be found here: https://codi.kanthaus.online/renamingtribes
* Shortlist already down to: Circles, Families, Rings
* In async conversation over on Slack, everyone seems to agree about Circles, while "Rings" and "Families" have had both cons/pros. Decided we will go for Circles as a replacement term.
* Google+ was using "Circles"
* Changing the term:
* Blog post to introduce the change a week prior [Martin]
* Coding [Mikael can get it started, anyone can feel free to help]
* Changing all texts all at once
* Let's not change old blog tests but add a note in old posts about Circles, link to new blog post
* Mariano would like to thank everyone for taking on and doing this change! Some context from Mariano on the context of the term change:
* https://en.m.wikipedia.org/wiki/Daniel_Munduruku
* https://medium.com/@desabafos/o-problema-da-palavra-tribo-5c89af4be369
* https://couchspinner.com
* Mikael made a quick tool for CS profile exports
* Feel free to share in different conversations!
* Matt points out that too easy signup flow from CoushSpinner to Trustroots might bring too many wrong kinda people to try out Trustroots, just like Facebook connection did for Couchsurfing.
* Valid point! Mikael will follow activity numbers first if it even makes sense
* Chagai could help with adding the profile import feature on Trustroots, could screenshare with Mikael to learn how to implement it.
* We talked about inactive users and about work we did to get reply rates up as well bring user quality more up (more filled profiles, better reply rates) :-)

== Action points and outcomes ==

*Next Date: July 06, 16:00 UTC
*Next Facilitator: You?

** The weekly meeting last week (22nd) was not held due to lacking participation.
** Join the #AhoyParty and help us develop the Volunteer Advocate role!
** We will gather options for new video meeting locations in Slack and then decide for next week. Martin will organise if necessary.
** Tribes will become Circles! Mariano and Martin will work on the blog announcement (help welcome), while Mikael will set up the basics for getting the ball rolling on the actual change.
** Have a look at CouchSpinner (https://couchspinner.com/) and spread the word :)

Torino

2020-06-17T13:46:28Z

Lemoert:

=Guida di Torino/Turin City Guide=
Page under construction
(A generic image would go well there -> and also an image or three in the text below.)
(Perhaps better to keep the whole text bilingual rather than separate, seeing as there will be lists that create unnecessary repetition.)

==Introduction==
==Places to see==
==Museums and galleries==
(You will want information about the Abbonamento Musei here.)
==What to eat==
==Gelato==
==Nightlife==
==Parks==
==Sports/Outdoor==
==Meetups==
==Travel info==
==Emergencies==

=Other languages=

Torino

2020-06-17T11:26:19Z

Lemoert:

=Guida di Torino/Turin City Guide=
Page under construction
(A generic image would go well there -> and also an image or three in the text below.)
(Perhaps better to keep the whole text bilingual rather than separate, seeing as there will be lists that create unnecessary repetition.)

==Introduction==
==Places to see==
==Museums and galleries==
(You will want information about the Abbonamento Musei here.)
==Food==
==Gelato==
==Nightlife==
==Parks==
==Sports/Outdoor==
==Meetups==
==Travel info==
==Emergencies==

Torino

2020-06-17T11:24:12Z

Lemoert: City Guide for Torino/Turin

=Guida di Torino/Turin City Guide=
(Page under construction)
(A generic image would go well there -> and also an image or three in the text below.)
(Perhaps better to keep the whole text bilingual rather than separate, seeing as there will be lists that create unnecessary repetition.)

==Introduction==
==Places to see==
==Food==
==Gelato==
==Nightlife==
==Parks==
==Sports/Outdoor==
==Meetups==
==Travel info==
==Emergencies==

Meeting Minutes/2020-06-15 Regular Meeting

2020-06-15T17:18:41Z

Lemoert: Created page with "= Trustroots Meeting = * Date: 2020-06-15 '''18:00''' UTC+2/CEST * Facilitator: Martin * Present: Chagai, Martin, Michael, Mikael == Agenda == * Hellos and checkin * Create..."

= Trustroots Meeting =

* Date: 2020-06-15 '''18:00''' UTC+2/CEST
* Facilitator: Martin
* Present: Chagai, Martin, Michael, Mikael

== Agenda ==
* Hellos and checkin
* Create page with hello/checkin info? /Martin
** Questions: (What is your current life situation/context? What are you motivated to contribute to trustroots? What do you need from others? What can offer to others?)
** Plenty of answers here already: https://wiki.trustroots.org/en/Meeting_Minutes/2020-05-25_Regular_Meeting
** Julien's answers in Slack
** Mikael will set up something for async conversation in the coming weeks, we'll gather the information there then.
* Volunteer advocate? [Mikael introduce the idea on Slack]
** Person who would welcome new developers(hopefully have a woman as well so women feel more comfortable in the see of men, maybe schedule 1 on 1 video call to make the volunteers feel more comfortable)
** Instead of a list of skills we have; and that participaiting in discussions is equally important(saying your opinion, voting on it, keeping the developers motivated).
* FYI, engineering call poll: https://dudle.inf.tu-dresden.de/tr-dev-call-time-2020/
* Update from the React Native workbench
** Lazy week, Michael at the beach :D
** Needs designs for "empty states" [Mikael can look into this]
* Pick facilitator for next meeting
* Random questions

== Action points and outcomes ==

*Next Date: June 22, 19:00
*Next Facilitator:

** Mikael has set up a poll to check times for the engineering call
** After an async solution has been sorted (in a couple of weeks, by Mikael) we will gather the hello/checkin answer in one spot.
** Michael is at the beach for a lazy week but needs designs for "empty states" [Mikael can look into this]
** We will try to organise a Volunteer Advocate role, Martin will add a brief summary on Slack and we will see where things go.

Meeting Minutes/2020-06-08 Regular Meeting

2020-06-08T20:50:31Z

Lemoert:

= Trustroots Meeting =

* Date: 2020-06-08 '''19:00''' UTC+2/CEST
* Facilitator: Everyone, ish
* Present: Carla, Changai, Michael, Dario, Martin, Gabriel

== 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

== Action points and outcomes ==

*Next Date: June 15, 18:00 (presuming we're alternating 18:00 and 19:00)
*Next Facilitator: Martin? (Not all too trustworthy schedule, if somebody else can it'd be great..)

* The value priorities discussion will be held at a future meeting.
* Alternatives for new Tribes name available in Slack and the pad, discussions as to which one is best suited should be held once a good number of opinions are on the pad.
* Preparing workflows for difficult support cases and potential ways to block a member could be useful. (Is the blocking feature something we're already working on? /Martin)
* It might be an idea to look into something similar to the CS vouching feature in the future.
* Michael is happy to get feedback on the mobile design. Beta likely live in about 2 weeks(!)
* Riot integration should be brought up again in a more tech-specific meeting, preferably with Mikael present as he implemented messages.

Meeting Minutes/2020-06-08 Regular Meeting

2020-06-08T20:37:50Z

Lemoert: Created page with "= Trustroots Meeting = * Date: 2020-06-08 '''19:00''' UTC+2/CEST * Facilitator: Everyone, ish * Present: Carla, Changai, Michael, Dario, Martin, Gabriel == Agenda == * hell..."

= Trustroots Meeting =

* Date: 2020-06-08 '''19:00''' UTC+2/CEST
* Facilitator: Everyone, ish
* Present: Carla, Changai, Michael, Dario, Martin, Gabriel

== 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

== Action points and outcomes ==

Next Date: June 15, 18:00 (presuming we're alternating 18:00 and 19:00)
Next Facilitator: Martin? (Not all too trustworthy schedule, if somebody else can it'd be great..)

* The value priorities discussion will be held at a future meeting.
* Alternatives for new Tribes name available in Slack and the pad, discussions as to which one is best suited should be held once a good number of opinions are on the pad.
* Preparing workflows for difficult support cases and potential ways to block a member could be useful. (Is the blocking feature something we're already working on? /Martin)
* It might be an idea to look into something similar to the CS vouching feature in the future.
* Michael is happy to get feedback on the mobile design. Beta likely live in about 2 weeks(!)
* Riot integration should be brought up again in a more tech-specific meeting, preferably with Mikael present as he implemented messages.