Migrate historic developer meetings
Open
Nobody has claimed this yet.
documentation
help wanted
migration
- Dominant language
- TypeScript
- Stars
- 74
- Forks
- 652
- Avg merge
- 2d 50m
- Merged PRs (30d)
- 12
Description
Migrate all historic meetings at https://docs.moodle.org/dev/Developer_meetings
This will involve determining the best format for them, perhaps including a custom jsx component for the table?
Don't forget to grab any files included as part of each meeting.
Contributor guide
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 by reviewing the historic meetings at https://docs.moodle.org/dev/Developer_meetings and inventorying each meeting and its included files. Then inspect the repository's existing documentation formats and JSX components before choosing the migration format. Done means all historic meetings and their associated files are represented consistently in the chosen format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100