Regions and Geodata

[1u]

Idea: only user-/course-location, no regions

• User selects where on the map zhe is.
• Every proposal / course has a Position (where user was/ that user selected when zhe proposed it).
• Regions Tab is converted to Round Map with user-location in the center.
  • Bar to zoom out and in (makes distance within courses and events are searched)
  • Save-button to save user-location to Profile

see #190 leaflet / Nominatim

Privacy concerns

If we should show users Position on map in course... At Publication user-location is rounded down on server then Jitter added (on server or client). <- Maybe only if high privacy is selected by user.

Cons/Open Questions:

• Responsibility and commitment of central groups and people: the scenario of controlling and making agreements for and by new regions will change. because results in flushing regions

[1u]

Idea2: Have official regions and add map-pointers for small/other/new locations beside

regions stay as they are, but we add option to propose courses (and create events) not in a region only but anywhere on a map as well.

Features:

• When new region is created near already proposed course it's taken into region.
• Regions selection stays easy as it is
• Not mandatory/later: search courses on map

Conceptual thoughts about organisation

In order to make Openki more decentralized and our workload achievable @1u and @lu40 see some need to assign most responsibility to the community/users. We think it's done most easily within regions (As for example done on http://foodsharing.de). - Speaking more about organizational side and the social field than site-specific privilege-levels.

Such responsible persons would be the ones

• that organize different kinds of gatherings,
• are contacts to answer questions from new users
• take responsibility for the content of the page at their region (moderate, remove, feature new courses...)
• advertise / network / answer media-requests. maybe take care of local social media channels...
• link new groups, initiatives, organisations to Openki
• introduce people that want to participate (in organizing Openki that region)
• search someone to take over once they leave... and so on.

Speaking about a kind of organizational units, I don't know how much these have to be represented in the functionality of the web-app. (other than maybe "regional-administrator" #20) But we are sure we need these on the social-level (and that there has to be documentation/transparency).

Imaginable would be Titles/Scopes like: "Ambasador", "Funktionär", "Hands", "HQ", "local branch/chapter", "Community manager", "Headmaster"...

• Before opening up an official new region we can ask for persons that take responsibility in that area.

(To round it off, here is the issue for auto-assigned user-levels: #164).

[1u]

Idea3: Have featured and unfeatured regions

Only show regions where Openki-chapter (responsible people) are.

but create Region for every request we get (atm: Wien, Basel...)

Tec:

add field to db: "list" : true if (search !== '') query = { name: new RegExp(search, 'i'), list: true }

[1u]

As discussed with @panosnethood For solution n°2: Have "Other Places" or "Regionless Courses" as concrete choices in the menu.

[panosnethood]

People keep asking me how they can start using Openki in their region, and since this needs some more thorough discussion from our side, I propose to create as soon as possible a generic default "World" region where people can start experimenting immediately with Openki without waiting for their region to be "approved".