snet-data.json

{ "a3d9a6d1-7976-4a18-bc0c-62f3e638e329": [
      {
        "workgroup": "Governance Workgroup",
        "workgroup_id": "bcfadc9a-79d3-4ac0-816a-6b3405fd4009",
        "meetingInfo": {
          "name": "Weekly",
          "date": "2025-01-07",
          "host": "PeterE",
          "documenter": "CallyFromAuron",
          "peoplePresent": "PeterE, CallyFromAuron, CollyPride, AshleyDawn, LadyTempestt, osmium, LordKizzy",
          "purpose": "Weekly Governance WG meeting",
          "workingDocs": [
            {
              "title": "Governance calls, rolling agenda",
              "link": "https://docs.google.com/document/d/1t39dwlwLYYB_1z_5szq1rnOH7mVTHe8Tmwv0R6ELOyE/edit?usp=sharing"
            },
            {
              "title": "Ambassador Program End of Year report - draft outline",
              "link": "https://docs.google.com/document/d/1TxKxP9sDNgvKncAqO0F-UhZgoftMdDktaqbt50-h2XM/edit?usp=sharing "
            },
            {
              "title": "Q4 budget decision - main issues mentioned in objections",
              "link": "https://docs.google.com/document/d/1vzqhY_KDaE5l_4z_NVwr5aNFJKa6f71roslsg9Md0vU/edit?usp=sharing"
            },
            {
              "title": "GovWG Budgets",
              "link": "https://docs.google.com/spreadsheets/d/1DeUB6ytoOeG6SOHwhJxe-vII_mXmkjdxG1iD-f5B2Sc/edit?usp=sharing"
            },
            {
              "title": "Treasury Policy Submission Form",
              "link": "https://docs.google.com/forms/d/e/1FAIpQLScA7Rcw-7QclL13qnfsdrtFt64nYRKM7zU1LgOK9wEoaWgpqg/viewform"
            }
          ],
          "timestampedVideo": {}
        },
        "agendaItems": [
          {
            "status": "carry over",
            "narrative": "Input needed:\n- We noted that some WGs haven't yet added to the draft End Of Year Report - we'll give reminders in Town Hall tonight, and on Discord.\n- There's only been 2 responses so far to the Googleform about what WG Sync Calls should be covering. We'll give reminders in Town Hall tonight, and on Discord; and hopefully discuss in Governance meeting on Thurs 9th or Thurs 16th when we have more input.\n\nRetrospective on Q1 consent process:\n- We noted that GovWG meeting on Tues 14th is scheduled to be the retrospective session on the Q1 budget consent process.\n- Peter has yet to DM Core Contributors who didn't take part in the Q1 budget approval process, to find out why they didn't. He'll do it as soon as poss.\n- We will also ask Tevo if he has data on how many Core Contributors did take part this time (it's hard to tell from the Googleform responses, as people submit one per WG so it is hard to see how many unique consenters there were).\n- We noted it could be interesting in the retrospective to consider overall patterns of *how* consenters took part (e.g. were there fewer objections than last time? Were objections similar to last time, or different? Were there people who blanket unapproved all WGs, like there was last time?)\n\nDocumentation of Governance WG meetings\n- We agreed it's not an entry-level task.\n- We agreed the low-ish price ($20) might be putting people off doing it; people might also be put off by feeling that summaries need to be very detailed\n- We noted that there is still quite a bit of work to do on the backlog of summaries from Q3 and Q4 - there are people working on it, but $20 feels very low, as backlog work is harder since it's not fresh in the mind\n- We discussed whether people should be able to document meetings they were not present at, and concluded that while it's better if you were there, it's OK to work from the Read.ai transcript (though *not* from just the Read.ai summary, as those are often very inaccurate)\n- We agreed that to make documentation less onerous (especially for the backlog work) it is OK to focus on decisions, action items, and who was present\n- We agreed to raise the price (see \"decisions\")\n\nNext WG Sync Call date\n - Next call is supposed to be Thurs 30th Jan at 10:00 UTC - is this too early in the day? Peter will ask in Town Hall tonight about preferred date and time - possibly move to Weds 29th at 13:00 UTC\n\nWG unspent budget / budget reserves\n- We outlined the current process (unspent budget used to be clawed back by Treasury - but since Jan last year, it has not been. Anything that a WG doesn't spend, becomes part of their WG reserves and they can still use it.)\n- Should there be a time limit on how long a WG has to use budget that was allocated to a particular task? And if they want to change what they use it for, how should they do that?\n- How to avoid gaming the system (e.g. submitting a quarterly budget to do amazing things, to ensure consent; but then changing it to less impressive things in the first week of the Quarter)\n- We agreed on a suggested approach based on a \"change request\" process if a WG wants to make major changes (see \"Decisions\" below) and agreed to submit this as a potential new Treasury Policy.\n",
            "actionItems": [
              {
                "status": "todo",
                "text": "Peter to DM Core Contributors who didn't take any part in the Q1 budget consent process, to ask why they didn't",
                "assignee": "PeterE",
                "dueDate": "14 January 2025"
              },
              {
                "text": "Peter to raise items from this meeting in Town Hall later today (Requests for input on  End of Year Report and WG Sync Calls; sharing info on proposed new policy on WG budget changes)",
                "assignee": "PeterE",
                "dueDate": "7 January 2025",
                "status": "done"
              },
              {
                "text": "Vani to ask Tevo if he has info on how many people took part in the Q1 budget consent process",
                "assignee": "CallyFromAuron",
                "dueDate": "9 January 2025",
                "status": "todo"
              }
            ],
            "decisionItems": [
              {
                "decision": "We will raise the price of backlog summaries to $30 per summary. Current summaries will stay at $20; but if AGIX price goes up by the end of Q1, we will give a bonus to documenters",
                "rationale": "Backlog work is more onerous, and can take a lot of time, so price should be higher - and we do have leftover budget to cover it in Q3 and Q4 budgets.\nBut our Q1 budget has allocated $20 for documentation - so we cannot raise this price unless we know AGIX price is high enough.",
                "opposing": "none",
                "effect": "affectsOnlyThisWorkgroup"
              },
              {
                "decision": "Suggested process for WG budget reallocation:\n - If the changed budget line is 0-5% of a WG's total quarterly budget, the WG can change this at their own discretion without any consultation (1x per quarter)\n - If it's 5-35% of the total quarterly budget, the WG should submit the suggested change to #decisions-to-be-made Discord channel, tagging @Core Contributor, and there will be 1 week for any objections to be registered. (If no objections, the WG can go ahead: if anyone objects, we didn't decide how that should be processed. Discuss in a Governance meeting?)\n- A 35% + change request needs to be included in the WG's budget proposal for the following Quarter (note that it would be separate from, and in addition to, their budget cap for that Quarter. So if a WG has a cap of 5k AGIX for Quarter 2 2025, and has 1k AGIX unspent from Q1 that it wants to reallocate, it will therefore have a total of 6k AGIX to work with).\n- If a WG has unused budget at the end of a Quarter that they still intend to use as originally planned, they don't need to do anything special - they just do the work as and when they can.",
                "rationale": "- To enable WGs to respond to changes that emerge out of their work, and to reallocate unspent budget if they find they no longer need to do the tasks they originally got the money for, but something else.\n- To prevent WGs losing budget that they have secured simply because they have realised there is a better use for the money.\n- To prevent gaming of the system.",
                "effect": "mayAffectOtherPeople"
              },
              {
                "decision": "The above policy suggestion will be discussed in Town Hall and in the Gov WG Discord channel, and then will be submitted as a potential new Treasury Policy",
                "rationale": "The Treasury Policy process seems like the best way to ratify and agree the idea.",
                "opposing": "none",
                "effect": "mayAffectOtherPeople"
              }
            ],
            "discussionPoints": [
              "Input needed for End of Year report",
              "Input needed for Googleform on what WG Sync calls should cover",
              "Retrospective on Q1 budget decision process",
              "Documentation of GovWG meetings",
              "Next WG Sync Call date",
              "WG unspent budget / budget reserves"
            ]
          }
        ],
        "tags": {
          "topicsCovered": "End of Year report, Workgroup Sync call, core contributors, retrospective, participation, consent process, Q1 2025 budget decision, Workgroup reserves, change request, WG budget changes, Documentation",
          "emotions": "Discursive, Good natured, interesting, progress made"
        },
        "type": "Custom",
        "noSummaryGiven": false,
        "canceledSummary": false
      }
    ] }