bernie-2016 / ground-control

Central volunteer and data portal

Ground Control

Ground Control is the campaign's central platform for creating, managing, and increasing turnout to events. It contains several key tools used every day by campaign volunteers and staff:

• An administrative interface for editing and approving events
• An event creation tool
• Call and email tools for event hosts to increase turnout
• A constituent lookup tool for administrative use
• A constituent event dashboard to allow uploading of data files for review by our data team

Getting Started

OS X

In OS X, we currently run everything locally using a Procfile and node-foreman. To get started, install Node.js 5.x and Homebrew. Then clone this repository and cd into ground-control. Then do the following:

npm install
./setup-osx

Then you should be able to start Ground Control on http://localhost:3000 with

npm run dev

Windows & Linux

On Linux, follow the same directions as OS X above, but substitute ./setup-linux for the equivalent OS X script.

You will also need to have Docker and docker-compose installed to provide your database.

Environment Variables

You can find environment defaults in .env.sample. The first time a setup script is run, .env will be generated with these defaults.

If you ever need to generate a missing .env, run

npm run gen-env

Contributing

Want to help out? You can jump right in to see issues that are ready to be tackled by looking at the status-ready issue label. If you are just getting started with the project, also check out the newbie-friendly label.

You can also see an overview of where all of our issues stand at https://waffle.io/Bernie-2016/ground-control

We use Gitflow to accept pull requests. To submit a change:

1. Fork the project to your own GitHub account (click "Fork" on the project page in GitHub)
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

For code review and discussion, ping @jlegrone on the berniebuilders slack.

More Info

Read our wiki for more guidance on development and other FAQs.

Contribution Activity

License

This project is licensed under AGPL.

ground-control's Issues

Import the phonebank-rsvp into new call tool

• Add event type and event attendees models
• Create BSDSurvey and BSDEventSurvey
• Make it possible to define in call assignment creation which survey renderer to use
• Make it show nearby events to be RSVP'd to
• Hardcode targets for assignment
• Grab the form data from the BSD iFrame, send it to backend and make the RSVP.
• Add something to the RSVP creation call to track it

Automatically update the schema when the schema changes

Make a proper deploy step

The way it currently is being deployed is not a good way. This means:
a) Don't use webpack-dev-server in production
b) Don't use babel-node in production
c) Switch out the private SSH key being used for compose.io to be an app user.
d) Remove the maestro conference keys from the codebase and put those in heroku config. Reset these keys from maestro as well.

Show maestro call links when you select a call from the left

Make it possible to modify existing group calls that have been made

These modifications should also probably notify anyone who has signed up for a given group call

Enter currently not working to submit forms

Add something that indicates the timezone when making group calls in the admin interface.

Actually hook up and finish the call assignment views

It needs to validate the non-iframe data, submit the assignment to a mutation on the backend, and create a record of the call.

Add pagination to group call list

Currently I'm returning the first 50 to the frontend and cutting off the rest. Use connectionArgs correctly and return a paginated list.

Implement deleting group calls

Seed dev data

Otherwise it's impossible to test the phonebanking tool.

Event approval admin

We need a way to let people approve events via ground control.

Finish homepage/welcome page

This is the VolunteerDashboard component. Flesh this out, hook it up with the login component once that is done.

Clean up call assignment creation to check local database for objects before checking BSD.

We should make the fetch also optimistically cache locally. E.g. this should look something like
let survey = await Survey.findByBSDId(Id)

This will check for the survey locally first, then check BSD, then fetch the object from BSD and create a survey locally using createFromBSDObject.

Switch from MaestroConference to our own system built on Plivo

This is a big big project and probably not one we should really be doing, but given how many complaints there have been about voice quality on maestro conference, it's worth talking about.

Plivo seems to be the new hotness compared to twilio, and a lot of reports that it has better audio quality than Twilio.

Add Clearbit integration

We should look into Clearbit to have attached notes on users when we talk to them. Might be interesting, might not.

Make test data and a setup script

Add survey for signing up for group calls

This means:

a) Set up Survey model
b) Add a default survey template react component
c) Add a survey processor that creates group call signups

Handle errors from call creation

Integrate mass call tool into this tool somehow

Once we do #26 we should try to use this data across our call tools and use the same model of surveys for the mass call tool. Will figure out this migration when we get there.

Add a way to make sure callees don't get locked up forever

We need a crob job or something to do this. Would be nice if RethinkDB has internal support for timing out entries in the DB.

Make call assignment list in the volunteer dashboard show only your call assignments

Currently it is showing all call assignments.

Fix bug with forms where clicking on a label doesn't focus the input

mui/material-ui#2183 is the issue

Integrate in data from Vertica/BSD/VAN to the backed

Sync calls from Maestro into Ground Control

Not sure if this will be a one time thing or a recurring thing.

Set up an app user for Compose.io tunnel

Have the default view in Group Calls be a calendar view of scheduled calls/a dashboard of some sort

Add Metabase integration

Once we get #26 in, we should start doing some useful metrics on the data. Metabase seems cool (and might support RethinkDB soon).

Implement authentication

Create call assignment logic

Currently we have not hooked up how to show who gets called for a particular assignment. The logic here needs to copy the logic from the old call tool +

• Default to calling people closest to the caller. We should be able to do this if we store point data per person of their location.
• Add a way to limit how far out a caller's callees can be.

Add a Date custom type for GraphQL endpoint for all things that return a Date.

We colud probably just use https://www.npmjs.com/package/graphql-custom-datetype

Add backend BSD data sync process

The way this will work is:

1. Stork job to export CSV of all our data
2. Some script that diffs this CSV with the last exported CSV
3. Script to turn CSV data into Ground Control data.

We could possibly just do this with amazon lambda so we don't have to build out another service.

Flesh out the volunteer dashboard

All the sections other than Call Assignments are dummy sections right now. We should put stuff there or remove them.

Fix bug where if you change the date on an individual call, it changes which call you are editing

Design help

Get someone better at design than me and think through how this dashboard should actually look/come up with a design for it. Especially need some design help on the group call form.

Add field validators in models.js

There is a stubbed out function for it. We need to validate notes based on the field type before saving the notes.

Clean up repeated styles, make some base styles

Make a /login endpoint and figure out how to redirect people there on 401

For a lot of views (such as the VolunteerDashboard), we just want to show the person something different based on if they are logged in or not. But for some endpoints (such as viewing a particular call assignment), we want to redirect you to /login that has the login component on it.

This probably means building in support for understanding 401s in the RelayNetworkLayer.

Clean up browser navigation logic and make navigation happen via routes

Clicking on a group call on the list on the side should change the URL.

Have better feedback when clicking "Create!" button in create calls

Either do optimistic update, or have a spinner of some sort. Probably the latter.

Make a calendar interface to call scheduling

I have a somewhat broken GroupCallCalendar.js React Component. Make this work so that when you generate a bunch of calls, you can schedule them by just dragging them around on the calendar.

Create view for managing persons

It should be possible for us to start looking at persons, adding persons, and making lists of persons (both dynamic via ReQL queries and static).

Automatically scrape Facebook to find out what Facebook Bernie Groups a person in our DB is part of

In the group call creation form, make it so changes to individual forms reflect back to the batch call generator form

Clean up BSD api call code

BSD fetches to get data should be a part of the model code instead of the current thing.

Add authentication

We should not make it possible fro just anyone to hit this endpoint and start making maestro calls.

Add propTypes to all the React components

Set up Google Sheets spreadsheets for each group call.

This involves using the Google Apps Scripts API to generate a note taking list for the call and then having a way to submit that data back into Ground Control.

Call assignment surveys need a loading view

The flashing of the iframe is janky. Make it show loading until the iframe shows up.

Block dev version from actually creating Maestro calls

Come up with a better solution