Yesterday during the contributors meetup, Nimisha introduced a new documentation writer they are bringing at edX to help improving the state of the developer documentation.
Survey
They have prepared a survey, which they are asking to fill:
It’s a good opportunity to influence their priorities with that project. Also, if you answer the survey, can you reply here to say so, so I know how many of us replied? Thanks!
Hackathon
They are also organizing a documentation hackathon next sprint (Jan 25-29th), to help completing the documentation of all the feature flags. They asked if we could participate, and I promised to ask you. It would be great if we could have at least a few participants to help with that - would anyone be willing and available for it next sprint? If so, can you reply to the current post, with how many hours you would be willing to commit? This will allow me to know how many people from our end would be participating, and for how long. (The time commitment is up to you, it doesn’t need to be many hours.)
Note that this would be a perfect task to include in the core committer hours for those who are alreaday core committers – or as a way to demonstrate core committer skills and commitments for those who will be core committers soon. :)
+1 to creating the tickets - they probably will need refining next week once we have more details on how it will be organized, but it will be useful to have them in the sprint already.
No hour limit on my side, just be careful that it doesn’t jeopardize your cell’s availability (ie still prioritize tasks from epics that had been planned for this month, only use extra availability for this), or sustainability (the contributions account is a cell account, so this will count against the cell’s sustainability ratio). For core committers, this can simply be part of your 20h/month.
@braden If you think there are better questions that haven’t been asked, that could end up being the best contribution to mention them? Or do you think that wouldn’t be helpful either?