Provide a pairing scheduler

[reinh]

As a user
So that I can find other users to pair with
I want to create pairing requests
And respond to the pairing requests of other users

A pairing request
Should include a time and duration
Should include a language
May reference a github project

[avdi]

See discussion on issue #2 - if there's one rathole I explicitly don't want to go down, it's scheduling :-) It's useless when it's simple, and even more annoyingly useless when it's complex.

[avdi]

...that said, the "lite" version of this is basically a contact form with fields for e.g. time zone, best hours to work, etc. After that the conversation can continue over email. I'm all for that.

[avdi]

An anecdote, based on personal experience, to explain some of my bias against dealing with scheduling: Let's say I have a pretty open schedule for pairing. There were maybe 5 potential 2-hour slots on a given day's schedule. So when I was using scheduling tools, I'd expose all of those slots.

BUT! Pairing is exhausting, and I don't actually want more than 2 sessions in a given day. And I don't really want two of them back-to-back either.

Pretty much all of the tools I've used were all-or-nothing: they assumed that if slots were open, they were open. Which left me holding the bag to explain "well, I know the tool SAID I was available then, but it doesn't really work for me..." when the tool let 4 people book back-to-back sessions.

Yes, you can code for this particular scenario, but this is just one example. The point is, tools, even complex tools, give an unrealistic picture of availability. And if the tool does something wrong, or confuses people in any way, they get mad at me, the person using it for scheduling, not at the tool. Because it's an obstacle I've thrown up between them and me. An annoying, broken (at least from their perspective) obstacle.

[reinh]

@avdi Yep, let's close this for now. There are bigger, tastier fish to fry.

[bf4]

Ah, but how about logging pairing sessions? rubyrogues/ppwm-matcher#47