Week 28

Mon 8th Jul - Sun 14th Jul 2024

Monday 8th July 2024

AI Ethics WG

Narrative:

Fill in your usernames for Github and Discord on AI Ethics Workgroup TAG username list spreadsheet

Peter has created an AI Ethics Forum for open discussion, in the General area. To be heavily moderated with notice at top saying only AI Ethics Discussions -no other conversations. Moderators TBD but Clement was interested

Q3 Workgoup Admin Roles - Duke declined "co-chair mentee" position and passed role to Colleen Clement did not receive any comments in spreadsheet nor this meeting

Roles confirmed as:

  • Co-chair GEI: Vani

  • Co-chair role mentee: Colleen

  • Reportbacks to GEI meetings: Jenn

  • WG Async work support: LadyTempestt

  • Internal WG management: Sucre

Now that Sucre is confirmed as internal WG manager, she will be prepping agendas and facilitating meetings, not Vani

AGI2024: Budget will not allow for many people to be funded for travel to the conference - TBD- LeeLoo will find out more

Q3 Budget fitting - (need to lose c. $1500, exact amount TBC) - halving the number of community interviews or moving some to Q4; "producing resources to demystify AI terminology" could be moved to Q4 as well

Informal AI Ethic Chats with a least 2 people and data involved - put ideas on "AI Ethics WG Stuff!" spreadsheet

We are changing task tracking from Dework to Github - see project board here https://github.com/orgs/SingularityNet-Ambassador-Program/projects/1/views/2 Please add both your usernames for Discord and Github to AI Ethics WG tag and username list, to be invited to GitHub organisation and be able to be assigned to tasks. Some invitations have already gone out - check your email.

Changing this meeting time to 14 UTC (this was agreed last meeting, but Vani forgot!)

Which Ambassadors will be funded for travel to AGI2024 in August - Budget concerns

Ambassador travel needs to be decided on earlier in the year - how early? 6 months?

Those working on Strategy drafting Teams (writing and editing groups) should ideally create Discord private chat groups to progress their work and liaise. LadyTempestt will offer support as needed.

Decision Items:

  • New AI Ethics Forum has been created

    • [rationale] Note at top of channel saying AI Ethics discussions only, all other conversation will be deleted

    • [effect] mayAffectOtherPeople

  • Fewer people than originally thought will go to AGI2024 due to budget restrictions. Travel to any future AI Conferences needs to be decided farther ahead in the future

    • [rationale] to allow people time to get visas if needed

    • [effect] mayAffectOtherPeople

  • Budget fitting cuts will likely include the item for creating learning resources, and halving the number of interviews to be done with the public

    • [rationale] More interviews can be done in Q4; and we could move learning resources to Q4 because then we'll have a better idea of what kinds of resources might be needed

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Moderators of AI Ethics Forum - Clement, and others TBC if needed. Roles might need to be assigned - Peter? [assignee] Clement Umoh, Peter [due] 14 July 2024 [status] in progress

  • [action] Vani to create recurring meeting invite at 1400 UTC fortnightly on Mondays - Peter to add to Ambassadors Calendar [assignee] CallyFromAuron, Peter [due] 14 July 2024 [status] todo

  • [action] Create Discord DM goups for strategy writing and editing groups and invite LadyTempestt as well [assignee] all [due] 9 July 2024 [status] in progress

  • [action] all to add ideas to AI Ethics Workgroup Stuff spreadsheet for "AI conversations" work, to be discussed next meeting [assignee] all [due] 22 July 2024 [status] todo

  • [action] all to add GitHub names to AI Ethics WG tag and username list, or DM to Vani or Sucre, asap [assignee] all [due] 15 July 2024 [status] in progress

Keywords/tags:

  • topics covered: workgroup tags, forum moderators, Admin Roles, change meeting time, Budget cuts, AGI conference attendees, forum, visa, Q3 budget, AI Ethics conversations, learning resources, GitHub

  • emotions: friendly , informative, calm, engaging, Collaborative

Strategy Guild

Narrative:

The meeting began late as few minutes was given to allow for others to join the call. The team discussed on the outcome of the last conseting round and how best to proceed with the group's budget request.

Ayo clarified the distinction between weekly meetings, research, and workshops in the budget.

Discussion Points:

  1. How were concerns raised addressed?

  2. What areas of the budget should be updated?

  3. Lessons learnt from the 2nd iteration

Decision Items:

  • Highlight how concerns were addressed in the new budget in a document

    • [rationale] It would help better inform the consenting process

    • [effect] affectsOnlyThisWorkgroup

  • The budget should be updated to reflect the discussions in today's meeting

    • [effect] affectsOnlyThisWorkgroup

  • Resolution for concerns raised from last iteration should be added to a budget in a separate sheet

    • [rationale] This would help better inform the consenting process especially for those who raised the concerns

  • Only the dollar figure should be submitted in the budget

    • [rationale] AGIX price always change

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Add additional sheet for the resolved concerns raised in last iteration [assignee] Effiom [due] 9 July 2024 [status] done

  • [action] Work on updating the budget async [assignee] Ayo, Effiom [due] 9 July 2024 [status] done

  • [action] Re-upload the updated budget to the Ambassador Program budget planner [assignee] Ayo [due] 9 July 2024 [status] done

Keywords/tags:

  • topics covered: Budget Request, concerns, resolutions, Quarterly Budget Calculator, Quarterly Report

  • emotions: Collaborative, decisive, productive, The meeting was quick and progressive

Tuesday 9th July 2024

Governance Workgroup

Narrative:

We noted that we had planned to send out a 2nd round of consent forms already, but due to some miscommunication, they have not been sent out yet, which changes the proposed overall timeline.

About Writers WG and Marketing Guild, Kenichi explained that concerns raised in the last round of consent were about things that needed explanations rather than changes, so no new changes have been made to Writers' budget; so does it still need to go through another round of consent?

For Marketing, an outstanding objection (about the points system) was acknowledged by the objector as actually intended for Writers' WG, so Marketing seems to be resolved. Peter checked whether one of the other objections (that Marketing's budget had increased fourfold) was accurate - it wasn't.

Vani raised the issue of the low participation in the latest consent round (4 responses out of 53 core contributors) - is this level of response valid? Several people said we never agreed on a quorum, so we can't impose one now for this Quarter, but we should prioritise agreeing one for next time.

Reasons for low participation: Vani suggested perhaps people didn't realise there was another round - so if we do a 3rd round, we need to publicise it better. Kenichi said people seem to drop out of the consent process once their own WG has passed - so now that there's only a few WGs left, most people are no longer participating. We need to educate Core Contributors better on the process.

Some comments from the latest consent forms were accidentally not transferred to the Budget Planner spreadsheet. We noted that in future there should be a double check that all comments have been copied over.

Peter added one comment from the consent forms which had been accidentally omitted - about Marketing Guild and whether all the work in the Marketing budget had been adequately costed. Kenichi addressed it, and it was resolved, so it was agreed that Marketing Guild's budget has now passed.

But we noted there may still be some concerns in the consent forms for Strategy Guild that have not been transferred to the Budget Planner, or covered in the doc that Strategy Guild created to address the concerns raised about them. (https://docs.google.com/document/d/1e4s9TMi6zoi2RpGNIssNvppA1zTjpfsk-bnjqAfWfWc/edit?usp=sharing)

We noted that there have been significant changes to Strategy Guild’s budget since the last round of consent (a drop from $13k to $8k). In Strategy Guild's doc, concerns fall into 4 categories: 1) Budget amounts 2) The validity of what Strategy Guild aims to do 3) Deliverables 4) Miscellaneous/other. Ayo talked through the doc, and noted that some of the concerns are about the old Strategy Guild's backlog, and should perhaps be addressed by Treasury Guild and/or or Governance WG; and that the only concerns raised that have not been addressed in the doc are the ones which are not about the Q3 budget or Q2 quarterly report, but which speak to decentralisation and whether Strategy Guild should exist at all.

Tevo questioned whether some of the functions that Strategy Guild wants to do are already being done in other places such as Town Hall, Governance WG, and the WG Sync call; and whether replying to concerns via a "comments" doc like this is really addressing the issues holistically, or whether a new report should be drafted that takes account of and incorporates concerns.

Ayo addressed the question of overlap between different workgroups, and argued that it is often valid - groups might superficially appear to be overlapping, but are actually doing different things (he cited the examples of Onboarding WG vs the onboarding efforts that are carried out by different WGs individually; and the difference between Archives WG and Knowledge Base WG.) He noted that the way that the Program works is not to have one group tasked with doing everything around a particular category of work, but to have some types of work spread across several WGs who address them in different ways; and argued that this is valid. He said objections to Strategy Guild were based on a misunderstanding that the guild is attempting to strategise internally for individual WGs, when it's not.

However, Vani noted that while it's true that different WGs should be free to do things in their own ways even if they look superficially like overlap, the objections to Strategy Guild were not really about this. They were not saying that Strategy Guild is attempting to strategise for individual WGs; they were questioning Strategy Guild's attempts to strategise for the program as a whole, as opposed to this being done by a coalition of all the WGs together.

We also noted that although Stragegy Guild has discussed and addressed objections, this doesn't meant they are actually resolved, if the objectors haven't yet withdrawn their objections. So given that what Strategy is presenting now is significantly different from what people consented/unconsented to last time, several people felt there should be a new round of consent.

Tevo suggested an ultra-low-budget, step-by-step approach for Strategy Guild, building up to a bigger budget next Quarter if trust is built up. He pointed out that when the Ambassador Program started, people did what Strategy Guild are proposing to do, but with much less money; and that given there are objections from several people, the guild might be missing something.

Guillermo raised a query on the $6,790 that is still in Strategy Guild's reserves from previous quarters; Ayo said that we should ask Treasury if Strategy Guild can use it, which would lower the amount they need to ask for in this Quarter's budget. Guillermo also noted some issues that have been raised (some people think Strategy Guild didn't work in its previous iteration; that strategy might be something we should all work on together; and that others have done similar kinds of research work for much less money). Ayo said that people are only objecting because they don't yet understand what Strategy Guild wants to do; and that the past iteration of Strategy Guild shouldn't be raised as an objection on this budget.

Peter summed up that there are clearly questions around the relevance and need for Strategy Guild; whether some of its budget items are needed; and whether it's aiming to do things that are actually just the Core Contributor role; so to minimise risk, he feels Strategy Guild should start with a much smaller budget, and see what happens.

Although it was almost the end of the meeting and people were beginning to leave, Tevo quickly created a Zoom poll to ask what would be an appropriate level for Strategy Guild's budget; 3 people (who cannot have been Peter, Tevo, or Vani, who had already left) voted, and all said "under 3,000 AGIX". So this suggests it's not just one or two people who have concerns.

Ayo said that Strategy Guild could amend its budget in response to comments by tomorrow; and then a new consent form can go out. But after he left the call, Tevo and Peter said that perhaps this is not the best way to address the issues, and it should instead be discussed in the Open Governance meeting on Thurs. So there was no definite agreement on next steps; it will be decided async.

Kenichi noted that Writers WG reduced its budget last week (and the changes have not yet been discussed), and hasn't made any further changes since. So rather than another consent form, the changes should be discussed to confirm whether they address the concerns raised. Tevo pointed out that the issues for Writers were also about their quarterly reporting, not just their budget; and there was some discussion of Writers' doc addressing the concerns raised.

There was a concern raised in general terms about how long it takes for an objector to read through the answers and additional docs, and whether people can find the info that addresses their concerns.

So the final decision was to discuss Strategy Guild further in Thursday's Open Governsance call; and to create an send out a new consent form for Writers' WG

Discussion Points:

  • Set-up of consent forms

  • Workgroup budgets that are still pending approval (Marketing, Writers, Strategy)

  • Low participation in consent rounds, the need for better awareness/publicity, possibility of a quorum

Decision Items:

  • Marketing Guild's budget has passed

    • [rationale] the concerns raised in the last consent round have been addressed, and the objectors have said they are satisfied.

    • [effect] mayAffectOtherPeople

  • Further discussion will be had, particularly of Strategy Guild, on the Open Governance Call on Thurs July 11, 2024.

    • [effect] mayAffectOtherPeople

  • Writers Workgroup and possibly Strategy Guild (if not resolved on Thurs 11th) will go through a new round of consent, to close on July 15, 2024.

    • [effect] mayAffectOtherPeople

  • We will look at the idea of agreeing a quorum for participation in the consent process next quarter

    • [rationale] because participation in the latest consent round has been low.

    • [effect] mayAffectOtherPeople

  • We will try to improve Core Contributors' understanding of the process, and their awareness of the need to participate beyond just the first round.

    • [rationale] because participation seems to drop off after the first round of consent.

    • [effect] mayAffectOtherPeople

  • In future Quarters, there should be a double check that all comments have been copied over from the consent form to the busdget planner spreadsheet

    • [rationale] because some were missed this time, which means they do not get addressed.

    • [effect] mayAffectOtherPeople

  • In future, we may need to address how easy /hard it is for an objector to see how their objection has been addressed, and see if the consent process or the publicity can be adjusted to make it clearer.

    • [rationale] Because sometimes, the material where a concern is addressed can be buried in a long doc and might be hard to find.

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Strategy Guild will amend its budget [assignee] Ayo [due] 10 July 2024 [status] todo

  • [action] Treasury Guild will prepare new consent forms for Writers WG and Strategy Guild [assignee] Tevo [due] 14 July 2024 [status] done

Keywords/tags:

  • topics covered: deadlines, community engagement, Budget , Quarterly Report, Strategy Guild, Marketing Guild, Quorum, Core Contributor, Budget Approvals, Decentralization, q2 2024 quarterly report, q3 2024 budget, consent decision making, consent process, consent form, Overlapping projects, work overlap, validity of strategy guild, validity

  • emotions: critical, analytical, chatty, shouty, aggressive in parts, inconclusive

Wednesday 10th July 2024

Education Workgroup

  • Type of meeting: Weekly

  • Present: Slate [facilitator], Slate [documenter], Clement Umoh, kateri, osmium, WaKa, malik, Slate, Photogee, Kenichi, Mikasa, GorgaSeagian, sakujennbornean, Franklynstein

  • Purpose: - Tasks Update go through dework - Review sheet post productions and rework showcase - Ai for beginners and Learn about Decentralized AI merge ? - Clement's infographic showcase - Gorga's proposal - Fetch and Ocean resources start off

In this meeting we discussed:

  • Tasks Update go through Dework

  • Review sheet post productions and rework showcase

  • Ai for beginners and Learn about Decentralized AI merge ?

  • Clement's infographic showcase

  • Gorga's proposal

  • Fetch and Ocean Task distribution

Discussion Points:

  • Slate started the meeting welcoming everybody

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

  • Slate mentioned that it was decided in the previous meeting that Ese will be taking up the intiial document for Ai for Beginners

  • There was a discussion regarding merging of "AI for Beginners" and "Understanding Decentralized Ai" into one single project as "Ai for beginners"

  • SNET reworked infographic was discussed

  • Kenichi was advised to bring up the initial document for his project "webinar series"

  • Osmium said that we dont currently need any rework for Awakening Health video

  • Osmium and Photogee will be discussing whether a rework of that video is needed or not

  • Gorga shared his proposal of making a website wiki for SNET and Ambassador Program and everybody liked the idea

  • Fetch and Ocean infographics are assigned and the work on it had started concluding from the discussion on it in todays meeting

  • There was also a discussion for a landing page for ACP/ CCCP

Decision Items:

  • Osmium and Waka to take up Fetch infographic

    • [rationale] Diverse knowledge regarding the project

    • [opposing] Nil

    • [effect] affectsOnlyThisWorkgroup

  • Malik and Gorga to take up Ocean Infographic

    • [rationale] Able to deliever fast and research properly

    • [opposing] nil

    • [effect] affectsOnlyThisWorkgroup

  • Kenichi to be making initial document for his project under education "presentation series"

    • [rationale] project is proposed by kenichi

    • [opposing] nil

    • [effect] affectsOnlyThisWorkgroup

  • Merge "Understanding Decentralized AI" & "Ai for beginners "

    • [rationale] Everybody agreed

    • [opposing] Nil

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Assign tasks for Fetch and Ocean infographic and Kenichi's initial document [assignee] Slate [due] 11 July 2024 [status] done

  • [action] Find out the budget amount after cut and fit accordingly [assignee] Slate [due] 17 July 2024 [status] in progress

Keywords/tags:

  • topics covered: fetch and ocean, task rework assignment, review team, Blueprint documents, Rework discussions, budget discussion, projects merger, Ai for Beginners, infographics, ACP, landing page, Wiki

  • emotions: productive, Collaborative, Businesslike.

Archives Workgroup

Decision Items:

  • OpenSource paradigm presentation See https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/164 - TBD next meeting (24th July) how the work will be presented

    • [rationale] The wish to engage more people with the issues around Open Source culture and ethos

    • [effect] mayAffectOtherPeople

  • Governance WG paying Ese to upload their backlog of summaries to the Tool: Vani has messaged Felix to ask him to create a Dework task for it

    • [rationale] Gov WG has budget to cover this, and they have summaries written and ready to upload, so Dework task is needed since they manage their budget on Dework

    • [effect] mayAffectOtherPeople

  • André demo'd the new Docs Management tool https://snet-doc-manager.netlify.app/#

    • [rationale] explaining how we will manage and open-source docs submitted in meeting summaries

  • As planned, André has created a doc ("New Summary Tool Features") collating ideas for the redesign of the summary tool. People who work with the community on using the tool (e.g. Vani, Onyeka) to add any issues they hear about (especially because, due to budget fitting, we might not be able to afford to do as much organised community engagement around this as we would have liked).

    • [rationale] To start organising ideas for changes and hearing from the community, without necessarily doing direct engagement work.

    • [effect] affectsOnlyThisWorkgroup

  • RE video walkthru of how to use the GitHub Board - see https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/116 Duke has reassigned it to Ayo, but we agreed there are a few issues with Ayo's first draft - may need an edit. We agreed Vani will DM Ayo.

    • [rationale] Mainly that it is a bit generic, rather than focusing on how we in this WG use our GitHub board; and that the voiceover doesn't explain sufficiently what's being done

    • [effect] mayAffectOtherPeople

  • The work on the Archives Backlog - some people have had to do more work than others for the same pay, as the month they were working on had more meetings to cover. After discussion both in the meeting and earlier in the Discord chat for the group who are working on it, we agreed to keep the money allocation as it is, even though it's not ideal and somewhat unfair; but for future tasks we'll bear this kind of issue in mind and allocate it better from the start

    • [rationale] Because working it out per meeting uploaded would be a disproportionate amount of work

    • [opposing] There were suggestions to try and work it out differently, but people decided it was easiest to leave it as it is.

    • [effect] affectsOnlyThisWorkgroup

  • We agreed that for the "Good Meeting Summaries" task in Q3, Sucre, Clement and Onyeka will continue as the judging team

    • [rationale] For continuity, as they've just established how to run the competition smoothly. Maybe hand over next quarter if we continue with the competition in Q4.

    • [effect] mayAffectOtherPeople

  • Holiday: We agreed that we will meet on 24th August as planned, but then will not meet in August (meeting dates would have been 7th and 21st Aug). So we return on 4th Sept.

    • [rationale] Because several people are away for parts of August, so easiest approach is to take a break.

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Video walkthru of how to use the GitHub Board - see https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/116 - reassigned to Ayo [assignee] Ayo [due] 24 July 2024 [status] in progress

  • [action] All to add comments to AI ethics doc async: it will only stay open for comments 2 more weeks, and will be reassessed next meeting (24th July) [assignee] all [due] 24 July 2024 [status] in progress

  • [action] Vanessa to write guide on how to make a doc community-owned - draft is in the issue here https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/148 and is open for comments to be discussed next meeting [assignee] Vanessa [due] 10 July 2024 [status] done

  • [action] Ekemini and Ese to liaise outside the meeting on Town Hall presentation on Ubio's work, and decide when to present. They can message André with any questions. See https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/150 [assignee] Ekemini Samuel, esewilliams, André [due] 10 July 2024 [status] in progress

  • [action] Ese, Onyeka and Ekemini to work on presentation on tag taxonomy work https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/151 - was presented at TH on 2nd July [assignee] Vanessa [due] 2 July 2024 [status] done

  • [action] André to ask Ubio if he can convert his Excel spreadsheet testing different LLM models into a more viewable format [assignee] Andre [due] 10 July 2024 [status] done

  • [action] Vani and André to meet to go thru André's docs management interface [assignee] CallyFromAuron, André [due] 10 July 2024 [status] done

  • [action] Stephen to tidy up the documentation of the Q2 RAG process, and close the issue https://github.com/SingularityNET-Archive/SingularityNET-Archive/issues/163 [assignee] Stephen [due] 10 July 2024 [status] done

  • [action] Stephen to decide how best to present the "Open-source paradigm" work: postponed to meeting on 24th July as Stephen not present today [assignee] Stephen [QADAO] [due] 24 July 2024 [status] in progress

  • [action] André to create a doc to collate issues that need to be addressed in the Q3 redesign of the meeting summary tool [assignee] André [due] 10 July 2024 [status] done

  • [action] Vani to post in the Discord chat for the backlog work that a) we have agreed to include the Deepfunding Community Governance meetings, and b) the deadline is 3rd July 2024 [assignee] CallyFromAuron [due] 28 June 2024 [status] done

  • [action] Onyeka will DM Peter to check there is space at TH for the Tag Taxonomy presentation on 2nd July [assignee] lord kizzy [due] 28 June 2024 [status] done

  • [action] Vani to create issues on the GitHub Board for all the forthcoming Q3 work, in time for meeti ng on 10th July - not done yet as we are still waiting for definite info on budget-lowering percentage. Postponed to 24th July [assignee] CallyFromAuron [due] 24 July 2024 [status] in progress

  • [action] Vani to DM Ayo about the GitHub Board walkthru video [assignee] CallyFromAuron [due] 24 July 2024 [status] todo

Keywords/tags:

  • topics covered: document management, github board, AI ethics, Ethics, good meeting summaries, LLMs, LLM development, AI tooling, open source, fair pay, payment, GitHub video walkthrough, meeting summary tool redesign, holiday, town hall presentations

  • emotions: Organised, inclusive, participatory, problem-solving

Research and Development Guild

Agenda Items:

  • Welcoming new members and Introduction

  • Review of last meeting summary Action Items

  • UPDATE Q3 BUDGET

  • UPDATE STATUS ON DEVELOPMENT TO FILL REPOS!

  • SHOWCASE FINISHED PROPOSAL

  • NEW OPERATIONS SYSTEM GOING FORWARD

Discussion Points:

  • Welcoming of new members: AJ introduced himself to the Guild.

  • ACTION ITEMS MEETING: Lordkizzy went through the action items from the previous meeting summary

  • SHOWCASE FINISHED PROPOSAL: We are trying to present deliverables on completed projects to the community. We weren't able to further discuss this because core members of respective projects weren't in attendance.

  • Q3 / Operations Objectives; DESIGN NEW OPERATIONS SYSTEM: Guillermo presented the outline document (https://docs.google.com/document/d/1AzG3_q3vOS0LoFXOjUrwyXu1OSv3qExPjiGYEYsaK44/edit?usp=sharing) for operations going forward but Waka had some blockers as to the process and questioned the "Overlapping between proposals with other guilds" concern presented by the community and the proposed solution to it and also the "Proposals must not receive funding from Ambassador and DF". Lordkizzy explain further on the process at which this new system will be implemented and the benefits of the system.

Action Items:

  • [action] Guilermo to ideate to see how Vasu can collaborate with guild members on project [assignee] Guillermo [due] 3 July 2024 [status] done

  • [action] Colleen to draft out a proposal for her initiative on The Quest for AI Game Design [assignee] Colleen [due] 3 July 2024 [status] done

  • [action] Kenichi to write a one page document addressing concerns about the overlapping proposals and collaboration with existing projects [assignee] Kenichi [due] 10 July 2024 [status] done

  • [action] Dan Watkins and advanceameayew to fill in the Onboarding Document and share that with the group [assignee] Advanceameyaw, Dan Watkins [due] 10 July 2024 [status] done

  • [action] Guillermo to have a discussion with Rojo and Kenichi on similarities between their projects and to see if there is a possibility for collaboration [assignee] Guillermo [due] 10 July 2024 [status] todo

  • [action] Guild to create a infographic to present the two completed projects to the community [assignee] Guild [due] 10 July 2024 [status] todo

  • [action] Guillermo and Lord kizzy to prepare the first draft of operations of the R&D Guild going forward [assignee] Guillermo, lord kizzy [due] 10 July 2024 [status] done

  • [action] Duke to prepare a short text to share with the community on the research project on disability inclusivity, and to invite them to the document to make comments, [assignee] Duke [due] 10 July 2024 [status] done

Keywords/tags:

  • topics covered: Guilds , Budget , Tool Development, Proposal, AI tooling, deliverables, Budget Request, Q2 budget, Budget preparation, contributors, Rewards, Overlapping projects, Operations

  • emotions: straightforward, questioning, speedy , Casual

  • other: Waka proposed an increase in allocation for Kenichi's legacy system if there is going to be a collaboration with Rojo

Knowledge Base Workgroup

Agenda item 1 - Knowledge Base Onboarding and Feedback - [carry over]

Discussion Points:

  • Should the new feedback be rewarded? https://docs.google.com/spreadsheets/d/1aepifawXPW_zG5Gd1jt1tveenZorS23mnhFrmuPbtJc/edit?resourcekey=&gid=1012113575#gid=1012113575

  • Should we reward for the same people who submitted multiple feedback but its different insight?

  • Has any update been done on the infographic?

Decision Items:

  • New feedback will be rewarded

    • [effect] mayAffectOtherPeople

  • We won't reward multiple feedback submissions from same person

    • [effect] mayAffectOtherPeople

Action Items:

  • [action] Create feedback Reward tasks [assignee] Tevo [status] todo

  • [action] Work on other color scheme for infographic [assignee] Onize [status] todo

  • [action] Update several infographic sections [assignee] Onize [status] todo

Agenda item 2 - Review Async Organizing Process Document - [carry over]

Discussion Points:

  • Google Doc: https://docs.google.com/document/d/1nhK0TK1pRYlHwzOI-nUe9olyGRWXZcTMuiRqtzfWrSw/edit#heading=h.1qoyee83j7c0

  • The strategy we use to Organise

  • How much experience do we expect from participants?

  • Steps to Async Process

  • Live Review Process

  • Rewards

  • Limits

Agenda item 3 - Review Administration and Dework Tasks - [resolved]

Discussion Points:

  • Currently Administration process is emerging and is related to Miro Board updates like color changes and Dework Updates to recognize rewards.

  • How do we identify items on the board for rewards?

  • Who should get double rewards from organizing?

  • How do we address organizers who were part of the legacy system?

Decision Items:

  • Double Ayo Organizing Rewards

    • [effect] affectsOnlyThisWorkgroup

  • Double Lord Kizzy Organizing Rewards

Action Items:

  • [action] Continue operational administration tasks to update status of items and associated rewards [assignee] Tevo [status] todo

Agenda item 4 - Reviewing Item Ambassador Program Analysis - Miro Board - [carry over]

Discussion Points:

  • Asset link: https://miro.com/app/board/uXjVM7pbrUY=/?moveToWidget=3458764557891618718&cot=14

  • It caused confusion about what part of the Miro Board should have been looked at.

Decision Items:

  • We removed the Item from Category Global Strategy under the section What is the Ambassador program?

    • [effect] affectsOnlyThisWorkgroup

  • We removed the item from the Identification Process under the section How do we identify new projects?

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Continue Reviewing the "Ambassador Program Analysis - Miro Board" Item in the next session [status] todo

Agenda item 5 - Analyze Live Review Process - [carry over]

Discussion Points:

  • What are the best practices for resolving conflicts?

  • How do you organize different assets and what do you look for?

  • More tags strengthen what has been organized or reviewed

  • Should the new emerging processes be added to the WG process doc?

Decision Items:

  • Invite people to add a Tag with their name to Items which locations they agree on

    • [effect] affectsOnlyThisWorkgroup

  • We clean the Organizing Resources window and add a new process to resolve conflict after a live review

    • [effect] affectsOnlyThisWorkgroup

  • We will try to manage cleaning with different teal colored sticky to move items to meeting summary by other organisers in the live meeting

    • [effect] affectsOnlyThisWorkgroup

  • We test new ideas before start documenting new changes

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Add extra context on how to review assets on the Miro board [status] todo

Agenda item 6 - Workgroup Planning - Summer Break - [carry over]

Discussion Points:

  • Should meetings be held during the summer break?

  • Activities of the WG going forward

Decision Items:

  • Ayo can help facilitate August Calls

  • Tevo takes break on 21.08

Keywords/tags:

  • topics covered: Onboarding, organizing, reviewing, conflicts, Rewards, Task Management, Summer break, workgroup,, newbie

  • emotions: Collaborative, decisive, lively

Thursday 11th July 2024

LatAm Guild

Agenda item 1 - Strategy Sub-Group - [carry over]

Narrative:

The speakers discussed the intersection of AI and governance, highlighting AI's potential to analyze data and help drafting strategies for sustainable development of the guild and the community. They also explored the importance of a reputation system, building a strong community, and building operations for decentralized communities. Speakers emphasized the need for a merit-based reputation system, task-based approach, and systematic approach to managing contributions and rewards. They also discussed the use of tokens for voting and decision-making in the context of SingularityNet's ambassadors program.

Action Items:

  • [action] Governance Blueprint Design Draft [assignee] Guillermo, Ines, Martin Rivero, Caue, Andrea Dekovic [due] 8 August 2024 [status] in progress

Agenda item 2 - Governance Sub-Group - [carry over]

Narrative:

In our discussions, we emphasized the critical importance of communication and collaboration in a remote work environment to ensure seamless interactions and productivity. We explored the potential of using AI for data analysis and intelligence, recognizing its value in making informed decisions. Facilitating documented work processes was highlighted as essential for maintaining clarity and consistency in our tasks. We also discussed the idea of using tokens or AGX to reward participants in on-chain governance, proposing a system where tokens could be used to vote on activities. Additionally, we addressed translation tasks and the associated rewards, aiming to create an inclusive and participatory framework for all team members.

Action Items:

  • [action] Governance Token Design [assignee] Guillermo, Caue, Martin Rivero [due] 24 July 2024 [status] todo

Agenda item 3 - Marketing Sub-Group - [carry over]

Narrative:

In our recent discussions, we outlined the draft concepts for a communication strategy targeting the four LATAM countries where we will begin our actions: Argentina, Mexico, Colombia, and Brazil. We defined the channels to use and assigned tasks for our next meeting, where we will develop our short-term objectives, particularly focusing on the upcoming ADN Event in Buenos Aires on July 31. Additionally, we planned for the participation of @SNET_Latam in the AGI-24 Round tables scheduled for August 7, ensuring that we are well-prepared to contribute to these significant discussions.

Action Items:

  • [action] Compile budget and communication actions proposals for ADN [assignee] Andrea Dekovic, Ines, Guillermo [due] 21 July 2024 [status] in progress

  • [action] Design Draft Proposal for topic of AGI-24 @SNET_Latam [assignee] Guillermo, Ines [status] todo

Agenda item 4 - Operations Sub-Group - [carry over]

Narrative:

In our discussions, we delved into the governance design for our global community, leading to an in-depth conversation on creating an inclusive and effective governance system. Guillermo explained the current governance framework, highlighting how contributions are rewarded and proposing a token-based system for community representation. We acknowledged the potential for power imbalances but focused on building a community where members are actively involved in decision-making through reputation systems and token incentives. Understanding the system's objectives and mechanisms was deemed crucial, and we emphasized that while newcomers are respected, tasks should be assigned based on merit. We also discussed using token-based systems to measure contributions and creativity within the ambassadors' global program, incentivizing new members through rewards for participation and engagement. Lastly, we outlined a plan to build a decentralized operations system using GitHub and Google Drive, ensuring transparency and collaboration.

Decision Items:

  • GitHub and Google Drive WorkShop

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] GitHub WorkShop [assignee] Guillermo, Caue [due] 24 July 2024 [status] todo

  • [action] Operations System Drive Setup [assignee] Guillermo [due] 17 July 2024 [status] todo

Keywords/tags:

  • topics covered: Rewards, Governance, Meeting Summaries, Onboarding, Budget, Roles, Collaboration, Translation, GitHub, governance design, inclusive, assigning tasks, merit, Google Drive

  • emotions: Collaborative, Friendly, Thoughtful , funny , entertaining, challenging

  • other: Step by Step

Onboarding Workgroup

In this meeting we discussed:

  • Minutes from the last meeting and action items; we agreed to the minutes of last meeting.

  • Onboarding Journeys update: Onize wasn't able to present the scripts in the meeting but there were also some discussions on the format we are going to use to if we are going to publicize the scripts (a video or rather infographics). Sucre will look at the budget to see which is feasible.

  • Skills Matrix: Vani wanted to know what are two skills we will to select to organize mentorship for Q3 in the group

  • Q3 budget: Since the total requested across all WGs is higher than the total available, budget-fitting will need to be implemented. The lowering percentage is yet to be determined since some workgroup budgets are yet to be approved, but we will get less than we asked for. Sucre is to take a look at the budget to see how we could prioritize activities.

  • Onboarders Team: Sucre explained the entire process (There is going be a new Discord channel and also note that new people get a Discord tag which will be removed once they become a Core contributor. Also the FAQ will be updated once the ASI migration is completed. See ONBOARDING document

  • Facilitation / Documentation Roster: There were some discussions around who the next facilitator and documenter was going to be. From the roster is going to be Duke facilitating and Lady Tempestt documenting and they both indicated that they would be up for it.

  • Gorga alleged that he had been passed over in the assignment of tasks such as documenting due to xenophobia, prejudice and favouritism, and that the workgroup's practices were untransparent. People in the meeting addressed and refuted these allegations in the Zoom chat - see doc "Onboarding meeting Chat, 27th June 2024 - Gorga"

  • August Break: Vani highlighted that many members of the ambassador program were going on a summer break and wanted to know if we would continue having meetings, she also proposed we could use some of the August sessions for skills training sessions. Lordkizzy indicated that we should try to see if those interested in the training session would be available during this period. We decided to continue the conversation in the next meeting.

  • Discussions on Gorga's accusations and comments on the Workgroup: we decided to for Sucre to reach out to Gorga and see if he would be available for the next meeting and then make further discussions on this.

Decision Items:

  • We agreed on Documentation as the first skill to organize mentorship for in Q3 and then GitHub Operations afterwards

    • [rationale] We had quite a large number for report writing but we noticed that no one has said in the skills matrix doc that they are interested in learning the skill. Since we plan to have a mentorship session next month for documentation we could just make that the first skill to learn.

    • [effect] affectsOnlyThisWorkgroup

  • We decided that Lady Tempestt will prepare and host the Mentorship session for Documentation, tho we are yet to set the date.

    • [rationale] She is skilled in Documentation

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Onize to bring onboarding journey scripts to the next meeting. [assignee] Onize [due] 18 July 2024 [status] in progress

  • [action] Lord Kizzy to prepare the facilitation and documentation roster for Q3 and present it in the WG channel. [assignee] lord kizzy [due] 4 July 2024 [status] done

  • [action] Sucre to present results on the selected team of Onboarders in the Onboarding WG channel. [assignee] Sucre n Spice [due] 4 July 2024 [status] done

  • [action] Sucre to work on editing the budget and present it to the next meeting. [assignee] Sucre n Spice [due] 18 July 2024 [status] in progress

  • [action] Lady Tempestt to share the Buddy system report document in the Ambassador General channel. [assignee] LadyTempestt [due] 18 July 2024 [status] todo

  • [action] Vanessa to find out where the information on "Other WGs and guilds may want to implement a Buddy system mechanism" was mentioned [assignee] CallyFromAuron [due] 18 July 2024 [status] todo

  • [action] Sucre to meet with Tevo and Demonix to see how the Onboarders process could be implemented on Discord [assignee] Sucren [due] 18 July 2024 [status] todo

  • [action] Sucre to try see where funds will be gotten for the Onboarding Journeys video [assignee] Sucre n Spice [due] 18 July 2024 [status] todo

  • [action] Sucre to reach out to Gorga and see if he will be available for the next meeting [assignee] Sucre n Spice [due] 18 July 2024 [status] todo

To carry over for next meeting:

  • Onboarding Journeys

  • Skillshare matrix and training session dates

  • Onboarders team

  • Q3 budget

  • Discussions on Gorga's allegations and comments on the Workgroup

  • Vacation

Keywords/tags:

  • topics covered: Getting Started, onboarding processes, buddy system, Quarterly Report, onboarders team, Facilitation, Documentation, skills matrix, allegation, gorga, Budget , Q3 budget, Onboarding Journey Scripts, Vacation

  • emotions: interesting, misunderstood, Casual, Well-attended

African Guild

  • Type of meeting: Weekly

  • Present: Duke [facilitator], esewilliams [documenter], Sucre n Spice, esewilliams, Isaac, Duke, Ayo, Photogee, AdvanceAmeyaw, Isaac Daniel

  • Purpose: Identify and touch base virtually with other AI/Web3 communities across Africa

  • Working Docs:

General Summary:

Clement Umoh raised concerns about the recurring scheduling conflicts and suggested finding a permanent solution to avoid wasting time. Duke proposed two options to address scheduling conflicts: complaining to Governance WG or changing the meeting time. These were put to a vote, with the group ultimately deciding to move the meeting to 5 p.m. on Thursdays.

The group discussed plans for the AI Ethics Expo in Nigeria, a collaboration between the AI Ethics Work Group and the African Guild. The event is projected for August or September, with a focus on securing a suitable venue and speakers, and a budget split between the two groups. It will be the group's first outreach initiative. Ese Williams questioned the roles of the four participants for the Expo, leading to a discussion on the implementation of proposed ideas and the need for volunteers to assist with the event. The conversation also addressed the selection process, potential locations for the event, and the possibility of covering travel expenses for participants.

The importance of the members' collective initiative was highlighted for generating ideas to drive the guild forward. The initiative aims to fund ideas from guild members to contribute to the guild's growth and achievement of KPIs.

Duke addressed the need to revise budgets due to pending budget approvals for Strategy, Marketing, and Writers. Budget cuts are expected; careful spending will be important this quarter, as the current budget lacks contingency provisions. The discussion also touched on the majority of the budget being allocated to recurring operational work.

Duke asked for feedback on the African Guild's progress, with Clement Umoh and Ese Williams expressing positive feedback and Ese suggesting improvements in organization and time management. Duke sought opinions on the pace of progress and the need for better coordination, and mentioned the possibility of giveaways for consistent meeting attendance.

Ese Williams expressed confusion about the AAG token and its legitimacy, prompting Clement Umoh to caution against engaging with it.

The discussion also included updates on uploading past meeting summaries and the need to ideate on strategies to increase African participation in the guild.

The meeting concluded with plans for future meetings and a reminder to communicate any scheduling conflicts.

Decision Items:

  • Should the meeting time be moved to a different day?

    • [effect] affectsOnlyThisWorkgroup

  • What is the feedback on the progress of the African Guild?

Action Items:

  • [action] Members will indicate their interest and specify the particular roles they are willing to take on for managing the volunteer workforce from the SingularityNet community. [assignee] All Members [status] in progress

  • [action] Duke Peter will revise the budget based on feedback from the Treasury [assignee] Duke [status] in progress

  • [action] Clement would go over his research work in the next meeting [assignee] Clement Umoh [status] todo

  • [action] Ese Williams would an update on the marketing guild initiatives members [assignee] esewilliams [status] in progress

  • [action] Duke Peter will provide updates on the African Guild AI Ethics Expo [assignee] Duke [status] todo

  • [action] Duke Peter will coordinate with Peter to move the meeting time by an hour [assignee] Duke [status] todo

Keywords/tags:

  • topics covered: African, African guild, Marketing initiative, AMA Session Updates, Q3 Budget Updates, change meeting time, documentation, meeting time, AI Ethics expo, progress, meeting summaries, Governance WG, members' collective, AAG token,

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

Friday 12th July 2024

Video Workgroup

Discussion Points:

  • Updates on task management: Slate shared some issues with the Town Hall editing task and also the Town Hall Summary video: assignees didn't follow the guidelines and tasks were late. Slate had a call with the Social Media manager (Malik) on how to streamline the process for these tasks, and now all issues have been resolved and the video links have been added to the content sheet.

  • Updates on social media management: Malik mentioned that 3 long videos and 3 shorts (including the Town Hall videos) were posted within the week.

  • Updates on Zealy: Lordkizzy highlighted that he had separate calls with Kenichi and Devon within the week and reached an agreement with the Writers' WG in regard to the payment for the liaison role: Devon will be paid from the Writers' WG points system in Q3 but in Q4 there will be an allocation for the liaison role in the Video WG budget. Kenichi is going to study the next two sprints to get the exact figure for the payment, so that we won't be over-paying or under-paying anyone. Secondly, Lordkizzy indicated that Devon sent out 5 long videos and 5 shorts in the previous sprint to Kenichi but only 3 long videos were created as quests, so going forward Lordkizzy has made emphasis on Devon completing the training and getting editorial access to the Zealy platform.

  • Discussion on Operations going forward: Lord kizzy suggested that we include new columns in our content sheet for Tiktok and Instagram links and Zealy Quest creation. Lordkizzy highlighted that there is a need for more participation in meetings since that is the environment where most decisions are made, and going forward he will try to see if the Video WG could adopt the Treasury system for task assignments rather than assigning members that are not up to speed on the conversation and decisions made by the Video WG.

  • Discussion on Budget: Lordkizzy and slate indicated that some other work groups are yet to get consent and that we should wait for one more week before making decisions.

  • Discussion on Quality Control: Malik suggested that we audit scripts before the video creation, zalfred suggested that we should rather make it a priority for members to give meaningful feedback while giving consent to videos. Malik also highlighted that the majority of members rarely consent to videos and asked how that can be improved. Lordkizzy suggested providing incentives ($5) to members for meaningful feedback on scripts and videos, that way we would get enough feedback on videos and ensure that the quality of videos is controlled. This will be implemented in Q4.

  • Discussion on Vacation: the Video WG is going to have further discussions on this in the next meeting.

  • Migration of Video WG calls to Zoom rather than Discord: Tuso was of the opinion that we should migrate to Zoom since majority of the Workgroups and Guilds are currently using Discord, some members still preferred Discord but we decided to continue the conversation in the next meeting.

Decision Items:

  • We decided to have further discussions on restructuring of the Q3 Budget in the next call

    • [rationale] We want to be sure of the exact figure for the budget cuts

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Lord_Kizzy to edit the Q2 Budget and Q3 Budget Proposal [assignee] lord kizzy [due] 5 July 2024 [status] done

  • [action] Lord_Kizzy to reach out to Rojo in regard to the Q3 Budget reduction and try to see if he could make the next Treasury call [assignee] lord kizzy [due] 5 July 2024 [status] done

  • [action] Lord kizzy to have a discussion with Devon and Kenichi on zealy operations rewards [assignee] lord kizzy [due] 12 July 2024 [status] done

  • [action] Zalfred and Lordkizzy to reach out to slate (as the Task manager) informing him on the decisions made in the meeting [assignee] Zalfred, lord kizzy [due] 12 July 2024 [status] done

  • [action] Lordkizzy to have a discussion with Rojo on the changes and decisions made by the video WG and to get his feedback [assignee] lord kizzy [due] 19 July 2024 [status] todo

Keywords/tags:

  • topics covered: Weekly updates, Budget Reduction, Budget, Budget fitting, Treasury Guild meeting, social media, Zealy Updates, Rewards, Video production, Zoom, Discord, feedback, consent, incentives quality, quality control

  • emotions: Casual, productive, Organised, Thoughtful, warm, new ideas, lengthy

Writers Workgroup

  • Type of meeting: Weekly

  • Present: Kenichi [facilitator], cjfrankie [documenter], Kenichi, Mikasa, cjfrankie, LadyTempestt, devon, Gorga Siagian, Ayo, Emmanuel Issac, Slate, AJ, kateri

  • Purpose: Regular weekly meeting of the Writers' WorkGroup in the SingularutyNET Ambassador Program, discuss on timestamped video shorts collaboration with the video workgroup and thrilling discussion centered around Zealy.

  • Working Docs:

Narrative:

The meeting started with Kenichi welcoming everyone to the meeting: following that, Kenichi surfed the Dework board to see all the tasks' progress. Firstly, Emmanuel Isaac and Mikasa shared an update from the Twitter management side of things. Emmanuel said that he has submitted the KPI for Q3, and he has created a draft for the content calendar which will start rolling out next week.

Secondly, Kenichi raised a discussion on the recent test taken by WWG aspirants — he also pointed out that the aspirants should enable suggestion mode to reflect the actual changes that they made. The aspirants should also open edit access and follow the exact instructions that were mentioned in the test. So far, three scribblers have reviewed the test done by Nengi and Gorga, while Kenichi will do the aggregate to show their total score, and if they reach the threshold, they will be welcomed to the WG.

Kenichi also pointed out some slips from Slate's article “Medical Advisor Roundtable: Chronic Disease” and why he still needs to make changes to the document. Kenichi also emphasized the need for more Twitter threads, and he also pointed out that Twitter threads aren't exclusive to Mikasa; other scribblers can find interesting topics and then showcase them during meetings.

We discussed “timestamped video shorts", and how we can embed them within our Medium articles to increase traction and engagement. Kenichi added that he will create a list of all the pending drafts and then give the video to WG. Devon asked, “What kind of videos?” Kenichi answered by saying that the shorts would be created from existing videos and would be no longer than 1 minute and 30 seconds. Lady Tempestt added that the scribblers should decide which part is the most captivating in a video, and then the video gets a timestamp.

We started a thrilling discussion centered around Zealy; thankfully, the current sprint is ending in a few days! Kenichi also shared insider tips on the sprinters' matrix; the current sprint has 36+ participants. We also talked about restructuring the Zealy rewards. Here’s the breakdown: the top 5 get $30 each, the next 5 get $20 each, the next 10 get $10 each, and 10 random people will earn $10 each. This decision was made to incentivize more people for their participation and time.

As a matter of finality, Ayo added that we should always give consent to new proposals to enable them to pass. He also spilled the beans by giving us insider tips from the Strategy Guild. The guild is looking forward to hosting a workshop that will involve the Writers' WG and video WG in their pipeline — more updates will be coming soon!

Decision Items:

  • In view of Dework priority bars, we decided that moving forward, Scribblers should pay close attention to the priority bars: any tasks that exceed the submission date will be assigned to another available scribbler to avoid delay!

    • [rationale] This decision was made to prevent any delay that may disrupt the overall impact of the workgroup

    • [effect] affectsOnlyThisWorkgroup

  • We have decided to incorporate “video shorts” within Medium articles to increase traction and engagement.

    • [rationale] To increase traction and engagement.

    • [effect] mayAffectOtherPeople

  • We decided to tweak Zealy's reward structure! Before now, only a few people got a chuck of the reward, but now we want to split the $400 reward among 30 sprinters.

    • [rationale] We want to spread the reward between 30 sprinters to incentivize their efforts and time.

    • [effect] affectsOnlyThisWorkgroup

Action Items:

  • [action] Following a discussion on “shorts,” Kenichi will chase LordKizzy to brief him about our discussion and let him know to move forward. [assignee] Kenichi [status] in progress

  • [action] Kenichi to draft a reward structure for Zealy and then share it in the WWG channel. [assignee] Kenichi [status] done

Keywords/tags:

  • topics covered: WWG Test, Twitter updates, Zealy sprint, priority bar, Strategy Guild, Workshop, sprinters, medium, shorts, Videos WG, timestamps, Translation, Dework

  • emotions: forward-thinking, Collaborative, productive, interesting

  • other: Introduction by AJ , Writers and Translation wg collabration, WWG Podcast

Saturday 13th July 2024

Gamers Guild

  • Type of meeting: Biweekly

  • Present: Slate [facilitator], devon [documenter], martinosoki, oep, lord kizzy, Gorga Siagian, flyn, Photogee, rebel, scarecrow, hufiumer69, hotasiro

  • Purpose: The meeting focused on workgroup creation updates.

  • Media link: Link

  • Working Docs:

Discussion Points:

  • Slate outlined the meeting agenda

  • Malik presented the Education Guild department, suggesting the building should resemble a school or college. Each classroom would represent a spin-off project with corresponding infographics on the board. (Watch the education guild video in the drive folder link under the media section)

  • Scarecrow provided the Treasury Guild creation update. They have created 6 NPCs representing guild members, who were well-received. Creation of the building is ongoing. (Watch the Treasury guild video in the drive folder link under the media section)

  • Gorga provided an update on the creation of the Archives workgroup, stating that it is in the initial stages and will demonstrate progress at the upcoming meeting.

  • Rebel updated that the Dework PBL workgroup creation is in its initial phase. He showed NPCs representing guild members as anime characters. Members proposed they be depicted as humans for a more professional look. (Watch the Dework PBL video in the drive folder link under the media section).

  • OEP announced that the progress of creating the R&D Guild department will be shown at the next meeting.

  • Slate emphasized the need to achieve the proposal goals by all means.

  • Slate inquired about the mentors' progress and found that Lord Kizzy, Gorga, and Slate have finished mentoring their assigned students, but Malik was unable to do so. (see the mentor sheet doc under the working docs section)

  • Slate answered Lord Kizzy's questions, demonstrating how to animate the prop, attach it to the NPCs, and set up the dialogue box. He also noted that we can use dialogue boxes from the toolbox as long as they are not copyrighted.

  • Lord Kizzy updated on video workgroup creation progress, showcasing NPCs animations and mentioning upcoming character and animation additions. (Watch the video workgroup video in the drive folder link under the media section)

Decision Items:

  • Avoid using NPCs that look like anime characters.

    • [rationale] for a professional look

  • Dialogue boxes used should not be copyrighted.

    • [rationale] The game can be taken down by their use.

  • All the destined departments to be created in this quarter

    • [rationale] To ensure presentation in the quarterly report and avoid concerns about unfulfilled deliverables.

Action Items:

  • [action] Department Creation - Education Guild [assignee] malik, hufiumer69 [due] 27 July 2024 [status] in progress

  • [action] Department Creation - Treasury Guild [assignee] martinsoki, scare-crow [due] 27 July 2024 [status] in progress

  • [action] Department Creation - Archival Workgroup [assignee] GorgaSeagian, kateri [due] 27 July 2024 [status] in progress

  • [action] Department Creation - Dework PBL [assignee] rebel, Photogee [due] 27 July 2024 [status] in progress

  • [action] Department Creation - RnD Guild [assignee] oep, CollyPride [due] 27 July 2024 [status] in progress

  • [action] Animation & Dialogue System (Video Workgroup) [assignee] lord kizzy, GorgaSeagian [due] 27 July 2024 [status] in progress

Game Rules:

Last Man Standing - Battle Royale game - final survivor wins the game. Players: Devon, Martinsoki, lord kizzy, photogee, hotasiro, rebel, hufiumer, flyn, scare crow, Gorga.

Leaderboard:

  • 1st Hufiumer

Keywords/tags:

  • topics covered: Roblox, metaverse, department creation, work updates, Collaboration, Game Development, mentorship, Dialogue Systems, Animation

  • emotions: Friendly, Collaborative, Deliberative, informative, focused on reporting

  • games played: Battle Royale

PreviousWeek 27NextWeek 29

Last updated

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