Meeting Note Archival
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- python
- Área
- documentation, tooling
Línea de trabajo
Empieza leyendo tools/import_meeting_notes.py e inspeccionando los archivos existentes de meeting_notes/{year}/. Sigue cómo podrían pasar las notas desde una ruta de entrada al archivo, conservando las reuniones recientes como contexto. Se considera terminado cuando el flujo de archivado sea fiable, produzca notas del repositorio que se puedan buscar y admita el proceso de sincronización de HackMD propuesto.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I'm writing this up as an issue so everybody can opine.
Right now, we use hackmd for meeting notes.
It's great for collaborative editing, but it's not the best from an archival perspective. Features such as full-text search and unlimited history are locked behind membership plans.
As a new member to the team, I struggled to find information covered in old meetings. I also struggled with immense browser slowdown and crashes when viewing/editing meeting notes (I thought it was my computer until Hannah mentioned that others experience it).
I was also confused as to the canonical location for archived notes, as they appeared on both hackmd and this repository.
I'd like the propose the following:
- We continue to use hackmd for meetings.
- We make this repo the "truth" for archival purposes. Existing notes on hackmd can redirect to the corresponding location in this repository.
- We use the "Push to GitHub" feature each month to save the current meeting notes to GitHub. Incoming meeting notes would be saved to a specific path, like
incoming/meeting_notes.mdorto_import/meeting_notes.md. - We use a variation of the
tools/import_meeting_notes.pyscript to extract the meeting notes from the "incoming" path and automatically put them into the correspondingmeeting_notes/{year}/…mdfile. - The script keeps the latest X meetings for context (maybe 4 meetings) and saves them back to
to_import/meeting_notes.md. - The trimmed file can be synced to hackmd via "Pull from GitHub". (Alternatively, we can manually trim the file on the hackmd side - whatever is easier).
Once we get steps 3 and 4 working reliably, it should be possible to either fully automate or at least automatically open up a PR for review.
We could also use the same approach for New Contributors Meetings notes and GSOC meeting notes.
Ideally, I'd like to make it as easy as possible to archive meeting notes so they get saved in searchable form more often.
- Lenguaje dominante
- Python
- Estrellas
- 3
- Forks
- 5
- Merge medio
- 2 d 14 h
- PR fusionados (30 d)
- 6
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
learningequality/ricecooker#747 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
run-llama/llama_index#23199 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
KhronosGroup/glTF-Blender-IO#2769 ·