Knowledge Base Workgroup Using the Participation Reward Tooling
>> YOUR LINK HERE: ___ http://youtube.com/watch?v=C4a2ndoAuGc
Knowledge Base Workgroup 18.09.2024 Meeting Summary • People Present: Tevo, advanceameyaw, Lady, lord_kizzy, Effiom, Eric • Purpose: Aggregating Ambassador Program assets and relevant information under GitBook • Meeting notes: https://miro.com/app/board/uXjVN-9yiv... • Dework Updates: https://app.dework.xyz/singularitynet... • Knowledge Base Onboarding and Feedback • Discussion Points • Response Link: https://docs.google.com/spreadsheets/... • Did we learn something new from the responses? • 2 new responses were submitted • Does the feedback move a needle for the WG? • Did we get improvements? • One member learned about us from WIMS • In general our score is improving on the WG purpose • Decision items • The 1st new feedback won't be rewarded • The 2nd feedback will be rewarded • Assign Rewards for previous meetings using Participation Reward Tooling • Discussion Points • How we used Participation Reward Tooling today: • Knowledge Base Workgroup - Using the ... • Context what is the Participation Tool: • Process Guild - Tooling to compare Pa... • Check if the fitted reward amount in the prior meeting is fair • How do we address the reduced rewards left over from this process? • Can the purpose of the tool be modeled differently for each guild and WG? • Reward Modeler can use already collected data and analytics to define contribution type for their WG and Guild based on the label names • Explaining some of the parameters used in the Tool • What does reward import or task creation look like? • How do we define task label contribution type? • How do Guilds and WGs define their own contribution type? • We have been rewarding facilitation with Dework Tasks until now • Decision items • More members of the WG need to contribute as this would address the rewards wastage concerns • Remove operations in the task label for meeting participation. This will unlock labels to be recognized as contributions to future tasks • Action Items • Create a task for Automation WG - Create a guiding document on how the rewards are calculated. • Create a task for Automation WG - Create a meeting selector button to further automate the Tool. • Review Q4 Proposal Status • Discussion Points • Q4 consent responses: https://docs.google.com/spreadsheets/... • Review the 2 concerns raised by objectors in Iteration 2 • The best way to capture our impact in reports • Some of the concerns do not make sense, such as unclear how it adds value to the program. In Poprosal, it's clearly written. • Decision items • We changed budget details and split GitBook budget items into three smaller differences. • Action Items • Create a feedback form to ask people how they find the Knowledge Base WG organized assets • Keywords • Ambassador Gitbook, Miro Board, Feedback, Rewards, Q4 Proposal, Concerns, operations, Task labels
#############################