Week 25
Mon 17th Jun - Sun 23rd Jun 2024
Last updated
Mon 17th Jun - Sun 23rd Jun 2024
Last updated
Type of meeting: Biweekly
Present: Tevo [facilitator], Tevo, Effiom [documenter], Tevo, Peter, kateri, Ayo, Kenichi, Billy, lord kizzy, vani
Purpose: Structuring Ambassador rules around payments, tasks and anything related to financial activities
Meeting video:
Miro board:
Other media:
Working Docs:
Treasury Guild transaction process https://docs.google.com/document/d/1sbZPqeS3-omflKMAg1SiYhG7hZG7Xqg34U-4SgUBd48/edit?usp=sharing
Exploring new ways of learning treasury operations and more guideline focused
Treasury Policy Template https://docs.google.com/document/d/1g-INSEasp4TsEWgGQSoTIxe-KLX79tXqzF3rhWbSI3M/edit?usp=sharing
More information can be found on 17.06 Policy WG Meeting Summary https://miro.com/app/board/uXjVKL5-fNY=/?moveToWidget=3458764592310197174&cot=10
Would these requirements be implemented for Quarter 3 proposals?
Are there any sanctions if these requirements are not adhered to?
Should the focus be on report format or requirement content?
How could we word better the requirements?
Workgroups/Guilds are allowed to have their own Reporting Format, but it should meet the requirements
[effect] mayAffectOtherPeople
Previous Guidelines and requirements are maintained for the creation of new WG
[effect] mayAffectOtherPeople
Guidelines document https://docs.google.com/document/d/1OkteXe_-UvvYuXh4hxrR4iRtOBHDKS_7ft8Yhn0EZpE/edit
What should be done if workgroup/guild don't submit on or before the deadline?
Should the proposal from previous quarter of the WG be adopted if they don't meet the deadline?
Would consenting still be done using google forms?
How feasible are the timelines set to ensure budget are approved before the start of Q3?
Do we provide GovWG tokens or make new ones for consenting on Proposals in Ambassador Program?
Proposals approved by the 2nd iteration share the leftover budget from the previous iteration
The proposal submission deadline of 19th June is for both the budget and quarterly report
[effect] mayAffectOtherPeople
Q2 Report is required for Q3 proposals that request budget increases for existing groups
[effect] mayAffectOtherPeople
There would be 2 iteration for submission and consent process
[effect] mayAffectOtherPeople
Proposals not approved after GovWG review on 2nd July, would be further reviewed
[effect] mayAffectOtherPeople
[action] Prepare consent forms right after submission phase [status] todo
Treasury Guild Q2 Report https://docs.google.com/document/d/1gUfkeZCwtw28gmpRShStBgRsOBaj6kRnxaJ7Ih2zZag/edit#heading=h.1w2fce1nfvp0
[action] Share your views, updates and comments to improve our reporting [status] todo
[action] Add contribution pictures from the dashboard [status] todo
[action] Add something to onboarding results [status] todo
Treasury Guild Q3 Proposal https://docs.google.com/document/d/16EmdnI9KXEF0iTfzdtSamRupuM3PITxlcfxqo4JT1o0/edit?usp=sharing
We create a new Treasury Automation Workgroup to build tools to speed up Transaction Creation processes. https://docs.google.com/document/d/18vPr6WIDKLNyFX1bGhIfvJjmU9mHe3C3Y1KtOjRFF9c/edit#heading=h.95bjzxymc8bt
We have removed Treasury Policy Workgroup information from Quarter 3 proposal currently no funding needed for this, but we will report on the results in Q3
topics covered: Budget report, Guidelines, deadlines, Proposals, Quarter 3, Reports, process
Type of meeting: Weekly
Present: Tevo [facilitator], Tevo [documenter], Tevo, Effiom, Kenichi, lord kizzy, Vanessa, Ayo, Onize, Gorga Siagian, Kareem, malik, Olokoji
Purpose: Design and Organize Ambassador Program Treasury Rules
Working Docs:
We spent more time ideating on the section, what are our current processes?
How should the policies be costed if there are more than 30 submissions?
Introduce limit for policies submitted monthly per person
How do we decide if policies are Valid?
How do we handle duplicate policies?
Let's use the Treasury Policy WG Retrospective session to capture insights
[effect] affectsOnlyThisWorkgroup
Let's use the Treasury Policy WG Retrospective session to check on policy limits and process
[effect] affectsOnlyThisWorkgroup
Increased the rewards for policy submission from 5$ to 10$
[effect] affectsOnlyThisWorkgroup
Reducing the proposal goals of 30 policies down to 15 policies
[effect] affectsOnlyThisWorkgroup
[action] Create a list of guiding questions to help bring out WG insights [status] todo
[action] Include Resource allocation and rules below introductions [status] todo
What should be written in the descriptions?
What questions should be included?
Should wallet address or discord name be collected?
topics covered: Miro Board, Google Form, Treasury Policy, Minimum Requirements, Requirements, Guidelines, Quiet Session
emotions: bit quiet
No Summary Given
Type of meeting: Weekly
Present: Felix [facilitator], LadyTempestt, CallyFromAuron [documenter], Felix, CallyFromAuron, billy, PeterE, esewilliams, nick, Ayo, LordKizzy, guillermolucero, Sucre n Spice, Duke, gavriel, Edet, martinsoki, photogee
Purpose: Weekly Governance WG meeting
Working Docs:
Governance WG Budget/Report: We agreed to submit the same budget as the previous quarter Felix will get to it soon and also draft the Q2 report.
Additional Governance Sessions: Do we host an open call to discuss governance topics concerning other WG or just check with the Strategy and Marketing Guild concerning the dates? This is mostly related to Marketing and Strategy Guilds needing some kind of support from us. Our fixed agenda for the month makes us less flexible in reacting to timely Governance changes or matters arising. The idea is to have it for a few weeks and then quit if it is no longer needed or helpful.
Next decision-making processes: What do we want to improve? From the retrospective we did, we found out that the timeline for the budget decision-making process is a bit rushy as people need more time to fill out stuff and the whole process was not announced properly. We discussed stretching out the timeline a bit even into Q4 and better communication patterns by possibly bringing it to everyone’s attention at Ambassador Townhall. There will also be monthly WG Leads’ Call starting next week. Will a step-by-step easy explainer video do the trick? Or a better resharing of the context setting document created by the onboarding WG? We want something self-explaining about the whole decision-making process for approving budgets.
Multi WG/Guilds Leads: We discussed workgroups deciding on internal representatives and the responsibilities of appointed leads, with a debate on whether formal leadership roles or a more shared approach to organizing tasks within workgroups would be more effective. We also considered the idea of co-leads in certain workgroups, alongside discussions on resource allocation for timestamping and archiving.
Upcoming Town Hall Presentation: Felix and Vani reviewed a presentation for the Town Hall meeting, ensuring alignment with the focus on budget and governance.
Lumio Video Update: Duke Peter provided an update on the Lumio video, with Felix reassuring him there was no rush.
Governance WG Budget/Report
Additional Governance Sessions
Next decision-making processes
Multi WG/Guilds Leads
Upcoming Town Hall Presentation
Lumio Video Update
We will host open governance calls on Thursdays by 14:00 UTC and start out with the Marketing and Strategy Guild.
[effect] mayAffectOtherPeople
There will be weekly governance calls to address ongoing topics and feedback.
[effect] mayAffectOtherPeople
Ese will be paid to add Felix's old documentation to the summary tool
[effect] affectsOnlyThisWorkgroup
[action] Felix to initiate discussions for weekly governance calls and finalize the proposed schedule. [assignee] Felix [status] todo
[action] Duke to possibly create an easy explainer video on the consent decision making process for budgets. [assignee] Duke [status] todo
[action] Felix and Vani will set up documents and budgets for governance workgroup tasks, particularly for archiving and onboarding. [assignee] Felix, CallyFromAuron [status] done
[action] Felix and Vani will refine the Town Hall presentation to ensure it aligns with budget and governance topics. [assignee] Felix, CallyFromAuron [status] todo
topics covered: Governance, WG Budget, Guild Leads, Town Hall Presentation.
emotions: Interesting, contributive, engaging
Type of meeting: Biweekly
Present: Tevo [facilitator], Effiom [documenter], Tevo, Gorga Siagian, malik, Effiom, Ayo, Photogee, Mikasa
Purpose: This Workgroup focuses on creating educational project-based learning material for Dework on the Andamio platform in collaboration with Gimbalabs and Governance Guild
Working Docs:
Looked at the list of values for Task labels on excel
How do we recognise participation vs contribution?
Categorised task labels associated with participation
Categorised task labels associated with contribution
Calculated the difference between AGIX and hours spent in respect to participation and contribution
Practicalised the reward sharing ratio among 3 WG members as an example
Task labels were sorted by either participation or contribution
[effect] affectsOnlyThisWorkgroup
[action] Continue figuring out the reward ratio for participation and contribution of WG members [status] todo
Creating our first task template
Creation of task using the template and addition of task tag
Ways to improve course content?
Changing task status and adding task points
Is approval triggered and required when subtask is changed to Done?
When you click SUBMIT WORK, then it asks for approval and moves task to done
Make each action statement a separate sentence and number them
[effect] mayAffectOtherPeople
Taking this lesson should be a requirement for every Treasury Guild member
[effect] mayAffectOtherPeople
[action] The template to be created in SLT 201:5 should be specified (i.e. task template) [assignee] Effiom [due] 26 June 2024 [status] done
[action] SLT 201:5 - Correct typo in step 4 (Example: Follwing, pastebale etc.) https://instance-dework-pbl.vercel.app/course/module/201/2015 [status] todo
[action] Itemise the action info for SLT 201:7 https://instance-dework-pbl.vercel.app/course/module/201/2017 [assignee] Effiom [due] 26 June 2024 [status] done
[action] SLT 201:7 - Update the wrong SubTask action info [assignee] Effiom [due] 26 June 2024 [status] done
[action] Itemise the action info for SLT 201:8 https://instance-dework-pbl.vercel.app/course/module/201/2018 [assignee] Effiom [due] 26 June 2024 [status] done
[action] Change SLT 201:9 action message [assignee] Effiom [due] 26 June 2024 [status] done
topics covered: Dework, Miro Board, Andamio, participation, contribution, participation vs contribution
emotions: Collaborative, repetitive
Type of meeting: Weekly
Present: Slate [facilitator], Slate [documenter], kateri, WaKa, GorgaSeagian, martinsoki, Photogee, WaKa, esewilliams, Clement Umoh, Kenichi, shuga, Peter
Purpose: - Budget Request Discussion - ACP blueprint walkthrough - Learn with AI
Working Docs:
Budget Request Discussion
ACP blueprint walkthrough
Learn with AI
Slate started the meeting welcoming everybody
Then we went over the education guild budget request with Slate explaining each module and how its going to be carried out in the next quarter
There was quite some interesting conversation on AI for beginner and its relation to Learn with Ai
osmium AI chatbot LLM and Waka's learn with AI to be included in the budget request
Then at the end Slate went through the education guild blueprint once again explaining all the points
Assign Osmium and Waka's project to budget request
[effect] affectsOnlyThisWorkgroup
[action] Added 2 new projects by osmium and waka [assignee] Slate [due] 20 June 2024 [status] done
topics covered: ACP, Blueprints , Budget
emotions: productive, Collaborative, Businesslike., speedy
Type of meeting: Weekly
Present: lord kizzy [facilitator], lord kizzy [documenter], WaKa, kateri, Vasu, martinsoki, Peter, Curtis, Kenichi, Ubiodee, CollyPride, Ubio, Oladepo Daniel, Rojo, Slate, Timmy, Samsung, Guillermo
Purpose: R&D Updates and Discussions
Working Docs:
Welcoming new Members and Introduction
Review of last meeting summary's Action Items
Updates status on Development to fill Repo
Reputation System using SoulBound Tokens
Q2 budget concerns and R&D Guild Q3 Updated Budget
Q3 Budget proposal discussions
New rules for proposal planning
Updates status on Development to fill Repo: Rojo gave updates on the development status on the Social Media Automation and Web Contributions Dashboard; he said: "For the Web3 dashboard and social media dashboard, we're almost done with the MVP. Obviously, you can see the code from the repos on our common GitHub. I think once the MVP is ready, we can open-source the code. We're going through some testings for the UI. We have very minimal backend functionalities for now, just because there wasn't enough time to have a lot of the functionalities that we predicted. But still, there is something to be tested and something to be improved. I expect it to be open source in the next week and a half, depending on how fast I will get well. But it should be done very soon. After that, we will be doing some testing with other workgroup members. And I guess the reporting on that would be part of Q3, not Q2. So Q2 was mainly about getting an MVP out." Ubio gave updates on his reasearch: "What we did was simply to convert responses we got from Q1 into Figma. In Q2, We converted the responses and the things we could derive from those response into a prototype design. so that's what we did for Q2. Q3 for us is about now taking that design back to the community to engage and see what comes out of that."
Presentation by Kenichi on a reputation system using SoulBound Tokens, here is the link to the document; https://docs.google.com/document/d/1l0A8BFSe_RDvqDLHyJaIa1A92ggXwBBNUG2RtM8BIgo/edit Rojo highlighted the similarities between this project and other web3 contributions projects and offered for a collaboration
There were discussions on R&D Guild Q2 Quarterly Report / R&D Guild Proposal & Q2 Community Concerns Response Document. there was an inclusion of more detailed deliverables
Discussion on Q3 Budget proposal, we had a brief Overview of the R&D Guild Budget for Q3
Discussions on New rules for PROPOSAL planning; There was a document highlighting the new rules for budget planning to prevent similar issues encounter in the previous Quarters (https://docs.google.com/document/d/1iaU5LI1KmKmcCbIa5yI1iRmDiqnkpzWNmnrgeRhvgeo/edit?usp=sharing)
We decided that if, by the closing date of Q2, the teams involved in the development proposal doesn't present progress in the assigned repositories and their respective reports with details of the progress and status, the resources assigned to said proposals will not be disbursed and will be reevaluated.
[rationale] This is to help build transparency between the Guild and the Community by providing deliverables
[effect] mayAffectOtherPeople
We decided to include Kenichi in the Guild Q3 Budget after we conducted a vote
[effect] affectsOnlyThisWorkgroup
We decided that all new proposals would go through community voting from Q3
[rationale] We want to encourage more initiatives from the community
[effect] mayAffectOtherPeople
[action] Guillermo to ideate to see how Vasu can collaborate with guild members on project [assignee] Guillermo [due] 26 June 2024 [status] in progress
[action] Colleen to draft out a proposal for her initiative on The Quest for AI Game Design [assignee] Colleen [due] 26 June 2024 [status] todo
[action] Ubio to add the link to the FIGMA to the GITHUB repo, and share a document highlighting the deliverables in screenshots [assignee] Ubiodee [due] 26 June 2024 [status] todo
topics covered: Guilds , Budget , Tool Development, Proposal, AI tooling, deliverables, Budget Request, Q2 budget, GitHub, loyalty system, Budget preparation, github board, contributors, Legacy project proposal
emotions: Collaborative, productive, Thoughtful, speedy, Welcoming, Friendly, straightforward, questioning
Type of meeting: Weekly
Present: LadyTempestt [facilitator], lord kizzy [documenter], duke peter, Ayo, Vanessa, SucrenSpice, Peter, Clement Umoh, kateri, daniel effiom, Onize, Gorga Siagian, Kenichi, martinsoki, Jenn, Guillermo, ToneTech, Slate, Guilermo
Purpose: Weekly meeting discussing how to onboard people to the Ambassador program
Working Docs:
There were suggestions to include
an overview onboarding survey analysis
share the Q2 Budget link
share the some insights on the Onboarders' plan for Q3
highlight that we have done skills analysis and we are currently planning on doing a peer education on core skills
Minutes from the last meeting and action items; we agreed to the minutes of last meeting.
Onboarding Journeys update: Onize said she hasn't had the time to edit the onboarding journey doc into a video script and she indicated that she would be done before the next meeting.
Getting Started channel
Onboarding session survey results
Skills Matrix document; Vani suggested that we could prioritise, 3 skills that lots of us want to learn, and that some of us could teach/share, and make further discussions once our budget gets approved. Love suggested that we should prioritize foundational skills like; Facilitations, Documentation & Community management.
Q2 Quarterly report & Q3 Budget Proposal Doc
Q2 Buddy System survey
Town Hall Updates: There were suggestions to include an overview onboarding survey analysis and also share the Q2 Budget link, there was also a suggestion to share the some insights on the Onboarder,s plan for Q3. There was also a suggestion to highlight that we have done skills analysis and we are currently planning on doing a peer education on core skills
We decided to stick with the laid out Criteria’s [which are: You have the Core contributor role/tag, You have been a member of this Workgroup for at least 3 months and you have the Onboarding WG member tag, You have at least 15 task points on Dework or you have done at least 4 approved and audited tasks in the workgroup ( meeting attendance excluded)] for the Onboarder’s team selection at least for this first time
[rationale] We want to make sure that those members who take up that role must have a vast experience of the ambassador program
[opposing] Ayo felt that eligible participants might be engulfed by Large ton of tasks and won't have the time
[effect] affectsOnlyThisWorkgroup
We agreed the Onboarders team will be decided by Sucre based on an application form (Here is the form: https://docs.google.com/forms/d/e/1FAIpQLSfOQr-BSMHjFjmSzia-t0AeHif_S4wmko2qzsxBLBp0_x1fHQ/viewform)
[effect] affectsOnlyThisWorkgroup
We decided that Duke is to Facilitate the next onboarding meeting if surce is unavailable to do that and Kateri is to document the next onboarding meeting
[rationale] Love was of the opinion that Sucre might not be interested in facilitating
[effect] affectsOnlyThisWorkgroup
We decide that Ayo is to train Kateri on Documentation
[rationale] This is Kateri first time documenting
[action] LadyTempestt to mentor Onize on giving the TownHall updates from the onboarding group for June [assignee] LadyTempestt [due] 27 June 2024 [status] in progress
[action] Onize to give Town Hall update for the WG on 25th June [assignee] Onize [due] 27 June 2024 [status] in progress
[action] Sucre to rewrite text in Getting Started to remove the Introductory Task, which has been discontinued [assignee] SucrenSpice [due] 27 June 2024 [status] in progress
[action] LadyTempestt to prepare a report for the Buddy system [assignee] LadyTempestt [due] 27 June 2024 [status] in progress
[action] Vani to prepare another page in the matrix doc where everyone could give their 3 picks of skills that are "foundational" for the WG [assignee] Vanessa [due] 27 June 2024 [status] todo
Onboarding Journeys
Skills Matrix report.
Onboarding Sessions Survey
Suggestions towards better Onboarding Processes document
Buddy System Report
topics covered: skills audit, Getting Started, mentorship, onboarding processes, buddy system, Q2 quarterly report, Quarterly Report, Video Script, Onboarder's form
emotions: interesting, funny , speedy , Friendly, Well-attended, Network Issues
Type of meeting: Weekly
Present: duke peter [facilitator], Ayo, Onize [documenter], esewilliams, Kenichi, Clement Umoh, Onize, kateri, Cjfrankie, SucrenSpice, PeterE, Ayo, LadyTempestt, hogantuso, guillermolucero, lord kizzy
Purpose: Getting more African countries into the Program and Guild
Working Docs:
Introduction: Statutory greeting calls in the multiple languages spoken across Africa by Ese Williams. Follow-up on previous Action Items Work ongoing on the Onboarding process structure document; Sucre, Love. Skills Database: Several people yet to fill in the skill database sNET African Guild Research on expansion and penetration strategies into other African Countries under way; critical success expected before next meeting: Clement. Initiative and Contribution Framework Document suggested to be opened to the guild or at least to a team of contributors because of necessary scope.
Getting more African countries into the Program and Guild: Suggestion towards strategy as a project by a select team to get more African countries onboard; feels like Nigeria is already at capacity in the Guild: Duke. Onyeka suggests a cross-country community approach while being mindful of the program’s budget.
Creative quarterly bounties: To be discussed further for ideation in the next meeting. Cross collaboration with AI Ethics WG: A SNET African Guild AI Ethics Expo, a collaborative event effort being accomplished alongside the AI Ethics workgroup. Town Hall Updates: Takers asked for who will do the townhall updates Onboarding Structure Update: Sucre urged people to make further contributions to the onboarding structure document. AMA Session Update: Ese reports that the AMA preparations are in the marketing phase and everything on queue. Q2 Report and Q3 Budget: Link shared so everyone can see, read and drop comments where they deem necessary. Duke sheds light on the circumstances of the report completion. Also budget approval is not automatic. All fingers advised to be crossed. AOB: Sucre wanted to understand why the Telegram group isn’t as active as before. Duke responded that it is difficult to discuss operational subjects on Telegram as there are people in the Telegram group who have yet to onboard to the Ambassador Program itself, which is a prerequisite to being a member. A concern was raised about why we are still using Google Meet and not Zoom. Resolved with an action item. Closing: All hands to be on deck for the furtherance of the objectives of the guild. Appreciation to everyone about how the AG call was free from tension that could have come from the Governance call.
We agreed the next meeting should happen on Zoom.
[effect] affectsOnlyThisWorkgroup
[action] Ayo to reach out to Peter to make sure our meetings are on the Zoom Calendar on Discord. [assignee] Ayodele [due] 18 July 2024 [status] in progress
[action] Clement to onboard volunteers on his action item for African countries penetration strategies. [assignee] All Members [due] 18 July 2024 [status] in progress
[action] Identify and touch base virtually with other AI/Web3 communities across Africa [assignee] All Members [due] 18 July 2024 [status] in progress
topics covered: African, African guild, Marketing initiative, Collaboration, expansion, meeting venue, Q3 budget, GEI, Global AI Ethics Initiative
emotions: Collaborative, contributive, calm, chatty
Type of meeting: Weekly
Present: Zalfred [facilitator], killy [documenter], lord kizzy, hogantuso, AndrewBen, Slate, kateri, osmium, oep, malik, devon, Photogee, Gavriel
Purpose: weekly updates /task assignment
More Updates on the zealy platform. We discussed on how the zealy task claim will be allocated and how the claim will be shared between the writers and video workgroup
slate,as our social media manager gave weekly updates on our social. He uploaded 2 long videos and 3 short videos and we have good engagement
we discussed on proposing 2000 points for the zealy platform
mallik as the task manager gave updates from last week and this week
we discussed on how frequent should our videos be uploaded
We decided to reach out to rojo head of video work group due to an unresolved conclusion about two roles taking by the same person [liaison and social media manager ]
[rationale] leaving the two roles to one person will be too much work load
[action] creation of our Q2 Budget proposal report [assignee] hogantuso, lordkizzy [status] done
[action] Task management [assignee] Slate [status] todo
[action] social media manager [status] todo
[action] Townhall summary [assignee] AndrewBen [status] todo
[action] Townhall editor [assignee] killy [status] todo
[action] facilitator [assignee] Zalfred [status] todo
[action] meeting summary [assignee] lord kizzy [status] todo
topics covered: social media management, Task Assignment, Budget
emotions: Casual
Type of meeting: Weekly
Present: Kenichi [facilitator], cjfrankie [documenter], Kenichi, Mikasa, cjfrankie, LadyTempestt, devon, Slate, Gorga Siagian, kateri, Nengi, Ayo
Purpose: Overview of the new Scribbler onboarding form, implementing a new mechanism to track meeting attendance and time, addressing issues hovering around the WWG editing framework, and implementation of a point delegation system.
Working Docs:
The meeting started with Kenichi welcoming everyone to the meeting, and then he highlighted the agenda items.
The meeting kicked off as Kenichi surfed dework to check assigned tasks and tasks in progress, and then he asked the scribblers to share an update regarding their tasks - Devon, Mikasa, and Cjfrankie updated us with their respective tasks.
In the meeting, we reviewed the “new Scribbler onboarding form.” Kenichi highlighted the importance of the form. He also stated that the form will help track new people coming to the WG and if they decide to become scribblers in the future.
Kenichi proposed the idea of tracking meeting matrices since read.ai doesn't track data such as attendance or the time people joined a meeting. Then he also emphasized the importance of these data and how they will help in the WG in the future.
Following that, he also proposed the idea of points delegations, where the scribblers and the scribes will be awarded an extra 10 points from the points system. These points can be delegated to other members of the workgroup to show love and support for their contributions towards your task(s), or whatever the case might be!
We also addressed and answered questions regarding the aspirants who took the WG test.
Lady Tempestt proposed the idea of implementing a rotational meeting facilitation system in the WWG, and then Kenichi cleared the air by saying that the scribes could facilitate meetings in his absence.
Discussion on dropping off inactive members with the scribbler tag; this discussion set the Thames on fire. As we fleshed out the tests of the aspiring writers, we desire to give room for new scribblers to join us, explore the world of AI, and also tell captivating stories through writing.
We decided to move the point delegation mechanism to the next quarter.
[rationale] Because Q3 is almost over!
[effect] affectsOnlyThisWorkgroup
We decided that inactive members with the scribbler tag would be dropped off, and then they would be given the pupil tag; the scribbler tag can be reinstated until they reach the scribbler threshold again.
[rationale] We want to create a opportunity window for aspirants to tell thir story through writing.
[effect] affectsOnlyThisWorkgroup
[action] The scribes to chase aspirants who took the WWG test and give them an update on their performance and possible ways to improve in their next try. [assignee] Cjfrankie , Mikasa [status] todo
topics covered: Editing Framework, Scribes , Scribblers, Points system, community page, Role document , read.ai, Zealy, pupil tag, Feedback Form, Points delegation , Governance, Notion
emotions: interesting, funny , interactive, speedy
Miro board:
Meeting video:
Miro board:
Other media: