SingularityNET-Archive
  • Welcome to SingularityNET-Archive
    • Workgroup Proposal
  • Ambassadors Program
    • Overview
  • Timeline
    • 2025
      • January 2025
        • Week 1
        • Week 2
        • Week 3
        • Week 4
        • Week 5
      • February 2025
        • Week 5
        • Week 6
        • Week 7
        • Week 8
        • Week 9
      • March 2025
        • Week 9
        • Week 10
        • Week 11
        • Week 12
        • Week 13
        • Week 14
      • April 2025
        • Week 14
        • Week 15
        • Week 16
        • Week 17
        • Week 18
      • May 2025
        • Week 18
        • Week 19
        • Week 20
        • Week 21
        • Week 22
      • June 2025
        • Week 22
        • Week 23
        • Week 24
        • Week 25
        • Week 26
        • Week 27
      • July 2025
        • Week 27
        • Week 28
        • Week 29
        • Week 30
        • Week 31
      • August 2025
        • Week 31
        • Week 32
        • Week 33
        • Week 34
        • Week 35
      • September 2025
        • Week 36
        • Week 37
        • Week 38
        • Week 39
        • Week 40
      • October 2025
        • Week 40
        • Week 41
        • Week 42
        • Week 43
        • Week 44
      • November 2025
        • Week 44
        • Week 45
        • Week 46
        • Week 47
        • Week 48
      • December 2025
        • Week 49
        • Week 50
        • Week 51
        • Week 52
        • Week 53
    • 2024
      • January 2024
        • Week 1
        • Week 2
        • Week 3
        • Week 4
        • Week 5
      • February 2024
        • Week 5
        • Week 6
        • Week 7
        • Week 8
        • Week 9
      • March 2024
        • Week 9
        • Week 10
        • Week 11
        • Week 12
        • Week 13
      • April 2024
        • Week 14
        • Week 15
        • Week 16
        • Week 17
        • Week 18
      • May 2024
        • Week 18
        • Week 19
        • Week 20
        • Week 21
        • Week 22
      • June 2024
        • Week 22
        • Week 23
        • Week 24
        • Week 25
        • Week 26
      • July 2024
        • Week 27
        • Week 28
        • Week 29
        • Week 30
        • Week 31
      • August 2024
        • Week 31
        • Week 32
        • Week 33
        • Week 34
        • Week 35
      • September 2024
        • Week 35
        • Week 36
        • Week 37
        • Week 38
        • Week 39
        • Week 40
      • October 2024
        • Week 40
        • Week 41
        • Week 42
        • Week 43
        • Week 44
      • November 2024
        • Week 44
        • Week 45
        • Week 46
        • Week 47
        • Week 48
      • December 2024
        • Week 48
        • Week 49
        • Week 50
        • Week 51
        • Week 52
        • Week 53
    • 2023
      • January 2023
        • Week 01
        • Week 02
        • Week 03
        • Week 04
        • Week 05
        • Week 06
      • February 2023
        • Week 06
        • Week 07
        • Week 08
        • Week 09
        • Week 10
      • March 2023
        • Week 10
        • Week 11
        • Week 12
        • Week 13
        • Week 14
      • April 2023
        • Week 14
        • Week 15
        • Week 16
        • Week 17
        • Week 18
      • May 2023
        • Week 19
        • Week 20
        • Week 21
        • Week 22
        • Week 23
      • June 2023
        • Week 23
        • Week 24
        • Week 25
        • Week 26
        • Week 27
      • July 2023
        • Week 27
        • Week 28
        • Week 29
        • Week 30
        • Week 31
        • Week 32
      • August 2023
        • Week 32
        • Week 33
        • Week 34
        • Week 35
        • Week 36
      • September 2023
        • Week 36
        • Week 37
        • Week 38
        • Week 39
        • Week 40
      • October 2023
        • Week 40
        • Week 41
        • Week 42
        • Week 43
        • Week 44
        • Week 45
      • November 2023
        • Week 45
        • Week 46
        • Week 47
        • Week 48
        • Week 49
      • December 2023
        • Week 49
        • Week 50
        • Week 51
        • Week 52
        • Week 53
    • 2022
      • January 2022
        • Week 1
        • Week 2
        • Week 3
        • Week 4
        • Week 5
        • Week 6
      • February 2022
        • Week 6
        • Week 7
        • Week 8
        • Week 9
        • Week 10
      • March 2022
        • Week 10
        • Week 11
        • Week 12
        • Week 13
        • Week 14
      • April 2022
        • Week 14
        • Week 15
        • Week 16
        • Week 17
        • Week 18
      • May 2022
        • Week 18
        • Week 19
        • Week 20
        • Week 21
        • Week 22
        • Week 23
      • June 2022
        • Week 23
        • Week 24
        • Week 25
        • Week 26
        • Week 27
      • July 2022
        • Week 27
        • Week 28
        • Week 29
        • Week 30
        • Week 31
      • August 2022
        • Week 32
        • Week 33
        • Week 34
        • Week 35
        • Week 36
      • September 2022
        • Week 36
        • Week 37
        • Week 38
        • Week 39
        • Week 40
      • October 2022
        • Week 40
        • Week 41
        • Week 42
        • Week 43
        • Week 44
        • Week 45
      • November 2022
        • Week 45
        • Week 46
        • Week 47
        • Week 48
        • Week 49
      • December 2022
        • Week 49
        • Week 50
        • Week 51
        • Week 52
        • Week 53
  • Development
    • Design
    • Documentation Automation
    • LLM Development
      • Retrieval-Augmented Generation
      • Data Loading and Preprocessing
      • Vector Store Creation
    • Research
      • Stalnaker’s Concept of Context
  • Links
    • Tools
      • Google
      • GitBook
      • GitHub
      • Medium
      • Miro
      • SingularityNET Links
        • SingularityNET Discord
        • SingularityNET Main Telegram
        • SingularityNET Announcement Channel
        • SingularityNET Website
    • AI Tools
      • Google colab - Python notebook
      • LangChain - development framework
      • Infranodus - network thinking
      • Read.ai - transcription tool
Powered by GitBook

This work is licensed under a Creative Commons Attribution 4.0 International License

On this page
  • Thursday 27th February 2025
  • WG Sync Call
Edit on GitHub
  1. Timeline
  2. 2025
  3. February 2025

Week 9

Mon 24th Feb - Sun 2nd Mar 2025

PreviousWeek 8NextMarch 2025

Last updated 2 months ago

Thursday 27th February 2025

WG Sync Call

  • Type of meeting: Monthly

  • Present: PeterE [facilitator], CallyFromAuron [documenter], PeterE, CallyFromAuron, CollyPride, Duke, advanceameyaw, osmium, AshleyDawn, Clement Umoh, Sucre n Spice, kenichi

  • Purpose: Monthly call for all Workgroups to discuss Program-wide issues

  • Working Docs:

Agenda Items:

  • Which WGs are represented on the call?

  • WG minimum budgets

  • Increasingly late meeting start times

  • Archives will not be checking meeting summaries in Q2 2025

  • What WG Sync calls should be about (results of Googleform)

  • Ambassador Program End of Year Report 2024

  • WGs that are not taking part?

  • MeTTa Coders Lab initiative

Discussion:

  1. Workgroups represented on the call: We asked in Chat and found the following groups are present

  • Archives

  • AI Ethics

  • Onboarding

  • Translation

  • Writers

  • Marketing

  • R & D

  • Moderators

  • African Guild

  • Governance

  • Sandbox/Think Tank

  1. WG minimum budgets - How to progress discussion on the idea, proposed in the "budget caps for Q2" discussion doc https://docs.google.com/document/d/1kVd_4Ih-lSdMoIcmVeOS3_H3aqOdnMmMG6o1WqGTx1w/edit?usp=sharing , that WGs should determine their minimum budgets - it was decided that Governance WG is the best place for this conversation, and that we should not actually discuss it in this meeting.

  2. Increasingly late meeting start times: We recognised that it's difficult to fix without putting people off turning up at all. Suggestions included:

  • If you're late, your participation will not be counted (but most people would not mind that);

  • Start meetings at 5 mins past, regardless of who's present - of course this can't be enforced on WGs, but we could suggest it, and try it out in e.g. Governance, Town Hall, etc.

  1. Archives WG will not be checking meeting summaries during Q2 - Meeting summaries are often inaccurate or garbled, and it is a lot of overhead to check and correct them. So for budget reasons and experimental reasons, Archives will stop doing this during Q2, and will simply approve and archive whatever is submitted. They will then test whether the graph RAG process they are developing is able to "fill in the gaps" and derive meaningful and accurate information from summaries in Q2. If yes, it will be helpful to know that our archiving system doesn't require accurate summaries; and if no, we can assess what kinds of errors matter.

  2. Googleform responses on what WG Sync calls should cover: see https://docs.google.com/spreadsheets/d/1DYQb3U4AkXsxtOl7uHONFtfBkavicU1wleJskQKf5Ms/edit?usp=sharing There were 5 responses, all quite different. Key points:

  • Some issues with not knowing when the call is (we need to keep publicising it)

  • Best uses of time include cross-WG collaborations; feedback, evaluation, and knowledge sharing; top-level planning, and assigning relevant people to go off and discuss issues in more detail; external speakers.

  • There was a suggestion of using the call for progress updates, but this was felt to be very similar to the monthly "WG Updates" Town Hall, so perhaps not useful.

  • Should NOT be used for: Grievances/conflict resolution (we note that there is a process in place for that, see https://docs.google.com/document/d/1beMEt9XmPvHNaH08Rh5_taTI0QhHcyy15Q6XcXXDWUI/edit?usp=sharing , though it has never been used); Personal ideas; Decisionmaking and detailed planning; Issues that belong in Governance meetings. Note that some people in the meeting disagreed with some of these.

  • Future wishes for the calls - several of these have already started to be done; the idea of expert training sessions in the call itself, and followup discussion afterwards, remains to be discussed. We note that a previous Governance session (9th Jan 2025, https://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2025/january-2025/week-2#governance-workgroup-1) discussed how to encourage attendance from all WGs - there was a suggestion of rewards from Program reserves for WGs that attended all 3 meetings in a Quarter; although we noted that given current token price, this might not be something we still want to do. Nevertheless, we have recorded which WGs were present.

  1. End of Year Report 2024 - we agreed a final date of Sunday 9th March to finish the report https://docs.google.com/document/d/1TxKxP9sDNgvKncAqO0F-UhZgoftMdDktaqbt50-h2XM/edit?usp=sharing, and WGs who have not added material will do so by Fri 7th to allow time for a final proofread. We also noticed that several WGs (Education, Gamers, Strategy) have not added material and have not been coming to WG Sync calls - are they feeling excluded or disengaged in any way, or facing barriers? We did not reach conclusions on how or whether to ask them.

  2. MeTTa Coder Lab: This is intended as a "low-barrier-to-entry" way for people to learn MeTTa, and was originally a proposal in an RFP funding round, but was unsuccessful - so Guillermo is suggesting it as a cross-WG collaboration - education+ RND + AI SANDBOX +Onboarding plus any others who want to. The proposal and other materials were shared and comments were invited. There will be meetings soon to discuss the collaboration and how to fund it.

Decision Items:

  • We will continue to publicise the WG Sync calls, and the agenda, in Discord - maybe a little further in advance than we have been doing.

    • [rationale] Because the survey indicated that some people are not aware when the call is, or what is on the agenda

    • [effect] mayAffectOtherPeople

  • RE late start to meetings: we will try starting calls such as Governance WG, Town Hall, etc no later than 5 minutes in, regardless of who is present, rather than waiting; and will publicise that we will be doing this. Then in the next WG Sync we will discuss whether it has helped.

    • [rationale] to see if it helps encourage people to arrive on time

    • [effect] mayAffectOtherPeople

  • The question of how to approach WG budget minimums will be taken up in Governance WG

    • [rationale] because this call (WG Sync) doesn't feel like the best place for it due to time constraints

    • [effect] mayAffectOtherPeople

  • We agreed we will continue to capture which WGs are represented at the WG Sync Calls, but will decide at the end of the Quarter whether we want to go ahead with rewarding WGs who attend all 3 sessions, as agreed in Open Governance meeting on 9th Jan 2025 https://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2025/january-2025/week-2#governance-workgroup-1

    • [rationale] Due to low token price

    • [effect] mayAffectOtherPeople

  • Ambassador Program End of Year Report 2024 to be finished by end of day, Sunday 9th March. Anything not added by then, will not be used

    • [rationale] Because it is now well into 2025, so we need to finish it off

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] All to add comments on the MeTTa Coder Lab program doc #01 _ Agenda Items MCLab _ 250225 [assignee] all [due] 4 March 2025 [status] todo

Keywords/tags:

  • topics covered: budget minimums, late start to meetings, Archives WorkGroup, Correcting errors in meeting summaries, Meeting Summaries, WG sync call purpose, conflict resolution, End of Year report, End of Year Report 2024, Participation in governance, participation, disengagement, Strategy Guild, Education Guild, Gamers Guild, MeTTa Coder Lab, cross-WG collaboration

  • emotions: quiet, not many speakers, late start, positive, interesting

“Budget caps for Q2” discussion
Ambassador Program End of Year report - draft outline
Workgroup syncing call feedback (Responses)
#01 _ Agenda Items MCLab _ 250225 (MeTTa Coder Lab program)
CONFLICT RESOLUTION FOR SINGULARITY NET AMBASSADORS