Backend - Organization Registry - Add Functionality indicating if buses will depart from a designated meeting place

[PamelaJohn]

I am an organization which wants to provide carpool services by designating a bus which will depart from a designated meeting place rather than stopping at individual residences to pick people up.

I am an operator who needs to know when a bus will be departing from a designated meeting place rather than stopping at individual residences to pick people up.

Operators need some kind of indicator on the Operation Registry (perhaps a check box) which indicates whether certain buses are departing from a designated meeting place or are available to pick people up from multiple residence addresses.

[jkbits1]

@acqsysandrea @aaghevli following our meeting, just pinging about these as discussed

[jkbits1]

@PamelaJohn this is a good real-world issue but tricky because it doesn't align with how the system is designed.

A work-around would be for riders to put in the address of the designated meeting place as their address. It would be up to the operators to tell the riders about this. Similarly, neither the operator nor driver should accept rides where the address is not the meeting place.

As it does reflect the real-world, I've created a new label 2019+ so we can review this after the mid-terms

[jkbits1]

@stephenscapelliti something to archive?

[stephenscapelliti]

@jkbits1 it's @PamelaJohn's issue, so best to ask her.

[jkbits1]

@stephenscapelliti sorry, I could have been more clear. I wasn't asking you to decide on someone else's issue, just contacting you as our resident "archivist" 🙂 this and a few other issues contain some useful discussions or comments that may be lost if the issue is closed. For some closed issues, the request will occur again naturally as the system is used, but the comment here may not be, or not so well explained, anyway.

The context is that I'm trying to cut down on various outstanding issues so that new volunteers can read through the issues and find out easily if something is appropriate to their skills or interests them. It's perfectly valid that we use github issues for discussion purposes but if that discussion become less relevant or isn't picked up on by other team members, it can be better to close it.

This issue will stay open with the 2019+ label as it seems very relevant to some organisations.

No need for you to be the "archivist" btw, just picking up on a comment by you in another discussion.

[stephenscapelliti]

Thank you, @jkbits1. 😄 I recall that. I'm looking forward to the next round of updates. This all looks amazing. Thanks for all your hard work.