Trustroots Wiki - User contributions [en]

Template:Tribes

2020-10-02T10:22:28Z

Rumwerfer: Rumwerfer moved page Template:Tribes to Template:Circles: renaming last summer

#REDIRECT [[Template:Circles]]

Template:Circles

2020-10-02T10:22:28Z

Rumwerfer: Rumwerfer moved page Template:Tribes to Template:Circles: renaming last summer

[[hitchhikers]], [[dumpster divers]], [[Veg|vegans&vegetarians]], [[nomads]], [[ecoliving]], [[musicians]], [[foodsharing]], [[cyclists]], [[hikers]], [[Guide to punk|punks]], [[artists]], [[hackers]], [[lgbtq]], [[yoga]], [[buskers]], [[rainbow gathering]], [[climbers]], [[spirituals]], [[dancers]], [[families]], [[sailors]], [[lindyhoppers]], [[slackliners]], [[acroyoga]], [[van life]], [[jugglers]], [[Volunteer|Trustroots volunteers]], cooking, photographers, gardeners & farmers, naturists, feminists, [[anarchists]], squatters, surfers, motorcyclists, pilgrims, burners, circus, skateboarders, beer brewers, winemakers

Template:Circles

2020-10-02T10:21:44Z

Rumwerfer: add new tribes

Safety/2020-05-20

2020-06-02T17:33:40Z

Rumwerfer: /* Value priorities */ formatting

= Trustroots Safety Team Meeting =

Date: 2020-05-20 20:00 UTC+2 / CEST Facilitator: Philipp Participants: Philipp, Dario, Ludo

== Agenda ==

* check-ins
* feedback about last week
* follow-ups on topics from [https://wiki.trustroots.org/en/Safety/2020-05-06 last meeting]?
** non-discriminative behavior in rules
*** RULES: we said we wanted to add something in order to ''be explicit about not tolerating objectionable content or abusive users''
*** (phrasing about discrimination)
** value priorities
** sexual abuse case
** open ticket: https://trustroots.zendesk.com/agent/tickets/3122 (Dario?)
* pick facilitator for next meeting
* random question

let’s try to get everything done within one hour

== Feedback about last week ==

* Philipp:
** felt unsecure in the beginning how to handle support requests, but now there is a lot going on and feels like there’s a lot he can do
** forwarded all the newsletter mails to Julien
** Noahs notes on open requests were quite helpful
** idea: have a shared support ticket answering session
* Ludo:
** felt much more effective through Noah’s notes
** feels less effective than old support team, but that’s ok
** experienced progress over the last week
* Dario:
** cool that there are new team members
** don’t be afraid to ask questions and go ahead and answer!
** most active week on trustroots ever in terms of signups and support traffic
** super interesting times, happy about the timing: team growth and couchsurfing spike -> we can handle this well

== Follow-ups from last week’s session ==

* new aspect: you ‘sign’ those rules when you sign up
* other possible places for more elaborate discussion about our stance towards racism and discrimination: blog post?
* maybe it’s better to have very short and simple rules
* Mikaels change to rules: “Be friendly and know when to stop messaging someone. We have no tolerance for objectionable content or abusive users.”
* let’s create a pad and work there on the rules after the call

== Rules for support team ==

* Ludo suggests to give ourself a code we follow while we do our work
* Dario: +1; on the github safety wiki they have started a rule book, until now only about creep profiles: https://github.com/Trustroots/safety/wiki/Rules-for-report-cases should be extended!
* Dario: for now it’s ok as an internal thing, but in the future we could be transparent and make it public?
* do that alongside real cases as an example

== Sexual abuse case ==

* Ludo is going to discuss the message draft with Noah (and Philipp?) on slack
* we’ll see how it goes when the message is sent to reporting person
* Philipp: aim to solve until next week maybe? Dario: But the new stuff is a lot less serios.

== https://trustroots.zendesk.com/agent/tickets/3122 ==

* reporting person ok to reach out to reported person
* Dario reached out to the reported person -> waiting for reply
* Dario: it’s standard procedure

== Value priorities ==

move to next call! Philipp wrote on Slack:

<blockquote>Maybe we could try to put up a priorities list of values to guide us in decisions or make things clearer? Something in the like of (probably missed a lot):
* keep trustroots community a safe space
* protect vulnerable members
* uncover problems
* be transparent
* be consistent in decisions
* offer TR members the possibility to reflect their attitude
</blockquote>

== Question: ==

Dario: “if you could only travel once more, to where and to who would it be?”

== Sexual abuse case take 2 ==

* Noah: explain to them in a reassuring way why we want to read their message.
* Noah: you reported xy. Our standard policy is to ask for permission
* Ludo: confused: message exchange 5y ago + message exchange with same users around the time they report came in
* whatever we do with a motivation to protect the socalled victim. reporting user with their past and recorded person using their trustroots account.
* Ludo: situation might be delicate with police case. We didn’t want to expose reporting person
* Noah: if to decide: making victim feel we don’t believe them is a lot worse than suspending reported person for no reason
* proposal: transparently message reported person -> he got reported (we won’t say by whom or for what) and that their account got suspended.
** either they don’t respond
** or they respond. What do we do then?
* besides their (linked) CS account got removed
* Noah is contacting BW if they received a report and how they are handling it

== Next meeting ==

Next Date: 2020-05-27 20:00 UTC+2 / CEST but check with Noah! Next Facilitator: Ludo

Safety/2020-05-06

2020-05-20T06:46:57Z

Rumwerfer: /* Follow-up on Sexual abuse case */

Date: 2020-05-06 20:00 UTC+2 / CEST

Facilitator: Dario

Participants: Philipp, Ludovica, Dario

= Follow-up on Sexual abuse case =

* we walked the new safety team members through the admin panel and the thread feature
* we found out that the reporting member had message exchange with the reported member 5 years ago
* also odd observation: they contacted a lot of the same people

== Action points ==

# ask reporting member if we can read the messages -> Ludovica
# delay further action until we have an explanation for the odd observation

= Follow-up: Non-discriminative behavior in rules =

== Action points ==

Philipp will come up with a draft for that

= Value priorities =

Philipp wrote on Slack:

<blockquote>Maybe we could try to put up a priorities list of values to guide us in decisions or make things clearer? Something in the like of (probably missed a lot):
* keep trustroots community a safe space
* protect vulnerable members
* uncover problems
* be transparent
* be consistent in decisions
* offer TR members the possibility to reflect their attitude
</blockquote>

'''postponed to next meeting'''

= Next meeting =

Next Date: 2020-05-13 20:00 UTC+2 / CEST

Next Facilitator: Philipp

Safety/2020-05-06

2020-05-20T06:43:00Z

Rumwerfer: remove agenda section

Date: 2020-05-06 20:00 UTC+2 / CEST

Facilitator: Dario

Participants: Philipp, Ludovica, Dario

= Follow-up on Sexual abuse case =

* we walked through the admin panel and the thread feature
* we found out that the reporting member had message exchange with the reported member 5 years ago
* also odd observation: they contacted a lot of the same people

== Action points ==

# ask reporting member if we can read the messages -> Ludovica
# delay further action until we have an explanation for the odd observation

= Follow-up: Non-discriminative behavior in rules =

== Action points ==

Philipp will come up with a draft for that

= Value priorities =

Philipp wrote on Slack:

<blockquote>Maybe we could try to put up a priorities list of values to guide us in decisions or make things clearer? Something in the like of (probably missed a lot):
* keep trustroots community a safe space
* protect vulnerable members
* uncover problems
* be transparent
* be consistent in decisions
* offer TR members the possibility to reflect their attitude
</blockquote>

'''postponed to next meeting'''

= Next meeting =

Next Date: 2020-05-13 20:00 UTC+2 / CEST

Next Facilitator: Philipp

Safety/2020-05-06

2020-05-20T06:42:32Z

Rumwerfer: fix syntax

Date: 2020-05-06 20:00 UTC+2 / CEST

Facilitator: Dario

Participants: Philipp, Ludovica, Dario

= Agenda =

* check-ins
* follow-ups on topics from [[Safety/2020-04-29 | last meeting]]?
* value priorities
* pick facilitator for next meeting

= Follow-up on Sexual abuse case =

* we walked through the admin panel and the thread feature
* we found out that the reporting member had message exchange with the reported member 5 years ago
* also odd observation: they contacted a lot of the same people

== Action points ==

# ask reporting member if we can read the messages -> Ludovica
# delay further action until we have an explanation for the odd observation

= Follow-up: Non-discriminative behavior in rules =

== Action points ==

Philipp will come up with a draft for that

= Value priorities =

Philipp wrote on Slack:

<blockquote>Maybe we could try to put up a priorities list of values to guide us in decisions or make things clearer? Something in the like of (probably missed a lot):
* keep trustroots community a safe space
* protect vulnerable members
* uncover problems
* be transparent
* be consistent in decisions
* offer TR members the possibility to reflect their attitude
</blockquote>

'''postponed to next meeting'''

= Next meeting =

Next Date: 2020-05-13 20:00 UTC+2 / CEST

Next Facilitator: Philipp

Safety/2020-05-06

2020-05-20T06:39:49Z

Rumwerfer: Created page with "= Trustroots Safety Team Meeting = Date: 2020-05-06 20:00 UTC+2 / CEST Facilitator: Dario Participants: Philipp, Ludovica, Dario == Agenda == * check-ins * follow-ups on..."

= Trustroots Safety Team Meeting =

Date: 2020-05-06 20:00 UTC+2 / CEST

Facilitator: Dario

Participants: Philipp, Ludovica, Dario

== Agenda ==

* check-ins
* follow-ups on topics from [last meeting](https://wiki.trustroots.org/en/Safety/2020-04-29)?
* value priorities
* pick facilitator for next meeting

== Follow-up on Sexual abuse case ==

* we walked through the admin panel and the thread feature
* we found out that the reporting member had message exchange with the reported member 5 years ago
* also odd observation: they contacted a lot of the same people

=== Action points ===

# ask reporting member if we can read the messages -> Ludovica
# delay further action until we have an explanation for the odd observation

== Follow-up: Non-discriminative behavior in rules ==

=== Action points ===

Philipp will come up with a draft for that

== Value priorities ==

Philipp wrote on Slack:

<blockquote>Maybe we could try to put up a priorities list of values to guide us in decisions or make things clearer? Something in the like of (probably missed a lot):
* keep trustroots community a safe space
* protect vulnerable members
* uncover problems
* be transparent
* be consistent in decisions
* offer TR members the possibility to reflect their attitude
</blockquote>

'''postponed to next meeting'''

== Next meeting ==

Next Date: 2020-05-13 20:00 UTC+2 / CEST

Next Facilitator: Philipp

Safety/2020-04-29

2020-05-05T17:29:18Z

Rumwerfer: /* Trustroots Meeting */

= Trustroots Safety Team Meeting =

* Date: 2020-04-29 20:00 UTC+2
* Participants: Ludovica, Philipp, Noah, Dario

= Agenda =

== Case: Sexual Abuse (unrelated to TR) ==

https://trustroots.zendesk.com/agent/tickets/3045

Actions:
* write to people the reported member contacted on TR if they had any bad experience (less to validate the incident, more to support people possibly assaulted by them. not mentioning the offender when contacting other people they had contact with, but more generally ask if they ever had any bad experience with anyone on TR and that we can give support if they did)
* ask the reporting member if it's okay to disclose anonymous information about why we suspend the reported member, and if so, suspend them with a message saying why (rather than shadow-ban). After the meeting, the discussion continued on Slack, and we're still undecisive between shadow-ban and suspension.

== Case: Offensive comments ==

https://trustroots.zendesk.com/agent/tickets/3122

Actions:
* give the reporting member another reply, confirm that we share their values, and ask if it's okay to mention their name when contacting the reported member. Let them know about our next steps. We could ask if they would want a communication room moderated by us.
* contact the reported member and let them know about the report, asking them for their opinion on what happened. If they wouldn't reply, we'll suspend them.

== Mention non-discriminative behavior in our rules ==

* we thought about if trustroots.org/rules should have a sentence especially mentioning "discriminative behavior"
* Maybe we can somehow add in the idea that non-discriminative spaces aren't a state but rather an ongoing process (and one we as trustroots want to go along…) ? - Philipp

= Next meeting =

* 2020-05-06 20:00 UTC+2

Safety/2020-04-29

2020-05-05T17:27:32Z

Rumwerfer: fix next date

= Trustroots Meeting =

* Date: 2020-04-29 20:00 UTC+2
* Participants: Ludovica, Philipp, Noah, Dario

= Agenda =

== Case: Sexual Abuse (unrelated to TR) ==

https://trustroots.zendesk.com/agent/tickets/3045

Actions:
* write to people the reported member contacted on TR if they had any bad experience (less to validate the incident, more to support people possibly assaulted by them. not mentioning the offender when contacting other people they had contact with, but more generally ask if they ever had any bad experience with anyone on TR and that we can give support if they did)
* ask the reporting member if it's okay to disclose anonymous information about why we suspend the reported member, and if so, suspend them with a message saying why (rather than shadow-ban). After the meeting, the discussion continued on Slack, and we're still undecisive between shadow-ban and suspension.

== Case: Offensive comments ==

https://trustroots.zendesk.com/agent/tickets/3122

Actions:
* give the reporting member another reply, confirm that we share their values, and ask if it's okay to mention their name when contacting the reported member. Let them know about our next steps. We could ask if they would want a communication room moderated by us.
* contact the reported member and let them know about the report, asking them for their opinion on what happened. If they wouldn't reply, we'll suspend them.

== Mention non-discriminative behavior in our rules ==

* we thought about if trustroots.org/rules should have a sentence especially mentioning "discriminative behavior"
* Maybe we can somehow add in the idea that non-discriminative spaces aren't a state but rather an ongoing process (and one we as trustroots want to go along…) ? - Philipp

= Next meeting =

* 2020-05-06 20:00 UTC+2

Safety/2020-04-29

2020-05-05T17:24:18Z

Rumwerfer: meeting minutes

Safety

2020-05-05T17:07:44Z

Rumwerfer: /* Safety team */ add meeting minutes

[[Trustroots]] takes safety seriously. We prefer implementing systems to avoid incidents. I.e. we prefer building [[trust]] features over safety features.

== Tips for women travelers ==

Especially women have to take care of safety, read more [[Tips_for_women_travelers|here]].

== What could possibly go wrong? ==

=== Unpleasant experience ===

Unpleasant experiences vary not a big deal (e.g. staying in a dirty place or loud guests or hosts at night) to much worse. We want to build features that allow people to rate their experience and later use that rating information so that similar (based on tagging) people will not have unpleasant experiences again with that person. E.g. very clean people will automatically avoid very dirty people, and party people will not easily be connected to people who prefer tranquility over Dionysian celebrations. Unless they choose otherwise of course, a conscious decision.

=== Violence ===

Violence is an extremely unpleasant experience (for most people).

We expect that most inherently violent people will cause unpleasant experiences before actual violence occurs. And that our system to prevent unpleasant experiences will also prevent violence.

There are some interesting cases, such as the famous Venetian wrestling contests - enforced by the host among various guests. A lot of people will consider this violence. We agree. But if it's obvious to potential guests that this is going to be their experience they should be free to go ahead.

=== Sexual abuse and harassment ===

This mainly affects solo traveling women, please read more [[Tips_for_women_travelers|here]].

== Safety team ==

Back in 2014 we didn't think building an extended dedicated safety team is the solution. Prevention is key. As soon as there is sign of a person showing violent behavior their trust rating should go down which leads to some kind of seclusion.

In 2018 we thought it's good to start building a team of people working on this (see also https://meta.trustroots.org/c/safety). Since 2019, our support / safety team consists of two people. More volunteers are welcome. Especially having a female point of view would be great in this team! If you are interested, join the [https://team.trustroots.org/Chat.html volunteer chat].

In 2020, our safety team grew to four people and we started having regular meetings: {{Special:Prefixindex|prefix=Safety/|stripprefix=1}}

== Random ideas ==

Add functionality to let local people check in with guests at an appointed time, e.g. through phone numbers.

== More safety advices ==

There is a very good article about safety on BeWelcome, http://www.bewelcome.org/safety.

[[Category:Trustroots]]

Hackweek Spring 2020

2020-04-19T20:24:36Z

Rumwerfer: /* Welcome session */ add picture

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

More thoughts can be found in the [https://codi.kanthaus.online/hackweek?edit planning pad]. If you want to join in, simply meet us in a check-in or check-out call in [[#Tools | Jitsi]] or directly join a [[#Program | session]].

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
|
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
| [[#Mobile app]]
|
|
|
|-
|17:00
|
|
|
|
| [[#Code walkthrough]]
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| [[#Closing session]]
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

[[File:2020-04-11-hackweek-opening.png|600px]]

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Please add your observations using Weblate to the [https://codi.kanthaus.online/trustroots-translations?edit pad]

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Mobile app ===

Theo, Nick, Mikael

two main approaches:

# Adapt the existing wrapped mobile website and start to see if we can introduce some native elements to it, either features or whole views where it makes sense
# Start with a fresh React Native / Expo project and implement a very small, core subset of features that would work really well on mobile and have really good offline support and take advantage of native APIs where possible (geolocation and messaging for instance).

From a developer perspective I felt number 2 was easier to approach and easier to get people on board with however there are some benefits to the first as well, namely keeping all the existing features and not duplicating UI work.There is also the idea that regardless which option we pick we should release the existing app into the iOS app store.

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Trustroots has an informal organizational structure right now. A do-ocracy approach, and trust-based access to resources and decisions.

I'd like to see the wider community much more involved in the direction/process, and get a really strong connection between the group of active contributors, where we take the time to listen to each other and find good ways forward.

It's a very alive topic for me right, as I also try to make my personal life work in harmony with projects like this (community-based open source software). I want these projects to be really sustainable and resilient, and the main part of my life - it's all I work on right now. You can read a bit more about my personal angle here --> https://liberapay.com/nicksellen/.

I don't want/need anything to happen very fast, most important to me is getting a good feeling within the team(s), but I do want to share this vision of how I can see trustroots going, and want to start the conversation about this stuff.

Topics that are interesting to me to share thoughts about are:

* how to decide things (low-bureaucracy, transparent, ...)
* receiving money (donations / funding)
* distributing money (solidarity, not wages; fair, not equal)
* supporting people to contribute that don't have the luxury of time to volunteer
* elected board?
* tech vs non-tech people (how to avoid being a dev-only project)

I also tie this stuff into wider concepts - how to challenge society and show there is another way to organise, gift economy approaches.

I really liked reading https://disco.coop/manifesto/ too, but I don't think the model quite fits this case. I'd love to have (or make) another model/manifesto that works for trustroots and other similar projects!

=== Closing session ===

Coordinator: Edvard

Meeting notes: https://codi.kanthaus.online/trustroots-hackweek-closing

==== Purpose of the meeting ====
* group cohesion - getting things an people together
* wrap up and celebrate
* reflection on the hackweek
* outlook for the future - how to continue from hereTrustroots has an informal organizational structure right now. A do-ocracy approach, and trust-based access to resources and decisions.

==== Subgroup wrap-ups ====
The subgroups summarize what happened and their outcomes.
* getting started with trustroots coding
* react migration
* references feature
* support
* devops
* translations
* iOS app
* content - roots of trust
* organization

==== Reflection ====
Everyone shares his/her individual reflection on the Hackweek
* things that went well
* things that went not so well
* emotions experienced
* open thoughts for the future
* how will I go on from here?

==== Announcements of next events ====
* 20.4. 17pm (CEST / UTC + 2) - next regular phone call
** pad for calls: https://codi.kanthaus.online/trustroots
** in jitsi: https://meet.collective.tools/trustroots
* next session on organization
** who's interested? please comment on slack thread: https://trustroots.slack.com/archives/CCHS8HPJQ/p1587240108134200
* points of contact: slack, mumble,...

==== Goodbye for now ====

[[File:Trustroots-closing-session.jpg|600px]]

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

File:2020-04-11-hackweek-opening.png

2020-04-19T20:20:24Z

Rumwerfer:

Trustroots Wiki:Create account

2020-04-16T21:56:08Z

Rumwerfer: change contact

{{trwiki}}

Only [https://wiki.trustroots.org/w/index.php?title=Special:ListUsers&group=sysop administrators] on this wiki can create new accounts on the wiki.

Send an email to request an account.

[[File:mail.jpg]]

== For sysops: create a new account ==

Admins can create an account here: [[Special:CreateAccount]]

For documentation see https://www.mediawiki.org/wiki/Manual:Preventing_access#Restrict_account_creation

If you're a sysop, feel free to create accounts for anyone who is not a spammer (that is most people).

If you're a bureaucrat, feel free to upgrade more people to sysops and bureaucrats.

File:Mail.jpg

2020-04-16T21:54:45Z

Rumwerfer:

Hackweek Spring 2020

2020-04-16T18:11:50Z

Rumwerfer: change introduction

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

More thoughts can be found in the [https://codi.kanthaus.online/hackweek?edit planning pad]. If you want to join in, simply meet us in a check-in or check-out call in [[#Tools | Jitsi]] or directly join a [[#Program | session]].

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
| [[#Mobile app]]
|
|
|
|-
|17:00
|
|
|
|
| [[#Code walkthrough]]
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Please add your observations using Weblate to the [https://codi.kanthaus.online/trustroots-translations?edit pad]

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Mobile app ===

Theo, Nick, Mikael

two main approaches:

# Adapt the existing wrapped mobile website and start to see if we can introduce some native elements to it, either features or whole views where it makes sense
# Start with a fresh React Native / Expo project and implement a very small, core subset of features that would work really well on mobile and have really good offline support and take advantage of native APIs where possible (geolocation and messaging for instance).

From a developer perspective I felt number 2 was easier to approach and easier to get people on board with however there are some benefits to the first as well, namely keeping all the existing features and not duplicating UI work.There is also the idea that regardless which option we pick we should release the existing app into the iOS app store.

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
* co-operatives / open co-ops
* gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

Hackweek Spring 2020

2020-04-16T18:05:32Z

Rumwerfer: add mobile app summary

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
| [[#Mobile app]]
|
|
|
|-
|17:00
|
|
|
|
| [[#Code walkthrough]]
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Please add your observations using Weblate to the [https://codi.kanthaus.online/trustroots-translations?edit pad]

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Mobile app ===

Theo, Nick, Mikael

two main approaches:

# Adapt the existing wrapped mobile website and start to see if we can introduce some native elements to it, either features or whole views where it makes sense
# Start with a fresh React Native / Expo project and implement a very small, core subset of features that would work really well on mobile and have really good offline support and take advantage of native APIs where possible (geolocation and messaging for instance).

From a developer perspective I felt number 2 was easier to approach and easier to get people on board with however there are some benefits to the first as well, namely keeping all the existing features and not duplicating UI work.There is also the idea that regardless which option we pick we should release the existing app into the iOS app store.

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
* co-operatives / open co-ops
* gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

Hackweek Spring 2020

2020-04-16T10:22:05Z

Rumwerfer: /* Translating Trustroots to other languages */

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
| Mobile app
|
|
|
|-
|17:00
|
|
|
|
| [[#Code walkthrough]]
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Please add your observations using Weblate to the [https://codi.kanthaus.online/trustroots-translations?edit pad]

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
* co-operatives / open co-ops
* gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

Hackweek Spring 2020

2020-04-16T10:14:26Z

Rumwerfer: /* Translating Trustroots to other languages */

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
| Mobile app
|
|
|
|-
|17:00
|
|
|
|
| [[#Code walkthrough]]
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

[https://codi.kanthaus.online/trustroots-translations?edit Pad]

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
* co-operatives / open co-ops
* gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

Hackweek Spring 2020

2020-04-16T10:08:59Z

Rumwerfer: /* Program */

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
| Mobile app
|
|
|
|-
|17:00
|
|
|
|
| [[#Code walkthrough]]
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
* co-operatives / open co-ops
* gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

User talk:Guaka/archive1

2020-04-15T14:41:08Z

Rumwerfer: BlockAndNuke

Which bot did I do? [[User:Azarethroy|Azarethroy]] 12:51, 28 April 2009 (UTC)
:Haha, oops! [[User:Azarethroy|Azarethroy]] 13:24, 28 April 2009 (UTC)

That's awesome. I've been toying with it. And I just noticed you installed VideoFlash -> [[Free Hugs Campaign]] :) [[User:Azarethroy|Azarethroy]] 22:48, 30 April 2009 (UTC)

== Rollbacks ==

I still don't understand all those rollbacks. I make some edit, press save. Later I check and suddenly there is a rollback to the last edit from guaka. Maybe there are some pre-settings, that don't allow me to edit certain pages and make automatic roll back? Because this happens only on the main page and some other core pages. My last edit was here https://wiki.trustroots.org/en/Wiki.trustroots.org:About and suddenly there was also a rollback.

== Hospitality Club ==

Why you wanna keep HC on the main page? HC is completely out-dated. I guess using the website is even a safety risk as there is no maintainance of the website. Also it's not possible to delete account there.

:Ah yeah it's good you removed it from the [[main page]]. Thanks. [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 14:26, 2 January 2019 (CET)

== wiki emails ==

I'm not getting my confirmation email. Does the wiki have permission to send emails? --[[User:Metal.lunchbox|Metal.lunchbox]] 20:56, 20 October 2009 (UTC)--[[User:Metal.lunchbox|Metal.lunchbox]] 20:56, 20 October 2009 (UTC)

:Just quickly fixed something in my mail servers. Should be better now. [[User:Guaka|guaka]] 08:50, 21 October 2009 (UTC)

I cannot get confirmation email on my gmx adress neither, but for hotmail it works fine (I would rather get the emails at gmx...) --[[User:Bikepunk|Bikepunk]] 22:09, 28 October 2009 (UTC)

:I requested an extra line in DNS (<tt>@ TXT v=spf1 a mx ~all</tt>) that might resolve this. [[User:Guaka|guaka]] 22:25, 28 October 2009 (UTC)

:: I still never get confirmation email @gmx.com ... [[User:Bikepunk|Bikepunk]] 01:17, 29 October 2009 (UTC)

::: The DNS update will take some time. I'm not doing the DNS myself, and even when it's updated it takes time to propagate... [[User:Guaka|guaka]] 01:18, 29 October 2009 (UTC)
:::: I've tried again today, and I still do not get emails @gmx.com [[User:Bikepunk|Bikepunk]] 14:20, 6 November 2009 (UTC)

::::: Hmm, Roy is transferring the couchwiki.org domain to me so that we can change stuff more quickly. Still, it might be another problem, but I want to make sure the DNS is correct first. I'll keep you updated. [[User:Guaka|guaka]] 23:29, 6 November 2009 (UTC)

:::::: Sorry for the delay guys. I've just emailed Kasper re: transferring the domain to him, so he can make any changes himself. [[user:azarethroy|azarethroy]] (15:51, 10 November 2009 (UTC))

:The transfer came through. I added a field in the DNS that should fix this issue. Let me know if it's better now - or not. [[User:Guaka|guaka]] 10:10, 9 December 2009 (UTC)
:: I still do not get emails at gmx.com :( [[User:Bikepunk|Bikepunk]] 18:34, 28 December 2009 (UTC)

== blocking those anoying bots ? ==

Hey

as you've seen, from yesterday a nasty bot is "attacking" couchwiki. I "undo"ed as much as possible, but since this bot is changing his IP for each edit, should we block th IPs, he's using ?
[[User:Bikepunk|Bikepunk]] 05:55, 14 November 2009 (UTC)

:It's possible to block thousands of IPs but I set up reCAPTCHA and no bot edits since then, I think it'll be adequate for now. [[User:Guaka|guaka]] 10:46, 14 November 2009 (UTC)



== What's the go with copying from wikipedia ==

See community portal for question.

:[[Couchwiki:Community_Portal#Added_cheat_sheet_from_wikipedia_-_compatible_licence.3F|And for the answer]] :) [[User:Guaka|guaka]] 16:03, 21 December 2009 (UTC)

== OpenID not working for me - see community tech portal ==

See [[Couchwiki:Tech#Bugs_to_fix]]

I tried logging in with my Aol Open ID but it say's it's cancelled. I ticked all the boxes except email for the moment. Is there a problem? I also have a twitter/hotmail accounts. I'm not sure I want them all linked though..... --118.208.189.140 08:59, 22 December 2009 (UTC)

:Hmm, AOL's OpenID might not work properly with MediaWiki OpenID extension. I'll try upgrading to the latest version of the extension (some time) to see if that solves it. Right now I'm only sure that MyOpenID and the WordPress OpenID provider plugin work for me :) [[User:Guaka|guaka]] 01:35, 27 December 2009 (UTC)

:: Same person as above. Still not working. I suppse with the NY period you've been very busy. --[[Special:Contributions/118.208.187.106|118.208.187.106]] 03:05, 9 January 2010 (UTC)

:::I upgraded to the latest version of the OpenID plugin (for mediawiki 1.15). I hope it works now. Otherwise, there might be relevant info [http://www.mediawiki.org/wiki/OpenID at the openid extension page at mediawiki.org]. [[User:Guaka|guaka]] 13:09, 9 January 2010 (UTC)

::::Happy to report it works with AIM openid. I'm not sure on my username though? Can I change it? (not asking you to do it yet).

:::::Cool that it works!
:::::I don't think it's easy to change usernames in mediawiki... [[User:Guaka|guaka]] 02:56, 16 January 2010 (UTC)

== Community Portal needs your attention. ==

http://couchwiki.org/en/Couchwiki:Community_Portal

== ref wiki command ==

Hi guaka. You told me a while ago that you would install an extension to make the ref tags work. Is there any progress on that? I would like to migrate the bw-fact-finding wiki to couchwiki but I need the ref things for this to make sense. Thanks for your help! [[User:Saraedum|Saraedum]] 12:49, 7 November 2011 (UTC)

:Ah, ok, I will try to set it up later this week. [[User:Guaka|guaka]] 06:19, 8 November 2011 (UTC)

:I installed the [[Special:Version|Cite extension]]. All should be good now. [[User:Guaka|guaka]] 06:21, 13 November 2011 (UTC)

::[[Help:Editing]] still doesn't show working ref commands. [[User:Saraedum|Saraedum]] 17:42, 16 November 2011 (UTC)

== IsIn Template ==

The [[Template:IsIn]] isn't working anymore, but I've no how idea how it worked anyway. It's heavy in use and I'd like to see it up again ... any ideas? [[User:Midsch|Midsch]] ([[User talk:Midsch|talk]]) 15:12, 24 December 2012 (CET)

:I emptied the includeonly part of the template for now. http://en.wikivoyage.org/wiki/Template:IsIn might have an anwer... I'll look into that after I manage to do something about the spambots. [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 16:21, 24 December 2012 (CET)

== relation to BW wiki / your message ==

Hi Guaka, I hope this is the right place and method to respond. Thank you for recognising my little contribution. You asked what I think of this couchwiki vs. bewelcome wiki. As a disgruntled CS user after the ToU change, I registered with BW and found the local group including the associated BW wiki, so I updated a few things there. With the CS wiki shutdown I became actively aware of Couchwiki, and generally I think the effort of maintaining information should be placed where it benefits most users. So if we document something not specific to a particular hospex network, why not document it on neutral ground and refer to it from everywhere. Likewise, in my contributions to couckwiki I would not try to copy statistic and general purpose data that can be found on wikipedia already, not would I concentrate on classic mass-tourist description of sights, but primarily on the practical aspects of how to get around, how to live on little budget, and interesting stuff to see beyond the main tourist paths.
This might also be a distinguisihing feature of couchwiki vs. wikivoyage. Whether the split is worth it depends of course if each wiki has enough momentum to build a document pool that is worth consulting. Looks like the Germany coverage is rather poor, as far as I can tell from the country/land index pages :( --[[User:KarlEMuc|KarlEMuc]] ([[User talk:KarlEMuc|talk]]) 01:10, 19 January 2013 (CET)

== Nice idea here, but it really misses Marketing! ==

Hello Guarka, nice you kept this wiki, but it would need much better Marketing, I guess one have to be pretty nerd to find this! Better explain, what to do in order to be found, when people search for couchsurfing in Google! I was thinking about launching realcouchsurfing.org, to enable a platform that unites all, that are not so happy with biggest hospitality exchange becoming a for profit organization, it would be much better, have this wiki, a discusstion/decision making forum and a guide, howto get well ranked in Google in one place. A domain having the buzzword couchsurfing in domain frame, could be an advantage to rank well against the now-for-profit-c$ webseite, how do you think about that?

:Hi Pianist! Eh, what exactly do you want to do? And what do you want me to do? :) [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 10:36, 7 June 2013 (CEST)

== Attribution ==
Hello Guaka! My name is Aleksandra and I am the community manager for Wikitravel.org. I have recently come across your website (which I find really nice) and noticed that you are republishing our travel guide content without a proper attribution, which is a violation of our writers' copyright. Please contact me as soon as possible at awocial@internetbrands.com. Thank you! [[User:AlexW|AlexW]] ([[User talk:AlexW|talk]]) 00:11, 27 June 2013 (CEST)

:Sorry I don't have (much) time to work on this wiki. It's a community wiki, so in that sense I see two options:
:1. Feel free to work it out on this wiki. Add a list or add the attribution where you think it's needed.
:2. Let your writers contact me about their copyright and I'll set things straight.
:Cheers, [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 23:12, 27 June 2013 (CEST)

:: Thank you, Guaka for your prompt response! Adding attribution is something that has to be '''implemented throughout your destination articles which use Wikitravel content'''. Please have a look at your [http://couchwiki.org/en/Beijing Beijing] page. The content from the first section is copied from Wikitravel wikitravel.org/en/Beijing page. I suggest you read wikitravel.org/shared/How_to_re-use_Wikitravel_guides that explains how to '''re-use Wikitravel guides'''. Basically, at the bottom of every article that has content copied from Wikitavel you would have to write something like ''This article is derived from the article wikitravel.org/en/Beijing on wikitravel.org/en. There it is published under the Creative Commons Attribution/Share-Alike 3.0 License. More details and the full list of contributors can be found on the associated wikitravel.org/wiki/en/index.php?title=Beijing&action=history history page and '''link back to Wikitravel'''. Please correct the attribution to point to the appropriate Wikitravel pages as soon as possible as otherwise this would be considered violation of our writers' copyrights. Let me know if you have any questions. You can contact me via email at awocial@internetbrand.com. Looking forward to hearing back from you. Cheers! [[User:AlexW|AlexW]] ([[User talk:AlexW|talk]]) 01:29, 28 June 2013 (CEST)

::: I created [[Template:Wikitravel]], which I put on [[Beijing]]. Feel free to edit the template and add it where you seem fit. That's about as much time as I can spend on this.
::: If any of the original writers have any problems with their work being copied I'll be happy to hear from them and I'll do my best to resolve their issues. Cheers, [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 01:12, 30 June 2013 (CEST)

:::: Guaka, this cannot be just a template. It has to be a proper attribution embedded within the article as this is a '''violation of the Attribution-Share License and the rights of Wikitravel.org as the original content creator'''. In view of the foregoing, Internet Brands, Inc. who owns Wikitravel.org, herby requests that you cease and desist copying content from Wikitravel.org, unless you '''provide proper attribution to Wikitravel.org wikitravel.org/shared/How_to_re-use_Wikitravel_guides'''. wikitravel.com/en/Beijing you have a page that is properly attributing Wikitravel.org and the article contributors. Please scroll to the bottom to see how the attribution should look like. We expect you to timely comply with the requests set forth herein. Should this use continue, Internet Brands, Inc. reserves all rights and remedies provided by law. Looking forward to your response. Warm regards, [[User:AlexW|AlexW]] ([[User talk:AlexW|talk]]) 23:45, 1 July 2013 (CEST)

:::::I've taken most of the site offline for now so that this can be properly resolved. I hope that makes all of you IB employees feel all warm inside. [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 00:56, 5 July 2013 (CEST)
:::::: Guaka, please let me know if there is any way I can help you with the attribution. Warm regards, [[User:AlexW|AlexW]] ([[User talk:AlexW|talk]]) 03:19, 9 July 2013 (CEST)

::::::: We checked all articles and deleted everything that could have possibly come from Wikitravel. No need for attribution anymore. Let me know if there's still a page that we missed that you want us to delete. [[User:Guaka|guaka]] ([[User talk:Guaka|talk]]) 10:58, 9 July 2013 (CEST)

== Combating spam ==

Could you install https://www.mediawiki.org/wiki/Extension:BlockAndNuke ? That would reduce the clicks needed until we're free of spam accounts. --[[User:Rumwerfer|Rumwerfer]] ([[User talk:Rumwerfer|talk]]) 16:41, 15 April 2020 (CEST)

Hackweek Spring 2020

2020-04-15T08:10:32Z

Rumwerfer: /* Organization Structures */ fix bullet points

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
|
|
|
|
|-
|17:00
|
|
|
|
|
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
* co-operatives / open co-ops
* gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

Hackweek Spring 2020

2020-04-15T08:08:53Z

Rumwerfer: /* Program */ make closing session 2h

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
| [[#Organization Structures | #Organization]]
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
|
|
|
|
|-
|17:00
|
|
|
|
|
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="3" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="7" rowspan="2" |Free hacking
|-
|20:00
|
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

=== Organization Structures ===

Coordinator: Nick

Stuff about creating and maintaining sustainable open source community projects.

Some concepts:
- co-operatives / open co-ops
- gift economies

I found a lot of interesting stuff through reading https://disco.coop/manifesto/.

And you can read what is kind of like my personal manifesto on my liberapay page --> https://liberapay.com/nicksellen/

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

React Migration Cheatsheet

2020-04-15T08:06:44Z

Rumwerfer:

{| class="wikitable"
|+
!Angular
!React
|-
|<code>someString</code>
|<code>import { useTranslation } from 'react-i18next';<br />const { t } = useTranslation('modulename');<br />{t('someString')}</code>
|-
|<code><someElement class="..."></code>
|<code><someElement className="..."></code>
|-
|<code><a ui-sref="alias"></code>
|<code><a href="path"></code>
|-
|<code><nowiki></nowiki></code>
|<code>{/* comment */}</code>
|-
|<code><someElement ng-if="condition"></code>
|<code>{condition && (<someElement>)}</code>
|-
|ng-repeat
|
|-
|ng-include
|
|-
|<code><section tr-boards="'...'"></code>
|<code><Board names="..."></code>
|}

Hackweek Spring 2020

2020-04-15T06:29:29Z

Rumwerfer: add feedback section

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
|
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
|
|
|
|
|-
|17:00
|
|
|
|
|
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="2" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="8" rowspan="2" |Free hacking
|-
|20:00
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

== Learnings ==

Feedback for future hackweeks

* We could make it clearer, which sessions are not coding-related or at least non-coders are welcome to contribute. Maybe a "Non-coding" badge for each session. This time, we unfortunately scared off someone from a discussion session because that wasn't clear.

Hackweek Spring 2020

2020-04-15T06:23:45Z

Rumwerfer: add content call (from mariano's proposal in slack)

Due to the CoViD-situation, we're having our [[Trustroots]] spring hackweek online-only.

'''When: 11.04.-19.04.2020.'''

For now, we're using our [https://codi.kanthaus.online/hackweek?edit hackweek pad] for planning. Please check-in there if you want to participate!

== Program ==
{| class="wikitable"
|+
!UTC+2
!Saturday 11th April
!Sunday 12th April
!Monday 13th April
!Tuesday 14th April
!Wednesday 15th April
!Thursday 16th April
!Friday 17th April
!Saturday 18th April
!Sunday 19th April
|-
|style="background:#CEF2E0 |'''09:30–10:00'''
|
| colspan="8" style="background:#CEF2E0 " |'''Check-in. Day presentation'''
|-
|-
|10:00
|
|
|
| [[#Support introduction]]
|
|
|
|
|
|-
|11:00
|
|
|
| References coding (mumble)
|
| [[#Translating Trustroots to other languages | #Translating]]
|
|
|
|-
|12:00
|
| rowspan="4" | [[#Migration to React]]
| rowspan="2" | [[#References discussion]]
|
|
|
|
|
|
|-
|13:00
|style="background:#CEF2E0 |'''[[#Welcome session]]'''
|
|
|
| [[#Joining Roots (Content) | #Content]]
|
|
|-
|14:00
| rowspan="6" | [[#Set up dev environment]] and enjoying the sun
|
|
|
|
|
|
|
|-
|15:00
|
|
|
|
|
|
|
|-
|16:00
|
|
|
|
|
|
|
|
|-
|17:00
|
|
|
|
|
|
|
|
|-
|18:00
|
|
|
|
|
|
|
|rowspan="2" style="background:#CEF2E0 "| '''Closing session'''
|-
|style="background:#CEF2E0 |'''18:30–19:00'''
| colspan="7" style="background:#CEF2E0 " |'''Check-out'''
|-
|19:00
| rowspan="2" | [[#Code walkthrough]]
| colspan="8" rowspan="2" |Free hacking
|-
|20:00
|}

== Sessions ==

=== Welcome session ===

Participants: Abel, Dario, Edvard, Ludovica, Marco, Mariano, Michal, Mikael, Nick

=== Setting up dev environment ===

everyone interested in getting started with development installs it on their own
* [https://team.trustroots.org/Install.html Manual] in our team guide
* if you need help, reach out on [[#Tools | Mumble or Slack]]

=== Code walkthrough ===

Coordinator: Nick

* Client / React
* Testing / Jest
* Server / Node

=== Migration to React ===

Edvard, Dario, Nick

[[React Migration Cheatsheet]]

=== References discussion ===
[https://meet.collective.tools/trustroots Jitsi Meet], [https://codi.kanthaus.online/trustroots-references Pad]

Coordinator: Mikael

* Vision about [https://github.com/Trustroots/trustroots/issues/718 References feature] and current state of development
* also trust metrics, invitation only feature and other related things

=== Support introduction ===

Coordinator: Dario

Answering messages from the community – introduction to the support tools and common issues people have

=== Translating Trustroots to other languages ===

Coordinator: Marco

Getting started with our new translation tool [https://hosted.weblate.org/projects/trustroots Weblate]

=== Joining Roots (Content) ===

Coordinator: Mariano

In this call I would like to get to know everybody in our community that is interested in helping fostering Content creation. We will be then getting to know s little bit more of each other on a first moment and then when we are more familiarised with each we will start making the outlines of our project.

I have some ideas of what is it that we could work with and I'll leave them here for you to read.

but hey! Those are not in any way necessary to be answered in order to participate of the call. You may join without contributing to it, tho I'm really looking forward to that! The idea is just to give you a script, so that you can prepare yourself, for what I have in mind to it.

I came up with the following:
* An introduction
Who are you? What do you do for living? How have you heard of Trustroots? for how long have you been involved? Would you like to participate on this project creating some kind of content, if so what would it be ?
* Roots of Trust Highlight Stories
Have you ever met in person anyone of the Trustroots community? What's the story behind it? Have that person received you in their house? What was something funny that happened?
* The Roots that stood the Pandemia
How are you holding up on this new scenario that our world is facing? How is life now where you live? What has been the toughest for you?
* I have a dream that in Trustroots there will be ________ .

== Tools ==

=== Communication ===

(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)

* Text chat: #collective channel on [https://team.trustroots.org/Chat.html our slack workspace]
* Voice chat: #trustroots channel on [https://wiki.ecotopiabiketour.net/Mumble_setup ecotopia's mumble server]
* Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
* Pair programming: Visual Studio Code with [https://visualstudio.microsoft.com/services/live-share/ Live Share Extension]

=== Shared music streaming ===

* [https://stream.abovethebeat.com/trustroots Stream] (open in browser or media player)
* [https://stream.abovethebeat.com/trustroots/ui/ see/edit playlist]
* add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com

[[Category:Trustroots]]

Hackweek Spring 2020

2020-04-14T17:39:15Z

Rumwerfer: /* Program */

Hackweek Spring 2020

2020-04-14T17:35:49Z

Rumwerfer: /* Program */ change evening call time

Hackweek Spring 2020

2020-04-14T08:07:14Z

Rumwerfer: /* Program */

Hackweek Spring 2020

2020-04-14T07:56:22Z

Rumwerfer: /* Program */

Hackweek Spring 2020

2020-04-13T16:29:04Z

Rumwerfer:

React Migration Cheatsheet

2020-04-13T13:07:13Z

Rumwerfer:

Hackweek Spring 2020

2020-04-13T13:02:46Z

Rumwerfer: /* References discussion */

Hackweek Spring 2020

2020-04-13T12:36:56Z

Rumwerfer: /* Program */

Hackweek Spring 2020

2020-04-13T09:52:20Z

Rumwerfer: /* References discussion */

Hackweek Spring 2020

2020-04-13T07:53:07Z

Rumwerfer: /* References discussion */ github issue

React Migration Cheatsheet

2020-04-13T07:20:19Z

Rumwerfer: init

{| class="wikitable"
|+
!Angular
!React
|-
|<code>someString</code>
|<code>import { useTranslation } from 'react-i18next';<br />const { t } = useTranslation('pages');<br />{t('someString')}</code>
|-
|<code><someElement class="..."></code>
|<code><someElement className="..."></code>
|-
|<code><a ui-sref="alias"></code>
|<code><a href="path"></code>
|-
|<code><nowiki></nowiki></code>
|<code>{/* comment */}</code>
|-
|<code><someElement ng-if="condition"></code>
|<code>{condition && (<someElement>)}</code>
|-
|ng-repeat
|
|-
|ng-include
|
|-
|<code><section tr-boards="..."></code>
|<code><Board names="..."></code>
|}

Hackweek Spring 2020

2020-04-12T15:00:20Z

Rumwerfer: add react migration session

Hackweek Spring 2020

2020-04-12T14:52:37Z

Rumwerfer: /* Code walkthrough */ contents

Hackweek Spring 2020

2020-04-12T07:52:21Z

Rumwerfer: /* Translations? */ weblate link

Hackweek Spring 2020

2020-04-11T20:26:16Z

Rumwerfer: /* Tools */ music streaming

Hackweek Spring 2020

2020-04-11T19:50:00Z

Rumwerfer: /* Program */ repair table

Hackweek Spring 2020

2020-04-11T19:49:33Z

Rumwerfer: add support session

Hackweek Spring 2020

2020-04-11T17:33:30Z

Rumwerfer: /* Tools */ live share

Hackweek Spring 2020

2020-04-11T15:22:00Z

Rumwerfer: /* Tools */ add jitsi

Hackweek Spring 2020

2020-04-11T13:32:47Z

Rumwerfer: /* Sessions */

Hackweek Spring 2020

2020-04-11T13:24:15Z

Rumwerfer: /* Sessions */ add two sessions that don't yet have a time slot

Hackweek Spring 2020

2020-04-11T13:17:14Z

Rumwerfer: /* Sessions */ ref

Hackweek Spring 2020

2020-04-11T13:07:27Z

Rumwerfer: