Rideshare Server (Operator Tooling)

[hwhelchel]

What do you want to see covered in the TRIP Report newsletter?

The DEC engineering team is building Rideshare Server software to power TRIP Operators on the network.

This software will be used starting in the Genesis City in Texas to match riders and drivers on the network as well as record ride activity on Solana. I'd like to see an issue of the TRIP Report newsletter that educates our community on how it works.

Areas of coverage could include:

• What's a TRIP Operator
• Why TRIP Operators need Rideshare Server software
• How the initial Rideshare Server software works
• DEC Engineering's vision for how the Rideshare Server software will change and improve from here
• Quotes and perspectives from other members of the DEC team as well as early TRIP community members
• Videos and photos of the software showing how it works

Are you interested in writing this newsletter yourself?

I would gladly support and advise anyone interested in contributing this issue.

[r-woosley]

Is there any current documentation on the current state of the rideshare server software? Here are some general items that could be covered in regards to how the software works/walkthrough

Hosting

• Options for hosting the server

Admin Panel

• Dashboard
• Admin management
• Rider/Driver management
• Ride management
• Pricing management
• Notifications
• Payouts
• Promocodes
• Ratings
• Map Views/Heat maps
• Geofencing

Customer Support

• Rider/Driver support solutions ex. Zendesk
• Outsourcing Solutions
• Build Integrations/Slack feeds

[hwhelchel]

@ivandiku has access to a dev version of the rideshare server. A production version will be going live soon for the Genesis City. Ivan how about you and Ryan find a time in the coming weeks to walk through the operator tooling and how it works together? Would that be alright?