shawnlauzon / joatu Goto Github PK

Because we load data asynchronously, some screens depend on data which hasn't loaded yet. For example, this screen loads the chats before the users are loaded, and then the User inflation fails.

I'm unsure how to resolve this right now.

Bugs, Features, Urgent, Discussion, Future, etc.

Here's the other list we had before for labels : https://github.com/joatuapp/joatu-v2/issues

If a user is already in a hub but a new one opens which might be closer, give the user an option to switch to the new one.

I've already gathered a list of names, I have to organise it more concretely now to facilitate a discussion around how JoatU should be created.

Spam, hate speech, pornography

Hub members can only fully interact with their hub (send messages, add comments, create projects, etc.) On all other hubs, they have the same permissions as users that aren't signed in at all.

Allowing people to sign up, fill out a profile, create offers/requests, but not be able to see anybody else's POR until the appropriate number of members have joined+they have a hub. There was a website I used to go on that 'opened' for a city once it reached a minimum threshold of members, I really appreciated it because it incentivized the first members to go and recruit more if they wanted to make use of the platform.

From Jamie:

The votes that you included for your average valuation will be removed at the end of X period and allocated to your new hub area at the beginning of Y period. I imagine automatic vote readjustments every Z months (but I'm open to other suggestions).

When message received, possibly when new PORs are posted in hub.

When volunteers are approved by the project organizer, they get access to a separate channel to discuss logistics.

For MVP purposes, they have the capability of creating everything, but the disability of seeing nothing. They exist only in stasis, waiting for the appropriate number of users to join. I have an image I drew up a long while ago as a front page (not logged in) showcasing the number of users required to join in different cities before JoatU launched in those spaces. I'm imagining it something like that.

In this way, once it launches in their location, they get a notification and have dozens of offers/requests already prepared to be traded.

Eventually include one of these to prevent fake profiles from signing up.

This means that when users volunteer for project, they are placed in "pending" status until they are approved.

Different offers would have different proximities. For example, if I have a photo studio, I'm not willing to travel at all, it's a fixed point. If I'm a photographer with gear, I'll travel 0.5KM. If I'm teaching piano, maybe I'll travel 10km.

Each person should be able to change their personal settings for themselves (how far they're willing to travel) and how far the offer extends. Let's say I'm scrolling through the list of offers on the list, when I click on one, I can see two circles, my circle around me (how far I'm willing to travel) and the circle around the offer (how far the person offering is willing to travel). We can then decide together visually about a meeting spot.

Offers/Requests should be able to click a button to show if they're global (internet) offers or local offers as well.

Each user thus needs to contain both requests and offers

Only contains description for now

Just enough so I'm not embarrassed to show it

These events are in the community center. They are similar to projects in that CAPs are generated for the organizer, but only the person teach the class receives CAPs.

e.g culture, environment, food

Users should not be able to modify their CAPS supply

I know there is a way to measure distance by walkable distance vs straight line distance. If there is a way we can display the walkable distance to a location instead of the straight line distance, this would be great.

Some thoughts :

If want people to think of CAPS like an alternate dollar, we give two decimal places. If we want them to look at them differently, we give them more or less decimal places.

If we do decide to want to give value to things beyond the actions, such as getting a friend to join who completes a transaction and/or participates in a project, then by giving (let's say) 1500 CAPS for an hour of community work, we could easily offer someone 50-150 for having brought on a new member without fear of devaluing the system while still giving semblance of some value-added because the numbers themselves are bigger than 0.50-1.50.

The profile contains:
Name & description
Offers & Requests
Feedback & rating

For MVP there is no rating system, just the ability to add comments. For our small scale, this should be sufficient for being able to provide feedback without creating a quantitative system which might not be completely correct.

#22 still exists for a rating system; see that item for some discussion.

This is the terms we currently have, we ought to make certain it's what we still want, but it's a good start.
http://alpha.joatu.org/en/tou

One for the backburner, but something that could be very important.

In the last iteration of JoatU, all of the CAPS were publicly view-able in the people's accounts. Is that something we want, I'd like to hear your collective thoughts on it.

Community Hubs (visible on all maps all the time w/a different symbol)

• Show that the user (given their location) is connected to the closest hub
• Automatically attach projects to their closest hub
• Have all of the community hubs where we have gotten letters of intent (e.g. concordia, cafe osmo, temps libre mile end, mcgill WWF club?*)

These are automatically displayed to everyone. Should this be limited to hub members or anyone?

This is different from #9 in that a separate "logistics" channel is available to accepted project volunteers.

When submitting a POR, the text you type is auto-translated into French or English underneath (with google translate). You can edit this text or leave it as written.