life-itself / life-itself/web3
[epic] Transcribing episodes / interviews
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
Transcribe and publish each of our episodes e.g. https://web3.lifeitself.us/notes/samer-hassan
For each of our interviews we can publish a proof-edited transcript so that content is readable (not just listenable) and e.g. annotable, linkable, reusable (in others parts of wiki)
* Probably don't need this for episodes like deep dives with extensive notes
Process:
* [ ] Do an automated transcription with Otter
* [ ] Hackmd or similar and proof edit (or just publish direct and then do the tidying)
* [ ] Proof-edit
* [ ] Sign-off
* [ ] Publish
## Acceptance
## Tasks
* [ ] Prep
* [ ] List all the interviews (that require transcribing) - see the front page for a list - my initial guess is jeff emett, samer hassan, (hypha)
* [ ] Prioritize
* [ ] For each episode do the process above ...
* [ ] ...
* [ ] https://web3.lifeitself.us/notes/samer-hassan
### https://web3.lifeitself.us/notes/samer-hassan
* [x] Do an automated transcription with Otter
* [x] Transcription published direct to page
* [x] Issue created: https://github.com/life-itself/web3/issues/208
* [ ] Proof-edit
### https://web3.lifeitself.us/notes/jeff-emmett-on-regenerative-finance.md
* [x] Do an automated transcription with Otter
* [x] Transcription published direct to page
* [x] Issue created: https://github.com/life-itself/web3/issues/209
* [ ] Proof-edit
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the front page list of interviews and the existing notes pages for Samer Hassan and Jeff Emmett. Review the Otter transcription, Hackmd or similar editing step, and the linked follow-up issues 208 and 209. Done means each applicable interview is prioritized, proof-edited, signed off, and published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100