Date
Goals
Time | Item | Who | Notes |
---|---|---|---|
10 min | Status | Everyone | |
Custom propType validators | Jae Bradley (Deactivated) | Slides, StackBlitz Example | |
ReactRenderer in edx-platform | Ari | Meet ReactRenderer, which makes it easier than ever to embed React components into non-React contexts. (Ari TODO: docs, demo usage PR). | |
Interview process update | Ari, Alasdair | We have a new Confluence page to track FED interview questions: /wiki/spaces/FEDX/pages/378602345 | |
Documentation | Ari |
Notes
Interview Process Stuff
- Useful to have some sort of rubric for first time interviewers, etc.
- Don't need the level of detail in the interview repo
Documentation
- Talk to people who have done the same thing, look at old PRs, git blame, etc
- Confluence (75% not helpful )
- Confluence, then Google (ReadTheDocs), then Hipchat
- Ask people
- ReadTheDocs feels more official
- More discussion
- Different types of documentation
- API (ReadTheDocs)
- Tutorials (probably ReadTheDocs)
- To do:
- Move everything into ReadTheDocs
- Stop being afraid of the docs repo
- Link people to PRs when they need quick help
- Ask doc team: what's the strategy for docs within repos vs. docs that tie all edx development together? Should edx-platform publish its own ReadTheDocs?
Action Items
- Demo ReactRenderer during dev demos