ucdavis / ucdavis/win

book name

Open
#39 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

"win" originally stood for "what if notes", because they they were notes versions of the what if book. however, over time I expect that this project will diverge from the original. what if by hernan and Robbins so we can rename it? what if? not! or what? if not? it's a joke on two levels. first, it's a nod to the fact that the key problem in the the fundamental problem of causal inference is that we can't observe the counterfactuals so half at least half of our data is always missing, at least for the outcomes. on another. in another sense, this book is not what the book. what if we can make a borat joke here? we can start the readme or the introduction saying this is a fork or a copy of the book. what if by her and robins. then leave a full screen width of blank space and then stick the meme of borat saying not. then explain why this book is not that book even though it originally was a copy outright.

Contributor guide

No contributing guide indexed for this repository

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

Start by reviewing the project README and introduction, which the issue identifies as the places for the name and explanation. Clarify the intended project name, relationship to the What If book, and whether the proposed meme belongs before making changes. Done should be an agreed naming and introductory presentation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.