Week 3
Mon 13th Jan - Sun 19th Jan 2025
Last updated
Mon 13th Jan - Sun 19th Jan 2025
Last updated
Type of meeting: Biweekly
Present: Tevo [facilitator], Effiom, Tevo [documenter], advanceameyaw, effiom, tevo
Purpose: Aggregating Ambassador Program assets and relevant information under GitBook
Meeting video:
Miro board:
Other media:
Working Docs:
Selection of a meeting summariser and a reviewer for 13.01.2025
New Meeting Summary template doc - https://docs.google.com/document/d/1v4zoPFp25Wx2M28JY5XiXFgBCV454iq_9fKF9sykNxU
Using Managing Meeting Summaries guide https://docs.google.com/document/d/1nT2f4Mo5ySK26W6r2zNLMY-uDKiRNdNRXLzykONUIR4 as Core Tasks guidelines
We are adopting a new meeting summary template using Google Docs
[rationale] Google docs is more user friendly compared to Miro, plus the final destination of meeting notes is the GitBook after it's been added to the summary tool and archived.
[opposing] None
[effect] affectsOnlyThisWorkgroup
[action] Effiom will draft the meeting summary and upload it to the summary tool. [assignee] Effiom [due] 27 January 2025 [status] in progress
[action] Tevo to review meeting summary and publish in Discord [assignee] Tevo [due] 27 January 2025 [status] in progress
[action] Tevo continues preparing the tool to generate Markdown files for the Knowledge Base GitBook [assignee] Tevo [due] 27 January 2025 [status] in progress
Quarter 1 2025 Report - https://docs.google.com/document/d/1I1KAFNsyQTtnXduB-q34MXsR63q-3g5eIbZh4AKdb-8/
Adoption of the fixed hourly AGIX rate for tasks and fixed AGIX amount
Some fixed hourly rate tasks are meeting summary and review, preparation of meetings, and review of tasks
Should we assign the report update to someone at the next meeting?
We will use the Exchange Rate (0.55) in Quarter 1. Hence, Hourly rate = Exchange Rate / 20 = 36 AGIX
[rationale] This was the advised rate used when budgeting for Q1 2025
[opposing] None
[effect] affectsOnlyThisWorkgroup
We decided to keep most of the tasks as fixed AGIX amount
[rationale] As the amount allocated is in AGIX
[opposing] None
[effect] affectsOnlyThisWorkgroup
We will reward 10 AGIX to those who add community engagement, but won’t reward if added through meeting summary
[opposing] None
[effect] affectsOnlyThisWorkgroup
[action] Include this agenda item in the next Meeting Agenda and assign it to someone [assignee] Tevo [due] 27 January 2025 [status] todo
[action] Everyone who has participated in any of the Knowledge Base calls can include engagement [assignee] Tevo [due] 27 January 2025 [status] in progress
What helps to draft the Q2 proposal?
Knowledge Base WG Q1 2025 Report- https://docs.google.com/document/d/1I1KAFNsyQTtnXduB-q34MXsR63q-3g5eIbZh4AKdb-8
Knowledge Base WG Q4 Report - https://docs.google.com/document/d/1o7oWhDiI4TScTqgWpORIO4_SMi-HMNw91LdOq9i4Fzo
Knowledge Base WG Proposal Q1 2025 - https://docs.google.com/document/d/1lV5E52tbfTb6tSjkqZVwtp9su92AwvqQopCCce-8pIY
What should we focus on in Q2?
User feedback, and uploading assets to Knowledge Base WG
Moving back to the basic process of what the group was initially intended for
Making all the relevant content created by the Ambassador Program easily accessible in an organized way
We will do a final collective review of the proposal at the February meeting
[opposing] None
[effect] affectsOnlyThisWorkgroup
[action] We will continue to check on the Q2 proposal topic again at the next meeting [assignee] all [due] 27 January 2025 [status] todo
No new updates have been made to Category Descriptions - https://docs.google.com/document/d/1NzpysgIDsZFigFJz4Tiik3h2l0X4FJTJC4xEbGiwsUw
First priority is creating descriptions
[effect] affectsOnlyThisWorkgroup
Second priority is to organise selected demo items on GitBook
[effect] affectsOnlyThisWorkgroup
[action] Effiom and AdvanceAmeyaw continue to show interest in providing descriptions [assignee] Effiom, advanceameyaw [due] 27 January 2025 [status] todo
topics covered: Workgroup management, Category Descriptions, Async work, Meeting attendance, Q2 2025 budget, Q2 2025 proposal, Q1 2025 report, task prioritising, meeting summary template, Meeting Summaries, community engagement, user feedback, Async, GitBook, Miro to GitBook, script
emotions: low attendance, Organised, simple
Type of meeting: Weekly
Present: PeterE [facilitator], CallyFromAuron [documenter], PeterE, CallyFromAuron, Sucre n Spice, LadyTempestt, guillermolucero, osmium, Duke, hogantuso, AshleyDawn, Effiom
Purpose: Weekly Governance WG meeting
Working Docs:
This session was a retrospective of the consent process for Q1 2025 workgroup budgets.
See the Miro board here https://miro.com/app/board/uXjVLtid06I=/
Everyone present agreed that the implementation of budget caps has been broadly a success, especially in that it saved time and made the process less onerous; and most said that caps should be used again for Q2. However, several people noted that some of the higher-budget workgroups were not entirely happy at the enforced lowering of their budgets; and that we still need to discuss and refine the process of setting caps and e.g deciding how a WG's cap can be changed.
We noted that this last topic is on the rolling Governance WG agenda for our next meeting on Thurs 16th Jan.
Retrospective on the consent process for Q1 budgets
topics covered: core contributors, participation, consent decision making, consent process, budget caps
emotions: Thoughtful , focused, participatory