https://wiki.trustroots.org/w/api.php?action=feedcontributions&user=Loberto&feedformat=atomWiki.trustroots.org - User contributions [en]2024-03-29T01:19:22ZUser contributionsMediaWiki 1.39.2https://wiki.trustroots.org/w/index.php?title=Safety/2020-07-31&diff=24294Safety/2020-07-312020-08-01T14:24:16Z<p>Loberto: /* Trustroots Safety Team Meeting */</p>
<hr />
<div>= Trustroots Safety Team Meeting =<br />
<br />
Date: 2020-07-31 15:00 UTC / 17:00 CEST <br />
<br />
Facilitator: Philipp <br />
<br />
Participants: Philipp, Ludo, Stove, Loberto<br />
<br />
== Agenda ==<br />
(we mixed the Agenda with the Note taking)<br />
<br />
* how is everyone doing in their life, what does everyone do, how is the energy level? /philipp done<br />
** Loberto: good, thursday back to Europe. not available end next week + weekend. would like more communication about what is happening, status updates (volunteer advocates stuff). Support is quite good.<br />
** Ludo: exams finished, moving. A bit confused after absence on Trustroots, taking back initiative and understanding better now. Strange feeling about volunteer getting into conversations, didn't understand this presence. Trying to be more active, but hard.<br />
** Stove: friends coming over and living with Stove. No access to zendesk yet, more focus on facebook, 2 support request on fb, otherwise pretty well<br />
** Philipp: …forgot to take notes. Pretty good, some real life projects, wants to limit screen time or use it well at least. Feeling great within support team.<br />
<br />
* discuss Rules: "no money" and "no abuse" (https://github.com/Trustroots/trustroots/pull/1468) /loberto done<br />
** not sure if the new rules have been edited in place. if not, make it happen soon<br />
** we are taking action.<br />
<br />
* Loberto need to discuss some tickets: done<br />
** Ticket 3514, 3534, repeated user, maybe same user -->3560, 3489, 3515<br />
<br />
* any specific questions about issues that better be discussed in the big round (we can always form a small task force which takes care of it, too) /philipp done<br />
<br />
* ###usernamehidden### -> paula answered a ticket from them. Ludo has seen they have three profiles in a lot of different cities in Italy. Is sending a lot of messages to people. Ludo was considering to write to them privately to check it out if they are asking for money or something<br />
** Loberto: if several profiles -> fake profile, no money = also breach of rules. Suggests to have general guidelines for cases like this. Create guidelines to guide our personal judgement<br />
** Stove: agrees. also different issue: how do we react to things we see ourselves and not get reported.<br />
** Philipp: why not?<br />
** Stove: support people would report people via the report button as well, official way<br />
** Loberto: ticket should then be handled by another person on support maybe?<br />
** if a support person is personally involved by something, they shall not take the ticket.<br />
<br />
* have something to link to the rules when we suspend an account or similar?<br />
** Loberto suggests longer terms and conditions more explanatory as long term goal.<br />
** Stove knows someone who is proficient from a legal point of view<br />
<br />
* with just info/feedback tickets, do we have to do something? or simply mark them as closed? (either feedback that we pass on, or "yeah, I'm doing great" replies to the initial emails) /Loberto done<br />
** if we copy/paste them on #userfeedback, we should put an internal note about it, so we don't repeat it.<br />
** Ludo bases her response on her feeling, depends on the message. If there is a question, she answers, also if it is a passionate message, otherwise just closes the issue.<br />
** Stove hasn't answered any tickets, agrees with Ludo.<br />
** Philipp: if enough energy + only short reply with no relevant feedback, try to just say thanks for message and introduce support team and tell person they can always message us<br />
** Ludo: if she sees potential (recently: person saying they would like to meet other people around them: Ludo told about her own experience. Tried to encourage to also interact aside hosting/being hosted) replies with her own experience.<br />
** Let's put the info in a hidden note on ZD if we posted a feedback to #userfeedback :)<br />
<br />
* proposal on meeting minutes: add long term goals area, max 3 goals? (philipp)<br />
** if do do, should we decide on a follow up process also? /loberto<br />
** Stove, Ludo, Philipp agree that it is good to have long-term-goals. Stove asks: is it for the team or for individuals? Where do we record them?<br />
** Ludo: brainstorm -> pick three. fears we're not actually working on them every meeting. Maybe once a month? Philipp: Maybe every three months? Could ask Noah to facilitate this kind of reflection? Ludo: also over several meetings?<br />
** Stove: delegate responsibility for Long term goals to _area champion_ for #support (concept of area champion was introduced last thursday on the volunteer welcome call.)<br />
** Loberto added note: if we have goals, they would need a date of accomplishment, or of update. We can do short update on every meeting also.<br />
<br />
** Stove says that they might apply structures we elaborate here to the facebook moderation group as well<br />
<br />
* in ZD, Merging user to connect FB to an email address /Loberto done<br />
** it's not working perfectly; so Stove will coordinate with FB mods to ask for username/email to open tickets.<br />
<br />
<br />
== Action items: ==<br />
<br />
* Stove needs Zendesk access. WIP with Mikael (mattstove@protonmail.com). No room for more agents. Check if we can add an extra agent seat.<br />
* Loberto takes discussion on slack #support: create guidelines for support team to guide our judgement<br />
* Loberto will send Philipp a text: "no money" and "no abuse" (https://github.com/Trustroots/trustroots/pull/1468), Philipp will make it appear on trustroots<br />
* Philipp will ask Mikael if messages in admin view can be sorted by time<br />
* there is a bug about unread messages with someone who is shadowbanned -> Philipp will talk to Mikael<br />
* ask Mikael for tool that automatically notifies us when someone creates yet another profile with a name of an account which is suspended. Loberto tries to find the slack-convo which we had about that before (?)<br />
* Philipp will help Stove how to create a manual ticket on Zendesk when people write us on facebook (we need to ask them for their email and trustroots username first though). Need to wait until Stove gets ZD access.<br />
* Ludo will contact Noah about Long term goals idea. Opinion, can Noah facilitate this?</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Safety/2020-07-31&diff=24293Safety/2020-07-312020-08-01T14:22:05Z<p>Loberto: Created page with "= Trustroots Safety Team Meeting = Date: 2020-07-31 15:00 UTC / 17:00 CEST Facilitator: Philipp Participants: Philipp, Ludo, Stove, Loberto == Agenda == (we mixed the Ag..."</p>
<hr />
<div>= Trustroots Safety Team Meeting =<br />
<br />
Date: 2020-07-31 15:00 UTC / 17:00 CEST <br />
<br />
Facilitator: Philipp <br />
<br />
Participants: Philipp, Ludo, Stove, Loberto<br />
<br />
== Agenda ==<br />
(we mixed the Agenda with the Note taking)<br />
<br />
* how is everyone doing in their life, what does everyone do, how is the energy level? /philipp done<br />
** Loberto: good, thursday back to Europe. not available end next week + weekend. would like more communication about what is happening, status updates (volunteer advocates stuff). Support is quite good.<br />
** Ludo: exams finished, moving. A bit confused after absence on Trustroots, taking back initiative and understanding better now. Strange feeling about volunteer getting into conversations, didn't understand this presence. Trying to be more active, but hard.<br />
** Stove: friends coming over and living with Stove. No access to zendesk yet, more focus on facebook, 2 support request on fb, otherwise pretty well<br />
** Philipp: …forgot to take notes. Pretty good, some real life projects, wants to limit screen time or use it well at least. Feeling great within support team.<br />
<br />
* discuss Rules: "no money" and "no abuse" (https://github.com/Trustroots/trustroots/pull/1468) /loberto done<br />
** not sure if the new rules have been edited in place. if not, make it happen soon<br />
** we are taking action.<br />
<br />
* Loberto need to discuss some tickets: done<br />
** Ticket 3514, 3534, repeated user, maybe same user -->3560, 3489, 3515<br />
<br />
* any specific questions about issues that better be discussed in the big round (we can always form a small task force which takes care of it, too) /philipp done<br />
<br />
* ###usernamehidden### -> paula answered a ticket from them. Ludo has seen they have three profiles in a lot of different cities in Italy. Is sending a lot of messages to people. Ludo was considering to write to them privately to check it out if they are asking for money or something<br />
** Loberto: if several profiles -> fake profile, no money = also breach of rules. Suggests to have general guidelines for cases like this. Create guidelines to guide our personal judgement<br />
** Stove: agrees. also different issue: how do we react to things we see ourselves and not get reported.<br />
** Philipp: why not?<br />
** Stove: support people would report people via the report button as well, official way<br />
** Loberto: ticket should then be handled by another person on support maybe?<br />
** if a support person is personally involved by something, they shall not take the ticket.<br />
<br />
* have something to link to the rules when we suspend an account or similar?<br />
** Loberto suggests longer terms and conditions more explanatory as long term goal.<br />
** Stove knows someone who is proficient from a legal point of view<br />
<br />
* with just info/feedback tickets, do we have to do something? or simply mark them as closed? (either feedback that we pass on, or "yeah, I'm doing great" replies to the initial emails) /Loberto done<br />
** if we copy/paste them on #userfeedback, we should put an internal note about it, so we don't repeat it.<br />
** Ludo bases her response on her feeling, depends on the message. If there is a question, she answers, also if it is a passionate message, otherwise just closes the issue.<br />
** Stove hasn't answered any tickets, agrees with Ludo.<br />
** Philipp: if enough energy + only short reply with no relevant feedback, try to just say thanks for message and introduce support team and tell person they can always message us<br />
** Ludo: if she sees potential (recently: person saying they would like to meet other people around them: Ludo told about her own experience. Tried to encourage to also interact aside hosting/being hosted) replies with her own experience.<br />
** Let's put the info in a hidden note on ZD if we posted a feedback to #userfeedback :)<br />
<br />
* proposal on meeting minutes: add long term goals area, max 3 goals? (philipp)<br />
** if do do, should we decide on a follow up process also? /loberto<br />
** Stove, Ludo, Philipp agree that it is good to have long-term-goals. Stove asks: is it for the team or for individuals? Where do we record them?<br />
** Ludo: brainstorm -> pick three. fears we're not actually working on them every meeting. Maybe once a month? Philipp: Maybe every three months? Could ask Noah to facilitate this kind of reflection? Ludo: also over several meetings?<br />
** Stove: delegate responsibility for Long term goals to _area champion_ for #support (concept of area champion was introduced last thursday on the volunteer welcome call.)<br />
** Loberto added note: if we have goals, they would need a date of accomplishment, or of update. We can do short update on every meeting also.<br />
<br />
** Stove says that they might apply structures we elaborate here to the facebook moderation group as well<br />
<br />
* in ZD, Merging user to connect FB to an email address /Loberto done<br />
** it's not working perfectly; so Stove will coordinate with FB mods to ask for username/email to open tickets.<br />
<br />
<br />
== Action items: ==<br />
<br />
* Stove needs Zendesk access. WIP with Mikael (mattstove@protonmail.com), maybe Loberto can add Stove already. No room for more agents. Check if we can add an extra agent seat.<br />
* Loberto takes discussion on slack #support: create guidelines for support team to guide our judgement<br />
* Loberto will send Philipp a text: "no money" and "no abuse" (https://github.com/Trustroots/trustroots/pull/1468), Philipp will make it appear on trustroots<br />
* Philipp will ask Mikael if messages in admin view can be sorted by time<br />
* there is a bug about unread messages with someone who is shadowbanned -> Philipp will talk to Mikael<br />
* ask Mikael for tool that automatically notifies us when someone creates yet another profile with a name of an account which is suspended. Loberto tries to find the slack-convo which we had about that before (?)<br />
* Philipp will help Stove how to create a manual ticket on Zendesk when people write us on facebook (we need to ask them for their email and trustroots username first though). Need to wait until Stove gets ZD access.<br />
* Ludo will contact Noah about Long term goals idea. Opinion, can Noah facilitate this?</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-27_Regular_Meeting&diff=24291Meeting Minutes/2020-07-27 Regular Meeting2020-07-27T19:46:09Z<p>Loberto: </p>
<hr />
<div>= Minute Weekly Call Monday July 27th 2020 ==<br />
<br />
'''Date:''' 2020-07-27 **16:00** UTC<br />
<br />
'''Facilitator:''' Loberto<br />
<br />
'''Present:''' Stove, David, Jans, Shawn, Martin A, Chagai, Loberto<br />
<br />
== Agenda ==<br />
* Hellos and check-in.<br />
** Jans and David joined for the first time =)<br />
* Last week's Action Points:<br />
** In promoting events, Shawn wants to create an "Event Tool Kit" as resource to create events and put it on wiki.<br />
*** in parallel, we need to find the power user, potential ambassadors, event organizer, etc.<br />
*** Martin A. and Ludo created an event in Torino. They can collaborate with their experience.<br />
* Martin A. is looking into figuring out how to send newsletters. He needs to get access to Mailtrain and find how the last one was sent. <br />
** Loberto will see if he can help, if not we will ping Mikael or Guaka.<br />
* Chagai will upload the video of the call from the 20th to Google Drive as soon as he has access.<br />
* Question for Guaka? There was a short list but he couldn't make it the call, so we will create a AMI Thread for him.<br />
<br />
* Areas of work, Stove would like feedback on the list:<br />
** Currently: Design, Development, Support, Translation, SocialMedia, VA, & (F,L,S), Communication (blog and newsletter) <br />
** (F,L,S) would be good to have profesional on these areas in case of future need.<br />
** We may need an area for Ambassadors. <br />
** Loberto pointed to https://codi.kanthaus.online/ahoyparty?view for a longer list.<br />
* Chagai wants to make more people aware of use of tinyurls and the time zone websites specifically.<br />
** tinyurls could be useful to save space in the "about" for the channels.<br />
** the general view is to use UTC for all time<br />
* It was pointed out that IF/WHEN the community grows, we may need to start doing 2 meetings a week, or going back to rotating the time of them.<br />
<br />
== Action Points ==<br />
* None really...</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-27_Regular_Meeting&diff=24290Meeting Minutes/2020-07-27 Regular Meeting2020-07-27T19:41:43Z<p>Loberto: </p>
<hr />
<div>= Minute Weekly Call Monday July 27th 2020 ==<br />
<br />
'''Date:''' 2020-07-27 **16:00** UTC<br />
<br />
'''Facilitator:''' Loberto<br />
<br />
'''Present:''' Stove, David, Jans, Shawn, Martin A, Chagai, Loberto<br />
<br />
== Agenda ==<br />
* Hellos and check-in.<br />
** Jan and David joined for the first time =)<br />
* Last week's Action Points:<br />
** In promoting events, Shawn wants to create an "Event Tool Kit" as resource to create events and put it on wiki.<br />
*** in parallel, we need to find the power user, potential ambassadors, event organizer, etc.<br />
*** Martin A. and Ludo created an event in Torino. They can collaborate with their experience.<br />
* Martin A. is looking into figuring out how to send newsletters. He needs to get access to Mailtrain and find how the last one was sent. <br />
** Loberto will see if he can help, if not we will ping Mikael or Guaka.<br />
* Chagai will upload the video of the call from the 20th to Google Drive as soon as he has access.<br />
* Question for Guaka? There was a short list but he couldn't make it the call, so we will create a AMI Thread for him.<br />
<br />
* Areas of work, Stove would like feedback on the list:<br />
** Currently: Design, Development, Support, Translation, SocialMedia, VA, & (F,L,S), Communication (blog and newsletter) <br />
** (F,L,S) would be good to have profesional on these areas in case of future need.<br />
** We may need an area for Ambassadors. <br />
** Loberto pointed to https://codi.kanthaus.online/ahoyparty?view for a longer list.<br />
* making more people aware of use of tinyurls and the time zone websites specifically./Chagai<br />
** tinyurls could be useful to save space in the "about" for the channels.<br />
** the general view is to use UTC for all time<br />
* It was pointed out that IF/WHEN the community grows, we may need to start doing 2 meetings a week, or going back to rotating the time of them.<br />
<br />
== Action Points ==<br />
* None really...</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-27_Regular_Meeting&diff=24289Meeting Minutes/2020-07-27 Regular Meeting2020-07-27T19:39:43Z<p>Loberto: Minute for TR Weekly meeting 20200727</p>
<hr />
<div>= Minute Weekly Call Monday July 27th 2020 ==<br />
<br />
'''Date:''' 2020-07-27 **16:00** UTC<br />
<br />
'''Facilitator:''' Loberto<br />
<br />
'''Present:''' Stove, David, Jans, Shawn, Martin A, Chagai, Loberto<br />
<br />
== Agenda ==<br />
* Hellos and check-in.<br />
** Jan and David joined for the first time =)<br />
* Last week's Action Points:<br />
** In promoting events, Shawn wants to create an "Event Tool Kit" as resource to create events and put it on wiki.<br />
*** in parallel, we need to find the power user, potential ambassadors, event organizer, etc.<br />
*** Martin A. and Ludo created an event in Torino. They can collaborate with their experience.<br />
* Martin A. is looking into figuring out how to send newsletters. He needs to get access to Mailtrain and find how the last one was sent. <br />
** Loberto will see if he can help, if not we will ping Mikael or Guaka.<br />
* Chagai will upload the video of the call from the 20th to Google Drive as soon as he has access.<br />
* Question for Guaka? There was a short list but he couldn't make it the call, so we will create a AMI Thread for him.<br />
<br />
* Areas of work, Stove would like feedback on the list:<br />
** Currently: Design, Development, Support, Translation, SocialMedia, VA, & (F,L,S), Communication (blog and newsletter) <br />
** (F,L,S) would be good to have profesional on these areas in case of future need.<br />
** We may need an area for Ambassadors. <br />
** Loberto pointed to https://codi.kanthaus.online/ahoyparty?view for a longer list.<br />
* making more people aware of use of tinyurls and the time zone websites specifically./Chagai<br />
** tinyurls could be useful to save space in the "about" for the channels.<br />
** the general view is to use UTC for all time<br />
* It was pointed out that IF/WHEN the community grows, we may need to start doing 2 meetings a week, or going back to rotating the time of them.</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-20_Regular_Meeting&diff=24288Meeting Minutes/2020-07-20 Regular Meeting2020-07-27T19:39:01Z<p>Loberto: </p>
<hr />
<div>{{weekly-meeting}}<br />
Date: 2020-07-20 **16:00** UTC<br />
<br />
Facilitator: Mariano, Loberto<br />
<br />
Present: Ludo, Chagai, Mariyano, Loberto, Phillip, Shawn, Stove, [[User:Guaka|guaka]] ([[User talk:Guaka|talk]])<br />
<br />
== Agenda ==<br />
<br />
* New(ish) Volunteers Welcome Call - THURSDAY 23RD, 17:00 utc / Loberto<br />
** Please come!<br />
** Invite anyone you know is on slack<br />
* Talk about importance of reference base system /Shawn&Chagai<br />
** Chagai is taking care of it as his top priority. He' welcome to anyone's help. Philipp is available to assist and test In the upcoming week.<br />
* Live or recorded Content from time to time elaborated for the community /Mariano<br />
** The idea is to create content for a Youtube channel for the community. So someone who is ok for being on camera, people could do a video summary of the Weekly call. Or other types of content; e.g. screencast of coding, conversation about travels, how to improve trustroots, etc.<br />
** We will start a conversation about on Slack. MARIANO takes point on this<br />
*** Look at what Matrix opentechwillsaveusall and Jitsi (bi)weekly call are doing on YouTube<br />
<br />
== Action Points ==<br />
<br />
* This call was recorded! Chagai need to find a place to host it and share it with everyone.<br />
* STILL need a discussion on protocol for recording video calls. (interest, how-to, and also check for consensus in each call).<br />
* 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.<br />
* Mikael will blast a short blurb to social media for call for developers<br />
* Need more people to learn how to send newsletters. A couple of people should know how to do it to not create dependency/stress.</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-20_Regular_Meeting&diff=24215Meeting Minutes/2020-07-20 Regular Meeting2020-07-21T13:49:58Z<p>Loberto: VA Meeting agenda 20200720</p>
<hr />
<div><br />
= Trustroots Weekly Meeting =<br />
<br />
Date: 2020-07-20 **16:00** UTC<br />
Facilitator: Mariano, Loberto<br />
Present: Ludo, Chagai, Mariyano, Loberto, Phillip, Shawn, Stove, Kasper/Guaka<br />
<br />
= Agenda =<br />
<br />
* New(ish) Volunteers Welcome Call - THURSDAY 23RD, 17:00 utc / Loberto<br />
** Please come!<br />
** Invite anyone you know is on slack<br />
* Talk about importance of reference base system /Shawn&Chagai<br />
** Chagai is taking care of it as his top priority. He' welcome to anyone's help. Philipp is available to assist and test In the upcoming week.<br />
* Live or recorded Content from time to time elaborated for the community /Mariano<br />
** The idea is to create content for a Youtube channel for the community. So someone who is ok for being on camera, people could do a video summary of the Weekly call. Or other types of content; e.g. screencast of coding, conversation about travels, how to improve trustroots, etc.<br />
** We will start a conversation about on Slack. MARIANO takes point on this<br />
*** Look at what Matrix opentechwillsaveusall and Jitsi (bi)weekly call are doing on YouTube<br />
<br />
= Action Points =<br />
* This call was recorded! Chagai need to find a place to host it and share it with everyone.<br />
* STILL need a discussion on protocol for recording video calls. (interest, how-to, and also check for consensus in each call).<br />
* 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.<br />
* Mikael will blast a short blurb to social media for call for developers<br />
* Need more people to learn how to send newsletters. A couple of people should know how to do it to not create dependency/stress.</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-17_VA_Meeting&diff=24214Meeting Minutes/2020-07-17 VA Meeting2020-07-17T18:26:33Z<p>Loberto: VA Meeting agenda mid july</p>
<hr />
<div>= Trustroots VA Meeting =<br />
<br />
Date: 17/07/2020 : 7 UTC<br />
Facilitator: ?<br />
Present: Stove, Loberto<br />
<br />
== Agenda ==<br />
<br />
* We should already send out invites by today and also if we already have the list (do we post it also on FB in case some are interested)<br />
** FRIST WE NEED A DATE AND TIME<br />
** make list of new volunteers: from everyone joining #general since May 14th<br />
** Message in General, tagging the channel, and tagging everyone from "new vol list"<br />
** FRIDAY Post on FB and Reddit about it, inviting new vol.<br />
** TUESDAY send EMAIL to people that joined VA_secret lab (previously AhoyParty) --> ask how to use the NL mailing system.<br />
* Where do we do the call? / Paula<br />
** BBB<br />
** if we happen to have TOO MANY people, we can go to Zoom or Google Meet.<br />
* Basic guide on how to Slack and do we get them on Clickup as well? / Paula<br />
** https://codi.kanthaus.online/how-to-slack<br />
** Loberto likes ClickUp, we need more people involved. <br />
* We need to identify the main contacts in all areas but seems some are away./ Paula<br />
** First we need a proper list of areas /Loberto<br />
** we can assign to the ones missing.<br />
* Loberto changed the name of the pad. /Loberto <br />
** Edited https://codi.kanthaus.online/ahoyparty for info for New Vols, and moved info for VAs to https://codi.kanthaus.online/VA_Permanent_Notes<br />
* Welcome Call next week, do we have anything prepared?<br />
** https://github.com/orgs/Trustroots/projects/3<br />
** https://app.clickup.com/3715923/v/l/li/7422502?pr=3797330<br />
<br />
* Some points were moved to next week, because of lack of participants.<br />
<br />
<br />
== Action points and outcomes (ACTION POINTS NEED TO HAVE AN OWNER/IN CHARGE) ==<br />
<br />
* Prepare WELCOME CALL <br />
** set a date<br />
*** message #general --> tag all people in New Vols List<br />
*** Post on FB and Reddit, with open invite (no link yet)<br />
*** ? Send email to members of AhoyParty (and VA Lab)<br />
** Agenda<br />
** questionnaire<br />
* List of New Vols since May 14th (Loberto)<br />
* Make proper list of Areas, with its Champion</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-06_Regular_Meeting&diff=24163Meeting Minutes/2020-07-06 Regular Meeting2020-07-06T21:29:21Z<p>Loberto: /* Agenda */</p>
<hr />
<div>= Trustroots Meeting =<br />
<br />
* Date: 2020-07-06 '''16:00''' UTC<br />
* Facilitator: Loberto<br />
* Present: Chagai, Stove, Pramus, Loberto, Dario, Shawn, Mariano, Michael, Paula, Philipp (maybe someone else...)<br />
<br />
== Agenda ==<br />
* Hellos and checkin<br />
* Raising awareness to recording our calls - especially the tech one's but also the discussions and even the chit chat - only if everyone on the call is comfortable with it of course! /Chagai<br />
** Concerns were raised regarding privacy, both personal (voice, face, room, etc) and professional (taking ideas from the recording to another platform)<br />
** ---> it was agreed to move to Slack for further conversation <br />
<br />
* using Kialo.com for big discussion with conflicting ideas<br />
** https://www.kialo.com/<br />
** pros: looks like a good platform for high-level discussion, organized and friendlier than GitHub<br />
** cons: too much branching on different tools; making conversations longer without reaching a point; being it an external, closed-source, SaaS platform.<br />
** If there is nothing specific about Kialo, maybe considering going back to the Discourse instance that existed 2 years ago.<br />
** https://support.kialo.com/hc/en-us/articles/115003878065-Published-vs-Private-Discussions<br />
<br />
* thoughts on -theoretically- buying Couchsurfing for the user database (making a petition, setting up a donation option, etc.) /Chagai - Shawn<br />
** Shawn heard something in some circles, just wanting to open the discussion and puting the idea in the open.<br />
** If Couchsurfing goes down the drain, we could theoretically try to do a fundraiser to buy out Couchsurfing and get access to their user database. Current value is 23 Million Dollars (that’s what was invested in it at some point)<br />
<br />
* promoting events on trustroots /Chagai - Shawn<br />
** finding power user to find people to promote events /Shawn<br />
** Adrian think of giving badges (gamification) - not only restricted to events, it can be a more general functionality also used for perks (10,50,100 etc. people hosted) or profile completion % /Adrian<br />
** Making "best practices" to organize events. <br />
** Finding people already organizing event and get feedback from them (tools they would want, etc)<br />
** there once were trustroots stickers. We could find them and distribute the design (is it open?)<br />
** Writing info for next Newsletter<br />
** Shawn will start the doc and convo<br />
<br />
* discuss one last time the bridging to other platforms and have a vote on trying out a very basic minimal set up which will try to take into account all the issues that were mentioned (Chagai)<br />
** Chagai will go ahead with a Test Run bridging Slack with one other platform (Whatsapp, TG, etc)<br />
<br />
* discuss adding a basic matrix set up with jitsi to try it out, maybe bring it up to a vote of enough people are interested in reading about the suggestion. (Chagai)<br />
** Matrix suggestion to be re-read and discussed by tech area, to decide which to use whether protocol, SDK etc.<br />
** Do we need IM in TR? Or can we use external apps specialised in that?<br />
<br />
* VA Team is looking for centralizing information on Regular Calls /Loberto<br />
** If you organize a call that is open to others, please share them on #va_secret_lab<br />
<br />
* VA Team is trying to make a '''Volunteer Map'''<br />
** Wanting 1 #AreaChampion for each area, a person to go to when there are questions, or to point new volunteers who want to help there.<br />
<br />
* Volunteers who only work in 1 limited area<br />
** It was discussed it they need to be part of Slack (not really a point in "making" then, since they can always ignore it)<br />
** it sounds like single area volunteers are acceptable as long as there are not many questions /Stove<br />
***If Social Media mods need to answer big question, should they join Slack?<br />
** Here we see the need for a Contact person, or in Charge person, to organize this “Lone Wolfs”<br />
<br />
* Codi Best Practices<br />
** info gaps already happening from different discussions<br />
** For people who edit in Codi (specially the weekly meeting one) it would be nice to log in to Codi, or at least edit their guest name to keep control on the version editing<br />
<br />
* DOCUMENTATION<br />
** There is a need to put efforts on Documentation; with easy way to access to it and search for it<br />
*** Slack is a glorified Chat Room, so not a good place for permanent info<br />
** There were question about a Roadmap for the developers<br />
<br />
* Sharing News / Making Announcement on the Monday meeting<br />
** whenever someone makes a decision or is having an important discussion, share it on the weekly meeting.<br />
** Update the main codi (https://codi.kanthaus.online/trustroots) with updates from all meetings to avoid loss of info<br />
<br />
<br />
== Action points and outcomes ==<br />
<br />
Next Date: July 13th 2020, **16:00** UTC<br />
Next Facilitator: You?<br />
<br />
* More discussion is needed to see the desire to record meeting<br />
* Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter<br />
* Chagai will implement a test bridge between Slack and one other platform<br />
* VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.<br />
* If you use Codi, keep an eye out for a Best Practices handout<br />
* Efforts are going towards Documentation, so start documenting things done, changes made, etc<br />
* If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)<br />
* Maybe we should make a call for more Devs in the next Newsletter</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-06_Regular_Meeting&diff=24162Meeting Minutes/2020-07-06 Regular Meeting2020-07-06T21:17:47Z<p>Loberto: /* Agenda */</p>
<hr />
<div>= Trustroots Meeting =<br />
<br />
* Date: 2020-07-06 '''16:00''' UTC<br />
* Facilitator: Loberto<br />
* Present: Chagai, Stove, Pramus, Loberto, Dario, Shawn, Mariano, Michael, Paula, Philipp (maybe someone else...)<br />
<br />
== Agenda ==<br />
* Hellos and checkin<br />
* Raising awareness to recording our calls - especially the tech one's but also the discussions and even the chit chat - only if everyone on the call is comfortable with it of course! /Chagai<br />
** Concerns were raised regarding privacy, both personal (voice, face, room, etc) and professional (taking ideas from the recording to another platform)<br />
** ---> it was agreed to move to Slack for further conversation <br />
<br />
* using Kialo.com for big discussion with conflicting ideas<br />
** https://www.kialo.com/<br />
** pros: looks like a good platform for high-level discussion, organized and friendlier than GitHub<br />
** cons: too much branching on different tools; making conversations longer without reaching a point; being it an external, closed-source, SaaS platform.<br />
** If there is nothing specific about Kialo, maybe considering going back to the Discourse instance that existed 2 years ago.<br />
** https://support.kialo.com/hc/en-us/articles/115003878065-Published-vs-Private-Discussions<br />
<br />
* thoughts on -theoretically- buying Couchsurfing for the user database (making a petition, setting up a donation option, etc.) /Chagai - Shawn<br />
** Shawn heard something in some circles, just wanting to open the discussion and puting the idea in the open.<br />
** If Couchsurfing goes down the drain, we could theoretically try to do a fundraiser to buy out Couchsurfing and get access to their user database. Current value is 23 Million Dollars (that’s what was invested in it at some point)<br />
<br />
* promoting events on trustroots /Chagai - Shawn<br />
** finding power user to find people to promote events /Shawn<br />
** Adrian think of giving badges (gamification) - not only restricted to events, it can be a more general functionality also used for perks (10,50,100 etc. people hosted) or profile completion % /Adrian<br />
** Making "best practices" to organize events. <br />
** Finding people already organizing event and get feedback from them (tools they would want, etc)<br />
** there once were trustroots stickers. We could find them and distribute the design (is it open?)<br />
** Writing info for next Newsletter<br />
** Shawn will start the doc and convo<br />
<br />
* discuss one last time the bridging to other platforms and have a vote on trying out a very basic minimal set up which will try to take into account all the issues that were mentioned (Chagai)<br />
** Chagai will go ahead with a Test Run bridging Slack with one other platform (Whatsapp, TG, etc)<br />
<br />
* discuss adding a basic matrix set up with jitsi to try it out, maybe bring it up to a vote of enough people are interested in reading about the suggestion. (Chagai)<br />
** Matrix suggestion to be re-read and discussed by tech area, to decide which to use whether protocol, SDK etc.<br />
** Do we need IM in TR? Or can we use external apps specialised in that?<br />
<br />
* VA Team is looking for centralizing information on Regular Calls /Loberto<br />
** If you organize a call that is open to others, please share them on #va_secret_lab<br />
<br />
* VA Team is trying to make a '''Volunteer Map'''<br />
** Wanting 1 #AreaChampion for each area, a person to go to when there are questions, or to point new volunteers who want to help there.<br />
<br />
* Volunteers who only work in 1 limited area<br />
** It was discussed it they need to be part of Slack (not really a point in "making" then, since they can always ignore it)<br />
** it sounds like single area volunteers are acceptable as long as there are not many questions /Stove<br />
***If Social Media mods need to answer big question, should they join Slack?<br />
** Here we see the need for a Contact person, or in Charge person, to organize this “Lone Wolfs”<br />
<br />
* Codi Best Practices<br />
** info gaps already happening from different discussions<br />
** For people who edit in Codi (specially the weekly meeting one) it would be nice to log in to Codi, or at least edit their guest name to keep control on the version editing<br />
<br />
* DOCUMENTATION<br />
** There is a need to put efforts on Documentation; with easy way to access to it and search for it<br />
*** Slack is a glorified Chat Room, so not a good place for permanent info<br />
** There were question about a Roadmap for the developers<br />
<br />
* Sharing News / Making Announcement on the Monday meeting<br />
** whenever someone makes a decision or is having an important discussion, share it on the weekly meeting.<br />
** Update the main codi (https://codi.kanthaus.online/trustroots) with updates from all meetings to avoid loss of info<br />
<br />
<br />
=== Action points and outcomes<br />
<br />
Next Date: July 13th 2020, **16:00** UTC<br />
Next Facilitator: You?<br />
<br />
* More discussion is needed to see the desire to record meeting<br />
* Shawn will look into seeing how to promote events with the most active users, maybe writing info for a Newsletter<br />
* Chagai will implement a test bridge between Slack and one other platform<br />
* VA Team is gathering info to share around: regular calls, volunteers map, and those outside of slack.<br />
* If you use Codi, keep an eye out for a Best Practices handout<br />
* Efforts are going towards Documentation, so start documenting things done, changes made, etc<br />
* If things worth noting happen, let's share them in the Weekly meeting (add them to the Agenda)<br />
* Maybe we should make a call for more Devs in the next Newsletter</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-06_Regular_Meeting&diff=24161Meeting Minutes/2020-07-06 Regular Meeting2020-07-06T21:07:37Z<p>Loberto: /* Agenda */</p>
<hr />
<div>= Trustroots Meeting =<br />
<br />
* Date: 2020-07-06 '''16:00''' UTC<br />
* Facilitator: Loberto<br />
* Present: Chagai, Stove, Pramus, Loberto, Dario, Shawn, Mariano, Michael, Paula, Philipp (maybe someone else...)<br />
<br />
== Agenda ==<br />
* Hellos and checkin<br />
* Raising awareness to recording our calls - especially the tech one's but also the discussions and even the chit chat - only if everyone on the call is comfortable with it of course! /Chagai<br />
** https://www.kialo.com/<br />
** Concerns were raised regarding privacy, both personal (voice, face, room, etc) and professional (taking ideas from the recording to another platform)<br />
** https://support.kialo.com/hc/en-us/articles/115003878065-Published-vs-Private-Discussions<br />
** ---> it was agreed to move to Slack for further conversation <br />
<br />
* using Kialo.com for big discussion with conflicting ideas<br />
** pros: looks like a good platform for high-level discussion, organized and friendlier than GitHub<br />
** cons: too much branching on different tools; making conversations longer without reaching a point; being it an external, closed-source, SaaS platform.<br />
** If there is nothing specific about Kialo, maybe considering going back to the Discourse instance that existed 2 years ago.<br />
<br />
* thoughts on -theoretically- buying Couchsurfing for the user database (making a petition, setting up a donation option, etc.) /Chagai - Shawn<br />
** Shawn heard something in some circles, just wanting to open the discussion and puting the idea in the open.<br />
** If Couchsurfing goes down the drain, we could theoretically try to do a fundraiser to buy out Couchsurfing and get access to their user database. Current value is 23 Million Dollars (that’s what was invested in it at some point)<br />
<br />
* promoting events on trustroots /Chagai - Shawn<br />
** finding power user to find people to promote events /Shawn<br />
** Adrian think of giving badges (gamification) - not only restricted to events, it can be a more general functionality also used for perks (10,50,100 etc. people hosted) or profile completion % /Adrian<br />
** Making "best practices" to organize events. <br />
** Finding people already organizing event and get feedback from them (tools they would want, etc)<br />
** there once were trustroots stickers. We could find them and distribute the design (is it open?)<br />
** Writing info for next Newsletter<br />
** Shawn will start the doc and convo<br />
<br />
* discuss one last time the bridging to other platforms and have a vote on trying out a very basic minimal set up which will try to take into account all the issues that were mentioned (Chagai)<br />
** Chagai will go ahead with a Test Run bridging Slack with one other platform (Whatsapp, TG, etc)<br />
<br />
* discuss adding a basic matrix set up with jitsi to try it out, maybe bring it up to a vote of enough people are interested in reading about the suggestion. (Chagai)<br />
** Matrix suggestion to be re-read and discussed by tech area, to decide which to use whether protocol, SDK etc.<br />
** Do we need IM in TR? Or can we use external apps specialised in that?<br />
<br />
* VA Team is looking for centralizing information on Regular Calls /Loberto<br />
** If you organize a call that is open to others, please share them on #va_secret_lab<br />
<br />
* VA Team is trying to make a '''Volunteer Map'''<br />
** Wanting 1 #AreaChampion for each area, a person to go to when there are questions, or to point new volunteers who want to help there.<br />
<br />
* Volunteers who only work in 1 limited area<br />
** It was discussed it they need to be part of Slack (not really a point in "making" then, since they can always ignore it)<br />
** it sounds like single area volunteers are acceptable as long as there are not many questions /Stove<br />
***If Social Media mods need to answer big question, should they join Slack?<br />
** Here we see the need for a Contact person, or in Charge person, to organize this “Lone Wolfs”<br />
<br />
* Codi Best Practices<br />
** info gaps already happening from different discussions<br />
** For people who edit in Codi (specially the weekly meeting one) it would be nice to log in to Codi, or at least edit their guest name to keep control on the version editing<br />
<br />
* DOCUMENTATION<br />
** There is a need to put efforts on Documentation; with easy way to access to it and search for it<br />
*** Slack is a glorified Chat Room, so not a good place for permanent info<br />
** There were question about a Roadmap for the developers<br />
<br />
* Sharing News / Making Announcement on the Monday meeting<br />
** whenever someone makes a decision or is having an important discussion, share it on the weekly meeting.<br />
** Update the main codi (https://codi.kanthaus.online/trustroots) with updates from all meetings to avoid loss of info<br />
<br />
<br />
## Action points and outcomes<br />
<br />
Next Date: July 13th 2020, **16:00** UTC<br />
Next Facilitator: Martin / Loberto<br />
<br />
Action points:<br />
* Ask for more Devs in the next Newsletter</div>Lobertohttps://wiki.trustroots.org/w/index.php?title=Meeting_Minutes/2020-07-06_Regular_Meeting&diff=24160Meeting Minutes/2020-07-06 Regular Meeting2020-07-06T21:02:29Z<p>Loberto: /* Agenda */ #trustrootsallstars</p>
<hr />
<div>= Trustroots Meeting =<br />
<br />
* Date: 2020-07-06 '''16:00''' UTC<br />
* Facilitator: Loberto<br />
* Present: Chagai, Stove, Pramus, Loberto, Dario, Shawn, Mariano, Michael, Paula, Philipp (maybe someone else...)<br />
<br />
== Agenda ==<br />
* Hellos and checkin<br />
* Raising awareness to recording our calls - especially the tech one's but also the discussions and even the chit chat - only if everyone on the call is comfortable with it of course! /Chagai<br />
** https://www.kialo.com/<br />
** Concerns were raised regarding privacy, both personal (voice, face, room, etc) and professional (taking ideas from the recording to another platform)<br />
** https://support.kialo.com/hc/en-us/articles/115003878065-Published-vs-Private-Discussions<br />
** ---> it was agreed to move to Slack for further conversation <br />
<br />
* using Kialo.com for big discussion with conflicting ideas<br />
** pros: looks like a good platform for high-level discussion, organized and friendlier than GitHub<br />
** cons: too much branching on different tools; making conversations longer without reaching a point; being it an external, closed-source, SaaS platform.<br />
** If there is nothing specific about Kialo, maybe considering going back to the Discourse instance that existed 2 years ago.<br />
<br />
* thoughts on -theoretically- buying Couchsurfing for the user database (making a petition, setting up a donation option, etc.) /Chagai - Shawn<br />
** Shawn heard something in some circles, just wanting to open the discussion and puting the idea in the open.<br />
** If Couchsurfing goes down the drain, we could theoretically try to do a fundraiser to buy out Couchsurfing and get access to their user database. Current value is 23 Million Dollars (that’s what was invested in it at some point)<br />
<br />
* promoting events on trustroots /Chagai - Shawn<br />
** finding power user to find people to promote events /Shawn<br />
** Adrian think of giving badges (gamification) - not only restricted to events, it can be a more general functionality also used for perks (10,50,100 etc. people hosted) or profile completion % /Adrian<br />
** Making "best practices" to organize events. <br />
** Finding people already organizing event and get feedback from them (tools they would want, etc)<br />
** there once were trustroots stickers. We could find them and distribute the design (is it open?)<br />
** Writing info for next Newsletter<br />
** Shawn will start the doc and convo<br />
<br />
* discuss one last time the bridging to other platforms and have a vote on trying out a very basic minimal set up which will try to take into account all the issues that were mentioned (Chagai)<br />
** Chagai will go ahead with a Test Run bridging Slack with one other platform (Whatsapp, TG, etc)<br />
<br />
* discuss adding a basic matrix set up with jitsi to try it out, maybe bring it up to a vote of enough people are interested in reading about the suggestion. (Chagai)<br />
** Matrix suggestion to be re-read and discussed by tech area, to decide which to use whether protocol, SDK etc.<br />
<br />
* VA Team is looking for centralizing information on Regular Calls /Loberto<br />
** If you organize a call that is open to others, please share them on #va_secret_lab<br />
<br />
* VA Team is trying to make a '''Volunteer Map'''<br />
** Wanting 1 #AreaChampion for each area, a person to go to when there are questions, or to point new volunteers who want to help there.<br />
<br />
* Volunteers who only work in 1 limited area<br />
** It was discussed it they need to be part of Slack (not really a point in "making" then, since they can always ignore it)<br />
** it sounds like single area volunteers are acceptable as long as there are not many questions /Stove<br />
***If Social Media mods need to answer big question, should they join Slack?<br />
** Here we see the need for a Contact person, or in Charge person, to organize this “Lone Wolfs”<br />
<br />
* Codi Best Practices<br />
** info gaps already happening from different discussions<br />
** For people who edit in Codi (specially the weekly meeting one) it would be nice to log in to Codi, or at least edit their guest name to keep control on the version editing<br />
<br />
* DOCUMENTATION<br />
** There is a need to put efforts on Documentation; with easy way to access to it and search for it<br />
*** Slack is a glorified Chat Room, so not a good place for permanent info<br />
<br />
* Sharing News / Making Announcement on the Monday meeting<br />
** whenever someone makes a decision or is having an important discussion, share it on the weekly meeting.<br />
** Update the main codi (https://codi.kanthaus.online/trustroots) with updates from all meetings to avoid loss of info</div>Loberto