The tws-on-rails from teawithstrangers

Reduce The Size of Images for Mobile Clients and Small Displays

Current photos for all cities and splash page are massive. Would like something more reasonable for desktop but if on mobile would prefer smaller

Not sure what best practice is here. Should they be same size for both?

Attendance can be created for a cancelled or post-dated tea time

Let's add more validation and testing around attendances. Might be best to create an instance method on the TT itself that returns a valid object and never manually instantiate one.

Authentication & Security Review

Look through and make sure that permissions are properly evaluated in all contexts and controllers

Make SMTP in Dev GMail Agnostic

Right now we assume everyone is using Gmail to send test emails in development. Let's make that configurable.

Add CSV Export of DB based on criteria

Essentially expose DB for marketing/user activation purposes, e.g. drip marketing.

Fix all FIXMEs and ToDos

Ack for them. it's somewhat scary :x

Users Can Subscribe to a Waiting List for a Full Tea Time

If a tea time is full, 1/5 people will almost certainly cancel upon receipt of reminder email. But to ask people to just refresh the page around noon on the day of a tea time is a lame way to have them fill in empty spots.

I think the button for a full tea time should be 'WAITING LIST', and the person signs up as normal, but they get an email confirming that the second a spot opens up, they get notified by email and have a chance to fill it in.

I could imagine this feature being stepped up a notch and actually keeping those spots open exclusively for wait-listed people for the first two hours or something before opening to anybody else, but I'd say that's less important.

Queue Emails, don't send during Request/Response

Currently emails are delivered immediately during the request/response cycle. Move them to use delayed_job, sidekiq, or something similar

Assets Should be Served from S3/CloudFront CDN not the App Process

Basically remove the assets gem, prepare a rake task for pushing updated assets up to S3

Flaking Users Should Be Able to Submit a Reason for Flaking

Right now, when people flake, they hit a button and that's that.

At the least, we need an 'Are you sure?' modal.

But really, we should have something like what's seen in the modal here, and we should be collecting the reasons to learn more (eventually, radio buttons with an 'Other' explanation would be good, but I don't know enough to effectively write options here.

No Host City Page

City pages without any hosts (i.e. cities that are 'Warming Up') should have a special view as seen in the Dropbox folder.

No attendees indicator

Making the markup in _host_tea_time_info.html.haml conditional on if there are attendees or not. Right now, if there are no attendees, there's still an attendees title.

Add T-48hr reminder email (and fix current reminder)

Right now, the only reminder email is coming the morning of tea time, seemingly sometime around 9am no matter when the tea time is happening (i.e. a 1pm weekend tea is getting a 9am notice (4hours) just as a 7pm weekday is (10hours)).

There should be an email 48hrs before (would probably lead to more advance-notice flakes) and another email 12hrs before.

I know an impediment here is the time zone problems, but let's please get this sorted out the second time zones are fixed plz!

Thanks so much <3

Tea confirmation email #2

After joining for tea time, everyone gets a confirmation email with details of tea time. Purpose = get them to put it in their cal.

Thinking harder about this, more and more people will be joining for tea time without having stalked its journey or hearing about what it was like for someone they know. That said, I think there is a place for a 'What tea time is about' email. I'm going to draft this later today (while converting all the other emails to .md.erb), but it should go out separate from the confirmation email.

Can we add this to the user_mailer file @nickbarnwell ?

Example of an etiquette / guidelines email from Pinterest a few years back:

Notifications Area and Inbox (was: Tea Time Attendee Changes Notify Host)

Can hosts receive emails every time someone signs up for or flakes from their tea times?

Are cancelation emails sent automatically if host deletes tea time?

Quick q @nickbarnwell

mailto: link for all attendees in host dashboard

There's no mailto:[all attendees] link for the hosts to conveniently email the whole group, that would be awesome for all sign ups (attendees + flakes), all attendees, and all flakes

Reminder emails only to attendees, not flakes

Right now, the reminder emails are going to everyone that ever signed up for a tea time (so it includes people that signed up and flaked before the reminders were sent.)

Because lots of sign ups might be flaking in the next few days / weeks (just given high traffic and desire to secure spots because they were in demand without actually thinking of if they could actually make it; people just want to host their spot when they know it might not be available) so there's going to be a lot of irrelevant emails going out.

Make Hosts and Cities use Slugs for Routing

E.g. for a city /cities/san-francisco/ and /cities/san-francisco/ankit for a host

Scheduled Emails and Reminders

HTML Email Templates

Create Admin Dashboard with Statistics, Top Cities, &c.

Add a view to Hosts Dashboards for them to see their tea times

Right now, a host can't see their own tea times on their dashboard, but they should be able to see that in addition to the attendees + email addresses.

Move from Unicorn to Puma

Moar concurrency, less memory.

Users Registering in a City without any Hosts/Tea Times should Receive a Different Welcome Mail

Right now, all the user registration emails are angled towards encouraging users to sign up for a tea time, but if they're in a city where there's no hosts or just one host, I'd want to create a new user registration email for them. @nickbarnwell when could we get this done by?

Host confirmation emails

Hosts get email confirmations when they create tea times with calendar event attachments (akin to how tea comers do)

Convert API into a simple iOS app

It'd be so dope to have a simple app where you log in with TWS credentials, see slots available, and book spots from the app.

Biggest value prop here, methinks, is push notifications when tea times slots open up same-day + integration with calendar. Would also be great for messaging with the hosts or tea time groups after tea time, but that's def a second order priority.

There are some iOS devs who are down to help with this, but I imagine it's important to have the API ready before this is possible.

Is this a realistic goal within the next 2 months (API, announcing open source, and working with more devs to build this)?

Hosts Can Reassign Tea Times to Other Hosts

Create a view for a host to reassign their tea times to another host

An instance method reassign! on TeaTime that takes a User and does update_attribute(host_id, user.id), validating that User is a host or admin
A view action under ProfileController for reassigning to another host with a dropdown list of all hosts
A PUT action to update the host with the information from the form
An email delivery when a host reassignment takes place to old host and new host explaining the new tea time status

Any host currently has access to /tea_times and can edit any tea time, but any edits saved from a hosts’ account makes the tea time theirs. This should not be the case. Edits made using /tea_times/X/edit should only change host IF the form for host reassignment is used. Clarity:

if Ankit edits Amy’s tea time but does not change host and clicks ‘Update’, it is still Amy’s tea time. Ankit just updated it.
if Ankit edits Amy’s tea time but does change host and clicks update, it becomes the new hosts’ tea time (even if new host is not Ankit)

Separating attendees / flakes on host dashboard

On the host dashboard, hosts just see all attendees' (including the flakes) names linked (mailto:[email protected]), but no separation of attendees/flakes (i.e. a section of attendees and a section for flakes for each tea time; i feel there IS use to showing flake names even though they're not coming in case it's needed for any sort of relevant comm)

Finish JBuilder Templates for API Endpoints

Currently JSON responses are undocumented and in some cases not built. Finish creating the API endpoints for these so people can build on top of the TWS interface and data

db data for development

Do you have an existing strategy for getting development data?
I usually make a seed_dev.rb file in db/ and a rake task that resets the db and loads the file to make fake data.

Show tt attendees on prof page

Automatic TWS Admin Post-tea Emails

Ideally, this would be triggered once the host has marked attendance for the tea time (i.e. marked no-shows, as anyone else would've marked their own attendance status by signing up and going OR 'flaking' on the interface and not going.)

That should be done within an hour of tea time ending (mobile interface), after which two emails would be fired out:

Thank you attendees — This gets sent to those that were in attendance. It includes admin info just showering them with love from TWS, welcoming them to do a few admin things:
- join the Tea Time group,
- like the fb page,
- sign up for another tea time,
- read and subscribe to the blog
- (eventually) download the app
NOT COOL ROBERT FROST — This gets sent to those that were marked 'no shows.' This just lets them know what tea time is about, gives them a friendly slap on the wrist, invites them to join again but impresses upon them the importance of attendance accountability ("come again, really, we want you to. but don't be a dick again.")

No host page template

User Dashboard and Drip Marketing Infrastructure

To filter the users by certain constraints, it'd be great to have a dashboard to filter, compose, and send messages in a seamless way. I don't know how complex each of these components is to build

select filters > show results,
compose interface
sending emails from [email protected], reply-to: [email protected] to the users in results
- scheduling these emails?

Change password isn't working

Model Refactor, Consolidation

Move logic out of controllers, especially for e.g. User registration

Create .html.erb templates for all emails

user_registration, tea confirmation, tea reminders, tea cancelation, and tea flake emails are all plain text. I'd like to be able to incorporate some linked text and gifs in these emails, so would love if we could implement an html.erb variant (with the .text.erb there to serve as backups)

Users Can Belong to Multiple Cities

If a user wants access to multiple cities with ease (i.e. select a primary locale, but add others as ones they go to often), it'd be great to allow a user to add locales they'd want tea time access to.

I imagine users having a schedule that's made for them and their chosen locales (i.e. when UserX is logged in + goes to teawithstrangers.com/schedule, he/she sees all tea times in all their locales in one place). So teawithstrangers.com/cities/[city]/schedule = relevant for non-logged in users; teawithstrangers.com/schedule relevant for logged in users. See #97 for more detail.

This is really important to sort out asap.

Unit Testing for Models
Integration Testing
End-to-end testing

teawithstrangers / tws-on-rails Goto Github PK

tws-on-rails's People

Contributors

Stargazers

Watchers

Forkers

tws-on-rails's Issues

Recommend Projects

Recommend Topics

Recommend Org