Update Technical Writing role as per budget forecasting meeting
-
"This means either mentoring other contributors or acting as a fallback if no other contributor volunteers to do it." → does not match reality. Mentoring/reviewing should be a bullet point below and we should not pretend tech writers "act as a fallback": what follows is their responsibility; other people doing that work is an occasional exception. (62d9cd2b) - "Tasks which favor onboarding new contributors, either writing code or writing documentation.": covered by the addition of contributors doc below
-
"Documentation writing should be included in the budget if the feature has one." (48389791) -
"Tasks which have to be completed for a given version as documentation is a blocker for releasing." → s/as/because/ (f33589cd) -
clarify in the intro that it's primarily about end-user documentation (91ce37a2) -
Pages under /contribute that are not under the responsibility of another team, e.g. GitLab, Git, /contribute itself: with nobody responsible for maintaining and improving these pages, they kind of suck and we keep having problems while onboarding new contributors. (f9d88b40) -
Coordinate with UX to ensure new/modified bits of UI are consistent with the language used in our doc. If needed, propose phrasing. (fa457460)
Edited by sajolida