☎ protocol: CALLS
< DRAFT+ >
Revisions:
20190730 draft
20190914 add <d
20190921 cleanup
20190921 overview +lies during call
20200722 first working call after L leaves cht7bf
20210209 D+L "retry using this" →D
20210228 quick ping
20230207 ping → needs work [!!**]
Ties to:
* 🔗postchatter — chats are bad
* [...]
Table of Contents
¶* Initiation and Regularity
Skip this step if you already have an agreed initiation style.
Do you have an agreed Initiation Style?:
→Skip.
¶ A) Just call me anytime ← BEST
Call me anytime on GSM, we can then move to another channel.
Proposed channels are (2023):
Telegram or a web Jitsi instance, like https://meet.jit.si/.
Call me anytime on GSM, we can then move to another channel.
Proposed channels are (2023):
Telegram or a web Jitsi instance, like https://meet.jit.si/.
¶ B) Call via shared availability slots:
For busy people, this should be more common, published on personal website.
Can be a calendar with open call slots, or the reverse pattern, a fully published calendar ("busy slots").
Example:
"I am free ___ ("afternoons 3-7PM every day)"
For busy people, this should be more common, published on personal website.
Can be a calendar with open call slots, or the reverse pattern, a fully published calendar ("busy slots").
Example:
"I am free ___ ("afternoons 3-7PM every day)"
¶ C) Schedule a call ("Let's talk at XY")
But, this sucks, if you're not sitting in an office. (So, no good for nomadic people).
"Is this specific office-time slot good for you?" or "What time is convenient to talk to you" is more meaningless and complicated than it might seem 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 sucks, if you're not sitting in an office. (So, no good for nomadic people).
"Is this specific office-time slot good for you?" or "What time is convenient to talk to you" is more meaningless and complicated than it might seem 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"
¶ (patterns)
* Establish interest (or obligation) to do it !
"hey, wanna talk sometime next week?"
-- yes !
* Call for real, or fuck off:
you give somebody a number
→ you MUST be able to give them a Short Call in so called Reasonable Time
if not:
→ just stop pretending you want to call & tell them to fuck off
* Reasonable Regularity:
* 3 days? 1 week?
* depends on urgency the initiator gives to call!
-------
* ESTABLISH: during Pre-prep?
* CONFIRM: during Call
* Good agendas make for short calls:
Short Calls MUST have a pre-defined agenda
* Repeat unanswered calls to show urgency:
(already a commonly recognized way)
* "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 !
* Switch call initiation:
A calls week 1, B calls week 2
* 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)
* Pause 2 hours before retrying:
when to call back, or expect being called back?:
maybe in an hour or two
* Don't message about calls:
#antichatter
Never "when can i call you" message me!
EXCEPT IF ... / IN THE FORM OF ...
* Set a regularity expectation:
"~1/month"
* Deal with broken regularity:
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
people working together see eachother every day, have regular meetings, etc. we should be at least as good as X.
* Wednesday pong & "short week":
If we talk (i "pinged") on wednesday
It's best you pong on monday or tuesday
Calling wednesday should be a "last resort", OR a "clear" message we should downgrade connection
* Establish interest (or obligation) to do it !
"hey, wanna talk sometime next week?"
-- yes !
* Call for real, or fuck off:
you give somebody a number
→ you MUST be able to give them a Short Call in so called Reasonable Time
if not:
→ just stop pretending you want to call & tell them to fuck off
* Reasonable Regularity:
* 3 days? 1 week?
* depends on urgency the initiator gives to call!
-------
* ESTABLISH: during Pre-prep?
* CONFIRM: during Call
* Good agendas make for short calls:
Short Calls MUST have a pre-defined agenda
* Repeat unanswered calls to show urgency:
(already a commonly recognized way)
* "Ping-pong" when returning calls:
A calls, B doesn't answer → B calls back
* Switch call initiation:
A calls week 1, B calls week 2
* 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)
* Pause 2 hours before retrying:
when to call back, or expect being called back?:
maybe in an hour or two
* Don't message about calls:
Never "when can i call you" message me!
EXCEPT IF ... / IN THE FORM OF ...
* Set a regularity expectation:
"~1/month"
* Deal with broken regularity:
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
people working together see eachother every day, have regular meetings, etc. we should be at least as good as X.
* Wednesday pong & "short week":
If we talk (i "pinged") on wednesday
It's best you pong on monday or tuesday
Calling wednesday should be a "last resort", OR a "clear" message we should downgrade connection
¶* Correct Tools & Workflow
Equipment & Context
Inform / apologize in advance if something from this is missing!
Inform / apologize in advance if something from this is missing!
¶ * 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)
¶ * Call channel
_____ Proposed
* Establish connection with GSM
* Have free minutes?:
YES) KEEP GSM
NO) Use:
1) telegram ON PHONE
2) whatsapp ON PHONE
3) ###:
_____ Proposed
* Establish connection with GSM
* Have free minutes?:
YES) KEEP GSM
NO) Use:
1) telegram ON PHONE
2) whatsapp ON PHONE
3) ###:
¶ * Pick best data channel
4G often works better than Wifi !
You need to experiment and know this in advance (for all locations where you might telephone!)
4G often works better than Wifi !
You need to experiment and know this in advance (for all locations where you might telephone!)
¶ * Establish recording policy
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
* ### [...]
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
* ### [...]
¶*** AGENDA BITS
Recomposing & shuffling different agenda bits / patterns / modules.
aka "MODULAR CALL TEMPLATES"
aka "OTHER AGENDAS"
aka "SUB-AGENDAS"
Recomposing & shuffling different agenda bits / patterns / modules.
¶* regular / random updates
###aka: regular random report
* 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.
### too CHT-specific
always / often:
* 🔗works
* XXX🔗todos
* 🔗todos
* [...]
also / sometimes:
* XXX🔗agenda — mid-term plans
* [...]
Go to regular todo docs.
always / often:
* 🔗works
* XXX🔗todos
* 🔗todos
* [...]
also / sometimes:
* XXX🔗agenda — mid-term plans
* [...]
¶* ping: personal work index
### THIS IS A PRETTY MUCH ALWAYS BIT ?
### [→] move this somewhere else
aka "main/personal work pad checkup"
:
* "level zero" TOC overview:
aka "make sure TOC is not totally fucked"
* check "[C" tasks
* [...] ###
aka "main/personal work pad checkup"
:
* "level zero" TOC overview:
aka "make sure TOC is not totally fucked"
* check "[C" tasks
* [...] ###
¶* editorial on specific pad
Pick randomly, from current work, or 🔗RFCs.
or XXX🔗queue.
$$$$ REVIEW 20210329
Pick randomly, from current work, or 🔗RFCs.
¶* presto reading and improving pads
Pick a random pad and push it.
Or, something we haven't touched in a while
Usually PD→D.
A) via 🔗oversee
B) via personal indexes
C) ###
Pick a random pad and push it.
Or, something we haven't touched in a while
Usually PD→D.
A) via 🔗oversee
B) via personal indexes
C) ###
¶( HOW TO PICK BITS )
Curating agenda.
* Essential:
"We must always push 2 or 3 pads."
* Cycles:
"We haven't done Works in a while"
* Shuffle:
"Throw a dice! Oh no, it's salvaging time!"
Curating agenda.
* Essential:
"We must always push 2 or 3 pads."
* Cycles:
"We haven't done Works in a while"
* Shuffle:
"Throw a dice! Oh no, it's salvaging time!"
¶ * FAST SKIPPING
Do the more regular partss really fast.
Like, all tasks — just run through them!
This could produce imprints.
Do the more regular partss really fast.
Like, all tasks — just run through them!
This could produce imprints.
¶ * EXECUTE > PLAN
Don't spend more time on planning than on doing!
"Does it make sense to keep re-reading the tasks?"
Don't spend more time on planning than on doing!
"Does it make sense to keep re-reading the tasks?"
¶ * AGENDA FOR NEW COLLABORATORS
Either:
A) pre-write an agenda & pre-share the link in a pad
B) just improvise it (assembled as point #0)
Either:
A) pre-write an agenda & pre-share the link in a pad
B) just improvise it (assembled as point #0)
¶ * 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
* ... finding & tagging DONE parts <------------ not sure what this means
* independent review of agenda
¶ * review
* "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)
¶ * reprioretize current agenda:
each suggests (ping-pong) style:
* re-sorting points of order
* ... either as:
A) "ANARCHIST":
move stuff yourself to appropriate position in agenda
B) "ORDERLY":
suggestions to a Single Editor Person
_____________________
Stuff that typical gets priority:
* time-critical shit !!
* cleaning up, merging fragments, etc
* [...]
each suggests (ping-pong) style:
* re-sorting points of order
* ... either as:
A) "ANARCHIST":
move stuff yourself to appropriate position in agenda
B) "ORDERLY":
suggestions to a Single Editor Person
_____________________
Stuff that typical gets priority:
* time-critical shit !!
* cleaning up, merging fragments, 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!)
* ###
¶[!] workflow/tools -- we need screen-sharing #workflow !!!
* would be faster for many tasks we are doing
* perhaps two-sided would be best !!!
_________
A) jitsi works (but ... not secure ... in a way?!)
B) 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 !!!
_________
A) jitsi works (but ... not secure ... in a way?!)
B) dedicated app ???:
anything free, but cross-platform?:
just ... VNC i guess?
¶[!↑] good meetings resources
### merge to a "resources" part
https://meetingexpectations.surge.sh/#/20
<dmytri
<-------------------------- ((new))
https://meetingexpectations.surge.sh/#/20
<dmytri
<-------------------------- ((new))