life-itself/web3

[epic] Transcribing episodes / interviews

Open

Aperta il 14 set 2022

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)HTML (1644 star) (218 fork)batch import
good first issue

Descrizione

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/jeff-emmett-on-regenerative-finance.md

Guida contributor

Tech stack
Nessuno
Dominio
contentdocumentation
Tipo issue
documentation
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
over 1 week
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
access to Otter.aifamiliarity with web3 topicsproofreading skills
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
40
Direzione di ricerca
This issue is an epic tracking transcription of several interviews. As a newcomer, consider focusing on a single interview that still needs proof editing. Check sub issues #208 and #209 for status. The process is outlined: use Otter.ai for automated transcription, then proof edit and publish. Be aware that this issue has been open since 2022, so verify with maintainers if the work is still needed.