> For the complete documentation index, see [llms.txt](https://snet-ambassadors.gitbook.io/singularitynet-archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snet-ambassadors.gitbook.io/singularitynet-archive/timeline/2022/october-2022/week-42.md).
# Week 42
## Tuesday 11th October 2022
### Ambassador Town Hall
* **Type of meeting:** Weekly
* **Present:** PeterE \[**facilitator**], Jenn \[**documenter**], Tevo, Felix, Julien Collins, Raido, Iain, PeterE, Sucre n Spice
* **Purpose:** Community Ambassador Townhall Meeting: Workgroup Progress - Process and Podcast, Tasks and Rewards Update, also Open Topic/Ideas
* **Town Hall Number:** 21
* **Working Docs:**
* [Miro Board Notes](https://miro.com/app/board/uXjVPQp07_o=/)
#### Slides:
{% embed url="" %}
#### Town Hall Summary:
The meeting is focused on discussing the progress of different work groups and guild, such as:
Process Guild is working on a document that outlines the translation process, including interview questions, reward levels, and automatic calculators for translation tests. They are also considering how to account for fluctuations in the value of the AGIX token when assigning rewards.
Treasury Guild discussing how to spend the project's budget and determine how rewards will be distributed for different tasks. Members or anyone interested in this guild will meet bi-weekly or monthly, as needed.
Podcast WG Creating a podcast called "Stories from the Singularity." They are currently working on interviewing Gabriel Axel Montes and finalizing the design for the podcast's logo and banner.
An important discussion point in this meeting is how to handle fees associated with managing the project's budget. There is a consensus that project members should not be responsible for covering these fees out of pocket.
#### Keywords/tags:
* **topics covered:** Rewards, workgroup updates, Documentation, Process Guild, treasury guild operations, Podcast WG, The Gabriel Axel Montes interview episode
* **emotions:** participatory, Friendly
## Wednesday 12th October 2022
### Deep Funding Town Hall
* **Type of meeting:** Biweekly
* **Present:** Jan Horlings \[**facilitator**], Jenn \[**documenter**], Jan Horlings, Kevin Chen, Tevo, Felix, PeterE
* **Purpose:** Discussion of Deep Funding R2
* **Working Docs:**
#### Timestamped video:
{% embed url="" %}
Deep Funding | Community Governance Proposals - October 12h, 2022
In this recorded Community Governance call, proposers of the current governance experiment were invited to present their proposals and receive feedback from the community.
[00:00-06:02](https://www.youtube.com/watch?v=3O7-448dAOk\&t=2s) Kevin Chen Intro To His Proposal [06:03-10:38](https://www.youtube.com/watch?v=3O7-448dAOk\&t=21818s) Adding Existing Services To The Portal [10:39-1:19:00](https://www.youtube.com/watch?v=3O7-448dAOk\&t=0s) Voter Eligibility
#### Town Hall Summary:
Kevin Chen presenting two governance proposals regarding SingularityNET's platform integration support for deep funding projects and voter eligibility in funding rounds. Important points are
Platform Integration Support Proposal: Kevin proposes offering support for integrating deep funding projects into the SingularityNET Marketplace. He highlights concerns about the complexity of current integration processes and suggests creating support networks or expert groups to assist with seamless deployment. Discussion expands to potentially involving the community in onboarding processes, aligning with another proposal from Peter.
Voter Eligibility Proposal: Kevin raises questions about voter eligibility in funding rounds, particularly whether proposers should be allowed to vote for their own projects. Concerns are discussed regarding the fairness and potential biases when proposers vote for their own projects. Suggestions include tracking voting behavior to identify and possibly discount or weight votes based on historical patterns or community engagement levels. Community
Engagement and Reputation Systems: There's a proposal to link voting weight with community engagement on the platform. Ideas include rewarding active engagement with higher voting weights and possibly integrating reputation systems visible on user profiles to encourage constructive participation. The discussion touches on potential issues like manipulation of votes and the need for mechanisms to adjust and reset such systems over time.
Long-Term Governance Considerations: Participants emphasize the importance of designing governance systems that can evolve and adapt over time without becoming locked into problematic structures. There's a preference for systems that allow adjustments based on community behavior and feedback rather than rigid rules.
In summary, the conversation delves into improving platform accessibility for deep funding projects, ensuring fair voting practices, and exploring ways to integrate community engagement and reputation into governance processes. The focus is on flexibility, transparency, and community involvement in shaping SingularityNET's governance framework.
#### Keywords/tags:
* **topics covered:** Proposal, Deepfunding proposal platform, DeepFunding R2, potential issues, Platform Integration Support, Voter Eligibility, Engagement and Reputation Systems, mechanisms, Governance
* **emotions:** Thoughtful
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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/2022/october-2022/week-42.md?ask=
```
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.