☎ protocol: CALLS
< RFC >
Revisions:
20190730 draft
20251104 quick overview →RFC
Ties to:
* 🔗postchatter: chats are bad
* 🔗workflow
Table of Contents
¶*** GRAPH (BASICS)
[!!!] Proposal: Only keep initiation parts for graph
You have INITIATOR(A) and RECEIVER(B).
You have INITIATOR(A) and RECEIVER(B).
¶*** Protocol: INITIATION & REGULARITY
Skip this step if you already have an agreed initiation style.
¶ A) Just call anytime. (This is best.)
Call anytime on GSM, we can then move to another channel.
Channel options are:
A) stay on GSM
B) Telegram
C) a trusted Jitsi instance, like ###
Call anytime on GSM, we can then move to another channel.
Channel options are:
A) stay on GSM
B) Telegram
C) a trusted Jitsi instance, like ###
¶ B) Call via shared availability slots
For "busy people" — please publish, on your personal site:
A) "free slots" calendar
B) (the reverse) "busy slots", usually semi-obscured calendar
Example:
* "I am free _____ ("afternoons 3-7PM every day)"
* (or link to your calendar app)
For "busy people" — please publish, on your personal site:
A) "free slots" calendar
B) (the reverse) "busy slots", usually semi-obscured calendar
Example:
* "I am free _____ ("afternoons 3-7PM every day)"
* (or link to your calendar app)
¶ C) Schedule a call ("Let's talk at XY")
But, this can be a complication if you are not sitting in an office every day (so, especially for nomadic people):
* "Is this specific office-time slot good for you?", "How about 11am next Sunday?"
* "What time is convenient to talk to you"?
Responses:
A) (probability):
--"OK, might work 70%"
B) (urgency!):
--"I will be there for sure, because it's urgent"
C) (availability):
--"I will be there for sure, because I generally have nothing to do"
But, this can be a complication if you are not sitting in an office every day (so, especially for nomadic people):
* "Is this specific office-time slot good for you?", "How about 11am next Sunday?"
* "What time is convenient to talk to you"?
Responses:
A) (probability):
--"OK, might work 70%"
B) (urgency!):
--"I will be there for sure, because it's urgent"
C) (availability):
--"I will be there for sure, because I generally have nothing to do"
¶ * Establish interest (or obligation)!
* "Hey, wanna talk sometime next week?" -- "Yes sure !"
* If you agreed to call & exchanged numbers, make (at least a short call) in reasonable time!
if not, just stop pretending you want to call & tell them to fuck off
* "Hey, wanna talk sometime next week?" -- "Yes sure !"
* If you agreed to call & exchanged numbers, make (at least a short call) in reasonable time!
¶ * Reasonable Regularity
* 3 days? 1 week?
* depends on urgency the initiator gives to call!
-------
* ESTABLISH: during Pre-prep?
* CONFIRM: during Call
* 3 days? 1 week?
* depends on urgency the initiator gives to call!
-------
* ESTABLISH: during Pre-prep?
* CONFIRM: during Call
¶ * Don't message about calls
Never send "when can I call you" messages ... just call, no overhead!
#antichatter
EXCEPT IF ... / IN THE FORM OF ...
Never send "when can I call you" messages ... just call, no overhead!
¶ * "Ping-pong" when returning calls
A calls, B doesn't answer → B calls back
if you get called, it's your responsibility to call back !
A calls, B doesn't answer → B calls back
¶ * When to call?
A) anytime !
B) base on approximate regularity
C) base on commonly understood SCHEDULE / SCHEDULE FRAME
D) call more regularly if you think things need to move:
(because they are not)
(this might feel counter-intuitive)
A) anytime !
B) base on approximate regularity
C) base on commonly understood SCHEDULE / SCHEDULE FRAME
D) call more regularly if you think things need to move:
(because they are not)
(this might feel counter-intuitive)
¶ * Pause 2 hours before retrying
(When to call back, or expect being called back?)
→ Maybe in an hour or two.
(When to call back, or expect being called back?)
→ Maybe in an hour or two.
¶ * Deal with broken regularity
1) try impromptu (3x)
2) try scheduling (3x)
3) re-set regularity expectation
1) try impromptu (3x)
2) try scheduling (3x)
3) re-set regularity expectation
¶ * Maintain responsibility for regularity
* Whose fault is it, if calls are not made?
* How bad is this?
* Should there be a baseline for different levels of collaboration?:
YES!
Mainline people are working together, see eachother every day, have regular meetings, etc!
We should be at least as serious!
* Whose fault is it, if calls are not made?
* How bad is this?
* Should there be a baseline for different levels of collaboration?:
YES!
Mainline people are working together, see eachother every day, have regular meetings, etc!
We should be at least as serious!
¶ * Raising regularity ("short week")
If we talk (I "pinged") on Wednesday, it's best if you pong on Monday or Tuesday.
The ideal is to go towards have more & shorter regularity, super-fast calls, and more work done off-call.
Otherwise, a connection should be intentionaly downgraded.
If we talk (I "pinged") on Wednesday, it's best if you pong on Monday or Tuesday.
The ideal is to go towards have more & shorter regularity, super-fast calls, and more work done off-call.
Otherwise, a connection should be intentionaly downgraded.
¶* Pre-setup quality Audio & Video
* Use earplugs (headphones), with mic !!
* Don't do it in external noise situation (except if urgent & agreed!)
* Set (lower) to correct earphone volume on phone:
(to not get headaches over it)
### establish with "what did you have to eat" or "recite me your national anthem"
* Use earplugs (headphones), with mic !!
* Don't do it in external noise situation (except if urgent & agreed!)
* Set (lower) to correct earphone volume on phone:
(to not get headaches over it)
¶* Pick call channel
Proposed:
* Establish connection with GSM
* Have free minutes?:
YES) KEEP GSM
NO) Use:
*) jitsi ON PHONE/LAPTOP
*) telegram ON PHONE
*) whatsapp ON PHONE
Proposed:
* Establish connection with GSM
* Have free minutes?:
YES) KEEP GSM
NO) Use:
*) jitsi ON PHONE/LAPTOP
*) telegram ON PHONE
*) whatsapp ON PHONE
¶* Use best data channel
* 4G often works better than Wifi !:
If you have a bad connection, first, try disabling wifi and seeing if it improves in a few seconds!
* You need to experiment and know this in advance (for all locations where you might telephone!):
Know where the best signal in is!
At least start the connection there!
* 4G often works better than Wifi !:
If you have a bad connection, first, try disabling wifi and seeing if it improves in a few seconds!
* You need to experiment and know this in advance (for all locations where you might telephone!):
Know where the best signal in is!
At least start the connection there!
¶* Establish recording policy
Options:
A) We agree & assume that there will be no recording:
(default, but to discuss, as not neccessary the best/most functional one)
B) Yes, if somebody remembers:
* informing it's recording
* start recording
C) Somebody is responsible:
(as above and also...)
* checking up on recording (make sure you don't run out of tape/space/x)
* keeping & regularly syncing the recordings
Tools:
* android call recorder
* jitsi has recording
* [...] ### #workflow
Recordings should be properly managed, available later, ideally synced with text, etc.
Options:
A) We agree & assume that there will be no recording:
(default, but to discuss, as not neccessary the best/most functional one)
B) Yes, if somebody remembers:
* informing it's recording
* start recording
C) Somebody is responsible:
(as above and also...)
* checking up on recording (make sure you don't run out of tape/space/x)
* keeping & regularly syncing the recordings
Tools:
* android call recorder
* jitsi has recording
Recordings should be properly managed, available later, ideally synced with text, etc.
¶ * "UH-HUH" (nods)
Give regular "nods" throughout the call.
* "uh-huh" so to clearly affirm you are there, on the right line, etc
* "i see" : i'm on the right line in a pad.... (= just wiggle your cursor!)
* ###
Give regular "nods" throughout the call.
* "uh-huh" so to clearly affirm you are there, on the right line, etc
* "i see" : i'm on the right line in a pad.... (= just wiggle your cursor!)
* ###
¶ * The agenda !
* create day pad
* apply the theme
* replicate meta-agenda
* check the last one (or few!) and refer to those points !
* create day pad
* apply the theme
* replicate meta-agenda
* check the last one (or few!) and refer to those points !
¶ * (Establish time constraints)
* Decide on approx time interval (length):
* "short" ~20min
* "optimum" ~1-2h
* "marathon" ~4h
* Decide on approx time interval (length):
* "short" ~20min
* "optimum" ~1-2h
* "marathon" ~4h
¶ * Take a short break
Independent review of agenda:
* re-prioretize (especially time critical!)
* clean up, merge fragments, etc
Independent review of agenda:
* re-prioretize (especially time critical!)
* clean up, merge fragments, etc
¶ * Superfast overview
* "break out" parts (=B+U)
* make quick remarks
* ... and try to form "fragments" like pieces:
(sometimes even already making them DONE)
* "break out" parts (=B+U)
* make quick remarks
* ... and try to form "fragments" like pieces:
(sometimes even already making them DONE)
¶PART 2: →MAIN WORK←
Recomposing & shuffling different agenda bits / patterns / modules.
aka "MODULAR CALL TEMPLATES"
aka "OTHER AGENDAS"
aka "SUB-AGENDAS"
Recomposing & shuffling different agenda bits / patterns / modules.
¶ * Facilitator guides current fragment focus
A) Auto-guided:
Using 🔗middlemachine
B) Essential
"We must always push 2 or 3 pads."
C) Cycles
"We haven't done Works in a while"
D) Shuffle
== "pick a random task → just do it"
"Throw a dice! Ok, let's salvage some old pads!"
A) Auto-guided:
Using 🔗middlemachine
B) Essential
"We must always push 2 or 3 pads."
C) Cycles
"We haven't done Works in a while"
D) Shuffle
== "pick a random task → just do it"
"Throw a dice! Ok, let's salvage some old pads!"
¶ * All take notes (especially the listening!)
This also helps to see if we understand eachother!
Obviously, use 🔗ethering !
This also helps to see if we understand eachother!
Obviously, use 🔗ethering !
¶ * Quick+Repeated > Slow+Stuck
Do the more regular parts really fast.
Especially "all tasks" — learn to just run through them!
Keeping time of this helps.
Do the more regular parts really fast.
Especially "all tasks" — learn to just run through them!
Keeping time of this helps.
¶ * Always brainstorm (but note quickly, don't takeover)
"This semi-related idea is currently on my mind, let's quickly note it, before I forge it"
"This semi-related idea is currently on my mind, let's quickly note it, before I forge it"
¶ * Execute > Plan
Don't spend more time on planning than on doing!
"Does it make sense to keep re-reading the tasks?"
(Though at the beginning in "brainstorming" phase, a lot of writing & editing is expected).
Don't spend more time on planning than on doing!
"Does it make sense to keep re-reading the tasks?"
(Though at the beginning in "brainstorming" phase, a lot of writing & editing is expected).
¶ * regular, random updates
* Outside main project:
* what have you been up to, where do you find yourself
* what's new on work on other (non-CHT) projects
* Inside main project:
* news from outside
* new tasks
* brief reports
* [...] ###
* Outside main project:
* what have you been up to, where do you find yourself
* what's new on work on other (non-CHT) projects
* Inside main project:
* news from outside
* new tasks
* brief reports
* [...] ###
¶ * overview: general works & todos
Go to regular todo docs.
→ 🔗works, XXX🔗todos, 🔗todos, XXX🔗agenda (mid-term plans), 🔗projects, [...]
Go to regular todo docs.
→ 🔗works, XXX🔗todos, 🔗todos, XXX🔗agenda (mid-term plans), 🔗projects, [...]
¶ * padwork: editorial on specific pad
Pick randomly, quick-read & improve pads.
From current work, 🔗RFCs, 🔗oversee, via personal indexes, ...
or XXX🔗queue.
Pick randomly, quick-read & improve pads.
From current work, 🔗RFCs, 🔗oversee, via personal indexes, ...
¶ * padwork: (via tools)
Use XXX🔗dev-hyperpods !
Use auto tools! :
* find "!!!!!!" and "??????" tasks
* overview NOW points
Use XXX🔗dev-hyperpods !
Use auto tools! :
* find "!!!!!!" and "??????" tasks
* overview NOW points
¶[!!**] WORKFLOW/TOOLS/ETHERBEAMER— We need a screen-sharing #workflow
* would be faster for many tasks we are doing
* perhaps two-sided would be best !!!
* consider security! (→ self host)
Options:
* jitsi
* BBB
* more dedicated app ???:
anything free, but cross-platform?:
just ... VNC i guess?
* would be faster for many tasks we are doing
* perhaps two-sided would be best !!!
* consider security! (→ self host)
Options:
* jitsi
* BBB
* more dedicated app ???:
anything free, but cross-platform?:
just ... VNC i guess?
¶[!!mi] SOURCE— Find & merge good meetings resources
* https://meetingexpectations.surge.sh/#/20
<dmytri
* ###
<-------------------------- ((new))
* https://meetingexpectations.surge.sh/#/20
<dmytri
* ###