Catalyst Improvement Task Force Fund 10--3rd Meeting === ### Agenda and meeting notes ###### tags: `Meeting` `Agenda` :::info - **Location:** [Catalyst United Server Hub Chat](https://discord.com/channels/946921942143885342/946921942525571133) - **Date:** Tuesday, October 18th, 2pm UTC - **Agenda** 1. Public Portal for WG/TF `20min` > [name=???] 2. Core Documentation Standardization Suggestion `20min` > [name=Jeffrey Mashaw] [Suggestion Doc on Hackmd](https://hackmd.io/d-Ekxy3ATMmNfz2G8a0kqQ) 3. Item 3 `00min` > [name=???] 4. Item 4 `00min` > [name=???] 5. Discuss ex-officio trustee for vPA Process Working Group (time permitting) `00min` - **Participants:** - Dan - Simon - Ratio - Jeffrey - Tevo - Babowsky - CaptainDang - Others ??? - **Contact:** JeremyB#9734 on discord - **Facilitator:** ?? - **Reference:** - [Last meeting minutes](https://hackmd.io/Dp8DDnAwR2O2DnQDQGPP_Q?both) ::: :mega: Public Portal for Task Force/WG --- - We need to discuss and consider our options for how the Task Force (temporary) and WG (longer term) should be accessible. - Accessibility includes not just the community (public) but also the membership. A simple portal where all resources and assets are collated. - Worth noting that a requirement of the WG (as noted in its charter) is to have a "Meeting Page" which is effectively a 'homepage' for the WG, where members are listed, meetings and minutes are archived for reference, and all tasks, assets and deliverables are easily found. - The PA/vPA Treasury will be building out [its own portal via HackMD](https://hackmd.io/@PA-vPATreasury/SynfeL8Xo/https%3A%2F%2Fhackmd.io%2F%40PA-vPATreasury%2FHJWOQI87j, and the WG and its task forces could be included there. [This Miro board](https://miro.com/app/board/uXjVPPEmlSk=/?share_link_id=393453349508) shows how WGs would be linked up to the main Portal for the Treasury. :::danger - IOG will likely be rolling out a "Catalyst Portal" that will be considered the 'Official' Catalyst Website. Any work we do should consider how it will interoperate and integrate into such efforts.:fire: ::: :gear: Core Documentation Standardization Suggestion --- [Suggestion Doc on Hackmd](https://hackmd.io/d-Ekxy3ATMmNfz2G8a0kqQ) * A suggestion for standardizing the core documentation so that improvement suggestions can be formatted in a way that leads to actionable tasks. :gear: Topic Coordinators to manage the work --- - We need a system for defining, accepting task applicants, evaluating the applicants and then rewarding them - Suggestion: - Introduce WG Topic coordinator roles - Each coordinator(s) is responsible for tasks within a specific area, e.g. Guidelines, vPA incentives & petition, Reforms, Auditing. - The topic coordinator(s) makes sure task descriptions follow the agreed upon format - Topic coordinator(s) finds reviewers who can approve or disapprove submissions. Usually it'll be the coordinators themselves - Topic coordinators also define the reward for completing each task through separate discussion meetings. - Being an area coordinator is a task itself. Suggestion = announce them on Thursday? For guidelines we'd need 3 people I recon. For other topics, we only need 1. :gear: What is IOHK doing? --- - Ideally, they join in on the discussion and work with us on the improvements, joining forces with the community... - Any news on this? - Best case scenario is we have a meeting with them and divide the work somehow :gear: Item 4 --- - :scroll: ~~Trustee discussion (if time allows)~~ Did not happen --- - 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 ## Tevo suggested topics 1. Innovation Fund Research Proposal improvement 2. Fund 11 Catalyst Governance Challenge Settings 3. Proposal Guide info (working on Mini Proposal Workshop template - will be ported to Dework) 4. Project Management framework workshops starting next month (educational material) - using Dework and other platforms 5. Focus areas for Catalyst Change Makers - Splitting Proposal Assessment stage into 2 (proposal validation stage based on proposal requirements and proposal feedback stage) - Changing validation metrics for veteran Proposal Assessors - Transparent and clear process and requirements for receiving funds for Funded proposals. (recently its been damaging and unclear for many why IOG does not do payments to funded proposals) :wrench: Tasks Assigned/Accomplished -- ### Guidelines Task Group: - [x] Working doc established - [Proposer, PA, vPA Guidelines Tasks Set-up Doc](https://hackmd.io/VFYwBvs7RVKkGiyahElwZA) - [ ] Organize effort to do initial sorting of backlog - [ ] Plan for communication with other stakeholders - [ ] Organize async space for the guidelines/documentation work specifically ### Reforms and Experiments: - [ ] Read Simon's doc and discuss async [Reforms and Experiments Doc](https://hackmd.io/@meZ8FgaaTlmP5hQnROPwIA/B1Kt_OWQo) - [ ] Add specific agenda item based on discussion for next meeting - [ ] ### Task Force Coordination: - [ ] Set up and announce next WG meeting - [x] Set up When2Meet for next week - [ ] Build agenda for next meeting - [x] Setup Async space for discussing and collecting thoughts on establishing payrates for the working group - [ ] [Collect input and insight on the issue](https://app.dework.xyz/catalyst-circle-ca-r/veteran-ca-wg?taskId=6db9cc18-fb28-4e52-ab56-96a1c869fa46) - [ ] Setup async space for discussing the organization of dework spaces for the WG, especially documentation - [ ] Establish subspace for Fund 10 documentation in community suggestions to have a place to sort suggestions to ### Appointment of Trustee: - [x] Can we set up async space where we can capture the overall conversation on this issue? - [x] Async space set up with [this dework thread.](https://app.dework.xyz/catalyst-circle-ca-r/veteran-ca-wg?taskId=68d6c93a-c374-4b64-9b68-14c6dd10357a) ## Notes **Decisions** - Tevo will coordinate with Jeffrey concerning the admin access to the ProjectCatalyst.st GitHub account. - Master file of all core documents in a GitHub repo - Standard format for core documentation - Standard format for proposing changes to core documentation **To Do** - Determine standardized requirents for documentation or improvemenet change requests (per Jeffrey). - From the information above generate a template for Dework task submissions. Must apply rules i.e. 'members must submit in the template of submission is discarded' **Process flow** 1. *Issues submission*. Low barrier-to-entry. Possible in multiple places in the ecosystem. 2. *Task creation*. Dework tasks to research/write proposal changes based on stuff in point 1 (Topic Coordinators) 3. *Solving problem*. People take up the bounties and produce actionble document change proposals using a standardised format. 4. *Consensus*. Through voting on proposals using pollbot/hazelbot. DripDropz for very large changes. 5. *Merge*. Topic coordinators make pull requests to the project-catalyst repo where we keep the official guidelines ## Meeting Minutes <!-- --> ## Recording - [MP3](https://drive.google.com/file/d/1e1dcrsT5DX9PTB71ZUVbHcFe_GKSDcpJ/view?usp=sharing)