Jan 8 2021
I currently do not have any image in mind. I'll be really glad if you could help with that.
Jan 5 2021
Yes, here is a link to it. https://www.mediawiki.org/wiki/Documentation/Documentation_Review_Processes
Dec 9 2020
That's fine Sarah. Thanks!
Dec 8 2020
Dec 7 2020
Thanks for the prompt @Aklapper. Nothing is left, hence closing as resolved.
Dec 2 2020
Dec 1 2020
Nov 25 2020
There is, and it has been added(Although it is still a draft). The "this document" hyperlinks to it.
Nov 23 2020
@Aklapper, the process looks good to Alex and Sarah as well. But we'll like to have a test review using this process just to be sure nothing was left out before proceeding to making it a standard review process.
Nov 19 2020
Nov 18 2020
I just watched https://www.youtube.com/watch?v=zm5Iw7jsyC4 (23 minutes) and that's a very interesting, great talk on managing docs.
A process is only as good as its discoverability. :)
Nov 16 2020
Nov 13 2020
Nov 12 2020
Yes, I totally agree. This was why I suggested having a review admin who would oversee the review process and encourage people to adopt it. The admin would also be responsible for getting people to review these documentations, and since its just one review step, the process is not intense.
This is very insightful, thanks a lot @Aklapper.
Nov 10 2020
I either don't understand, and/or we might be getting lost in terms here. One Phab project has one workboard. A workboard has columns. Columns can be used either for progress tracking or for categorizing tasks. I don't know what you mean by "the category the task belongs". Categories of tasks usually do not change.
PS: General note: Please feel encouraged to replace "he" with "they" in sentences, for some more inclusiveness.
I am deeply sorry if that was perceived as offensive, that wasn't my intention. I will be more cautious with my use of pronouns.
It's currently unclear to me how that would be implemented and where.
In any case: Relying on single individuals creates bottlenecks and basically never scales
I wasn't aware that tags are meant to be static, using workboard columns to express progress is a really great Idea!
I don't understand how "in-review / needs-review" and "prototype review / technical review / non-technical review" relate to each other.
Maybe this means "Create a dedicated task for a dedicated piece of documentation work"?
Workboard uses should not and cannot be mixed: there should not be columns to both track progress (e.g. "in-review") and track categories on one single board as a task can only be in one column on a workboard.
Hi @Aklapper Thanks a lot for the thorough feedbacks. It's very much appreciated.
Nov 6 2020
Thanks a lot for the feedbacks @srodlund.