Week 31

Mon 29th Jul - Sun 4th Aug 2024

Monday 29th July 2024

Treasury Policy WG

Agenda item 1 - Reviewing responses on policies submitted, and its next steps - [carry over]

Discussion Points:

  • Response link: https://docs.google.com/spreadsheets/d/1Tlq_125RZp3C_uESRUy7mhYP1q7nbf7jdSE3b3iU46g

  • Check and review policy responses

  • What is the proper way to publish submitted policies?

  • At what point in the process should a quorum be required?

  • What should be the proper quorum to move a policy forward?

  • How to proceed in a situation if we have no idea how to decide, and we don't reach quorum?

Decision Items:

  • No quorum needed in voting phase for policy selection

    • [effect] affectsOnlyThisWorkgroup

  • The quorum is made of the people who share their review on policy

    • [effect] affectsOnlyThisWorkgroup

  • The policy is selected for Treasury Guild review if more than 80% of policy feedback is positive

    • [effect] mayAffectOtherPeople

  • The policy is ratified if more than 50% of core contributors who take part in deciding on the policy consent to the policy.

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Include quorum into the Policy Templates https://docs.google.com/document/d/1g-INSEasp4TsEWgGQSoTIxe-KLX79tXqzF3rhWbSI3M [status] todo

Agenda item 2 - Policies WG and its retrospective on process - [carry over]

Discussion Points:

  • Why did you get involved?

  • WG intends to develop a critical function for the entire program

  • WG meetings have been constructive and progresses very quickly

  • What didn't go well?

  • We don't have clarity on why other Core Contributors don't join these sessions or take part in policy creation

  • Unclear if lack of attention to policy development is a good thing (no changes needed) or a bad thing (we are improvement suggestions poorly)

  • How hard or easy is it for you to create a policy?

  • Submitting policies is a direct result of observing, and requires listening skills

  • Feel like we have extensive and clear guidelines to make policy creation simpler

  • Has the policy feedback that we have gathered in Policy WG been useful?

  • Currently not enough data, but with current responses its been useful for submitter

  • Has the Policy Workgroup and its new policies had any impact?

  • Currently no impact, but its great to increase awareness

Agenda item 3 - Review New Policy Submissions - [carry over]

Discussion Points:

  • Policy submission link: https://docs.google.com/spreadsheets/d/1-tAwCD3vrXNSbUdQApljTVMfFGVDJo6PBdM39CO73Uk/

  • No new policy was submitted

Decision Items:

  • We continue to keep the Policy Submission form open and move over to async submissions and reviews

    • [effect] mayAffectOtherPeople

Treasury Guild

Agenda item 1 - Review of Q3 Consent Dashboard and Iteration Process - [carry over]

Discussion Points:

  • How did we progress from Quarter 2 to Quarter 3?

  • What insights can we get from these dashboards?

  • Mitigating the instance of duplicate submissions by people

  • What information would we like to add?

  • Did the Quarter 3 budget proposal timeline and consent rounds duration have any impact on participation?

  • Participation of core contributors in consenting rounds

  • Do we maintain the consenting rounds as it is?

  • Are there particular insights we want to see in the dashboard next quarter?

Decision Items:

  • Allow editing responses, but enable only 1 submission per person

    • [effect] affectsOnlyThisWorkgroup

  • Move all consent decision making into a single form

    • [effect] affectsOnlyThisWorkgroup

  • Publicize the concerns about any proposals that do not pass iteration

    • [effect] mayAffectOtherPeople

  • There are no concerns with core contributors consenting to only their WG's proposal

    • [effect] affectsOnlyThisWorkgroup

  • We maintain the consent rounds and dashboard but add comparative analysis across quarters

    • [effect] affectsOnlyThisWorkgroup

Agenda item 2 - Ambassador Program Reserves - [carry over]

Discussion Points:

  • Do we know where the funds are coming from?

  • How do we know how much reserves we have left?

  • Do we know the wallet address?

  • How public should be the SingularityNET Foundation Wallets?

  • How does the token merger affect reserves?

  • The process from SC Wallet to intermediary SC wallet to Treasury for distribution

  • Ambassador Program gets to request a % from the 1.5% in SC Wallet

  • The 10% price change buffer from reserves

  • Currently, there is no deadline for when WGs' carried-over budgets should be used

  • A percentage to allow go over budget, overspending and use of reserves

Decision Items:

  • We don't know exactly how much reserves we have because of all the entities involved

    • [effect] affectsOnlyThisWorkgroup

  • Related to token merger, ASI tokens are already pre-minted but locked

    • [effect] affectsOnlyThisWorkgroup

  • It was agreed previously to roll over unused WG budgets for each quarter

    • [effect] mayAffectOtherPeople

Agenda item 3 - Consent Recognition - [carry over]

Discussion Points:

  • Does MINS tokens make sense?

  • Influence Tokens with ticker [INF]

  • Do we want to request Token Design from Marketing Guild?

  • There was no feedback or interest about token thinking outside this call idea

Agenda item 4 - Treasury Guild Administration - [carry over]

Discussion Points:

  • Next steps for Treasury Guild

Decision Items:

  • No Treasury Guild meeting till September 2024

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Start drafting Treasury Guild Q4 proposal after break [status] todo

Agenda item 5 - Treasury Guild Dashboard Columns - [carry over]

Discussion Points:

  • How do we reconstruct history, if at all?

Keywords/tags:

  • topics covered: dashboard, forms, insights, consent, reserve, Budget, wallet, reallocation, reserves, token merger, ASI, MINS, Influence tokens, Q4 budget, consent process, consent dashboard, buffer, 10% buffer

Strategy Guild

Narrative:

Action Items Checkboxes from the last meeting - Ayo led the discussion on the action items from the previous meeting.

1.Volunteers (i.e. Ayo, Tuso, and Onyeka) will engage Writers, Video, and Marketing WG respectively to ensure they have representation at the next meeting 2.Everyone to contribute to the Strategy Guild Working Document 3.Everyone to contribute to the Possible Survey Questions [Strategy Guild] 4.Effiom to create a new sheet in working doc for interest in meeting facilitation 5.Core members should indicate interest in facilitating the new sheet in the working doc 6.Effiom to share previous meeting summaries and this meeting summary

Onboard New Members/Core Member Roll Call - Tuso and Effiom were welcomed officially as new core members of the Strategy guild. Ayo explained how everyone can become a member, and also contribute and be a part of what is happening within the guild.

Selection of the Workshop Documenter - Yemi Solves was selected as the Workshop Documenter and Onyeka agreed to mentor him for this role.

The Outbound WGs/Gs Workshop Ideation Session - The Workshop coordinator and documenter shared the agenda and notes for this session below.

Strategy Guild Workshop Ideation Session: https://docs.google.com/document/d/1SeyaZ_yKFK34KRkQ78jkLqHsZXFL3-b_mSgGRqWy62Y/ Workshop Ideation Session Notes: Strategy Guild 29th July 2024: https://docs.google.com/document/d/1Qz2WiEmTZYOEPhOVdYl_VY_U_YmdHXap_AehXLqycko/edit#heading=h.6fyp3cl3ve7w

A.O.B - Ayo expressed gratitude to the participants and provided an overview of the plan for the next sessions

Decision Items:

  • The next meeting will be about improvements and execution

    • [effect] mayAffectOtherPeople

  • Participants from other WGs are to join the next sessions

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Everyone to contribute to the Strategy Guild Working Document [status] todo

  • [action] Everyone to contribute to the Possible Survey Questions [Strategy Guild] Document [status] todo

  • [action] Core members should indicate interest in facilitating the new sheet in the working doc [status] todo

  • [action] Effiom to share previous meeting summaries and this meeting summary [assignee] Effiom [status] todo

  • [action] YemiSolves to document and share the Workshop Session [assignee] Yemi Solves [status] todo

  • [action] Onyeka to mentor Yemi Solves [assignee] lord kizzy [status] todo

Keywords/tags:

  • topics covered: Guild Membership, Workshop Ideation, Core Membership, survey, participation, contribution

  • emotions: Brainstorm, planning, new ideas, Ideating, interesting, Collaborative

Wednesday 31st July 2024

Education Workgroup

  • Type of meeting: Weekly

  • Present: Slate [facilitator], Slate [documenter], Clement Umoh, esewilliams, GorgaSeagian, kateri, malik, Slate, Kenichi, Photogee, Yemi Solves, Onize

  • Purpose: - Dework Go through tasks - Deepfunding infographic - Clement's video after adjustments - OCEAN infographic after adjustments - Projects alignment with Google Classroom - Next meeting for Notion Setup - Meeting time increase poll - Rework task on SIngularityDAO

  • Working Docs:

In this meeting we discussed:

  • Dework Go-through tasks

  • Quizzes Review sheet go-through

  • Clement's video after adjustments

  • Projects alignment with Google Classroom

  • Next meeting for Notion Setup

  • Meeting time increase poll

  • Rework task on SingularityDAO

  • Deepfunding infographic

Discussion Points:

  • Slate started the meeting welcoming everybody

  • discussed tasks assigned and the updates on the tasks on Dework

  • Osmium gave updates regarding tasks reviews for quizzes and informed about reviews of some tasks

  • There was a discussion on deepfunding infographic and its quiz, as most sources should be from the infographic and the video

  • Then we discussed about CCCP, and everybody agreed that the completed projects should be put on the google classroom platform

  • Gorga and Osmium as uploaders and Slate as coordinator for that task was decided

  • There was also a discussion that the next meeting should be on "Notion page overview for 'Ai for beginners' project"

  • Osmium suggested that the next meeting time should be increased by about 30 minutes to cover all projects; everybody agreed to have a poll on that specific thing

  • Reworking the task on SingularityDAO was assigned to Clement, because the current one is outdated

Decision Items:

  • Ese and Osmium to present in next meeting on "Ai for beginners"

    • [rationale] Both assigned

    • [opposing] Nil

    • [effect] affectsOnlyThisWorkgroup

  • Clement to do SingularityDAO infographic rework

    • [rationale] Task assigned to him

    • [opposing] nil

    • [effect] affectsOnlyThisWorkgroup

  • OCEAN infographic approved

    • [rationale] everybody gave a green signal

    • [opposing] nil

  • have a poll for increase of meeting time

    • [rationale] Osmium suggested that the meeting should be longer to cover all topics

    • [opposing] nil

Action Items:

  • [action] Set up poll for increase meeting time [assignee] Slate [due] 31 July 2024 [status] done

  • [action] Assign google classroom setup to Gorga, Osmium and Slate as coordinator [assignee] Slate [due] 29 July 2024 [status] in progress

  • [action] audit approved tasks [assignee] Slate [due] 31 July 2024 [status] done

  • [action] Kenichi to present his "presentation series" project in next meeting [assignee] Kenichi [status] in progress

  • [action] Osmium and Ese to prepare for next meeting presentation for "Ai for beginners" [assignee] esewilliams, osmium [due] 7 August 2024 [status] in progress

Keywords/tags:

  • topics covered: review team, Dework Go through, Dework, Initial docs, Notion, Ai for beginners, video adjustments , representation, meeting time, task presentation, Google Classroom, SingularityDAO, Deep Funding

  • emotions: productive, Collaborative, Businesslike.

Dework PBL

Agenda item 1 - Updates on Participation vs Contribution Tooling - [resolved]

Discussion Points:

  • Now you can make select members to create the group of people who are in meeting

  • New parameter columns created for total AGIX contribution amount and selected contribution percent

  • Finished Source Data table which can now show all different contribution types

  • We used Knowledge Base WG to demonstrate updates

Action Items:

  • [action] Test tooling in use to for workgroups - September [assignee] Tevo [status] todo

Agenda item 2 - Constructing the algorithm and the next steps for Implementation - [carry over]

Discussion Points:

  • How do we construct the algorithm to be fair and incentivize expected behavior?

  • How do we use AGIX ratio?

Decision Items:

  • We use levels of differences in ratio to create rewarding weight

    • [effect] mayAffectOtherPeople

  • Final rewards per meeting will have a cap on total cost, hourly rate per person and personal limits

    • [effect] mayAffectOtherPeople

  • Total Weighted Rewards will be fitted to total cost

    • [effect] mayAffectOtherPeople

  • Final Rewards over personal limits will not be redistributed

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Implement algorithms to simulate results [assignee] Tevo [status] todo

Agenda item 3 - Future Session Facilitation - [resolved]

Discussion Points:

  • Future session facilitation

  • How to access zoom call while Tevo is on break?

Decision Items:

  • If meeting is cancelled still do the meeting summary if applicable

    • [rationale] Based on previously cancelled meeting, summary was done where applicable

    • [effect] affectsOnlyThisWorkgroup

  • Ensure to open call for at least 15mins before closing call if no one attends

    • [rationale] Some Treasury Operators taking call might join call for assistance and 15mins is enough time to accomodate latecomers

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Tevo to make sure zoom calls can be opened with phone, in case we need to open any Dework PBL Session [status] todo

Keywords/tags:

  • topics covered: Dework, Miro Board, tooling, implementation, Facilitation, holidays

Research and Development Guild

Agenda Items:

  • Welcoming new Members and Introduction

  • Review of last meeting summary Action Items

  • UPDATE STATUS ON DEVELOPMENT TO FILL REPOS!

  • SHOWCASE FINISHED PROPOSAL

  • NEW OPERATIONS SYSTEM GOING FORWARD

Discussion Points:

  • Review of last meeting summary Action Items: Lordkizzy went through the action items for the previous meeting

  • UPDATE STATUS ON DEVELOPMENT: Rojo gave the updates on Social Media Automation; The platform is currently in testing. The way the platform will interact with social media is that there is an API contact and some of these APIs need some time to be approved. We got approval from Google, YouTube API, and we're waiting for X (Twitter) and for Facebook. We're doing some testing. We are polishing the UI. We will do a push for the GitHub. Probably today or tomorrow we should be doing a push. Rojo shared a major challenge: he came across an open source project called Mixpost. This open source project is basically like an open source replica of Buffer.com, which does social media automation and social media dashboarding and team coordination, which is what the Guild is aiming for. He is currently testing this solution and the major issue is if while testing this solution, it does prove itself to be as good as what he seen so far, would it be a good idea to actually use this solution and part of the funding for our project so far would go to hosting and maintaining this solution rather than keeping working on the previous one and trying to improve it to reach the same level because our aim from the beginning was to build an open source project for this exact case. And it is sad that we had to build so far all of these things and just to realize that there was a solution already available, but it might be a more judicious and a smarter thing to do is to actually build upon previous open source solution that are already existing.

  • UPDATE STATUS ON DEVELOPMENT: Rojo gave the updates on the Web3 dashboard: He is done with the UI design. Talks will commence with Treasury Guild so that we can have the data access. Once we have the data access, we will be building from that.

  • UPDATE STATUS ON DEVELOPMENT: Kenichi gave the updates on the Legacy website

  • SHOWCASE FINISHED PROPOSAL: The Town Hall presentation for the Research on Inclusivity of people with disabilities was conducted by Clement on 30th of July 2024, now it's just left with the public announcement

  • NEW OPERATIONS SYSTEM GOING FORWARD: Lordkizzy shared the new operations system going forward

Decision Items:

  • We decided that AJ was going to continue the "Skills Collaboration Database" previously done by Curtis

    • [rationale] This selection was done based on AJ's skills and also due to lack of communication with Curtis

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Guillermo and Lord kizzy to have a discussion with Rojo and Kenichi on similarities between their projects and to see if there is a possibility for collaboration [assignee] guillermolucero, lord_kizzy [due] 7 August 2024 [status] todo

  • [action] Clement to reach out to Duke to create an infographic to project presentation on Discord [assignee] Clement Umoh [due] 24 July 2024 [status] todo

Keywords/tags:

  • topics covered: Guilds , Tool Development, AI tooling, contributors, Operations, Core team, Presentation, Voting process, deliverables, open source, disability, disability research, Collaboration, skills database, skills

  • emotions: Casual, Collaborative, speedy , Welcoming

PreviousWeek 30NextAugust 2024

Last updated

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