Week 27
26th June to 2nd July 2023
Last updated
26th June to 2nd July 2023
Last updated
We Prioritize critical Ambassador Activities and cover process changes
1) Closing down Action items from "To be Archived" lane
Description - in previous week we identified Agendas, actions and tasks that could be archived. Selected completed items to give brief updates on the results and outcomes Decision - No longer report completed items in Process Guild sessions Decision - Closed Items will be reported on the Meeting Summary as Decision Items Decision - Task to create a visual representation about Writers Workgroup onboarding model is completed Decision - Action to comment on Archival proposal is completed Decision - Task to Define frame / structure of Translation Guild is completed Insight - Miro Board should not be used to manage tasks that require change log auditability Learning - Notion has built in Project Management board and calendar Question - For items that have an strong archival sentiment from majority, should we also archive them without having to report them in on Process Guild session?
Description - A new model to help us organize tasks Decision - There will be no more async Miro Board votes from Process Guild sessions Insight - We have randomly tested creating sentiment analysis votes for async purposes; the participation rate has never been more than 5% of voter participation in the call. Learning - some participants don't have the capacity to participate in sentiment analysis because they have been voting too often in recent activities. Insight - some task priorities change week to week. Insight - it is possible to get quite good sentiment from 3 people voting compared to 7 people voting, shows that Ambassador Program Process Guild participants are quite aligned on most immediate agendas that the program should discuss and act on
We focus on creating educational project-based learning material for Dework. One of the main platform being used for this project is Andamio
Description - what roles stand out in the workgroup and who wants to take responsibility Decision - Learning Administrative side will not be incentivized with AGIX Action - Create PBL Workgroup Role in Discord Action - Coordinate a workshop to set up a local environment Insight - 4 people were interested in the administrative side of the Andamio platform.
Description - reasoning of markdown file requirements and recommendations Decision - After the first examples build a style guide Decision - Temporarily we will upload pictures to Ambassador Google Drive and include the picture name as a template on the markdown text Insight - Include links to different existing lessons if applicable Insight - Once Repo is public we will collect pictures for our own repository.
Establishing or maintaining processes to help community members to efficiently collaborate together
1) Workgroup Formation
Description - What should the workgroup formation roadmap look like? Decision - Workgroups have to have minimum requirements Decision - Workgroups will be differentiated by types Action - Search for potential guidelines from Mini Proposal Workshop templates Insight - We identified 3 different workgroup types that have different requirements Learning - 1 person workgroups are not sustainable
Create a Matrix table for workgroup types and requirements.
Cran, Headelf
cran, sucrenspice, rojo, peter, headelf, tevo, felix, eszter
2 hrs
Discussion highlights included what the malleability of a Fund Request could be and how proposals fit into this outline. Seemed to be an agreeance that the simplified budget made sense although not everything is fully hashed out quite yet.
The Draft outlines what a WG/Guild Lead is, Observable Responsibilities, and How to become a Lead. Some conversation also happened around introducing Rejuve into the program.
SucrenSpice
SucrenSpice, Peter, Headelf, Vani
1HR
The process flow for onboarding was analyzed and we came to a conclusion that the introductions channel might not be needed if new applicants to the program were directed to the sign-up form in the getting started channel. This channel should contain all a new member needs to know to get started and contribute to the program.
A discord channel for new members is not necessary. New members are to be directed to join the guild or workgroup they have interest in. The workgroup lead is responsible for welcoming the member into the group and conducting an interview/test or assigning a task if it is a requirement to be a member of the workgroup.
Information about the various workgroups and updates on what they are currently working in should be pinned in the respective channels. This would help new members have a sense of direction.
Vani and SucrenSpice would work together to update the onboarding process in the Gitbook.
How to structure Ambassador rules around payments, tasks and anything related to financial activities.
Description - Strategy Guild introduced quarterly timeline for budget changes Decision - We don't change budget distribution rules before quarter ends
Description - What roles have extra incentives or permissions related to Ambassador Treasury? Decision - WorkGroup leads have permission to request funds from Ambassador Treasury Decision - Ambassadors have permission to request funds from Ambassador Treasury Decision - Each month Ambassador role gets fixed percent (17%) AGIX from Ambassador Treasury that is distributed between the members. Questions - Should the Ambassador rewards be distributed at the start of the month or end? Insight - There are currently 11 ambassadors in the Ambassador program Insight - There is no defined way how to become Ambassador in Ambassador Program Insight - for the next 3 months Ambassador Treasury limits treasury spending to 57,000 AGIX per month
Description - Guiding activities to audit fund requests Decision - Before each bundle transaction, Treasury Guild checks for reward blocks in the 'Ambassadors Only' channel. Decision - With the consent of 3 Ambassadors or Workgroup Leads, a fund request can be blocked. Decision - Saturday, Sunday and Monday fund requests that are over 500$ are not rewarded in the first following distribution meeting. Decision - There has to be proof of requirements and deliverables where the fund request is over $100. Decision - a fund request has to be created by Ambassador or Workgroup Lead. Decision - At least 6 different Ambassadors or Workgroup Leads need to approve fund requests over $500. Insight - Reward block is state where we should wait or discuss before we distribute the rewards that are blocked.
Ambassadors prepare to vote for decisions and rules.
Rojo, Felix, Cran
Jan Horlings, Rafael Presa, Peter Elfink, Curtis Myers (DCypher), Kenric Nelson & William Thistleton (Photrek), Ubio Obu (Facilitators Collective), Tommy Frey (SNET Ambassador), Guillermo.
announcement of DeepFunding round 3 in 2 weeks from now
announcement of new engagements at DeepFunding through different review activities:
Proposal Review by previously awarded proposers
Proposal Eligibility review by DeepFunding Community
Awarded Proposer Milestone review by DeepFunding Community
where present participants seem pretty aligned that such initiatives would be indeed helpful and could bring strong benefits.
This was the last DeepFunding Town Hall funded by DeepFunding at Round 2. Wrapping up the proposal now and preparing a close out report.
2.5 hrs
Rojo [facilitator] [Documenter], Agus, SucrenSpice, Lilycupcake.
Discussed workgroup progress (projects, social media,…)
Discussed Agus’ work on social media management
Discussed Lily’s progress on the onboarding video and decided to put it up for a vote by tomorrow morning (Sat 30th June).
Discussed making a new video about using Dework, for onboarding purposes.
Discussed making the weekly meetings a bit later to accommodate other workgroup members.
[decision] Make new video for Onboarding. [decision] Make new video about using Dework
[action] Put Lilycupcake's Onboarding video up for a vote by Sat 30th June
No summary given
Description - How should we plan our recharging time? Decision - Use a calendar to identify breaks, and treat the calendar as a coordination tool Action - If you want to coordinate your recharge or busy times when you are not able to facilitate sessions, include your time on Miro Board calendar Insight - Calendar location Insight - we don't need to stop program its opportunity to change workshop leads
Description - migrate Miro Board from Swarm Account to SingularityNET Ambassador Account Decision - The All Meetings board will be discontinued Decision - Each workgroup and guild can be listed as separate board under Miro Map Decision - All Boards are with edit access Insight - Favorite the main Miro Board for easier navigation
Prepare the PBL Lesson draft for sharing in the next meeting. Most of the background knowledge can be found in Dework GitBook: Recreating Zoom link (be aware of the change)
Goal and/or Action Items: Continue discussion on Q3 Budget 30min prior to next Treasury Guild meeting on 29th June. Brief Summary: We started the meeting with headelf providing an overview on last week's discussion which included the overview of the Simplified Q3 Budget DeWork Template for Fund Requests: We outlined Pros, Cons, Thoughts & Ideas via Miro (see images below)
WG Leads Draft: "The outlined text is not theoretical, rather looking back and simply identifies and formulates already existing knowledge, work and responsibilities which emerged though the previous months…. So, this document is more of an observation than a proposal as it does not introduce anything new to already observable items !"
see
Description - Services and Tools where we allocate a minimum amount of resources each month Decision - Tooling costs will be asked through Fund Request Decision - Tag the Fund Request with the label 'Tool Sub' (Tool Subscription) Insight - You can read about Fund Request here:
