dblock / dblock/code.dblock.org

How (not) to have a one-way conversation

Open
#86 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

post topic suggestion
Dominant language
JavaScript
Stars
7
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Sometimes decisions have been made and the owner of the decision communicates it downstream wrapped into a conversation sandwich, otherwise known as a one-way conversation. Examples are: reorgs, technology decisions, ...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named; first clarify whether this is intended as an article, discussion, or other repository change. Define the expected scope and examples for one-way conversations, then document what completed work should contain and where it belongs.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.