OpenSupporter Tech Call 1/16/2019 12:30 PM EST

[Tim Holahan]

Hi, folks.

Since Sonya's unavailable, I'll take the helm for this week's tech call, particularly because we didn't get to all the items on the agenda last week.

Let me know ASAP if there are any other items you feel should be on the agenda.

Thanks,

Tim

Here's the call-in info and agenda from the Google Doc:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/336246126 Or iPhone one-tap : US: +16699006833,,336246126# or +19294362866,,336246126# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 929 436 2866 Meeting ID: 336 246 126 International numbers available: https://zoom.us/u/eshvZEn5t

Agenda!

1.0 - Website Things

opensupporter.org

           spreadsheet of requests - here

https add - update from Tim/Dan

Need to update:

https://github.com/opensupporter/osdi-docs/wiki/Implementations-of-the-OSDI-API

Check in on FAQ progress

Tim’s first draft

2.0 - Tech Work

Gemfile Review

Review https://github.com/opensupporter/osdi-docs/pull/324, which adds a Gemfile for folks to be able to build and serve the docs locally to preview their changes.

To reduce confusion, can we remove the master branch?

Can we get a CONTRIBUTING doc in place?

A CONTRIBUTING file tells your audience how to participate in your project. For example, you might include information on:

• How to file a bug report (try using issue and pull request templates)

• How to suggest a new feature

• How to set up your environment and run tests

In addition to technical details, a CONTRIBUTING file is an opportunity to communicate your expectations for contributions, such as:

• The types of contributions you’re looking for

• Your roadmap or vision for the project

• How contributors should (or should not) get in touch with you

Augustus: list of contributors but hasn’t been modified

http://opensupporter.github.io/osdi-docs/

Be sure to include:

At least 2 people’s opinions on a topic, let people know that they submit a pull request and then the submitted will attend the tech call, and we will vote on adopting it

If Ragtag makes it, Augustus is happy to review it

Cost-efficiency when mapping OpenSupporter to proprietary systems that charge fees per api call

Developers need a way to test out APIs - OpenSupporter Sandbox

Go to http://public.demo.osdi.io

Next steps? Add the FAQ? Add somewhere else on the website?

Augustus is happy to set up sandbox for callhub!

Recreate the netroots walkthrough (was action network or databank, callhub, hero) as a webinar/video?

Augustus will create a callhub connection to sandbox

On Hold - to be returned to in Jan (which is now!)

Voter Reg and Rides to Polls Data Work

Check back in, mid-January

SMS Data

Make sure to include Augustus/callhub

4.0 - Closing

----

Tim Holahan
Product Manager, Broadstripes LLC
tim.h...@broadstripes.com
(203) 687-6186