2016-09-13 - Narrowing down features

Present: Nick Sellen, Sarah, fr4nk 0nf1r3, Tilmann, Janina Abels, Tais Real, Konrad Becker

Facilitator: Nick

Notary: Taïs

Location: Neuried, München

[Meeting begins: 15:20]

going through https://mvp-design.yunity.org/login/index.html#/

Outcomes :

- merging the two existing front-ends

- how to select your community? A drop down menu with all your communities to select and an invitation to join new ones - atlassianwiki style (spaces) but better looking

- have the history of the edits visible (so the community watches out for people doing bullshit)

- keep the system of entering pick-up dates manually

- remove one-to-one messaging functionality

Chandi: what's missing? what's there that isn't important for the MVP?

NS: Something that won't take too long and might be ready at some point into the tour

Location

Remove location of users as a feature to add- general agreement, because by name, communities will be already connected to an area

Lars was planning to map out. Not necessary but he's free to work on it if he wants to.

Chandi: but it would fit to yunity to have a map so people can connect with neighbours etc

JA: for sure but on the long term, now we focus on foodsaving more than on social

Community

people sign up and have to search for the community, no direct link possible to a community (signups page first and then homepage)

Chandyi suggests a homepage which invites to join communities

TB: suggests that one must join a community during the signup -because how likely it is that users will join sereval communities?

If you're in two com., how can you shift from one to the other?

TR: see it as different spaces because of how it will evolve: different communities will have different needs and hierarchy organization etc etc.

then messages would be divided too

suggestion: switch to one default community per user (when you log in, joins the one you logged in for last time)

ML: implement a “make this as my default com.” button

TB: resistance because complicated

--> A drop down menu with all your communities as a selector and an invitation to join new ones - wiki style but better looking

community - anyone can create one. Limited number of communities suggested.

TR: each new community creation could set up a page for new users to sign (internal rules & liability waiver) - not a priority

Suggestion TB: you can only join through an invite (invite link or email adress?)

NS: Better not keep it open, to keep control. TB: remain open. NS: you won't convince me but ok. Right now it's open, might change, who knows.

Admin

No admin so far

All people in a group can see and add all pick-up dates and stores

History approach: the database is available so the community watches for people doing bullshit

Cannot kick people out

But it's okay, these test groups will learn while doing and we will learn their needs

Chandi:??

TB: Delete the database, even though it's a shame

NS: I think we won't need to delete the database

Stores & Pick-ups

have to enter manually each pick-up even if they reoccur daily

calendar extension for django - TB will evaluate which is best and implement it

NS: not a priority

Can you cancel having entered yourself for a pick-up?

No. It's very important but not essential.

Messaging

the messaging functionality will be removed

TB: already implemented in the backend, untested, and i'd have to remove the code from the back end

- just remove it in the front-end

TB: doesn't like leaving untested features just hanging out in the backend

- ah well, that's life

Can we see other users' email adresses? In order to contact people without messaging app.

It is public now. Let's keep it like this then, until people complain?

It'd be more important to have store chats than interpersonal chats

Notifications: there are none.

They seem essential. But actually for what purpose?

- Reminder that a pick-up has still open slots, for store coordinators. Important but not crucial.

No email system is in place (checking the email adress, confirming sign-up, sending notifications)

Seems quite important but not very high priority.

Profile pictures? Not necessary. But then erase those confusing smiley faces.

(everyone gets error messages and are in between logged in and logged out. It's all fucked.)

Translation

suggestion: make icons for everything. A language-less platform.

Sounds interesting but is actually a lot more work than making it translatable. So nó.

Seems high priority - Curtis said he could do that.

Offering collective intelligence tools - like syscons etc, people in foodsharing are overwhelmed with the hierarchy. Sure, but definitely not for now!

[Meeting ends: 16:45]