# Week 32

{% embed url="<https://github.com/orgs/SingularityNET-Archive/projects/1/views/3?itemId=35070391&pane=issue>" %}

## Monday 31st July 2023 <a href="#docs-internal-guid-565643b2-7fff-f227-7377-f80e405da06c" id="docs-internal-guid-565643b2-7fff-f227-7377-f80e405da06c"></a>

### Education Guild

## Tuesday 1st August 2023

### Governance WorkGroup

### Ambassador Town Hall

### Process Guild

## Wednesday 2nd August 2023

### <mark style="color:green;">Archives Workgroup</mark>

Not this week

### <mark style="color:green;">Dework PBL Workgroup</mark>

#### **Meeting Summary** **Context:**

This Workgroup focuses on creating educational project-based learning material for Dework on the Andamio platform in collaboration with Gimbalabs and Governance Guild.

#### **Meeting notes:**

<https://miro.com/app/board/uXjVM7pbrUg=/?moveToWidget=3458764559745101280&cot=10>

#### **Agenda Items**

#### **1) Review and get the lessons in the right format**

**Description** - We looked at all our lessons and identified improvements\
\&#xNAN;**\[Action]** - Refine our current lessons and turn them into markdown\
**Insight** - To turn into markdown, copy all text and pictures in PBL Google Docs and paste in <https://stackedit.io/app>\
**Learning** - stackedit.io will turn the pictures into working links.

#### **2) Checking the structure of BBK Lessons**

**Description** - We looked at current structure and updated Miro board\
\&#xNAN;**\[Action]** - Peter will do PBL Module on Permissions

#### **3) Feedback Forms**

**Description** - We discussed feedback forms for the PBLs\
**Insight** - Having feedback forms for each lesson and a general form for whole course can be useful\
\&#xNAN;**\[Decision]** - Completing feedback forms should not be mandatory.

#### **Next elegant steps** (general action items)

Refine our lessons and turn them into markdown.

### Process Modelling Workgroup

### Incubation Workgroup and Strategy Guild

## Thursday 3rd August 2023

### <mark style="color:green;">Onboarding Workgroup</mark>

#### Present: <a href="#docs-internal-guid-41a2aff8-7fff-de35-b10d-754eb5484212" id="docs-internal-guid-41a2aff8-7fff-de35-b10d-754eb5484212"></a>

Sucre \[facilitator], Peter, Tommy, Kenichi, Vani \[documenter]

#### Miro Board

See <https://miro.com/app/board/uXjVM5jyehQ=/?moveToWidget=3458764560782272677&cot=14>

#### Agenda

#### **1) Go through Action items from last meeting**

**\[ACTION]** Vani and Sucre to tweak the email and then post a new version in Discord for comments **(done)**\
\&#xNAN;**\[ACTION]** Vani and Sucre to include a suggestion on how to phrase what the process is to be formally accepted as an Ambassador in the new draft of the Onboarding email. All to comment.\
\&#xNAN;**\[ACTION]** Once the new Onboarding email text is agreed, Peter will share his list of 300-ish people with Sucre so they can be contacted. **(done)**\
\&#xNAN;**\[ACTION]** when emails go out, they will be BCCd\
\&#xNAN;**\[ACTION]** Name of the “Ambassadors Only” meeting changed on calendar to “leadership session”, for clarity **(done)**\
\&#xNAN;**\[ACTION]** We will give a heads-up to WG and Guild leads that new prospective Ambassadors might attend their meetings, and they should be welcomed.\
\&#xNAN;**\[ACTION]** Sucre, Ash and Vani will continue to do 1-2-1 contacts\
\&#xNAN;**\[ACTION]** We will meet again on 3rd August and see how it feels to meet weekly **(done)**\
\&#xNAN;**\[ACTION]** Vani to liaise with Tevo re access to account to be able to start meetings **(done)**

#### 2) Onboarding email - ready to send?

Yes, except for\
1\) adding a link to Instagram at the end\
2\) wording the “You applied a while ago” line at the start, so we can add it to those for whom it’s relevant\
3\) sorting out the Dework task about sign up to Dework and adding a wallet - it shouldn’t ask people to DM Felix, etc\
\&#xNAN;**\[ACTION]** Sucre (and Vani if needed) to fix these things then it can go out

#### 3) One-to-one contacting - how’s it going?

Not enough time to discuss

#### 4) Ensuring new people get a warm welcome

* Was mentioned last meeting that new people are not always feeling welcomed.
* Part of it could be fear that someone unknown who turns up in a Zoom meeting is a spammer. Should we circulate a list of the Zoom names of new people, so WG leads can keep an eye out for them?
* Or do WG leads need a bit of training or ideas on how to welcome new people? (e.g. saying Hi rather than just ignoring)

### <mark style="color:green;">Treasury Guild</mark>

#### **Meeting Summary** **Context:**

How to structure Ambassador rules around payments, tasks and anything related to financial activities.

#### **Meeting notes:**

<https://miro.com/app/board/uXjVM7pbrKE=/?moveToWidget=3458764559872563238&cot=10>

#### **Agenda Items**

#### **1) Collecting wallets during onboarding**

**Description** - We need an alternative to people sending wallets to Felix\
\&#xNAN;**\[Decision]** - We will use Google form in "My first Bounty" task\
\&#xNAN;**\[Action]** - Google form needs to be added to task

#### **2) No Gimbal tokens for tasks without task points**

**Description** - Informed Ambassadors in the call that no gimbals will be allocated to tasks without task points\
**Insight** - There are tasks that don't need gimbals, like monthly subscriptions

#### **3) Better reporting on monthly budgets**

**Description** - We need better reporting on how the budget is spent each month.\
**Insight** - Upgrading the treasury dashboard can solve this problem.

#### **Next elegant steps** (general action items)

\[Action] Implement the google form for wallet collection\
\[Action] Start work on the Treasury Dashboard

### AI Sandbox

### Deepfunding Town Hall

No summary provided

## Friday 4th August 2023

### Video Workgroup

No summary given

***

### Writers' Workgroup

#### Present: <a href="#docs-internal-guid-0a894e1c-7fff-a7ec-7ad7-5c9899613088" id="docs-internal-guid-0a894e1c-7fff-a7ec-7ad7-5c9899613088"></a>

Kenichi \[facilitator] \[workgroup lead], Slate \[documenter], Devon, Mikasa

#### Agenda <a href="#docs-internal-guid-0a894e1c-7fff-a7ec-7ad7-5c9899613088" id="docs-internal-guid-0a894e1c-7fff-a7ec-7ad7-5c9899613088"></a>

<https://docs.google.com/document/d/1zJa0d-aV91WaGoBRgF4G-HKEuAdWpvLzoxGPJsiAWGw/edit?usp=sharing>

#### Summary:

The meeting commenced with introducing a new member, Devon, who was guided through the copy-editing test to join the writers' team.

Kenichi introduced the use of Substack for creating individual portfolios, and Medium for community-based publishing under the name of SingularityNet.

#### Key Decisions and Discussions:

**\[decision]** Consistent Deadlines: The workgroup decided to set consistent deadlines for article publication and Twitter threads.\
\&#xNAN;**\[decision]** Article Backlog: The team currently has at least 5 articles pending publication, ensuring that content is available even during holidays or periods of reduced writing activity.\
\&#xNAN;**\[decision]** Generating Ideas: The group will brainstorm articles and thread ideas during SingularityNet town halls on Tuesdays.\
\&#xNAN;**\[decision]** Incentives: The workgroup agreed to incentivize participation and contributions to the meetings, to value the time and effort of the participants.\
\&#xNAN;**\[decision]** Review Process: The team will review articles together and make comments before publishing.\
\&#xNAN;**\[decision]** Publication Timing: Articles will be published on Fridays after the meeting when everyone has reviewed them.\
\&#xNAN;**\[decision]** Reward for Scribbler Role: Kenichi proposed rewarding the scribbler role for joining calls and contributing, and all participants agreed to this.\
\&#xNAN;**\[decision]** Meeting Incentives: A rate of 10 USD per hour for meeting calls will be offered as an incentive for participants.\
\&#xNAN;**\[decision]** Documentation task recognition: Slate's previous week's meeting summary will be rewarded as a recurring task on Dework.\
\&#xNAN;**\[decision]** Contribution System: The workgroup will discuss implementing a contribution system to evaluate individual contributions during the next meeting.\
\&#xNAN;**\[decision]** Urgent Tasks: A system for urgent tasks on Dework, with delivery within 24 hours, was proposed.\
\&#xNAN;**\[decision]** Recurring Tasks: The team plans to assign individuals to recurring tasks for 2-3 weeks, which may include tasks related to milestone publications and ecosystem updates.\
\&#xNAN;**\[decision]** Educational Series: The "AI and Beyond" educational series was proposed, and a graphic with title "Ai and Beyond Educational Series" will be used.\
\&#xNAN;**\[decision]** Mindplex Articles: Slate's article on "Synthesis of Art and Altruism" will be the second article on Mindplex, while the first article will cover "Introduction to the Ambassador Program."

#### Progress Update:

Kenichi reviewed the progress made on the Mindplex Episode 11 article.

#### Next Steps:

The next meeting will focus on

* finalizing the contribution system and
* discussing *AI and Beyond* tasks.

#### Action Items:

* Finalize the contribution system for evaluation in the next meeting.
* Create *AI and Beyond* tasks on Dework for review in the following week.
* Complete and publish "*Introduction to the Ambassador Program*" as the first Mindplex article.
* Complete and publish Slate's article on "*Synthesis of Art and Altruism*."
* Review the progress of Mindplex Episode 11 article.
* Brainstorm article and thread ideas during SingularityNet townhalls on Tuesdays.

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2023/august-2023/week-32.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.