2016-09-13 Preparation I - Software, Transportation

Present: Tais Real, Anja Konhäuser, Zed Redstone fr4nk 0nf1r3, Arno Döpper, Paul Free, fritz holscher, Anna O'Neill, Janina Abels, Kaiser Mikato, Caro, Adrean Liegel, Chandi, Nick Sellen, Tilmann

Notary: Janina Abels

Facilitators: Tais Real, Janina Abels

Meeting starts: 11:20

Location: Neuried (Markt Indersdorf)

Agenda: tour preparation - software, transportation, (how to contact people, media kit, how to get materials like banners, event creation like disco soupe)

Outcomes

the software will probably not be ready by october, but the tour will commence still

follow-up meeting on how to make the lean foodsaving tool even more minimal at 3pm the same day

transportation apparently is a minor issue that is more fun to talk about than anything else

Minutes

Software

who is working on it and who will be working on it?

→ flo (sneezo), lars (donpiano), tilmann. nick gave a lot of consulting and joachim did scrum mastering and wireframes

mvp-design.yunity.org is design-focused

dev.yunity.org is more focused on functionalities

nicks priority now is to merge the two, since they're basically the same, meaning one account works on both

the frontend is atm very much behind the backend. only lars knows how he structured his code so we need to get it more modular to make it easier to change things.

currently there is no scrum matsering because joachim stepped back from it. nico from rotterdam got invited, maybe he can do it. otherwise maybe tilmann will organize it himself or janina could step in. but if noone fills this role it's also not the end of the world, says nick.

what's the status of the software?

curtis: imagine you have a car that has no doors and no seats, the brakes are there but they're not wired.

tilmann: we can show what we have to potential users but tell them that it doesn't work atm. if this is not what they want in its basic structure, why should we continue working on it?

tais: but it's not really testing if we just let people click around, because we cannot give the software to a bigger group of people who actually do pick-ups, it's not just about the handful of core-people we meet to decide.

tais: do we need more people to work in this?

tilmann: yes.

nick: you could ask 10 devs and get 10 different answers on that, because there are so many different ways to do it.

tais: i wouldn't feel comfortable doing a tour without having any kind of software. I want to do real testing and not only show design proposals. otherweise we could drown in feature requests and maybe even add to the confusion.

fritz: i think we already have a lot to offer: we have time and experience. i don't have a problem with going on tour without having a software.

nick: we can also maybe take features out of the software we're creating atm, to make it more easily achievable.

curtis: we probably could make it work in two weeks, as soon as i also get my laptop in a workable state...
nick: true, it's not a crazy amount of work, but the work would need to be focused. also, getting something ready quick normally is not a great idea in the longer term.
arno: i would really prefer to do the tour with a tool, but i will travel anyways, so i'll do it with or without...
tais: if we go on tour without a tool, maybe we need to set our priorities differently.
chandi: imo the mvp-design is pretty usable. the basic functionalities are already done. where is the problem?
nick: well, not all the buttons are working... like for the chat..
chandi: let's just get rid of that.
nick: we should have a little meeting on which features are actually crucial later.

tais: is the software translatable?
tilmann: no.
nick: that is a huge functionality...
janina: what about creating a copy of the whole software and manually changing the strings? it's not like the tool contains a shitload of text...
nick: but then the developers would need to do it.
janina: i think i could do it if someone showed me how to do it.
nick: but a developer would need to do it.
janina: yes, once.

tais: it would be good to get developers more interested.
paul: i'm interested in having a setup of tools to offer to groups to help them self-organize. it does not directly relate to the foodsaving tool and is not even focused on foodsaving, but it could be somehow integrated with what you're developing now. if somebody else is interested in setting up an open source software environment for groups to use, just contact me and we can work on that.

short feedback round on software

anna: i really like to learn more about the dev side, because i know nothing about it. it was an interesting meeting for me.
paul: i liked to get an update on where the software is at right now, i didn't like the pinpong about the question if we go on without a software or not.
arno: i'm interested in helping the developers in the dev process, i'm interested in the minimalization meeting and I convinced a dev friend of mine to join next week.
tais: i like the attitude of people to just go on with their own skills, but i still don'z feel confident myself to do it like that and without any software. i think the pinpong is necessary.
fritz: was very nice hearing about the status of the tool, i'm looking forard to go wherever we're gonna go and do whatever we're gonna do.
janina: interested in minimalization meeting to get clarity on where the tool couls actually be at. i won't take minutes on fsint meetings again, it's really stressful.
nick: i enjoyed the meeting, my motivation got up.

transportation
hitchhiking with fun challenges

silence
nudity
who shares tho most items?
to get the driver to join the trip

buses/vans

flixbus - axel, philip
van - pia, janina2
quicker but less sustainable, because we don't need to transport a lot of things

meeting ends at 12:30