Hackweek Spring 2020
Due to the CoViD-situation, we're having our Trustroots spring hackweek online-only.
- 1 Program
- 2 Sessions
- 2.1 Welcome session
- 2.2 Setting up dev environment
- 2.3 Code walkthrough
- 2.4 Migration to React
- 2.5 References discussion
- 2.6 Support introduction
- 2.7 Translating Trustroots to other languages
- 2.8 Mobile app
- 2.9 Joining Roots (Content)
- 2.10 Organization Structures
- 2.11 Closing session
- 3 Tools
- 4 Learnings
|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|
|09:30–10:00||Check-in. Day presentation|
|11:00||References coding (mumble)||#Translating||#Organization|
|12:00||#Migration to React||#References discussion||#Content|
|14:00||#Set up dev environment and enjoying the sun|
|19:00||#Code walkthrough||Free hacking|
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
- Client / React
- Testing / Jest
- Server / Node
Migration to React
Edvard, Dario, Nick
- Vision about References feature and current state of development
- also trust metrics, invitation only feature and other related things
Answering messages from the community – introduction to the support tools and common issues people have
Translating Trustroots to other languages
Please add your observations using Weblate to the pad
Getting started with our new translation tool Weblate
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)
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 ________ .
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!
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.
The subgroups summarize what happened and their outcomes.
- getting started with trustroots coding
- react migration
- references feature
- iOS app
- content - roots of trust
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
- 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
(Sessions marked in green will happen in Jitsi, the rest probably in Mumble)
- Text chat: #collective channel on our slack workspace
- Voice chat: #trustroots channel on ecotopia's mumble server
- Video chat: https://meet.collective.tools/trustroots (public Jitsi Meet instance, works in browser)
- Pair programming: Visual Studio Code with Live Share Extension
- Stream (open in browser or media player)
- see/edit playlist
- add music (e.g. with filezilla) to sftp://trustroots:97HeN0iLXWa2@stream.abovethebeat.com
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.