New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize stores and pickups #1127

Open
nicksellen opened this Issue Nov 7, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@nicksellen
Copy link
Member

nicksellen commented Nov 7, 2018

To implement public locations for food distribution we seemed to go with the feeling to generalize stores and pickups to be places and events. It's a bit wider than the existing issues so I'll create it's own one here.

Renaming things is quite fiddly and have to be careful, I think as a first goal I would try and make them generalized but not add any new types, so the site will carry on working as it does now.

The translations are a bit fiddly, there are ~25 strings in the frontend with the matching /store/i, and 3 or 4 in the backend. It might be possible to keep the frontend one as they are, but maybe reasonable to just move forward and people will have to translate new words.

Related:

  • Public locations for food distribution (Food-share points, open fridges) #354
  • Generalization of store pickups for other tasks #359
@brnsolikyl

This comment has been minimized.

Copy link

brnsolikyl commented Jan 8, 2019

I'm wondering if it would be better to rename pickups to tasks, instead of events. It is a more general word, like the task of doing a pickup, the task of opening a Bike Kitchen, of going to a meeting, etc. It goes in line with #359 . Karrot can be a tool for self-assigning tasks in the more general collective work of food saving, bike saving and world saving. hihi

@nicksellen

This comment has been minimized.

Copy link
Member Author

nicksellen commented Jan 8, 2019

I like the idea, and it keeps a focus on using karrot for things you actually do, but it doesn't to quite sound right when it's being used for a meeting, or a public gathering, but neither are perfect for all the things. It might be that as karrot is more for internal group co-ordination stuff that the task is a much better focus than general events. Naming is hard.

To me, event can be more general sounding, depending on the definition used, from https://www.merriam-webster.com/dictionary/event - a is very general, whereas b-d are more specific.

a : something that happens : occurrence
b : a noteworthy happening
c : a social occasion or activity
d : an adverse or damaging medical occurrence a heart attack or other cardiac event

I googled "event or task" and activity was another word mentioned, maybe that works well? (but that also gets a bit confused with a list of recent activities on the site e.g. user signed up, etc... we were going to rename history to activity before #427).

... also to bear in mind, the user might only ever see this word in the url.

@brnsolikyl

This comment has been minimized.

Copy link

brnsolikyl commented Jan 9, 2019

To me, event can be more general sounding, depending on the definition used

I trust you there, since you're native speaker :)

activity was another word mentioned, maybe that works well?

I like activity. And personally I'd rather not change History (what's the status of it btw?) if we are to choose this name.

Figuring out the right words is something that can be asked from users or tried out in usability tests, so I'll include this to my list!

... also to bear in mind, the user might only ever see this word in the url.

Do you mean because of the different languages? Or because stores will be kept for foodsaving groups?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment