When I saw the kanban/taiga mentioned on the test list today, I thought
about a comment KParal made a while back about that there were some Test
Cases that he knew of that needed some updating. I'm aware of some too.
It seems to me we could use the kanban to keep our test documentation up
to date. We could use Issues to propose a change in a document or
propose a new document. As soon as the proposal got a certain number of
+1 votes the proposal could be transferred to the kanban where anyone so
inclined could make the draft and push it on for review. etc. etc. like
they do at Fedora Mazazine.
Anyone could write a proposal, anyone could do the draft. We'd need a
few select editors to judge if a draft was ready for a broader review
then if ready for publishing.
This would provide more visibility for the document work that is needed.
This could also help move the burden from a few people to the broader
community.
Have a Great Day!
Pat (tablepc)
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
