Hey, curious what the next step is here. Is the idea for this to be a specific way to parse the sensed issues pile, or a way to get sorted tasks that are relevant to our documentation efforts structured as actionable tasks (most likely for dework)?

Newest Swarm version rubric: https://docs.google.com/document/d/1L7ixSfpjiEiy781XlqtBY02jLNf6Mz3bprTDCHyqVVY/edit# n

I have been using the rubric from Governance Oversight ever since we finished it and updating it based on external needs and requirements (mostly due to dework restrictions)

I think that the idea is to identify sensed issues that relate to documentation and then work through them in a probelm matrix sort of way, or by following through with Tevo’s Task reqs.

So @Jeffrey Mashaw, you will be using Tevo’s problem/task assignment rubric and maybe adapt it to better fit our needs to produce a document right?

i think having some section that details requirements of the submission/work is also necessary (not needed for problem rubric but necessary when making a task imo)

As I wrote separately, I think a smaller team of people (eg 3 ppl) who have a strong overview of Catalyst could then work through all tasks and then rank order the urgency/importance and put approximate hour efforts for them. Then there can be a general open meeting to ratify/accept/amend their work, specially individuals can raise objections to some rank order choice and then there’s a vote on that amendment

I do like the idea of working with a small team. I am more collaborative than solo, and I think that a smaller team working together to id the tasks and then having a larger group ratify makes a lot of sense.

@DanMercurius thoughts on this? @JeremyB