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
  • Monday 22nd January 2024
  • Tuesday 23rd January 2024
  • Ambassador Town Hall
  • Wednesday 24th January 2024
  • Knowledge Base Workgroup
  • Education Workgroup
  • R&D Guild
  • Archival Workgroup
  • Research and Development Guild
  • Thursday 25th January 2024
  • Treasury Guild
  • Onboarding Workgroup
  • Deep Funding Town Hall
  • Friday 26th January 2024
  • Video Workgroup
  • Writers Workgroup
  • Saturday 27th January 2024
Edit on GitHub
  1. Timeline
  2. 2024
  3. January 2024

Week 4

Mon 22nd Jan - Sun 28th Jan 2024

PreviousWeek 3NextWeek 5

Last updated 1 year ago

Monday 22nd January 2024

Tuesday 23rd January 2024

Ambassador Town Hall

  • Type of meeting: Weekly

  • Present: Peter [facilitator], Vanessa [documenter], André, Emotu, Eric, Judith, Tevo, Vanessa, WaKa, Will Tatz, Peter, Boaz, Musonda Bemba, Rojo, lord kizzy, Headelf, Curtis, Vasu

  • Town Hall Number: 82

Timestamped video:

The Ambassador Town Hall is a recurring event happening live on the Ambassador Zoom channel https://www.youtube.com/@SNET_Ambassador each Tuesday at 19:00 UTC.

Slides:

Keywords/tags:

  • topics covered: BGI 2024 summit, meeting summary tool, the Ambassador role, roles and levels, mental wellbeing, mental health, useful documentation, what data to capture to assign ambassador role, the human touch, transition from manual archiving to use of meeting summary tool

  • emotions: curious, questioning, resistant to change, data driven

Wednesday 24th January 2024

Knowledge Base Workgroup

  • Type of meeting: Biweekly

  • People present: Tevo [host], Tevo [documenter], Tevo, Shankar, Vanessa, Peter, André, love, Slate, Jade, Emotu, Sucren, Friday, Anthony, devon

  • Purpose: Aggregating Ambassador Program assets and relevant information under GitBook

  • Miro board: https://miro.com/app/board/uXjVN-9yivE=/?moveToWidget=3458764574355478962&cot=10

  • Working Docs:

Agenda item 1 - Continues Onboarding - [resolved]

Discussion Points:

  • How new people are introduced?

  • How are participants encouraged to learn how to engage in and about workgroup activities?

  • Information that is available to learn about workgroup

  • How do new people become workgroup members?

  • potential causes of low retention rate of contributors

Decision Items:

  • Before doing public onboarding, we need clear entry-level tasks

    • [effect] affectsOnlyThisWorkgroup

  • Go through participant task in the call to make sure we are able to recognize new participants in Dework

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Create an onboarding feedback form that is mainly meant for new members [assignee] Tevo [status] todo

Agenda item 2 - Introduction to Knowledge Base Workgroup - [resolved]

Discussion Points:

  • Went over the Resource planning process

  • Share examples of the task outputs

  • Explained rewards for different tasks

Agenda item 3 - Reviewed Onboarding Items - [carry over]

Discussion Points:

  • Should Ambassador Program Onboarding Analysis be part of GitBook?

  • Should the Getting Started Google Doc version be available in GitBook?

  • The goal of an Ambassador GitBook: Should it be for resource management, How it related to Onboarding, What type of knowledge it should include

Decision Items:

  • Include "Onboarding WG report Q4 2023 - Google Doc" in GitBook

    • [effect] mayAffectOtherPeople

Keywords/tags:

  • topics covered: Onboarding, Getting Started, Video Script, Analysis, Proposal, Introduction, Feedback Form, Ambassador GitBook, Miro Board

  • emotions: This session had a lot of new members and we needed to slow down a lot to get people introduced into workgroup

  • other: Onboarding WG Quarterly Report - https://docs.google.com/document/d/173UxTc38LhXwR6QuJCKpH9CivgMCQhL4jZZXoMOw-nM/edit#heading=h.ybfi2uikflvv, Ambassador Program Onboarding Analysis - https://docs.google.com/document/d/1buAkowcI_kEbycPd_U6nkJeAeryOwYb_o9Nt18dKozc/edit#heading=h.c3dwzdvtnpi1, Ambassador Program Getting Started guide - https://docs.google.com/document/d/1q4dhediWgcbgAP3Wfsky_-roVyfCUe6xi-dhBdHbU4s/edit#heading=h.xtpvv9xicqnq, Onboarding Workgroup Miro Board - https://miro.com/app/board/uXjVM5jyehQ=/?moveToWidget=3458764576645510044&cot=14

Education Workgroup

  • Type of meeting: Weekly

  • People present: Headelf [host], Slate [documenter], Slate, devon, osmium, esewilliams, Rojo, Headelf

  • Purpose: ACP

Meeting Topics:

  • Introduction and Tool Discussion

  • Scribe Appointment - Slate

  • Slate's Video for ACP

  • Infographic on SingularityDAO by Devon

Discussion Points:

  • Headelf welcomed everyone and discussed the archive tool presented by the workgroup.

  • Identified challenges in using the tool for meeting notes due to specific sections.

  • Proposed the role of a scribe to document meeting summaries in the archive tool.

  • Slate volunteered for the scribe role, having participated in the tool's beta testing

  • Slate showcased a video on the "Sophiaverse" spin-off project

  • Headelf sought opinions on the video's content and quality

  • Positive feedback received; video praised as the best in ACP so far

  • Devon presented an infographic, discussed its target audience, and raised concerns about design consistency

Decision Items:

  • Slate appointed as the scribe

    • [effect] affectsOnlyThisWorkgroup

  • Agreed on a payment of $20USD per meeting, subject to change based on time spent

    • [effect] affectsOnlyThisWorkgroup

  • Suggestions for improvement: Add more subtitles

    • [effect] affectsOnlyThisWorkgroup

  • Adjust infographic to target the ambassador audience

    • [effect] affectsOnlyThisWorkgroup

  • Maintain standard color scheme; avoid copying and pasting text

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Opened a position for a scribe. [assignee] Slate [due] 24 January 2024 [status] done

  • [action] Consider adding subtitles using YouTube's autogenerated feature [assignee] Slate [due] 31 January 2024 [status] in progress

  • [action] Explore the video's potential for marketing efforts [assignee] Slate [due] 31 January 2024 [status] in progress

  • [action] Devon to revise the infographic as per feedback [assignee] devon [due] 31 January 2024 [status] in progress

Keywords/tags:

  • topics covered: Meeting Summaries, ACP, Videomaking, infographic

  • emotions: Collaborative

R&D Guild

Present:

Rojo [facilitator], Guillermo [documenter], Ubio, Curtis, Vasu, Duke, WaKa

In this meeting we discussed:

The overall purpose of the meeting was to go over the new R&D Guild proposal, the new workgroup operations strategy, and fundamentals for the governance system for the guild.

  • Discussed the difference and definition of Resaerch, Ideation and Development, and the potential scope of the Guild in relation to ambassadors' needs, and how to approach the different guilds and WorkGroups for further actions.

  • We continued with the discussion that began in the guild Discord chat about the possible segregation or not into two independent bodies, advantages and disadvantages. The members will present their positions and arguments.

  • WaKa: I envision **Innovation** [ex-Incubation] providing a range of services to other Ambassador units, according to their needs and our capabilities. These will eventually include analysis of wants and needs, identifying processes, features and benefits, crafting designs and executing development, organizing testing, deployment, training, and support. Ambassador program has a very specific charter and a fixed budget, in most ways separate organization from a dozen and a half projects and organizations under the sNET umbrella. To me, a Guild formed within Ambassadors and applying its budget has an obligation to focus on executing a definitive segment of the overall organizational vision and plan. Providing services according to the needs and the timelines of other groups, while tapping into their budgets, is best delivered by a separate unit, perhaps a financially self-sufficient WorkGroup. Without a clear separation, I do not see bringing more external business or recruiting specific skill sets, as those may not align with Ambassadors' mandate and plan."

  • Rojo: The R&D initiative is funded based on projects according to the sheet we agreed upon. That means that the ambassador program is funding specific projects with clear outcomes and use cases. Any external endowment, if agreed upon, will also be funding a specific project. Therefore, double rewarding for the same work, or making use of ambassador funds for other entities, cannot happen under this paradigm."

  • Discussed the different governance systems. For the selection of the proposals to be developed according to the available budget, the possibility of involving the different guilds in the selection was discussed, thus establishing a priority according to the needs of the group.

  • Discussed the possibility of voting among guild members.

Decisions:

[decision] Guild members agreed that it is beneficial for the whole to maintain the unity of the guild and evaluate reincorporating the 'ideation' functionality as a service for the other guilds and workgroups. This completes the circle with the total capacity of Research, Ideation and Development.

[decision] The use of a template for the standardization of the guild’s proposal submission processes was discussed and approved.

[decision] TBD Final schedule and time slot for guilds weekly meeting.

Action items

none

Keywords:

Topics covered: Teamwork, deliverables, respect, scope, flow, tooling, results, trust

How the meeting felt: Fun, Exciting, Collaborative, Productive

Other We miss Fly!

Archival Workgroup

  • Type of meeting: Biweekly

  • Present: Stephen [facilitator], Stephen [documenter], André, Vanessa, Stephen, Peter, Slate, Onyeka, Vasu

  • Working Docs:

Action Items:

  • [action] Bring to next meeting a list of things that should be included in Governance GitBook update [assignee] Vanessa [due] 7 February 2024 [status] todo

  • [action] Manually finish archiving all summaries from Nov and Dec 2023, and close the issues for those months so that fund request can be submitted [assignee] Vanessa [due] 7 February 2024 [status] todo

  • [action] Once November and December 2023 are archived, submit funding requests for those months, and close Q4 2023 Budget issue [assignee] Stephen [due] 21 February 2024 [status] todo

  • [action] Add bounties to Dework for 4 bounties: 1) Meeting publicity, 2) General Archives publicity; 3) Chasing meeting summaries; 4) Updates to Ambassador GitBook [assignee] Vanessa, Stephen [due] 26 January 2024 [status] done

  • [action] Draft an approach, with budget, for the Tag Taxonomy work, ready for next meeting on 7th Feb [assignee] Vanessa [due] 7 February 2024 [status] todo

  • [action] Contact Ubio with brief for his work on LLM tooling [assignee] André [due] 31 January 2024 [status] todo

  • [action] Core Archives team to meet with Supervisory Council re knowledge management on Fri 26th Jan [assignee] Stephen, Vanessa, André [due] 31 January 2024 [status] todo

Keywords/tags:

  • topics covered: Tag taxonomy, bounties, monthly archiving, publicity, meeting summary tool, Tool Development, AI tooling, Governance GitBook, mentorship, transition from manual archiving to use of meeting summary tool, Outreach, Knowledge management across the singularityNET ecosystem

  • emotions: Organised, Discursive, Well-attended, outward-looking

Research and Development Guild

  • Type of meeting: Weekly

  • Present: Rojo, Guillermo [facilitator], Guillermo [documenter], Curtis, Vasu, Duke, WaKa, Ubiodee

  • Purpose: R&D Purpose & Proposal

  • Working Docs:

Agenda Items:

  • The overall purpose of the meeting was to go over the new R&D Guild proposal, the new workgroup operations strategy. Fundamentals for the governance system for the guild.

Discussion Points:

  • -Discussed the difference and definition of Resaerch, Ideation and Developemnt and the potential scope of the guild in regards of ambassadors needs and on how to approach the differente guild and groups for further actions.

    • We continue with the discussion that began in the guild chat about the possible segregation or not into two independent bodies, advantages and disadvantages. The members will present their positions and arguments.

  • Walter; I envision Innovation [ex-Incubation] providing a range of services to other Ambassador units, according to their needs and our capabilities. These will eventually include analysis of wants and needs, identifying processes, features and benefits, crafting designs and executing development, organizing testing, deployment, training, and support.

  • Ambassador has a very specific charter and a fixed budget, in most ways separate organization from a dozen and a half projects and organizations under the sNET umbrella. To me, a Guild formed within Ambassadors and applying its budget has an obligation to focus on executing a definitive segment of the overall organizational vision and plan. Providing services according to the needs and the timelines of other groups, while tapping into their budgets, is best delivered by a separate unit, perhaps a financially self-sufficient Workgroup. Without a clear separation, I do not see bringing more external business or recruiting specific skill sets, as those may not align with Ambassadors mandate and plan.

  • Rojo: The R&D initiative is funded based on projects according to the sheet we agreed upon. That means that the ambassador program is funding specific projects with clear outcomes and use cases. Any external endowment if agreed upon will also be funding a specific project. Therefore double rewarding for the same work, or making use of ambassador funds for other entities cannot happen under this paradigm.

    • The use of a template for the standardization of the guild’s proposal submission processes was discussed and approved.

    • Discussed the different governance system For the selection of the proposals to be developed according to the available budget, the possibility of involving the different guilds in the selection was discussed, thus establishing a priority according to the need of the group. The possibility of voting among guild members.

Decision Items:

    • Guild members agreed that it is beneficial for the whole to maintain the unity of the guild and evaluate reincorporating the 'ideation' functionality as a service for the other guilds and WG. This completes the circle with the total capacity of Reasearch, ideation and development.

    • [effect] mayAffectOtherPeople

    • TBD Final schedule and time slot for guilds weekly meeting

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Next step will be to analyze the team's proposals. to this day we have 10 proposals or ideas in a state of ideation, some of them have the backup of a research and blue print and others are just ideas of potential developments that the different members of the team have developed and shared in the initial document that we have reviewed in this session and will share tomorrow with the tresury guild. Proposals name and description can be found at the GR&D Guilds Propposal. [assignee] Rojo, Guillermo [due] 31 January 2024 [status] done

Keywords/tags:

  • topics covered: Guilds , Budget , Onboarding, Roles, Tool Development, Proposal, Q1 projections

  • emotions: Collaborative

Thursday 25th January 2024

Treasury Guild

  • Type of meeting: Biweekly

  • People present: Tevo [host], Tevo [documenter], Tevo, André, Miro, Emotu, Vanessa, Peter, Rojo, William, Headelf, Guilermo, Sucren

  • Purpose: Structuring Ambassador rules around payments, tasks and anything related to financial activities

  • Miro board: https://miro.com/app/board/uXjVN8kUlbw=/?moveToWidget=3458764574789806585&cot=10

  • Transcript: https://app.dework.xyz/singularitynet-ambas/treasury-guild-87240

  • Working Docs:

Agenda item 1 - Differentiating long-term (core) contributors - [carry over]

Discussion Points:

  • Default System Criteria to recognise Core Contributors

  • Additional options to become a Core contributor

  • Downsides of differentiating Core contributors

Decision Items:

  • Core Contributors can also be nominated

    • [effect] mayAffectOtherPeople

  • Core Contributors will have a higher weight in the decisions

    • [effect] mayAffectOtherPeople

  • Policy Rules are ratified in the Governance Workgroup

    • [effect] mayAffectOtherPeople

Agenda item 2 - Staking AGIX - [resolved]

Discussion Points:

  • Ethical concerns

  • Education on Staking AGIX

  • Social effect when staking AGIX

  • How AGIX staking works and its purpose

Decision Items:

  • Currently, we will not start staking Ambassador Program Reserved AGIX due to ethical concerns

    • [effect] mayAffectOtherPeople

Agenda item 3 - 2024 Treasury Budget Quarter 1 - [carry over]

Discussion Points:

  • How could we lower our budget requests to fit the Ambassador Budget?

  • How could we improve the Ambassador Program Quarterly Budget Sheet?

Decision Items:

  • Move back to create proposals and budget requests in stable values (USD) and AGIX conversion applied at the ambassador program budget level

    • [effect] mayAffectOtherPeople

  • We will not include a budget for new ideas and potential experiments in Quarter 1

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Include a new column that links to budget proposals to the Ambassador Program Quarterly Budget Sheet [assignee] Tevo [status] todo

  • [action] Wait for other workgroups to deliver their budget proposal [due] 8 February 2024 [status] todo

  • [action] Every workgroup is expected to remove the budget for unplanned items [status] todo

Keywords/tags:

  • topics covered: Miro Board, Budget , Quarter 1, Staking, Proposals, AGIX, Stable Value, Ethics

  • emotions: We had quite a tension around discussing the differentiation of core contributors and how it's done

Onboarding Workgroup

  • Type of meeting: Weekly

  • People present: LadyTempestt [host], Onyeka [documenter], Sucren, Vanessa, Peter, esewilliams, Tevo, Cjfrankie, Slate, Precious, Duke, lord kizzy, LadyTempestt

  • Working Docs:

Town Hall Updates:

-Thanks to those who participated in our Continuous onboarding sessions -Onboarding session on the 8th February 2024. -We have more people joining the Onboarding Workgroup and talk on the criterias for you to become a member. -Quarterly Budget Report.

Discussion Points:

  • Minutes of last Meeting

  • Action items from last meeting

  • Next Ambassador TH Update

  • Twitter thread on the Getting started channel

  • Continuous Onboarding Session Report

  • Onboarding Workgroup Facilitation and Documentation Roster

  • Q4 Quarterly report

  • Budget for Q1

Decision Items:

  • We agreed to set a deadline (15th of February) for the Onboarding Session Report.

    • [opposing] None

    • [effect] affectsOnlyThisWorkgroup

  • We decided that the asynchronous input from R&D, Education and Strategy can be added as comments to the Report.

    • [opposing] None

    • [effect] affectsOnlyThisWorkgroup

  • We have decided to create a Twitter tweet to announce our Onboarding session.

    • [opposing] None

  • We decided to split the Facilitation of the Onboarding Session into 4 parts

    • [opposing] None

Action Items:

  • [action] Sucren to speak to Mikasa to create a tweet to announce the Onboarding session [assignee] Sucren [due] 1 February 2024 [status] todo

  • [action] Lady Tempestt to create a resource, with ideas for how WGs can support continuous onboarding [assignee] LadyTempestt [due] 1 February 2024 [status] in progress

  • [action] Vani to make the necessary corrections to the Onboarding Session slides [assignee] Vanessa [due] 1 February 2024 [status] todo

  • [action] Lord Kizzy to create a report on Continuous Onboarding (1st draft bring to meeting on 15th) [assignee] lord kizzy [due] 15 February 2024 [status] in progress

  • [action] Lord Kizzy to give the onboarding updates in the next TH meeting [assignee] lord kizzy [due] 30 January 2024 [status] todo

  • [action] Lord Kizzy to share the infographic to announce the Onboarding session on the 8th of February [assignee] lord kizzy [due] 2024-01-11 [status] todo

Learning Points:

  • GMBLS has been changed to MINS

Issues:

  • The Onboarding Session.

  • The Continuous Onboarding Report

  • The Question on Guilds and WorkGroups

Keywords/tags:

  • topics covered: Guilds , Onboarding, TH Update , Roles, Budget

  • emotions: Collaborative, speedy , funny , Thoughtful , Friendly

Deep Funding Town Hall

  • Type of meeting: Biweekly

  • Present: Judith, Jan Horlings [facilitator], Vanessa [documenter], Judith, Jan Horlings, Kenric, Mauro Andreoli, Juana Attieh, Headelf, Megan Hess, Mercy, Mike Lewis, Juan Pablo Barea, Guillermo, Curtis, Newman Lanier, Ubio

  • Purpose: Improving voting and decison-making

  • Town Hall Number: 25

  • Working Docs:

Timestamped video:

This bi-weekly meeting is an initiative led by the SingularityET Ambassador community. We invite you to be part of our regular event where we share updates, presentations & conversations about topics that relate to Deep Funding and SingularityNET.

Keywords/tags:

  • topics covered: voting, testing voting behaviours, Deep Funding test round, Community RFPs, RFP, feedback, quadratic voting, Decision Making Process, identity, distributed, platform, Deepfunding proposal platform, proposal platform, voting behavior, strategic, reputation, complex systems, experiment

  • emotions: analytical, fiery, lively, silencing, complex, heated, passionate, frank, upfront, straightforward, ideas

Friday 26th January 2024

Video Workgroup

  • Type of meeting: Weekly

  • Present: Rojo [facilitator], Judith [documenter], cardano_class, devon, Dr Strange, Duke, Judith, lord kizzy, malik, Peter, Rojo, Slate, Zalfred

Discussion Points:

  • Updates from Task Manager Devon on everybody's outstanding tasks

  • Slate got welcomed as new video WG member

  • Updates from Lord Kizzy and Judith on Q4 report and Q1 projections

  • Updates from Malik (Social Media Management) on social media numbers and that analytics are difficult to get

  • Is it time to push the Ambassadors Program?

  • Anwering questions from Zalfred who introduced himself

  • BGI - people can still apply to go

Decision Items:

  • You will have to assign tasks points yourself to subtasks in Dework (not main tasks)

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Malik to do research on best social media metrics to track (others can help too) [assignee] malik [due] 2 February 2024 [status] todo

  • [action] Check at Ambassadors' TH if we should start pushing the program [assignee] Anyone [due] 1 March 1 [status] todo

Keywords/tags:

  • topics covered: BGI, social media management, Q4 report, Q1 projections, Ambassador Program marketing

  • emotions: Friendly

Writers Workgroup

  • Type of meeting: Weekly

  • Present: Kenichi [facilitator], cjfrankie [documenter], Kenichi, cjfrankie, Mikasa, devon

Narrative:

Kenichi shared his screen for the Scribblers to see the milestones the workgroup has achieved in the last couple of months.

We’re growing indeed and it’s a thing of joy to share it with the Scribblers who have been part of this remarkable journey.

One of the articles that piqued the interest of many individuals is the article written by our very own Mikasa: “AI Cryptography: Enhancing Security and Privacy in the Digital Age."

Good news: our first ever points system will be up and running by the end of this month; scribblers will be rewarded with points as they contribute along the way!

Buildup to the BGI Event is still ongoing. Scribblers are encouraged to tune in; they can also find interesting article suggestions while participating.

Kenichi shared an article suggestion from the CEO of Rejuve.ai, "Using AI and blockchain to target aging", and some interesting updates from Cogito, including a forthcoming Twitter space this Mon 29th Jan with the CEO, Cloris Chen https://twitter.com/CogitoProtocol/status/1750443374304239674

Cjfrankie shared some article suggestions: "AI and Longevity: Unlocking the secrets to prolonged Human Lifespan" and "Digital Dynamo: How AI-Powered Marketing Strategies Catapult Startups to Success".

Our Medium page is growing exponentially. Our goal is to reach the milestone of 1k reads by the end of February 2024.

Decision Items:

  • We set a goal to reach 1k reads on Medium by the end of February 2024.

    • [effect] affectsOnlyThisWorkgroup

Keywords/tags:

  • topics covered: Cogito, Points system, BGI 2024 summit, Zealy, Rejuve, Longevity, medium, AI-powered marketing, Marketing, Medium milestones, Beneficial AGI, Weekly updates

  • emotions: quiet

Saturday 27th January 2024

Intro Who Will Be Attending The Bgi 24 Summit Meeting Summary Tool What Cool Things Will The Tool Enable Us To Do Next How The Tool Works Useful Documentation And Tracking Decisions The Ambassador Role Experiment Who's Tracking Time? Any Strong Objections To Using Governance Workgroup Meetings To Discuss Further? Mental Wellbeing

[decision] Next step will be to analyze the team's proposals. To date, we have 10 proposals or ideas in a state of ideation; some of them have the backup of research and a blueprint, and others are just ideas for potential developments that the different members of the team have developed and shared in the initial document that we have reviewed in this session and will share tomorrow with the Treasury Guild. Proposals' names and descriptions can be found in the GR&D Guilds Proposal:

Sources Research & Development Guild Presentation _ @SingularityNET Ambassador _090124

Research & Development Guild Budget Proposals Sheet _ 100124:

Meeting video:

Deep Funding Town Hall Is A Platform For Community Engagement And Feedback. Test Round Updates And Challenges Encouraging Community To Create Rfps For New Rounds Collecting Feedback On Improving Voting And Decision-making Process What Problem Are We Trying To Solve With This Complex Reputation System, And Is There An Easier Way? Improving Voting And Decision-making Process In The Df Rounds Quadratic Voting Forces Consideration And Constraints On Allocation The Importance Of A Strong Identity System For Decision-making Process. Testing Different Voting Scenarios And Behaviors Importance Of Distributed Identity In Decision-making Process Improving Decision-making Process In Deep Funding Rounds

00:00
01:58
09:46
14:18
15:27
37:15
44:21
47:13
53:31
54:21
Knowledge Base WG
https://docs.google.com/document/d/1PNd2LwMJSZw38w_G8vAph20pTWmjT62bcYmiEUB0ve8/edit
https://docs.google.com/presentation/d/1MVHXfjQDAafVFPwduLam4anMnHx0b8cUE8W08uniHrs/edit#slide=id.g2ad24b6b863_0_2
https://docs.google.com/spreadsheets/d/1RB7XBd393xGxpBg7ZuYQKyMIaGp18oevVDddW6vbcXo/edit#gid=1248558897
Link
Meeting Issue
Research & Development Guild Presentation _ @SingularityNET Ambassador _090124
Research & Development Guild Budget Proposals Sheet _ 100124
Treasury Guild Dework Space
Treasury Quaterly Budget Calculator
Treasury Guild Proposal
SNET Onboarding WG Task Reward Sheet
Quarterly Workgroup Budget Calculator
GETTING STARTED CHANNEL / overview
Onboarding WG - how can we support other WGs to onboard new people in their meetings
Onboarding Workgroup MIRO
F&D roster
Sign-up form to run a breakout room
00:16
02:54
08:12
10:47
14:04
16:36
26:25
40:43
45:22
48:14
53:27