Week 8
Mon 17th Feb - Sun 23rd Feb 2025
Monday 17th February 2025
Knowledge Base Workgroup
Type of meeting: Biweekly
Present: Tevo, Effiom [facilitator], Tevo, Effiom [documenter], effiom, tevo
Purpose: Aggregating Ambassador Program assets and relevant information under GitBook
Miro board: Link
Other media: Link
Agenda item 1 - Workgroup Management - [resolved]
Discussion Points:
Going over old and new action items
Assigning meeting summarizer and reviewer for 17.02.2025
How we manage Meeting Summaries - https://docs.google.com/document/d/1nT2f4Mo5ySK26W6r2zNLMY-uDKiRNdNRXLzykONUIR4
Meeting Summary Template - https://docs.google.com/document/d/1VU_VG8z7wnROx0DKsHsXOYshaJAoeZQ8dYZlRWYMSzE/
Action Items:
[action] Effiom will draft the meeting summary and upload it to the summary tool [assignee] Effiom [due] 24 February 2025 [status] done
[action] Tevo will review and publish the Meeting Summary on Discord [assignee] Tevo [due] 24 February 2025 [status] done
Agenda item 2 - Finalise Quarterly Report and Proposal - [resolved]
Discussion Points:
Are there any pending async tasks before we submit the report and proposal?
Knowledge Base WG Q1 2025 Report - https://docs.google.com/document/d/1I1KAFNsyQTtnXduB-q34MXsR63q-3g5eIbZh4AKdb-8/
Does the Q2 proposal fit within the WG's budget cap?
Knowledge Base WG Proposal Q2 2025 https://docs.google.com/document/d/10TjExpU7uScZ0k9FtJLLLOhXZk_El0enKVC9RSYj_Wo/
Updating the Community Engagement section in the report
Decision Items:
Continue with monthly Knowledge Base sessions, and continue updating Knowledge Base GitBook
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] Report and Proposal to be submitted once the deadline has been fixed, as we are done [assignee] Effiom, Tevo [due] 3 March 2025 [status] todo
Agenda item 3 - Review Category Descriptions - [carry over]
Discussion Points:
Category Descriptions https://docs.google.com/document/d/1NzpysgIDsZFigFJz4Tiik3h2l0X4FJTJC4xEbGiwsUw/
We reviewed 5 sub-sections of the categories
Action Items:
[action] We will continue the category descriptions while script development is ongoing [assignee] all [due] 3 March 2025 [status] in progress
Agenda item 4 - GitBook, GitHub, and Markdown Automation - [carry over]
Discussion Points:
Updates on GitBook and GitHub
Updates on the current markdown automation progress
Knowledge Base structure is visible now on GitBook
Keywords/tags:
topics covered: Miro Board, Workgroup Management, GitBook, GitHub, Budget, Category Descriptions, Q2 2025 proposal, Q2 2025 budget, Budget caps, Q1 2025 quarterly report, Miro to GitBook, Markdown, community engagement
Treasury Automation WG
Type of meeting: Monthly
Present: Tevo [facilitator], Effiom, Tevo [documenter], Effiom, Tevo, Kateri, PeterE
Purpose: We develop the Treasury System
Meeting video: Link
Miro board: Link
Other media: Link
Agenda item 1 - Development progress since last Meeting - [carry over]
Discussion Points:
Tevo has mainly worked on updating Treasury Operations User Experience and fixing related issues we run into when using the Treasury Manager Excel for the past 2 quarters. The focus has recently shifted towards new features.
Previous Core Contribution calculations have been operational 1-2 hour activities that don’t produce structured assets. Which makes it less transparent.
Presented Core Contributor Sheet on Treasury Manager which will be used for Core Contributor calculations. Described difference between Task Types Described based on what task types are selected
How could we improve calculating Core Contributors?
Decision Items:
Once Core Contributors are done, the next focus is to integrate GitHub into the Treasury Manager
[effect] mayAffectOtherPeople
If task Manager wants to recognise contributions without financial rewards that have no relations a different task that has the rewards then they can use Task Label Tag "contribution" to indicate that these contributions should be calculated towards Core Contributions
[effect] mayAffectOtherPeople
Action Items:
[action] Tevo to double check if Effiom has received missing rewards from the contributions that did not have rewards on the Core Contributor dashboard [assignee] Tevo [status] todo
Agenda item 2 - Update Proposal for Quarter 2 and Report For Quarter 1 - [carry over]
Discussion Points:
Reviewed and Updated Quarter 2 Proposal
Reviewed and Updated Quarter 1 Quarterly Report
Decision Items:
Use the Quarter 2 budget to top up the development costs that were not yet started
[effect] affectsOnlyThisWorkgroup
If we don’t create new features for Quarter 2, we increase the Technical Dept Support funds. This allows us to build a reserve to be more agile towards small updates
[effect] affectsOnlyThisWorkgroup
We move to 2 meetings per quarter and increase the meeting time from 90 to 120 min
We reduced the preparation time for meetings down to 2 hours from 4 hours. Without new development plans, it takes less time to prepare meetings and we have now gotten also used to the new operational cycle, which doesn't require changing often
Action Items:
[action] Finalise Quarterly Report after async review of Quarter 2 proposal [assignee] Tevo [status] todo
[action] Quarter 2 Budget items need an async review on which items we carry over from Q1 and whether we have the capacity to add something new [assignee] Tevo [status] todo
[action] After reviewing budget items, update the Proposal with new deliverables or changes. [status] todo
Keywords/tags:
topics covered: Miro Board, Proposal, Reports, Quarter, Treasury System, Budget, Development, Update
Treasury Guild
Type of meeting: Biweekly
Present: Tevo [facilitator], Effiom, Tevo [documenter], PeterE, AshleyDawn, Effiom, Tevo
Purpose: Structuring Ambassador rules around payments, tasks and anything related to financial activities
Miro board: Link
Other media: Link
Agenda item 1 - Guild Management - Distribute Action Items - [resolved]
Discussion Points:
Assigning meeting summarizer and reviewer for 17.02.2025
How we manage Meeting Summaries - (https://docs.google.com/document/d/1nT2f4Mo5ySK26W6r2zNLMY-uDKiRNdNRXLzykONUIR4)
Meeting Summary Template - (https://docs.google.com/document/d/1v4zoPFp25Wx2M28JY5XiXFgBCV454iq_9fKF9sykNxU)
Action Items:
[action] Effiom will draft the meeting summary and upload it to the summary tool [assignee] Effiom [due] 24 February 2025 [status] done
[action] Tevo will review and publish the Meeting Summary on Discord [assignee] Tevo [due] 24 February 2025 [status] done
Agenda item 2 - Policy Management - Review New Policies - [carry over]
Discussion Points:
Review New Policies and Next Steps
Are there new Policy submissions?
Treasury Policy Submission Form Responses - (https://docs.google.com/spreadsheets/d/1-tAwCD3vrXNSbUdQApljTVMfFGVDJo6PBdM39CO73Uk)
Agenda item 3 - Ratification of policies and Next Steps - [carry over]
Discussion Points:
What are the next Steps for Ratified Policies?
Treasury Policy Processes - (https://docs.google.com/document/d/1g-INSEasp4TsEWgGQSoTIxe-KLX79tXqzF3rhWbSI3M)
GitBook Update? Where and What we would say?
We had 0 comments on ratified policy that gained 11 yes votes again 0 objections
Decision Items:
Every time a policy decision is being made or decided, we link it to GitBook
[effect] mayAffectOtherPeople
Action Items:
[action] Add a new section to Process (in policy doc) based on the way we decide to solve the implementation [status] todo
[action] Anyone to Create an Announcement and ping all @Core Contributors about ratified policies (include the link to GitBook) [status] todo
[action] Anyone to Update policy process Doc to remind using the announcement template. We use Template created in meeting for announcing policies - Do Reformat for discord use [status] todo
[action] Tevo to add a policy page to Ambassador Gitbook, add a summary of how policies are handled, and share the policy process and policy sheet [assignee] Tevo [status] todo
Agenda item 4 - Finalise Quarterly Report and Proposal - [resolved]
Discussion Points:
Should we call Quarterly reports, Progress Reports?
Treasury Guild Proposal Q2 2025 - (https://docs.google.com/document/d/1huN1mzMD1n42UHPTZ7HiBNuDAbhy8rlCJGGKIk5jykc)
Treasury Guild Q1 Report 2025 - (https://docs.google.com/document/d/1AND0meYR-owrW1yiURmB_DyAKhD15iRMh7JGx-Dl9Qs)
We updated Community Engagement section
Are there any sync tasks before we submit the report?
Does the Q2 proposal fit within caps?
Could we include Documentation and development time in Q2 to automate participation recording documentation or should it go to Automation WG? or Process Guild?
Decision Items:
There is enough scale and interest to keep using the Participation Recognition service. We should focus on improving the way we report the outcomes and automate rewarding the import, auditing, and operations. In theory this would reduce the weekly average of 30mins operations down to 10mins
[effect] mayAffectOtherPeople
Action Items:
[action] Tevo to Update Quarterly Report with the new policy name if its submitted next week [assignee] Tevo [due] 7 March 2025 [status] todo
Agenda item 5 - INF Tokens - [resolved]
Discussion Points:
Do we want to leverage Influence Tokens?
Decision Items:
We continue collecting Influence Tokens as paper trail and not yet create transactions
[effect] mayAffectOtherPeople
Agenda item 6 - Open Topics - [resolved]
Discussion Points:
How do we address Token Price drops?
Guidance on how to budget and avoid price changes and its impact
Keywords/tags:
topics covered: Miro Board, Guild Management, Ratification, Q2 Proposal, Q1 Report, Treasury system, Operations, Budget, INF Tokens
Tuesday 18th February 2025
Governance Workgroup
Type of meeting: Weekly
Present: PeterE [facilitator], CallyFromAuron [documenter], PeterE, CallyFromAuron, AshleyDawn, guillermolucero, CollyPride, Sucre n Spice, Évéline Trinité, maxmilez, Valola
Purpose: Weekly Governance WG meeting
Working Docs:
Narrative:
We signed off Guillermo's infographics for the Q2 decision, and discussed how best to share them and what relevant links should be posted with them.
We agreed on an exchange rate of $0.30 for Q2 2025 budgets
We provisionally agreed the Q2 2025 budget for GovWG, pending any rethinks before the submission date of 10th March. We looked at the WG task sheet, and what surplus we have; and we discussed briefly whether we can still afford to continue with backlog documentation, or whether we should simply record "No summary given" for uncompleted summaries - to be discussed
We discussed whether and how to implement the ideas around WG minimum budgets suggested in the “Budget caps for Q2” discussion doc https://docs.google.com/document/d/1kVd_4Ih-lSdMoIcmVeOS3_H3aqOdnMmMG6o1WqGTx1w/edit?usp=sharing. We decided yes, we should discuss how different WGs might approach decising on their operational minimum and what would be included in it, and that the next WG sync call would be a good place to start; so we added it to the WG Sync Call rolling agenda.
Discussion Points:
Agreeing publicity and infographics for the Q2 budget process
Agreeing exchange rate for Q2 budgets
Agreeing draft GovWG budget for Q2 2025
Minimum WG budgets
Decision Items:
We signed off Guillermo's infographics for the Q2 2025 budget process, pending a couple of small changes (e.g. adding the agreed exchange rate)
[effect] mayAffectOtherPeople
We agreed that Peter and Vani will both post the infographics; and that when the timeline and/or the "Take part in governance" infographics are posted, the post will include a link to the list of Core Contributors, and the context-setting doc for Core Contributors; and the "Submit your WG budgets" will be posted together with links to the Budget Planner, the Budget Caps spreadsheet, and the context-stetting doc for WGs
[rationale] to ensure that people can easily find the info they need
[effect] mayAffectOtherPeople
We agreed the exchange rate for Q2 budgets will be $0.30
[rationale] because the rate in recent days has been under $0.35 and falling; and because, for WG budget management, it would be preferable to set it too low than too high
[opposing] $0.35 was also suggested, but the majority preferred $0.30
[effect] mayAffectOtherPeople
We provisionally agreed the draft Q2 budget for Gov WG, including taking c. $800 from reserves to cover elements that we cannot otherwise afford. Changes can still be made up until the submission date of 10th March.
[rationale] Token price being low, we will need to take from reserves in order to be able to do any additional sessions (e.g. a retrospective, as we always do) and to cover content creation such as infographics. We might not spend all of what we plan to take from our reserves.
[opposing] Some concerns were raised about the fact that doing this could mean we go in to Q3 2025 with no WG reserves
[effect] affectsOnlyThisWorkgroup
We agreed that the idea of WG minimum budgets should be discussed in the next WG sync call; covering how different WGs approach deciding on their operational minimum budgets, and what would be included in a minimum for different WGs. We added this to the WG Sync Call rolling agenda.
[effect] mayAffectOtherPeople
Action Items:
[action] Vani and Peter to share Guillermo's infographics regularly over the next few weeks, together with links to relevant docs [assignee] CallyFromAuron, PeterE [due] 10 March 2025 [status] todo
Keywords/tags:
topics covered: Q2 2025 budget, WG reserves, Reserves, WG Sync calls, Core Contributors , publicity, Infographics, consent process, minimum budgets
emotions: gloomy, decisive, Organised
GitHub PBL WG
Type of meeting: Monthly
Present: Tevo [facilitator], Tevo, Sebastian Pabon [documenter], Tevo, Effiom, Sebastian Pabon, AshleyDawn, LadyTempestt, maxmilez, salometee
Purpose: We are creating a PBL course on Andamio about GitHub features and use cases to manage
Miro board: Link
Agenda item 1 - Workgroup management - [carry over]
Discussion Points:
Reviewed and updated the Quarter 1 Report
Decision Items:
Created Q2 budget sheet and allocated 500 USD in AGIX for potential additional support funds
[effect] affectsOnlyThisWorkgroup
We use color-coded reporting on the Report, so next time we do a progress report, we will have a comparable snapshot
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] Tevo to create a meeting summary. [due] 11 February 2025 [status] done
[action] Sebastian will review the meeting summary. [due] 11 February 2025 [status] done
[action] Submit Report and Budget for Q2 budget planning [due] 11 February 2025 [status] todo
Agenda item 2 - Finalise and Upload Lessons to Andamio - [carry over]
Discussion Points:
We reviewed Module 104 - Reward Management
There were comments about WG difficulties in doing the work required in creating, editing and revising lessons and course content in general, related to the time that content creators can dedicate asynchronously to delegated tasks. During meetings the group is doing a better job than asynchronously, but unfortunately, it takes more time overall for everyone.
Decision Items:
We updated links and some wording, but no major changes to lessons, if feedback forms provide no suggestions, Module 104 is completed.
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] Love Tempestt, Gorga, Onize, Sucren to update their Andamio Lesson based on existing feedback. More information in GitHub Lessons Thread in Discord GitHub PBL WG Channel [assignee] LadyTempestt [due] 11 February 2025 [status] in progress
[action] In the next session, we start to review GitHub Project Board features and configurations in module 202 [assignee] LadyTempestt, Tevo [due] 11 February 2025 [status] in progress
Agenda item 3 - What issues did we run into as Andamio Course Creators? - [carry over]
Discussion Points:
Is there capacity for the Andamio team to build a Quiz-creating feature for course creators that is part of an assignment or has its own page. SingularityNET is able to support an average 2000$ in AGIX per quarter.
Action Items:
[action] Personal Assignment Notes no longer seem to be working as before. How do we change the Status of the assignment? Find out how assignments work now. [status] todo
[action] The navigation overlay buttons go behind the commenting panel in each lesson [status] todo
[action] Sebastian looks into the Andamio team to find out if it’s feasible to build quiz creating feature by end of Q2 and what would be the cost of such a feature. [status] todo
Keywords/tags:
topics covered: Proposal, Reports, Quarter, Dework, Andamio, Course, PBL, Course structure, Statuses
Wednesday 19th February 2025
Education Workgroup
Type of meeting: Weekly
Present: Slate [facilitator], Slate [documenter], AndrewBen, AshleyDawn, esewilliams, eve, frosh, Gorga Siagian, Kateri, kenichi, LordKizzy, Malik, Mikasa, osmium, SubZero, UknowZork, Slate, maxmilez, Alfred Itodele
Purpose: Project Updates-Presentation Series Budget Allocation-Agix Price Discussion
Working Docs:
Discussion Points:
Meeting started off with the updates from Ai for Beginners which was presented by Ese
Ese notified that there is one SEO still missing. The Franklyn video has been updated which were having link issues which is also fixed now
Then the presentation of the Presentation Series project started by Kenichi in which budget allocation for the modules were showed.
Ese notified that her and clement were working on the Webinar series , on which Slate notified that we would have to consider the AGIX price before executing the projects at initial stages
Then there was a shift of discussion on the AGIX price in which different opinions were shared that
allocate agix not dollars
reduce the rate till the price goes up and pay the rest later
Reduce the amount of projects
More detailed discussion on agix price with the current project allocation to be showcased in next meeting by Slate
Action Items:
[action] Slate to present the budget allocation on different projects by next meeting and deducing possible routes for allocation [assignee] Slate [due] 26 February 2025 [status] in progress
Keywords/tags:
topics covered: Budget Allocation, ACP, Google Classroom, Experimentation, Q2 2025 budget, Budget caps, Governance Workshop Presentation Series
emotions: Collaborative
LatAm Guild
Type of meeting: Weekly
Present: guillermolucero [facilitator], SergioBenaR [documenter], guillermolucero, andrea reyes, SergioBenaR
Purpose: Activities and events for LatAm_SNET and task assignment
Meeting video: Link
Transcript: Link
Agenda item 1 - Strategy SubGroup - [carry over]
Narrative:
Progress in the SingularityNET community in Latin America was discussed, focusing on event planning and the adaptation of the roadmap for the second quarter.
The importance of optimizing meeting time and the need to have representatives in each country to improve event participation were highlighted. Andrea mentioned the possibility of collaborating in specific events, such as the summit in La Paz, and opportunities were identified to participate in an Ethereum event in Córdoba and in ALEPH growth.
Decision Items:
Participate in the ALEPH Crecimiento event representing SingularityNET and analyze the possibility of participating in the ETH Córdoba event.
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] evaluate the details of participation in the ETH Córdoba event and confirm participation in the ALEPH Crecimiento event. [assignee] guillermolucero [due] 7 marzo 2025 [status] in progress
Agenda item 2 - Operations SubGroup - [carry over]
Narrative:
The organization of objectives for the quarters Q2 and Q3 was addressed, with Guillermo in charge of editing the roadmap to specify the objectives. It was proposed to eliminate the "Task Assignment" section in the document, replacing it with an "Action Item" that includes André's email to ensure proper notification.
Decision Items:
Determine 5 concrete objectives to prioritize during Q2.
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] Guillermo will edit the goals for Q2, reducing them to a maximum of 5 achievable goals. [assignee] guillermolucero [due] 7 febrero 2025 [status] in progress
Agenda item 3 - Onboarding SubGroup - [carry over]
Narrative:
The need to implement a developer academy in the MeTTa language in Spanish and Portuguese was raised, which was then developed in detail in different spaces and meetings of the SingularityNET working groups. It is expected that the next steps for its implementation can be established, thanks to having a real utility for the ecosystem.
Decision Items:
Determine the concrete objectives to prioritize during Q2.
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] Guillermo will edit the goals for Q2, reducing them to a maximum of 5 achievable goals. [assignee] guillermolucero [due] 7 marzo 2025 [status] in progress
Keywords/tags:
topics covered: onboarding form, roadmap, Events, La Paz summit, ETH Córdoba event, ALEPH Crecimiento event, MeTTa in Spanish, MeTTa., AI developers, developer academy
Thursday 20th February 2025
Governance Workgroup
Type of meeting: Weekly
Present: PeterE [facilitator], martinsoki, CallyFromAuron [documenter], PeterE, CallyFromAuron, AshleyDawn, guillermolucero, martinsoki, LordKizzy, LadyTempestt, Effiom, advanceameyaw, Évéline Trinité
Purpose: Weekly Open Governance meeting
Narrative:
We noted that in Q1, Process Guild voluntarily gave up 1,000 AGIX to help with budget fitting (reducing their cap from 2,000 to 1,000); so this should be restored in Q2. Since we have already said that budget caps will remain the same this Quarter as they were in Q1, the only way to do this is to give Process Guild 1,000 AGIX from Program reserves. We also agreed that we definitely need to reassess budget caps for Q3; and that this should be done in the light of the discussion on minimum budgets (the minimum a WG needs in order to operate).
Anonymity: Peter noted that it can be difficult to resolve objections when the objectors are not present in the meeting and prepared to "un-anonymise" themselves.
Vani said it can be difficult to raise concerns - especially serious, "whistle-blowing" type concenrns - without anonymity. How will we make sure the space feels safe to raise things?
We recapped the point made in the previous meeting that the process is not anonymous now, because anyone with access to the Ambassador Gmail account can see who said what - but it's not clear if people fully realise that.
LordKizzy confirmed that the Governance dashboard being developed in R&D Guild will keep user identities anonymous to the public, but admins will still have access to this information - this raises the question of who should be an admin.
LadyTempestt stated that she doesn't feel OK raising issues in the budget consent forms ever since she found out that it is not confidential, so she just abstains.
We noted that it would be possible to create the consent forms on a different Google account that only 1 person has access to (perhaps Peter, given his particular role in the ecosystem).
Guillermo said that a non-anonymous consent process can foster a stronger community. When you fear to give your opinion whatever it is, it's not good - raising concerns openly will improve our professional relationships and help us learn to accept criticism. The planned Governance dashboard hopes to address this, and to make it easier for people to raise concerns transparently. Vani said that while this can work, sometimes lack of anonymity means people give less honest feedback; so we get an apparent "consensus" that isn't real. Also, any negative effects of removing anonymity are likely to fall more heavily on those who are already marginalized, or who feel the least confident or the least safe. Guillermo countered that having anonymity can make it more likely that people will raise unfair or nonsense concerns. Kizzy pointed out that if people do not attend the discussion meetings, they don't know that their concern has been resolved, and will raise it again next time, so we go round in circles. Guillermo suggested we could make it an option when the new Governance dashboard is built - people could choose whether or not they want to be anonymous. Vani referenced a previous Governance meeting where it was suggested that we need an independent person or group who maintain oversight, but are not otherwise involved in budget decisions, and are neutral. It was agreed back then that it would be difficult to find such a person
We noted that by the end of Q2, the Governance dashboard should be ready, and this might change things - so this Quarter might be the only chance we get to try out a non-anonymous consent process and see how it goes.
We checked the new sheet for Q2 which LordKizzy has added to the Budget Planner, and agreed the additions he needed to make to it.
Discussion Points:
Process Guild's budget cap for Q2 2025
Need to reassess budget caps for Q3
Anonymity in decision-making
New Q2 sheet in the Budget Planner
Decision Items:
We decided to add 1,000 AGIX from Program Reserves to Process Guild's Q2 budget cap
[rationale] because Process Guild agreed last Quarter to voluntarily give up 1,000 AGIX to help with budget-fitting, but this was only ever intended as a temporary measure. When we agreed in a previous meeting that budget caps should stay the same as they were for Q1, we forgot about this.
[effect] mayAffectOtherPeople
We agreed that we will reassess / recalculate the budget caps for Q3, and will do it in the light of discussion of WG budget minimums
[rationale] Several WGs are unhappy with their caps; and we cannot continue to "top up" Process Guild from reserves indefinitely; so there needs to be an adjustment; and we need to ensure that minimums are covered.
[effect] mayAffectOtherPeople
We agreed to continue the discussion on anonymity next meeting.
[effect] mayAffectOtherPeople
Action Items:
[action] Vani and Peter to share Guillermo's infographics regularly over the next few weeks, together with links to relevant docs [assignee] CallyFromAuron [due] 10 March 2025 [status] todo
[action] Peter to create an anonymous Googleform to ask people whether they have ever not said what they think in the consent process because it is not anonymous. [assignee] PeterE [due] 27 February 2025 [status] todo
[action] LordKizzy to make agreed tweaks to the new sheet in the budget planner, adding formulae and budget cap totals. [assignee] LordKizzy [due] 27 February 2025 [status] todo
Keywords/tags:
topics covered: Q2 2025 budget, Reserves, consent process, Process Guild, Budget caps, anonymity, R&D guild, governance dashboard, safe space
emotions: decisive, Organised, Interactive, thoughtful
AI Sandbox/Think-tank
Type of meeting: Weekly
Present: osmium [facilitator], advanceameyaw [documenter], LordKizzy, Gorga, Kateri, martinsoki, Effiom, Clement Umoh, Santos, Osmium, advanceameyaw
Purpose: AI TOOLSET EXHIBITION
Media link: [Link](Platform link: https://audioread.com/ Video demo: https://www.youtube.com/watch?v=MVcS_jpdJPk)
In this meeting we discussed:
Meeting Coordination and Introductions:The call started with a welcoming conversation and retrospection on AI toolset exhibition, budget and AGIX performance were mentioned.
Kizzy drew our attention to the fact that we have to start looking into possible adoption and testing of some the tools that have been presented, eg., erazer.io, podcast.ai and LM notetaker.
Osmium walked us through the overview and importance of AI toolset exhibition.
The meeting continued with Gorga finally presenting on Audioread.
-Overview of the toolset: Audioread converts articles, PDFs, text, and emails into audio, allowing you to listen via your favorite podcast app or browser for more efficient content.
Architecture and Technology Stack: Audioread's system includes a Chrome extension and mobile apps for access, AI-powered TTS for text and PDF conversion, and API integrations for seamless podcast syncing and sharing.
-Outcome Report or Results and Impact:Audioread boosts productivity with 90% user satisfaction, fast 10-15s conversions, 98% accuracy, helping professionals and students save time with audio content. -Presentation was concluded with questions and comments concerning opensource projects within the context of the tool presented.
Kizzy highlighted on our next session plan, AI Sandbox & Project Showcase presentation by the NuNet core team on onboarding a device to NuNet.
Some concerns and challenges concerning our breakout panel debate session were raised, and we discussed on how we can do better next time.
Decision Items:
We decided to try the breakout session for the panel debate again next time to measure its impact
[effect] affectsOnlyThisWorkgroup
Action Items:
[action] advanceameyaw to document meeting [assignee] advanceameyaw [due] 27 February 2025 [status] done
[action] publishing the roundtable session video and retrospective sessions [assignee] LordKizzy, osmium [due] 13 March 2025 [status] todo
Keywords/tags:
topics covered: Audioread, architecture and technology, nunet, breakout panel debate, productivity.
emotions: Informative, interactive, educational
Onboarding Workgroup
Type of meeting: Biweekly
Present: Gorga Siagian [facilitator], Onize, CallyFromAuron [documenter], CallyFromAuron, AshleyDawn, Clement Umoh, Gorga Siagian, Sucre n Spice, Kateri, LordKizzy, martinsoki, maxmilez, daniel effiom, CJFrankie
Purpose: Biweekly meeting of Onboarding WG
In this meeting we discussed:
GitHub Board Updates
Gorga Siagian reviewed the action items for the group.
Anyone who is not yet a member of the Ambassador Program GitHub organization should DM SucrenSpice for their GitHub username.
Q2 2025 Budget Planning
Gorga outlined the deadlines for the Q2 budget, stating that proposals must be submitted by March 10. Lord Kizzy will contribute to budget planning alongside the Foscus Group.
Updates on Skillshare Session
Gorga announced that the Skillshare session on Understanding SNET's ecosystem will be postponed until Q2 because of budget issues.
Vani and Gorga worked on assigning facilitators for the next meeting, noting that Ayo has been absent from recent meetings. Kizzy volunteered to facilitate, while CJ was tasked with reminding Ayo about his availability.
Q1 2025 Quarterly Report Submission date: 27th February CJFrankie is working on it - he will change access on the document so everyone can leave comments
Review of Onboarding to Decentralization Research
Vani highlighted some issues with the research conclusions indicating that some terms were poorly defined and that the conclusions drawn contradicted the evidence. Gorga supported Vani's proposal to move the document back to in progress for further refinement. Vani added that the recommendations at the end might need to be in separate conclusions. It could be unethical to present them as directly supported by the eviden
Agreed on a call next week with Vani, Clement and LordKizzy to iron out the problems.
Action Items:
[action] Timestampping M&E session [assignee] Onize [due] 21 January 2025 [status] todo
[action] Arrangement of Q2 Budget proposals before deadline [assignee] LordKizzy [due] 10 March 2025 [status] todo
[action] Move completed action items to "Done" on the GitHub board. [assignee] Gorga Siagian [due] 20 February 2025 [status] done
[action] Submit quarterly report [assignee] CJFrankie [due] 27 February 2025 [status] done
Keywords/tags:
topics covered: Q1 2025 quarterly report, Q2 2025 budget, Onboarding to Decentralization research, research conclusions, skillshare sessions
emotions: Brief, Collaborative
Friday 21st February 2025
Marketing Guild
Type of meeting: Weekly
Present: LordKizzy [facilitator], martinsoki [documenter], LordKizzy, esewilliams, photogee, kareem, CJFrankie, Eric Davies, Kateri, advanceameyaw, Gorga Siagian, SubZero, martinsoki, PeterE, Ayo, Effiom
Purpose: Marketing Guild weekly meeting
Discussion Points:
LordKizzy began the meeting by welcoming everyone and reviewing the last meeting summary. LordKizzy went through Eric Davis document and gave update on the Zealy initiative progress report, indicating it is nearing completion with significant growth and massive increase in participation. Specifically, he developed two models, each containing 10 tags, which have been successfully uploaded to the Zealy board.
Photogee gave an update on the Podcast initiative. He noted that he collaborated with Kenichi concerning this and has received feedback from 6 people and the response was evenly distributed, two people for writers, two people for audio and visual specialist, and two people as producer and host. Which is going to be two two per month, two episodes for each month. They are going to test run one episode first. Kenichi brought up a suggestion on creating a general form with three sections of questions.The first episode is intended to serve as a learning experience, with Peter suggesting that initial episodes would help attract more guests. LordKizzy acknowledged that there shouldn't be an extra allocation for the operation for the initiative team because there is already an allocation for the initiative team in our budget. He also noted that people working on this podcast are working outside their scope but they are working within their scope.
Kareem presented his proposal on the design workgroup initiative under marketing guild. He stated that the budget of the design workgroup will come from the marketing guild. However, Lord kizzy stated that currently our budget is low and even with our reserves we can’t still fund the proposal.
Mikasa gave update on the Social media management and contributor spotlight. Which stated that the contributor Spotlight is not out yet but hopefully it will be out today. Also, the Twitter account already has the Premium Plus.
Graphics Team: Gorga stated he has made the design for the contributor Spotlight and he has changed the background, with the design of the Town Hall call announcement, the design of the Weekly meeting schedule in two languages, namely English and French, then the design of the AI sandbox related to the Think-tank debate and the design for the Writers workgroup related to the ecosystem page article, the community page, the post for the X trip, and the design of the monthly Twitter article post.
Kareem to give update on graphics. He stated that he has been reviewing designs making sure they meet up to the standards, and he has been working on the comic initiative, also, a couple of templates that will be used across the quarter.
Budget and task management: LordKizzy said he's currently drafting out the Q1 report and Q2 budget proposal for the Guild. we are actually going to have to make new cuts because of the token price. Hopefully by next he would present it so we can have a discussion around it.
Kenichi said based on the Marketing Guild Survey they have been getting more submissions on that. He stated that People have asked a lot of questions about the Ambassador program. There's not enough information about the Ambassador program out there. He plans on sharing links to the responses he received.
Community initiative review team LordKizzy and Kenichi had a call on Saturday whereby they looked at the responses from the community initiatives and also analyzed it before sending it to Ayo, so that they can get feedback from him. So that they can start reaching out to the selected members that got selected, so that they can make some necessary corrections for those that need to.
Kateri stated regarding the Community Spotlight, she has sent it across to Mikasa to post it. Guild Spotlights. She created the questionnaire and sent it to R&D Guild, which Guillermo told her that before the meeting, he would have responded to her. So she's going to check the questionnaire and then send it over to Goga.
Action Items:
[action] Ese to merge and present the Governance Doc. [assignee] esewilliams [status] todo
[action] Photogee to add items to Marketing Guild Google drive [assignee] photogee [status] todo
[action] Ese to create the charts for February so members can submit there task. [assignee] esewilliams [status] todo
[action] LordKizzy to reach out to the graphics Team and maybe mikasa to spotlight there previous project in R&D Guild [assignee] LordKizzy [status] todo
Keywords/tags:
topics covered: Governance, Guilds , Meeting Summaries, Zealy, Ambassador GitBook, Initiatives, GitHub project, Community podcast update, community spotlight
emotions: Friendly, informative, Discursive
Video Workgroup
Type of meeting: Weekly
Present: hogantuso [facilitator], Zalfred [documenter], hogantuso, LordKizzy, Slate, Malik, killy, AndrewBen, osmium, devon, frosh, SubZero, Zalfred
Purpose: The purpose of this meeting was to discuss the video work group activities and have a series of task distribution.
Working Docs:
Discussion Points:
UPDATE FROM THE TASK MANAGER A quick update from Slate on various tasks assigned within the week. He highlighted the November and December recap videos submission.
UPDATE FROM SOCIAL MEDIA MANAGER Andrew Ben gave a precise update highlighting that he didn't post out much. He added that he had reached out the certain persons that turned in videos with missing thumbnails and timestamps.
UPDATE FROM THE CURRENT ZEALY SPRINT Concerning the current zealy sprint, Lord kizyy announced that zealy sprint is having such a great impact specially across our social media platforms. For instance, he added that there’s been a significant increase in the number of subscribers across our socials media platforms.
UPDATE ON THE SPIN OFF PROJECT VIDEOS A presentation by lord Kizzy leaving the floor open for deliberation and suggestions. Lord Kizzy added that the videos for our spin off projects are ready which he shared to the house However, lord kizzy added that we'd prolly stand a chance to show case our quality videos and see how we can work abreast our spin off projects. lastly, He urged the house to make hay while the sun shines concerning drafting spin off project proposals.
DISCUSSION AROUND BUDGET CUTTING Due to the severe budget constraint, Lord Kizzy added that we have to make severe adjustments as we’re in a critical situation. Questions of how we can get more funding, cut out a lot of things, most probably, video productions and the rest of other recurring tasks as the allocations were drastically reduced. We need to look at how we can further reduce our budgets. Tuso raised concerns around the the current Agix Token price and the recurring tasks of the video work group as this appears to be an up hill battle. He added that we think critically before taking actions. 1.We need to look at how we can further reduce our budgets. lord kizzy suggested a biweekly call as a measure to reduce our pay out.
2.Slate suggested we keep some tasks of course with some cuts and basically see how we can sustain it for the rest of the quarter while having our eyes on the agix token price.
3.Lord Kizzy affirmed that there’s no way we’d pass Q2 without making cuts. Adding that we have to work with what we have.
FURTHER DISCUSSION ON THE CURRENT ZEALY SPRINT Concerning the zealy program,Lord kizy added that about 10 tasks has been published already and by the end of the zealy sprint, we could maximize the impact of the zealy and discuss how we can improvements, and basically measure the impact of the zealy program.
DISCUSSIONS ON Q1 REPORT Kizzy announced that he’s half way through the quarterly report and concerning the analytics, he added that the zealy would be a great impact for instance, there’s been a significant engagements across our socials.
Decision Items:
We need to look into how we can further reduce our budgets. The House Agreed that the next meeting will be dedicated to discussions around Budget fitting
[rationale]
[effect] mayAffectOtherPeople
Further operational calls with kenichi and the rest of the team to evaluate the impact of the zealy program and discuss measures to make it better
[effect] mayAffectOtherPeople
Action Items:
[action] Next meeting's is strictly for Budget fitting discussion [status] todo
[action] lord Kizzy to prolly draw a pull concerning videos selections for the spin off projects [assignee] LordKizzy [status] todo
[action] Task manager [assignee] hogantuso [status] todo
[action] Social media manager [assignee] AndrewBen [status] todo
[action] Meeting Facilitator [status] todo
[action] Town Hall Video Edits [status] todo
[action] Town Hall Video Summary [status] todo
[action] Meeting Documenting [status] todo
[action] Review Team [status] todo
Keywords/tags:
topics covered: Budget Allocation, Decision-Making , Budget Proposals , Budget fitting
emotions: Collaborative, Need for Clarity , Optimism , forward-looking
Writers Workgroup
Type of meeting: Weekly
Present: kenichi [facilitator], CJFrankie [documenter], kenichi, Mikasa, CJFrankie, Gorga Siagian, devon, inesgav, LadyTempestt, AJ, Évéline Trinité
Purpose: The weekly meeting of the writers workgroup
Working Docs:
Narrative:
Kick-off: The writers' workgroup weekly meeting commenced at 3:10 p.m. Kenichi reviewed the action items from the previous meeting. He announced that the Twitter premium plan had been activated and that the monthly Town Hall updates from January would be the first publication on X. Furthermore, Kenichi stated that the Web3 publishing platforms required additional attention and, to that end, requested that Cj Frankie and Gorga submit their first drafts.
DRAFTs: As agreed in the previous meeting, article suggestions will now be submitted via spreadsheet. In this meeting, Kenichi demonstrated the new writer's draft submission form, which streamlines the process. Writers can now suggest articles, include submission and preferred publication dates, and provide other relevant information. The form's integration with a Google Sheet simplifies tracking for the workgroup. Ines also recommended considering tools like Trello to further enhance workflow. In response to a question from Lady Tempestt, Kenichi confirmed that both writers and scribes will have access to the submission form. Once a draft is approved, the scribes will submit it to the community page. Kenichi will coordinate with Peter to pin the form link to the writer's channel for easy access.
Role document: Ines inquired about the new role document and its associated thresholds. Kenichi clarified that the document would be accessible this quarter and that there would be no penalties for not meeting any outlined expectations. He explained that the document's purpose is to track Scribblers' progress over time, enabling the workgroup to make informed decisions, such as whether or not to onboard new members.
Ambassador program website: In this meeting, Ines proposed the idea of creating a platform or WordPress for the workgroup, where all information about what we do can be easily accessed! Kenichi then revealed that he is collaborating with the R&D guild to develop an ambassador program website. This site will house comprehensive information about all participating workgroups, each of which will have its dedicated page with updated access.
Action Items:
[action] Kenichi to chase Peter to pin the writer's draft submission form in the writer's channel. [assignee] kenichi [due] 28 February 2025 [status] todo
Learning Points:
Last updated