worked a bit more on a bootstrapping endpoint to improve frontend performance, but looking for a way to have less code duplication in backend (Tilmann)
Finalized basic CLI for karmantra so far (Sandro)
offer follow up points (pagination, removing accepted) (nick)
thought about GPX export (nick)
2. Up this week
write down what you want to do for the project in the next days
finalize importable karmantra module for testing in hackweek (Sandro)
fix <img src="[object Module]"> bug and deploy (Tilmann)
Ask on the forum thread about offer: do they want to add “wants/needs”? something else (Bruno)
ask others in slack e.g. Danny about attending the at the weekend (Nick)
write up GPX export as a PR (Nick)
3. Discussion
How to translater “Offers” into German?
Angebote
Umsonstladen
Kleinanzeigen
Teilen
Needs/Wants
=> ask people how (don’t) use it, translate it anyhow or leave it
What do we want to focus on the hackweek(end)?
make it easier to understand Karrot for new users/random visitors
frontend architecture talks (related to performance, testing, developer-happiness)
usability / navigation improvements
notification settings
get more into karrot code generally (Sandro)
4. Next
Next meeting: 2020-01-20 12:30 (UTC+1)
Next facilitator: Nick
They are finishing the testing phase (one month) and decide based on consensus. Unlikely that they’re going to Karrot, because of some inertia, very used to the tools they used before. They were interested mainly on the conflict resolution.
Taïs saw a lot of confusion about how Karrot works when they used it. Necessity of a tutorial video, make it easy to learn. Taïs could do one in French. (Valentin plans one in english or maybe English and German)
Nick’s idea: try to find people who might be connected to the group somehow and motivated to do the changes they want (also who knows French. Language is a barrier)
admin stuff (Nick)
streamline hosting (add for hosters)
complexity inside docker is overwhelming (Nick)
Wouldnt it be useful to adapt and modularize the ansible setup (yuca) so it can be used by other hosters/usecases? (Valentin)
nick: ah, I missed this point in the meeting, yes for sure! although it’s hard to do in the abstract, better when someone actively wants to use it, although I also found it very hard problem on how to write genuinely reusable ansible roles… they end up being tailored to a particular ansible ecosystem
find resources (hosters that want to donate?)
update roadmap (bruno)
a lot of outdated things and things we’ve already achieved
finished (maybe?)
PR on sidenav (Bruno)
set default group theme by local_settings/settings.py (valentin)
I think I got enough feedback from tilmann (Valentin) but need a last review
landing page (Nick)
is ready to merge was only delayed to get some translations through to production
annoying push notifications, not as sleek as slack - but overall favourable to switch (Nick)
Bruno favourable to switch
should decide later with Tilman and Janina (check consent per message this week)
telegram
plantsharing (Valentin)
I recognized that plantsharing could basicly fork the grav instance karrot-world
nick: feel free to fork it - you might have the same confusion as us about project info site vs the app, etc…
group types
postponed till next week
2. Actions/Outcomes
Taïs is willing to help DLC and getting feedback
Make roadpmap update as a main topic for next week, maybe setup an extra call. Also considering to ask the community which features they want if we have the capacity
Nick will review/comment/merge Bruno’s PR
Landing page ready to merge
Nick can look through Valentin’s set default group thing, also maybe tilmann will again
Bruno will check again the feedback on conflict resolution and turn them into Github issues
Talk more on the next call to Valentin and group types when mic is working
3. Next
Next meeting: 2020-05-10 11:00 (UTC+2)
Next facilitator: Bruno
matrix is now e2e encrypted by default! … but maybe a bit overwhelming
remaining things
importing history?
github notifications
doesn’t seem to have all the useful stuff
community forum email setup (Nick)
foodsaving@yunity.org / info@foodsaving.world / karrot@foodsaving.world are now going to foodsaving-mails group
will receive spam
need to adapt to new workflow
push notifications…
screencast / tutorial
several ideas:
2 videos: one for introduction, one in-depth
different short screencasts for different main features, maybe max 2 minutes each. and one getting-started screencast
Is it a tutorial for people who already joined or something for the landing page?
not make it too specific because things change, but focus on general description of features / overview
group types (Valentin)
generalization/customization of instances (Valentin)
update roadmap
nick: meta/ what approach do we want to take? maybe there are three aspects:
visionary (define vision completely?) and
“organizational care work” (lot of work 2-3h) and
the next (specific) tasks
nick: input from our users/communities/groups
tilmann: go through all issues and determine if they are relevant (bruno)
bruno: should we ask for new input/feedback on the community forum?
bruno: personal motivations/interests for the next steps/tasks, write them down, have a discussion about them
issue handling:
janina: is there a need to go through the existing ideas/are they still relevant (will be worked on in like the next three months)?
nick: implement auto-close bot for karrot’s stale issues (issues have to be actively kept open).
however, issues might be related, have been opened by tilmann for other people
bruno: theory informing development
nick: move discussion to discourse because non-techy people are scared of GitHub
2. Actions/Outcomes
We’ll fully adopt Rocket Chat
change references: on foodsaving.world, Github, Karrot itself (anywhere else?)
Check if we can fix import history from Slack. Nick will check if Github notifications on RC can be improved
E-mail setup
accounts@foodsaving.world and *@foodsaving.world will go into foodsaving-accounts group
Update email address + point to forum at foodsharing page (Janina)
configure spam filter on postal?
Start writing a script for a screencast and make them available for future translations. Focus on the tutorial part for now (having in mind DLC as a use case), rather than an overview and presentation for the landing page (Taïs? Bruno)
Further discussion about generalization/customization of instances in a rocket chat discussion (Valentin)
Further discussion about roadmap in a rocket chat discussion (Bruno)
3. Next
Next meeting: 2020-05-17 11:00 (UTC+2)
Next facilitator: Tilmann
who is the target audience: people who start a group? people who just stumble onto the page? people who want to join a group?
what’s needed from the software side to make nice screencasts?
→ more thoughts are needed, Bruno and Tais will make time for this this week and potentially have another call
roadmap
github actions marked a lot of stuff as stale
triggered some people to comment on them
some issues will be closed soon, but maybe that’s fine - we can still look at them while they are closed
focus could be on public locations or extending conflict resolution
3-month period seems nice, to discuss the bigger topics once in a while
could be helpful to define the phase the project is in for the next 3 months: maintaining or expanding
possible structure for call:
retrospective of last period
collect list of bigger topics
go through topics, somehow timeboxed
conflict resolution for everyone, not just editors?
apparently groups let only sufficiently trusted people into the group, and trust karrots are less used, so it seems ok to allow access to conflict resolution for everyone
was only delayed to get some translations through to production