Trustroots Wiki - User contributions [en]

Meeting Minutes/2020-06-01 Regular Meeting

2020-06-01T16:47:25Z

Nicksellen: /* Agenda */

= Trustroots Meeting =

* Date: 2020-06-01 '''18:00''' UTC+2/CEST
* Facilitator: Nick
* Present: Mariano, Julien, Michael, Gabriel, Nick

== Agenda ==

* hellos and checkin
* integrate riot? integrate the matrix protocol without riot?
** don’t know who added this, they weren’t in the call
* Potentially setting time for Tribe video call discussion /Martin
** https://poll.disroot.org/v7WhGQTcbsWOWei8
** Looking at the poll we chose 2020-06-05 19:00 CEST
* Update from the React Native workbench
** lots of progress!
** automated deployments with fastlane mostly setup
** you can join the test builds in play store (send you play store account email address to Michael)
** 2-3 weeks should be realistic to get something ready to beta release
** invitation for people to join in react native development :)
*** lots to do still!
*** Mikael started at some new wireframes for new parts of the app (that aren’t already on the site)
*** especially welcome for design-orientated people
*** really would like to work with some people
*** always ready to walk through code in 1on1
** waiting Google approval for public beta deployment
** most “blocking” (no urgency) aspects are:
*** user blocking (for iOS store)
*** UI/UX stuff, e.g. for profile page

== Action points and outcomes ==

* if you want access to the android test builds send Michael your play store account email address
* if you can help with any mobile UI/UX topics, goto #mobile and chat to Michael
* user blocking feature would be really great to have ready (eventually it will be the blocker to iOS release)
* call about renaming tribes is scheduled for next Friday - 2020-06-05 19:00 CEST

Meeting Minutes/2020-06-01 Regular Meeting

2020-06-01T16:47:14Z

Nicksellen: Created page with "= Trustroots Meeting = * Date: 2020-06-01 '''18:00''' UTC+2/CEST * Facilitator: Nick * Present: Mariano, Julien, Michael, Gabriel, Nick == Agenda == * hellos and checkin *..."

= Trustroots Meeting =

* Date: 2020-06-01 '''18:00''' UTC+2/CEST
* Facilitator: Nick
* Present: Mariano, Julien, Michael, Gabriel, Nick

== Agenda ==

* hellos and checkin
* integrate riot? integrate the matrix protocol without riot?
** don’t know who added this, they weren’t in the call
* Potentially setting time for Tribe video call discussion /Martin
** https://poll.disroot.org/v7WhGQTcbsWOWei8
** Looking at the poll we chose 2020-06-05 19:00 CEST
* Update from the React Native workbench
** lots of progress!
** automated deployments with fastlane mostly setup
** you can join the test builds in play store (send you play store account email address to Michael)
** 2-3 weeks should be realistic to get something ready to beta release
** invitation for people to join in react native development :)
*** lots to do still!
*** Mikael started at some new wiregrames for new parts of the app (that aren’t already on the site)
*** especially welcome for design-orientated people
*** really would like to work with some people
*** always ready to walk through code in 1on1
** waiting Google approval for public beta deployment
** most “blocking” (no urgency) aspects are:
*** user blocking (for iOS store)
*** UI/UX stuff, e.g. for profile page

== Action points and outcomes ==

* if you want access to the android test builds send Michael your play store account email address
* if you can help with any mobile UI/UX topics, goto #mobile and chat to Michael
* user blocking feature would be really great to have ready (eventually it will be the blocker to iOS release)
* call about renaming tribes is scheduled for next Friday - 2020-06-05 19:00 CEST

Meeting Minutes/2020-05-25 Regular Meeting

2020-05-26T17:00:13Z

Nicksellen: /* Agenda */

= Trustroots Meeting =

* Date: 2020-05-25 '''18:00''' UTC+2/CEST
* Facilitator: Nick/Mikael
* Present: Dario, Ying, Michael, Mikael, Bryan, Ludo, Gabriel, Martin (secretly listening)

== Agenda ==

* presentation of a few stats (Mikael)
** Brazilian has a very high conversation rate!
** showing a lot of new people arriving from Social media after the CS announcement
* hellos and checkin
*# what is your current life situation/context?
*#* Nick: kind of full-time on these volunteer/opensource projects, low income, move around quite a bit
*#* Mikael: co-founder of TR, not much time right now, kids and job
*#* Ludo: living in Italy, studying/working in social work, not much spare time, graduating soon and hoping for more time, started at hackweek
*#* Michael: currently living/breahthing/loving software dev in south germany, local stuff, information systems, lots of spare time, jumping around projects
*#* Ying: first time in meeting! in Zurich, CH, between jobs, has quite a bit of time right now, but in a few weeks maybe working full time again
*#* Dario: part of TR for 1.5y, mostly focused on university degree (computer science), end of money is near, so trying to rush through, more time in uni than anticipated. ~5h/week for trustroots
*#* Bryan: working full time in Hell-sinky, furloughed 1day/week right now, normally not much time for stuff but like sticking around
*#* Martin: living in Turin (like Ludo) to be close to the mountains
*#* Gabriel: phd student in sweden, for 1y to work on thesis (on robotics), working with students in brazil
*# what are you motivated to contribute to trustroots?
*#* Nick: a bit of everything, and helping people, when there are other people doing all the other stuff, maybe I revert to development more, a lot interested in organizational structures too, and abstract philosophising stuff
*#* Mikael: trying to not be a bottleneck, have opinions/thoughts, developer/designer/manager, aiming to do more design and less coding
*#* Ludo: in support team, replyng to emails, reports, technical issues, newsletter messages, also helping with translations
*#* Michael: contributing swiss army knife skills of react native, already started!
*#* Ying: joined because of CS incident, looking for an alternative and found TR was open source and volunteer made, why not contribute! not really high-tech tech guy, analytics/mathematics background and financial stuff, lots of data related stuff (not much finance data needed here :)) short term, help out with some basic analytics, but need to get familiar with infrastructure, how it works. long term: maybe we can apply some advanced analytic tools, machine learning if it fits in the scope. e.g. enhance security feature from the platform.
*#* Dario: mostly answering support messages, and organizational stuff, github issues, motivated to get more active with coding
*#* Bryan: groupy from snowdrift.coop, have been around the whole time, socially if nothing else, a cool project! like being part of a whole world of projects that outside capitalism and connecting the projects. was lead dev for snowdrift.coop (funding opensource) and that’s current focus still in free time. feels very aligned.
*#* Martin: Plenty motivtion, less skills, do what I can when there’s time.
*#* Gabriel: old CS user, really like the community/idea, hospitality/sharing, missed the best time of CS
*# what do you need from others?
*#* Nick: uuummm
*#* Mikael: not sure, people to take ownership, and be proactive
*#* Ludo: mostly asking from the support team as hard to get into the tasks, also random questions about computers :) (and private issues, etc, feel very supported)
*#* Michael: pretty fine navigating system right now, would like to see reporting issues tackled to get past app-store barriers
*#* Ying: a lot of help from technical side, and what is the plan, how do we organise, first time on open source project, a lot to learn
*#* Dario: technical introduction… glad I can ask any dumb question on slack, enjoy the communication culture
*#* Bryan: not a lot! mostly spectating.
*#* Martin: not much unless trying to do smth I don’t know, happy to talk and chat with ye all though!
*#* Gabriel: some help understanding how it’s working, workingon dev issues
*# what can offer to others?
*#* Nick: anything, ask me!
*#* Mikael: unblocking people to do things, connector
*#* Ludo: happy to feel useful, in both psychical and practical sense, so just ask :) happy to discuss about visions and meanings and shades of the words used in traslation process.
*#* Michael: love and passion! enjoying motivation and can offer opinions!
*#* Ying: not sure yet, always available at the moment, so feel free to share things with him, a lot of curiousity right now
*#* Dario: can introduce new people to support team tools if interested, doing a lot of moderator/organizational stuff in local groups but not so confident to do that in English right now
*#* Bryan: just, hi, I’m here!
*#* Martin: more words than perhaps striclty required for discussions, thoughts, ideas ect. Some language expertise :D
*#* Gabriel: can work on the dev project, experiened with nodejs, curious with the design part too, evaluating frameworks, create reusable libraries, refactoring, testing
* Focused developer call (Mikael)
** we’ve had main call for a while, still figuring out structure
** support has their own call on wednesday
** would be nice to have a call for each “team”
** once a week or every two weeks
** what technical tasks people are working on
** idea to have working groups for temporary issues that come up
* A log for async topics/decisions? Similar to Github but for non-development work. (Mikael)
** github is great, but should be more technical focused
** and to capture things that happen in slack in a more permanent way
** we tried discussion forum before (discourse) meta.trustroots.org
*** but we didn’t define what it is for
*** random people would drop in comments
*** (we had previously invited the community, but weren’t ready)
** thinking more like a wiki where you put stuff, rather than a discussion place
** at work (automaticc) they have loads of blogs (“lets put everything in a wordpress”), e.g. putting meeting notes in blog posts, and use comments, proposals go into a post, and discussion goes under, can get email updates/rss feeds etc
** maybe public, but clearly for internal use
** not opposed to forum, but harder to work out mechanics and culture
** what is the difference compared to meta.trustroots.org?
*** if it was just for the team, not thte community, that should work no?
*** seems the same as a blog?
*** mikael: more simple/focused, like a log, but more async
** examples of what it might be used for:
*** meeting notes
*** ideas, bigger discussions or proposals
*** decision log
** could discuss in a document (e.g. google docs) with comments?
*** seeing it more like a stream
* Current state of the React Native art (Michael)
** login works
** thread list works
** map shows up
** offline works
** navigation slide-in works
** looking forward to proof of concept!
** plan is to implement all the features on the site
** Mikael: thought to simplify the client-side image logic fetching and have an API for images. Otherwise we implement the same thing double in web-client and mobile-client. https://github.com/Trustroots/trustroots/issues/982
** Next:
** reading messages, sending messages, marking messages read,
** i18n? https://www.i18next.com/
** Need: deploy repo, new public repo for code
* Change of “Tribes” to “Circles”, “Communities”, “Groups”, “Other”?
** Suggestions how to decide?
** Need for layout change to make them seem less essential?
** maybe a good chance to create a working group for work it through
*** one of the people that raised the issue was invited to slack
* Current state of references (mini update) (Nick)
** overview issue https://github.com/Trustroots/trustroots/issues/1493
* Current state of translations (mini update) (Nick)
** overview issue https://github.com/Trustroots/trustroots/issues/1485

== Action points and outcomes ==

* propose a time for a regular tech call [Mikael]
* continue discussion about blog/forum for team in slack [Mikael]
* create react-native public repo for app [Mikael/Nick]
* create react-native private repo for fastlane config [Mikael/Nick]
* communicate to the person about the tribes renaming [Ludo]
* writing in slack to announce the working group for tribes rename [Nick]

Meeting Minutes/2020-05-25 Regular Meeting

2020-05-26T16:43:51Z

Nicksellen: Created page with "= Trustroots Meeting = * Date: 2020-05-25 '''18:00''' UTC+2/CEST * Facilitator: Nick/Mikael * Present: Dario, Ying, Michael, Mikael, Bryan, Ludo, Gabriel, Martin (secretly li..."

= Trustroots Meeting =

* Date: 2020-05-25 '''18:00''' UTC+2/CEST
* Facilitator: Nick/Mikael
* Present: Dario, Ying, Michael, Mikael, Bryan, Ludo, Gabriel, Martin (secretly listening)

== Agenda ==

* presentation of a few stats (Mikael)
** Brazilian has a very high conversation rate!
** showing a lot of new people arriving from Social media after the CS announcement
* hellos and checkin
*# what is your current life situation/context?
*#* Mikael: co-founder of TR, not much time right now, kids and job
*#* Ludo: living in Italy, studying/working in social work, not much spare time, graduating soon and hoping for more time, started at hackweek
*#* Michael: currently living/breahthing/loving software dev in south germany, local stuff, information systems, lots of spare time, jumping around projects
*#* Ying: first time in meeting! in Zurich, CH, between jobs, has quite a bit of time right now, but in a few weeks maybe working full time again
*#* Dario: part of TR for 1.5y, mostly focused on university degree (computer science), end of money is near, so trying to rush through, more time in uni than anticipated. ~5h/week for trustroots
*#* Bryan: working full time in Hell-sinky, furloughed 1day/week right now, normally not much time for stuff but like sticking around
*#* Martin: living in Turin (like Ludo) to be close to the mountains
*#* Gabriel: phd student in sweden, for 1y to work on thesis (on robotics), working with students in brazil
*# what are you motivated to contribute to trustroots?
*#* Mikael: trying to not be a bottleneck, have opinions/thoughts, developer/designer/manager, aiming to do more design and less coding
*#* Ludo: in support team, replyng to emails, reports, technical issues, newsletter messages, also helping with translations
*#* Michael: contributing swiss army knife skills of react native, already started!
*#* Ying: joined because of CS incident, looking for an alternative and found TR was open source and volunteer made, why not contribute! not really high-tech tech guy, analytics/mathematics background and financial stuff, lots of data related stuff (not much finance data needed here :)) short term, help out with some basic analytics, but need to get familiar with infrastructure, how it works. long term: maybe we can apply some advanced analytic tools, machine learning if it fits in the scope. e.g. enhance security feature from the platform.
*#* Dario: mostly answering support messages, and organizational stuff, github issues, motivated to get more active with coding
*#* Bryan: groupy from snowdrift.coop, have been around the whole time, socially if nothing else, a cool project! like being part of a whole world of projects that outside capitalism and connecting the projects. was lead dev for snowdrift.coop (funding opensource) and that’s current focus still in free time. feels very aligned.
*#* Martin: Plenty motivtion, less skills, do what I can when there’s time.
*#* Gabriel: old CS user, really like the community/idea, hospitality/sharing, missed the best time of CS
*# what do you need from others?
*#* Nick: uuummm
*#* Mikael: not sure, people to take ownership, and be proactive
*#* Ludo: mostly asking from the support team as hard to get into the tasks, also random questions about computers :) (and private issues, etc, feel very supported)
*#* Michael: pretty fine navigating system right now, would like to see reporting issues tackled to get past app-store barriers
*#* Ying: a lot of help from technical side, and what is the plan, how do we organise, first time on open source project, a lot to learn
*#* Dario: technical introduction… glad I can ask any dumb question on slack, enjoy the communication culture
*#* Bryan: not a lot! mostly spectating.
*#* Martin: not much unless trying to do smth I don’t know, happy to talk and chat with ye all though!
*#* Gabriel: some help understanding how it’s working, workingon dev issues
*# what can offer to others?
*#* Nick: anything, ask me!
*#* Mikael: unblocking people to do things, connector
*#* Ludo: happy to feel useful, in both psychical and practical sense, so just ask :) happy to discuss about visions and meanings and shades of the words used in traslation process.
*#* Michael: love and passion! enjoying motivation and can offer opinions!
*#* Ying: not sure yet, always available at the moment, so feel free to share things with him, a lot of curiousity right now
*#* Dario: can introduce new people to support team tools if interested, doing a lot of moderator/organizational stuff in local groups but not so confident to do that in English right now
*#* Bryan: just, hi, I’m here!
*#* Martin: more words than perhaps striclty required for discussions, thoughts, ideas ect. Some language expertise :D
*#* Gabriel: can work on the dev project, experiened with nodejs, curious with the design part too, evaluating frameworks, create reusable libraries, refactoring, testing
* Focused developer call (Mikael)
** we’ve had main call for a while, still figuring out structure
** support has their own call on wednesday
** would be nice to have a call for each “team”
** once a week or every two weeks
** what technical tasks people are working on
** idea to have working groups for temporary issues that come up
* A log for async topics/decisions? Similar to Github but for non-development work. (Mikael)
** github is great, but should be more technical focused
** and to capture things that happen in slack in a more permanent way
** we tried discussion forum before (discourse) meta.trustroots.org
*** but we didn’t define what it is for
*** random people would drop in comments
*** (we had previously invited the community, but weren’t ready)
** thinking more like a wiki where you put stuff, rather than a discussion place
** at work (automaticc) they have loads of blogs (“lets put everything in a wordpress”), e.g. putting meeting notes in blog posts, and use comments, proposals go into a post, and discussion goes under, can get email updates/rss feeds etc
** maybe public, but clearly for internal use
** not opposed to forum, but harder to work out mechanics and culture
** what is the difference compared to meta.trustroots.org?
*** if it was just for the team, not thte community, that should work no?
*** seems the same as a blog?
*** mikael: more simple/focused, like a log, but more async
** examples of what it might be used for:
*** meeting notes
*** ideas, bigger discussions or proposals
*** decision log
** could discuss in a document (e.g. google docs) with comments?
*** seeing it more like a stream
* Current state of the React Native art (Michael)
** login works
** thread list works
** map shows up
** offline works
** navigation slide-in works
** looking forward to proof of concept!
** plan is to implement all the features on the site
** Mikael: thought to simplify the client-side image logic fetching and have an API for images. Otherwise we implement the same thing double in web-client and mobile-client. https://github.com/Trustroots/trustroots/issues/982
** Next:
** reading messages, sending messages, marking messages read,
** i18n? https://www.i18next.com/
** Need: deploy repo, new public repo for code
* Change of “Tribes” to “Circles”, “Communities”, “Groups”, “Other”?
** Suggestions how to decide?
** Need for layout change to make them seem less essential?
** maybe a good chance to create a working group for work it through
*** one of the people that raised the issue was invited to slack
* Current state of references (mini update) (Nick)
** overview issue https://github.com/Trustroots/trustroots/issues/1493
* Current state of translations (mini update) (Nick)
** overview issue https://github.com/Trustroots/trustroots/issues/1485

== Action points and outcomes ==

* propose a time for a regular tech call [Mikael]
* continue discussion about blog/forum for team in slack [Mikael]
* create react-native public repo for app [Mikael/Nick]
* create react-native private repo for fastlane config [Mikael/Nick]
* communicate to the person about the tribes renaming [Ludo]
* writing in slack to announce the working group for tribes rename [Nick]

Meeting Minutes/2020-05-20 Mobile Discussion

2020-05-24T09:07:13Z

Nicksellen: Created page with " Who: Michael, Theo, Nick, Mikael When: 2020-05-20 What: React native mobile app; next steps? - Michael would be focusing on writing a react native proof of concept with so..."

Who: Michael, Theo, Nick, Mikael

When: 2020-05-20

What: React native mobile app; next steps?

- Michael would be focusing on writing a react native proof of concept with some basics

- Longer term goal to write Trustroots features in native way in mobile app, vs having them accessible via webview

- For now just write proof of concept with react native, and decide/think about if to use webview later on

- Start in new repository to keep it lightweight, consider in longer term to bring it into `/trustroots` repo to have monorepo approach. Starting in separate repo just is easier and we don't need to deal with any complexity that e.g. dealing with CI setup might bring. Monorepo can be useful way to encourage code-sharing on data-layer level across web & mobile.

- Start with Expo.io framework as the current app uses it as well and it's easy to jump to development with it/implement notifications etc. All the features might not be able to doable in expo in long term, so at some point we might need to drop it out. Nobody has strong feelings about keeping it; it's primary use was to ease up getting something out with little effort.

- Michael's proof of concept something concrete to talk about, to choose tech and decide what to do

- Release incomplete beta-release for small scale testing

- Iterate on this.

- Consider how would ideal authentication mechanism look like? Previous native mobile app attempted to use cookies in header requests as a simple mechanism. Trustroots uses Passport.js so it might be possible to plug something existing to it easily that's useful for mobile.

- Both Michael and Theo are available to work on this. :-)

- Nick and Mikael would like not super actively participate in mobile-development, but want to familiarize with it so that they can understand, test, fix, deploy, etc it. This is to ensure longevity of the project by having people who understand little bit about everything around.

Meeting Minutes/2020-05-18 Regular Meeting

2020-05-18T16:11:35Z

Nicksellen: Created page with "= Trustroots Meeting = * Date: 2020-05-18 * Facilitator: Mikael * Present: Mikael, Julien, Ludo, Philipp, Nick, Gary, Dario, Noah, Gabriel, Mauro, Martin, Marco == Agenda ==..."

= Trustroots Meeting =

* Date: 2020-05-18
* Facilitator: Mikael
* Present: Mikael, Julien, Ludo, Philipp, Nick, Gary, Dario, Noah, Gabriel, Mauro, Martin, Marco

== Agenda ==

* New members and volunteers (welcome! 👋)
* Look into stats:
** https://grafana.trustroots.org/
** signups up to level pre-covid19
** we’ll need to check in few weeks how’s the impact otherwise
* CS switches to paywall
** Do we do something? What. Not this please: https://trustroots.slack.com/files/U08SEHYCC/F013TMNFLKC/screenshot_20200518-105848_facebook.jpg
*** already knew they were going to do this on 22nd april, were just deciding the price
*** a lot of people are complaining in groups on facebook
*** could be useful to just mention trustroots there instead of trying to rush new features
*** also reddit is a place where these discussions happen
*** new people should understand that trustroots is not just the same as CS
*** idea: a blog post to explain this perspective (e.g. we don’t have references, but it’s coming, etc…)
** CS importer? https://github.com/Trustroots/trustroots/issues/1080
** CS had a much more international community than we have until now (very EU-centric). Any ideas on how to keep the first wave of immigrants in scarcely filled countries like the US active, so that the community can grow there in the future?
** announcement of Edvard: Preparing a workshop on organizatinal development for the next weeks
** Make a blog post for people to point to. [Julien]
** Blog post about references. [Mikael]
*** How to use features as they are now to fullfill needs for references? -> put to blog post
*** Focus ahead by making post more about Trustroots and future, rather than about Couchsurfing and about past.
*** People are seeking for answers; we also noticed that CS did what they did. Our project can be answer to them, invite to participate if they want. Elaborate on our values.
** Consolidate little more where we are with references, see next steps to get it out.
** Idea for newsletter? people who have joined trustroots recently since CS change, people to articulate positive vision
* People want to give us money
** Should we even?
** Liberapay
** bountysource (fee: 10%)
** opencollective (fee is dependent on which “fiscal host” you are part of)
** there are expenses for servers etc, but they are currently covered by people who are on the board and are not that big compared to the effort of setting up financial infrastructure and bookkeeping
** did imagine trustroots would accept donations at some point and distribute as salary somehow, it’s a big and interesting topic to consider how to distribute it and maybe we can start that conversation soon
** big question is how to use it, not the technical bit of how it gets to bank account
** salaries could be for people that don’t have financial security to contribute at the moment
** actual numbers on the existing finances and tax admin burden, financial burden in a thousands/year, finance admin costs more like hundreds/year, idea was that approx half a salary amount of money makes the difference, but spreading money across more people is another direction
** collecting thousands/year would be around the threshold where it might make sense to setup the infrastructure for this (admin, fundraising, etc…)
** bewelcome collects ~3000-4000/year, they have a treasurer to handled expenses/bookkeeping
** requires some switch to be start asking for donations
** basic important principle of transparency and authenticity
* FYI: sent iOS app for review to Apple again, waiting to hear back.
** We’ll need an email to be sent to 870 people who asked to be informed when it’s out. Any volunteers? :-)
*** [Noah] already sent out 40k msg for the hackweek and can do that again ;)
**** Julien helps to write email
*** [Nick] where are the email addresses? [on ideas.trustroots.org/wp-admin -> feedback -> export CSV]
* Gary would like to help with communications <3
** Julien and Mikael
* Weekly call: Are there other time slots that would work for most people?
** Dario won’t be able to join at Monday 17 UTC+2 for the next 2 months

== Action points and outcomes ==

* Blog post [Mikael to start draft]
** Talk about money. How little we need, how it’s not a problem (and who currently pays it?). Maybe point donations to the orgs listed in the thread below.
** Talk about community
** Talk about transparency, organization, empowerment.
* Somebody to write email to iOS users [Somewhere between Noah, Julien, and Gary!]
* Import iOS app people from wordpress into mailtrain [Nick]
* Start a thread on Slack about collecting ideas on orgs to forward generosity to. [Julien]
* Organise a conversation about Money. [Who? otherwise I, Nick, would just suggest we just make a #money channel in slack and start mulling over higher level thoughts…]
** Yes yes yes!
* Create a doodle poll to find a new time for weekly meeting that more people can join [Dario]

== Next meeting ==

* Next Date: 2020-05-25 17:00 UTC+2/CEST (unless we pick a new time before then… so check again!)
* Next Facilitator: Julien again unless anyone else volunteers

Meeting Minutes/2020-04-16 Hackweek - mobile discussion

2020-05-11T11:53:40Z

Nicksellen:

We didn't take structured notes, but here's a slack thread conversation (source: https://trustroots.slack.com/archives/C08SENA9Z/p1586968132213200?thread_ts=1586967195.211900&cid=C08SENA9Z) (edited for relevance/brevity)

'''Mikael'''

the biggest priority for the current mobile app was to;
- folks have something to install to have TR icon on their phones
- have push notifications working on their phones (I cannot stress how important this is)

'''theo'''

understood, and the existing mobile app fulfills these 2 points?

'''Mikael '''

yep, and not much anything else :grin:

'''Mikael '''

well, it’s not on ios actually, so it half accomplishes them :wink:

'''Mikael '''

I’ve recently done little bit of work to make things work for apple too, we should re-send it for review to their store finally.

'''theo '''

@rumwerfer we chatted about two main approaches:

1. 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

2.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. Would be cool to hear your thoughts?
:+1:
1

'''rumwerfer '''

Thanks. I don't really have an opinion or knowledge on this topic. Number 2 also sounds more beneficial to the community, but I'll leave that to others. Is the existing app ready-to-go to iOS app store? Mind if I post your summary on the wiki? (edited)

'''theo '''

yeah for sure you can post it, I'd be interested to hear what others have to say. I had some trouble running the existing app in the iOS simulator last night I can try again, as far as I understand it was at some point submitted for review and rejected, I'm guessing due to an older react native version bundling the deprecated WebView API? but I think that shouldn't be an issue anymore with the latest expo.

'''Mikael'''

it was rejected due us having google play store badge visible on ios :grin:
:facepalm3:
1

'''Mikael'''

fixed in https://github.com/Trustroots/trustroots/pull/1139 (edited)

'''Mikael'''

https://github.com/Trustroots/trustroots-expo-mobile/issues/10#issuecomment-528238998

'''simison'''

Comment on #10 Bundle an iOS version
Next steps:
☑︎ hide store buttons when wrapping in webview Trustroots/trustroots#1139
☐ re-submit to apple for review (@simison). I have the Apple dev account for Trustroots already.
☐ when accepted, update app store links to point to download page
☐ send email to people who asked to be notified when iOS app is out
<https://github.com/Trustroots/trustroots-expo-mobile|Trustroots/trustroots-expo-mobile>Trustroots/trustroots-expo-mobile | Sep 5th, 2019 | Added by GitHub

'''nick'''

if option 2. was the one to go for, I would wonder what the users would make of having the webview version available, then a future version suddenly has all the features ripped out :confused: ... although I think, as we came to realise on the call, whatever we do there will be some users complaining about the approach, it's hard to achieve this slick and cohesive user experience with this kind of project.

'''theo'''

depending on how many people there are wanting to use it we could have a longer open beta type thing using test flight and google beta program thing, so that there isn't a hard switch to a newer, less feature rich version?

'''Mikael'''

I think we’d anyway have some kind of “open website on browser” type link on the sidebar? so the features would still be discoverable

'''nick'''

@theo I didn't quite get the sequence of things there, did you mean:

* release iOS app as-is in normal release mode as soon as we can
* once ready start publishing the new (approach 2) app in open beta
* after some time, switch over (edited)

'''theo'''

yeah that was the rough idea, what do you think?

'''nick'''

yes, sounds good to me!

Meeting Minutes/2020-05-04 Regular Meeting

2020-05-04T15:59:28Z

Nicksellen: Created page with "= Trustroots Meeting = * Date: 2020-05-04 17:00 UTC+2 / CEST * Facilitator: Nick * Participants: Nick, Julien, Mikael, Edvard == Agenda == * hellos / check-ins * code of co..."

= Trustroots Meeting =

* Date: 2020-05-04 17:00 UTC+2 / CEST
* Facilitator: Nick
* Participants: Nick, Julien, Mikael, Edvard

== Agenda ==

* hellos / check-ins
* code of conduct read through (Martin/Nick)
** https://codi.kanthaus.online/trustroots-coc?edit
* Newsletter update (Julien)
** 8 people had joined newsletter group at hackweek co-ordinated by Mariano
** pad was started for work, but not much progress
** Julien has been collecting content, about 50% done :)
** too much content for a newsletter, thinking to send teasers in newsletter and full content in blog
** Mikael suggests to focus on smallest first step goal to not get paralyzed with bigger goal
** Julien feels it’s not his project, and would like to recruit Mariano back to support with work :)
** Mikael was wondering if there could have been new-volunteer issue with task ownership, Julien feels good enough to continue
** Nick will send a short recap about trustroots hackweek going online-only
** discussion about formatting, simple plain HTML is fine (or start with markdown and convert), for more complex layouts, need email clients don’t support much HTML so need to use “email-specific” templates, mailtrain has some features for this if desired, but needs some learning
** importance of having proper footer (see existing trustroots emails, or templates in mailtrain)
** need unsubscribe link (link to settings)
** mention that possible we are getting more problems with being seen as spam so have to be careful about it
* non-binary followup (Nick)
** two possible steps we discussed previously that we could do after the storm dies down (which it has by now)
*** contacting the weblate people to let them know what happened (Mikael)
*** me (Nick) personally wanted to share/warn/inform a wider set of people about this incident (contributing to the public/wider debate on such topics)
**** Nick will write personally on his mastodon, and possible a blog post in the future follows, Mikael was interested in finding out if anybody has any tips
** Weblate thread: https://hosted.weblate.org/translate/trustroots/users/nb_NO/?&offset=38#comments
* meta: call structure/rhythm (Nick)
** does the timing still work, nick is wanting to have other people to help co-ordinating/facilitating the call
** … we went into discussions of the role/purpose of the board, legal responsiblities, etc…

== Action points and outcomes ==

* Mikael will write to weblate about the non-binary topic sometime
* Julien will proceed with newsletter with offer of help/support from Nick
* Nick will try and stimulate people to read/comment on the CoC

== Next meeting ==

* Next Date: 2020-05-11 17:00 UTC+2 / CEST
* Next Facilitator: Julien

Meeting Minutes/2020-04-16 Hackweek - mobile discussion

2020-04-21T10:48:33Z

Nicksellen: Created page with "We didn't take structured notes, but here's a slack thread conversation (source: https://trustroots.slack.com/archives/C08SENA9Z/p1586968132213200?thread_ts=1586967195.211900&..."

We didn't take structured notes, but here's a slack thread conversation (source: https://trustroots.slack.com/archives/C08SENA9Z/p1586968132213200?thread_ts=1586967195.211900&cid=C08SENA9Z) (edited for relevance/brevity)

'''Mikael'''

the biggest priority for the current mobile app was to;
- folks have something to install to have TR icon on their phones
- have push notifications working on their phones (I cannot stress how important this is)

'''theo'''

understood, and the existing mobile app fulfills these 2 points?

'''Mikael '''

yep, and not much anything else :grin:

'''Mikael '''

well, it’s not on ios actually, so it half accomplishes them :wink:

'''Mikael '''

I’ve recently done little bit of work to make things work for apple too, we should re-send it for review to their store finally.

'''theo '''

@rumwerfer we chatted about two main approaches:

1. 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

2.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. Would be cool to hear your thoughts?
:+1:
1

'''rumwerfer '''

Thanks. I don't really have an opinion or knowledge on this topic. Number 2 also sounds more beneficial to the community, but I'll leave that to others. Is the existing app ready-to-go to iOS app store? Mind if I post your summary on the wiki? (edited)

'''theo '''

yeah for sure you can post it, I'd be interested to hear what others have to say. I had some trouble running the existing app in the iOS simulator last night I can try again, as far as I understand it was at some point submitted for review and rejected, I'm guessing due to an older react native version bundling the deprecated WebView API? but I think that shouldn't be an issue anymore with the latest expo.

'''Mikael'''

it was rejected due us having google play store badge visible on ios :grin:
:facepalm3:
1

'''Mikael'''

fixed in https://github.com/Trustroots/trustroots/pull/1139 (edited)

'''Mikael'''

https://github.com/Trustroots/trustroots-expo-mobile/issues/10#issuecomment-528238998

'''simison'''

Comment on #10 Bundle an iOS version
Next steps:
☑︎ hide store buttons when wrapping in webview Trustroots/trustroots#1139
☐ re-submit to apple for review (@simison). I have the Apple dev account for Trustroots already.
☐ when accepted, update app store links to point to download page
☐ send email to people who asked to be notified when iOS app is out
<https://github.com/Trustroots/trustroots-expo-mobile|Trustroots/trustroots-expo-mobile>Trustroots/trustroots-expo-mobile | Sep 5th, 2019 | Added by GitHub

'''nick'''

if option 2. was the one to go for, I would wonder what the users would make of having the webview version available, then a future version suddenly has all the features ripped out :confused: ... although I think, as we came to realise on the call, whatever we do there will be some users complaining about the approach, it's hard to achieve this slick and cohesive user experience with this kind of project.

'''theo'''

depending on how many people there are wanting to use it we could have a longer open beta type thing using test flight and google beta program thing, so that there isn't a hard switch to a newer, less feature rich version?

'''Mikael'''

I think we’d anyway have some kind of “open website on browser” type link on the sidebar? so the features would still be discoverable

'''nick'''

@theo I didn't quite get the sequence of things there, did you mean:
- release iOS app as-is in normal release mode as soon as we can
- once ready start publishing the new (approach 2) app in open beta
- after some time, switch over (edited)

'''theo'''

yeah that was the rough idea, what do you think?

'''nick'''

yes, sounds good to me!

Meeting Minutes/2020-04-13 Hackweek - references session

2020-04-21T10:28:02Z

Nicksellen: Created page with "History At the begining, refs were not needed (similar people) and the size of the community was too small. How do you actually trust profile? * When you see picture * When y..."

History At the begining, refs were not needed (similar people) and the size of the community was too small.

How do you actually trust profile? * When you see picture * When you can read more about them * When they have friends * Life outside Trustroots

References as: * Security/safety feature * A way to say “thank you” * Indication of experience * Indication of like-mindedness

No “negative” “vs positive” Removing green/red as connotation of good/bad Free text description; load on support?

== Demo: ==

* Invitation only feature — history + data
* +1 idea to tribe belonging
* reference people according to meet in person
* report ppl when you give negative ref
* 3rd step is free-text

== Invitation-only feature ==

* it was not in the very beginning
* introduced in Spring 2017 to get more quality on UX
* Autumn 2018 feature was removed

== New ideas: ==

* connect feature with “add as contact” feature? tie refereces closer to contacts as a way to lower the barrier to get references, also solves problems around “this profile doesn’t have references” — highlight them that they have contacts instead.
* show only “this person has hosted someone within 6 months” -type of indication about activity, hide “no” / “yes” answers publicly
* it’s problematic to collect “yes”/“no” replies first privately, then publish them later on
* giving a “matching score” about like-minded people can be misleading.
* option to say “haven’t met them”
* guidelines for writing free text
* how much do you trust the person?
* at some point have a minimum measure for new profiles to be allowed to leave references (but not in the beginning)
* How do we not make the freetext field a popularity contest?

== Action items ==

=== Team 1 ===

who: Abel, Dario branch: https://github.com/Trustroots/trustroots/tree/references-private-experience

* <s>Change question to “did you feel comfortable hosting this person/being guest/meeting them?”</s>
** ask michal: How do we have to handle the translation of strings? Do the json files update automatically? <s>- Change colors from red/green to neutral</s>
* Check expected behaviour and database storing
** How is stored in db when you check more than one option of how do you know them
* go through other UI to make sure that texts are clear what is public/what is not

=== Team 2 ===

who: Nick, Edvard, Michal

* Add guidelines how to fill freetext, what to write in it? describe more the person, not the event/place. Ideas:
** “What would you add to this profile?”
** [michal] first of all, what culture of references do we want to encourage?
** [michal] how to use non-judgmental language, say I had that experience rather than this person is such and such. What else is important in non-violent communication?
* Add public freetext
* Remove frontend display of negative / positive refs
* public fields in listing: hosted or not, free text, people, date
** ensure backend API only returns public fields
* PR for listing references, needs rebasing and reworking a bit: https://github.com/Trustroots/trustroots/pull/918

==== Steps ====

* add freetext field in the backend/database model + add freetext field to the backend API + maybe backend tests for those parts
** TODO: feedbackPublic is optional, but should it have a minimum/maximum length (max:2000, min:none)
** TODO: check about email notification message
** TODO: check about push notification message
** TODO: what format should the message be in? plaintext, or rich text with mediumeditor?
** TODO: if with mediumeditor then we need to check the maximum is plaintext value
* restrict which fields are viewable for other members (i.e. the “did you feel comfortable” bit (and other stuff?) should be kept private)
* later… some more UI stuff

=== To distribute ===

* Keep the 2 week period,
* General question: Will references be available in the “Download your data” section?
** Just add it there and it will. :-) -Mikael

=== Nice-haves: ===

* Possibly private free text?
* Encourage people to leave references
* Activity or experience number in profile summary-area: Number of references in the last 6 months? Similar to “last seen 2 months ago” thing.

Meeting Minutes/2020-04-16 Hackweek - languages session

2020-04-21T10:25:07Z

Nicksellen: Nicksellen moved page Meeting Minutes/2020-04-16 Hackweek languages session to Meeting Minutes/2020-04-16 Hackweek - languages session without leaving a redirect

= Languages Session - Hackweek 2020/04/16 =

We will try translations for one or two weeks and collect ideas and obstacles here, before writing a guide for new volunteers and a blog post inviting the community to use Weblate.

== How to get started ==

* https://hosted.weblate.org/projects/trustroots/
* please register if you want to do translate a lot (github oauth possible), otherwise you can only “suggest”, not “save”
* To add a new language: open a component -> “start new translation”
* it’s helpful to have Trustroots open next it, to see context
* There’s 2 buttons: “Save” and “Suggest”
** use “Save” when you’re sure, “suggest” when you want someone else to have a look
* Use the glossary for often-used words …
* placeholders! don’t translate them, but leave them in your translation
** words in {{double curly brackets}} should stay as they are
** <1>, <2>, </1>, </2> should stay, but the words in between should be translated (they will be replaced by html tags later)
* Use a glossary for words that appear often:
** “Add word to glossary”
** with another string, it will then appear in the top right when the word is part of that string

== Ideas ==

* Having Trustroots open in another tab is too much work, could we ave screenshots in Weblate for context?
* Or maybe is even in-page / in-line editing possible?
* If adding screenshots for each segment is too hard to implement (too much work) another option would be to translate what can be done without much context and add comments where a clarifying screenshot is needed.
* Have a text somewhere on the page saying “translations are a community effort, you can help”
* Have a “disclaimer” of sorts on the translated versions, in the lines of “This is a translation of the English original. If you see anything odd, -click here- to let us know.” This would allow for direct feedback after launch.
* We should have translations live (deployed) before inviting the community, so people have immediate feedback

== Tech stuff ==

* strings are located in json files: https://github.com/Trustroots/trustroots/tree/master/public/locales
* how can we have Weblate integrate new languages automatically?

Meeting Minutes/2020-04-18 Hackweek - organization structure

2020-04-21T10:24:39Z

Nicksellen: Created page with "= organization structure meeting = present: Nick, Edvard, Ludo, Marco, Dario, Mikael, Michal, Abel, Julien time: 1h == purpose / expected outcome == initial motivations fo..."

= organization structure meeting =

present: Nick, Edvard, Ludo, Marco, Dario, Mikael, Michal, Abel, Julien

time: 1h

== purpose / expected outcome ==

initial motivations for joining meeting. what we would like to get out of it. where do you start from?

time: ~1m per person

edvard:

* explore everyones standpoint, on how trustroots should organise itself
* practical outcome of how to proceed, another meeting? or initial ideas? even if just to have another discussion?

ludo:

* learn how trustroots is structured
* would like to be involved in decision processes to feel part of community
* first understand how it is now, then to understand how things should be changed or maintained

marco:

* to hear thoughts from nick, and motivation for this session
* interested in how it’s currently structured
* skeptical how much we can fit in this session, maybe needs more
* not too big, have discussion on a smaller number of points

dario:

* generally, to evaluate how chaotic do-cractic approach works for us
* see what ideas the new team has for organisation
* would like Mikael involved too in the discussions

michal:

* would like to listen, and speak if something comes up
* curious about the topic in general, and for trustroots in general

mikael:

* baby steps of humble start to understand where we are at
* don’t need to come up with solutions right now.
* get picture of ideas and possible directions
* vision and mission are huge things to do, lots of meetings and talkings will be needed for those.
* to understand and hear people

abel:

* wider discussion, not just about trustroots
* liking the thinking about different approach to make a sustainable life
* getting an income coming from communities and collaborative work, different from usual work + hobby model, radical change
* also like the idea of manifesto/philosophy that can be applied in other projects/living, will get more and more practical with the way work/remote work/vaues are going, not just job work, but care and community work
* not expecting a outcome just in this small meeting, but good to work on this
* would like to write this manifesto!
* offline vs computer time harmony/bal

== nick introducing the topic(s) ==

time: 5-10m

=== how trustroots is organized at the moment: ===

* original structure was quite hierarchical
* is about to change cause it prooved not to work so well, and the original team is less involved now
* lean startup philosoph - move fast and break things
* doocracy model - being able to do and not being blocked

==== some numbers: ====

* 40.000 registered users
* 14.000 active in last years
* 1000 weekly active users
* 122 slack channel members
* 5-10 active slack members (hackweek peek 20-30 people)
* 3 GitHub owners
* 28 GitHub developers, of which 2 were significantly more active than the others
* 4 people with server access
* 8 people approx signed the paper for member data access
* call every two weeks, 3 to 5 people joining usually
* 3 board members Kasper, Natalia, Mikael

==== Reading materials ====

* Current mission/vision/values: https://www.trustroots.org/foundation
* Foundation: https://www.trustroots.org/faq/foundation
*

== input from other people ==

time: … 3-5m each?

anything, but could also think about questions:

* how would you like society to be organised
* how would you like trustroots to be organised
* how would like your own life to be organised

marco:

* huge topic don’t know where to start, nice to be able to participate and see people have it on their mind
* software development world (conferences, etc), seems nice and impressive but also skeptical and see 2 faces of it, everybody thinks they need big sponsors, e.g. open source conferences funded by big companies that he is quite critical of. missing critical discussions around who you collaborate with, and how influences works. e.g. companies like google, who contribute to open source, but also doesn’t like this company.
* personal/financial aspect, always have to care for how you make a living, even with a simple life you need some amount of money, depends on where you live, we hvae different backgrounds and stability, e.g. what happens if you have money, some peopl get crazy, for others it is easy, and don’t feel threatened

mikael:

* where to start…
* co-founded this whole thing, previously working on bewelcome, and with others that worked on couchsurfing… underyling mission for life for a long term, also with hitchwiki
* personally wanting to have a sizable impact in the world, have helped nestle sell more ice cream, but don’t want that kind of impact
* now, want to help young people regardless of whether they have money to travel and meet other people, sharing, and all that stuff
* therefore trustroots to have big impact, long term would like it to be able to run a sizable project, thinking big, e.g. mozilla foundation, greenpeace, wikimedia. organisations with a vision/mission i the world, clear focus on what they want to get done, relying on volunteers, that drive impact/organisation forward. organisation is there to ensure volunteers can be effective.
* personal side: don’t need to work on trustroots, trying to not to be the bottleneck, an enabler for others. sometimes might sound like being sole visionary, but that’s not how I nercsarily want thiss org to be. helpful to have people with strong vision, but important that everyone can input and participate. but from experience effectiveness comes from several people …
* from bewelcome, want to avoid the informal hierarchy, supposedly democratic, but in reality it doesn’t happen, would like to stay pragmatic when thinking of this.
* lets see! I’d like this to be long term stuff, 10-15-20 years… more people to think in that way…

michal:

* really is a big topic! haven’t figured out what I’d like to say
* don’t tend to philosophize so much, in a long talk get bored usually, but not right now
* value freedom, community, and experimenting generally, in theory, try things and see if they work, like to see and observe
* value software as something to enable people to more together in the real world, trustroots does do this
* a non-philosophising anarchist

julien:

* not much to say, just arrived
* been in hospex since hospitality club, couchsurfing smelt fishy
* very active in bewelcome, part of board, when trustrots appeared, disppearing from bewelcome, talking, not doing, don’t want to talk too much because of this!

dario:

* really like anarchist/chaotic way it’s organised, but not working in a long for a long scope/scale/size, at some point if we want it to be a long term thing, we need people who are more involved than just in a little bit of their free time
* either having a basic income from somewhere, or somehow paid by the community, long term seems unavoidable. would prefer it if it didn’t happen, as experienced it in another organisation, as it creates more hierarchy and lots of obstacles to tackle
* not clear how decisions are made right now, just because someone is doing something, maybe bi-weekly calls enabled decisions as they considered something importat
* on personal life: would liket contibute to things that put people in power, in constract to big companies that people get more and more dependent on. would like to work less (whihc involves workin a lot more right now ;)

abel:

* mostly said stuff before (see above)
* was reading about de-growth - we should work less, fewer working hours, there is still a lot of work that is not paid. 20 hours in computer work, then rest of time in other stuff (q: now or intention?) -> intention becomes real purposing it for now :).
* income stuff, something we’d have to think about if we want to make it sustainable and accessible. currently something you can’t have as a priority as you need income from elsewhere.

ludo:

* important to talk about these topics, and about money. we can’t avoid money talks and discussions, even if it’s not urgent right now and don’t need a decision
* hard talking about if moneyshould be involved in the project or not, it brings in our personal perspectives o how we deal with money in our private lives, so decisions and discussions can be hard
* line between ho trustroots is right now and a drift in a “corporation” direction is thinner than we think, focus should be on participation, to make it affordable, if this means money that could be,the most important is that everybody can start from the same point, give the possibility for everyone to participate. e.g. if people want to join a meeting but has no money to get there, would be nice to support that.
* society and personal life: exactly how trustroots is :) welcome everyone that has thoughts and contributions, at least listen to them. felt very welcomed when joining trustroots hackweek. want life and society to be like this too.

edvard:

* come from background of organizational development, trustroots and general question is a question of structure. structure is where everything manifests in the end. esp. for trustroots et al that motivates people by values. important that structure matches inherent beliefs that we share. share mikaels view that structure should be explicit. if we tried to organise more people, and tried to provide overview of how it works, would be helpful to have it explciit.
* how it should be: manifestion of values in structure. hierachy is unavoidable if you manage more than 10 people. the problem is not in hierarchy, but how you design organisation. hierarchy that matches our values and style is permableae (allowing to move inside it), alow collaborating in different roles without barrier. structure is up for constant change, need to adapt to different situations in the phases of the project. design/change in structure should be a participative process.
* main point: designing a structure we’d all like to contribute to and work inside of. long process of establishing that, iterating it and keeping it alive.

== discussions ==

mikael:

* money side of things, people need money, but what else do people need. they want to learn. often students, learning programming and how to participate. can be more value than money as time is scarce. levelling everyone up, growing others.

== next steps / action items ==

abel:

* could try to in next (of the bi-weekly) meetings, have a time for discuss this. -> Continous discussion
* if people are up for writing some of this manifesto stuff, to take these things together, would like to join (seperate thing, maybe other non-trustroots people could join too)

julien:

* no comments

michal:

* not thought about it :) will let you know if I figure something out

ludo:

* same, not sure concretely how we can go on, didn’t think about it yet
* maybe we could split topics, which we feel are more short term, putting everything together in this organizational box could be chaotic

dario:

* also don’t know how to proceed :)
* should be a follow-up, would like to talk more about how decisions are made, and to note it somewhere

edvard:

* have an idea! : would look into the tools used in his consultancy on how they guide other companies to develop their way of decisions making, take care of organising the next meeting to get together, would love to collaborate
* in general, come to a common demoninator of our values, we listed a lot of things, and we have to elaborate our overlap and the direction of trustroots that us (the people working on it and the community), then derive a structure from that purpose, a bit fuzzy about how, will work more on- it!

mikael:

* would love edvard to drive to the next meeting, and anyone else, proactiveness is very cool!
* would encourage to get as practical as possible next step, maybe all gather a list individually, or what slows us done,what is negative, what could be better, maybe don’t need solutions at that stage. then come togeter to find solutions. identifying practical things we’d like to improve. find structures to address those negative things.
* practical questions: if we did receive donations, what would it look like. decision making is a good thing to look at.
* hard to plan too much ahead, be experimental!
* Get as practical as possible
** Gather a list on your own times: find out what slows us down, or harms us, all the negative things that could be better in Trustroots. No need to come up with solutions yet, just problems. :-)
** Talking points: * What kind of structures or systems would help? * What if we receive donations? How would it look like? * Decision making is big topic that is helpful to talk about, but also good to experiment rather than try.
** Would love if Edvard you can drive the next one! :-) Thanks for stepping up!

marco:

* feel a bit overwhelmed, so much inputs of many different topics, always veryinteresting to get the personal stories, in organizational discussions you create something artifical that doesn’t belong to the people themselves. really impressed. have to think about all the ideas.
* would love to be part of a community has a structure that represents the people, not one from above. quite impressed that it can work to have these very different levels of knowledge, also very complex to have good discussion
* hard to see how to make decisions
* not clear who are the main people from the outside

nick:

<ul>
<li><blockquote>Fail to dream about the future, and you forfeit your role in its creation.</blockquote></li>
<li><blockquote>Keep your eyes on the stars and your feet on the ground</blockquote></li></ul>

== chat messages from jitsi ==

pad for note
https://codi.kanthaus.online/trustroots-organization-structure#
or versio with edit link:
https://codi.kanthaus.online/trustroots-organization-structure?edit
11:00
Julien
Sounds like mozilla
Ah... lol
11:42
Abel
I like more the WMF example since mozilla it's mostly founded by Google and this kind of stuff. Besides WMF gets all its income from donations
11:43
Julien
Democrac
11:44
Abel
*WMF stands for Wikimedia Foundation
11:45
Julien
+1 Abel
11:45
Mikael
Abel: agree that about Mozilla. 😃
❤️ love the chaos, but yes let's get more organized 😄
11:50
Julien
Paid worker?
11:51
Mikael
big yes to increasing accessibility and barrier to participate.
11:59
👋
👏
^ ah that is applause
11:59
Abel
❤️ can work as well
11:59
Mikael
🙌
11:59
Julien
Everyone seems to want a full time project manager without saying it
12:01
Mikael
hehe
12:01
dario
I forgot: +1 for Mikael's approach of accepting that there is a hierarchy instead of hiding it, and work on that
12:04
Julien
Gift eco +1
12:04
Mikael
gift eco +100
12:04
Julien
He didn't include so many things...
12:05
dario
@nick: what was the text/book/author you were mentioning again?
12:07
Abel
disco.coop
?
https://disco.coop/manifesto/
or you're refering Adam Smith "The wealth of nations"?
12:09
michal
that's the one,
disco.coop
12:09
Abel
😛
12:09
dario
adam smith, thx
12:09
Julien
My personal goal is to start learning Javascript, just so you know
Be short everyone
I remember already reading a Trustroots manifesto
12:12
Mikael
Get as practical as possible - Gather a list on your own times: find out what slows us down, or harms us, all the negative things that could be better in Trustroots. No need to come up with solutions yet, just problems. 😃 Talking points: - What kind of structures or systems would help? - What if we receive donations? How would it look like? - Decision making is big topic that is helpful to talk about, but also good to experiment rather than try
12:17
Julien
I want
12:17
Mikael
on TR decisions are not made, they happen 🙊 haha, Something to improve likely is documentation/transparency/acknowledgement of people who are driving decisions.
yes to high-level vision and dreaming:
https://www.trustroots.org/faq#what-is-your-long-term-vision
https://www.trustroots.org/team
12:24
😃
Type a message

Meeting Minutes/2020-04-16 Hackweek - languages session

2020-04-21T10:17:18Z

Nicksellen: Created page with "= Languages Session - Hackweek 2020/04/16 = We will try translations for one or two weeks and collect ideas and obstacles here, before writing a guide for new volunteers and..."

Meeting Minutes/2020-04-20 Regular Meeting

2020-04-20T16:26:53Z

Nicksellen: /* Action points and outcomes */

= Trustroots Meeting =

* Date: 2020-04-20 17:00 UTC+2
* Facilitator: Nick
* Participants: Nick, Noah, Philipp, Martin, Mikael, Ludo

== Agenda ==

* hellos / check-ins
* non-binary translation issue (nick)
** background
*** (someone translated “non-binary” into “unsure”)
*** https://trustroots.slack.com/archives/C01217E3M2M/p1587377631000500
*** https://hosted.weblate.org/translate/trustroots/users/nb_NO/?&offset=38#comments
** aspect 1 : that specific case where the meaning of the translated text should match the meaning of the source text
*** online norwegian dictionary: https://snl.no/ikke-bin%C3%A6r
**** says it’s an ongoing process of change and more and more people are identifying as non-binary
*** Mikael already replied on the thread
*** got reverted by the person
*** Mikael favours jumping into calls in these cases
**** although doesn’t leave a trail
**** doesn’t have time personally
*** many layers of issues here
**** imposing views in a translation tool
*** Mikael would be up for making it very clear it’s not ok if seems useful
*** Martin/Mikael will contact their Norwegian friends, and Mikael will revert the change again with a more extensive explanation
*** nick investigated the permission options in weblate, and we could switch our project to more closed model, and only invite specific people to translate
**** would not suggest it right now, as it’s nice to keep it as open as possible
*** question about whether we have any feature that lets people contact us about translation or other content issues on the site (e.g. relating to inclusive language):
**** translation is very new, and not yet on the site
**** directing people to contact support, and making it more visible
**** can encourage people more to express their opinion
**** Martin finds the comment tool in weblate useful to markup things that are complicated. would be useful if the comment could show up for all the languages/translators, unclear if that feature eists
** aspect 2 : how to handle conflict in general (could be in any aspect of trustroots)
*** big topic!
*** support team already has some discussions/approaches about how to deal with this
*** to bring people into a chat, and have both of them show their opinion and discuss with a third party to find a compromise. Probably not efficient for highly polarized progressive political debate.
*** maybe bring the conflict to the general slack channel to share it and to gain and learn from solving it together. Needs skilled moderation! Noah could try it.
**** note: in this particular case the I believe the person has refused to join slack because it is not open source (but we could find another place)
*** Code of conduct: https://github.com/Trustroots/trustroots/blob/a6114484a33a0275252261c81fba7c06b7aacdd1/CONTRIBUTING.md
** aspect 3 : a gender-expression-denying person who is might be spreading that perspective into a load of FOSS projects without anyone really knowing (users or maintainers) * I doubt a lot are able to check this stuff (without @Martin’s keen eye, I don’t think any of us would have ever found out)
*** nick finds it very problematic
*** Mikael would like to flag it to weblate: support@weblate.org
* references next steps (nick, …)
** changes to existing UI: https://github.com/Trustroots/trustroots/pull/1389
** add public feedback UI: https://github.com/Trustroots/trustroots/pull/1413
** read references UI…
*** old work at: https://github.com/Trustroots/trustroots/pull/918
*** needs new work to incorporate discussed changes in https://codi.kanthaus.online/trustroots-references
*** can merge something very soon, as we can change it later, currently references will not be on live site even if master as they are behind a flag
** could be nice to prepare blog post that can be published when it’s ready… if somebody wanted to do that
* issue with https://www.trustroots.org/support ? not appearing in zendesk? (Philipp)
** sometimes has some spam issues (as the server sends it from your email address)
** sometimes things go into “suspended tickets” folder, although currently empty * sometimes when people write messages why they are stopping hosting
** Noah received 3 emails saying a ticket was written, but they didn’t arrive in zendesk
* react refactoring update (Mikael)
** high level tracking issue, needs updating: https://github.com/Trustroots/trustroots/issues/1334
** Mikael to focus on map refactoring when time allows
** would like a balance of feature development and refactoring
** state management will come soon!

== Action points and outcomes ==

* Martin/Mikael will contact their Norwegian friends to canvas for perspectives on the non-binary term in Norwegian culture
* following that Mikael will revert the change again and provide a more extensive explanation
* we intend to contact weblate about the topic once we’re a bit further advanced with our process
* Noah has volunteered to try moderating a (text-based?) chat with conflicting parties, generally
* Mikael happy to debug support email issue Philipp reported
* Nick will update the react overview issue #1334 to bring it closer to reality

== Next meeting ==

Next Date: 2020-04-27 17:00 UTC+2 / CEST

Next Facilitator: ?

Meeting Minutes/2020-04-20 Regular Meeting

2020-04-20T16:04:31Z

Nicksellen: /* Trustroots Meeting */

= Trustroots Meeting =

* Date: 2020-04-20 17:00 UTC+2
* Facilitator: Nick
* Participants: Nick, Noah, Philipp, Martin, Mikael, Ludo

== Agenda ==

* hellos / check-ins
* non-binary translation issue (nick)
** background
*** (someone translated “non-binary” into “unsure”)
*** https://trustroots.slack.com/archives/C01217E3M2M/p1587377631000500
*** https://hosted.weblate.org/translate/trustroots/users/nb_NO/?&offset=38#comments
** aspect 1 : that specific case where the meaning of the translated text should match the meaning of the source text
*** online norwegian dictionary: https://snl.no/ikke-bin%C3%A6r
**** says it’s an ongoing process of change and more and more people are identifying as non-binary
*** Mikael already replied on the thread
*** got reverted by the person
*** Mikael favours jumping into calls in these cases
**** although doesn’t leave a trail
**** doesn’t have time personally
*** many layers of issues here
**** imposing views in a translation tool
*** Mikael would be up for making it very clear it’s not ok if seems useful
*** Martin/Mikael will contact their Norwegian friends, and Mikael will revert the change again with a more extensive explanation
*** nick investigated the permission options in weblate, and we could switch our project to more closed model, and only invite specific people to translate
**** would not suggest it right now, as it’s nice to keep it as open as possible
*** question about whether we have any feature that lets people contact us about translation or other content issues on the site (e.g. relating to inclusive language):
**** translation is very new, and not yet on the site
**** directing people to contact support, and making it more visible
**** can encourage people more to express their opinion
**** Martin finds the comment tool in weblate useful to markup things that are complicated. would be useful if the comment could show up for all the languages/translators, unclear if that feature eists
** aspect 2 : how to handle conflict in general (could be in any aspect of trustroots)
*** big topic!
*** support team already has some discussions/approaches about how to deal with this
*** to bring people into a chat, and have both of them show their opinion and discuss with a third party to find a compromise. Probably not efficient for highly polarized progressive political debate.
*** maybe bring the conflict to the general slack channel to share it and to gain and learn from solving it together. Needs skilled moderation! Noah could try it.
**** note: in this particular case the I believe the person has refused to join slack because it is not open source (but we could find another place)
*** Code of conduct: https://github.com/Trustroots/trustroots/blob/a6114484a33a0275252261c81fba7c06b7aacdd1/CONTRIBUTING.md
** aspect 3 : a gender-expression-denying person who is might be spreading that perspective into a load of FOSS projects without anyone really knowing (users or maintainers) * I doubt a lot are able to check this stuff (without @Martin’s keen eye, I don’t think any of us would have ever found out)
*** nick finds it very problematic
*** Mikael would like to flag it to weblate: support@weblate.org
* references next steps (nick, …)
** changes to existing UI: https://github.com/Trustroots/trustroots/pull/1389
** add public feedback UI: https://github.com/Trustroots/trustroots/pull/1413
** read references UI…
*** old work at: https://github.com/Trustroots/trustroots/pull/918
*** needs new work to incorporate discussed changes in https://codi.kanthaus.online/trustroots-references
*** can merge something very soon, as we can change it later, currently references will not be on live site even if master as they are behind a flag
** could be nice to prepare blog post that can be published when it’s ready… if somebody wanted to do that
* issue with https://www.trustroots.org/support ? not appearing in zendesk? (Philipp)
** sometimes has some spam issues (as the server sends it from your email address)
** sometimes things go into “suspended tickets” folder, although currently empty * sometimes when people write messages why they are stopping hosting
** Noah received 3 emails saying a ticket was written, but they didn’t arrive in zendesk
* react refactoring update (Mikael)
** high level tracking issue, needs updating: https://github.com/Trustroots/trustroots/issues/1334
** Mikael to focus on map refactoring when time allows
** would like a balance of feature development and refactoring
** state management will come soon!

== Action points and outcomes ==

* Martin/Mikael will contact their Norwegian friends to canvas for perspectives on the non-binary term in Norwegian culture
* following that Mikael will revert the change again and provide a more extensive explanation
* we intend to contact weblate about the topic once we’re a bit further advanced with our process
* Noah has volunteered to try moderating a (text-based?) chat with the person, we leave that option open for consideration for now
* Mikael happy to debug support email issue Philipp reported
* Nick will update the react overview issue #1334 to bring it closer to reality

== Next meeting ==

Next Date: 2020-04-27 17:00 UTC+2 / CEST

Next Facilitator: ?

Meeting Minutes/2020-04-20 Regular Meeting

2020-04-20T16:04:10Z

Nicksellen: /* Next meeting */

= Trustroots Meeting =

Date: 2020-04-20 17:00 UTC+2 Facilitator: Nick Participants: Nick, Noah, Philipp, Martin, Mikael, Ludo

== Agenda ==

* hellos / check-ins
* non-binary translation issue (nick)
** background
*** (someone translated “non-binary” into “unsure”)
*** https://trustroots.slack.com/archives/C01217E3M2M/p1587377631000500
*** https://hosted.weblate.org/translate/trustroots/users/nb_NO/?&offset=38#comments
** aspect 1 : that specific case where the meaning of the translated text should match the meaning of the source text
*** online norwegian dictionary: https://snl.no/ikke-bin%C3%A6r
**** says it’s an ongoing process of change and more and more people are identifying as non-binary
*** Mikael already replied on the thread
*** got reverted by the person
*** Mikael favours jumping into calls in these cases
**** although doesn’t leave a trail
**** doesn’t have time personally
*** many layers of issues here
**** imposing views in a translation tool
*** Mikael would be up for making it very clear it’s not ok if seems useful
*** Martin/Mikael will contact their Norwegian friends, and Mikael will revert the change again with a more extensive explanation
*** nick investigated the permission options in weblate, and we could switch our project to more closed model, and only invite specific people to translate
**** would not suggest it right now, as it’s nice to keep it as open as possible
*** question about whether we have any feature that lets people contact us about translation or other content issues on the site (e.g. relating to inclusive language):
**** translation is very new, and not yet on the site
**** directing people to contact support, and making it more visible
**** can encourage people more to express their opinion
**** Martin finds the comment tool in weblate useful to markup things that are complicated. would be useful if the comment could show up for all the languages/translators, unclear if that feature eists
** aspect 2 : how to handle conflict in general (could be in any aspect of trustroots)
*** big topic!
*** support team already has some discussions/approaches about how to deal with this
*** to bring people into a chat, and have both of them show their opinion and discuss with a third party to find a compromise. Probably not efficient for highly polarized progressive political debate.
*** maybe bring the conflict to the general slack channel to share it and to gain and learn from solving it together. Needs skilled moderation! Noah could try it.
**** note: in this particular case the I believe the person has refused to join slack because it is not open source (but we could find another place)
*** Code of conduct: https://github.com/Trustroots/trustroots/blob/a6114484a33a0275252261c81fba7c06b7aacdd1/CONTRIBUTING.md
** aspect 3 : a gender-expression-denying person who is might be spreading that perspective into a load of FOSS projects without anyone really knowing (users or maintainers) * I doubt a lot are able to check this stuff (without @Martin’s keen eye, I don’t think any of us would have ever found out)
*** nick finds it very problematic
*** Mikael would like to flag it to weblate: support@weblate.org
* references next steps (nick, …)
** changes to existing UI: https://github.com/Trustroots/trustroots/pull/1389
** add public feedback UI: https://github.com/Trustroots/trustroots/pull/1413
** read references UI…
*** old work at: https://github.com/Trustroots/trustroots/pull/918
*** needs new work to incorporate discussed changes in https://codi.kanthaus.online/trustroots-references
*** can merge something very soon, as we can change it later, currently references will not be on live site even if master as they are behind a flag
** could be nice to prepare blog post that can be published when it’s ready… if somebody wanted to do that
* issue with https://www.trustroots.org/support ? not appearing in zendesk? (Philipp)
** sometimes has some spam issues (as the server sends it from your email address)
** sometimes things go into “suspended tickets” folder, although currently empty * sometimes when people write messages why they are stopping hosting
** Noah received 3 emails saying a ticket was written, but they didn’t arrive in zendesk
* react refactoring update (Mikael)
** high level tracking issue, needs updating: https://github.com/Trustroots/trustroots/issues/1334
** Mikael to focus on map refactoring when time allows
** would like a balance of feature development and refactoring
** state management will come soon!

== Action points and outcomes ==

* Martin/Mikael will contact their Norwegian friends to canvas for perspectives on the non-binary term in Norwegian culture
* following that Mikael will revert the change again and provide a more extensive explanation
* we intend to contact weblate about the topic once we’re a bit further advanced with our process
* Noah has volunteered to try moderating a (text-based?) chat with the person, we leave that option open for consideration for now
* Mikael happy to debug support email issue Philipp reported
* Nick will update the react overview issue #1334 to bring it closer to reality

== Next meeting ==

Next Date: 2020-04-27 17:00 UTC+2 / CEST

Next Facilitator: ?

2020-04-14T08:56:06Z

Nicksellen: /* Program */

Hackweek Spring 2020

2020-04-11T23:04:12Z

Nicksellen: /* Shared music streaming */

2020-02-14T13:54:10Z

Nicksellen:

Meeting Minutes/2020-02-10

2020-02-10T18:11:05Z

Nicksellen:

= Trustroots Meeting =

* Date: 2020-02-10 18:00 UTC+1
* Facilitator: Mikael
* Participants: Nick, Abel, Mikael, Michal

= Agenda =

* brief status update on invitation email (nick/noah)
** https://mailtrain.trustroots.org/ now exists for sending mass emails
** can we track when people click on links and fill the survey?
** please log open rates somewhere, useful for 

* thoughts on balance between feature development vs framework? (mikael)
** Get better at feature discussions? “This is the feature” it’s implementable as-is
** bring decision making models to hackweek; organise talking workshop about it.

* references, how to move forward? (nick)
** https://github.com/Trustroots/trustroots/issues/718
** need to know what we want?
** discussion on Github had hard to distill decisions from
*** discussion needs to resolve more?
** would having testing group be useful?
*** would require two parties to be on beta group to be useful
** Nick has “network of trust” slider idea;
*** he’ll write it in the github issue thread
** Survey had question about references
** Excercise of going through the process of decision making would be healthy for the team
* hackweek team (nick)
** would like 1 or 2 people to commit to be on team to work on it
** TODO:
*** work out what sort of tasks are needed
*** actively invite various groups/people
*** blog post

= Next meeting =

* Next Date: 2020-02-24 18:00 UTC+1
* Next Facilitator: Nick

Punted for next time from previous meeting:

* Mobile apps state
** Android; works
** iOS; can now be re-submitted, Mikael to own.
** Plans in future?
*** why wrap trustroots in an app and not just use a browser?
*** let’s make a react native app!is a lot of work though
**** offline support
**** Mariano mentions http://ioverlander.com/ as an app with offline support
**** Nick asked a person that might be able to help with it
* references, how to move forward? (v2) (nick)

* Trustroots Plattform invitation system: pros and cons (noah and dario)
** Mikael:
*** Two initial goals 1) more people joining, and bigger portion of those to be “better quality”.
*** Outcome: way less people joining, quality of experience lower, no way to measure actual member quality. Lots of time went to maintaining the feature instead of working on longer term features.
*** Conclusion:
**** Take the feature down, (some code still in place so that we can use it to measure “campaigns”).
**** Concentrate on things that can be used to effect quality long term (e.g. refernces, sandboxing tribes)
**** and being able to measure “trust metric”.
* help on the support line (noah)
* Who are coming to hackweek?

Meeting Minutes/2020-02-10

2020-02-10T18:10:41Z

Nicksellen:

= Trustroots Meeting =

__TOC__

* Date: 2020-02-10 18:00 UTC+1
* Facilitator: Mikael
* Participants: Nick, Abel, Mikael, Michal

= Agenda =

* brief status update on invitation email (nick/noah)
** https://mailtrain.trustroots.org/ now exists for sending mass emails
** can we track when people click on links and fill the survey?
** please log open rates somewhere, useful for 

* thoughts on balance between feature development vs framework? (mikael)
** Get better at feature discussions? “This is the feature” it’s implementable as-is
** bring decision making models to hackweek; organise talking workshop about it.

* references, how to move forward? (nick)
** https://github.com/Trustroots/trustroots/issues/718
** need to know what we want?
** discussion on Github had hard to distill decisions from
*** discussion needs to resolve more?
** would having testing group be useful?
*** would require two parties to be on beta group to be useful
** Nick has “network of trust” slider idea;
*** he’ll write it in the github issue thread
** Survey had question about references
** Excercise of going through the process of decision making would be healthy for the team
* hackweek team (nick)
** would like 1 or 2 people to commit to be on team to work on it
** TODO:
*** work out what sort of tasks are needed
*** actively invite various groups/people
*** blog post

= Next meeting =

* Next Date: 2020-02-24 18:00 UTC+1
* Next Facilitator: Nick

Punted for next time from previous meeting:

* Mobile apps state
** Android; works
** iOS; can now be re-submitted, Mikael to own.
** Plans in future?
*** why wrap trustroots in an app and not just use a browser?
*** let’s make a react native app!is a lot of work though
**** offline support
**** Mariano mentions http://ioverlander.com/ as an app with offline support
**** Nick asked a person that might be able to help with it
* references, how to move forward? (v2) (nick)

* Trustroots Plattform invitation system: pros and cons (noah and dario)
** Mikael:
*** Two initial goals 1) more people joining, and bigger portion of those to be “better quality”.
*** Outcome: way less people joining, quality of experience lower, no way to measure actual member quality. Lots of time went to maintaining the feature instead of working on longer term features.
*** Conclusion:
**** Take the feature down, (some code still in place so that we can use it to measure “campaigns”).
**** Concentrate on things that can be used to effect quality long term (e.g. refernces, sandboxing tribes)
**** and being able to measure “trust metric”.
* help on the support line (noah)
* Who are coming to hackweek?

2020-01-08T14:07:51Z

Nicksellen: /* Trustroots Meeting */

= Trustroots Meeting =

Date: 2019-12-30 17:00 UTC+1

Facilitator: Nick Participants: Nick, Michal

= Agenda =

* general chitchat! we had a nice chat about things like:
** our chistmas period activities
** https://solid.mit.edu/
** mathematics
** german grammar
** casual religion
** community-led features
** …
** neither of us had done a lot of trustroots related stuff in the last couple of weeks

= Next meeting =

Next Date: 2020-01-13 17:00 UTC+1 Next Facilitator: Nick (if nobody else offers)