<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on</title><link>https://dicendistros.com/posts/</link><description>Recent content in Posts on</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dicendistros.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Infrastructure Updates</title><link>https://dicendistros.com/posts/infrastructure-updates/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://dicendistros.com/posts/infrastructure-updates/</guid><description>Join Page We added a &amp;ldquo;Join&amp;rdquo; page and added a link to the navbar. This page presently contains links to a Discord server, Matrix space, and Mastodon profile, all of which are quite barebones and should be fleshed out in the coming days. In the future, we should also add information about meatspace meetings and provide clear and transparent information re: onboarding newcomers.
CoC and Other Documents A number of documents have been created to set expectations and avoid future conflict.</description><content>&lt;h2 id="join-page">Join Page&lt;/h2>
&lt;p>We added a &amp;ldquo;Join&amp;rdquo; page and added a link to the navbar. This page presently contains links to a Discord server, Matrix space, and Mastodon profile, all of which are quite barebones and should be fleshed out in the coming days. In the future, we should also add information about meatspace meetings and provide clear and transparent information re: onboarding newcomers.&lt;/p>
&lt;h2 id="coc-and-other-documents">CoC and Other Documents&lt;/h2>
&lt;p>A number of documents have been created to set expectations and avoid future conflict. This includes a Code of Conduct (adopted from the Contributor Covenant), a Financial Transparency page detailing moneys in and out, and a Governance Document describing the requirements of membership, voting procedures, and the like.&lt;/p>
&lt;p>As of now, the Governance Document calls for consensus-based decision-making with a supermajority vote as a fallback if consensus cannot be reached. Active members with voting rights are defined as people who have attended at least 2 meatspace meetings in the last 12 months. It is worth considering modifying the Governance Document to put stricter conditions on membership, e.g. requiring a certain number of existing members to sponsor new members, in order to ensure group integrity and prevent hostile takeovers.&lt;/p>
&lt;h2 id="sops-planned">SOPs Planned&lt;/h2>
&lt;p>The following is a list of SOPs that we should consider creating&amp;hellip; They should be triaged, and the most important ones created first. We should also consider a discussion to determine where/how they will be stored: this website will become quite cluttered and increase administrative overhead if we keep them all here, but moving them elsewhere may create unnecessary informational friction. Some solutions could be to house the documents in this website&amp;rsquo;s GitHub Wiki, create a secondary site using a Hugo template more conducive to this type of content, or simply create a page on this site which aggregates links to documents as they are created. In any case, vcs should be used to transparently track changes, any aggregate lists should be kept up-to-date, and informational friction should be kept to a minimum given the restraints of whatever system we adopt.&lt;/p>
&lt;h3 id="sops-standard-operating-procedures">SOPs (Standard Operating Procedures)&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Event setup &amp;amp; teardown&lt;/strong>: venue checklist, timeline, room layout, equipment hookup, accessibility checks, cleanup.&lt;/li>
&lt;li>&lt;strong>On-site safety &amp;amp; incident response&lt;/strong>: immediate actions, who to notify, documentation template, privacy handling.&lt;/li>
&lt;li>&lt;strong>Code of Conduct enforcement&lt;/strong>: reporting steps, investigation timeline, temporary measures, documentation form.&lt;/li>
&lt;li>&lt;strong>New-member onboarding&lt;/strong>: welcome script, membership criteria verification, orientation checklist.&lt;/li>
&lt;li>&lt;strong>Facilitator handover&lt;/strong>: role responsibilities, account/access transfer checklist, handoff notes template.&lt;/li>
&lt;li>&lt;strong>Financial handling&lt;/strong>: petty cash procedure, receipt tracking, monthly reconciliation, expense approval flow.&lt;/li>
&lt;li>&lt;strong>Equipment lending&lt;/strong>: inventory log, checkout/return procedure, damage/loss policy.&lt;/li>
&lt;li>&lt;strong>Volunteer recruitment &amp;amp; management&lt;/strong>: role descriptions, shift signup, volunteer briefing checklist.&lt;/li>
&lt;li>&lt;strong>Venue booking &amp;amp; negotiation&lt;/strong>: contact script, room requirements, accessibility/access keys, insurance/liability checklist.&lt;/li>
&lt;li>&lt;strong>Emergency contact &amp;amp; medical response&lt;/strong>: local emergency numbers, nearest clinic/hospital, consent &amp;amp; data handling.&lt;/li>
&lt;li>&lt;strong>Privacy &amp;amp; data handling&lt;/strong>: membership list storage, event photos consent procedure, retention policy.&lt;/li>
&lt;/ul>
&lt;h3 id="event-toolkits">Event Toolkits&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>New-player tabletop session kit&lt;/strong>: beginner rules cheat-sheets, pregenerated characters, quick-start adventure, table signs (open/closed/looking for players).&lt;/li>
&lt;li>&lt;strong>Linux workshop kit&lt;/strong>: install media checklist (USB images), common distro cheat-sheets, step-by-step installation guide, troubleshooting flowchart.&lt;/li>
&lt;li>&lt;strong>Hybrid event toolkit&lt;/strong>: A/V checklist, mic/camera placement, streaming settings, remote-participant facilitation tips.&lt;/li>
&lt;li>&lt;strong>Accessibility &amp;amp; inclusion kit&lt;/strong>: sensory-friendly room setup, quiet space checklist, pronoun badges, accessibility accommodations request form.&lt;/li>
&lt;li>&lt;strong>Game-night essentials&lt;/strong>: dice/pen/paper stash list, timers, rule-reference binder, table assignment templates.&lt;/li>
&lt;li>&lt;strong>Beginner tech-help station&lt;/strong>: common fixes checklist, backup procedures, privacy-safe data-handling script for assisting others’ devices.&lt;/li>
&lt;li>&lt;strong>Outreach &amp;amp; recruitment kit&lt;/strong>: event flyer templates, social-media post templates, welcome email template, partner-org contact list.&lt;/li>
&lt;li>&lt;strong>Onboarding/Info packet&lt;/strong>: printable one-pager about group purpose, CoC summary, how to get active membership, upcoming events.&lt;/li>
&lt;/ul>
&lt;h3 id="templates--forms">Templates &amp;amp; Forms&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Proposal template&lt;/strong>: title, summary, rationale, resource needs, timeline, decision method.&lt;/li>
&lt;li>&lt;strong>Meeting agenda &amp;amp; minutes&lt;/strong>: standard agenda format, decision log, action-item tracker.&lt;/li>
&lt;li>&lt;strong>Incident report form&lt;/strong>: anonymized template with facts, witnesses, actions taken, follow-up steps.&lt;/li>
&lt;li>&lt;strong>Consent forms&lt;/strong>: photo/recording consent, data-sharing consent.&lt;/li>
&lt;li>&lt;strong>Expense request &amp;amp; reimbursement form&lt;/strong>: itemized fields, receipts attached, approver signature.&lt;/li>
&lt;li>&lt;strong>Volunteer signup form&lt;/strong>: role, availability, contact, emergency contact, accessibility needs.&lt;/li>
&lt;li>&lt;strong>Working-group charter&lt;/strong>: scope, deliverables, members, sunset date, budget.&lt;/li>
&lt;li>&lt;strong>Event feedback survey&lt;/strong>: Likert-scale items and open feedback fields for safety, accessibility, enjoyment, and logistics.&lt;/li>
&lt;/ul>
&lt;h3 id="checklists">Checklists&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Pre-event checklist (1 week / 24 hours / 1 hour before)&lt;/strong>: venue confirmation, supplies, signage, accessibility, facilitator brief.&lt;/li>
&lt;li>&lt;strong>Post-event checklist&lt;/strong>: attendance log, lost-and-found, finances tallied, feedback collected, follow-ups assigned.&lt;/li>
&lt;li>&lt;strong>Monthly admin checklist&lt;/strong>: membership active roster update, financial summary posted, upcoming events planned.&lt;/li>
&lt;/ul>
&lt;h3 id="communication-kits">Communication Kits&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Crisis communication script&lt;/strong>: templated messages for attendees, volunteers, venue, and public statements.&lt;/li>
&lt;li>&lt;strong>Moderator guidance for online channels&lt;/strong>: escalation rules, banned-content handling, welcome message templates.&lt;/li>
&lt;li>&lt;strong>Newsletter template&lt;/strong>: events, volunteer needs, highlights, finance snapshot.&lt;/li>
&lt;/ul>
&lt;h3 id="training-materials">Training Materials&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Facilitator training deck&lt;/strong>: consensus process, running inclusive discussions, consent checks.&lt;/li>
&lt;li>&lt;strong>Safety &amp;amp; de-escalation training&lt;/strong>: role-play scenarios, contact/resource list.&lt;/li>
&lt;li>&lt;strong>Linux basics workshop slides&lt;/strong>: command-line essentials, package management, common troubleshooting.&lt;/li>
&lt;/ul></content></item><item><title>Introducing Dice &amp; Distros</title><link>https://dicendistros.com/posts/hello/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://dicendistros.com/posts/hello/</guid><description>There really is a weird intersection between the LGBT+ community, tabletop gaming, and open source. There&amp;rsquo;s also a shocking lack of community in Jackson, Michigan.
My goal in starting this group is to help build sustainable, scaleable, grassroots community infrastructure. I know that sounds lofty, so I won&amp;rsquo;t dwell on it much. For now, I&amp;rsquo;ll just say that I hope to create and disseminate standard operating procedures (SOPs), event toolkits, and the like to make it easier for anybody to run similar events and groups without having to replicate quite so much of the logistical work.</description><content>&lt;p>&lt;img alt="Venn diagram" src="https://dicendistros.com/img/venn.svg">&lt;/p>
&lt;p>There really is a weird intersection between the LGBT+ community, tabletop gaming, and open source. There&amp;rsquo;s also a shocking lack of community in Jackson, Michigan.&lt;/p>
&lt;p>My goal in starting this group is to help build sustainable, scaleable, grassroots community infrastructure. I know that sounds lofty, so I won&amp;rsquo;t dwell on it much. For now, I&amp;rsquo;ll just say that I hope to create and disseminate standard operating procedures (SOPs), event toolkits, and the like to make it easier for &lt;em>anybody&lt;/em> to run similar events and groups without having to replicate quite so much of the logistical work.&lt;/p>
&lt;p>In the meantime, our &lt;strong>real&lt;/strong> goal is to play some games and talk about Linux!&lt;/p>
&lt;p>This group was conceived as a half-joke earlier today. The website was developed and deployed, and the domain purchased, over the course of the afternoon and evening. In the coming days, I plan to set up some basic infrastructure on Discord, Mastodon, Matrix, and/or MeetUp. Scheduling and location will be announced once they are determined.&lt;/p>
&lt;p>While things are getting set up, feel free to reach out to &lt;a href="mailto:info@dicendistros.com">info@dicendistros.com&lt;/a> with any ideas, questions, or concerns. You can also find my personal blog at &lt;a href="https://evelynpark.com">evelynpark.com&lt;/a> if you want to learn a little about me before placing your DnD character&amp;rsquo;s life in my hands.&lt;/p>
&lt;p>Bad at conclusions. Pretend I said something appropriately aspirational.&lt;/p></content></item></channel></rss>