Catalyst Improvement Task Force Fund 10--4th Meeting
===
### Agenda and meeting notes
###### tags: `Meeting` `Agenda`
:::info
- **Location:** [Catalyst United Server Hub Chat](https://discord.com/channels/946921942143885342/946921942525571133)
- **Date:** Tuesday, October 25th, 3pm UTC
- **Agenda**
1. Task force purpose, membership and roadmap `15min`
> [name=Simon]
2. Establish starting payrate for tasks `15min`
> [name=JeremyB]
3. Tasks template `15min`
> [name=Simon and Dan]
4. Discuss ex-officio trustee for vPA Process Working Group `15min`
> [name=JeremyB]
- **Participants:**
- Simon Sallstrom
- AlexanderRau
- Ratio13
- Jeffrey Mashaw
- JeremyB
- GeorgeJR
- Tevo Saks
- Quasar
- vgr
- Dan Mercurius
- **Contact:** JeremyB#9734 on discord
- **Facilitator:** ??
- **Reference:** - [Last meeting minutes](https://hackmd.io/@PA-vPATreasury/HyLvz3NXs)
:::
:gear: Task Force purpose, membership, roadmap
---
- Check out Simons suggestion https://hackmd.io/@PA-vPATreasury/S1H32eyNs
- Share what you think and how you arrived at that conclusion!
:moneybag: Establish starting Payrate
---
- Let's hold a vote to set a WG payrate.
- We should consider how it creates a 'floor' for bounties under this WG and what that might mean.
- We should consider whether it is based on hours or task points.
- The benefit of hours is that it is familiar and easily understood and could potentially circumvent the 'floor' effect.
- Hours however are widely understood to be an inaccurate and wasteful measure of value, especially in decentralized or holocratic systems
- The benefits of task points are that Dework uses that measure, and it allows flexible assignment of value to things like deliverables and participation
- Task Points however are not necessarily intuitive and adopting them may create delays in compensating valid work
- We should consider whether we want to price in $ or ADA (or Hosky!)
- A starting rate of $40 per [unit] has been suggested. We can vote on this or provide a poll with multiple options.
:gear: Task template discussion (move to async)
---
- See overview and discussion in this document https://hackmd.io/wS3F6hogRZSO-ey5n84v2g?view
- Alternative 1
```
What is the problem?
... This should be one sentence.
What are some potential solutions? (optional)
... These should be rough sketches, one sentence each
(you may add more info to the bounty hunter in background section below)
What are the acceptance criteria for this task?
... For example, "Quantitative data with a sample size of at least 10",
"Two Propositions on how to solve the problem",
"A clearer formulation of section 1.2.4"
Please provide additional background and links here
...
```
:scroll: Trustee discussion (tabled)
---
- Discuss any points brought up in the [async discussion](https://app.dework.xyz/catalyst-circle-ca-r/veteran-ca-wg?taskId=68d6c93a-c374-4b64-9b68-14c6dd10357a) around appointment of a Trustee by this Working Group
- Decide on strategy to find 4 more trustees
- Is Nadia available?
- Where should trustees related to working groups be pulled from? Does it make sense to have trustee appointed from outside the immediate ecosystem, in order to have internal oversight?
:wrench: Tasks Assigned/Accomplished
--
### General Tasks:
- [ ] Complete Code of Conduct page and add link to Task Force Page
- [ ] Finalize a task template for dework
- [ ] What does the "Change Log" space for a given fund look like? Set up a task in dework to start ideating and capturing input.
### Task Force Milestones:
- [ ] Gather Core documentation into Github
### Appointment of Trustee:
- [ ] Make decision about whether to appoint a trustee
## Notes
- Reviewed the document from Item 1 above, and went through and generally ratified all sections of the document. This language was deemed acceptable for defining the purpose and goals of the Task Force.
- It was pointed out that under participation there should be an indication of general community guidelines, and agreed that adding the Code of Conduct link in relevant areas was needed.
- The milestones section of the above doc was discussed, and it was agree that these would be good stretch goals for the Task Force to adopt.
- The question was brought up about how collaboration and coordination could be structured and encouraged. The point was made that a space needed to be created (combination of a repo and a convening) to facilitate the creation and sharing of a "change log" each fund. Such a space would provide an opportunity for bringing all work from any sector of the community into alignment before presenting a batch of formal change requests to IOG/Catalyst. Such a space would also be a place for various groups to check in as they were working on their solutions.
- Starting payrates were discussed and it was generally agreed to avoid adopting too much of a 'legacy paradigm', but that a starting rate should be agreed upon.
- A poll was suggested for async input with the following items seeking approval (all received near unanimous support):
- $40/unit
- Task Points rather than hours for units
- Repository of past tasks and points assigned
- Set a time to analayze the repo and iterate the price per unit
- General flow would be for the task creator to suggest the number of units for a task (set the task price) and then the other group memebers should discuss and vote to finalize the suggestion
- The subject of capping the price of tasks came up. It was generally agreed that a cap made sense and would be more sustainable. Also indicated was that if a task was accruing too many units, it was an indicator that the task needed to be broken up and distributed more.
- It was agreed to keep the conversation on basic 'working group economics' open and lively in the Catalyst United Discord thread linked above. This includes the subject of capping rates, as well as pricing in ADA rather than $.
- Meeting was concluded at the one hour mark, though Dan and Simon stayed on in order to discuss the task template from Item 3 above.
- Appointment of a trustee was tabled.
## Meeting Minutes
<!-- -->
## Recording
- [Audio Recording](https://drive.google.com/file/d/1K-hUV9AdZKEodJ2XXrQICZS-vMxWyhWB/view?usp=sharing)