Week 16
Mon 14th Apr - Sun 20th Apr 2025
Last updated
Mon 14th Apr - Sun 20th Apr 2025
Last updated
Type of meeting: Monthly
Present: Tevo [facilitator], Évéline Trinité [documenter], Tevo, Gorga Siagian, Évéline Trinité, advanceameyaw, Jeffrey Ndarake, Effiom
Purpose: AGGREGATING AMBASSADOR PROGRAM ASSETS AND RELEVANT INFORMATION UNDER GITBOOK
Miro board:
Working Docs:
Dework Task Management
Who will collect assets?
Recognise Knowledge Base WG contributions using Github
[effect] affectsOnlyThisWorkgroup
[action] Daniel Effiom to draft Q2 progress report. [assignee] Effiom [status] todo
[action] Gorga to review Q2 Progress report. [assignee] Gorga Siagian [status] todo
[action] Eveline to draft Meeting summary [assignee] Évéline Trinité [status] todo
[action] Gorga to review meeting summary [assignee] Gorga Siagian [status] todo
[action] Daniel Effiom and Tevo lead to collect the assets [assignee] Tevo [status] todo
What is the Knowledge Base GitBook useful for?
The Knowledge Base GitBook serves as a structured repository for storing key assets and information, enabling better coordination in a decentralized environment. It helps establish a commonly understood source of truth, ensuring alignment and accessibility across contributors.
The Knowledge Base GitBook is for searching general information about the Ambassador Program and understanding how contributors are engaging with current projects.
While the initial Miro Board layout helped visualise content types and identify gaps, the transition to GitBook has made it difficult to compare the coverage of questions.
Is there something that should be there that isn't there?
Is there a link that should be removed?
Is anything unclear or confusing?
Can you think of “why” or “how” questions that you would like to know about the Ambassador Program in the KB structure?
Do you use "Knowledge Bases" often?
Decentralised organisations seem to use Knowledge Bases more often
Focus on improving the guiding Knowledge Base users
[effect] mayAffectOtherPeople
[action] Create a short (2min) video Tutorial on how to use Gitbook. [status] todo
[action] Create a short summary about the Knowledge Base approach for organising GitBook. [status] todo
[action] Tevo to update Miro Board Colours to match with the new asset visibility status on GitBook [assignee] Tevo [status] todo
Reviewed Knowledge Organising Process
Should we create templates and publicity material?
This quarter, we will collect material without templates and publicity, but collect information that the selected leads choose to add to GitBook
[effect] mayAffectOtherPeople
[action] Create a video showing and explaining the steps in the Organising Process [status] todo
[action] Check back on the last meeting before Q3 submission if we benefit from having built in onboarding features used by our Organising GPT to help contribute to workgroup [status] todo
topics covered: Gitbook, Miro Board, Dework, Q2 Progress report, Video Tutorial, Summary, Github, knowledge base
emotions: Collaborative, Businesslike.
Type of meeting: Weekly
Present: Slate [facilitator], Slate [documenter], kenichi, osmium, esewilliams, Zalfred, hogantuso, eve, AshleyDawn, Malik, Gorga Siagian
Purpose: CCCP Discussion - Presentation Series Discussion - Malik Presentation From Gamers Guild
Meeting started off with the discussion on the last week topic of Certification Program, and its process document .
Two platforms are being discovered: Canvas LMS and Moodle, which are being done by zalfred and tuso respectively.
Slate outlined the process of getting information regarding the portfolio's and other materials for the selection of creators.
Then the discussion on Presentation Series project started, with the discussion on module 2 and 3 which are being worked by zalfred and gorga , still some modifications required in both
Ese had some question for kenichi in regards to the presentation series : "So this would be updated overtime? Cos we have knowledge bank of SingularityNet everywhere. So why should we use the presentation for every event knowing fully well every event have their theme, focus, and even pattern. How then would we be able to use it"
These questions were answered by Kenichi
Then Malik presented the Gamers Guild presentation of Education Guild which was liked and approved, with a little modification/ addition of certified tag on the NFT section
[action] Work upon Portfolio Forms [assignee] Slate [due] 23 April 2025 [status] in progress
[action] Work upon Modules [assignee] Gorga Siagian, Zalfred [due] 23 April 2025 [status] in progress
topics covered: ACP, Google Classroom, proceses, Budget Allocation
Type of meeting: Weekly
Present: Ayo [facilitator], martinsoki [documenter], kareem, kenichi, Eric Davies, Kateri, UknowZork, SubZero, photogee, esewilliams, LordKizzy, AJ, Évéline Trinité
Purpose: Marketing Guild weekly meeting
Working Docs:
Ayo kicked off the Marketing Guild call, welcoming attendees. Noticing the low turnout, he considered holding off a bit to see if more members would join.
Quorum Discussion and Updates: The discussion centered on the importance of establishing a quorum for future meetings, noting that sessions with low attendance risk being unproductive. Martinsoki suggested setting a minimum attendance threshold to determine whether meetings should proceed—a proposal that was well-received by others. Acknowledging that they currently lacked quorum, the group debated whether to continue or postpone the meeting. Members were encouraged to share updates that didn’t require consensus, underscoring the need for clearer attendance and decision-making protocols going forward.
Updates on Proposals and Budget Discussion: Lordkizzy shared updates from his conversations with Kenichi regarding the Zealy project, with EricDavies noting the lack of feedback on the proposal. He emphasized the importance of clearly defining the graphics team's responsibilities, with some input from CJFrankie expected next week. Lordkizzy also stressed the need to adjust Q2 rewards in light of the current token price.
Updates on Twitter Spaces Document: Kenichi discussed a document he is developing to support the creation of Twitter databases, which he believes will aid growth efforts, despite facing technical difficulties. He proposed leveraging Twitter spaces to enhance the visibility of the Singularity Ambassador program and engage a wider audience.
Updates on Governance document: Ese Williams raised concerns about unpaid payments for Eric Davies and Photogee, suggesting a separate call to address the issue. Ayo noted the difficulty of making decisions without a quorum, emphasizing the need to adopt formal governance documents. The discussion also highlighted the importance of improving communication and collaboration within the Marketing Guild. Discussion on Core Member Rewards and Deliverables: Ayo emphasized the need to define core member value before addressing reward adjustments. Kareem noted that reduced funding for the graphics team would require scaled-back deliverables across all teams. Discussion on Attendance, Rewards, and Quorum: The discussion focused on the importance of establishing a quorum for meetings, especially as attendance has declined due to reduced rewards. Concerns were raised about how the current token price limits fair reward distribution. Suggestions included adjusting the number of members and how rewards are allocated to address past complaints.
[action] Ese Williams to schedule a follow-up call to discuss payment for Eric Davies and Photogee. [assignee] esewilliams [due] 25 April 2025 [status] todo
[action] Lordkizzy to present the graphics team's new structure and KPIs in the next meeting. [assignee] LordKizzy [due] 25 April 2025 [status] todo
topics covered: Governance document, Budget Proposals
emotions: insightful, Collaborative, Satisfaction
(New )
We agreed that short tutorial videos will be created by members of the Knowledge Base Workgroup who are both willing and familiar with the content. If additional support is needed, we’ll follow the to request assistance.
[action] Check back on the last meeting before Q3 submission if we benefit from updating the Miro Board Organising Resources View (as now its directly done in Google Sheet using ) [status] todo