Week 23
Mon 2nd Jun - Sun 8th Jun 2025
Last updated
Mon 2nd Jun - Sun 8th Jun 2025
Last updated
Type of meeting: Monthly
Present: CallyFromAuron [facilitator], CallyFromAuron [documenter], André, CallyFromAuron, Jeffrey Ndarake, Stephen [QADAO], PeterE, Effiom
Purpose: Regular monthly meeting of the Archives WorkGroup in the SingularityNET Ambassador program
Meeting video:
Working Docs:
Due to current token price being above $0.30, we agreed we can submit fund requests for all Q2 tasks now.
But we won't submit any pending tasks for Q1 at the moment
[rationale] The Q2 budget was calculated at the agreed exchange rate of $0.30, but Q1 was calculated at $0.55 so we're not there yet
[opposing] We might rethink in a month or two, and pay outstanding Q1 tasks anyway
[effect] affectsOnlyThisWorkgroup
André's tool development in May (see https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/262) included
working on a caching issue with the Archives dashboard (still not completely fixed), - updating scripts to capture meeting summary audits, so we can see what kinds of corrections are made when we do audit summaries.
We discussed how it would be useful to categorise what different types of corrections are made to meeting summaries - Vani will add a list to the June tool development issue.
[effect] mayAffectOtherPeople
In June, Stephen's focus will be on beginning to develop rule-based auditing of knowledge graph outputs - see https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/266 and https://github.com/Quality-Assurance-DAO/neo4j
This work will also be what Archives WG intends to focus on in Q3 2025; it might draw on sme ideas from the proposal that the Archives team submitted to the BGI Nexus funding round in March: https://deepfunding.ai/proposal/ethical-ai-auditing-a-practice-based-approach/
[rationale] To look at how communities can audit the knowledge graphs of their own data - an ethical approach
[effect] affectsOnlyThisWorkgroup
We closed the tag taxoonomy issue https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/133, and André will be using the defined tags in Q4 2025 when we re-start work on the redesigned Summary Tool.
We might also use some of the insights from it in ur knowledge graph wrk in Q3.
[effect] mayAffectOtherPeople
On the monthly archives GitBook issues: we noted that so far, Q2 summaries are being submitted without any chasing.
There are fewer meetings happening in general, since most WGs have moved to meeting only once a month; but the meetings that are happening, are generally getting summarised.
However, we noted that some cancelled meetings are still on the Calendar - we will ask WGs to tidy that up, since we take our list of what meetings are supposed to take place from the Calendar.
[effect] mayAffectOtherPeople
[action] Vani has approached DeepFunding to ask if the Events Circle could take on documentation of DF Town Hall. Events Circle is interested and is asking one of their members if he would be interested in taking it on. We'll review this next meeting. [assignee] CallyFromAuron [due] 2 July 2025 [status] in progress
[action] Vani to make a list of the different types of coorrectioons that get made to meeting summaries, and add it to https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/263 [status] todo
topics covered: AGIX price, controlled vocab, Knowledge management across the singularityNET ecosystem, AI ethics, Q3 2025 budget, Q2 2025 quarterly report, summary tool redesign, meeting summary audits, rule-based auditing, tag taxonomy, Deepfunding Town Hall, token price
emotions: interesting, low attendance, slow
Type of meeting: Weekly
Present: PeterE [facilitator], Tevo [documenter], UKnowZork, Kateri, CallyFromAuron, guillermolucero, Tevo, Alfred Itodele, Sucre n Spice, Clement Umoh, Duke, Jeffrey Ndarake, martinsoki, maxmiles, PeterE
Purpose: Regular weekly Open Governance meeting This group discusses governance issues for the Ambassador program, such as how we make decisions, how we reward contribution, how we decentralize, and how we ensure inclusion
Working Docs:
Q3 Budget Cap Finalisation
How do we proceed with Ambassador Program Budget Limits to existing groups?
Even if some groups wouldn't request funding, it still would affect the broader structure
Several workgroups have not communicated their Q3 funding needs clearly, delaying the collective understanding of total financial obligations.
There's a reliance on a few active contributors to raise concerns, with others remaining passive
[rationale] There was pushback to this change, but we could not find agreement on any other alternatives that could be applied in a relatively short amount of time (before the budget submission period)
[effect] mayAffectOtherPeople
[action] Update Core contributors about the new context and budget limits [assignee] CallyFromAuron [due] 9 June 2025 [status] todo
topics covered: Budget caps, Workgroup Funding, Sentiment Analysis
provided interesting outputs and an opportunity to change how we govern the budget, but further discussions and more involvement were expected before we implement it to steer our budgetary decisions.
Proceed with the percentage decrease based on the budget request in the previous quarter for the .