<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.snafucon.com/mw/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Beta</id>
	<title>SNAFU Con Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.snafucon.com/mw/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Beta"/>
	<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/wiki/Special:Contributions/Beta"/>
	<updated>2026-04-04T01:03:39Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.7</generator>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Dorms&amp;diff=1838</id>
		<title>Dorms</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Dorms&amp;diff=1838"/>
		<updated>2026-03-06T04:49:13Z</updated>

		<summary type="html">&lt;p&gt;Beta: updated dorms records&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Staff Dorms / Housing ===&lt;br /&gt;
SNAFU Con does not yet have the budget to outright purchase hotel rooms for the staff. However, we are able to offer a discounted rate for the staff, and group the staff in rooms.&lt;br /&gt;
===Eligibility===&lt;br /&gt;
If you are a staff member you are eligible to use the staff dorms. We also occasionally have special cases stay in the staff dorms.&lt;br /&gt;
&lt;br /&gt;
We do not offer this to volunteers, you must have full staff status.&lt;br /&gt;
&lt;br /&gt;
If you are removed as staff for any reason, you will no longer be eligible for the staff dorms. If this happens during the convention itself it is up to the discretion of the convention chairs as to whether you may continue to stay in the dorms. &lt;br /&gt;
&lt;br /&gt;
Refund may only be given if a staff member cancels or is removed from the dorms earlier than 1 week before the convention starts. After that point, refund is increasingly unlikely, but is up to the discretion of the convention chairs.&lt;br /&gt;
===Placements===&lt;br /&gt;
We group staff together by gender. &lt;br /&gt;
&lt;br /&gt;
We group staff up to 4 in a single room. There are two beds in a room. It is up to the members of the room to determine who gets beds, who shares beds, and who sleeps on the floor. You’re adults – work it out. &lt;br /&gt;
&lt;br /&gt;
Generally we do not let staff choose what room they will be in or who they will be with. However, requests to be housed with a certain staff member or to *not* be housed with a certain staff member will be considered. We may not be able to accommodate all requests.&lt;br /&gt;
&lt;br /&gt;
A staff member may pay for all four person slots and stay with their significant other or family at the staff dorm rates. Other members of the room need not be staff. One must take and pay for all four person-slots to be able to do this. If you do take a full room, you will likely have to check in and out your own room (it will be determined immediately before the convention). &lt;br /&gt;
===Check In, Keys===&lt;br /&gt;
Beta checks in the staff rooms and distributes keys. Beta has a key for each room and might periodically check on the room. If you lose your key, Beta will be able to get another one.&lt;br /&gt;
&lt;br /&gt;
If a person has paid for all four slots, they might have to check in their own room (this will be determined immediately before the convention). The company owners can get into any room in our room block, and still might periodically check in on that room.&lt;br /&gt;
=== Check Out ===&lt;br /&gt;
If the room is booked for longer than you are staying, you can just leave when you have the chance at any point that morning. If the room is booked until the morning you&#039;re planning to leave, you need to be completely out by 11am.&lt;br /&gt;
===Rates===&lt;br /&gt;
* 2015-2019 the rate was $15/person/night. &lt;br /&gt;
* 2021 was going to be $25 but due to a misquote it became $20/person/night. &lt;br /&gt;
* 2022-2024 is $25/person/night.&lt;br /&gt;
* 2025 $40/person/night&lt;br /&gt;
If you truly cannot afford the current rate, please contact us anyway. We have allowed staff to stay in the dorms for lesser rates up to and including $0 because they just couldn’t afford anything and would have been sleeping under tables otherwise. Please be honest about what you can afford.&lt;br /&gt;
===How To===&lt;br /&gt;
At least 1 month before con (ASAP), PM Beta in chat or via email and let her know that you want to be in the staff dorms for that year. Please include what nights you need. Be as clear as possible. It is recommended to state when you will need the room and what morning you are leaving. Eg: “Need a room starting Thursday night and leaving Sunday morning.”&lt;br /&gt;
===Special At-Con Situations===&lt;br /&gt;
It is up to you to plan how you sleep and shower during con. However, if you find yourself without a place to sleep or shower, please contact Beta and we might be able to temporarily accommodate you. &lt;br /&gt;
&lt;br /&gt;
We sometimes have extra dorm space, and we often have a non-committed room that we can allow people to use temporarily for a nap or a shower. We can’t promise that we can help you, but please reach out to us and we will do what we can. &lt;br /&gt;
&lt;br /&gt;
Please do not sleep under tables or in your car. =(&lt;br /&gt;
=== How to Pay ===&lt;br /&gt;
Bring cash or a check to con. Ideally put it in an unsealed envelope with your name and the amount on it and the word &amp;quot;Dorms.&amp;quot; We will verify the money at con and put the envelope away. It helps me with the books post-con to keep the payment separate. &lt;br /&gt;
&lt;br /&gt;
The reason we do cash/check is because just about any other method will cost us in processor fees and we&#039;re already losing money on this deal. &lt;br /&gt;
===VIP Eligibility===&lt;br /&gt;
You do not receive VIP status if you use the staff dorms. You must reserve your own room through our hotel link if you want VIP status.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Category:Bookkeeping&amp;diff=1836</id>
		<title>Category:Bookkeeping</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Category:Bookkeeping&amp;diff=1836"/>
		<updated>2026-02-25T15:24:32Z</updated>

		<summary type="html">&lt;p&gt;Beta: Created page with &amp;quot;Entering things into quickbooks&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Entering things into quickbooks&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Bank_Run&amp;diff=1835</id>
		<title>Bank Run</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Bank_Run&amp;diff=1835"/>
		<updated>2025-11-17T15:56:07Z</updated>

		<summary type="html">&lt;p&gt;Beta: origami ones&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
At con on Saturday we need to clear out our cash as much as possible and make a bank deposit. &lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
# Count out two deposit amounts from the main cash box. Each deposit is to be no more than the deposit limits. For simplicity, if you have less than the combined limit make one deposit the full limit amount and the remainder can go in the other account.&lt;br /&gt;
# Record the amounts being removed from the main box on the General Ledger&lt;br /&gt;
# We have two bank accounts and each one has its own deposit slip. Attach a different deposit slip to each pile of money counted in the previous step. &lt;br /&gt;
# Put the money in a money bag&lt;br /&gt;
# Take to the nearest Wells Fargo (Money is only to be taken by a trusted high-level staffer authorized by Beta.)&lt;br /&gt;
# Stand in the business line&lt;br /&gt;
# Give them the money and wait for your receipt&lt;br /&gt;
# Bring the receipt back to reg&lt;br /&gt;
# If we have a scanning/filing system set up, scan and file the receipts&lt;br /&gt;
&lt;br /&gt;
=== Cash Deposit Limits ===&lt;br /&gt;
&lt;br /&gt;
* $5,000 can be deposited into Checking per calendar month (used to be $7,500, but it&#039;s $5,000 now)&lt;br /&gt;
* $5,000 can be deposited into Savings per calendar month&lt;br /&gt;
&lt;br /&gt;
Anything over these limits and the bank charges us money.&lt;br /&gt;
&lt;br /&gt;
=== Cash Box Amounts ===&lt;br /&gt;
Keep in the box, post-con&lt;br /&gt;
&lt;br /&gt;
* 0 x 20&#039;s&lt;br /&gt;
* 20 x 10&#039;s ($200)&lt;br /&gt;
* 20 x 5&#039;s ($100)&lt;br /&gt;
* 50 x 1&#039;s ($50) (plus the 2 origami ones, equaling $52 in the box)&lt;br /&gt;
* Coins as reasonable; roll up all of them as much as possible, deposit what we can&#039;t reasonably keep in the box.&lt;br /&gt;
&lt;br /&gt;
I like to sort the bills and keep the nicest looking ones, while sorting and distributing any extra-crisp bills so they don&#039;t sit next to each other in the stack.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Bank_Run&amp;diff=1834</id>
		<title>Bank Run</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Bank_Run&amp;diff=1834"/>
		<updated>2025-11-17T15:32:55Z</updated>

		<summary type="html">&lt;p&gt;Beta: add cash box amounts&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
At con on Saturday we need to clear out our cash as much as possible and make a bank deposit. &lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
# Count out two deposit amounts from the main cash box. Each deposit is to be no more than the deposit limits. For simplicity, if you have less than the combined limit make one deposit the full limit amount and the remainder can go in the other account.&lt;br /&gt;
# Record the amounts being removed from the main box on the General Ledger&lt;br /&gt;
# We have two bank accounts and each one has its own deposit slip. Attach a different deposit slip to each pile of money counted in the previous step. &lt;br /&gt;
# Put the money in a money bag&lt;br /&gt;
# Take to the nearest Wells Fargo (Money is only to be taken by a trusted high-level staffer authorized by Beta.)&lt;br /&gt;
# Stand in the business line&lt;br /&gt;
# Give them the money and wait for your receipt&lt;br /&gt;
# Bring the receipt back to reg&lt;br /&gt;
# If we have a scanning/filing system set up, scan and file the receipts&lt;br /&gt;
&lt;br /&gt;
=== Cash Deposit Limits ===&lt;br /&gt;
&lt;br /&gt;
* $5,000 can be deposited into Checking per calendar month (used to be $7,500, but it&#039;s $5,000 now)&lt;br /&gt;
* $5,000 can be deposited into Savings per calendar month&lt;br /&gt;
&lt;br /&gt;
Anything over these limits and the bank charges us money.&lt;br /&gt;
&lt;br /&gt;
=== Cash Box Amounts ===&lt;br /&gt;
Keep in the box, post-con&lt;br /&gt;
&lt;br /&gt;
* 0 x 20&#039;s&lt;br /&gt;
* 20 x 10&#039;s ($200)&lt;br /&gt;
* 20 x 5&#039;s ($100)&lt;br /&gt;
* 50 x 1&#039;s ($50)&lt;br /&gt;
* Coins as reasonable; roll up all of them as much as possible, deposit what we can&#039;t reasonably keep in the box.&lt;br /&gt;
&lt;br /&gt;
I like to sort the bills and keep the nicest looking ones, while sorting and distributing any extra-crisp bills so they don&#039;t sit next to each other in the stack.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Per_Diem&amp;diff=1829</id>
		<title>Per Diem</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Per_Diem&amp;diff=1829"/>
		<updated>2025-10-30T14:06:59Z</updated>

		<summary type="html">&lt;p&gt;Beta: sometimes we just trust someone to handle it&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Per diem is offered occasionally contractors providing a service to the convention.&lt;br /&gt;
&lt;br /&gt;
=== Policy ===&lt;br /&gt;
&lt;br /&gt;
* Per diem must be approved by owners.&lt;br /&gt;
** Approval may be granted verbally or in writing (discord, email, etc) &lt;br /&gt;
** Individual non-owners may be granted temporary authority to approve per diem autonomously&lt;br /&gt;
* Per diem is provided in cash, so that it can be spent on food immediately&lt;br /&gt;
* A cash per diem receipt must be prepared then signed by the contractor to prove cash receipt by contractor&lt;br /&gt;
&lt;br /&gt;
=== Per Diem Process ===&lt;br /&gt;
&lt;br /&gt;
# Contractor negotiates per diem with the convention&lt;br /&gt;
# Per diem amounts approved by an owner (verbal okay, written/discord preferred)&lt;br /&gt;
# Per diem contracted&lt;br /&gt;
# Cash withdrawn for per diem amount&lt;br /&gt;
# Per diem receipt attached to cash which is kept at registration until contractor picks it up&lt;br /&gt;
# Contractor signs receipt to receive cash&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Per_Diem&amp;diff=1828</id>
		<title>Per Diem</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Per_Diem&amp;diff=1828"/>
		<updated>2025-10-30T14:04:01Z</updated>

		<summary type="html">&lt;p&gt;Beta: start page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Per diem is offered occasionally contractors providing a service to the convention.&lt;br /&gt;
&lt;br /&gt;
=== Policy ===&lt;br /&gt;
&lt;br /&gt;
* Per diem must be approved by owners.&lt;br /&gt;
* Per diem is provided in cash, so that it can be spent on food immediately&lt;br /&gt;
* A cash per diem receipt must be prepared then signed by the contractor to prove cash receipt by contractor&lt;br /&gt;
&lt;br /&gt;
=== Per Diem Process ===&lt;br /&gt;
&lt;br /&gt;
# Contractor negotiates per diem with the convention&lt;br /&gt;
# Per diem amounts approved by an owner (verbal okay, written/discord preferred)&lt;br /&gt;
# Per diem contracted&lt;br /&gt;
# Cash withdrawn for per diem amount&lt;br /&gt;
# Per diem receipt attached to cash which is kept at registration until contractor picks it up&lt;br /&gt;
# Contractor signs receipt to receive cash&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=BST_-_Amounts_Paid_Using_SCIENCE_AMEX&amp;diff=1809</id>
		<title>BST - Amounts Paid Using SCIENCE AMEX</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=BST_-_Amounts_Paid_Using_SCIENCE_AMEX&amp;diff=1809"/>
		<updated>2025-03-14T00:08:35Z</updated>

		<summary type="html">&lt;p&gt;Beta: intercompany clearing process&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;BST is owned by SCIENCE. Sometimes SCIENCE pays BST bills and needs to do the appropriate bookkeeping. &lt;br /&gt;
&lt;br /&gt;
# In the BST Quickbooks - there is a SCIENCE short term account set up as a credit card. Use that &amp;quot;card&amp;quot; to pay bills posted to the correct vendors (VPSDime, etc)&lt;br /&gt;
# In the SCIENCE Quickbooks - post the bills to the individual vendors as normal (VPSDime, etc), but set it to the &#039;&#039;&#039;Intercompany Clearing&#039;&#039;&#039; account&lt;br /&gt;
# At the end of the year, when the annual Cash Back rec is complete, some amount may be allocated to the intercompany clearing account. Post as appropriate.&lt;br /&gt;
# At the end of the year, write an invoice to BST with the item code &amp;quot;BST Intercompany&amp;quot; and the description as appropriate. Use as many line items as needed to break out the charges but can group appropriately. Examples:&lt;br /&gt;
#* 2024 VPS Dime hosting less AMEX cash back&lt;br /&gt;
#* 2024 Nevada Business license, less AMEX cash back&lt;br /&gt;
# Ensure the Intercompany clearing account is $0 for the year, adjust invoice as needed to make it hit $0.&lt;br /&gt;
# Save invoice to PDF in the BST books backup folder&lt;br /&gt;
# Move over to BST Quickbooks&lt;br /&gt;
# In the BST Quickbooks, enter the invoice as a CC Refund/Credit to Accounts Payable using SCIENCE, LLC-vend as the Customer/Job. Use the invoice # as the reference.&lt;br /&gt;
# Cash back amounts should have a credit entered to the appropriate expense accounts. &lt;br /&gt;
# If both the invoice and the cash back amounts were entered correctly what this will do is zero out the credit card account for the year, but make the amount due in the SCIENCE Vendor.&lt;br /&gt;
# Enter a check for SCIENCE to pay the amount due for the year. &lt;br /&gt;
# Amount can be paid via check or zelle to the SCIENCE account.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=BST_-_Rackspace_Invoices&amp;diff=1808</id>
		<title>BST - Rackspace Invoices</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=BST_-_Rackspace_Invoices&amp;diff=1808"/>
		<updated>2025-03-09T21:41:59Z</updated>

		<summary type="html">&lt;p&gt;Beta: Copied from Bitrix24 Wiki&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Downloading Invoices=&lt;br /&gt;
&lt;br /&gt;
#[https://cp.rackspace.com/MyAccount/CompanyInfo/Invoices.aspx You can click here to go directly to the invoices.]&lt;br /&gt;
#Log in.&lt;br /&gt;
#All the invoices are listed here, newest at the top. Click the one you want to download.&lt;br /&gt;
#Click &#039;&#039;&#039;Print Invoice&#039;&#039;&#039;.&lt;br /&gt;
#Print to PDF.&lt;br /&gt;
&lt;br /&gt;
=Entering into Kashoo=&lt;br /&gt;
&lt;br /&gt;
#Log in to Kashoo.&lt;br /&gt;
#Click &#039;&#039;&#039;Suppliers&#039;&#039;&#039;.&lt;br /&gt;
#Click &#039;&#039;&#039;Rackspace&#039;&#039;&#039; (you may need to search if it doesn’t show up on the first page).&lt;br /&gt;
#Scroll down to the list of bills.&lt;br /&gt;
#&#039;&#039;&#039;NOTE:&#039;&#039;&#039; You may not need to create a new bill if bills were auto-entered in advance. If you see the bill dates are already there, open that bill and just fix it (and possibly the payment) to be accurate and attach the PDF.&lt;br /&gt;
#Right-click on the most recent regular bill.&lt;br /&gt;
#Click &#039;&#039;&#039;Duplicate&#039;&#039;&#039;.&lt;br /&gt;
#Update the &#039;&#039;&#039;Bill#&#039;&#039;&#039; with the Invoice ID and update the dates.&lt;br /&gt;
#Make sure the total looks right.&lt;br /&gt;
#Click &#039;&#039;&#039;Show Options&#039;&#039;&#039;.&lt;br /&gt;
#Fill in the date of payment (same as the date on the invoice) in the &#039;&#039;&#039;Date&#039;&#039;&#039; field.&lt;br /&gt;
#Update &#039;&#039;&#039;Paid From&#039;&#039;&#039; as &#039;&#039;&#039;Bank of the West Checking&#039;&#039;&#039;.&lt;br /&gt;
#Update the &#039;&#039;&#039;Amount&#039;&#039;&#039; to match the bill.&lt;br /&gt;
#Click on the bill you just entered.&lt;br /&gt;
#Scroll down to the attachment section and attach the PDF you downloaded.&lt;br /&gt;
&lt;br /&gt;
Make sure the PDF is also in Evernote.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=BST_-_Namecheap_Books_Process&amp;diff=1807</id>
		<title>BST - Namecheap Books Process</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=BST_-_Namecheap_Books_Process&amp;diff=1807"/>
		<updated>2025-03-09T21:40:14Z</updated>

		<summary type="html">&lt;p&gt;Beta: Copied from Bitrix24 Wiki&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Accounting]] &lt;br /&gt;
[[Category:Bookkeeping]]&lt;br /&gt;
&lt;br /&gt;
=Namecheap=&lt;br /&gt;
&lt;br /&gt;
==Downloading Invoices==&lt;br /&gt;
&lt;br /&gt;
#Log into Namecheap.&lt;br /&gt;
#Go to &#039;&#039;&#039;Profile&#039;&#039;&#039;.&lt;br /&gt;
#Go to &#039;&#039;&#039;Billing&#039;&#039;&#039;.&lt;br /&gt;
#Select &#039;&#039;&#039;Orders&#039;&#039;&#039;.&lt;br /&gt;
#&#039;&#039;&#039;Use the calendar to select a relevant date range.&#039;&#039;&#039;&lt;br /&gt;
#Choose the drop-down arrow next to &#039;&#039;&#039;Details&#039;&#039;&#039;.&lt;br /&gt;
#Select &#039;&#039;&#039;Download PDF&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Downloading Payment Confirmation==&lt;br /&gt;
&lt;br /&gt;
#From the &#039;&#039;&#039;Billing&#039;&#039;&#039; page, select &#039;&#039;&#039;Transactions&#039;&#039;&#039;.&lt;br /&gt;
#&#039;&#039;&#039;Use the calendar to select a relevant date range.&#039;&#039;&#039;&lt;br /&gt;
#Click &#039;&#039;&#039;Details&#039;&#039;&#039;.&lt;br /&gt;
#Click &#039;&#039;&#039;Download&#039;&#039;&#039;.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=BST_-_DIDforSale_Invoice_Interpretation&amp;diff=1806</id>
		<title>BST - DIDforSale Invoice Interpretation</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=BST_-_DIDforSale_Invoice_Interpretation&amp;diff=1806"/>
		<updated>2025-03-09T20:10:49Z</updated>

		<summary type="html">&lt;p&gt;Beta: Copied from Bitrix24 Wiki&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=DIDforSale Invoice Interpretation=&lt;br /&gt;
&lt;br /&gt;
The invoices we get from DIDforSale (our phone provider) are confusing. This document is a guide to correctly interpreting and filing them.&lt;br /&gt;
&lt;br /&gt;
Much of the confusion stems from their billing model (the rest is from bad invoice design). We pay a fixed amount each month (currently $1.09) for our phone number, plus some amount per minute. On the first of each month, they assess the fixed charges and an estimated usage charge based on usage in the previous month. On each invoice, we receive a credit for the estimated usage we were charged in the previous month and are then charged for our actual usage in that month. The invoice also shows the fixed charges and estimated usage charge for the month on the invoice.&lt;br /&gt;
&lt;br /&gt;
==File the Invoices into Evernote==&lt;br /&gt;
&lt;br /&gt;
Before interpreting the invoices, you should file them into Evernote because it&#039;s easier to interpret them in the context of the prior and following months.&lt;br /&gt;
&lt;br /&gt;
#Open the &#039;&#039;&#039;Receipts and Payables&#039;&#039;&#039; notebook in Evernote.&lt;br /&gt;
#Filter it to the &#039;&#039;&#039;DIDforSale&#039;&#039;&#039; tag.&lt;br /&gt;
#Sort by created date descending.&lt;br /&gt;
#Download the invoices using the following section’s instructions.&lt;br /&gt;
&lt;br /&gt;
===Download Invoices===&lt;br /&gt;
&lt;br /&gt;
#Use LastPass to log in to the DIDforSale website at https://portal.didforsale.com/.&lt;br /&gt;
#Go to the [https://portal.didforsale.com/account/invoices invoices page] by hovering &#039;&#039;&#039;Account&#039;&#039;&#039; in the header and clicking &#039;&#039;&#039;Invoices&#039;&#039;&#039;.&lt;br /&gt;
#The [https://portal.didforsale.com/account/invoices invoices page] contains a list of downloadable invoice files, newest first. Download all files for the time period you need (both &amp;lt;code&amp;gt;.txt&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;.pdf&amp;lt;/code&amp;gt;) because they’re all needed.&lt;br /&gt;
&lt;br /&gt;
====The file types:====&lt;br /&gt;
*&#039;&#039;&#039;YYYY-MM_Invoice.pdf&#039;&#039;&#039; - A PDF with an overview of the account activity for the preceding month.&lt;br /&gt;
*&#039;&#039;&#039;YYYY-MM_Monthly-Charge-Detail.txt&#039;&#039;&#039; - A detailed list of the recurring charges for the preceding month in plain text.&lt;br /&gt;
&lt;br /&gt;
===Download CDR Reports===&lt;br /&gt;
&lt;br /&gt;
#To get to the CDR Reports page, hover &#039;&#039;&#039;Reporting&#039;&#039;&#039; in the header and click &#039;&#039;&#039;CDR&#039;&#039;&#039;.&lt;br /&gt;
#Click &#039;&#039;&#039;Show Advanced Search&#039;&#039;&#039;.&lt;br /&gt;
#Use the advanced search to find call information that occurred. You can only download a file for a 30-day period.&lt;br /&gt;
#When you have a month with calls, click &#039;&#039;&#039;Download as CSV&#039;&#039;&#039; at the bottom of the page.&lt;br /&gt;
#Repeat steps 3-4 until you have files for every month which had calls.&lt;br /&gt;
&lt;br /&gt;
This details each call that occurred during that month. The file will be missing for any month in which no calls were made. Note that the date on these files is the month in which the calls occurred, so they go with the invoice from the following month.&lt;br /&gt;
&lt;br /&gt;
===Build the Evernote Note===&lt;br /&gt;
&lt;br /&gt;
This must be done in Evernote for Windows. The Web client is missing necessary features. For each month that doesn’t already have a note:&lt;br /&gt;
&lt;br /&gt;
#Create a note titled &#039;&#039;&#039;DIDforSale Invoice YYYY-MM-01 $X.XX&#039;&#039;&#039; where &#039;&#039;&#039;YYYY-MM&#039;&#039;&#039; is the year and month and &#039;&#039;&#039;$X.XX&#039;&#039;&#039; is the total charges for that month. When you first create the note, you don’t know the total charges, so leave that part off.&lt;br /&gt;
#Tag the note &#039;&#039;&#039;DIDforSale&#039;&#039;&#039; and &#039;&#039;&#039;receipt&#039;&#039;&#039;.&lt;br /&gt;
#At the top of the note is a table summarizing the changes to the prepaid account balance for the month. Copy the table from an existing month.&lt;br /&gt;
#Below the table, attach the invoice PDF for the month in question.&lt;br /&gt;
#Below the invoice, attach the monthly charge detail, which will insert it as text in the note. Select that text and click the &#039;&#039;&#039;Code Block&#039;&#039;&#039; button in the formatting toolbar.&lt;br /&gt;
#Do the same with the CDR report for the prior month, or enter &#039;&#039;&#039;[no calls this month]&#039;&#039;&#039; if none exists.&lt;br /&gt;
#Update the created date of the note to match the date in the title.&lt;br /&gt;
&lt;br /&gt;
==Interpret the Invoices==&lt;br /&gt;
&lt;br /&gt;
===Using the spreadsheet===&lt;br /&gt;
&lt;br /&gt;
It’s not perfect, but it’s fast and mostly brainless compared to figuring it out manually.&lt;br /&gt;
&lt;br /&gt;
#Open the &#039;&#039;&#039;DIDforSale.xlsx&#039;&#039;&#039; file from the BST Dropbox.&lt;br /&gt;
#Copy the most recent tab and rename it to the invoice you want to interpret.&lt;br /&gt;
#Open the PDF for the invoice you need a charge for.&lt;br /&gt;
#Copy everything from &#039;&#039;&#039;Last Month Details&#039;&#039;&#039; to the bottom of the charge table.&lt;br /&gt;
#Right-click on cell A3 and paste &#039;&#039;&#039;without formatting&#039;&#039;&#039;.&lt;br /&gt;
#If there are any extra rows at the bottom, remove the extra information in column A.&lt;br /&gt;
#Your total is next to &#039;&#039;&#039;Net Charges&#039;&#039;&#039; in cell E11.&lt;br /&gt;
&lt;br /&gt;
====Troubleshooting:====&lt;br /&gt;
Sometimes Cell &#039;&#039;&#039;B&#039;&#039;&#039; gives an error. This is due to how it actually finds the substring in column A that is the dollar value. You probably pasted it right, but the formula needs more tweaking. Sorry about that. =(&lt;br /&gt;
&lt;br /&gt;
===Manually===&lt;br /&gt;
&lt;br /&gt;
First, examine the summary table at the top of the note, which looks like this:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Charge Type!!Change!!Running Balance&lt;br /&gt;
|-&lt;br /&gt;
|Starting Balance|| ||22.03&lt;br /&gt;
|-&lt;br /&gt;
|Last Month Payments||+0.00||22.03&lt;br /&gt;
|-&lt;br /&gt;
|Last Month Estimated Usage||+0.00||22.03&lt;br /&gt;
|-&lt;br /&gt;
|Last Month Actual Usage||-0.01||22.02&lt;br /&gt;
|-&lt;br /&gt;
|This Month Fixed Charges||-1.09||20.93&lt;br /&gt;
|-&lt;br /&gt;
|This Month Estimated Usage||-0.01||&#039;&#039;&#039;20.91&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|Net Charges||&#039;&#039;&#039;1.11&#039;&#039;&#039;||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This table summarizes the various charges and credits that can affect our prepaid account balance in a given month. The right-hand column is a running balance.&lt;br /&gt;
&lt;br /&gt;
==Entering into Kashoo==&lt;br /&gt;
&lt;br /&gt;
The invoices can be entered just by duplicating the last invoice and updating the amount and date. Don’t enter any payment information for them.&lt;br /&gt;
&lt;br /&gt;
===Entering Prepayments===&lt;br /&gt;
&lt;br /&gt;
#Go to &#039;&#039;&#039;Bills to Pay&#039;&#039;&#039; on the left.&lt;br /&gt;
#Click the &#039;&#039;&#039;Enter Bill for Payment&#039;&#039;&#039; tab.&lt;br /&gt;
#Change the supplier to &#039;&#039;&#039;DIDforSale&#039;&#039;&#039;.&lt;br /&gt;
#Paid From is probably PayPal (NOTE: you probably need to enter a transfer from Bank of the West to PayPal for the same date!).&lt;br /&gt;
#Update the date appropriately.&lt;br /&gt;
#Select the &#039;&#039;&#039;Prepaid Expenses&#039;&#039;&#039; account.&lt;br /&gt;
#Enter the amount of the payment; the total should update.&lt;br /&gt;
#Click &#039;&#039;&#039;Add Payment&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
You should be able to use this page to apply the payment to any open bills that exist at this time. Otherwise, use the following section to apply the payment at any point.&lt;br /&gt;
&lt;br /&gt;
===Paying Bills from Prepayment===&lt;br /&gt;
&lt;br /&gt;
#Go to &#039;&#039;&#039;Accounts&#039;&#039;&#039; on the left.&lt;br /&gt;
#Click &#039;&#039;&#039;1400 Prepaid Expenses&#039;&#039;&#039;.&lt;br /&gt;
#Scroll down the list and find the most recent prepayment.&lt;br /&gt;
#Click the &#039;&#039;&#039;Bill Payment #00###&#039;&#039;&#039; link.&lt;br /&gt;
#&#039;&#039;&#039;IMPORTANT:&#039;&#039;&#039; Note what the Total says at the bottom.&lt;br /&gt;
#Click the &#039;&#039;&#039;&amp;gt;&amp;gt;&#039;&#039;&#039; chevrons to move the balance of the open bills to this prepayment as appropriate.&lt;br /&gt;
#Update the Total to be what it was (if it started out at $25, it probably increased as you applied payment, reset it to $25).&lt;br /&gt;
#Click &#039;&#039;&#039;Save&#039;&#039;&#039;.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1805</id>
		<title>Staff Snack Preferences</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1805"/>
		<updated>2024-11-07T21:38:49Z</updated>

		<summary type="html">&lt;p&gt;Beta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When buying food at costco for staff:&lt;br /&gt;
&lt;br /&gt;
=== Yes ===&lt;br /&gt;
&lt;br /&gt;
* Hello Panda&lt;br /&gt;
* Choco Mushrooms&lt;br /&gt;
* Kirkland brand Nut Bar&lt;br /&gt;
* Black Forest Gummy Bears&lt;br /&gt;
* Skinny Pop&lt;br /&gt;
* Trail Mix&lt;br /&gt;
* Apple Sauce&lt;br /&gt;
* The weird flavored apple sauce: &amp;quot;Fruit and Vegetable Pouches&amp;quot; (surprisingly tasty and a healthy addition)&lt;br /&gt;
&lt;br /&gt;
=== No ===&lt;br /&gt;
&lt;br /&gt;
* Chips and cracker packs don&#039;t get eaten enough to warrant the amount left at the end&lt;br /&gt;
* Kirkland chocolate chip soft &amp;amp; chewy granola bar, there were a ton left over&lt;br /&gt;
* those weird oat chocolate chip muffin-like things&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stick to one box each of things, even if you think we should buy more. It never seems like enough, and then we have a bunch left over&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1804</id>
		<title>Staff Snack Preferences</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1804"/>
		<updated>2024-11-07T20:18:51Z</updated>

		<summary type="html">&lt;p&gt;Beta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When buying food at costco for staff:&lt;br /&gt;
&lt;br /&gt;
=== Yes ===&lt;br /&gt;
&lt;br /&gt;
* Hello Panda&lt;br /&gt;
* Choco Mushrooms&lt;br /&gt;
* Kirkland brand Nut Bar&lt;br /&gt;
* Black Forest Gummy Bears&lt;br /&gt;
* Skinny Pop&lt;br /&gt;
* Trail Mix&lt;br /&gt;
* Apple Sauce&lt;br /&gt;
* The weird flavored apple sauce: &amp;quot;Fruit and Vegetable Pouches&amp;quot; (surprisingly tasty and a healthy addition)&lt;br /&gt;
&lt;br /&gt;
=== No ===&lt;br /&gt;
&lt;br /&gt;
* Chips and cracker packs don&#039;t get eaten enough to warrant the amount left at the end&lt;br /&gt;
* Those other granola bars (update here when found), there were a ton left over&lt;br /&gt;
* those weird oat chocolate chip muffin-like things&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Stick to one box each of things, even if you think we should buy more. It never seems like enough, and then we have a bunch left over&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1803</id>
		<title>Staff Snack Preferences</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1803"/>
		<updated>2024-11-07T20:18:02Z</updated>

		<summary type="html">&lt;p&gt;Beta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When buying food at costco for staff:&lt;br /&gt;
&lt;br /&gt;
=== Yes ===&lt;br /&gt;
&lt;br /&gt;
* Hello Panda&lt;br /&gt;
* Choco Mushrooms&lt;br /&gt;
* Kirkland brand Nut Bar&lt;br /&gt;
* Black Forest Gummy Bears&lt;br /&gt;
* Skinny Pop&lt;br /&gt;
* Trail Mix&lt;br /&gt;
* Apple Sauce&lt;br /&gt;
* The weird flavored apple sauce: &amp;quot;Fruit and Vegetable Pouches&amp;quot; (surprisingly tasty and a healthy addition)&lt;br /&gt;
&lt;br /&gt;
=== No ===&lt;br /&gt;
&lt;br /&gt;
* Chips and cracker packs don&#039;t get eaten enough to warrant the amount left at the end&lt;br /&gt;
* Those other granola bars (update here when found), there were a ton left over&lt;br /&gt;
* those weird oat chocolate chip muffin-like things&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1802</id>
		<title>Staff Snack Preferences</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1802"/>
		<updated>2024-11-07T20:12:06Z</updated>

		<summary type="html">&lt;p&gt;Beta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When buying food at costco for staff:&lt;br /&gt;
&lt;br /&gt;
=== Yes ===&lt;br /&gt;
&lt;br /&gt;
* Hello Panda&lt;br /&gt;
* Choco Mushrooms&lt;br /&gt;
* Kirkland brand Nut Bar&lt;br /&gt;
* Black Forest Gummy Bears&lt;br /&gt;
* Skinny Pop&lt;br /&gt;
* Trail Mix&lt;br /&gt;
* Apple Sauce&lt;br /&gt;
* The weird flavored apple sauce (surprisingly tasty and a healthy addition)&lt;br /&gt;
&lt;br /&gt;
=== No ===&lt;br /&gt;
&lt;br /&gt;
* Chips and cracker packs don&#039;t get eaten enough to warrant the amount left at the end&lt;br /&gt;
* Those other granola bars (update here when found), there were a ton left over&lt;br /&gt;
* those weird oat chocolate chip muffin-like things&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1801</id>
		<title>Staff Snack Preferences</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Staff_Snack_Preferences&amp;diff=1801"/>
		<updated>2024-11-07T20:11:01Z</updated>

		<summary type="html">&lt;p&gt;Beta: started page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;When buying food at costco for staff:&lt;br /&gt;
&lt;br /&gt;
=== Yes ===&lt;br /&gt;
&lt;br /&gt;
* Hello Panda&lt;br /&gt;
* Choco Mushrooms&lt;br /&gt;
* Kirkland brand Nut Bar&lt;br /&gt;
* Black Forest Gummy Bears&lt;br /&gt;
* Skinny Pop&lt;br /&gt;
* Trail Mix&lt;br /&gt;
* Apple Sauce&lt;br /&gt;
* The weird flavored apple sauce (surprisingly tasty and a healthy addition)&lt;br /&gt;
&lt;br /&gt;
=== No ===&lt;br /&gt;
&lt;br /&gt;
* Chips and cracker packs don&#039;t get eaten enough to warrant the amount left at the end&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1800</id>
		<title>2024 Meeting Notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1800"/>
		<updated>2024-10-29T06:34:06Z</updated>

		<summary type="html">&lt;p&gt;Beta: add 2024-10-26 staff meeting notes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Staff Meeting Summary 2024-06-22 ==&lt;br /&gt;
&lt;br /&gt;
=== Convention Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Announcement:&#039;&#039;&#039;&lt;br /&gt;
** We&#039;re having a convention! The contract is signed with the &#039;&#039;&#039;Reno Sparks Convention Center&#039;&#039;&#039; for a &#039;&#039;&#039;Nov 1-3&#039;&#039;&#039; convention. We have the space from Wednesday to Monday.&lt;br /&gt;
* &#039;&#039;&#039;Website and Registration:&#039;&#039;&#039;&lt;br /&gt;
** Convention dates updated on the website.&lt;br /&gt;
** Additional updates needed.&lt;br /&gt;
** General registration expects to open by the end of the weekend.&lt;br /&gt;
** Staff registration will open alongside general registration, even without the staff contract being ready.&lt;br /&gt;
** Staff contract is being worked on by Natasha.&lt;br /&gt;
* &#039;&#039;&#039;Need for Staff:&#039;&#039;&#039;&lt;br /&gt;
** Emphasis on the need for more staff.&lt;br /&gt;
** Encouragement for current staff to recruit friends.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introduction of New Staff Member:&#039;&#039;&#039;&lt;br /&gt;
** TheUltimateDragon (William) introduced as the new head of the game room.&lt;br /&gt;
** Plans to involve the local fighting game community, with 20 to 30 active members.&lt;br /&gt;
&lt;br /&gt;
=== Department Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Game Room Logistics:&#039;&#039;&#039;&lt;br /&gt;
** William plans to bring in his community for the game room.&lt;br /&gt;
** Discussion on the availability of consoles and other equipment. We may need to source consoles.&lt;br /&gt;
* &#039;&#039;&#039;Separation of Main Stage and Gaming Areas:&#039;&#039;&#039;&lt;br /&gt;
** Main stage and gaming areas will be separated at the new venue.&lt;br /&gt;
* &#039;&#039;&#039;Beta&#039;s Role Change:&#039;&#039;&#039;&lt;br /&gt;
** John has stepped down as vice chair and gaming head.&lt;br /&gt;
** Beta has stepped down as vice chair and is stepping back from some responsibilities. &lt;br /&gt;
** Beta&#039;s focus will largely be on continuous improvement and documentation to streamline processes.&lt;br /&gt;
** Tim is now a vice chair and will be more involved in ensuring tasks are completed.&lt;br /&gt;
* &#039;&#039;&#039;Recognition of Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Cupcake Doll recognized for consistent efforts in keeping things moving.&lt;br /&gt;
&lt;br /&gt;
=== Pricing and Budget ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Weekend passes likely $60.&lt;br /&gt;
** Individual day passes expected to be $30, with possible higher price for Saturday.&lt;br /&gt;
* &#039;&#039;&#039;Vendor Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Vendor table prices will increase slightly.&lt;br /&gt;
* &#039;&#039;&#039;Prize Procurement:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on handling prizes for the convention.&lt;br /&gt;
** Tighter budget than usual this year, need for smart procurement.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotion ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Urgent need to start marketing the convention.&lt;br /&gt;
** Plans to distribute business cards and possibly larger flyers or posters.&lt;br /&gt;
* &#039;&#039;&#039;RAGECON Presence:&#039;&#039;&#039;&lt;br /&gt;
** Potential for having a table at RAGECON to promote the convention.&lt;br /&gt;
** Discussion on staffing the table and badges.&lt;br /&gt;
* &#039;&#039;&#039;Community Engagement:&#039;&#039;&#039;&lt;br /&gt;
** Importance of engaging with the local community through various events.&lt;br /&gt;
&lt;br /&gt;
=== Social Media and Streaming ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Social Media Activity:&#039;&#039;&#039;&lt;br /&gt;
** Current presence on Facebook and Twitter (X).&lt;br /&gt;
** Need to boost activity on these platforms.&lt;br /&gt;
* &#039;&#039;&#039;Streaming Ideas:&#039;&#039;&#039;&lt;br /&gt;
** Streaming tournaments and other events to generate hype.&lt;br /&gt;
** Use of Twitch and YouTube for streaming and promoting the convention.&lt;br /&gt;
* &#039;&#039;&#039;Social Media Management:&#039;&#039;&#039;&lt;br /&gt;
** Fae offered to help with social media posts and engagement.&lt;br /&gt;
** Discussion on using Social Pilot for automated posts, with manual posts for Instagram.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New Venue Details:&#039;&#039;&#039;&lt;br /&gt;
** New venue is the convention center, more expensive but possibly a better fit.&lt;br /&gt;
** Concerns about lighting at the new venue and potential solutions.&lt;br /&gt;
* &#039;&#039;&#039;Security Requirements:&#039;&#039;&#039;&lt;br /&gt;
** Need to hire ESI security, details still unclear.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Communication and Collaboration:&#039;&#039;&#039;&lt;br /&gt;
** Encouragement for effective communication and collaboration.&lt;br /&gt;
** Importance of being proactive in managing tasks and responsibilities.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-07-14 ==&lt;br /&gt;
&lt;br /&gt;
=== Welcome and Introduction ===&lt;br /&gt;
&lt;br /&gt;
* The meeting was initiated to discuss updates and plans for SNAFU Con, emphasizing the importance of recruiting more staff.&lt;br /&gt;
&lt;br /&gt;
=== Website and Marketing Updates ===&lt;br /&gt;
&lt;br /&gt;
* The website is nearly ready for directing traffic, with social media updates to follow soon.&lt;br /&gt;
* Business card-sized flyers are ready, and 4x6 flyers are being prepared for distribution.&lt;br /&gt;
* Marketing efforts are expected to kick off in August. Flyers and posters will be distributed at local nerdy businesses.&lt;br /&gt;
* Posters will be available closer to the event, no later than the con book release.&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Conventions and Events ===&lt;br /&gt;
&lt;br /&gt;
* A list of upcoming conventions and events was provided to schedule possible promotional efforts:&lt;br /&gt;
** August 16-18: GalaxyCon San Jose&lt;br /&gt;
** August 17-18: Con for a Cause (formerly Aerie-Con) in Reno&lt;br /&gt;
** August 30-Sept 1: SacAnime&lt;br /&gt;
** September 7-10: Kaboom Con in Carson City&lt;br /&gt;
** October 14-17: BLFC at GSR&lt;br /&gt;
** October 26-27: YumeConUSA in San Jose&lt;br /&gt;
** November 2-3: Reno Toy Con at GSR&lt;br /&gt;
* Additional local events and new shops were suggested as potential flyer distribution points.&lt;br /&gt;
** Kobold’s Keep in Reno&lt;br /&gt;
** New shop in Sparks called &amp;quot;The Coffer&amp;quot;&lt;br /&gt;
** Warhammer store at Summit&lt;br /&gt;
* Cosplay meetups and other geek clubs were identified as good opportunities for promotion.&lt;br /&gt;
** Local libraries often have anime and gaming clubs that could be reached out to for promotion.&lt;br /&gt;
** South Reno Library, which has regular Pokémon days for kids.&lt;br /&gt;
** Cosplay for Kindness, a group that runs various events in town and was suggested for potential collaboration.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment and Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Emphasis on the prompt signing of staff contracts to avoid last year&#039;s issues.&lt;br /&gt;
* Encouragement for staff to recruit friends and acquaintances to join the team.&lt;br /&gt;
* Discussion on the contract checking process using the existing HR system. (We have to actually make phone calls again to catch stragglers.)&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Plans ===&lt;br /&gt;
&lt;br /&gt;
* The new convention layout at the Reno-Sparks Convention Center was discussed, including the need for large signs to guide attendees.&lt;br /&gt;
* We have all of C, D and E rooms.&lt;br /&gt;
* Initial maps were shared, highlighting the layout of C and D halls and the ballroom for vendors and artists.&lt;br /&gt;
* Focus on controlling badge points and managing the flow of attendees.&lt;br /&gt;
** We expect to need 5 badge controlled spots &lt;br /&gt;
&lt;br /&gt;
=== Food and Concessions ===&lt;br /&gt;
&lt;br /&gt;
* Concerns were raised about the availability of substantial food options at the venue.&lt;br /&gt;
** If you have a request for the concessions stand, send it to Tim.&lt;br /&gt;
** Coordination with Aramark for concessions and the possibility of vendors providing snacks were discussed.&lt;br /&gt;
&lt;br /&gt;
=== Merchants and Artist Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Merchant and artist contracts are in progress and will be opened soon.&lt;br /&gt;
* A first-come, first-serve approach was proposed for artist alley applications.&lt;br /&gt;
* Emphasis on adhering to city deadlines for paperwork submission.&lt;br /&gt;
** City deadline is now 30 days before con instead of the 15 day deadline we used to have.&lt;br /&gt;
&lt;br /&gt;
=== Partnering with Local Organizations ===&lt;br /&gt;
&lt;br /&gt;
* Plans to reach out to local professors, science museums, and other educational organizations for panel presentations and partnerships.&lt;br /&gt;
* Contact with the Discovery Museum for potential collaboration was initiated.&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* At least one future in-person meeting will be held at libraries to facilitate face-to-face interactions. Possibly more.&lt;br /&gt;
* Potential venues for these meetings include South Valleys Library and Sparks Library.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* Updates on social media graphics and preparations for the convention were shared.&lt;br /&gt;
* A press release will be drafted following the guidelines on the SNAFU Con wiki.&lt;br /&gt;
* Reminder to be cautious about staff burnout and to maintain a balanced workload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - In Person Meeting 2024-08-10 ==&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Meeting Issues:&#039;&#039;&#039;&lt;br /&gt;
** Attendance was taken manually due to errors in logging into the system.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introductions:&#039;&#039;&#039;&lt;br /&gt;
** Staff members introduced themselves, their roles, and their previous experience with the convention.&lt;br /&gt;
&lt;br /&gt;
=== Event Planning and Roles ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing:&#039;&#039;&#039;&lt;br /&gt;
** There are several open positions that need to be filled.&lt;br /&gt;
** Current staff are encouraged to take on multiple roles due to the shortage.&lt;br /&gt;
** Beta is stepping back but will still assist with HR, graphics, documentation, and continual improvement.&lt;br /&gt;
** The chair is Tim, who will oversee various departments and tasks.&lt;br /&gt;
** Registration and contract signing for staff will be done online, with no in-person signings allowed.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Layout:&#039;&#039;&#039;&lt;br /&gt;
** Overview of the venue layout:&lt;br /&gt;
*** Artist Alley and Vendor spaces will be located in D1-D3 ballrooms.&lt;br /&gt;
*** E1-E3 for video gaming, E9-E10 for tabletop gaming.&lt;br /&gt;
*** Main stage, panels, cosplay, and manga library also mapped out.&lt;br /&gt;
** Discussions on the potential need for more lighting in certain rooms, particularly for the Artist Alley.&lt;br /&gt;
** A walkthrough is needs to be scheduled to assess lighting and other venue specifics.&lt;br /&gt;
** Badge control points and door management will be 5 points this year due to venue layout. We may be able to use ESI for two of them.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Features ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Room:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is the new head of the gaming room and is planning a retro gaming corner.&lt;br /&gt;
** The retro gaming corner will feature classic consoles like PS2, SNES Classic, etc.&lt;br /&gt;
** A tournament is being planned, potentially requiring more PS5 consoles.&lt;br /&gt;
** Volunteers are needed to help with the gaming room.&lt;br /&gt;
** A spreadsheet may be created to track who is bringing what equipment (consoles, TVs, etc.).&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Artist Alley and Vendor Contracts:&#039;&#039;&#039;&lt;br /&gt;
** Artist Alley and Vendor space has been slightly reduced&lt;br /&gt;
** Contracts are almost ready, pending some final details.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Cosplay:&#039;&#039;&#039;&lt;br /&gt;
** The main lobby area and ballroom lobby are potential spaces for cosplay meetups.&lt;br /&gt;
** Discussion on the benefits of high visibility areas for cosplay meetups.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Initiatives:&#039;&#039;&#039;&lt;br /&gt;
** There is a strong need for increased marketing due to the new venue and the desire to attract a larger audience.&lt;br /&gt;
** Social media efforts need to ramp up, with plans to highlight artists, vendors, and panels.&lt;br /&gt;
** There is a call for everyone to contribute to marketing, especially on social media.&lt;br /&gt;
** Short science videos and other creative content ideas were discussed as potential marketing tools.&lt;br /&gt;
** Plans to advertise on local event pages, including Nevada Appeal and RGJ Events.&lt;br /&gt;
** Potential collaboration with other local events (e.g., toy fair, punk rock market) to cross-promote.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Outreach to Other Communities:&#039;&#039;&#039;&lt;br /&gt;
** UNR (University of Nevada, Reno) clubs and groups are potential targets for outreach.&lt;br /&gt;
** Suggestions to connect with local businesses like Cap&#039;n Games for retro gaming partnerships.&lt;br /&gt;
** Discussed using UNR’s radio station and event calendars for advertising.&lt;br /&gt;
&lt;br /&gt;
=== Other Discussions ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Venue Logistics:&#039;&#039;&#039;&lt;br /&gt;
** Badge-controlled areas were discussed, and it&#039;s determined that certain doors may be monitored by ESI security.&lt;br /&gt;
** Seating arrangements and areas for interactive activities (like doodle tables) were considered. We may be able to put them out in the main venue space.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Miscellaneous:&#039;&#039;&#039;&lt;br /&gt;
** Questions were raised about the availability and acquisition of CRTs (for retro gaming), with some potential leads mentioned.&lt;br /&gt;
** Mention of potential storage issues if the con were to acquire CRTs.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Next Steps:&#039;&#039;&#039;&lt;br /&gt;
** Finalization of contracts and opening up vendor applications.&lt;br /&gt;
** Continued efforts in staff recruitment and training.&lt;br /&gt;
** Preparation for the next walkthrough of the venue.&lt;br /&gt;
** Further development of marketing strategies, including social media engagement and partnerships.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Mingle Time:&#039;&#039;&#039;&lt;br /&gt;
** After the meeting, there was a designated time for staff to network and discuss roles and tasks further.&lt;br /&gt;
&lt;br /&gt;
=== Closing Remarks ===&lt;br /&gt;
&lt;br /&gt;
* The meeting concluded with an open call for any additional questions or ideas from the attendees.&lt;br /&gt;
* Those interested in specific roles or tasks were encouraged to speak with Tim or other department heads.&lt;br /&gt;
&lt;br /&gt;
The meeting wrapped up with a reminder that continued collaboration and communication will be key as the convention date approaches.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-08-30 ==&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Inventory ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Inventory Day&#039;&#039;&#039;:&lt;br /&gt;
** Scheduled for September 8 at 9:00 AM.&lt;br /&gt;
** Volunteers are needed; early arrival (8:00 AM) is encouraged, though not mandatory.&lt;br /&gt;
** Tasks: The inventory process involves pulling everything out of the storage unit, counting, and then putting it back.&lt;br /&gt;
** Inventory Sheets: There are existing inventory sheets that have been used for the past few years. These may need updating.&lt;br /&gt;
** Digital vs. Paper Inventory: Discussion on whether to digitize the inventory process using phones or continue using paper due to previous difficulties with digital attempts. Currently remaining with paper but will review. &lt;br /&gt;
** Volunteer Roles: More volunteers are needed for the logistics department to help with inventory.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Flyers and Posters:&#039;&#039;&#039;&lt;br /&gt;
** Posters have been ordered and are expected to arrive in about two weeks.&lt;br /&gt;
** &#039;&#039;&#039;Distribution:&#039;&#039;&#039; Cupcakedoll is actively distributing flyers across various locations. Others are encouraged to do the same once more flyers are available.&lt;br /&gt;
** &#039;&#039;&#039;Flier Locations:&#039;&#039;&#039; Noted that some locations, like Game Kastle, might be less receptive to flyers.&lt;br /&gt;
** &#039;&#039;&#039;Other Conventions:&#039;&#039;&#039; Suggestions to advertise at other conventions.&lt;br /&gt;
* &#039;&#039;&#039;Social Media:&#039;&#039;&#039; There is a need to increase social media activity to promote the convention further.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Department Leadership:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is leading the gaming department &lt;br /&gt;
** Support from other staff members is assured.&lt;br /&gt;
* &#039;&#039;&#039;CRT and Console Rentals:&#039;&#039;&#039;&lt;br /&gt;
** Efforts are being made to source CRT TVs for the gaming tournaments.&lt;br /&gt;
** &#039;&#039;&#039;Contacts:&#039;&#039;&#039; Attempts to contact Abe, who may have CRTs, and explore rental options at Cap and Games.&lt;br /&gt;
** &#039;&#039;&#039;Consoles:&#039;&#039;&#039; There’s a need for 20-25 consoles for a tournament, with current availability being around 12-15.&lt;br /&gt;
** &#039;&#039;&#039;Challenges:&#039;&#039;&#039; Securing enough consoles to avoid the tournament running late is a significant concern. Without enough consoles, running the tournament may not be feasible.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer Consoles:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on how to incentivize people to lend their consoles for the event.&lt;br /&gt;
** &#039;&#039;&#039;Suggestions:&#039;&#039;&#039; Offering volunteer hours as a percentage discount on badges in exchange for console loans.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Coordination ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing Needs:&#039;&#039;&#039;&lt;br /&gt;
** There’s a push to have more people sign up for staff roles, with a reminder that the convention is about two months away.&lt;br /&gt;
** &#039;&#039;&#039;Volunteer Roles:&#039;&#039;&#039; The convention still needs volunteers across various departments, including programming, registration, and general staffing roles.&lt;br /&gt;
** &#039;&#039;&#039;Benefits:&#039;&#039;&#039; Volunteers can get their badge cost refunded after completing 12 hours of work, with a prorated refund available for fewer hours.&lt;br /&gt;
** &#039;&#039;&#039;Recruitment&#039;&#039;&#039;: Staff members are encouraged to recruit friends and community members to volunteer.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer and Staff Contracts:&#039;&#039;&#039;&lt;br /&gt;
** A reminder that staff contracts need to be completed as soon as possible to finalize roles.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Concerns ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Center Walkthrough:&#039;&#039;&#039;&lt;br /&gt;
** There’s a need to schedule a walkthrough of the new convention center to address concerns, particularly regarding lighting.&lt;br /&gt;
* &#039;&#039;&#039;Main Stage Lighting:&#039;&#039;&#039;&lt;br /&gt;
** Concerns were raised about the quality of lighting on the main stage, as poor lighting affected photography during the previous year.&lt;br /&gt;
** &#039;&#039;&#039;Solutions:&#039;&#039;&#039; Potential solutions include renting or purchasing LED lights to improve the stage lighting.&lt;br /&gt;
* &#039;&#039;&#039;Layout Planning:&#039;&#039;&#039;&lt;br /&gt;
** The layout for the convention spaces needs to be finalized and submitted to the venue. A draft of the main space layout is ready, but other rooms still need to be organized.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Nervousness and Excitement:&#039;&#039;&#039;&lt;br /&gt;
** Several staff members expressed a mix of excitement and nervousness about the upcoming convention, especially given the new venue and leadership roles.&lt;br /&gt;
** &#039;&#039;&#039;Encouragement:&#039;&#039;&#039; The leadership team encouraged everyone to communicate their concerns and offered support to ensure a successful event.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-09-21 ==&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* Meeting Space Issues&lt;br /&gt;
** The original meeting room was unavailable due to backstock, so the team had to relocate to a smaller space.&lt;br /&gt;
** Ongoing technical difficulties with the audio setup and Discord transcription services.&lt;br /&gt;
* Reno-Sparks Convention Center&lt;br /&gt;
** Event dates: November 1-3, 2024, with Day Zero starting on October 31, 2024.&lt;br /&gt;
** Venue address: 4590 S Virginia St, Reno, NV 89502.&lt;br /&gt;
* CRT Monitors for Gaming&lt;br /&gt;
** A query was raised regarding obtaining CRT monitors for retro gaming, with a potential deal to borrow them for free since SNAFU Con originally provided them.&lt;br /&gt;
** William (Derp) is coordinating with Skyline to finalize the monitor logistics, and a pickup date will be determined soon.&lt;br /&gt;
* Convention Layout and Hallways&lt;br /&gt;
** The convention hallways are significantly large, providing ample space for setup, including planned conversation pods for attendees to rest.&lt;br /&gt;
** There will be cars from a display that the venue would like to keep there. One car might need to be moved, but overall, it’s not considered a major issue.&lt;br /&gt;
* Table Setup and Placement&lt;br /&gt;
** Artist Alley and vendor spaces are being optimized. There was discussion about avoiding the obstruction of key views by the pipe and drape for guest tables. Possible solutions include:&lt;br /&gt;
*** Moving guest banners to the front of the tables instead of using pipe and drape.&lt;br /&gt;
* Power and Charging Stations&lt;br /&gt;
** Discussion about including charging stations in conversation pods, but it was clarified that they would not have power access for this year.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* Gaming Console Contributions&lt;br /&gt;
** Derp is finalizing console and game contributions from volunteers. Volunteers should bring one console, 1-2 controllers, and one game per console.&lt;br /&gt;
** There’s a need to coordinate the finalization of hours worked for contributing consoles and the announcement for sign-ups.&lt;br /&gt;
* Retro Gaming Section&lt;br /&gt;
** Retro consoles such as PS3 and Xbox 360 or older will be part of the gaming section, along with unique and rare consoles to appeal to attendees.&lt;br /&gt;
* Tournament Brackets&lt;br /&gt;
** Derp is working on setting up brackets for gaming tournaments and plans to announce the event over the weekend.&lt;br /&gt;
* Magic: The Gathering RCQ Tournament&lt;br /&gt;
** Plans to host a Regional Championship Qualifier (RCQ) for Magic: The Gathering at the convention. This would be a high-level local tournament that could help draw attendees.&lt;br /&gt;
** Special tournament badges will be offered at a discounted price, combining both day passes and tournament entry fees.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotions ===&lt;br /&gt;
&lt;br /&gt;
* Posters and Discount Codes&lt;br /&gt;
** Coordinating the distribution of convention posters across venues and local colleges. Each poster will include a discount code, with CupcakeDoll managing the creation of these codes.&lt;br /&gt;
** Posters should be placed only where they’re welcome, and coordinators should avoid places where they might cause issues.&lt;br /&gt;
* Social Media and Advertising&lt;br /&gt;
** Planning to use social media ads, particularly on Facebook, to promote events like a potential trick-or-treat event during the convention. These targeted ads would aim at drawing in families and younger attendees.&lt;br /&gt;
&lt;br /&gt;
=== Contracts and Signatures ===&lt;br /&gt;
&lt;br /&gt;
* Contract Issues&lt;br /&gt;
** Some contract files lacked signature fields, creating problems for electronic signing. Staff members have submitted as much as they could without signatures.&lt;br /&gt;
** A volunteer contract is being created that should be easily signable.&lt;br /&gt;
&lt;br /&gt;
=== Special Events ===&lt;br /&gt;
&lt;br /&gt;
* Trick-or-Treating Event&lt;br /&gt;
** Discussions around hosting a trick-or-treat event during the convention, where cosplayers hand out candy to children. The event could become a big draw for families.&lt;br /&gt;
** The team is working on getting approval from Aramark.&lt;br /&gt;
* Performance and Guest Events&lt;br /&gt;
** A guest performance featuring singing is planned. Karaoke will not be held on the main stage this year.&lt;br /&gt;
** DJ performances and a dance event are scheduled, with a possibility of integrating a VR dance club portal that connects to a virtual environment. This requires network drops or alternative solutions like Ethernet connections.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Management and Staffing ===&lt;br /&gt;
&lt;br /&gt;
* Logistics and Volunteer Coordination&lt;br /&gt;
** The logistics department is understaffed due to the departure of some department heads. They’re actively recruiting volunteers to handle load-ins, load-outs, and other logistical tasks, particularly for Wednesday and Monday shifts.&lt;br /&gt;
** Efforts are being made to coordinate staff availability for key load-in and load-out days, especially the day before and after the convention.&lt;br /&gt;
* Volunteer Scheduling&lt;br /&gt;
** There is a significant need for volunteers for load-out on Monday, the hardest day to staff. Scheduling posts will be updated in the logistics channel.&lt;br /&gt;
&lt;br /&gt;
=== Video Room and Media Permissions ===&lt;br /&gt;
&lt;br /&gt;
* Issues with Video Permissions&lt;br /&gt;
** The video room coordinator is still working to secure permissions for screenings. Funimation is no longer a reliable source, but requests have been sent to companies like Media Blasters and Discotek.&lt;br /&gt;
** Public domain content may be used as a fallback if no permissions are granted in time.&lt;br /&gt;
* Coordination with Media Blasters&lt;br /&gt;
** A historical note was mentioned about obtaining permissions directly from the founder of Media Blasters using his personal contact details found in a public document.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Topics ===&lt;br /&gt;
&lt;br /&gt;
* Earplugs for Attendees&lt;br /&gt;
** A suggestion was made to provide cheap earplugs at registration if noise pollution between the main stage and vendor area becomes an issue. However, it’s not expected to be a major problem.&lt;br /&gt;
* Workshop Rooms&lt;br /&gt;
** There will be no dedicated workshop rooms, but certain breakout rooms may serve similar functions.&lt;br /&gt;
* Halloween Decorations&lt;br /&gt;
** The team discussed the timing of the convention (right after Halloween) and the difficulty in sourcing Halloween decorations during that period.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - 2024-10-06 ==&lt;br /&gt;
&lt;br /&gt;
=== General Reminders ===&lt;br /&gt;
&lt;br /&gt;
* Staff Sign-ups: Staff members were reminded to sign up for roles, particularly in areas like logistics.&lt;br /&gt;
* Panel Submissions: Urgent reminder to submit panels, with emphasis on finalizing the con schedule soon.&lt;br /&gt;
* Con Book Deadlines: Last call for submitting information (e.g., panel details, logos) for inclusion in the con book. Work on the book is happening this weekend: 10/12.&lt;br /&gt;
* Guest Announcements: Guest information has not been widely announced yet, and marketing needs to expedite this process.&lt;br /&gt;
&lt;br /&gt;
=== Classic Consoles and E-Gaming ===&lt;br /&gt;
&lt;br /&gt;
* Classic Consoles: Staff members need to sign up for this section. The more obscure the console, the better. A thread was linked for sign-ups: https://discord.com/channels/416146296097865729/1279259494236291212&lt;br /&gt;
* Equipment Status: CRT TVs for classic consoles need further confirmation, but PS5s and monitors for other gaming areas are set.&lt;br /&gt;
&lt;br /&gt;
=== Con Book and Map Creation ===&lt;br /&gt;
&lt;br /&gt;
* Map for Tables: Nuriko Windchaser requested a table map layout, which will be completed within the week.&lt;br /&gt;
* Con Book Map: The map for the con book and artist tables will be finalized soon and sent out for review.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Guest Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Guest Promotion: Marketing is behind in promoting confirmed guests, and there&#039;s a need for immediate action to make the guest lineup public.&lt;br /&gt;
* Graphics: Marketing materials are still in progress, and several guest graphics will soon be sent for approval.&lt;br /&gt;
&lt;br /&gt;
=== Cosplayers and Performers ===&lt;br /&gt;
&lt;br /&gt;
* Cosplay Coordination: Discussions are underway to involve both cosplayers and the Buccaneers for day-zero candy distribution. Tim will reach out to both. &lt;br /&gt;
&lt;br /&gt;
=== Hotel and Staff Dorms ===&lt;br /&gt;
&lt;br /&gt;
* Dorm System: Dorms are available for staff at $25 per person per night or $100 for a full room. Staff interested in this option need to contact Beta directly.&lt;br /&gt;
* Affordable Option: This dorm system is significantly cheaper than standard hotel rates, and the convention is absorbing some of the costs to make it affordable for staff.&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Volunteers ===&lt;br /&gt;
&lt;br /&gt;
* Logistics Staffing: Volunteers are needed for load-in on Wednesday and Thursday (10/30-10/31). Shelby, the new logistics head, noted they might miss Monday due to work travel but will be available for most of the weekend.&lt;br /&gt;
* Post-Con Load-Out: Additional volunteers are needed for Monday after the con (11/4) to help with loading trucks back into storage, as this day typically lacks sufficient help.&lt;br /&gt;
&lt;br /&gt;
=== Registration and Training Video ===&lt;br /&gt;
&lt;br /&gt;
* New Registration Training: A new 20-minute registration training video will cover policies and customer service procedures. All registration staff are required to watch it before working at Registration.&lt;br /&gt;
* Software Changes: Minor changes to the registration system include the removal of vaccine check requirements. Overall, the process remains similar to previous years.&lt;br /&gt;
&lt;br /&gt;
=== Philanthropy and Charity Auction ===&lt;br /&gt;
&lt;br /&gt;
* New Philanthropy Head: Elizabeth was introduced as the head of philanthropy.&lt;br /&gt;
* Charity Auction: Volunteers are needed to gather donations from vendors for the charity auction. Assistance is also required to organize items, label them, and set starting prices for the auction on Sunday.&lt;br /&gt;
&lt;br /&gt;
=== Security and Rovers ===&lt;br /&gt;
&lt;br /&gt;
* ESI Security: Additional support from ESI security will be available on Saturday, the busiest day of the con, to help with badge checks and general assistance. However, SNAFU Con staff will retain primary authority.&lt;br /&gt;
* Rovers Support: ESI security will provide extra manpower, but there was discussion about how to make them approachable for attendees who might have questions.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Panels ===&lt;br /&gt;
&lt;br /&gt;
* Panel Coverage: The programming department needs more volunteers, especially on Friday. Natasha, the former head of programming, will be available to help out.&lt;br /&gt;
* Panel Approvals: Notices are being sent to panelists regarding their submission statuses.&lt;br /&gt;
&lt;br /&gt;
=== Artist Alley and Vendor Management ===&lt;br /&gt;
&lt;br /&gt;
* Table Allocation: Nuriko Windchaser requested 52 tables for Artist Alley, which is more than originally planned. Tim confirmed there would likely be enough extra tables due to fewer club reservations.&lt;br /&gt;
* Vendor Donations for Charity Auction: Vendors will be asked for donations for the charity auction, and more volunteers are needed to assist with this effort.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Theme Decorations: Fun science-themed decorations, including interactive toys, have been purchased for the event.&lt;br /&gt;
* Tech and Equipment: Some equipment from last year needs to be replaced. An updated tech document, including room layouts, has been shared, and the wiki is up to date.&lt;br /&gt;
* Merchandise and Auction Donations: Vendors and artists are encouraged to donate items for the charity auction.&lt;br /&gt;
&lt;br /&gt;
=== Closing and Open Floor ===&lt;br /&gt;
&lt;br /&gt;
* Budget Requests: Staff were reminded to submit [https://register.snafucon.com/admin/budget_request/form budget requests] if they need additional resources or materials.&lt;br /&gt;
* Science-Themed Jokes for Con Book: The meeting wrapped up with a lighthearted discussion about creating original science-themed jokes for the con book.&lt;br /&gt;
* Open Questions: The meeting concluded with an open floor for additional questions or concerns.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - 2024-10-20 ==&lt;br /&gt;
&lt;br /&gt;
=== General Convention Overview: ===&lt;br /&gt;
&lt;br /&gt;
* Preparation Status:&lt;br /&gt;
** The team feels confident in their progress overall. Tim mentions that despite being close to the event, everything seems to be going well.&lt;br /&gt;
** The focus is on completing the remaining tasks, as anything not finished soon will likely be a source of last-minute stress.&lt;br /&gt;
&lt;br /&gt;
=== Program Book &amp;amp; Digital Files: ===&lt;br /&gt;
&lt;br /&gt;
* Program Book Preview:&lt;br /&gt;
** A preview of the program book is ready for review. Team members are encouraged to check it and report any errors.&lt;br /&gt;
** There was a conversation about the importance of opening the file in proper programs like Adobe Reader to avoid rendering issues, as some programs (e.g., Dropbox) cause display problems.&lt;br /&gt;
&lt;br /&gt;
=== Staff and Volunteer Logistics: ===&lt;br /&gt;
&lt;br /&gt;
* Food for Staff:&lt;br /&gt;
** Tim is finalizing food court options, and staff members were asked to notify if there’s nothing suitable on the menu for dietary reasons.&lt;br /&gt;
** There will be some attempts to ensure staff members have access to food throughout the event, though breakfast will likely be an individual responsibility.&lt;br /&gt;
** A possible plan involving food runners (volunteers delivering food to busy staff) is being considered.&lt;br /&gt;
** The main food service will operate from the Food Court during the following hours:&lt;br /&gt;
*** Friday: 3 PM - 10 PM&lt;br /&gt;
*** Saturday: 12 PM - 10 PM&lt;br /&gt;
*** Sunday: 12 PM - 4 PM&lt;br /&gt;
* “Tablecloths”:&lt;br /&gt;
** “Tablecloths” is a code word we will be using at con. All staff need to know what it is. If you don’t know what it means, please ask in chat. We do not post the meaning publicly in our wiki or meeting notes.&lt;br /&gt;
* Volunteer Staffing:&lt;br /&gt;
** There was a discussion about the need for additional volunteers for roles such as badge checks and general staffing. Aidan (Rover head) pointed out that more people are always needed.&lt;br /&gt;
** Volunteers can sign up at the convention itself.&lt;br /&gt;
** Blanca (Volunteer Head) confirmed that she will be at the convention earlier than in previous years to handle volunteer contracts and assignments.&lt;br /&gt;
&lt;br /&gt;
=== Event Logistics: ===&lt;br /&gt;
&lt;br /&gt;
* Setup and Tear Down Schedule:&lt;br /&gt;
** The logistics team plans to begin setup on Wednesday afternoon, with staff loading trucks and taking materials to the venue.&lt;br /&gt;
** Tear-down will start right after closing ceremonies on Sunday, with final wrap-up happening by Monday morning.&lt;br /&gt;
** Volunteers were asked to join logistics to ensure a smooth setup and breakdown process.&lt;br /&gt;
* Parking:&lt;br /&gt;
** Staff will not be charged for parking during setup (Thursday).&lt;br /&gt;
** For the rest of the event, parking passes will be distributed, though anyone arriving after Thursday may have to pay for parking if they don&#039;t pick up a pass in advance or request assistance. &lt;br /&gt;
&lt;br /&gt;
=== Gaming and Console Section: ===&lt;br /&gt;
&lt;br /&gt;
* CRTs and Consoles:&lt;br /&gt;
** A key concern is the pickup of CRTs (cathode ray tube monitors) for retro gaming setups. William (Derp) mentioned issues with communication regarding the pickup of these monitors from a vendor named Skyline, who was slow to respond. Determined he had likely been busy with another event. &lt;br /&gt;
** There are plans to have around five CRTs for the gaming section, and more consoles are being confirmed, including NES, SNES, PS2, and N64.&lt;br /&gt;
** Specific games like Guitar Hero II and Shadow the Hedgehog were discussed as options to be included in the gaming lineup.&lt;br /&gt;
&lt;br /&gt;
=== Badge and Panel Logistics: ===&lt;br /&gt;
&lt;br /&gt;
* Badge Checks:&lt;br /&gt;
** Badge check locations were discussed, particularly around entry points and key areas, to ensure proper flow of attendees.&lt;br /&gt;
** There will be a simplified layout for badge checks to direct people straight from registration into the main vendor room.&lt;br /&gt;
* Panel Schedule:&lt;br /&gt;
** A tentative panel schedule has been posted, but it is still awaiting feedback and minor adjustments.&lt;br /&gt;
** The final panel schedule will be printed and distributed as soon as it&#039;s finalized.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Communication: ===&lt;br /&gt;
&lt;br /&gt;
* Staff Contracts:&lt;br /&gt;
** Staff members who haven’t completed their contracts were reminded to submit them before the event. Contracts will not be processed at the convention. (You will be removed as staff if you don’t get it done.)&lt;br /&gt;
** Cassy is in charge of collecting contracts and has been offering help to those having trouble submitting them electronically.&lt;br /&gt;
* Theme Voting for Next Year:&lt;br /&gt;
** The next meeting will involve voting on the theme for next year’s convention. Staff members were encouraged to think of fun ideas for themes and attend the meeting to have a say.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous: ===&lt;br /&gt;
&lt;br /&gt;
* Prizes and Merchandise:&lt;br /&gt;
** Llama delivered a batch of prizes for the prize booth, which will include various attractive items that staff members might enjoy.&lt;br /&gt;
** Staff were encouraged to check out the prize booth during the event.&lt;br /&gt;
* Vaccination Policy:&lt;br /&gt;
** There is no requirement for proof of vaccination this year, although it is still recommended to avoid illness.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Final Staff Meeting Before Con 2024-10-26 =&lt;br /&gt;
&lt;br /&gt;
=== Incident Reporting and Code Usage ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Incident Reporting:&#039;&#039;&#039;&lt;br /&gt;
** All issues, incidents, or attendee complaints should be reported in the designated &#039;&#039;&#039;#rovers-reports&#039;&#039;&#039; Discord channel in the &#039;&#039;&#039;At-Con Channels&#039;&#039;&#039; category.&lt;br /&gt;
** Staff should avoid assuming an incident is already reported and are encouraged to file it themselves if unsure.&lt;br /&gt;
** Incident tracking aims to help identify recurring issues and improve responses.&lt;br /&gt;
* &#039;&#039;&#039;Code Definitions and Usage:&#039;&#039;&#039;&lt;br /&gt;
** &#039;&#039;&#039;Hot Coffee:&#039;&#039;&#039; Signals a &#039;&#039;&#039;&#039;&#039;significant&#039;&#039;&#039;&#039;&#039; problem requiring &#039;&#039;&#039;&#039;&#039;immediate&#039;&#039;&#039;&#039;&#039; attention. Staff should use this code in Discord to notify other team members, and once resolved, report it as “Hot Coffee Clear.”&lt;br /&gt;
** &#039;&#039;&#039;Code Silver:&#039;&#039;&#039; Indicates a staff member is overwhelmed or unavailable for a period. Use this code if someone needs coverage due to stress or exhaustion.&lt;br /&gt;
** &#039;&#039;&#039;Code Green:&#039;&#039;&#039; Used to identify a potential “creeper” or suspicious person in the area.&lt;br /&gt;
** &#039;&#039;&#039;Code Everclear&#039;&#039;&#039;: Indicates intoxication or substance-related disturbances.&lt;br /&gt;
** &#039;&#039;&#039;Code Pink:&#039;&#039;&#039; Potential Dress Code violation&lt;br /&gt;
** &#039;&#039;&#039;Code Yellow:&#039;&#039;&#039; I need a bathroom break (optional, say whatever you’re comfortable with)&lt;br /&gt;
** &#039;&#039;&#039;I’m in a Tunnel:&#039;&#039;&#039; “I’ll have to call you back.” Staff member is completely occupied with something important and cannot help you right now. Find someone else or leave  the staff member a note and they’ll get to you as soon as they can. &lt;br /&gt;
** &#039;&#039;&#039;It’s Raining Tacos:&#039;&#039;&#039; &#039;&#039;(Stolen from Otakon/Otakon Vegas)&#039;&#039; Everything’s great! Really. =)&lt;br /&gt;
* &#039;&#039;&#039;Emergency Protocols:&#039;&#039;&#039;&lt;br /&gt;
** Staff should familiarize themselves with fire exits and extinguisher locations&lt;br /&gt;
** Jokes about emergencies or codes are &#039;&#039;strongly discouraged&#039;&#039; to prevent miscommunication.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Logistics &amp;amp; Schedule ===&lt;br /&gt;
Our storage unit is the &#039;&#039;&#039;Public Storage&#039;&#039;&#039; across from the GSR: &#039;&#039;&#039;200 Telegraph Way.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Setup and Teardown Timeline:&#039;&#039;&#039;&lt;br /&gt;
** &#039;&#039;&#039;Wednesday (Storage Into Truck), 2:30 PM ish:&#039;&#039;&#039;   Meet us at Public Storage (addr above) to help load storage items loaded onto our truck around 2:30 PM.   After the truck is loaded we go to Thomas’s place for final pre-con prep (stapling schedules, laminating badges, etc.). Address will be provided in Discord and we usually order pizza for anyone hanging out helping there.&lt;br /&gt;
** &#039;&#039;&#039;Thursday (Truck into Convention Center), 9:00 AM ish:&#039;&#039;&#039;   Start unloading the truck at the convention center by 9-10 AM to set up all areas. The day involves organizing materials and preparing the rooms.&lt;br /&gt;
** &#039;&#039;&#039;Friday (Final Prep) 9:00 AM:&#039;&#039;&#039;   Final setup preparations starting 9 AM, before the convention opens at noon.&lt;br /&gt;
** &#039;&#039;&#039;Sunday (Convention Center back into Truck) 4:00 PM ish - Midnight:&#039;&#039;&#039;   Starts around 3-4 PM, packing items and staging for load-out, potentially until midnight if necessary. Con purchases a post-con dinner once the truck is handled. Restaurant TBD.&lt;br /&gt;
** &#039;&#039;&#039;Monday (Truck back into Storage) 10:00 AM ish:&#039;&#039;&#039;   Meeting at 10 AM at Public Storage storage to return items to storage. Con purchases a post-storage lunch once the truck is handled.&lt;br /&gt;
* &#039;&#039;&#039;Parking Passes:&#039;&#039;&#039;&lt;br /&gt;
** Staff should obtain parking passes outside of peak times to avoid charges. You can grab one when you are getting your badge if you need be park at the convention center when they charge. &lt;br /&gt;
** Parking is charged: &lt;br /&gt;
*** Friday: 11:30AM-9:30PM &lt;br /&gt;
*** Saturday: 9:30AM-9:30PM &lt;br /&gt;
*** Sunday: 9:30AM-3:30PM &lt;br /&gt;
* &#039;&#039;&#039;Use of Tape:&#039;&#039;&#039;&lt;br /&gt;
** Tape restrictions were emphasized: “Tape Yes” and “Tape No” types are clarified to prevent damage to venue property.&lt;br /&gt;
** Gaffer tape ONLY is allowed on floors when necessary.&lt;br /&gt;
** &#039;&#039;&#039;NO TAPE ON THE WALLS.&#039;&#039;&#039; At all. There is no authorized type of tape for walls at this venue. &lt;br /&gt;
** &#039;&#039;&#039;NO TAPE ON THE SIGNS EVER&#039;&#039;&#039; unless you have VERY SPECIFIC approval to put tape on a sign. Tape ruins the poster board signs. It doesn’t matter what kind of tape it is. All types of tape ruin these signs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Staff Roles &amp;amp; Volunteer Management ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Volunteer Requests:&#039;&#039;&#039;&lt;br /&gt;
** Requests for assistance should be made even if  we are short-staffed. Volunteers or reassignments will be arranged as necessary. Department heads are encouraged to ask for volunteers in &#039;&#039;&#039;#volunteer-requests&#039;&#039;&#039; in the &#039;&#039;&#039;At-Con Channels&#039;&#039;&#039; category&lt;br /&gt;
** Staff are encouraged to ask for help when needed and avoid handling challenging situations alone. Use your department-specific channel, #staff, or any relevant-seeming channel to ask for help.&lt;br /&gt;
* &#039;&#039;&#039;Break Protocols:&#039;&#039;&#039;&lt;br /&gt;
** Staff should reach out to their department head in their department-specific channel if they need a break to ensure their area remains covered. Department heads can reach out to volunteers department or other staff as needed to get you covered. Do not just leave your post.&lt;br /&gt;
* &#039;&#039;&#039;Customer Service Guidelines:&#039;&#039;&#039;&lt;br /&gt;
** Basic customer service protocols include being polite, providing clear directions, and avoiding phrases like “I don’t know” without offering further assistance or directing them to someone who does know.&lt;br /&gt;
** Avoid sarcasm, especially with unfamiliar attendees, to prevent misinterpretation and ensure clear communication.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Event Notes ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Photography &amp;amp; Social Media:&#039;&#039;&#039;&lt;br /&gt;
** Staff are encouraged to contribute to social media with attendee photos (respecting badges that indicate “no photos”). These can be shared in the designated social media channel.&lt;br /&gt;
** Artist Alley intends to set up a science-themed backdrop for photo opportunities.&lt;br /&gt;
* &#039;&#039;&#039;Halloween Activities:&#039;&#039;&#039;&lt;br /&gt;
** The venue approved trick-or-treating for Day 0, though staffing for candy distribution is lacking. Our backup plan is to place candy bowls in accessible locations because we still want to have candy for Halloween, especially since it was approved.&lt;br /&gt;
* &#039;&#039;&#039;Final Reminders:&#039;&#039;&#039;&lt;br /&gt;
** All department heads were given a last call for questions or clarifications.&lt;br /&gt;
** To make suggestions for next year, be sure to use an interdepartmental channel (like &#039;&#039;&#039;#interdepartmental-talk&#039;&#039;&#039;), a thread in #staff or #castle, or send an email to &#039;&#039;&#039;feedback@snafucon.com&#039;&#039;&#039;. If you use the #notes-to-selves channels, it will be to yourself and nobody else will likely see it. &lt;br /&gt;
** Staff are reminded to prioritize positive attendee interactions and to escalate situations if needed, asking for help when unsure of how to proceed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If you have any questions, ask us in Discord! We want to help staff have a great con, and if you don’t ask we won’t know you have questions.&#039;&#039;&#039; &lt;br /&gt;
&#039;&#039;&#039;We would rather you ask questions than struggle.&#039;&#039;&#039;We&#039;ll see you all at con!! &amp;lt;3&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Rovers&amp;diff=1799</id>
		<title>Rovers</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Rovers&amp;diff=1799"/>
		<updated>2024-10-29T03:13:47Z</updated>

		<summary type="html">&lt;p&gt;Beta: redirect to new Rovers place&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[:Category:Rovers Department]]&lt;br /&gt;
[[Category:Departments]][[Category:Rovers Department]]&lt;br /&gt;
Rovers are the &#039;&#039;&#039;Customer Service&#039;&#039;&#039; department!&lt;br /&gt;
Rovers are here to assist attendees with everything they need to make sure that all attendees can continue to enjoy the convention to their fullest by providing information and ensuring that all attendees are safe and follow the convention policies. &lt;br /&gt;
&lt;br /&gt;
==Peace Bonding==&lt;br /&gt;
Rovers handle peace bonding. &lt;br /&gt;
See the [[Peace Bonding]] page.&lt;br /&gt;
&lt;br /&gt;
==Rave==&lt;br /&gt;
Rovers ensure that there is only one door at the [[Rave]].&lt;br /&gt;
&lt;br /&gt;
==Head of rovers responsibilities and procedures==&lt;br /&gt;
&lt;br /&gt;
Organizing efforts and schedules between coheads&lt;br /&gt;
&lt;br /&gt;
Dealing with extremely disgruntled guests that standard rovers can&#039;t handle&lt;br /&gt;
updating rovers policies from year to year as needed. &lt;br /&gt;
&lt;br /&gt;
Setting up rotation for Rovers staff, to keep shifts equal and keep your staff happy, within reason.&lt;br /&gt;
 &lt;br /&gt;
Always have a radio on you, and keep in contact with your cohead and department should you have to go off floor&lt;br /&gt;
&lt;br /&gt;
Always remember your towel&lt;br /&gt;
&lt;br /&gt;
Keep an ear out for code words, and remember what they are.&lt;br /&gt;
&lt;br /&gt;
Ensuring that we always have bodies, warm or cold, where we need them. &lt;br /&gt;
&lt;br /&gt;
Ensuring that there is always someone checking badges, at peacebonding, and at Henti (when applicable) ensuring that there are rovers for rave.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Category:Rovers_Department&amp;diff=1798</id>
		<title>Category:Rovers Department</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Category:Rovers_Department&amp;diff=1798"/>
		<updated>2024-10-29T03:11:17Z</updated>

		<summary type="html">&lt;p&gt;Beta: Create page off old Rovers dept page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Rovers are the &#039;&#039;&#039;Customer Service Department&#039;&#039;&#039; of the convention, dedicated to helping attendees have a safe and enjoyable experience. Rovers serve as the primary point of contact for attendees, offering assistance, information, and guidance to ensure everyone can participate in the convention smoothly. They uphold convention policies and respond to any issues that arise, working to keep the environment safe and enjoyable for all.&lt;br /&gt;
&lt;br /&gt;
=== General Responsibilities ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Attendee Assistance&#039;&#039;&#039;: Rovers provide directions, answer questions, and support attendees in navigating the convention spaces. They help attendees understand and follow convention guidelines to maintain a positive atmosphere.&lt;br /&gt;
* &#039;&#039;&#039;Policy Enforcement&#039;&#039;&#039;: Rovers politely remind attendees of event policies, such as badge visibility, dress code, and general behavior expectations. They report any violations or safety concerns to the appropriate team.&lt;br /&gt;
* &#039;&#039;&#039;Incident Reporting&#039;&#039;&#039;: Rovers document incidents and escalate situations as needed, especially when policy violations or safety concerns arise.&lt;br /&gt;
&lt;br /&gt;
=== Key Policies ===&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Event Monitoring at the Rave&#039;&#039;&#039;  Rovers ensure that the Rave has only one accessible entry/exit door, monitoring the space to maintain safety and crowd control.&lt;br /&gt;
# &#039;&#039;&#039;Head of Rovers Responsibilities&#039;&#039;&#039;&lt;br /&gt;
#* &#039;&#039;&#039;Scheduling and Rotation&#039;&#039;&#039;: The Head of Rovers organizes staff schedules to ensure even shifts and coverage throughout the convention.&lt;br /&gt;
#* &#039;&#039;&#039;Communication&#039;&#039;&#039;: Heads coordinate with co-heads and other departments, especially during incidents requiring quick response.&lt;br /&gt;
#* &#039;&#039;&#039;Badge and Venue Checkpoints&#039;&#039;&#039;: Ensure Rovers are stationed at badge checkpoints, peace bonding, Hentai screenings, and the Rave.&lt;br /&gt;
#* &#039;&#039;&#039;Managing Disruptive Situations&#039;&#039;&#039;: Head Rovers handle escalated situations and update policies annually as needed.&lt;br /&gt;
#* &#039;&#039;&#039;Radio Protocol&#039;&#039;&#039;: Always carry a radio for instant communication, especially if leaving your post.&lt;br /&gt;
# &#039;&#039;&#039;Code Awareness&#039;&#039;&#039;  Rovers should be familiar with any event code words and their meanings for quick, discreet communication during incidents.&lt;br /&gt;
# &#039;&#039;&#039;“Always Bring a Towel” &#039;&#039;(Joking)&#039;&#039;&#039;&#039;&#039;  Remembering a towel is a longstanding tradition among Rovers, representing preparedness and adaptability. &#039;&#039;(This is a reference to the Hitchhiker&#039;s Guide to the Galaxy. You can totally bring a towel, but you don&#039;t actually need to)&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Training Document ===&lt;br /&gt;
For a detailed guide on Rovers procedures, see the [[Basic Rovers Training|Rovers Training Document]]. This document covers communication protocols, badge checking, and incident response procedures to help Rovers perform their roles effectively.&lt;br /&gt;
&lt;br /&gt;
=== Cosplay and Peace Bonding ===&lt;br /&gt;
[[Peace Bonding]] responsibilities have been handed off to the [[:Category:Cosplay Department|Cosplay Department]]. However, final determination on the safety of a prop and whether a prop is within or not within our policies is the responsibility of the Rovers Department Head.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Basic_Rovers_Training&amp;diff=1797</id>
		<title>Basic Rovers Training</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Basic_Rovers_Training&amp;diff=1797"/>
		<updated>2024-10-29T03:03:09Z</updated>

		<summary type="html">&lt;p&gt;Beta: create page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==== Purpose and Role Overview ====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Rovers’ Role&#039;&#039;&#039;: Rovers are responsible for assisting attendees, answering questions, and ensuring a positive, safe environment. Rovers focus on de-escalation and verbal communication, rather than physical intervention, as they are &#039;&#039;not&#039;&#039; security staff.&lt;br /&gt;
* &#039;&#039;&#039;Introduction and Experience&#039;&#039;&#039;: Typically led by a team member with extensive experience in roving operations, who can guide the team on protocol, response methods, and key responsibilities.&lt;br /&gt;
&lt;br /&gt;
==== Key Responsibilities ====&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Assistance and Information&#039;&#039;&#039;:&lt;br /&gt;
#* Rovers serve as the main point of contact for attendee inquiries, providing guidance to event locations, schedules, and other event-related information.&lt;br /&gt;
#* Rovers should be approachable and ready to address attendee needs or direct them to the appropriate staff members if they cannot help directly.&lt;br /&gt;
# &#039;&#039;&#039;Event Resources&#039;&#039;&#039;:&lt;br /&gt;
#* &#039;&#039;&#039;Event Schedule and Map&#039;&#039;&#039;: Rovers should carry a schedule and map (digital or printed) to help attendees locate event spaces, exits, restrooms, and other critical areas.&lt;br /&gt;
#* &#039;&#039;&#039;Communication Channels&#039;&#039;&#039;: Rovers should stay updated by periodically checking any communication channels specific to rovers, such as reports or inquiries. This helps ensure they’re aware of current situations and announcements.&lt;br /&gt;
# &#039;&#039;&#039;Communication and Reporting&#039;&#039;&#039;:&lt;br /&gt;
#* &#039;&#039;&#039;Customer Service and General Inquiries&#039;&#039;&#039;: Rovers should periodically check channels designated for attendee questions and incident reports, staying updated on event activities without becoming distracted.&lt;br /&gt;
#* &#039;&#039;&#039;Reporting Incidents&#039;&#039;&#039;: Documenting incidents is essential. Rovers should report all infractions or concerns, no matter the severity. Incident types can range from minor violations (e.g., dress code issues) to more serious matters (e.g., harassment or unauthorized entry). For serious incidents, Rovers may need to escalate the report to heads or security.&lt;br /&gt;
# &#039;&#039;&#039;Badge Checks and Policy Enforcement&#039;&#039;&#039;:&lt;br /&gt;
#* Rovers are responsible for upholding policies such as badge checks, dress codes, and behavior guidelines.&lt;br /&gt;
#* &#039;&#039;&#039;Badge Checks&#039;&#039;&#039;: Rovers should confirm that badges are visible and valid for the current day. Any discrepancies or missing badges should be directed to registration or escalated as needed.&lt;br /&gt;
# &#039;&#039;&#039;Incident Types&#039;&#039;&#039;:&lt;br /&gt;
#* &#039;&#039;&#039;Minor Incidents&#039;&#039;&#039;: These include simple dress code adjustments or minor prop usage violations. Rovers should politely remind attendees of the rules and document the interaction.&lt;br /&gt;
#* &#039;&#039;&#039;Escalated Incidents&#039;&#039;&#039;: Serious incidents, such as harassment or unauthorized behavior, must be reported promptly. Heads or security may need to intervene, and Rovers should provide detailed documentation.&lt;br /&gt;
&lt;br /&gt;
==== Communication Best Practices ====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Incident Documentation&#039;&#039;&#039;: It’s crucial to document all incidents accurately. Even minor reports can provide valuable insight and prevent issues from escalating.&lt;br /&gt;
* &#039;&#039;&#039;Consistency in Reporting&#039;&#039;&#039;: Reports should be clear, factual, and, if necessary, include follow-up actions taken by Rovers or other staff.&lt;br /&gt;
&lt;br /&gt;
==== Important Reminders ====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Non-Security Role&#039;&#039;&#039;: Rovers are not permitted to physically intervene and should focus on verbal resolution and communication. For any situation that may require physical intervention, contact security or escalate to the appropriate department heads.&lt;br /&gt;
* &#039;&#039;&#039;Event Rules and Protocols&#039;&#039;&#039;: Rovers should be familiar with the event’s policies, such as the dress code, behavior expectations, and prohibited items. A solid understanding of these policies will help Rovers communicate effectively with attendees.&lt;br /&gt;
* &#039;&#039;&#039;Checking In&#039;&#039;&#039;: Rovers should stay connected with event communication channels for updates, report their status as needed, and ensure prompt response times.&lt;br /&gt;
&lt;br /&gt;
==== Conclusion ====&lt;br /&gt;
Rovers play a vital role in maintaining a welcoming and safe atmosphere at the event. Their contributions in assisting, guiding, and reporting help the event run smoothly and create a positive experience for all attendees. Rovers are encouraged to ask questions, seek clarification when needed, and stay engaged with their team and event staff throughout the event.&lt;br /&gt;
[[Category:Rovers Department]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Rovers&amp;diff=1796</id>
		<title>Rovers</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Rovers&amp;diff=1796"/>
		<updated>2024-10-29T02:59:22Z</updated>

		<summary type="html">&lt;p&gt;Beta: add cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Departments]][[Category:Rovers Department]]&lt;br /&gt;
Rovers are the &#039;&#039;&#039;Customer Service&#039;&#039;&#039; department!&lt;br /&gt;
Rovers are here to assist attendees with everything they need to make sure that all attendees can continue to enjoy the convention to their fullest by providing information and ensuring that all attendees are safe and follow the convention policies. &lt;br /&gt;
&lt;br /&gt;
==Peace Bonding==&lt;br /&gt;
Rovers handle peace bonding. &lt;br /&gt;
See the [[Peace Bonding]] page.&lt;br /&gt;
&lt;br /&gt;
==Rave==&lt;br /&gt;
Rovers ensure that there is only one door at the [[Rave]].&lt;br /&gt;
&lt;br /&gt;
==Head of rovers responsibilities and procedures==&lt;br /&gt;
&lt;br /&gt;
Organizing efforts and schedules between coheads&lt;br /&gt;
&lt;br /&gt;
Dealing with extremely disgruntled guests that standard rovers can&#039;t handle&lt;br /&gt;
updating rovers policies from year to year as needed. &lt;br /&gt;
&lt;br /&gt;
Setting up rotation for Rovers staff, to keep shifts equal and keep your staff happy, within reason.&lt;br /&gt;
 &lt;br /&gt;
Always have a radio on you, and keep in contact with your cohead and department should you have to go off floor&lt;br /&gt;
&lt;br /&gt;
Always remember your towel&lt;br /&gt;
&lt;br /&gt;
Keep an ear out for code words, and remember what they are.&lt;br /&gt;
&lt;br /&gt;
Ensuring that we always have bodies, warm or cold, where we need them. &lt;br /&gt;
&lt;br /&gt;
Ensuring that there is always someone checking badges, at peacebonding, and at Henti (when applicable) ensuring that there are rovers for rave.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1793</id>
		<title>2024 Meeting Notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1793"/>
		<updated>2024-10-22T16:15:12Z</updated>

		<summary type="html">&lt;p&gt;Beta: add 2024-10-20 notes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Staff Meeting Summary 2024-06-22 ==&lt;br /&gt;
&lt;br /&gt;
=== Convention Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Announcement:&#039;&#039;&#039;&lt;br /&gt;
** We&#039;re having a convention! The contract is signed with the &#039;&#039;&#039;Reno Sparks Convention Center&#039;&#039;&#039; for a &#039;&#039;&#039;Nov 1-3&#039;&#039;&#039; convention. We have the space from Wednesday to Monday.&lt;br /&gt;
* &#039;&#039;&#039;Website and Registration:&#039;&#039;&#039;&lt;br /&gt;
** Convention dates updated on the website.&lt;br /&gt;
** Additional updates needed.&lt;br /&gt;
** General registration expects to open by the end of the weekend.&lt;br /&gt;
** Staff registration will open alongside general registration, even without the staff contract being ready.&lt;br /&gt;
** Staff contract is being worked on by Natasha.&lt;br /&gt;
* &#039;&#039;&#039;Need for Staff:&#039;&#039;&#039;&lt;br /&gt;
** Emphasis on the need for more staff.&lt;br /&gt;
** Encouragement for current staff to recruit friends.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introduction of New Staff Member:&#039;&#039;&#039;&lt;br /&gt;
** TheUltimateDragon (William) introduced as the new head of the game room.&lt;br /&gt;
** Plans to involve the local fighting game community, with 20 to 30 active members.&lt;br /&gt;
&lt;br /&gt;
=== Department Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Game Room Logistics:&#039;&#039;&#039;&lt;br /&gt;
** William plans to bring in his community for the game room.&lt;br /&gt;
** Discussion on the availability of consoles and other equipment. We may need to source consoles.&lt;br /&gt;
* &#039;&#039;&#039;Separation of Main Stage and Gaming Areas:&#039;&#039;&#039;&lt;br /&gt;
** Main stage and gaming areas will be separated at the new venue.&lt;br /&gt;
* &#039;&#039;&#039;Beta&#039;s Role Change:&#039;&#039;&#039;&lt;br /&gt;
** John has stepped down as vice chair and gaming head.&lt;br /&gt;
** Beta has stepped down as vice chair and is stepping back from some responsibilities. &lt;br /&gt;
** Beta&#039;s focus will largely be on continuous improvement and documentation to streamline processes.&lt;br /&gt;
** Tim is now a vice chair and will be more involved in ensuring tasks are completed.&lt;br /&gt;
* &#039;&#039;&#039;Recognition of Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Cupcake Doll recognized for consistent efforts in keeping things moving.&lt;br /&gt;
&lt;br /&gt;
=== Pricing and Budget ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Weekend passes likely $60.&lt;br /&gt;
** Individual day passes expected to be $30, with possible higher price for Saturday.&lt;br /&gt;
* &#039;&#039;&#039;Vendor Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Vendor table prices will increase slightly.&lt;br /&gt;
* &#039;&#039;&#039;Prize Procurement:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on handling prizes for the convention.&lt;br /&gt;
** Tighter budget than usual this year, need for smart procurement.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotion ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Urgent need to start marketing the convention.&lt;br /&gt;
** Plans to distribute business cards and possibly larger flyers or posters.&lt;br /&gt;
* &#039;&#039;&#039;RAGECON Presence:&#039;&#039;&#039;&lt;br /&gt;
** Potential for having a table at RAGECON to promote the convention.&lt;br /&gt;
** Discussion on staffing the table and badges.&lt;br /&gt;
* &#039;&#039;&#039;Community Engagement:&#039;&#039;&#039;&lt;br /&gt;
** Importance of engaging with the local community through various events.&lt;br /&gt;
&lt;br /&gt;
=== Social Media and Streaming ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Social Media Activity:&#039;&#039;&#039;&lt;br /&gt;
** Current presence on Facebook and Twitter (X).&lt;br /&gt;
** Need to boost activity on these platforms.&lt;br /&gt;
* &#039;&#039;&#039;Streaming Ideas:&#039;&#039;&#039;&lt;br /&gt;
** Streaming tournaments and other events to generate hype.&lt;br /&gt;
** Use of Twitch and YouTube for streaming and promoting the convention.&lt;br /&gt;
* &#039;&#039;&#039;Social Media Management:&#039;&#039;&#039;&lt;br /&gt;
** Fae offered to help with social media posts and engagement.&lt;br /&gt;
** Discussion on using Social Pilot for automated posts, with manual posts for Instagram.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New Venue Details:&#039;&#039;&#039;&lt;br /&gt;
** New venue is the convention center, more expensive but possibly a better fit.&lt;br /&gt;
** Concerns about lighting at the new venue and potential solutions.&lt;br /&gt;
* &#039;&#039;&#039;Security Requirements:&#039;&#039;&#039;&lt;br /&gt;
** Need to hire ESI security, details still unclear.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Communication and Collaboration:&#039;&#039;&#039;&lt;br /&gt;
** Encouragement for effective communication and collaboration.&lt;br /&gt;
** Importance of being proactive in managing tasks and responsibilities.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-07-14 ==&lt;br /&gt;
&lt;br /&gt;
=== Welcome and Introduction ===&lt;br /&gt;
&lt;br /&gt;
* The meeting was initiated to discuss updates and plans for SNAFU Con, emphasizing the importance of recruiting more staff.&lt;br /&gt;
&lt;br /&gt;
=== Website and Marketing Updates ===&lt;br /&gt;
&lt;br /&gt;
* The website is nearly ready for directing traffic, with social media updates to follow soon.&lt;br /&gt;
* Business card-sized flyers are ready, and 4x6 flyers are being prepared for distribution.&lt;br /&gt;
* Marketing efforts are expected to kick off in August. Flyers and posters will be distributed at local nerdy businesses.&lt;br /&gt;
* Posters will be available closer to the event, no later than the con book release.&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Conventions and Events ===&lt;br /&gt;
&lt;br /&gt;
* A list of upcoming conventions and events was provided to schedule possible promotional efforts:&lt;br /&gt;
** August 16-18: GalaxyCon San Jose&lt;br /&gt;
** August 17-18: Con for a Cause (formerly Aerie-Con) in Reno&lt;br /&gt;
** August 30-Sept 1: SacAnime&lt;br /&gt;
** September 7-10: Kaboom Con in Carson City&lt;br /&gt;
** October 14-17: BLFC at GSR&lt;br /&gt;
** October 26-27: YumeConUSA in San Jose&lt;br /&gt;
** November 2-3: Reno Toy Con at GSR&lt;br /&gt;
* Additional local events and new shops were suggested as potential flyer distribution points.&lt;br /&gt;
** Kobold’s Keep in Reno&lt;br /&gt;
** New shop in Sparks called &amp;quot;The Coffer&amp;quot;&lt;br /&gt;
** Warhammer store at Summit&lt;br /&gt;
* Cosplay meetups and other geek clubs were identified as good opportunities for promotion.&lt;br /&gt;
** Local libraries often have anime and gaming clubs that could be reached out to for promotion.&lt;br /&gt;
** South Reno Library, which has regular Pokémon days for kids.&lt;br /&gt;
** Cosplay for Kindness, a group that runs various events in town and was suggested for potential collaboration.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment and Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Emphasis on the prompt signing of staff contracts to avoid last year&#039;s issues.&lt;br /&gt;
* Encouragement for staff to recruit friends and acquaintances to join the team.&lt;br /&gt;
* Discussion on the contract checking process using the existing HR system. (We have to actually make phone calls again to catch stragglers.)&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Plans ===&lt;br /&gt;
&lt;br /&gt;
* The new convention layout at the Reno-Sparks Convention Center was discussed, including the need for large signs to guide attendees.&lt;br /&gt;
* We have all of C, D and E rooms.&lt;br /&gt;
* Initial maps were shared, highlighting the layout of C and D halls and the ballroom for vendors and artists.&lt;br /&gt;
* Focus on controlling badge points and managing the flow of attendees.&lt;br /&gt;
** We expect to need 5 badge controlled spots &lt;br /&gt;
&lt;br /&gt;
=== Food and Concessions ===&lt;br /&gt;
&lt;br /&gt;
* Concerns were raised about the availability of substantial food options at the venue.&lt;br /&gt;
** If you have a request for the concessions stand, send it to Tim.&lt;br /&gt;
** Coordination with Aramark for concessions and the possibility of vendors providing snacks were discussed.&lt;br /&gt;
&lt;br /&gt;
=== Merchants and Artist Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Merchant and artist contracts are in progress and will be opened soon.&lt;br /&gt;
* A first-come, first-serve approach was proposed for artist alley applications.&lt;br /&gt;
* Emphasis on adhering to city deadlines for paperwork submission.&lt;br /&gt;
** City deadline is now 30 days before con instead of the 15 day deadline we used to have.&lt;br /&gt;
&lt;br /&gt;
=== Partnering with Local Organizations ===&lt;br /&gt;
&lt;br /&gt;
* Plans to reach out to local professors, science museums, and other educational organizations for panel presentations and partnerships.&lt;br /&gt;
* Contact with the Discovery Museum for potential collaboration was initiated.&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* At least one future in-person meeting will be held at libraries to facilitate face-to-face interactions. Possibly more.&lt;br /&gt;
* Potential venues for these meetings include South Valleys Library and Sparks Library.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* Updates on social media graphics and preparations for the convention were shared.&lt;br /&gt;
* A press release will be drafted following the guidelines on the SNAFU Con wiki.&lt;br /&gt;
* Reminder to be cautious about staff burnout and to maintain a balanced workload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - In Person Meeting 2024-08-10 ==&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Meeting Issues:&#039;&#039;&#039;&lt;br /&gt;
** Attendance was taken manually due to errors in logging into the system.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introductions:&#039;&#039;&#039;&lt;br /&gt;
** Staff members introduced themselves, their roles, and their previous experience with the convention.&lt;br /&gt;
&lt;br /&gt;
=== Event Planning and Roles ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing:&#039;&#039;&#039;&lt;br /&gt;
** There are several open positions that need to be filled.&lt;br /&gt;
** Current staff are encouraged to take on multiple roles due to the shortage.&lt;br /&gt;
** Beta is stepping back but will still assist with HR, graphics, documentation, and continual improvement.&lt;br /&gt;
** The chair is Tim, who will oversee various departments and tasks.&lt;br /&gt;
** Registration and contract signing for staff will be done online, with no in-person signings allowed.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Layout:&#039;&#039;&#039;&lt;br /&gt;
** Overview of the venue layout:&lt;br /&gt;
*** Artist Alley and Vendor spaces will be located in D1-D3 ballrooms.&lt;br /&gt;
*** E1-E3 for video gaming, E9-E10 for tabletop gaming.&lt;br /&gt;
*** Main stage, panels, cosplay, and manga library also mapped out.&lt;br /&gt;
** Discussions on the potential need for more lighting in certain rooms, particularly for the Artist Alley.&lt;br /&gt;
** A walkthrough is needs to be scheduled to assess lighting and other venue specifics.&lt;br /&gt;
** Badge control points and door management will be 5 points this year due to venue layout. We may be able to use ESI for two of them.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Features ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Room:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is the new head of the gaming room and is planning a retro gaming corner.&lt;br /&gt;
** The retro gaming corner will feature classic consoles like PS2, SNES Classic, etc.&lt;br /&gt;
** A tournament is being planned, potentially requiring more PS5 consoles.&lt;br /&gt;
** Volunteers are needed to help with the gaming room.&lt;br /&gt;
** A spreadsheet may be created to track who is bringing what equipment (consoles, TVs, etc.).&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Artist Alley and Vendor Contracts:&#039;&#039;&#039;&lt;br /&gt;
** Artist Alley and Vendor space has been slightly reduced&lt;br /&gt;
** Contracts are almost ready, pending some final details.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Cosplay:&#039;&#039;&#039;&lt;br /&gt;
** The main lobby area and ballroom lobby are potential spaces for cosplay meetups.&lt;br /&gt;
** Discussion on the benefits of high visibility areas for cosplay meetups.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Initiatives:&#039;&#039;&#039;&lt;br /&gt;
** There is a strong need for increased marketing due to the new venue and the desire to attract a larger audience.&lt;br /&gt;
** Social media efforts need to ramp up, with plans to highlight artists, vendors, and panels.&lt;br /&gt;
** There is a call for everyone to contribute to marketing, especially on social media.&lt;br /&gt;
** Short science videos and other creative content ideas were discussed as potential marketing tools.&lt;br /&gt;
** Plans to advertise on local event pages, including Nevada Appeal and RGJ Events.&lt;br /&gt;
** Potential collaboration with other local events (e.g., toy fair, punk rock market) to cross-promote.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Outreach to Other Communities:&#039;&#039;&#039;&lt;br /&gt;
** UNR (University of Nevada, Reno) clubs and groups are potential targets for outreach.&lt;br /&gt;
** Suggestions to connect with local businesses like Cap&#039;n Games for retro gaming partnerships.&lt;br /&gt;
** Discussed using UNR’s radio station and event calendars for advertising.&lt;br /&gt;
&lt;br /&gt;
=== Other Discussions ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Venue Logistics:&#039;&#039;&#039;&lt;br /&gt;
** Badge-controlled areas were discussed, and it&#039;s determined that certain doors may be monitored by ESI security.&lt;br /&gt;
** Seating arrangements and areas for interactive activities (like doodle tables) were considered. We may be able to put them out in the main venue space.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Miscellaneous:&#039;&#039;&#039;&lt;br /&gt;
** Questions were raised about the availability and acquisition of CRTs (for retro gaming), with some potential leads mentioned.&lt;br /&gt;
** Mention of potential storage issues if the con were to acquire CRTs.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Next Steps:&#039;&#039;&#039;&lt;br /&gt;
** Finalization of contracts and opening up vendor applications.&lt;br /&gt;
** Continued efforts in staff recruitment and training.&lt;br /&gt;
** Preparation for the next walkthrough of the venue.&lt;br /&gt;
** Further development of marketing strategies, including social media engagement and partnerships.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Mingle Time:&#039;&#039;&#039;&lt;br /&gt;
** After the meeting, there was a designated time for staff to network and discuss roles and tasks further.&lt;br /&gt;
&lt;br /&gt;
=== Closing Remarks ===&lt;br /&gt;
&lt;br /&gt;
* The meeting concluded with an open call for any additional questions or ideas from the attendees.&lt;br /&gt;
* Those interested in specific roles or tasks were encouraged to speak with Tim or other department heads.&lt;br /&gt;
&lt;br /&gt;
The meeting wrapped up with a reminder that continued collaboration and communication will be key as the convention date approaches.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-08-30 ==&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Inventory ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Inventory Day&#039;&#039;&#039;:&lt;br /&gt;
** Scheduled for September 8 at 9:00 AM.&lt;br /&gt;
** Volunteers are needed; early arrival (8:00 AM) is encouraged, though not mandatory.&lt;br /&gt;
** Tasks: The inventory process involves pulling everything out of the storage unit, counting, and then putting it back.&lt;br /&gt;
** Inventory Sheets: There are existing inventory sheets that have been used for the past few years. These may need updating.&lt;br /&gt;
** Digital vs. Paper Inventory: Discussion on whether to digitize the inventory process using phones or continue using paper due to previous difficulties with digital attempts. Currently remaining with paper but will review. &lt;br /&gt;
** Volunteer Roles: More volunteers are needed for the logistics department to help with inventory.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Flyers and Posters:&#039;&#039;&#039;&lt;br /&gt;
** Posters have been ordered and are expected to arrive in about two weeks.&lt;br /&gt;
** &#039;&#039;&#039;Distribution:&#039;&#039;&#039; Cupcakedoll is actively distributing flyers across various locations. Others are encouraged to do the same once more flyers are available.&lt;br /&gt;
** &#039;&#039;&#039;Flier Locations:&#039;&#039;&#039; Noted that some locations, like Game Kastle, might be less receptive to flyers.&lt;br /&gt;
** &#039;&#039;&#039;Other Conventions:&#039;&#039;&#039; Suggestions to advertise at other conventions.&lt;br /&gt;
* &#039;&#039;&#039;Social Media:&#039;&#039;&#039; There is a need to increase social media activity to promote the convention further.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Department Leadership:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is leading the gaming department &lt;br /&gt;
** Support from other staff members is assured.&lt;br /&gt;
* &#039;&#039;&#039;CRT and Console Rentals:&#039;&#039;&#039;&lt;br /&gt;
** Efforts are being made to source CRT TVs for the gaming tournaments.&lt;br /&gt;
** &#039;&#039;&#039;Contacts:&#039;&#039;&#039; Attempts to contact Abe, who may have CRTs, and explore rental options at Cap and Games.&lt;br /&gt;
** &#039;&#039;&#039;Consoles:&#039;&#039;&#039; There’s a need for 20-25 consoles for a tournament, with current availability being around 12-15.&lt;br /&gt;
** &#039;&#039;&#039;Challenges:&#039;&#039;&#039; Securing enough consoles to avoid the tournament running late is a significant concern. Without enough consoles, running the tournament may not be feasible.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer Consoles:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on how to incentivize people to lend their consoles for the event.&lt;br /&gt;
** &#039;&#039;&#039;Suggestions:&#039;&#039;&#039; Offering volunteer hours as a percentage discount on badges in exchange for console loans.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Coordination ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing Needs:&#039;&#039;&#039;&lt;br /&gt;
** There’s a push to have more people sign up for staff roles, with a reminder that the convention is about two months away.&lt;br /&gt;
** &#039;&#039;&#039;Volunteer Roles:&#039;&#039;&#039; The convention still needs volunteers across various departments, including programming, registration, and general staffing roles.&lt;br /&gt;
** &#039;&#039;&#039;Benefits:&#039;&#039;&#039; Volunteers can get their badge cost refunded after completing 12 hours of work, with a prorated refund available for fewer hours.&lt;br /&gt;
** &#039;&#039;&#039;Recruitment&#039;&#039;&#039;: Staff members are encouraged to recruit friends and community members to volunteer.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer and Staff Contracts:&#039;&#039;&#039;&lt;br /&gt;
** A reminder that staff contracts need to be completed as soon as possible to finalize roles.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Concerns ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Center Walkthrough:&#039;&#039;&#039;&lt;br /&gt;
** There’s a need to schedule a walkthrough of the new convention center to address concerns, particularly regarding lighting.&lt;br /&gt;
* &#039;&#039;&#039;Main Stage Lighting:&#039;&#039;&#039;&lt;br /&gt;
** Concerns were raised about the quality of lighting on the main stage, as poor lighting affected photography during the previous year.&lt;br /&gt;
** &#039;&#039;&#039;Solutions:&#039;&#039;&#039; Potential solutions include renting or purchasing LED lights to improve the stage lighting.&lt;br /&gt;
* &#039;&#039;&#039;Layout Planning:&#039;&#039;&#039;&lt;br /&gt;
** The layout for the convention spaces needs to be finalized and submitted to the venue. A draft of the main space layout is ready, but other rooms still need to be organized.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Nervousness and Excitement:&#039;&#039;&#039;&lt;br /&gt;
** Several staff members expressed a mix of excitement and nervousness about the upcoming convention, especially given the new venue and leadership roles.&lt;br /&gt;
** &#039;&#039;&#039;Encouragement:&#039;&#039;&#039; The leadership team encouraged everyone to communicate their concerns and offered support to ensure a successful event.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-09-21 ==&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* Meeting Space Issues&lt;br /&gt;
** The original meeting room was unavailable due to backstock, so the team had to relocate to a smaller space.&lt;br /&gt;
** Ongoing technical difficulties with the audio setup and Discord transcription services.&lt;br /&gt;
* Reno-Sparks Convention Center&lt;br /&gt;
** Event dates: November 1-3, 2024, with Day Zero starting on October 31, 2024.&lt;br /&gt;
** Venue address: 4590 S Virginia St, Reno, NV 89502.&lt;br /&gt;
* CRT Monitors for Gaming&lt;br /&gt;
** A query was raised regarding obtaining CRT monitors for retro gaming, with a potential deal to borrow them for free since SNAFU Con originally provided them.&lt;br /&gt;
** William (Derp) is coordinating with Skyline to finalize the monitor logistics, and a pickup date will be determined soon.&lt;br /&gt;
* Convention Layout and Hallways&lt;br /&gt;
** The convention hallways are significantly large, providing ample space for setup, including planned conversation pods for attendees to rest.&lt;br /&gt;
** There will be cars from a display that the venue would like to keep there. One car might need to be moved, but overall, it’s not considered a major issue.&lt;br /&gt;
* Table Setup and Placement&lt;br /&gt;
** Artist Alley and vendor spaces are being optimized. There was discussion about avoiding the obstruction of key views by the pipe and drape for guest tables. Possible solutions include:&lt;br /&gt;
*** Moving guest banners to the front of the tables instead of using pipe and drape.&lt;br /&gt;
* Power and Charging Stations&lt;br /&gt;
** Discussion about including charging stations in conversation pods, but it was clarified that they would not have power access for this year.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* Gaming Console Contributions&lt;br /&gt;
** Derp is finalizing console and game contributions from volunteers. Volunteers should bring one console, 1-2 controllers, and one game per console.&lt;br /&gt;
** There’s a need to coordinate the finalization of hours worked for contributing consoles and the announcement for sign-ups.&lt;br /&gt;
* Retro Gaming Section&lt;br /&gt;
** Retro consoles such as PS3 and Xbox 360 or older will be part of the gaming section, along with unique and rare consoles to appeal to attendees.&lt;br /&gt;
* Tournament Brackets&lt;br /&gt;
** Derp is working on setting up brackets for gaming tournaments and plans to announce the event over the weekend.&lt;br /&gt;
* Magic: The Gathering RCQ Tournament&lt;br /&gt;
** Plans to host a Regional Championship Qualifier (RCQ) for Magic: The Gathering at the convention. This would be a high-level local tournament that could help draw attendees.&lt;br /&gt;
** Special tournament badges will be offered at a discounted price, combining both day passes and tournament entry fees.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotions ===&lt;br /&gt;
&lt;br /&gt;
* Posters and Discount Codes&lt;br /&gt;
** Coordinating the distribution of convention posters across venues and local colleges. Each poster will include a discount code, with CupcakeDoll managing the creation of these codes.&lt;br /&gt;
** Posters should be placed only where they’re welcome, and coordinators should avoid places where they might cause issues.&lt;br /&gt;
* Social Media and Advertising&lt;br /&gt;
** Planning to use social media ads, particularly on Facebook, to promote events like a potential trick-or-treat event during the convention. These targeted ads would aim at drawing in families and younger attendees.&lt;br /&gt;
&lt;br /&gt;
=== Contracts and Signatures ===&lt;br /&gt;
&lt;br /&gt;
* Contract Issues&lt;br /&gt;
** Some contract files lacked signature fields, creating problems for electronic signing. Staff members have submitted as much as they could without signatures.&lt;br /&gt;
** A volunteer contract is being created that should be easily signable.&lt;br /&gt;
&lt;br /&gt;
=== Special Events ===&lt;br /&gt;
&lt;br /&gt;
* Trick-or-Treating Event&lt;br /&gt;
** Discussions around hosting a trick-or-treat event during the convention, where cosplayers hand out candy to children. The event could become a big draw for families.&lt;br /&gt;
** The team is working on getting approval from Aramark.&lt;br /&gt;
* Performance and Guest Events&lt;br /&gt;
** A guest performance featuring singing is planned. Karaoke will not be held on the main stage this year.&lt;br /&gt;
** DJ performances and a dance event are scheduled, with a possibility of integrating a VR dance club portal that connects to a virtual environment. This requires network drops or alternative solutions like Ethernet connections.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Management and Staffing ===&lt;br /&gt;
&lt;br /&gt;
* Logistics and Volunteer Coordination&lt;br /&gt;
** The logistics department is understaffed due to the departure of some department heads. They’re actively recruiting volunteers to handle load-ins, load-outs, and other logistical tasks, particularly for Wednesday and Monday shifts.&lt;br /&gt;
** Efforts are being made to coordinate staff availability for key load-in and load-out days, especially the day before and after the convention.&lt;br /&gt;
* Volunteer Scheduling&lt;br /&gt;
** There is a significant need for volunteers for load-out on Monday, the hardest day to staff. Scheduling posts will be updated in the logistics channel.&lt;br /&gt;
&lt;br /&gt;
=== Video Room and Media Permissions ===&lt;br /&gt;
&lt;br /&gt;
* Issues with Video Permissions&lt;br /&gt;
** The video room coordinator is still working to secure permissions for screenings. Funimation is no longer a reliable source, but requests have been sent to companies like Media Blasters and Discotek.&lt;br /&gt;
** Public domain content may be used as a fallback if no permissions are granted in time.&lt;br /&gt;
* Coordination with Media Blasters&lt;br /&gt;
** A historical note was mentioned about obtaining permissions directly from the founder of Media Blasters using his personal contact details found in a public document.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Topics ===&lt;br /&gt;
&lt;br /&gt;
* Earplugs for Attendees&lt;br /&gt;
** A suggestion was made to provide cheap earplugs at registration if noise pollution between the main stage and vendor area becomes an issue. However, it’s not expected to be a major problem.&lt;br /&gt;
* Workshop Rooms&lt;br /&gt;
** There will be no dedicated workshop rooms, but certain breakout rooms may serve similar functions.&lt;br /&gt;
* Halloween Decorations&lt;br /&gt;
** The team discussed the timing of the convention (right after Halloween) and the difficulty in sourcing Halloween decorations during that period.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - 2024-10-06 ==&lt;br /&gt;
&lt;br /&gt;
=== General Reminders ===&lt;br /&gt;
&lt;br /&gt;
* Staff Sign-ups: Staff members were reminded to sign up for roles, particularly in areas like logistics.&lt;br /&gt;
* Panel Submissions: Urgent reminder to submit panels, with emphasis on finalizing the con schedule soon.&lt;br /&gt;
* Con Book Deadlines: Last call for submitting information (e.g., panel details, logos) for inclusion in the con book. Work on the book is happening this weekend: 10/12.&lt;br /&gt;
* Guest Announcements: Guest information has not been widely announced yet, and marketing needs to expedite this process.&lt;br /&gt;
&lt;br /&gt;
=== Classic Consoles and E-Gaming ===&lt;br /&gt;
&lt;br /&gt;
* Classic Consoles: Staff members need to sign up for this section. The more obscure the console, the better. A thread was linked for sign-ups: https://discord.com/channels/416146296097865729/1279259494236291212&lt;br /&gt;
* Equipment Status: CRT TVs for classic consoles need further confirmation, but PS5s and monitors for other gaming areas are set.&lt;br /&gt;
&lt;br /&gt;
=== Con Book and Map Creation ===&lt;br /&gt;
&lt;br /&gt;
* Map for Tables: Nuriko Windchaser requested a table map layout, which will be completed within the week.&lt;br /&gt;
* Con Book Map: The map for the con book and artist tables will be finalized soon and sent out for review.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Guest Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Guest Promotion: Marketing is behind in promoting confirmed guests, and there&#039;s a need for immediate action to make the guest lineup public.&lt;br /&gt;
* Graphics: Marketing materials are still in progress, and several guest graphics will soon be sent for approval.&lt;br /&gt;
&lt;br /&gt;
=== Cosplayers and Performers ===&lt;br /&gt;
&lt;br /&gt;
* Cosplay Coordination: Discussions are underway to involve both cosplayers and the Buccaneers for day-zero candy distribution. Tim will reach out to both. &lt;br /&gt;
&lt;br /&gt;
=== Hotel and Staff Dorms ===&lt;br /&gt;
&lt;br /&gt;
* Dorm System: Dorms are available for staff at $25 per person per night or $100 for a full room. Staff interested in this option need to contact Beta directly.&lt;br /&gt;
* Affordable Option: This dorm system is significantly cheaper than standard hotel rates, and the convention is absorbing some of the costs to make it affordable for staff.&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Volunteers ===&lt;br /&gt;
&lt;br /&gt;
* Logistics Staffing: Volunteers are needed for load-in on Wednesday and Thursday (10/30-10/31). Shelby, the new logistics head, noted they might miss Monday due to work travel but will be available for most of the weekend.&lt;br /&gt;
* Post-Con Load-Out: Additional volunteers are needed for Monday after the con (11/4) to help with loading trucks back into storage, as this day typically lacks sufficient help.&lt;br /&gt;
&lt;br /&gt;
=== Registration and Training Video ===&lt;br /&gt;
&lt;br /&gt;
* New Registration Training: A new 20-minute registration training video will cover policies and customer service procedures. All registration staff are required to watch it before working at Registration.&lt;br /&gt;
* Software Changes: Minor changes to the registration system include the removal of vaccine check requirements. Overall, the process remains similar to previous years.&lt;br /&gt;
&lt;br /&gt;
=== Philanthropy and Charity Auction ===&lt;br /&gt;
&lt;br /&gt;
* New Philanthropy Head: Elizabeth was introduced as the head of philanthropy.&lt;br /&gt;
* Charity Auction: Volunteers are needed to gather donations from vendors for the charity auction. Assistance is also required to organize items, label them, and set starting prices for the auction on Sunday.&lt;br /&gt;
&lt;br /&gt;
=== Security and Rovers ===&lt;br /&gt;
&lt;br /&gt;
* ESI Security: Additional support from ESI security will be available on Saturday, the busiest day of the con, to help with badge checks and general assistance. However, SNAFU Con staff will retain primary authority.&lt;br /&gt;
* Rovers Support: ESI security will provide extra manpower, but there was discussion about how to make them approachable for attendees who might have questions.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Panels ===&lt;br /&gt;
&lt;br /&gt;
* Panel Coverage: The programming department needs more volunteers, especially on Friday. Natasha, the former head of programming, will be available to help out.&lt;br /&gt;
* Panel Approvals: Notices are being sent to panelists regarding their submission statuses.&lt;br /&gt;
&lt;br /&gt;
=== Artist Alley and Vendor Management ===&lt;br /&gt;
&lt;br /&gt;
* Table Allocation: Nuriko Windchaser requested 52 tables for Artist Alley, which is more than originally planned. Tim confirmed there would likely be enough extra tables due to fewer club reservations.&lt;br /&gt;
* Vendor Donations for Charity Auction: Vendors will be asked for donations for the charity auction, and more volunteers are needed to assist with this effort.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Theme Decorations: Fun science-themed decorations, including interactive toys, have been purchased for the event.&lt;br /&gt;
* Tech and Equipment: Some equipment from last year needs to be replaced. An updated tech document, including room layouts, has been shared, and the wiki is up to date.&lt;br /&gt;
* Merchandise and Auction Donations: Vendors and artists are encouraged to donate items for the charity auction.&lt;br /&gt;
&lt;br /&gt;
=== Closing and Open Floor ===&lt;br /&gt;
&lt;br /&gt;
* Budget Requests: Staff were reminded to submit [https://register.snafucon.com/admin/budget_request/form budget requests] if they need additional resources or materials.&lt;br /&gt;
* Science-Themed Jokes for Con Book: The meeting wrapped up with a lighthearted discussion about creating original science-themed jokes for the con book.&lt;br /&gt;
* Open Questions: The meeting concluded with an open floor for additional questions or concerns.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - 2024-10-20 ==&lt;br /&gt;
&lt;br /&gt;
=== General Convention Overview: ===&lt;br /&gt;
&lt;br /&gt;
* Preparation Status:&lt;br /&gt;
** The team feels confident in their progress overall. Tim mentions that despite being close to the event, everything seems to be going well.&lt;br /&gt;
** The focus is on completing the remaining tasks, as anything not finished soon will likely be a source of last-minute stress.&lt;br /&gt;
&lt;br /&gt;
=== Program Book &amp;amp; Digital Files: ===&lt;br /&gt;
&lt;br /&gt;
* Program Book Preview:&lt;br /&gt;
** A preview of the program book is ready for review. Team members are encouraged to check it and report any errors.&lt;br /&gt;
** There was a conversation about the importance of opening the file in proper programs like Adobe Reader to avoid rendering issues, as some programs (e.g., Dropbox) cause display problems.&lt;br /&gt;
&lt;br /&gt;
=== Staff and Volunteer Logistics: ===&lt;br /&gt;
&lt;br /&gt;
* Food for Staff:&lt;br /&gt;
** Tim is finalizing food court options, and staff members were asked to notify if there’s nothing suitable on the menu for dietary reasons.&lt;br /&gt;
** There will be some attempts to ensure staff members have access to food throughout the event, though breakfast will likely be an individual responsibility.&lt;br /&gt;
** A possible plan involving food runners (volunteers delivering food to busy staff) is being considered.&lt;br /&gt;
** The main food service will operate from the Food Court during the following hours:&lt;br /&gt;
*** Friday: 3 PM - 10 PM&lt;br /&gt;
*** Saturday: 12 PM - 10 PM&lt;br /&gt;
*** Sunday: 12 PM - 4 PM&lt;br /&gt;
* “Tablecloths”:&lt;br /&gt;
** “Tablecloths” is a code word we will be using at con. All staff need to know what it is. If you don’t know what it means, please ask in chat. We do not post the meaning publicly in our wiki or meeting notes.&lt;br /&gt;
* Volunteer Staffing:&lt;br /&gt;
** There was a discussion about the need for additional volunteers for roles such as badge checks and general staffing. Aidan (Rover head) pointed out that more people are always needed.&lt;br /&gt;
** Volunteers can sign up at the convention itself.&lt;br /&gt;
** Blanca (Volunteer Head) confirmed that she will be at the convention earlier than in previous years to handle volunteer contracts and assignments.&lt;br /&gt;
&lt;br /&gt;
=== Event Logistics: ===&lt;br /&gt;
&lt;br /&gt;
* Setup and Tear Down Schedule:&lt;br /&gt;
** The logistics team plans to begin setup on Wednesday afternoon, with staff loading trucks and taking materials to the venue.&lt;br /&gt;
** Tear-down will start right after closing ceremonies on Sunday, with final wrap-up happening by Monday morning.&lt;br /&gt;
** Volunteers were asked to join logistics to ensure a smooth setup and breakdown process.&lt;br /&gt;
* Parking:&lt;br /&gt;
** Staff will not be charged for parking during setup (Thursday).&lt;br /&gt;
** For the rest of the event, parking passes will be distributed, though anyone arriving after Thursday may have to pay for parking if they don&#039;t pick up a pass in advance or request assistance. &lt;br /&gt;
&lt;br /&gt;
=== Gaming and Console Section: ===&lt;br /&gt;
&lt;br /&gt;
* CRTs and Consoles:&lt;br /&gt;
** A key concern is the pickup of CRTs (cathode ray tube monitors) for retro gaming setups. William (Derp) mentioned issues with communication regarding the pickup of these monitors from a vendor named Skyline, who was slow to respond. Determined he had likely been busy with another event. &lt;br /&gt;
** There are plans to have around five CRTs for the gaming section, and more consoles are being confirmed, including NES, SNES, PS2, and N64.&lt;br /&gt;
** Specific games like Guitar Hero II and Shadow the Hedgehog were discussed as options to be included in the gaming lineup.&lt;br /&gt;
&lt;br /&gt;
=== Badge and Panel Logistics: ===&lt;br /&gt;
&lt;br /&gt;
* Badge Checks:&lt;br /&gt;
** Badge check locations were discussed, particularly around entry points and key areas, to ensure proper flow of attendees.&lt;br /&gt;
** There will be a simplified layout for badge checks to direct people straight from registration into the main vendor room.&lt;br /&gt;
* Panel Schedule:&lt;br /&gt;
** A tentative panel schedule has been posted, but it is still awaiting feedback and minor adjustments.&lt;br /&gt;
** The final panel schedule will be printed and distributed as soon as it&#039;s finalized.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Communication: ===&lt;br /&gt;
&lt;br /&gt;
* Staff Contracts:&lt;br /&gt;
** Staff members who haven’t completed their contracts were reminded to submit them before the event. Contracts will not be processed at the convention. (You will be removed as staff if you don’t get it done.)&lt;br /&gt;
** Cassy is in charge of collecting contracts and has been offering help to those having trouble submitting them electronically.&lt;br /&gt;
* Theme Voting for Next Year:&lt;br /&gt;
** The next meeting will involve voting on the theme for next year’s convention. Staff members were encouraged to think of fun ideas for themes and attend the meeting to have a say.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous: ===&lt;br /&gt;
&lt;br /&gt;
* Prizes and Merchandise:&lt;br /&gt;
** Llama delivered a batch of prizes for the prize booth, which will include various attractive items that staff members might enjoy.&lt;br /&gt;
** Staff were encouraged to check out the prize booth during the event.&lt;br /&gt;
* Vaccination Policy:&lt;br /&gt;
** There is no requirement for proof of vaccination this year, although it is still recommended to avoid illness.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Phone_System&amp;diff=1792</id>
		<title>Phone System</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Phone_System&amp;diff=1792"/>
		<updated>2024-10-13T15:28:27Z</updated>

		<summary type="html">&lt;p&gt;Beta: added phone message scripts&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We have used &#039;&#039;&#039;Phone.com&#039;&#039;&#039; for our phone system since 2012. While there are cheaper alternatives if we want to do more legwork to manage the system, phone.com had a simple enough setup in the beginning for setting up a phone system with different lines without too much fore-knowledge. We pay approximately $420 per year on phone.com, although in 2012 we were only paying about $180/year. &lt;br /&gt;
&lt;br /&gt;
We may consider replacing the system someday but it is a lower priority than some of our other costs. &lt;br /&gt;
&lt;br /&gt;
We can take incoming calls to our cellphones, make outgoing calls through their system, which does have an app, and we can send and receive texts. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Over the years we&#039;ve mostly just devolved into using the one line, internally referenced as the Rovers line. We have a few phone numbers, but probably should pare it down to just the one&lt;br /&gt;
&lt;br /&gt;
== Phone Messages ==&lt;br /&gt;
We have two messages we set on our system for when we are open or closed. &lt;br /&gt;
&lt;br /&gt;
=== Open Message ===&lt;br /&gt;
This is the message that plays while the system dials through our phones to try to find someone to pick up and help them.&amp;lt;blockquote&amp;gt;Thank you for calling the SNAFU Con Hotline&lt;br /&gt;
&lt;br /&gt;
If you know your party&#039;s extension you may dial it at any time&lt;br /&gt;
&lt;br /&gt;
Stay on the line and we will try to reach a staff member for you&lt;br /&gt;
&lt;br /&gt;
If no one is available, you will be prompted to leave a voicemail.&lt;br /&gt;
&lt;br /&gt;
We will return as soon as we can!&lt;br /&gt;
&lt;br /&gt;
Have a great con!&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Closed Message / Voicemail Message ===&lt;br /&gt;
If we are closed, or no one picked up their phone, this is the message to prompt for voicemail. &#039;&#039;&#039;Note that it will need to be re-recorded for every location we host at.&#039;&#039;&#039;&amp;lt;blockquote&amp;gt;You&#039;ve reached the SNAFU CON voicemail&lt;br /&gt;
&lt;br /&gt;
Come down and join us at the Reno Sparks Convention Center&lt;br /&gt;
&lt;br /&gt;
Please leave us a message and we will get back to you as soon as we can!&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Opening / Closing ==&lt;br /&gt;
&lt;br /&gt;
==== Overview ====&lt;br /&gt;
The system is set up to route calls to the appropriate teams, with different handling methods depending on whether the event is open or closed. The primary number we use is the &amp;quot;SNAFU Hotline,&amp;quot; which is the main line for the event. We also have other numbers, including a company line and two 800 numbers, but they are rarely used and ignored in this configuration.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;SNAFU Hotline&#039;&#039;&#039; configuration involves setting up different schedules to manage calls during and outside of event hours. This document outlines how we handle this, why we set it up the way we do, and considerations for future events.&lt;br /&gt;
&lt;br /&gt;
==== Why We Do It This Way ====&lt;br /&gt;
The challenge with Phone.com is that their scheduling system doesn’t allow for complex open/close setups across midnight, which is crucial for a 24-hour event like SNAFU Con. We need to manage hotline availability to ensure calls are routed properly to the Rovers when the event is active, while sending calls to voicemail during closed hours. The system also doesn’t natively support splitting the day across midnight without closing the line entirely during the overlap period.&lt;br /&gt;
&lt;br /&gt;
To work around this, we use a &amp;quot;reverse schedule&amp;quot; approach, defining &#039;&#039;&#039;closed hours&#039;&#039;&#039; instead of open hours. This allows us to manage the hotline’s availability more flexibly, especially during event days that run late into the night or early morning.&lt;br /&gt;
&lt;br /&gt;
==== Current Configuration ====&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Hotline Setup&#039;&#039;&#039;:  The SNAFU Hotline’s call handling is managed through two sections in Phone.com:&lt;br /&gt;
#* &#039;&#039;&#039;Top Section (Closed Hours)&#039;&#039;&#039;: When the schedule indicates the hotline is closed, calls are sent directly to voicemail for the Rovers extension.&lt;br /&gt;
#* &#039;&#039;&#039;Bottom Section (Open Hours)&#039;&#039;&#039;: When the schedule doesn’t apply (i.e., the hotline is open), calls are routed to the Rovers queue. The system attempts to connect with available Rovers, and if no one is available, the call goes to voicemail.&lt;br /&gt;
# &#039;&#039;&#039;Reverse Schedule Definition&#039;&#039;&#039;:  Phone.com schedules normally allow you to set open hours for each day of the week. However, since we need the hotline to stay open past midnight, we reversed the logic by defining closed hours instead of open hours. Here’s how the schedule is configured:&lt;br /&gt;
#* &#039;&#039;&#039;Main Schedule&#039;&#039;&#039;: For weekdays when the event is not running, we set the hotline to be closed from midnight to midnight (i.e., closed all day).&lt;br /&gt;
#* &#039;&#039;&#039;Exception Days (Event Days)&#039;&#039;&#039;: For days when the event is active, we define exceptions. For example:&lt;br /&gt;
#** Thursday: Closed from midnight to noon, then open from noon to midnight.&lt;br /&gt;
#** Friday, Saturday, and Sunday: Closed from 3:00 a.m. to 8:00 a.m., then open from 8:00 a.m. to midnight.&lt;br /&gt;
# &#039;&#039;&#039;Challenges with Midnight Crossovers&#039;&#039;&#039;:  The main complication comes from Phone.com’s inability to define schedules that cross over midnight without closing the line for the entire day. For example, we can’t configure the hotline to be open from midnight to 3:00 a.m. and then again from 8:00 a.m. to midnight. To address this, we’ve defined the schedule as closed from 3:00 a.m. to 8:00 a.m. on event days. This keeps the hotline open during peak hours and only closed for a few hours of downtime.&lt;br /&gt;
&lt;br /&gt;
==== Future Considerations ====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Switching to a Positive Schedule&#039;&#039;&#039;:  In future years, we may switch from a “closed” schedule to an “open” schedule to simplify management. This would allow us to define the hotline as open from specific hours, such as 10:00 a.m. to 11:00 p.m., rather than working with a reverse schedule. However, the current reverse setup has worked well, and there’s no pressing need to change it yet.&lt;br /&gt;
* &#039;&#039;&#039;Sunday Closure&#039;&#039;&#039;:  Currently, the hotline stays open until midnight on Sunday as we continue event-related tasks late anyway. We may consider closing the hotline earlier on Sunday in future years, but for now, we’ve decided to keep it open until the end of the event.&lt;br /&gt;
&lt;br /&gt;
==== Steps to Configure Hotline in Phone.com ====&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Access the Hotline Configuration&#039;&#039;&#039;:&lt;br /&gt;
#* Log into Phone.com and locate the &#039;&#039;&#039;SNAFU Hotline&#039;&#039;&#039; number.&lt;br /&gt;
#* Edit the &#039;&#039;&#039;call handling settings&#039;&#039;&#039; for this number.&lt;br /&gt;
# &#039;&#039;&#039;Define the Schedule&#039;&#039;&#039;:&lt;br /&gt;
#* In the settings, there are two sections:&lt;br /&gt;
#** &#039;&#039;&#039;Top Section&#039;&#039;&#039;: Controlled by a schedule, set this to send calls to voicemail during closed hours.&lt;br /&gt;
#** &#039;&#039;&#039;Bottom Section&#039;&#039;&#039;: Set this to route calls to the Rovers queue during open hours.&lt;br /&gt;
# &#039;&#039;&#039;Set Up Closed Hours&#039;&#039;&#039;:&lt;br /&gt;
#* Configure the schedule as &#039;&#039;&#039;closed&#039;&#039;&#039; from 3:00 a.m. to 8:00 a.m. on Friday, Saturday, and Sunday.&lt;br /&gt;
#* For days when the event isn’t running (weekdays), set the schedule to be closed from midnight to midnight.&lt;br /&gt;
# &#039;&#039;&#039;Add Exception Dates&#039;&#039;&#039;:&lt;br /&gt;
#* For event days, use the exception system to define specific open hours. For example, for Thursday, set the hotline to be closed from midnight to noon, then open from noon to midnight.&lt;br /&gt;
# &#039;&#039;&#039;Test and Adjust&#039;&#039;&#039;:&lt;br /&gt;
#* Test the schedule to ensure it works as expected, especially with midnight crossovers. Make adjustments as necessary based on event needs.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Phone_System&amp;diff=1791</id>
		<title>Phone System</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Phone_System&amp;diff=1791"/>
		<updated>2024-10-13T15:01:30Z</updated>

		<summary type="html">&lt;p&gt;Beta: create phone.com wiki page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We have used &#039;&#039;&#039;Phone.com&#039;&#039;&#039; for our phone system since 2012. While there are cheaper alternatives if we want to do more legwork to manage the system, phone.com had a simple enough setup in the beginning for setting up a phone system with different lines without too much fore-knowledge. We pay approximately $420 per year on phone.com, although in 2012 we were only paying about $180/year. &lt;br /&gt;
&lt;br /&gt;
We may consider replacing the system someday but it is a lower priority than some of our other costs. &lt;br /&gt;
&lt;br /&gt;
We can take incoming calls to our cellphones, make outgoing calls through their system, which does have an app, and we can send and receive texts. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Over the years we&#039;ve mostly just devolved into using the one line, internally referenced as the Rovers line. We have a few phone numbers, but probably should pare it down to just the one&lt;br /&gt;
&lt;br /&gt;
== Phone Messages ==&lt;br /&gt;
We have two messages we set on our system for when we are open or closed. &lt;br /&gt;
&lt;br /&gt;
{insert scripts and explanations here}&lt;br /&gt;
&lt;br /&gt;
== Opening / Closing ==&lt;br /&gt;
&lt;br /&gt;
==== Overview ====&lt;br /&gt;
The system is set up to route calls to the appropriate teams, with different handling methods depending on whether the event is open or closed. The primary number we use is the &amp;quot;SNAFU Hotline,&amp;quot; which is the main line for the event. We also have other numbers, including a company line and two 800 numbers, but they are rarely used and ignored in this configuration.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;SNAFU Hotline&#039;&#039;&#039; configuration involves setting up different schedules to manage calls during and outside of event hours. This document outlines how we handle this, why we set it up the way we do, and considerations for future events.&lt;br /&gt;
&lt;br /&gt;
==== Why We Do It This Way ====&lt;br /&gt;
The challenge with Phone.com is that their scheduling system doesn’t allow for complex open/close setups across midnight, which is crucial for a 24-hour event like SNAFU Con. We need to manage hotline availability to ensure calls are routed properly to the Rovers when the event is active, while sending calls to voicemail during closed hours. The system also doesn’t natively support splitting the day across midnight without closing the line entirely during the overlap period.&lt;br /&gt;
&lt;br /&gt;
To work around this, we use a &amp;quot;reverse schedule&amp;quot; approach, defining &#039;&#039;&#039;closed hours&#039;&#039;&#039; instead of open hours. This allows us to manage the hotline’s availability more flexibly, especially during event days that run late into the night or early morning.&lt;br /&gt;
&lt;br /&gt;
==== Current Configuration ====&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Hotline Setup&#039;&#039;&#039;:  The SNAFU Hotline’s call handling is managed through two sections in Phone.com:&lt;br /&gt;
#* &#039;&#039;&#039;Top Section (Closed Hours)&#039;&#039;&#039;: When the schedule indicates the hotline is closed, calls are sent directly to voicemail for the Rovers extension.&lt;br /&gt;
#* &#039;&#039;&#039;Bottom Section (Open Hours)&#039;&#039;&#039;: When the schedule doesn’t apply (i.e., the hotline is open), calls are routed to the Rovers queue. The system attempts to connect with available Rovers, and if no one is available, the call goes to voicemail.&lt;br /&gt;
# &#039;&#039;&#039;Reverse Schedule Definition&#039;&#039;&#039;:  Phone.com schedules normally allow you to set open hours for each day of the week. However, since we need the hotline to stay open past midnight, we reversed the logic by defining closed hours instead of open hours. Here’s how the schedule is configured:&lt;br /&gt;
#* &#039;&#039;&#039;Main Schedule&#039;&#039;&#039;: For weekdays when the event is not running, we set the hotline to be closed from midnight to midnight (i.e., closed all day).&lt;br /&gt;
#* &#039;&#039;&#039;Exception Days (Event Days)&#039;&#039;&#039;: For days when the event is active, we define exceptions. For example:&lt;br /&gt;
#** Thursday: Closed from midnight to noon, then open from noon to midnight.&lt;br /&gt;
#** Friday, Saturday, and Sunday: Closed from 3:00 a.m. to 8:00 a.m., then open from 8:00 a.m. to midnight.&lt;br /&gt;
# &#039;&#039;&#039;Challenges with Midnight Crossovers&#039;&#039;&#039;:  The main complication comes from Phone.com’s inability to define schedules that cross over midnight without closing the line for the entire day. For example, we can’t configure the hotline to be open from midnight to 3:00 a.m. and then again from 8:00 a.m. to midnight. To address this, we’ve defined the schedule as closed from 3:00 a.m. to 8:00 a.m. on event days. This keeps the hotline open during peak hours and only closed for a few hours of downtime.&lt;br /&gt;
&lt;br /&gt;
==== Future Considerations ====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Switching to a Positive Schedule&#039;&#039;&#039;:  In future years, we may switch from a “closed” schedule to an “open” schedule to simplify management. This would allow us to define the hotline as open from specific hours, such as 10:00 a.m. to 11:00 p.m., rather than working with a reverse schedule. However, the current reverse setup has worked well, and there’s no pressing need to change it yet.&lt;br /&gt;
* &#039;&#039;&#039;Sunday Closure&#039;&#039;&#039;:  Currently, the hotline stays open until midnight on Sunday as we continue event-related tasks late anyway. We may consider closing the hotline earlier on Sunday in future years, but for now, we’ve decided to keep it open until the end of the event.&lt;br /&gt;
&lt;br /&gt;
==== Steps to Configure Hotline in Phone.com ====&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Access the Hotline Configuration&#039;&#039;&#039;:&lt;br /&gt;
#* Log into Phone.com and locate the &#039;&#039;&#039;SNAFU Hotline&#039;&#039;&#039; number.&lt;br /&gt;
#* Edit the &#039;&#039;&#039;call handling settings&#039;&#039;&#039; for this number.&lt;br /&gt;
# &#039;&#039;&#039;Define the Schedule&#039;&#039;&#039;:&lt;br /&gt;
#* In the settings, there are two sections:&lt;br /&gt;
#** &#039;&#039;&#039;Top Section&#039;&#039;&#039;: Controlled by a schedule, set this to send calls to voicemail during closed hours.&lt;br /&gt;
#** &#039;&#039;&#039;Bottom Section&#039;&#039;&#039;: Set this to route calls to the Rovers queue during open hours.&lt;br /&gt;
# &#039;&#039;&#039;Set Up Closed Hours&#039;&#039;&#039;:&lt;br /&gt;
#* Configure the schedule as &#039;&#039;&#039;closed&#039;&#039;&#039; from 3:00 a.m. to 8:00 a.m. on Friday, Saturday, and Sunday.&lt;br /&gt;
#* For days when the event isn’t running (weekdays), set the schedule to be closed from midnight to midnight.&lt;br /&gt;
# &#039;&#039;&#039;Add Exception Dates&#039;&#039;&#039;:&lt;br /&gt;
#* For event days, use the exception system to define specific open hours. For example, for Thursday, set the hotline to be closed from midnight to noon, then open from noon to midnight.&lt;br /&gt;
# &#039;&#039;&#039;Test and Adjust&#039;&#039;&#039;:&lt;br /&gt;
#* Test the schedule to ensure it works as expected, especially with midnight crossovers. Make adjustments as necessary based on event needs.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1790</id>
		<title>RT</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1790"/>
		<updated>2024-10-10T14:24:04Z</updated>

		<summary type="html">&lt;p&gt;Beta: add steps on how to forward an email to RT&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Procedures]][[Category:Third Party Software]]&lt;br /&gt;
==Request Tracker==&lt;br /&gt;
RT (Request Tracker) is the ticketing system the con uses to handle email requests. As of 2016, &#039;&#039;&#039;all&#039;&#039;&#039; departmental emails are handled in RT. &lt;br /&gt;
&lt;br /&gt;
The best way to think of RT is like a really fancy group email system. Queues are the group email boxes. Multiple people can see and handle emails, and everyone who is involved with that box gets updated on everything going on so that everyone is on the same page.&lt;br /&gt;
==Video Tutorials==&lt;br /&gt;
Beta made a four-part video tutorial series, which is posted on our YouTube:&lt;br /&gt;
https://www.youtube.com/playlist?list=PLnJMQShIVjsl4XuTJJ4bPEYWDJJowhEN0&lt;br /&gt;
==Logging in ==&lt;br /&gt;
You can access RT from https://tickets.snafucon.com/&#039;&#039;&#039;.&#039;&#039;&#039; Your account is linked to [[BACON]] so log in with your current username and password. However, you will need to have privileges set up by the admin or you will only be able to see your previous tickets (if any) but not actually be able to see or answer any from the queue.&lt;br /&gt;
== Setting your Signature ==&lt;br /&gt;
When logged in: &lt;br /&gt;
# Hover over &amp;quot;Logged in as {you}&amp;quot;&lt;br /&gt;
# Hover over Settings&lt;br /&gt;
# Click &amp;quot;About Me&amp;quot;&lt;br /&gt;
# Your signature box is on the lower left. Edit as you see fit.&lt;br /&gt;
# Click &amp;quot;Save Preferences&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Signature Format ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;{Your Name}&lt;br /&gt;
&lt;br /&gt;
{Your Title or Department, as relevant}&lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite!&lt;br /&gt;
&lt;br /&gt;
https://snafucon.com&lt;br /&gt;
&lt;br /&gt;
{Optional relevant message}&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Example Signature ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Beta&lt;br /&gt;
&lt;br /&gt;
SNAFU Con Human Resources &lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite! &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;https://snafucon.com&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Apply now! &amp;lt;nowiki&amp;gt;https://register.snafucon.com/staff/apply/&amp;lt;/nowiki&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Queues==&lt;br /&gt;
Most users will only have one Queue, but some users will have multiple ones. The easiest way to navigate RT is by queue. The Queues you have access to are listed on the right-hand side of the screen under &amp;quot;Quick Search.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Click on the queue name to see all the tickets in a queue.&lt;br /&gt;
==Reply/Comment to a Ticket==&lt;br /&gt;
When you reply to a ticket it is sent to all of the people who administer the queue that it is in, and the requester (the person who sent the email in the first place.)&lt;br /&gt;
&lt;br /&gt;
When you comment on a ticket, it is only sent to the people who administer the queue.&lt;br /&gt;
&lt;br /&gt;
There are two ways of replying to and commenting on tickets. &lt;br /&gt;
===Reply by Email ===&lt;br /&gt;
You should only reply by email if you aren&#039;t closing or resolving the ticket. &#039;&#039;&#039;You can not resolve the ticket by email.&#039;&#039;&#039;&lt;br /&gt;
#Simply respond to the email that was sent to you.&lt;br /&gt;
Notice that the email you&#039;re sending goes back to the queue email. So, if you&#039;re responding to an email that originally went to [[/cdn-cgi/l/email-protection|[email protected]]], then the email you send will also go to [[/cdn-cgi/l/email-protection|[email protected]]] It is important that you do not alter the [SNAFU #(number)] part of the subject. RT will look at the subject to put the reply in the right ticket. &lt;br /&gt;
&lt;br /&gt;
The information that is added to the beginning of the email you received (the ticket information with Queue info and Ticket URL, etc.) &#039;&#039;&#039;WILL be included in your email if you don&#039;t delete it&#039;&#039;&#039;. It is up to you if you want that information in your email, but it should probably be removed before sending to minimize confusion.&lt;br /&gt;
===Comment by Email===&lt;br /&gt;
Comment by replying and changing the email to (queue email)[[/cdn-cgi/l/email-protection|[email protected]]] snafucon.com&lt;br /&gt;
So if the queue email was registration, you can comment by sending an email to [[/cdn-cgi/l/email-protection|[email protected]]]&lt;br /&gt;
&lt;br /&gt;
As before, keep the [SNAFU #(number)] part of subject the same so RT can route your comment correctly. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reply/Comment by Logging In===&lt;br /&gt;
To reply to a ticket you need to get into a ticket to view it. You can click on a ticket from your dashboard, or from your queue.&lt;br /&gt;
#To reply/comment to the ticket, scroll down to the &#039;&#039;&#039;History&#039;&#039;&#039; section. You can view all history for this ticket (emails in and out).&lt;br /&gt;
#Click Reply or Comment [[File:History.png]]&lt;br /&gt;
#If you are the first reply, on the right-hand side you may want to update the &#039;&#039;&#039;Status to Open&#039;&#039;&#039; and the &#039;&#039;&#039;Owner to you&#039;&#039;&#039;. RT should update it for you after your reply if you don&#039;t make any settings. &#039;&#039;&#039;If you are closing the ticket&#039;&#039;&#039; you will want to change the status to &#039;&#039;&#039;resolved&#039;&#039;&#039; (or rejected as applicable). [[file:Ticket and Transactions.gif]]&lt;br /&gt;
#Type your reply in the box (if you have one set up, your signature is automatically added to the end of the message - if you are replying at the top of the message make sure your signature is at the top. If you are replying in-line, your signature stays at the bottom).&lt;br /&gt;
# If you want to add a person as a one-time cc or bcc, then do that in the applicable fields&lt;br /&gt;
#When you are ready to send your reply (or add your comment), click &amp;quot;Update Ticket&amp;quot; and your reply will be sent and will show in the ticket history&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; The reply box is exactly the same for reply or comment except it will be pink if you are replying. If you want to change your reply to a comment (or vice versa) on the right-hand side of the screen there is a drop-down menu and you can change whether the message you are writing is a reply or a comment. The color of the text area will change accordingly.&lt;br /&gt;
[[file:Reply-vs-comment.png]]&lt;br /&gt;
==Creating a Ticket/Emailing Out==&lt;br /&gt;
[[File:How to send emails.png|845x845px]]&lt;br /&gt;
==Bulk Update==&lt;br /&gt;
To do a bulk update (&#039;&#039;&#039;most useful for deleting spam&#039;&#039;&#039;):&lt;br /&gt;
#From the landing page, click on the queue you want to update (right-hand side of the screen)&lt;br /&gt;
#In the upper-right corner, click on &#039;&#039;&#039;Bulk Update&#039;&#039;&#039;&lt;br /&gt;
#Uncheck the messages you want to leave alone, or use the &#039;&#039;&#039;Clear All&#039;&#039;&#039; button at the bottom if that&#039;s faster.&lt;br /&gt;
#Once you have only the messages checked that you want to update, scroll to the bottom&lt;br /&gt;
#In the form at the bottom make the changes that you want to apply to all the messages checked. To set them to &amp;quot;deleted,&amp;quot; you pull down the drop-down next to &#039;&#039;&#039;Make Status&#039;&#039;&#039; and choose deleted.&lt;br /&gt;
#Once you have filled the form with all the changes you want to make, click &#039;&#039;&#039;Update.&#039;&#039;&#039;&lt;br /&gt;
You can also use Bulk Update to merge tickets (see below) or do many other maintenance tasks. Deleting is the most common.&lt;br /&gt;
&lt;br /&gt;
[[file:Bulk_Update.gif]]&lt;br /&gt;
==Updating a Ticket==&lt;br /&gt;
Once you are in a ticket you will see a header with all sorts of information you can change. &#039;&#039;&#039;Every section had things you can modify by clicking on its header.&#039;&#039;&#039;&lt;br /&gt;
So, if you want to update who owns the ticket and whether it&#039;s open/closed, you can click on &#039;&#039;&#039;The Basics&#039;&#039;&#039; and update those things from there. &#039;&#039;&#039;If you have multiple queues&#039;&#039;&#039; you can change what queue the ticket is in from The Basics section, because people often send requests to the wrong email.&lt;br /&gt;
===Statuses===&lt;br /&gt;
;Initial Phase (search &amp;lt;code&amp;gt;__initial__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket is new and hasn&#039;t yet been reviewed by department staff.&lt;br /&gt;
:;&amp;lt;code&amp;gt;triage&amp;lt;/code&amp;gt;&lt;br /&gt;
::The initial status for tickets created via email. These tickets are waiting for triage, and may be spam.&lt;br /&gt;
:;&amp;lt;code&amp;gt;new&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket has been triaged and is not spam, but has not yet been reviewed by department staff.&lt;br /&gt;
:&lt;br /&gt;
;Active Phase (search &amp;lt;code&amp;gt;__active__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket has been reviewed by a staffer at least once and is actively being worked on.&lt;br /&gt;
:;&amp;lt;code&amp;gt;review&amp;lt;/code&amp;gt;&lt;br /&gt;
::Something has happened (usually a reply) and the ticket needs the attention of a staffer.&lt;br /&gt;
:;&amp;lt;code&amp;gt;working&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket has been reviewed, but the Owner still needs to reply. This should only be set by the ticket owner, and indicates that they&#039;re working on a reply and so it doesn&#039;t need to be reviewed by anyone else.&lt;br /&gt;
:;&amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;&lt;br /&gt;
::We&#039;re waiting for the Requestor to reply. No action is needed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;timeout&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket was &amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;, but the Requestor hasn&#039;t responded for too long. Either send a reminder or set to &amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;.&lt;br /&gt;
:;&amp;lt;code&amp;gt;hold&amp;lt;/code&amp;gt;&lt;br /&gt;
::No one needs to do anything, but we don&#039;t want the ticket to be closed for some reason.&lt;br /&gt;
:&lt;br /&gt;
;Inactive Phase (search &amp;lt;code&amp;gt;__inactive__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket does not require more work and should not normally be shown. Inactive tickets can still be found via the search system.&lt;br /&gt;
:;&amp;lt;code&amp;gt;resolved&amp;lt;/code&amp;gt;&lt;br /&gt;
::The Requestor&#039;s objective has been achieved and the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;rejected&amp;lt;/code&amp;gt;&lt;br /&gt;
::We declined to do what the Requestor wanted and the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;&lt;br /&gt;
::The Requestor took too long to respond and we gave up, so the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket isn&#039;t spam, but we want it to go away and there&#039;s no reason to keep it as a permanent record. This will be used most often for automated notifications from various systems. Tickets in the &amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt; status aren&#039;t actually deleted immediately: they stick around for at least 30 days before being shredded.&lt;br /&gt;
:;&amp;lt;code&amp;gt;spam&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket is spam and should go away. Tickets marked spam will be kept for at least 30 days, then used to train the spam filter and shredded.&lt;br /&gt;
&lt;br /&gt;
==Merging Tickets==&lt;br /&gt;
Sometimes the way someone replies to a thread opens a new ticket. Sometimes people email multiple times. Sometimes you just need to merge everything together. &lt;br /&gt;
&lt;br /&gt;
If you have two or more tickets that are really all part of the same thread then they should be merged into the same ticket. Luckily, merging is really easy (a little TOO easy).&lt;br /&gt;
===Merging One Ticket===&lt;br /&gt;
#In the ticket view click on &amp;quot;Links&amp;quot;&lt;br /&gt;
#Fill out the Merge Into field the bottom&lt;br /&gt;
#Click Save Changes&lt;br /&gt;
The ticket is now merged.&lt;br /&gt;
===Merging by Bulk Update===&lt;br /&gt;
The way you merge tickets is:&lt;br /&gt;
#Determine the id number of the main ticket you want to merge into.&lt;br /&gt;
#Go to bulk update for that queue and select the other ticket(s) you want to merge&lt;br /&gt;
#Scroll to the bottom and enter the id number of the main ticket&lt;br /&gt;
#Click Update.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:RT_Merge.png]]&lt;br /&gt;
&lt;br /&gt;
You should now have the whole thread in one.&lt;br /&gt;
Notice that it warns that the process is not reversible, so don&#039;t mess it up!&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CAUTION: If you do any more bulk updating RT will continue to merge tickets until you either navigate to another page or clear out the merge field!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Forwarding a Ticket into RT ==&lt;br /&gt;
If an email went to the wrong place and you need to get it into RT you need to forward it there and update it so replies can be done correctly. Depending on the queue or the time, you may not have the ability to update it yourself, so you may have to warn the queue handlers to update the ticket for you. &lt;br /&gt;
&lt;br /&gt;
# Forward the email out of your email to the correct email&lt;br /&gt;
# Go into RT and open the ticket that was just created. It will say that you&#039;re the requestor. If the queue handler replied now it would go to you, not the original requestor&lt;br /&gt;
# In the ticket, scroll down to &amp;quot;People&amp;quot; and click the Edit icon&lt;br /&gt;
# Click the checkbox next to your name/email to remove it as a requestor&lt;br /&gt;
# Under &amp;quot;Add new watchers&amp;quot; pick one and use the drop-down to change it to &amp;quot;Requestor&amp;quot;&lt;br /&gt;
# Add the original requestor&#039;s email to the email box next to where you just changed&lt;br /&gt;
# Click Save&lt;br /&gt;
# Review the people box to ensure you did it right - your email should be gone, and the original person who emailed you should be the requestor&lt;br /&gt;
&lt;br /&gt;
==For the Admin==&lt;br /&gt;
===Create a Privileged User===&lt;br /&gt;
#Admin-&amp;gt;Users-&amp;gt;Select&lt;br /&gt;
#Put user in the go to user box.&lt;br /&gt;
#*If the user does not exist, it needs to be created. So you can create the user by sending them an email from RT letting them know they can log into RT. It&#039;s freaking magic!&lt;br /&gt;
#Open the user account&lt;br /&gt;
#Check the box to make the user a privileged user&lt;br /&gt;
#Save Changes at the bottom&lt;br /&gt;
===Add a user to a queue===&lt;br /&gt;
#Admin-&amp;gt;Queues-&amp;gt;Select&lt;br /&gt;
#Select the queue&lt;br /&gt;
#Click &amp;quot;Watchers&amp;quot;&lt;br /&gt;
#enter the user&#039;s name in the &amp;quot;Find People whose&amp;quot; box and hit Go - The user will show up in the lower right area&lt;br /&gt;
#Select &amp;quot;AdminCC&amp;quot;&lt;br /&gt;
#Click &amp;quot;Save Changes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===Merging users where the good email is on the account not connected to BACON===&lt;br /&gt;
This is a common but really, really annoying condition where RT will will not email to the BACON email because the BACON account is already linked to a different email. It is common when people change their email address, though. &lt;br /&gt;
&lt;br /&gt;
====Beta&#039;s Method====&lt;br /&gt;
I don&#039;t know if this is the best way but here&#039;s how I&#039;m handling it on an old ticket and a way that Sammich seems to believe will work. &lt;br /&gt;
&lt;br /&gt;
#Copy good and bad emails to a third location like notepad so I have them safe for this process. I like to be very clear in my notes &amp;quot;good email: (email)&amp;quot; and &amp;quot;bad email:(email)&amp;quot; along with links to each user so if I messed up I had all the information still available.&lt;br /&gt;
#On the bad account, set the email address (and possibly the username if it&#039;s the same as the email address) to something unique but bogus. I used &amp;quot;x@gmail.com&amp;quot; because the email in question was @gmail and it was temporary and easy.&lt;br /&gt;
#On the good account, set the email address to what you want it to be: the &amp;quot;good&amp;quot; email address&lt;br /&gt;
#Save&lt;br /&gt;
#On the bad account, set the email address to what the good account use to have: the &amp;quot;bad&amp;quot; email address&lt;br /&gt;
#Save&lt;br /&gt;
#Merge the &amp;quot;bad&amp;quot; user into the &amp;quot;good&amp;quot; user&lt;br /&gt;
&lt;br /&gt;
====Sammich&#039;s Method/note====&lt;br /&gt;
&amp;lt;blockquote&amp;gt;What I did is change the non-BACON-linked account with the new email to have no email, change the BACON-linked account to the correct email, and then merge the non-BACON account into the BACON account. If they&#039;re still going to use the old address you&#039;d either need to swap the addresses as you said, or create a new account for the old email and immediately merge it into their main account.&amp;lt;/blockquote&amp;gt;&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1789</id>
		<title>2024 Meeting Notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1789"/>
		<updated>2024-10-08T14:31:36Z</updated>

		<summary type="html">&lt;p&gt;Beta: /* Staff Meeting Summary - 2024-10-06 */ Link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Staff Meeting Summary 2024-06-22 ==&lt;br /&gt;
&lt;br /&gt;
=== Convention Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Announcement:&#039;&#039;&#039;&lt;br /&gt;
** We&#039;re having a convention! The contract is signed with the &#039;&#039;&#039;Reno Sparks Convention Center&#039;&#039;&#039; for a &#039;&#039;&#039;Nov 1-3&#039;&#039;&#039; convention. We have the space from Wednesday to Monday.&lt;br /&gt;
* &#039;&#039;&#039;Website and Registration:&#039;&#039;&#039;&lt;br /&gt;
** Convention dates updated on the website.&lt;br /&gt;
** Additional updates needed.&lt;br /&gt;
** General registration expects to open by the end of the weekend.&lt;br /&gt;
** Staff registration will open alongside general registration, even without the staff contract being ready.&lt;br /&gt;
** Staff contract is being worked on by Natasha.&lt;br /&gt;
* &#039;&#039;&#039;Need for Staff:&#039;&#039;&#039;&lt;br /&gt;
** Emphasis on the need for more staff.&lt;br /&gt;
** Encouragement for current staff to recruit friends.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introduction of New Staff Member:&#039;&#039;&#039;&lt;br /&gt;
** TheUltimateDragon (William) introduced as the new head of the game room.&lt;br /&gt;
** Plans to involve the local fighting game community, with 20 to 30 active members.&lt;br /&gt;
&lt;br /&gt;
=== Department Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Game Room Logistics:&#039;&#039;&#039;&lt;br /&gt;
** William plans to bring in his community for the game room.&lt;br /&gt;
** Discussion on the availability of consoles and other equipment. We may need to source consoles.&lt;br /&gt;
* &#039;&#039;&#039;Separation of Main Stage and Gaming Areas:&#039;&#039;&#039;&lt;br /&gt;
** Main stage and gaming areas will be separated at the new venue.&lt;br /&gt;
* &#039;&#039;&#039;Beta&#039;s Role Change:&#039;&#039;&#039;&lt;br /&gt;
** John has stepped down as vice chair and gaming head.&lt;br /&gt;
** Beta has stepped down as vice chair and is stepping back from some responsibilities. &lt;br /&gt;
** Beta&#039;s focus will largely be on continuous improvement and documentation to streamline processes.&lt;br /&gt;
** Tim is now a vice chair and will be more involved in ensuring tasks are completed.&lt;br /&gt;
* &#039;&#039;&#039;Recognition of Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Cupcake Doll recognized for consistent efforts in keeping things moving.&lt;br /&gt;
&lt;br /&gt;
=== Pricing and Budget ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Weekend passes likely $60.&lt;br /&gt;
** Individual day passes expected to be $30, with possible higher price for Saturday.&lt;br /&gt;
* &#039;&#039;&#039;Vendor Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Vendor table prices will increase slightly.&lt;br /&gt;
* &#039;&#039;&#039;Prize Procurement:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on handling prizes for the convention.&lt;br /&gt;
** Tighter budget than usual this year, need for smart procurement.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotion ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Urgent need to start marketing the convention.&lt;br /&gt;
** Plans to distribute business cards and possibly larger flyers or posters.&lt;br /&gt;
* &#039;&#039;&#039;RAGECON Presence:&#039;&#039;&#039;&lt;br /&gt;
** Potential for having a table at RAGECON to promote the convention.&lt;br /&gt;
** Discussion on staffing the table and badges.&lt;br /&gt;
* &#039;&#039;&#039;Community Engagement:&#039;&#039;&#039;&lt;br /&gt;
** Importance of engaging with the local community through various events.&lt;br /&gt;
&lt;br /&gt;
=== Social Media and Streaming ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Social Media Activity:&#039;&#039;&#039;&lt;br /&gt;
** Current presence on Facebook and Twitter (X).&lt;br /&gt;
** Need to boost activity on these platforms.&lt;br /&gt;
* &#039;&#039;&#039;Streaming Ideas:&#039;&#039;&#039;&lt;br /&gt;
** Streaming tournaments and other events to generate hype.&lt;br /&gt;
** Use of Twitch and YouTube for streaming and promoting the convention.&lt;br /&gt;
* &#039;&#039;&#039;Social Media Management:&#039;&#039;&#039;&lt;br /&gt;
** Fae offered to help with social media posts and engagement.&lt;br /&gt;
** Discussion on using Social Pilot for automated posts, with manual posts for Instagram.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New Venue Details:&#039;&#039;&#039;&lt;br /&gt;
** New venue is the convention center, more expensive but possibly a better fit.&lt;br /&gt;
** Concerns about lighting at the new venue and potential solutions.&lt;br /&gt;
* &#039;&#039;&#039;Security Requirements:&#039;&#039;&#039;&lt;br /&gt;
** Need to hire ESI security, details still unclear.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Communication and Collaboration:&#039;&#039;&#039;&lt;br /&gt;
** Encouragement for effective communication and collaboration.&lt;br /&gt;
** Importance of being proactive in managing tasks and responsibilities.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-07-14 ==&lt;br /&gt;
&lt;br /&gt;
=== Welcome and Introduction ===&lt;br /&gt;
&lt;br /&gt;
* The meeting was initiated to discuss updates and plans for SNAFU Con, emphasizing the importance of recruiting more staff.&lt;br /&gt;
&lt;br /&gt;
=== Website and Marketing Updates ===&lt;br /&gt;
&lt;br /&gt;
* The website is nearly ready for directing traffic, with social media updates to follow soon.&lt;br /&gt;
* Business card-sized flyers are ready, and 4x6 flyers are being prepared for distribution.&lt;br /&gt;
* Marketing efforts are expected to kick off in August. Flyers and posters will be distributed at local nerdy businesses.&lt;br /&gt;
* Posters will be available closer to the event, no later than the con book release.&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Conventions and Events ===&lt;br /&gt;
&lt;br /&gt;
* A list of upcoming conventions and events was provided to schedule possible promotional efforts:&lt;br /&gt;
** August 16-18: GalaxyCon San Jose&lt;br /&gt;
** August 17-18: Con for a Cause (formerly Aerie-Con) in Reno&lt;br /&gt;
** August 30-Sept 1: SacAnime&lt;br /&gt;
** September 7-10: Kaboom Con in Carson City&lt;br /&gt;
** October 14-17: BLFC at GSR&lt;br /&gt;
** October 26-27: YumeConUSA in San Jose&lt;br /&gt;
** November 2-3: Reno Toy Con at GSR&lt;br /&gt;
* Additional local events and new shops were suggested as potential flyer distribution points.&lt;br /&gt;
** Kobold’s Keep in Reno&lt;br /&gt;
** New shop in Sparks called &amp;quot;The Coffer&amp;quot;&lt;br /&gt;
** Warhammer store at Summit&lt;br /&gt;
* Cosplay meetups and other geek clubs were identified as good opportunities for promotion.&lt;br /&gt;
** Local libraries often have anime and gaming clubs that could be reached out to for promotion.&lt;br /&gt;
** South Reno Library, which has regular Pokémon days for kids.&lt;br /&gt;
** Cosplay for Kindness, a group that runs various events in town and was suggested for potential collaboration.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment and Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Emphasis on the prompt signing of staff contracts to avoid last year&#039;s issues.&lt;br /&gt;
* Encouragement for staff to recruit friends and acquaintances to join the team.&lt;br /&gt;
* Discussion on the contract checking process using the existing HR system. (We have to actually make phone calls again to catch stragglers.)&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Plans ===&lt;br /&gt;
&lt;br /&gt;
* The new convention layout at the Reno-Sparks Convention Center was discussed, including the need for large signs to guide attendees.&lt;br /&gt;
* We have all of C, D and E rooms.&lt;br /&gt;
* Initial maps were shared, highlighting the layout of C and D halls and the ballroom for vendors and artists.&lt;br /&gt;
* Focus on controlling badge points and managing the flow of attendees.&lt;br /&gt;
** We expect to need 5 badge controlled spots &lt;br /&gt;
&lt;br /&gt;
=== Food and Concessions ===&lt;br /&gt;
&lt;br /&gt;
* Concerns were raised about the availability of substantial food options at the venue.&lt;br /&gt;
** If you have a request for the concessions stand, send it to Tim.&lt;br /&gt;
** Coordination with Aramark for concessions and the possibility of vendors providing snacks were discussed.&lt;br /&gt;
&lt;br /&gt;
=== Merchants and Artist Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Merchant and artist contracts are in progress and will be opened soon.&lt;br /&gt;
* A first-come, first-serve approach was proposed for artist alley applications.&lt;br /&gt;
* Emphasis on adhering to city deadlines for paperwork submission.&lt;br /&gt;
** City deadline is now 30 days before con instead of the 15 day deadline we used to have.&lt;br /&gt;
&lt;br /&gt;
=== Partnering with Local Organizations ===&lt;br /&gt;
&lt;br /&gt;
* Plans to reach out to local professors, science museums, and other educational organizations for panel presentations and partnerships.&lt;br /&gt;
* Contact with the Discovery Museum for potential collaboration was initiated.&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* At least one future in-person meeting will be held at libraries to facilitate face-to-face interactions. Possibly more.&lt;br /&gt;
* Potential venues for these meetings include South Valleys Library and Sparks Library.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* Updates on social media graphics and preparations for the convention were shared.&lt;br /&gt;
* A press release will be drafted following the guidelines on the SNAFU Con wiki.&lt;br /&gt;
* Reminder to be cautious about staff burnout and to maintain a balanced workload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - In Person Meeting 2024-08-10 ==&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Meeting Issues:&#039;&#039;&#039;&lt;br /&gt;
** Attendance was taken manually due to errors in logging into the system.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introductions:&#039;&#039;&#039;&lt;br /&gt;
** Staff members introduced themselves, their roles, and their previous experience with the convention.&lt;br /&gt;
&lt;br /&gt;
=== Event Planning and Roles ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing:&#039;&#039;&#039;&lt;br /&gt;
** There are several open positions that need to be filled.&lt;br /&gt;
** Current staff are encouraged to take on multiple roles due to the shortage.&lt;br /&gt;
** Beta is stepping back but will still assist with HR, graphics, documentation, and continual improvement.&lt;br /&gt;
** The chair is Tim, who will oversee various departments and tasks.&lt;br /&gt;
** Registration and contract signing for staff will be done online, with no in-person signings allowed.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Layout:&#039;&#039;&#039;&lt;br /&gt;
** Overview of the venue layout:&lt;br /&gt;
*** Artist Alley and Vendor spaces will be located in D1-D3 ballrooms.&lt;br /&gt;
*** E1-E3 for video gaming, E9-E10 for tabletop gaming.&lt;br /&gt;
*** Main stage, panels, cosplay, and manga library also mapped out.&lt;br /&gt;
** Discussions on the potential need for more lighting in certain rooms, particularly for the Artist Alley.&lt;br /&gt;
** A walkthrough is needs to be scheduled to assess lighting and other venue specifics.&lt;br /&gt;
** Badge control points and door management will be 5 points this year due to venue layout. We may be able to use ESI for two of them.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Features ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Room:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is the new head of the gaming room and is planning a retro gaming corner.&lt;br /&gt;
** The retro gaming corner will feature classic consoles like PS2, SNES Classic, etc.&lt;br /&gt;
** A tournament is being planned, potentially requiring more PS5 consoles.&lt;br /&gt;
** Volunteers are needed to help with the gaming room.&lt;br /&gt;
** A spreadsheet may be created to track who is bringing what equipment (consoles, TVs, etc.).&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Artist Alley and Vendor Contracts:&#039;&#039;&#039;&lt;br /&gt;
** Artist Alley and Vendor space has been slightly reduced&lt;br /&gt;
** Contracts are almost ready, pending some final details.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Cosplay:&#039;&#039;&#039;&lt;br /&gt;
** The main lobby area and ballroom lobby are potential spaces for cosplay meetups.&lt;br /&gt;
** Discussion on the benefits of high visibility areas for cosplay meetups.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Initiatives:&#039;&#039;&#039;&lt;br /&gt;
** There is a strong need for increased marketing due to the new venue and the desire to attract a larger audience.&lt;br /&gt;
** Social media efforts need to ramp up, with plans to highlight artists, vendors, and panels.&lt;br /&gt;
** There is a call for everyone to contribute to marketing, especially on social media.&lt;br /&gt;
** Short science videos and other creative content ideas were discussed as potential marketing tools.&lt;br /&gt;
** Plans to advertise on local event pages, including Nevada Appeal and RGJ Events.&lt;br /&gt;
** Potential collaboration with other local events (e.g., toy fair, punk rock market) to cross-promote.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Outreach to Other Communities:&#039;&#039;&#039;&lt;br /&gt;
** UNR (University of Nevada, Reno) clubs and groups are potential targets for outreach.&lt;br /&gt;
** Suggestions to connect with local businesses like Cap&#039;n Games for retro gaming partnerships.&lt;br /&gt;
** Discussed using UNR’s radio station and event calendars for advertising.&lt;br /&gt;
&lt;br /&gt;
=== Other Discussions ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Venue Logistics:&#039;&#039;&#039;&lt;br /&gt;
** Badge-controlled areas were discussed, and it&#039;s determined that certain doors may be monitored by ESI security.&lt;br /&gt;
** Seating arrangements and areas for interactive activities (like doodle tables) were considered. We may be able to put them out in the main venue space.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Miscellaneous:&#039;&#039;&#039;&lt;br /&gt;
** Questions were raised about the availability and acquisition of CRTs (for retro gaming), with some potential leads mentioned.&lt;br /&gt;
** Mention of potential storage issues if the con were to acquire CRTs.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Next Steps:&#039;&#039;&#039;&lt;br /&gt;
** Finalization of contracts and opening up vendor applications.&lt;br /&gt;
** Continued efforts in staff recruitment and training.&lt;br /&gt;
** Preparation for the next walkthrough of the venue.&lt;br /&gt;
** Further development of marketing strategies, including social media engagement and partnerships.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Mingle Time:&#039;&#039;&#039;&lt;br /&gt;
** After the meeting, there was a designated time for staff to network and discuss roles and tasks further.&lt;br /&gt;
&lt;br /&gt;
=== Closing Remarks ===&lt;br /&gt;
&lt;br /&gt;
* The meeting concluded with an open call for any additional questions or ideas from the attendees.&lt;br /&gt;
* Those interested in specific roles or tasks were encouraged to speak with Tim or other department heads.&lt;br /&gt;
&lt;br /&gt;
The meeting wrapped up with a reminder that continued collaboration and communication will be key as the convention date approaches.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-08-30 ==&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Inventory ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Inventory Day&#039;&#039;&#039;:&lt;br /&gt;
** Scheduled for September 8 at 9:00 AM.&lt;br /&gt;
** Volunteers are needed; early arrival (8:00 AM) is encouraged, though not mandatory.&lt;br /&gt;
** Tasks: The inventory process involves pulling everything out of the storage unit, counting, and then putting it back.&lt;br /&gt;
** Inventory Sheets: There are existing inventory sheets that have been used for the past few years. These may need updating.&lt;br /&gt;
** Digital vs. Paper Inventory: Discussion on whether to digitize the inventory process using phones or continue using paper due to previous difficulties with digital attempts. Currently remaining with paper but will review. &lt;br /&gt;
** Volunteer Roles: More volunteers are needed for the logistics department to help with inventory.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Flyers and Posters:&#039;&#039;&#039;&lt;br /&gt;
** Posters have been ordered and are expected to arrive in about two weeks.&lt;br /&gt;
** &#039;&#039;&#039;Distribution:&#039;&#039;&#039; Cupcakedoll is actively distributing flyers across various locations. Others are encouraged to do the same once more flyers are available.&lt;br /&gt;
** &#039;&#039;&#039;Flier Locations:&#039;&#039;&#039; Noted that some locations, like Game Kastle, might be less receptive to flyers.&lt;br /&gt;
** &#039;&#039;&#039;Other Conventions:&#039;&#039;&#039; Suggestions to advertise at other conventions.&lt;br /&gt;
* &#039;&#039;&#039;Social Media:&#039;&#039;&#039; There is a need to increase social media activity to promote the convention further.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Department Leadership:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is leading the gaming department &lt;br /&gt;
** Support from other staff members is assured.&lt;br /&gt;
* &#039;&#039;&#039;CRT and Console Rentals:&#039;&#039;&#039;&lt;br /&gt;
** Efforts are being made to source CRT TVs for the gaming tournaments.&lt;br /&gt;
** &#039;&#039;&#039;Contacts:&#039;&#039;&#039; Attempts to contact Abe, who may have CRTs, and explore rental options at Cap and Games.&lt;br /&gt;
** &#039;&#039;&#039;Consoles:&#039;&#039;&#039; There’s a need for 20-25 consoles for a tournament, with current availability being around 12-15.&lt;br /&gt;
** &#039;&#039;&#039;Challenges:&#039;&#039;&#039; Securing enough consoles to avoid the tournament running late is a significant concern. Without enough consoles, running the tournament may not be feasible.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer Consoles:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on how to incentivize people to lend their consoles for the event.&lt;br /&gt;
** &#039;&#039;&#039;Suggestions:&#039;&#039;&#039; Offering volunteer hours as a percentage discount on badges in exchange for console loans.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Coordination ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing Needs:&#039;&#039;&#039;&lt;br /&gt;
** There’s a push to have more people sign up for staff roles, with a reminder that the convention is about two months away.&lt;br /&gt;
** &#039;&#039;&#039;Volunteer Roles:&#039;&#039;&#039; The convention still needs volunteers across various departments, including programming, registration, and general staffing roles.&lt;br /&gt;
** &#039;&#039;&#039;Benefits:&#039;&#039;&#039; Volunteers can get their badge cost refunded after completing 12 hours of work, with a prorated refund available for fewer hours.&lt;br /&gt;
** &#039;&#039;&#039;Recruitment&#039;&#039;&#039;: Staff members are encouraged to recruit friends and community members to volunteer.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer and Staff Contracts:&#039;&#039;&#039;&lt;br /&gt;
** A reminder that staff contracts need to be completed as soon as possible to finalize roles.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Concerns ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Center Walkthrough:&#039;&#039;&#039;&lt;br /&gt;
** There’s a need to schedule a walkthrough of the new convention center to address concerns, particularly regarding lighting.&lt;br /&gt;
* &#039;&#039;&#039;Main Stage Lighting:&#039;&#039;&#039;&lt;br /&gt;
** Concerns were raised about the quality of lighting on the main stage, as poor lighting affected photography during the previous year.&lt;br /&gt;
** &#039;&#039;&#039;Solutions:&#039;&#039;&#039; Potential solutions include renting or purchasing LED lights to improve the stage lighting.&lt;br /&gt;
* &#039;&#039;&#039;Layout Planning:&#039;&#039;&#039;&lt;br /&gt;
** The layout for the convention spaces needs to be finalized and submitted to the venue. A draft of the main space layout is ready, but other rooms still need to be organized.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Nervousness and Excitement:&#039;&#039;&#039;&lt;br /&gt;
** Several staff members expressed a mix of excitement and nervousness about the upcoming convention, especially given the new venue and leadership roles.&lt;br /&gt;
** &#039;&#039;&#039;Encouragement:&#039;&#039;&#039; The leadership team encouraged everyone to communicate their concerns and offered support to ensure a successful event.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-09-21 ==&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* Meeting Space Issues&lt;br /&gt;
** The original meeting room was unavailable due to backstock, so the team had to relocate to a smaller space.&lt;br /&gt;
** Ongoing technical difficulties with the audio setup and Discord transcription services.&lt;br /&gt;
* Reno-Sparks Convention Center&lt;br /&gt;
** Event dates: November 1-3, 2024, with Day Zero starting on October 31, 2024.&lt;br /&gt;
** Venue address: 4590 S Virginia St, Reno, NV 89502.&lt;br /&gt;
* CRT Monitors for Gaming&lt;br /&gt;
** A query was raised regarding obtaining CRT monitors for retro gaming, with a potential deal to borrow them for free since SNAFU Con originally provided them.&lt;br /&gt;
** William (Derp) is coordinating with Skyline to finalize the monitor logistics, and a pickup date will be determined soon.&lt;br /&gt;
* Convention Layout and Hallways&lt;br /&gt;
** The convention hallways are significantly large, providing ample space for setup, including planned conversation pods for attendees to rest.&lt;br /&gt;
** There will be cars from a display that the venue would like to keep there. One car might need to be moved, but overall, it’s not considered a major issue.&lt;br /&gt;
* Table Setup and Placement&lt;br /&gt;
** Artist Alley and vendor spaces are being optimized. There was discussion about avoiding the obstruction of key views by the pipe and drape for guest tables. Possible solutions include:&lt;br /&gt;
*** Moving guest banners to the front of the tables instead of using pipe and drape.&lt;br /&gt;
* Power and Charging Stations&lt;br /&gt;
** Discussion about including charging stations in conversation pods, but it was clarified that they would not have power access for this year.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* Gaming Console Contributions&lt;br /&gt;
** Derp is finalizing console and game contributions from volunteers. Volunteers should bring one console, 1-2 controllers, and one game per console.&lt;br /&gt;
** There’s a need to coordinate the finalization of hours worked for contributing consoles and the announcement for sign-ups.&lt;br /&gt;
* Retro Gaming Section&lt;br /&gt;
** Retro consoles such as PS3 and Xbox 360 or older will be part of the gaming section, along with unique and rare consoles to appeal to attendees.&lt;br /&gt;
* Tournament Brackets&lt;br /&gt;
** Derp is working on setting up brackets for gaming tournaments and plans to announce the event over the weekend.&lt;br /&gt;
* Magic: The Gathering RCQ Tournament&lt;br /&gt;
** Plans to host a Regional Championship Qualifier (RCQ) for Magic: The Gathering at the convention. This would be a high-level local tournament that could help draw attendees.&lt;br /&gt;
** Special tournament badges will be offered at a discounted price, combining both day passes and tournament entry fees.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotions ===&lt;br /&gt;
&lt;br /&gt;
* Posters and Discount Codes&lt;br /&gt;
** Coordinating the distribution of convention posters across venues and local colleges. Each poster will include a discount code, with CupcakeDoll managing the creation of these codes.&lt;br /&gt;
** Posters should be placed only where they’re welcome, and coordinators should avoid places where they might cause issues.&lt;br /&gt;
* Social Media and Advertising&lt;br /&gt;
** Planning to use social media ads, particularly on Facebook, to promote events like a potential trick-or-treat event during the convention. These targeted ads would aim at drawing in families and younger attendees.&lt;br /&gt;
&lt;br /&gt;
=== Contracts and Signatures ===&lt;br /&gt;
&lt;br /&gt;
* Contract Issues&lt;br /&gt;
** Some contract files lacked signature fields, creating problems for electronic signing. Staff members have submitted as much as they could without signatures.&lt;br /&gt;
** A volunteer contract is being created that should be easily signable.&lt;br /&gt;
&lt;br /&gt;
=== Special Events ===&lt;br /&gt;
&lt;br /&gt;
* Trick-or-Treating Event&lt;br /&gt;
** Discussions around hosting a trick-or-treat event during the convention, where cosplayers hand out candy to children. The event could become a big draw for families.&lt;br /&gt;
** The team is working on getting approval from Aramark.&lt;br /&gt;
* Performance and Guest Events&lt;br /&gt;
** A guest performance featuring singing is planned. Karaoke will not be held on the main stage this year.&lt;br /&gt;
** DJ performances and a dance event are scheduled, with a possibility of integrating a VR dance club portal that connects to a virtual environment. This requires network drops or alternative solutions like Ethernet connections.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Management and Staffing ===&lt;br /&gt;
&lt;br /&gt;
* Logistics and Volunteer Coordination&lt;br /&gt;
** The logistics department is understaffed due to the departure of some department heads. They’re actively recruiting volunteers to handle load-ins, load-outs, and other logistical tasks, particularly for Wednesday and Monday shifts.&lt;br /&gt;
** Efforts are being made to coordinate staff availability for key load-in and load-out days, especially the day before and after the convention.&lt;br /&gt;
* Volunteer Scheduling&lt;br /&gt;
** There is a significant need for volunteers for load-out on Monday, the hardest day to staff. Scheduling posts will be updated in the logistics channel.&lt;br /&gt;
&lt;br /&gt;
=== Video Room and Media Permissions ===&lt;br /&gt;
&lt;br /&gt;
* Issues with Video Permissions&lt;br /&gt;
** The video room coordinator is still working to secure permissions for screenings. Funimation is no longer a reliable source, but requests have been sent to companies like Media Blasters and Discotek.&lt;br /&gt;
** Public domain content may be used as a fallback if no permissions are granted in time.&lt;br /&gt;
* Coordination with Media Blasters&lt;br /&gt;
** A historical note was mentioned about obtaining permissions directly from the founder of Media Blasters using his personal contact details found in a public document.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Topics ===&lt;br /&gt;
&lt;br /&gt;
* Earplugs for Attendees&lt;br /&gt;
** A suggestion was made to provide cheap earplugs at registration if noise pollution between the main stage and vendor area becomes an issue. However, it’s not expected to be a major problem.&lt;br /&gt;
* Workshop Rooms&lt;br /&gt;
** There will be no dedicated workshop rooms, but certain breakout rooms may serve similar functions.&lt;br /&gt;
* Halloween Decorations&lt;br /&gt;
** The team discussed the timing of the convention (right after Halloween) and the difficulty in sourcing Halloween decorations during that period.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - 2024-10-06 ==&lt;br /&gt;
&lt;br /&gt;
=== General Reminders ===&lt;br /&gt;
&lt;br /&gt;
* Staff Sign-ups: Staff members were reminded to sign up for roles, particularly in areas like logistics.&lt;br /&gt;
* Panel Submissions: Urgent reminder to submit panels, with emphasis on finalizing the con schedule soon.&lt;br /&gt;
* Con Book Deadlines: Last call for submitting information (e.g., panel details, logos) for inclusion in the con book. Work on the book is happening this weekend: 10/12.&lt;br /&gt;
* Guest Announcements: Guest information has not been widely announced yet, and marketing needs to expedite this process.&lt;br /&gt;
&lt;br /&gt;
=== Classic Consoles and E-Gaming ===&lt;br /&gt;
&lt;br /&gt;
* Classic Consoles: Staff members need to sign up for this section. The more obscure the console, the better. A thread was linked for sign-ups: https://discord.com/channels/416146296097865729/1279259494236291212&lt;br /&gt;
* Equipment Status: CRT TVs for classic consoles need further confirmation, but PS5s and monitors for other gaming areas are set.&lt;br /&gt;
&lt;br /&gt;
=== Con Book and Map Creation ===&lt;br /&gt;
&lt;br /&gt;
* Map for Tables: Nuriko Windchaser requested a table map layout, which will be completed within the week.&lt;br /&gt;
* Con Book Map: The map for the con book and artist tables will be finalized soon and sent out for review.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Guest Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Guest Promotion: Marketing is behind in promoting confirmed guests, and there&#039;s a need for immediate action to make the guest lineup public.&lt;br /&gt;
* Graphics: Marketing materials are still in progress, and several guest graphics will soon be sent for approval.&lt;br /&gt;
&lt;br /&gt;
=== Cosplayers and Performers ===&lt;br /&gt;
&lt;br /&gt;
* Cosplay Coordination: Discussions are underway to involve both cosplayers and the Buccaneers for day-zero candy distribution. Tim will reach out to both. &lt;br /&gt;
&lt;br /&gt;
=== Hotel and Staff Dorms ===&lt;br /&gt;
&lt;br /&gt;
* Dorm System: Dorms are available for staff at $25 per person per night or $100 for a full room. Staff interested in this option need to contact Beta directly.&lt;br /&gt;
* Affordable Option: This dorm system is significantly cheaper than standard hotel rates, and the convention is absorbing some of the costs to make it affordable for staff.&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Volunteers ===&lt;br /&gt;
&lt;br /&gt;
* Logistics Staffing: Volunteers are needed for load-in on Wednesday and Thursday (10/30-10/31). Shelby, the new logistics head, noted they might miss Monday due to work travel but will be available for most of the weekend.&lt;br /&gt;
* Post-Con Load-Out: Additional volunteers are needed for Monday after the con (11/4) to help with loading trucks back into storage, as this day typically lacks sufficient help.&lt;br /&gt;
&lt;br /&gt;
=== Registration and Training Video ===&lt;br /&gt;
&lt;br /&gt;
* New Registration Training: A new 20-minute registration training video will cover policies and customer service procedures. All registration staff are required to watch it before working at Registration.&lt;br /&gt;
* Software Changes: Minor changes to the registration system include the removal of vaccine check requirements. Overall, the process remains similar to previous years.&lt;br /&gt;
&lt;br /&gt;
=== Philanthropy and Charity Auction ===&lt;br /&gt;
&lt;br /&gt;
* New Philanthropy Head: Elizabeth was introduced as the head of philanthropy.&lt;br /&gt;
* Charity Auction: Volunteers are needed to gather donations from vendors for the charity auction. Assistance is also required to organize items, label them, and set starting prices for the auction on Sunday.&lt;br /&gt;
&lt;br /&gt;
=== Security and Rovers ===&lt;br /&gt;
&lt;br /&gt;
* ESI Security: Additional support from ESI security will be available on Saturday, the busiest day of the con, to help with badge checks and general assistance. However, SNAFU Con staff will retain primary authority.&lt;br /&gt;
* Rovers Support: ESI security will provide extra manpower, but there was discussion about how to make them approachable for attendees who might have questions.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Panels ===&lt;br /&gt;
&lt;br /&gt;
* Panel Coverage: The programming department needs more volunteers, especially on Friday. Natasha, the former head of programming, will be available to help out.&lt;br /&gt;
* Panel Approvals: Notices are being sent to panelists regarding their submission statuses.&lt;br /&gt;
&lt;br /&gt;
=== Artist Alley and Vendor Management ===&lt;br /&gt;
&lt;br /&gt;
* Table Allocation: Nuriko Windchaser requested 52 tables for Artist Alley, which is more than originally planned. Tim confirmed there would likely be enough extra tables due to fewer club reservations.&lt;br /&gt;
* Vendor Donations for Charity Auction: Vendors will be asked for donations for the charity auction, and more volunteers are needed to assist with this effort.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Theme Decorations: Fun science-themed decorations, including interactive toys, have been purchased for the event.&lt;br /&gt;
* Tech and Equipment: Some equipment from last year needs to be replaced. An updated tech document, including room layouts, has been shared, and the wiki is up to date.&lt;br /&gt;
* Merchandise and Auction Donations: Vendors and artists are encouraged to donate items for the charity auction.&lt;br /&gt;
&lt;br /&gt;
=== Closing and Open Floor ===&lt;br /&gt;
&lt;br /&gt;
* Budget Requests: Staff were reminded to submit [https://register.snafucon.com/admin/budget_request/form budget requests] if they need additional resources or materials.&lt;br /&gt;
* Science-Themed Jokes for Con Book: The meeting wrapped up with a lighthearted discussion about creating original science-themed jokes for the con book.&lt;br /&gt;
* Open Questions: The meeting concluded with an open floor for additional questions or concerns.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1788</id>
		<title>2024 Meeting Notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1788"/>
		<updated>2024-10-08T14:29:49Z</updated>

		<summary type="html">&lt;p&gt;Beta: Add 2024-10-06 meeting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Staff Meeting Summary 2024-06-22 ==&lt;br /&gt;
&lt;br /&gt;
=== Convention Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Announcement:&#039;&#039;&#039;&lt;br /&gt;
** We&#039;re having a convention! The contract is signed with the &#039;&#039;&#039;Reno Sparks Convention Center&#039;&#039;&#039; for a &#039;&#039;&#039;Nov 1-3&#039;&#039;&#039; convention. We have the space from Wednesday to Monday.&lt;br /&gt;
* &#039;&#039;&#039;Website and Registration:&#039;&#039;&#039;&lt;br /&gt;
** Convention dates updated on the website.&lt;br /&gt;
** Additional updates needed.&lt;br /&gt;
** General registration expects to open by the end of the weekend.&lt;br /&gt;
** Staff registration will open alongside general registration, even without the staff contract being ready.&lt;br /&gt;
** Staff contract is being worked on by Natasha.&lt;br /&gt;
* &#039;&#039;&#039;Need for Staff:&#039;&#039;&#039;&lt;br /&gt;
** Emphasis on the need for more staff.&lt;br /&gt;
** Encouragement for current staff to recruit friends.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introduction of New Staff Member:&#039;&#039;&#039;&lt;br /&gt;
** TheUltimateDragon (William) introduced as the new head of the game room.&lt;br /&gt;
** Plans to involve the local fighting game community, with 20 to 30 active members.&lt;br /&gt;
&lt;br /&gt;
=== Department Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Game Room Logistics:&#039;&#039;&#039;&lt;br /&gt;
** William plans to bring in his community for the game room.&lt;br /&gt;
** Discussion on the availability of consoles and other equipment. We may need to source consoles.&lt;br /&gt;
* &#039;&#039;&#039;Separation of Main Stage and Gaming Areas:&#039;&#039;&#039;&lt;br /&gt;
** Main stage and gaming areas will be separated at the new venue.&lt;br /&gt;
* &#039;&#039;&#039;Beta&#039;s Role Change:&#039;&#039;&#039;&lt;br /&gt;
** John has stepped down as vice chair and gaming head.&lt;br /&gt;
** Beta has stepped down as vice chair and is stepping back from some responsibilities. &lt;br /&gt;
** Beta&#039;s focus will largely be on continuous improvement and documentation to streamline processes.&lt;br /&gt;
** Tim is now a vice chair and will be more involved in ensuring tasks are completed.&lt;br /&gt;
* &#039;&#039;&#039;Recognition of Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Cupcake Doll recognized for consistent efforts in keeping things moving.&lt;br /&gt;
&lt;br /&gt;
=== Pricing and Budget ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Weekend passes likely $60.&lt;br /&gt;
** Individual day passes expected to be $30, with possible higher price for Saturday.&lt;br /&gt;
* &#039;&#039;&#039;Vendor Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Vendor table prices will increase slightly.&lt;br /&gt;
* &#039;&#039;&#039;Prize Procurement:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on handling prizes for the convention.&lt;br /&gt;
** Tighter budget than usual this year, need for smart procurement.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotion ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Urgent need to start marketing the convention.&lt;br /&gt;
** Plans to distribute business cards and possibly larger flyers or posters.&lt;br /&gt;
* &#039;&#039;&#039;RAGECON Presence:&#039;&#039;&#039;&lt;br /&gt;
** Potential for having a table at RAGECON to promote the convention.&lt;br /&gt;
** Discussion on staffing the table and badges.&lt;br /&gt;
* &#039;&#039;&#039;Community Engagement:&#039;&#039;&#039;&lt;br /&gt;
** Importance of engaging with the local community through various events.&lt;br /&gt;
&lt;br /&gt;
=== Social Media and Streaming ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Social Media Activity:&#039;&#039;&#039;&lt;br /&gt;
** Current presence on Facebook and Twitter (X).&lt;br /&gt;
** Need to boost activity on these platforms.&lt;br /&gt;
* &#039;&#039;&#039;Streaming Ideas:&#039;&#039;&#039;&lt;br /&gt;
** Streaming tournaments and other events to generate hype.&lt;br /&gt;
** Use of Twitch and YouTube for streaming and promoting the convention.&lt;br /&gt;
* &#039;&#039;&#039;Social Media Management:&#039;&#039;&#039;&lt;br /&gt;
** Fae offered to help with social media posts and engagement.&lt;br /&gt;
** Discussion on using Social Pilot for automated posts, with manual posts for Instagram.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New Venue Details:&#039;&#039;&#039;&lt;br /&gt;
** New venue is the convention center, more expensive but possibly a better fit.&lt;br /&gt;
** Concerns about lighting at the new venue and potential solutions.&lt;br /&gt;
* &#039;&#039;&#039;Security Requirements:&#039;&#039;&#039;&lt;br /&gt;
** Need to hire ESI security, details still unclear.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Communication and Collaboration:&#039;&#039;&#039;&lt;br /&gt;
** Encouragement for effective communication and collaboration.&lt;br /&gt;
** Importance of being proactive in managing tasks and responsibilities.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-07-14 ==&lt;br /&gt;
&lt;br /&gt;
=== Welcome and Introduction ===&lt;br /&gt;
&lt;br /&gt;
* The meeting was initiated to discuss updates and plans for SNAFU Con, emphasizing the importance of recruiting more staff.&lt;br /&gt;
&lt;br /&gt;
=== Website and Marketing Updates ===&lt;br /&gt;
&lt;br /&gt;
* The website is nearly ready for directing traffic, with social media updates to follow soon.&lt;br /&gt;
* Business card-sized flyers are ready, and 4x6 flyers are being prepared for distribution.&lt;br /&gt;
* Marketing efforts are expected to kick off in August. Flyers and posters will be distributed at local nerdy businesses.&lt;br /&gt;
* Posters will be available closer to the event, no later than the con book release.&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Conventions and Events ===&lt;br /&gt;
&lt;br /&gt;
* A list of upcoming conventions and events was provided to schedule possible promotional efforts:&lt;br /&gt;
** August 16-18: GalaxyCon San Jose&lt;br /&gt;
** August 17-18: Con for a Cause (formerly Aerie-Con) in Reno&lt;br /&gt;
** August 30-Sept 1: SacAnime&lt;br /&gt;
** September 7-10: Kaboom Con in Carson City&lt;br /&gt;
** October 14-17: BLFC at GSR&lt;br /&gt;
** October 26-27: YumeConUSA in San Jose&lt;br /&gt;
** November 2-3: Reno Toy Con at GSR&lt;br /&gt;
* Additional local events and new shops were suggested as potential flyer distribution points.&lt;br /&gt;
** Kobold’s Keep in Reno&lt;br /&gt;
** New shop in Sparks called &amp;quot;The Coffer&amp;quot;&lt;br /&gt;
** Warhammer store at Summit&lt;br /&gt;
* Cosplay meetups and other geek clubs were identified as good opportunities for promotion.&lt;br /&gt;
** Local libraries often have anime and gaming clubs that could be reached out to for promotion.&lt;br /&gt;
** South Reno Library, which has regular Pokémon days for kids.&lt;br /&gt;
** Cosplay for Kindness, a group that runs various events in town and was suggested for potential collaboration.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment and Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Emphasis on the prompt signing of staff contracts to avoid last year&#039;s issues.&lt;br /&gt;
* Encouragement for staff to recruit friends and acquaintances to join the team.&lt;br /&gt;
* Discussion on the contract checking process using the existing HR system. (We have to actually make phone calls again to catch stragglers.)&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Plans ===&lt;br /&gt;
&lt;br /&gt;
* The new convention layout at the Reno-Sparks Convention Center was discussed, including the need for large signs to guide attendees.&lt;br /&gt;
* We have all of C, D and E rooms.&lt;br /&gt;
* Initial maps were shared, highlighting the layout of C and D halls and the ballroom for vendors and artists.&lt;br /&gt;
* Focus on controlling badge points and managing the flow of attendees.&lt;br /&gt;
** We expect to need 5 badge controlled spots &lt;br /&gt;
&lt;br /&gt;
=== Food and Concessions ===&lt;br /&gt;
&lt;br /&gt;
* Concerns were raised about the availability of substantial food options at the venue.&lt;br /&gt;
** If you have a request for the concessions stand, send it to Tim.&lt;br /&gt;
** Coordination with Aramark for concessions and the possibility of vendors providing snacks were discussed.&lt;br /&gt;
&lt;br /&gt;
=== Merchants and Artist Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Merchant and artist contracts are in progress and will be opened soon.&lt;br /&gt;
* A first-come, first-serve approach was proposed for artist alley applications.&lt;br /&gt;
* Emphasis on adhering to city deadlines for paperwork submission.&lt;br /&gt;
** City deadline is now 30 days before con instead of the 15 day deadline we used to have.&lt;br /&gt;
&lt;br /&gt;
=== Partnering with Local Organizations ===&lt;br /&gt;
&lt;br /&gt;
* Plans to reach out to local professors, science museums, and other educational organizations for panel presentations and partnerships.&lt;br /&gt;
* Contact with the Discovery Museum for potential collaboration was initiated.&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* At least one future in-person meeting will be held at libraries to facilitate face-to-face interactions. Possibly more.&lt;br /&gt;
* Potential venues for these meetings include South Valleys Library and Sparks Library.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* Updates on social media graphics and preparations for the convention were shared.&lt;br /&gt;
* A press release will be drafted following the guidelines on the SNAFU Con wiki.&lt;br /&gt;
* Reminder to be cautious about staff burnout and to maintain a balanced workload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - In Person Meeting 2024-08-10 ==&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Meeting Issues:&#039;&#039;&#039;&lt;br /&gt;
** Attendance was taken manually due to errors in logging into the system.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introductions:&#039;&#039;&#039;&lt;br /&gt;
** Staff members introduced themselves, their roles, and their previous experience with the convention.&lt;br /&gt;
&lt;br /&gt;
=== Event Planning and Roles ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing:&#039;&#039;&#039;&lt;br /&gt;
** There are several open positions that need to be filled.&lt;br /&gt;
** Current staff are encouraged to take on multiple roles due to the shortage.&lt;br /&gt;
** Beta is stepping back but will still assist with HR, graphics, documentation, and continual improvement.&lt;br /&gt;
** The chair is Tim, who will oversee various departments and tasks.&lt;br /&gt;
** Registration and contract signing for staff will be done online, with no in-person signings allowed.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Layout:&#039;&#039;&#039;&lt;br /&gt;
** Overview of the venue layout:&lt;br /&gt;
*** Artist Alley and Vendor spaces will be located in D1-D3 ballrooms.&lt;br /&gt;
*** E1-E3 for video gaming, E9-E10 for tabletop gaming.&lt;br /&gt;
*** Main stage, panels, cosplay, and manga library also mapped out.&lt;br /&gt;
** Discussions on the potential need for more lighting in certain rooms, particularly for the Artist Alley.&lt;br /&gt;
** A walkthrough is needs to be scheduled to assess lighting and other venue specifics.&lt;br /&gt;
** Badge control points and door management will be 5 points this year due to venue layout. We may be able to use ESI for two of them.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Features ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Room:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is the new head of the gaming room and is planning a retro gaming corner.&lt;br /&gt;
** The retro gaming corner will feature classic consoles like PS2, SNES Classic, etc.&lt;br /&gt;
** A tournament is being planned, potentially requiring more PS5 consoles.&lt;br /&gt;
** Volunteers are needed to help with the gaming room.&lt;br /&gt;
** A spreadsheet may be created to track who is bringing what equipment (consoles, TVs, etc.).&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Artist Alley and Vendor Contracts:&#039;&#039;&#039;&lt;br /&gt;
** Artist Alley and Vendor space has been slightly reduced&lt;br /&gt;
** Contracts are almost ready, pending some final details.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Cosplay:&#039;&#039;&#039;&lt;br /&gt;
** The main lobby area and ballroom lobby are potential spaces for cosplay meetups.&lt;br /&gt;
** Discussion on the benefits of high visibility areas for cosplay meetups.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Initiatives:&#039;&#039;&#039;&lt;br /&gt;
** There is a strong need for increased marketing due to the new venue and the desire to attract a larger audience.&lt;br /&gt;
** Social media efforts need to ramp up, with plans to highlight artists, vendors, and panels.&lt;br /&gt;
** There is a call for everyone to contribute to marketing, especially on social media.&lt;br /&gt;
** Short science videos and other creative content ideas were discussed as potential marketing tools.&lt;br /&gt;
** Plans to advertise on local event pages, including Nevada Appeal and RGJ Events.&lt;br /&gt;
** Potential collaboration with other local events (e.g., toy fair, punk rock market) to cross-promote.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Outreach to Other Communities:&#039;&#039;&#039;&lt;br /&gt;
** UNR (University of Nevada, Reno) clubs and groups are potential targets for outreach.&lt;br /&gt;
** Suggestions to connect with local businesses like Cap&#039;n Games for retro gaming partnerships.&lt;br /&gt;
** Discussed using UNR’s radio station and event calendars for advertising.&lt;br /&gt;
&lt;br /&gt;
=== Other Discussions ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Venue Logistics:&#039;&#039;&#039;&lt;br /&gt;
** Badge-controlled areas were discussed, and it&#039;s determined that certain doors may be monitored by ESI security.&lt;br /&gt;
** Seating arrangements and areas for interactive activities (like doodle tables) were considered. We may be able to put them out in the main venue space.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Miscellaneous:&#039;&#039;&#039;&lt;br /&gt;
** Questions were raised about the availability and acquisition of CRTs (for retro gaming), with some potential leads mentioned.&lt;br /&gt;
** Mention of potential storage issues if the con were to acquire CRTs.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Next Steps:&#039;&#039;&#039;&lt;br /&gt;
** Finalization of contracts and opening up vendor applications.&lt;br /&gt;
** Continued efforts in staff recruitment and training.&lt;br /&gt;
** Preparation for the next walkthrough of the venue.&lt;br /&gt;
** Further development of marketing strategies, including social media engagement and partnerships.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Mingle Time:&#039;&#039;&#039;&lt;br /&gt;
** After the meeting, there was a designated time for staff to network and discuss roles and tasks further.&lt;br /&gt;
&lt;br /&gt;
=== Closing Remarks ===&lt;br /&gt;
&lt;br /&gt;
* The meeting concluded with an open call for any additional questions or ideas from the attendees.&lt;br /&gt;
* Those interested in specific roles or tasks were encouraged to speak with Tim or other department heads.&lt;br /&gt;
&lt;br /&gt;
The meeting wrapped up with a reminder that continued collaboration and communication will be key as the convention date approaches.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-08-30 ==&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Inventory ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Inventory Day&#039;&#039;&#039;:&lt;br /&gt;
** Scheduled for September 8 at 9:00 AM.&lt;br /&gt;
** Volunteers are needed; early arrival (8:00 AM) is encouraged, though not mandatory.&lt;br /&gt;
** Tasks: The inventory process involves pulling everything out of the storage unit, counting, and then putting it back.&lt;br /&gt;
** Inventory Sheets: There are existing inventory sheets that have been used for the past few years. These may need updating.&lt;br /&gt;
** Digital vs. Paper Inventory: Discussion on whether to digitize the inventory process using phones or continue using paper due to previous difficulties with digital attempts. Currently remaining with paper but will review. &lt;br /&gt;
** Volunteer Roles: More volunteers are needed for the logistics department to help with inventory.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Flyers and Posters:&#039;&#039;&#039;&lt;br /&gt;
** Posters have been ordered and are expected to arrive in about two weeks.&lt;br /&gt;
** &#039;&#039;&#039;Distribution:&#039;&#039;&#039; Cupcakedoll is actively distributing flyers across various locations. Others are encouraged to do the same once more flyers are available.&lt;br /&gt;
** &#039;&#039;&#039;Flier Locations:&#039;&#039;&#039; Noted that some locations, like Game Kastle, might be less receptive to flyers.&lt;br /&gt;
** &#039;&#039;&#039;Other Conventions:&#039;&#039;&#039; Suggestions to advertise at other conventions.&lt;br /&gt;
* &#039;&#039;&#039;Social Media:&#039;&#039;&#039; There is a need to increase social media activity to promote the convention further.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Department Leadership:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is leading the gaming department &lt;br /&gt;
** Support from other staff members is assured.&lt;br /&gt;
* &#039;&#039;&#039;CRT and Console Rentals:&#039;&#039;&#039;&lt;br /&gt;
** Efforts are being made to source CRT TVs for the gaming tournaments.&lt;br /&gt;
** &#039;&#039;&#039;Contacts:&#039;&#039;&#039; Attempts to contact Abe, who may have CRTs, and explore rental options at Cap and Games.&lt;br /&gt;
** &#039;&#039;&#039;Consoles:&#039;&#039;&#039; There’s a need for 20-25 consoles for a tournament, with current availability being around 12-15.&lt;br /&gt;
** &#039;&#039;&#039;Challenges:&#039;&#039;&#039; Securing enough consoles to avoid the tournament running late is a significant concern. Without enough consoles, running the tournament may not be feasible.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer Consoles:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on how to incentivize people to lend their consoles for the event.&lt;br /&gt;
** &#039;&#039;&#039;Suggestions:&#039;&#039;&#039; Offering volunteer hours as a percentage discount on badges in exchange for console loans.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Coordination ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing Needs:&#039;&#039;&#039;&lt;br /&gt;
** There’s a push to have more people sign up for staff roles, with a reminder that the convention is about two months away.&lt;br /&gt;
** &#039;&#039;&#039;Volunteer Roles:&#039;&#039;&#039; The convention still needs volunteers across various departments, including programming, registration, and general staffing roles.&lt;br /&gt;
** &#039;&#039;&#039;Benefits:&#039;&#039;&#039; Volunteers can get their badge cost refunded after completing 12 hours of work, with a prorated refund available for fewer hours.&lt;br /&gt;
** &#039;&#039;&#039;Recruitment&#039;&#039;&#039;: Staff members are encouraged to recruit friends and community members to volunteer.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer and Staff Contracts:&#039;&#039;&#039;&lt;br /&gt;
** A reminder that staff contracts need to be completed as soon as possible to finalize roles.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Concerns ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Center Walkthrough:&#039;&#039;&#039;&lt;br /&gt;
** There’s a need to schedule a walkthrough of the new convention center to address concerns, particularly regarding lighting.&lt;br /&gt;
* &#039;&#039;&#039;Main Stage Lighting:&#039;&#039;&#039;&lt;br /&gt;
** Concerns were raised about the quality of lighting on the main stage, as poor lighting affected photography during the previous year.&lt;br /&gt;
** &#039;&#039;&#039;Solutions:&#039;&#039;&#039; Potential solutions include renting or purchasing LED lights to improve the stage lighting.&lt;br /&gt;
* &#039;&#039;&#039;Layout Planning:&#039;&#039;&#039;&lt;br /&gt;
** The layout for the convention spaces needs to be finalized and submitted to the venue. A draft of the main space layout is ready, but other rooms still need to be organized.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Nervousness and Excitement:&#039;&#039;&#039;&lt;br /&gt;
** Several staff members expressed a mix of excitement and nervousness about the upcoming convention, especially given the new venue and leadership roles.&lt;br /&gt;
** &#039;&#039;&#039;Encouragement:&#039;&#039;&#039; The leadership team encouraged everyone to communicate their concerns and offered support to ensure a successful event.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-09-21 ==&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* Meeting Space Issues&lt;br /&gt;
** The original meeting room was unavailable due to backstock, so the team had to relocate to a smaller space.&lt;br /&gt;
** Ongoing technical difficulties with the audio setup and Discord transcription services.&lt;br /&gt;
* Reno-Sparks Convention Center&lt;br /&gt;
** Event dates: November 1-3, 2024, with Day Zero starting on October 31, 2024.&lt;br /&gt;
** Venue address: 4590 S Virginia St, Reno, NV 89502.&lt;br /&gt;
* CRT Monitors for Gaming&lt;br /&gt;
** A query was raised regarding obtaining CRT monitors for retro gaming, with a potential deal to borrow them for free since SNAFU Con originally provided them.&lt;br /&gt;
** William (Derp) is coordinating with Skyline to finalize the monitor logistics, and a pickup date will be determined soon.&lt;br /&gt;
* Convention Layout and Hallways&lt;br /&gt;
** The convention hallways are significantly large, providing ample space for setup, including planned conversation pods for attendees to rest.&lt;br /&gt;
** There will be cars from a display that the venue would like to keep there. One car might need to be moved, but overall, it’s not considered a major issue.&lt;br /&gt;
* Table Setup and Placement&lt;br /&gt;
** Artist Alley and vendor spaces are being optimized. There was discussion about avoiding the obstruction of key views by the pipe and drape for guest tables. Possible solutions include:&lt;br /&gt;
*** Moving guest banners to the front of the tables instead of using pipe and drape.&lt;br /&gt;
* Power and Charging Stations&lt;br /&gt;
** Discussion about including charging stations in conversation pods, but it was clarified that they would not have power access for this year.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* Gaming Console Contributions&lt;br /&gt;
** Derp is finalizing console and game contributions from volunteers. Volunteers should bring one console, 1-2 controllers, and one game per console.&lt;br /&gt;
** There’s a need to coordinate the finalization of hours worked for contributing consoles and the announcement for sign-ups.&lt;br /&gt;
* Retro Gaming Section&lt;br /&gt;
** Retro consoles such as PS3 and Xbox 360 or older will be part of the gaming section, along with unique and rare consoles to appeal to attendees.&lt;br /&gt;
* Tournament Brackets&lt;br /&gt;
** Derp is working on setting up brackets for gaming tournaments and plans to announce the event over the weekend.&lt;br /&gt;
* Magic: The Gathering RCQ Tournament&lt;br /&gt;
** Plans to host a Regional Championship Qualifier (RCQ) for Magic: The Gathering at the convention. This would be a high-level local tournament that could help draw attendees.&lt;br /&gt;
** Special tournament badges will be offered at a discounted price, combining both day passes and tournament entry fees.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotions ===&lt;br /&gt;
&lt;br /&gt;
* Posters and Discount Codes&lt;br /&gt;
** Coordinating the distribution of convention posters across venues and local colleges. Each poster will include a discount code, with CupcakeDoll managing the creation of these codes.&lt;br /&gt;
** Posters should be placed only where they’re welcome, and coordinators should avoid places where they might cause issues.&lt;br /&gt;
* Social Media and Advertising&lt;br /&gt;
** Planning to use social media ads, particularly on Facebook, to promote events like a potential trick-or-treat event during the convention. These targeted ads would aim at drawing in families and younger attendees.&lt;br /&gt;
&lt;br /&gt;
=== Contracts and Signatures ===&lt;br /&gt;
&lt;br /&gt;
* Contract Issues&lt;br /&gt;
** Some contract files lacked signature fields, creating problems for electronic signing. Staff members have submitted as much as they could without signatures.&lt;br /&gt;
** A volunteer contract is being created that should be easily signable.&lt;br /&gt;
&lt;br /&gt;
=== Special Events ===&lt;br /&gt;
&lt;br /&gt;
* Trick-or-Treating Event&lt;br /&gt;
** Discussions around hosting a trick-or-treat event during the convention, where cosplayers hand out candy to children. The event could become a big draw for families.&lt;br /&gt;
** The team is working on getting approval from Aramark.&lt;br /&gt;
* Performance and Guest Events&lt;br /&gt;
** A guest performance featuring singing is planned. Karaoke will not be held on the main stage this year.&lt;br /&gt;
** DJ performances and a dance event are scheduled, with a possibility of integrating a VR dance club portal that connects to a virtual environment. This requires network drops or alternative solutions like Ethernet connections.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Management and Staffing ===&lt;br /&gt;
&lt;br /&gt;
* Logistics and Volunteer Coordination&lt;br /&gt;
** The logistics department is understaffed due to the departure of some department heads. They’re actively recruiting volunteers to handle load-ins, load-outs, and other logistical tasks, particularly for Wednesday and Monday shifts.&lt;br /&gt;
** Efforts are being made to coordinate staff availability for key load-in and load-out days, especially the day before and after the convention.&lt;br /&gt;
* Volunteer Scheduling&lt;br /&gt;
** There is a significant need for volunteers for load-out on Monday, the hardest day to staff. Scheduling posts will be updated in the logistics channel.&lt;br /&gt;
&lt;br /&gt;
=== Video Room and Media Permissions ===&lt;br /&gt;
&lt;br /&gt;
* Issues with Video Permissions&lt;br /&gt;
** The video room coordinator is still working to secure permissions for screenings. Funimation is no longer a reliable source, but requests have been sent to companies like Media Blasters and Discotek.&lt;br /&gt;
** Public domain content may be used as a fallback if no permissions are granted in time.&lt;br /&gt;
* Coordination with Media Blasters&lt;br /&gt;
** A historical note was mentioned about obtaining permissions directly from the founder of Media Blasters using his personal contact details found in a public document.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Topics ===&lt;br /&gt;
&lt;br /&gt;
* Earplugs for Attendees&lt;br /&gt;
** A suggestion was made to provide cheap earplugs at registration if noise pollution between the main stage and vendor area becomes an issue. However, it’s not expected to be a major problem.&lt;br /&gt;
* Workshop Rooms&lt;br /&gt;
** There will be no dedicated workshop rooms, but certain breakout rooms may serve similar functions.&lt;br /&gt;
* Halloween Decorations&lt;br /&gt;
** The team discussed the timing of the convention (right after Halloween) and the difficulty in sourcing Halloween decorations during that period.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - 2024-10-06 ==&lt;br /&gt;
&lt;br /&gt;
=== General Reminders ===&lt;br /&gt;
&lt;br /&gt;
* Staff Sign-ups: Staff members were reminded to sign up for roles, particularly in areas like logistics.&lt;br /&gt;
* Panel Submissions: Urgent reminder to submit panels, with emphasis on finalizing the con schedule soon.&lt;br /&gt;
* Con Book Deadlines: Last call for submitting information (e.g., panel details, logos) for inclusion in the con book. Work on the book is happening this weekend: 10/12.&lt;br /&gt;
* Guest Announcements: Guest information has not been widely announced yet, and marketing needs to expedite this process.&lt;br /&gt;
&lt;br /&gt;
=== Classic Consoles and E-Gaming ===&lt;br /&gt;
&lt;br /&gt;
* Classic Consoles: Staff members need to sign up for this section. The more obscure the console, the better. A thread was linked for sign-ups: &amp;lt;nowiki&amp;gt;https://discord.com/channels/416146296097865729/1279259494236291212&amp;lt;/nowiki&amp;gt; &lt;br /&gt;
* Equipment Status: CRT TVs for classic consoles need further confirmation, but PS5s and monitors for other gaming areas are set.&lt;br /&gt;
&lt;br /&gt;
=== Con Book and Map Creation ===&lt;br /&gt;
&lt;br /&gt;
* Map for Tables: Nuriko Windchaser requested a table map layout, which will be completed within the week.&lt;br /&gt;
* Con Book Map: The map for the con book and artist tables will be finalized soon and sent out for review.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Guest Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Guest Promotion: Marketing is behind in promoting confirmed guests, and there&#039;s a need for immediate action to make the guest lineup public.&lt;br /&gt;
* Graphics: Marketing materials are still in progress, and several guest graphics will soon be sent for approval.&lt;br /&gt;
&lt;br /&gt;
=== Cosplayers and Performers ===&lt;br /&gt;
&lt;br /&gt;
* Cosplay Coordination: Discussions are underway to involve both cosplayers and the Buccaneers for day-zero candy distribution. Tim will reach out to both. &lt;br /&gt;
&lt;br /&gt;
=== Hotel and Staff Dorms ===&lt;br /&gt;
&lt;br /&gt;
* Dorm System: Dorms are available for staff at $25 per person per night or $100 for a full room. Staff interested in this option need to contact Beta directly.&lt;br /&gt;
* Affordable Option: This dorm system is significantly cheaper than standard hotel rates, and the convention is absorbing some of the costs to make it affordable for staff.&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Volunteers ===&lt;br /&gt;
&lt;br /&gt;
* Logistics Staffing: Volunteers are needed for load-in on Wednesday and Thursday (10/30-10/31). Shelby, the new logistics head, noted they might miss Monday due to work travel but will be available for most of the weekend.&lt;br /&gt;
* Post-Con Load-Out: Additional volunteers are needed for Monday after the con (11/4) to help with loading trucks back into storage, as this day typically lacks sufficient help.&lt;br /&gt;
&lt;br /&gt;
=== Registration and Training Video ===&lt;br /&gt;
&lt;br /&gt;
* New Registration Training: A new 20-minute registration training video will cover policies and customer service procedures. All registration staff are required to watch it before working at Registration.&lt;br /&gt;
* Software Changes: Minor changes to the registration system include the removal of vaccine check requirements. Overall, the process remains similar to previous years.&lt;br /&gt;
&lt;br /&gt;
=== Philanthropy and Charity Auction ===&lt;br /&gt;
&lt;br /&gt;
* New Philanthropy Head: Elizabeth was introduced as the head of philanthropy.&lt;br /&gt;
* Charity Auction: Volunteers are needed to gather donations from vendors for the charity auction. Assistance is also required to organize items, label them, and set starting prices for the auction on Sunday.&lt;br /&gt;
&lt;br /&gt;
=== Security and Rovers ===&lt;br /&gt;
&lt;br /&gt;
* ESI Security: Additional support from ESI security will be available on Saturday, the busiest day of the con, to help with badge checks and general assistance. However, SNAFU Con staff will retain primary authority.&lt;br /&gt;
* Rovers Support: ESI security will provide extra manpower, but there was discussion about how to make them approachable for attendees who might have questions.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Panels ===&lt;br /&gt;
&lt;br /&gt;
* Panel Coverage: The programming department needs more volunteers, especially on Friday. Natasha, the former head of programming, will be available to help out.&lt;br /&gt;
* Panel Approvals: Notices are being sent to panelists regarding their submission statuses.&lt;br /&gt;
&lt;br /&gt;
=== Artist Alley and Vendor Management ===&lt;br /&gt;
&lt;br /&gt;
* Table Allocation: Nuriko Windchaser requested 52 tables for Artist Alley, which is more than originally planned. Tim confirmed there would likely be enough extra tables due to fewer club reservations.&lt;br /&gt;
* Vendor Donations for Charity Auction: Vendors will be asked for donations for the charity auction, and more volunteers are needed to assist with this effort.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Announcements ===&lt;br /&gt;
&lt;br /&gt;
* Theme Decorations: Fun science-themed decorations, including interactive toys, have been purchased for the event.&lt;br /&gt;
* Tech and Equipment: Some equipment from last year needs to be replaced. An updated tech document, including room layouts, has been shared, and the wiki is up to date.&lt;br /&gt;
* Merchandise and Auction Donations: Vendors and artists are encouraged to donate items for the charity auction.&lt;br /&gt;
&lt;br /&gt;
=== Closing and Open Floor ===&lt;br /&gt;
&lt;br /&gt;
* Budget Requests: Staff were reminded to submit [https://register.snafucon.com/admin/budget_request/form budget requests] if they need additional resources or materials.&lt;br /&gt;
* Science-Themed Jokes for Con Book: The meeting wrapped up with a lighthearted discussion about creating original science-themed jokes for the con book.&lt;br /&gt;
* Open Questions: The meeting concluded with an open floor for additional questions or concerns.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Philanthropy&amp;diff=1787</id>
		<title>Philanthropy</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Philanthropy&amp;diff=1787"/>
		<updated>2024-10-02T03:54:08Z</updated>

		<summary type="html">&lt;p&gt;Beta: add 2023 charity&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Philanthropy Team==&lt;br /&gt;
&lt;br /&gt;
The Philanthropy Team focuses on establishing partnerships with charities, fundraising, and promoting charitable causes. &lt;br /&gt;
&lt;br /&gt;
Generally SNAFU Con only has one charity per year that we promote and organize a charity auction for, however smaller charities have also done tabling and their own panels and programming to promote themselves and gather donations. &lt;br /&gt;
&lt;br /&gt;
We have been partnering with [https://www.bbbs.org/ BBBS] for the last several years, and [https://sncnn.org/ SNCNN] in 2023.&lt;br /&gt;
&lt;br /&gt;
===Roles and Responsibilities===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Charity Partnerships:&#039;&#039;&#039; They establish or maintain partnerships with charities. As needed, they identify, reach out to, and establish partnerships with charities. Generally con only has one major charity per year, and generally we stick with the same one annually unless we have a reason to change it. In general the person managing the department gets to choose the charity the convention is supporting for the year (with chair approval).&lt;br /&gt;
* &#039;&#039;&#039;Donation Promotion:&#039;&#039;&#039; They prepare and distribute info sheets to merchants at the convention, explaining the donation process. They work with social media to solicit pre-con donations or to prime people on how to donate at the convention.&lt;br /&gt;
* &#039;&#039;&#039;Donation Management:&#039;&#039;&#039; They solicit, organize, label, and securely store donations from convention merchants at the convention.&lt;br /&gt;
* &#039;&#039;&#039;Charity Representative Coordination:&#039;&#039;&#039; They ensure the timely arrival and registration of charity representatives.&lt;br /&gt;
* &#039;&#039;&#039;Financial Management:&#039;&#039;&#039; They handle monetary donations, including obtaining change and a cash box for the charity auction. However, we generally try to get the charity to do the money handling as much as possible as we do not want to be responsible for any of the donation money if avoidable.&lt;br /&gt;
&lt;br /&gt;
===Charity Auction===&lt;br /&gt;
&lt;br /&gt;
The Philanthropy Team&#039;s main responsibilities is organizing the Charity Auction.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Preparation:&#039;&#039;&#039; Before the auction, the team solicits donations from merchants, ensuring each item is correctly labeled with information about the donor and a potential starting bid.&lt;br /&gt;
* &#039;&#039;&#039;Storage:&#039;&#039;&#039; Donations are initially placed in a monitored donation bin close to the merchant area. As the auction approaches, items are moved to a secure location near the main stage, where the auction will take place.&lt;br /&gt;
* &#039;&#039;&#039;Auction Management:&#039;&#039;&#039; They oversee the auction proceedings, handle the cash box, and ensure there&#039;s change available for transactions.&lt;br /&gt;
* &#039;&#039;&#039;Post-Auction:&#039;&#039;&#039; All money from the auction is handed directly to the charity at the convention itself. The team keeps track of the total amount raised for announcement at the closing ceremonies.&lt;br /&gt;
&lt;br /&gt;
===Challenges and Solutions===&lt;br /&gt;
&lt;br /&gt;
The team faces several challenges, such as unresponsive charities, time constraints, limited availability, obtaining high-quality logos, and managing last-minute donations. To overcome these, they:&lt;br /&gt;
&lt;br /&gt;
* Establish early contact with charities.&lt;br /&gt;
* Prepare promotional materials in advance and adjust them based on feedback.&lt;br /&gt;
* Utilize the graphics team to recreate logos in a high-quality format using Illustrator when the one provided is too small.&lt;br /&gt;
* Coordinate with registration staff for badges for charity representatives, and for change for the charity auction.&lt;br /&gt;
* Coordinate with relevant staff for the secure storage and transport of donations.&lt;br /&gt;
&lt;br /&gt;
===Continuous Improvement===&lt;br /&gt;
&lt;br /&gt;
Following the convention, the Philanthropy Team solicits feedback from the charity to improve the process for future events. They also document all processes and procedures to facilitate knowledge transfer and future reference.&lt;br /&gt;
&lt;br /&gt;
==Procedure==&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Pre-Convention Preparation:&#039;&#039;&#039; ===&lt;br /&gt;
*&#039;&#039;&#039;Contact Charity:&#039;&#039;&#039; Reach out to the annual charity and confirm their participation. &lt;br /&gt;
**Make sure to use [[RT]] for all communications unless a phone call is required. If calling, provide a summary of the discussion in Discord.&lt;br /&gt;
**Make sure to give them information on when the charity auction is, how long it is, what we expect, etc., and request someone from their organization attend to receive donations&lt;br /&gt;
**Get a list of all the names and birth dates of people attending and pass it on to Registration. Follow up with Registration to ensure all members receive badges.&lt;br /&gt;
**Make sure that we have received up-to-date high-res logos for the con book. Vector format is preferred, but we will take what we can get. If logo is not high-res, Graphics will recreate a high res version as best they can for the con book.&lt;br /&gt;
*&#039;&#039;&#039;Prepare Information Sheet:&#039;&#039;&#039; Update the info sheet outlining the donation process for merchants for distribution at the convention.&lt;br /&gt;
*&#039;&#039;&#039;Solicit Donations:&#039;&#039;&#039; Work with the social media team to solicit pre-con donations and inform attendees about how to donate at the convention.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;At the Convention Before the Auction:&#039;&#039;&#039; ===&lt;br /&gt;
*&#039;&#039;&#039;Distribute Information Sheet:&#039;&#039;&#039; Work with the merchant heads to get the info sheet out on checkin, or go to each table to talk to every vendor and artist regarding donations and distribute sheet then.&lt;br /&gt;
*&#039;&#039;&#039;Set Up Donation Management:&#039;&#039;&#039; Set up a monitored donation bin in Ops, since it is close to the merchant area, to gather and store donations. Each donation must be labeled with the donor&#039;s information and a potential starting bid. If the merchant did not label it appropriately, you will need to label it.&lt;br /&gt;
*&#039;&#039;&#039;Charity Representative Coordination:&#039;&#039;&#039; Ensure the charity representative&#039;s timely arrival and assist them with their registration. Have Registration prepare a temporary badge if needed.&lt;br /&gt;
*&#039;&#039;&#039;Relocate Donations:&#039;&#039;&#039; As the auction approaches, transfer the donations to a secure location near the main stage.&lt;br /&gt;
*&#039;&#039;&#039;Financial Preparation:&#039;&#039;&#039; Obtain &#039;&#039;&#039;change&#039;&#039;&#039;, a &#039;&#039;&#039;receipt book&#039;&#039;&#039;, and a &#039;&#039;&#039;cash box&#039;&#039;&#039; from the registration team for use at the charity auction. Note the amount of change received, you must return that exact amount back after the auction!&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Charity Auction:&#039;&#039;&#039; ===&lt;br /&gt;
*&#039;&#039;&#039;Manage the Auction:&#039;&#039;&#039; Oversee the auction, ensuring all proceedings run smoothly. The main stage team will handle the show. You will be needed for organizing and handling the items before and after they are on stage.&lt;br /&gt;
*&#039;&#039;&#039;Handle Finances:&#039;&#039;&#039; Use the cash box to manage cash transactions. Track all sales in a receipt book. Date the sales receipts, at least with year (eg. &amp;quot;2023&amp;quot;) so we can keep the paperwork straight&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Post-Auction:&#039;&#039;&#039; ===&lt;br /&gt;
*&#039;&#039;&#039;Charity Handoff:&#039;&#039;&#039; Immediately after the auction, hand over all money raised to the charity representative.&lt;br /&gt;
*&#039;&#039;&#039;Return Cashbox:&#039;&#039;&#039; Return the cash box with the same amount of money received for change to registration. If needed, registration can break large bills.&lt;br /&gt;
*&#039;&#039;&#039;Report Amount Raised:&#039;&#039;&#039; Put the amount raised into the Philanthropy chat channel. Provide the amount to the main stage team for announcement at Closing Ceremonies.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Post-Convention Follow-Up:&#039;&#039;&#039; ===&lt;br /&gt;
*&#039;&#039;&#039;Solicit Feedback:&#039;&#039;&#039; Reach out to the charity to &#039;&#039;&#039;thank them&#039;&#039;&#039; for their participation and for &#039;&#039;&#039;feedback&#039;&#039;&#039; to improve future events.&lt;br /&gt;
*&#039;&#039;&#039;Documentation:&#039;&#039;&#039; Document all processes and procedures for future reference and knowledge transfer.&lt;br /&gt;
&lt;br /&gt;
Remember, challenges may arise such as unresponsive charities, time constraints, or last-minute donations. Always be prepared to adapt and overcome these challenges, and don&#039;t hesitate to ask for assistance or coordination from other teams.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1783</id>
		<title>2024 Meeting Notes</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=2024_Meeting_Notes&amp;diff=1783"/>
		<updated>2024-09-30T01:37:31Z</updated>

		<summary type="html">&lt;p&gt;Beta: add 2024-09-21 meeting notes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Staff Meeting Summary 2024-06-22 ==&lt;br /&gt;
&lt;br /&gt;
=== Convention Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Announcement:&#039;&#039;&#039;&lt;br /&gt;
** We&#039;re having a convention! The contract is signed with the &#039;&#039;&#039;Reno Sparks Convention Center&#039;&#039;&#039; for a &#039;&#039;&#039;Nov 1-3&#039;&#039;&#039; convention. We have the space from Wednesday to Monday.&lt;br /&gt;
* &#039;&#039;&#039;Website and Registration:&#039;&#039;&#039;&lt;br /&gt;
** Convention dates updated on the website.&lt;br /&gt;
** Additional updates needed.&lt;br /&gt;
** General registration expects to open by the end of the weekend.&lt;br /&gt;
** Staff registration will open alongside general registration, even without the staff contract being ready.&lt;br /&gt;
** Staff contract is being worked on by Natasha.&lt;br /&gt;
* &#039;&#039;&#039;Need for Staff:&#039;&#039;&#039;&lt;br /&gt;
** Emphasis on the need for more staff.&lt;br /&gt;
** Encouragement for current staff to recruit friends.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introduction of New Staff Member:&#039;&#039;&#039;&lt;br /&gt;
** TheUltimateDragon (William) introduced as the new head of the game room.&lt;br /&gt;
** Plans to involve the local fighting game community, with 20 to 30 active members.&lt;br /&gt;
&lt;br /&gt;
=== Department Updates ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Game Room Logistics:&#039;&#039;&#039;&lt;br /&gt;
** William plans to bring in his community for the game room.&lt;br /&gt;
** Discussion on the availability of consoles and other equipment. We may need to source consoles.&lt;br /&gt;
* &#039;&#039;&#039;Separation of Main Stage and Gaming Areas:&#039;&#039;&#039;&lt;br /&gt;
** Main stage and gaming areas will be separated at the new venue.&lt;br /&gt;
* &#039;&#039;&#039;Beta&#039;s Role Change:&#039;&#039;&#039;&lt;br /&gt;
** John has stepped down as vice chair and gaming head.&lt;br /&gt;
** Beta has stepped down as vice chair and is stepping back from some responsibilities. &lt;br /&gt;
** Beta&#039;s focus will largely be on continuous improvement and documentation to streamline processes.&lt;br /&gt;
** Tim is now a vice chair and will be more involved in ensuring tasks are completed.&lt;br /&gt;
* &#039;&#039;&#039;Recognition of Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Cupcake Doll recognized for consistent efforts in keeping things moving.&lt;br /&gt;
&lt;br /&gt;
=== Pricing and Budget ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Weekend passes likely $60.&lt;br /&gt;
** Individual day passes expected to be $30, with possible higher price for Saturday.&lt;br /&gt;
* &#039;&#039;&#039;Vendor Pricing:&#039;&#039;&#039;&lt;br /&gt;
** Vendor table prices will increase slightly.&lt;br /&gt;
* &#039;&#039;&#039;Prize Procurement:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on handling prizes for the convention.&lt;br /&gt;
** Tighter budget than usual this year, need for smart procurement.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotion ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Efforts:&#039;&#039;&#039;&lt;br /&gt;
** Urgent need to start marketing the convention.&lt;br /&gt;
** Plans to distribute business cards and possibly larger flyers or posters.&lt;br /&gt;
* &#039;&#039;&#039;RAGECON Presence:&#039;&#039;&#039;&lt;br /&gt;
** Potential for having a table at RAGECON to promote the convention.&lt;br /&gt;
** Discussion on staffing the table and badges.&lt;br /&gt;
* &#039;&#039;&#039;Community Engagement:&#039;&#039;&#039;&lt;br /&gt;
** Importance of engaging with the local community through various events.&lt;br /&gt;
&lt;br /&gt;
=== Social Media and Streaming ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Social Media Activity:&#039;&#039;&#039;&lt;br /&gt;
** Current presence on Facebook and Twitter (X).&lt;br /&gt;
** Need to boost activity on these platforms.&lt;br /&gt;
* &#039;&#039;&#039;Streaming Ideas:&#039;&#039;&#039;&lt;br /&gt;
** Streaming tournaments and other events to generate hype.&lt;br /&gt;
** Use of Twitch and YouTube for streaming and promoting the convention.&lt;br /&gt;
* &#039;&#039;&#039;Social Media Management:&#039;&#039;&#039;&lt;br /&gt;
** Fae offered to help with social media posts and engagement.&lt;br /&gt;
** Discussion on using Social Pilot for automated posts, with manual posts for Instagram.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;New Venue Details:&#039;&#039;&#039;&lt;br /&gt;
** New venue is the convention center, more expensive but possibly a better fit.&lt;br /&gt;
** Concerns about lighting at the new venue and potential solutions.&lt;br /&gt;
* &#039;&#039;&#039;Security Requirements:&#039;&#039;&#039;&lt;br /&gt;
** Need to hire ESI security, details still unclear.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Communication and Collaboration:&#039;&#039;&#039;&lt;br /&gt;
** Encouragement for effective communication and collaboration.&lt;br /&gt;
** Importance of being proactive in managing tasks and responsibilities.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-07-14 ==&lt;br /&gt;
&lt;br /&gt;
=== Welcome and Introduction ===&lt;br /&gt;
&lt;br /&gt;
* The meeting was initiated to discuss updates and plans for SNAFU Con, emphasizing the importance of recruiting more staff.&lt;br /&gt;
&lt;br /&gt;
=== Website and Marketing Updates ===&lt;br /&gt;
&lt;br /&gt;
* The website is nearly ready for directing traffic, with social media updates to follow soon.&lt;br /&gt;
* Business card-sized flyers are ready, and 4x6 flyers are being prepared for distribution.&lt;br /&gt;
* Marketing efforts are expected to kick off in August. Flyers and posters will be distributed at local nerdy businesses.&lt;br /&gt;
* Posters will be available closer to the event, no later than the con book release.&lt;br /&gt;
&lt;br /&gt;
=== Upcoming Conventions and Events ===&lt;br /&gt;
&lt;br /&gt;
* A list of upcoming conventions and events was provided to schedule possible promotional efforts:&lt;br /&gt;
** August 16-18: GalaxyCon San Jose&lt;br /&gt;
** August 17-18: Con for a Cause (formerly Aerie-Con) in Reno&lt;br /&gt;
** August 30-Sept 1: SacAnime&lt;br /&gt;
** September 7-10: Kaboom Con in Carson City&lt;br /&gt;
** October 14-17: BLFC at GSR&lt;br /&gt;
** October 26-27: YumeConUSA in San Jose&lt;br /&gt;
** November 2-3: Reno Toy Con at GSR&lt;br /&gt;
* Additional local events and new shops were suggested as potential flyer distribution points.&lt;br /&gt;
** Kobold’s Keep in Reno&lt;br /&gt;
** New shop in Sparks called &amp;quot;The Coffer&amp;quot;&lt;br /&gt;
** Warhammer store at Summit&lt;br /&gt;
* Cosplay meetups and other geek clubs were identified as good opportunities for promotion.&lt;br /&gt;
** Local libraries often have anime and gaming clubs that could be reached out to for promotion.&lt;br /&gt;
** South Reno Library, which has regular Pokémon days for kids.&lt;br /&gt;
** Cosplay for Kindness, a group that runs various events in town and was suggested for potential collaboration.&lt;br /&gt;
&lt;br /&gt;
=== Staff Recruitment and Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Emphasis on the prompt signing of staff contracts to avoid last year&#039;s issues.&lt;br /&gt;
* Encouragement for staff to recruit friends and acquaintances to join the team.&lt;br /&gt;
* Discussion on the contract checking process using the existing HR system. (We have to actually make phone calls again to catch stragglers.)&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Plans ===&lt;br /&gt;
&lt;br /&gt;
* The new convention layout at the Reno-Sparks Convention Center was discussed, including the need for large signs to guide attendees.&lt;br /&gt;
* We have all of C, D and E rooms.&lt;br /&gt;
* Initial maps were shared, highlighting the layout of C and D halls and the ballroom for vendors and artists.&lt;br /&gt;
* Focus on controlling badge points and managing the flow of attendees.&lt;br /&gt;
** We expect to need 5 badge controlled spots &lt;br /&gt;
&lt;br /&gt;
=== Food and Concessions ===&lt;br /&gt;
&lt;br /&gt;
* Concerns were raised about the availability of substantial food options at the venue.&lt;br /&gt;
** If you have a request for the concessions stand, send it to Tim.&lt;br /&gt;
** Coordination with Aramark for concessions and the possibility of vendors providing snacks were discussed.&lt;br /&gt;
&lt;br /&gt;
=== Merchants and Artist Contracts ===&lt;br /&gt;
&lt;br /&gt;
* Merchant and artist contracts are in progress and will be opened soon.&lt;br /&gt;
* A first-come, first-serve approach was proposed for artist alley applications.&lt;br /&gt;
* Emphasis on adhering to city deadlines for paperwork submission.&lt;br /&gt;
** City deadline is now 30 days before con instead of the 15 day deadline we used to have.&lt;br /&gt;
&lt;br /&gt;
=== Partnering with Local Organizations ===&lt;br /&gt;
&lt;br /&gt;
* Plans to reach out to local professors, science museums, and other educational organizations for panel presentations and partnerships.&lt;br /&gt;
* Contact with the Discovery Museum for potential collaboration was initiated.&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* At least one future in-person meeting will be held at libraries to facilitate face-to-face interactions. Possibly more.&lt;br /&gt;
* Potential venues for these meetings include South Valleys Library and Sparks Library.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* Updates on social media graphics and preparations for the convention were shared.&lt;br /&gt;
* A press release will be drafted following the guidelines on the SNAFU Con wiki.&lt;br /&gt;
* Reminder to be cautious about staff burnout and to maintain a balanced workload.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary - In Person Meeting 2024-08-10 ==&lt;br /&gt;
&lt;br /&gt;
=== General Meeting Logistics ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Meeting Issues:&#039;&#039;&#039;&lt;br /&gt;
** Attendance was taken manually due to errors in logging into the system.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Introductions:&#039;&#039;&#039;&lt;br /&gt;
** Staff members introduced themselves, their roles, and their previous experience with the convention.&lt;br /&gt;
&lt;br /&gt;
=== Event Planning and Roles ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing:&#039;&#039;&#039;&lt;br /&gt;
** There are several open positions that need to be filled.&lt;br /&gt;
** Current staff are encouraged to take on multiple roles due to the shortage.&lt;br /&gt;
** Beta is stepping back but will still assist with HR, graphics, documentation, and continual improvement.&lt;br /&gt;
** The chair is Tim, who will oversee various departments and tasks.&lt;br /&gt;
** Registration and contract signing for staff will be done online, with no in-person signings allowed.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Layout:&#039;&#039;&#039;&lt;br /&gt;
** Overview of the venue layout:&lt;br /&gt;
*** Artist Alley and Vendor spaces will be located in D1-D3 ballrooms.&lt;br /&gt;
*** E1-E3 for video gaming, E9-E10 for tabletop gaming.&lt;br /&gt;
*** Main stage, panels, cosplay, and manga library also mapped out.&lt;br /&gt;
** Discussions on the potential need for more lighting in certain rooms, particularly for the Artist Alley.&lt;br /&gt;
** A walkthrough is needs to be scheduled to assess lighting and other venue specifics.&lt;br /&gt;
** Badge control points and door management will be 5 points this year due to venue layout. We may be able to use ESI for two of them.&lt;br /&gt;
&lt;br /&gt;
=== Programming and Features ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Room:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is the new head of the gaming room and is planning a retro gaming corner.&lt;br /&gt;
** The retro gaming corner will feature classic consoles like PS2, SNES Classic, etc.&lt;br /&gt;
** A tournament is being planned, potentially requiring more PS5 consoles.&lt;br /&gt;
** Volunteers are needed to help with the gaming room.&lt;br /&gt;
** A spreadsheet may be created to track who is bringing what equipment (consoles, TVs, etc.).&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Artist Alley and Vendor Contracts:&#039;&#039;&#039;&lt;br /&gt;
** Artist Alley and Vendor space has been slightly reduced&lt;br /&gt;
** Contracts are almost ready, pending some final details.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Cosplay:&#039;&#039;&#039;&lt;br /&gt;
** The main lobby area and ballroom lobby are potential spaces for cosplay meetups.&lt;br /&gt;
** Discussion on the benefits of high visibility areas for cosplay meetups.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Marketing Initiatives:&#039;&#039;&#039;&lt;br /&gt;
** There is a strong need for increased marketing due to the new venue and the desire to attract a larger audience.&lt;br /&gt;
** Social media efforts need to ramp up, with plans to highlight artists, vendors, and panels.&lt;br /&gt;
** There is a call for everyone to contribute to marketing, especially on social media.&lt;br /&gt;
** Short science videos and other creative content ideas were discussed as potential marketing tools.&lt;br /&gt;
** Plans to advertise on local event pages, including Nevada Appeal and RGJ Events.&lt;br /&gt;
** Potential collaboration with other local events (e.g., toy fair, punk rock market) to cross-promote.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Outreach to Other Communities:&#039;&#039;&#039;&lt;br /&gt;
** UNR (University of Nevada, Reno) clubs and groups are potential targets for outreach.&lt;br /&gt;
** Suggestions to connect with local businesses like Cap&#039;n Games for retro gaming partnerships.&lt;br /&gt;
** Discussed using UNR’s radio station and event calendars for advertising.&lt;br /&gt;
&lt;br /&gt;
=== Other Discussions ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Venue Logistics:&#039;&#039;&#039;&lt;br /&gt;
** Badge-controlled areas were discussed, and it&#039;s determined that certain doors may be monitored by ESI security.&lt;br /&gt;
** Seating arrangements and areas for interactive activities (like doodle tables) were considered. We may be able to put them out in the main venue space.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Miscellaneous:&#039;&#039;&#039;&lt;br /&gt;
** Questions were raised about the availability and acquisition of CRTs (for retro gaming), with some potential leads mentioned.&lt;br /&gt;
** Mention of potential storage issues if the con were to acquire CRTs.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Next Steps:&#039;&#039;&#039;&lt;br /&gt;
** Finalization of contracts and opening up vendor applications.&lt;br /&gt;
** Continued efforts in staff recruitment and training.&lt;br /&gt;
** Preparation for the next walkthrough of the venue.&lt;br /&gt;
** Further development of marketing strategies, including social media engagement and partnerships.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Mingle Time:&#039;&#039;&#039;&lt;br /&gt;
** After the meeting, there was a designated time for staff to network and discuss roles and tasks further.&lt;br /&gt;
&lt;br /&gt;
=== Closing Remarks ===&lt;br /&gt;
&lt;br /&gt;
* The meeting concluded with an open call for any additional questions or ideas from the attendees.&lt;br /&gt;
* Those interested in specific roles or tasks were encouraged to speak with Tim or other department heads.&lt;br /&gt;
&lt;br /&gt;
The meeting wrapped up with a reminder that continued collaboration and communication will be key as the convention date approaches.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-08-30 ==&lt;br /&gt;
&lt;br /&gt;
=== Logistics and Inventory ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Inventory Day&#039;&#039;&#039;:&lt;br /&gt;
** Scheduled for September 8 at 9:00 AM.&lt;br /&gt;
** Volunteers are needed; early arrival (8:00 AM) is encouraged, though not mandatory.&lt;br /&gt;
** Tasks: The inventory process involves pulling everything out of the storage unit, counting, and then putting it back.&lt;br /&gt;
** Inventory Sheets: There are existing inventory sheets that have been used for the past few years. These may need updating.&lt;br /&gt;
** Digital vs. Paper Inventory: Discussion on whether to digitize the inventory process using phones or continue using paper due to previous difficulties with digital attempts. Currently remaining with paper but will review. &lt;br /&gt;
** Volunteer Roles: More volunteers are needed for the logistics department to help with inventory.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Outreach ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Flyers and Posters:&#039;&#039;&#039;&lt;br /&gt;
** Posters have been ordered and are expected to arrive in about two weeks.&lt;br /&gt;
** &#039;&#039;&#039;Distribution:&#039;&#039;&#039; Cupcakedoll is actively distributing flyers across various locations. Others are encouraged to do the same once more flyers are available.&lt;br /&gt;
** &#039;&#039;&#039;Flier Locations:&#039;&#039;&#039; Noted that some locations, like Game Kastle, might be less receptive to flyers.&lt;br /&gt;
** &#039;&#039;&#039;Other Conventions:&#039;&#039;&#039; Suggestions to advertise at other conventions.&lt;br /&gt;
* &#039;&#039;&#039;Social Media:&#039;&#039;&#039; There is a need to increase social media activity to promote the convention further.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Gaming Department Leadership:&#039;&#039;&#039;&lt;br /&gt;
** William (Derp) is leading the gaming department &lt;br /&gt;
** Support from other staff members is assured.&lt;br /&gt;
* &#039;&#039;&#039;CRT and Console Rentals:&#039;&#039;&#039;&lt;br /&gt;
** Efforts are being made to source CRT TVs for the gaming tournaments.&lt;br /&gt;
** &#039;&#039;&#039;Contacts:&#039;&#039;&#039; Attempts to contact Abe, who may have CRTs, and explore rental options at Cap and Games.&lt;br /&gt;
** &#039;&#039;&#039;Consoles:&#039;&#039;&#039; There’s a need for 20-25 consoles for a tournament, with current availability being around 12-15.&lt;br /&gt;
** &#039;&#039;&#039;Challenges:&#039;&#039;&#039; Securing enough consoles to avoid the tournament running late is a significant concern. Without enough consoles, running the tournament may not be feasible.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer Consoles:&#039;&#039;&#039;&lt;br /&gt;
** Discussion on how to incentivize people to lend their consoles for the event.&lt;br /&gt;
** &#039;&#039;&#039;Suggestions:&#039;&#039;&#039; Offering volunteer hours as a percentage discount on badges in exchange for console loans.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Coordination ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Staffing Needs:&#039;&#039;&#039;&lt;br /&gt;
** There’s a push to have more people sign up for staff roles, with a reminder that the convention is about two months away.&lt;br /&gt;
** &#039;&#039;&#039;Volunteer Roles:&#039;&#039;&#039; The convention still needs volunteers across various departments, including programming, registration, and general staffing roles.&lt;br /&gt;
** &#039;&#039;&#039;Benefits:&#039;&#039;&#039; Volunteers can get their badge cost refunded after completing 12 hours of work, with a prorated refund available for fewer hours.&lt;br /&gt;
** &#039;&#039;&#039;Recruitment&#039;&#039;&#039;: Staff members are encouraged to recruit friends and community members to volunteer.&lt;br /&gt;
* &#039;&#039;&#039;Volunteer and Staff Contracts:&#039;&#039;&#039;&lt;br /&gt;
** A reminder that staff contracts need to be completed as soon as possible to finalize roles.&lt;br /&gt;
&lt;br /&gt;
=== Venue and Layout Concerns ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Convention Center Walkthrough:&#039;&#039;&#039;&lt;br /&gt;
** There’s a need to schedule a walkthrough of the new convention center to address concerns, particularly regarding lighting.&lt;br /&gt;
* &#039;&#039;&#039;Main Stage Lighting:&#039;&#039;&#039;&lt;br /&gt;
** Concerns were raised about the quality of lighting on the main stage, as poor lighting affected photography during the previous year.&lt;br /&gt;
** &#039;&#039;&#039;Solutions:&#039;&#039;&#039; Potential solutions include renting or purchasing LED lights to improve the stage lighting.&lt;br /&gt;
* &#039;&#039;&#039;Layout Planning:&#039;&#039;&#039;&lt;br /&gt;
** The layout for the convention spaces needs to be finalized and submitted to the venue. A draft of the main space layout is ready, but other rooms still need to be organized.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Nervousness and Excitement:&#039;&#039;&#039;&lt;br /&gt;
** Several staff members expressed a mix of excitement and nervousness about the upcoming convention, especially given the new venue and leadership roles.&lt;br /&gt;
** &#039;&#039;&#039;Encouragement:&#039;&#039;&#039; The leadership team encouraged everyone to communicate their concerns and offered support to ensure a successful event.&lt;br /&gt;
&lt;br /&gt;
== Staff Meeting Summary 2024-09-21 ==&lt;br /&gt;
&lt;br /&gt;
=== Venue and Logistics ===&lt;br /&gt;
&lt;br /&gt;
* Meeting Space Issues&lt;br /&gt;
** The original meeting room was unavailable due to backstock, so the team had to relocate to a smaller space.&lt;br /&gt;
** Ongoing technical difficulties with the audio setup and Discord transcription services.&lt;br /&gt;
* Reno-Sparks Convention Center&lt;br /&gt;
** Event dates: November 1-3, 2024, with Day Zero starting on October 31, 2024.&lt;br /&gt;
** Venue address: 4590 S Virginia St, Reno, NV 89502.&lt;br /&gt;
* CRT Monitors for Gaming&lt;br /&gt;
** A query was raised regarding obtaining CRT monitors for retro gaming, with a potential deal to borrow them for free since SNAFU Con originally provided them.&lt;br /&gt;
** William (Derp) is coordinating with Skyline to finalize the monitor logistics, and a pickup date will be determined soon.&lt;br /&gt;
* Convention Layout and Hallways&lt;br /&gt;
** The convention hallways are significantly large, providing ample space for setup, including planned conversation pods for attendees to rest.&lt;br /&gt;
** There will be cars from a display that the venue would like to keep there. One car might need to be moved, but overall, it’s not considered a major issue.&lt;br /&gt;
* Table Setup and Placement&lt;br /&gt;
** Artist Alley and vendor spaces are being optimized. There was discussion about avoiding the obstruction of key views by the pipe and drape for guest tables. Possible solutions include:&lt;br /&gt;
*** Moving guest banners to the front of the tables instead of using pipe and drape.&lt;br /&gt;
* Power and Charging Stations&lt;br /&gt;
** Discussion about including charging stations in conversation pods, but it was clarified that they would not have power access for this year.&lt;br /&gt;
&lt;br /&gt;
=== Gaming and Tournaments ===&lt;br /&gt;
&lt;br /&gt;
* Gaming Console Contributions&lt;br /&gt;
** Derp is finalizing console and game contributions from volunteers. Volunteers should bring one console, 1-2 controllers, and one game per console.&lt;br /&gt;
** There’s a need to coordinate the finalization of hours worked for contributing consoles and the announcement for sign-ups.&lt;br /&gt;
* Retro Gaming Section&lt;br /&gt;
** Retro consoles such as PS3 and Xbox 360 or older will be part of the gaming section, along with unique and rare consoles to appeal to attendees.&lt;br /&gt;
* Tournament Brackets&lt;br /&gt;
** Derp is working on setting up brackets for gaming tournaments and plans to announce the event over the weekend.&lt;br /&gt;
* Magic: The Gathering RCQ Tournament&lt;br /&gt;
** Plans to host a Regional Championship Qualifier (RCQ) for Magic: The Gathering at the convention. This would be a high-level local tournament that could help draw attendees.&lt;br /&gt;
** Special tournament badges will be offered at a discounted price, combining both day passes and tournament entry fees.&lt;br /&gt;
&lt;br /&gt;
=== Marketing and Promotions ===&lt;br /&gt;
&lt;br /&gt;
* Posters and Discount Codes&lt;br /&gt;
** Coordinating the distribution of convention posters across venues and local colleges. Each poster will include a discount code, with CupcakeDoll managing the creation of these codes.&lt;br /&gt;
** Posters should be placed only where they’re welcome, and coordinators should avoid places where they might cause issues.&lt;br /&gt;
* Social Media and Advertising&lt;br /&gt;
** Planning to use social media ads, particularly on Facebook, to promote events like a potential trick-or-treat event during the convention. These targeted ads would aim at drawing in families and younger attendees.&lt;br /&gt;
&lt;br /&gt;
=== Contracts and Signatures ===&lt;br /&gt;
&lt;br /&gt;
* Contract Issues&lt;br /&gt;
** Some contract files lacked signature fields, creating problems for electronic signing. Staff members have submitted as much as they could without signatures.&lt;br /&gt;
** A volunteer contract is being created that should be easily signable.&lt;br /&gt;
&lt;br /&gt;
=== Special Events ===&lt;br /&gt;
&lt;br /&gt;
* Trick-or-Treating Event&lt;br /&gt;
** Discussions around hosting a trick-or-treat event during the convention, where cosplayers hand out candy to children. The event could become a big draw for families.&lt;br /&gt;
** The team is working on getting approval from Aramark.&lt;br /&gt;
* Performance and Guest Events&lt;br /&gt;
** A guest performance featuring singing is planned. Karaoke will not be held on the main stage this year.&lt;br /&gt;
** DJ performances and a dance event are scheduled, with a possibility of integrating a VR dance club portal that connects to a virtual environment. This requires network drops or alternative solutions like Ethernet connections.&lt;br /&gt;
&lt;br /&gt;
=== Volunteer Management and Staffing ===&lt;br /&gt;
&lt;br /&gt;
* Logistics and Volunteer Coordination&lt;br /&gt;
** The logistics department is understaffed due to the departure of some department heads. They’re actively recruiting volunteers to handle load-ins, load-outs, and other logistical tasks, particularly for Wednesday and Monday shifts.&lt;br /&gt;
** Efforts are being made to coordinate staff availability for key load-in and load-out days, especially the day before and after the convention.&lt;br /&gt;
* Volunteer Scheduling&lt;br /&gt;
** There is a significant need for volunteers for load-out on Monday, the hardest day to staff. Scheduling posts will be updated in the logistics channel.&lt;br /&gt;
&lt;br /&gt;
=== Video Room and Media Permissions ===&lt;br /&gt;
&lt;br /&gt;
* Issues with Video Permissions&lt;br /&gt;
** The video room coordinator is still working to secure permissions for screenings. Funimation is no longer a reliable source, but requests have been sent to companies like Media Blasters and Discotek.&lt;br /&gt;
** Public domain content may be used as a fallback if no permissions are granted in time.&lt;br /&gt;
* Coordination with Media Blasters&lt;br /&gt;
** A historical note was mentioned about obtaining permissions directly from the founder of Media Blasters using his personal contact details found in a public document.&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous Topics ===&lt;br /&gt;
&lt;br /&gt;
* Earplugs for Attendees&lt;br /&gt;
** A suggestion was made to provide cheap earplugs at registration if noise pollution between the main stage and vendor area becomes an issue. However, it’s not expected to be a major problem.&lt;br /&gt;
* Workshop Rooms&lt;br /&gt;
** There will be no dedicated workshop rooms, but certain breakout rooms may serve similar functions.&lt;br /&gt;
* Halloween Decorations&lt;br /&gt;
** The team discussed the timing of the convention (right after Halloween) and the difficulty in sourcing Halloween decorations during that period.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Logistics_Inventory&amp;diff=1778</id>
		<title>Logistics Inventory</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Logistics_Inventory&amp;diff=1778"/>
		<updated>2024-09-29T19:19:07Z</updated>

		<summary type="html">&lt;p&gt;Beta: box labeling image&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Logistics_Department]]&lt;br /&gt;
== Policies ==&lt;br /&gt;
[[File:How-to-label-a-box.png|alt=how we label boxes|thumb|How we label our boxes]]&lt;br /&gt;
* &#039;&#039;&#039;Everything gets inventoried, but not everything gets counted.&#039;&#039;&#039; Some boxes may have different instructions. But in general, take pictures of what&#039;s in the DNI box, and post it to the logistics channel you have access to, or somewhere relevant per the instructions on the DNI sheet, along with what box it came from. Even though we don&#039;t want written inventory, we still need a rough idea as to what&#039;s in the box. Ideally spread the stuff around a little so we know what we have. This is especially important for prize boxes.&lt;br /&gt;
* &#039;&#039;&#039;If we decide we don&#039;t need a sheet for something, we need a picture of it.&#039;&#039;&#039;&lt;br /&gt;
*&#039;&#039;&#039;Color spikes go on opposite corners of a box, with the location written on the spike.&#039;&#039;&#039;&lt;br /&gt;
*&#039;&#039;&#039;Box labels go on the short ends of the box, on white duck tape.&#039;&#039;&#039; Technically we only need them on one side, and logistics staff want it on the side opposite the sterilite label, but it&#039;s far easier to tell a volunteer to just label both ends.&lt;br /&gt;
*&#039;&#039;&#039;All sheets go back to Beta.&#039;&#039;&#039; I don&#039;t care what happens to them, I want them all back&lt;br /&gt;
*&#039;&#039;&#039;As much as reasonable, one box to one sheet.&#039;&#039;&#039; Exceptions can be made&lt;br /&gt;
*&#039;&#039;&#039;Every box needs a unique name.&#039;&#039;&#039; Ideally a descriptive unique name, but you can also just append &amp;quot;A&amp;quot;, &amp;quot;B&amp;quot; etc. as needed.&lt;br /&gt;
*&#039;&#039;&#039;Any loose paper goes home with Beta.&#039;&#039;&#039; It may need to be scanned, it may need to be recycled, but it must come home with me!&lt;br /&gt;
&lt;br /&gt;
==Procedure==&lt;br /&gt;
&lt;br /&gt;
===Prep===&lt;br /&gt;
&lt;br /&gt;
*Have upper staff involved in the process read this procedure as a refresher; discuss and updated as needed&lt;br /&gt;
* Organize and print sheets (inventory sheets and DNI list)&lt;br /&gt;
*Print a list of things that need to be respiked&lt;br /&gt;
*Update and print instructions&lt;br /&gt;
*Print tape key&lt;br /&gt;
*Print this procedure&lt;br /&gt;
*Make sure to set out anything that needs to go in the morning (like scales, or those damn stickers I bought 2 years ago)&lt;br /&gt;
&lt;br /&gt;
===Plan for===&lt;br /&gt;
&lt;br /&gt;
*Someone to bring ice chests&lt;br /&gt;
*Someone to bring ice&lt;br /&gt;
*Consider if we need snacks/water. There is likely some in storage.&lt;br /&gt;
*Who&#039;s in charge of the inventory day - who will be assigning people to places, ensuring they&#039;ve read the instructions, and helping when needed&lt;br /&gt;
&lt;br /&gt;
===At Storage Prep before counting===&lt;br /&gt;
These can mostly be done in any order&lt;br /&gt;
&lt;br /&gt;
* Have everyone read the instructions, discuss as needed&lt;br /&gt;
*Get counting supplies out of filing cabinet&lt;br /&gt;
**clipboards&lt;br /&gt;
**pens&lt;br /&gt;
**binder clips for completed sheets&lt;br /&gt;
*Match pieces of tape to the tape key to help people match them&lt;br /&gt;
*Have everyone read the instructions, discuss as needed&lt;br /&gt;
&lt;br /&gt;
*Post tape key and instructions in a central location&lt;br /&gt;
&lt;br /&gt;
===Empty Storage and organize boxes and sheets ===&lt;br /&gt;
&lt;br /&gt;
#Pull everything out of storage and organize boxes by tape color. Spread out as needed along the wall to give plenty of space between color stacks. This helps get boxes together so all cosplay boxes will be together when we start for example. It will also help with respiking, which we had some issues getting corrected this year. Tape color piles may need to be split further into locations if there are a lot to a color (Light green and purple, are each 4 locations).&lt;br /&gt;
#Organize sheets with their colored box stacks.&lt;br /&gt;
#Match sheets to individual boxes. Do not separate out highlighted / precounted sheets, they still need to be verified.&lt;br /&gt;
#Respike then relocate boxes as needed, based on what the sheets say to do.&lt;br /&gt;
&lt;br /&gt;
===Count, minion, count! ===&lt;br /&gt;
Two people to a box, one person handles the sheet, one person handles the box, and otherwise work together to get through the box faster &lt;br /&gt;
#Put both your names on the sheet&lt;br /&gt;
#Check color tag, location, box name&lt;br /&gt;
##Respike or relabel as needed. Update sheet as needed.&lt;br /&gt;
#Empty the box&lt;br /&gt;
#Count things as they are going back into the box&lt;br /&gt;
# If the count doesn&#039;t match expected to actual -  &lt;br /&gt;
##Is this a consumable item that you may be able to refill? Pens, for example, you could pull more of from the misc office supplies boxes&lt;br /&gt;
##If it&#039;s not an item that can be refilled easily today at storage, just write in the actual quantity&lt;br /&gt;
#Put actual quantity in the &amp;quot;Actual Quantity&amp;quot; field &lt;br /&gt;
##Make sure to put in &amp;quot;0&amp;quot; if there were 0 there. That will either get refilled or removed from the sheet later.&lt;br /&gt;
# When box is done, set aside in a &amp;quot;done&amp;quot; pile, keeping it next to your &amp;quot;todo&amp;quot; color pile. The colors should still stay grouped.&lt;br /&gt;
# Put sheets with that color&#039;s &amp;quot;done&amp;quot; sheets. Use a clipboard or binder clip to keep them together and separated from the &amp;quot;todo&amp;quot; sheets.&lt;br /&gt;
&lt;br /&gt;
====Notes====&lt;br /&gt;
&lt;br /&gt;
*Do Misc Office Supplies LAST, we likely need to pull from these boxes to restock others&lt;br /&gt;
*We should consider having most people focus on one color at a time, as space allows, so that a color can be reviewed by upper staff and things tweaked in the boxes as needed&lt;br /&gt;
&lt;br /&gt;
====Verification Process====&lt;br /&gt;
If a box was counted on the way out, plan for a quicker review &lt;br /&gt;
&lt;br /&gt;
#Look at sheet, look in box.&lt;br /&gt;
#If necessary, empty the box&lt;br /&gt;
#For each item on the sheet, look at the corresponding items in the box and &#039;&#039;eyeball&#039;&#039; if the count is plausible&lt;br /&gt;
#If the count is plausible, put a checkbox in &amp;quot;Actual Quantity&amp;quot;&lt;br /&gt;
#If the count looks wrong, count the items and put the actual quantity in the &amp;quot;Actual Quantity&amp;quot; field&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Completed Box Review===&lt;br /&gt;
Upper staff (Logistics head, Sammich, Beta) reviews the sheets for a color stack, thinks about how they need to be for con, and makes any changes necessary. Could direct a second person to make changes to boxes while they update the sheets. Buddying up here also makes sense.&lt;br /&gt;
&lt;br /&gt;
===After Inventory===&lt;br /&gt;
&lt;br /&gt;
# Determine a place to have lunch - the company pays for lunch&lt;br /&gt;
#Take attendance for who is going to the lunch for tax and record purposes&lt;br /&gt;
#Company pays for lunch&lt;br /&gt;
#Discuss how inventory went and take notes. Focus on&lt;br /&gt;
##What were the pain points? How can we fix them&lt;br /&gt;
## What went wrong? How can we prevent it&lt;br /&gt;
##What when right? Lets make sure we do it again&lt;br /&gt;
##Any lessons learned?&lt;br /&gt;
#Update documentation and resources as needed&lt;br /&gt;
&lt;br /&gt;
===After-After Inventory=== &lt;br /&gt;
&lt;br /&gt;
#Reorder the sheets&lt;br /&gt;
#Scan the sheets&lt;br /&gt;
#Update the inventory spreadsheet - USING A WORKSHEET COPY. Do not edit the originals as they were before inventory&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=File:How-to-label-a-box.png&amp;diff=1777</id>
		<title>File:How-to-label-a-box.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=File:How-to-label-a-box.png&amp;diff=1777"/>
		<updated>2024-09-29T19:17:17Z</updated>

		<summary type="html">&lt;p&gt;Beta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;diagram on how we label boxes&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=IT_Processes_and_Responsibilities&amp;diff=1776</id>
		<title>IT Processes and Responsibilities</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=IT_Processes_and_Responsibilities&amp;diff=1776"/>
		<updated>2024-09-29T04:23:10Z</updated>

		<summary type="html">&lt;p&gt;Beta: add cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The IT department at the convention is responsible for setting up and maintaining the core technology infrastructure, including the registration server, network systems, and payment platforms like PayPal. They ensure reliable internet access, manage on-site equipment such as laptops and printers, and troubleshoot any technical issues that arise during the event. Post-con, IT handles server decommissioning, data syncing, and backups to keep the registration and other systems running smoothly.&lt;br /&gt;
&lt;br /&gt;
IT may provide assistance to our Tech (A/V) team, and vice versa when relevant and available.&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Key Skills for IT&#039;&#039;&#039; ==&lt;br /&gt;
Key skills an IT staff member needs include &#039;&#039;&#039;general Linux administration&#039;&#039;&#039; for managing servers and systems, &#039;&#039;&#039;networking&#039;&#039;&#039; to set up and troubleshoot internet and Wi-Fi connections, and &#039;&#039;&#039;DevOps automation&#039;&#039;&#039; skills (preferably with tools like Ansible) for software deployment and maintenance. They should also be proficient in &#039;&#039;&#039;hardware troubleshooting&#039;&#039;&#039; (printers, laptops, networking equipment), familiar with &#039;&#039;&#039;cloud services&#039;&#039;&#039; (such as Cloudflare for syncing and security), and have strong &#039;&#039;&#039;problem-solving&#039;&#039;&#039; and &#039;&#039;&#039;communication skills&#039;&#039;&#039; to assist users and work with other departments efficiently.&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Processes and Responsibilities&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Server Maintenance (Year-Round)&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Maintain the main server, Yuzuki on VPS Dime.&lt;br /&gt;
* Regular package updates for GitLab, MediaWiki, OS, and any other software. (Every two weeks in a perfect world, but this world ain&#039;t that perfect.)&lt;br /&gt;
* Maintain email systems via MX Route.&lt;br /&gt;
* Manage Cloudflare setup&lt;br /&gt;
* Update other web properties and ensure uptime.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Pre-Con IT Prep&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Negotiate and plan with the venue regarding internet and wireless setup.&lt;br /&gt;
* Pull out laptops and other IT equipment from storage, check them over.&lt;br /&gt;
** Reinstall or update operating systems, ensure readiness for use.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;At-Con IT Responsibilities&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Set up the &amp;quot;At-Con&amp;quot; registration server, network, and other IT systems.&lt;br /&gt;
* Work with venue IT and AV teams for power drops, network setup, and printer/server setups on our stringer.&lt;br /&gt;
* Set up and manage Scylla, our at-con server, including ensuring syncing/access to the internet is working&lt;br /&gt;
* Manage in-person network and printer support (desktop support) for other staff and departments.&lt;br /&gt;
* Monitor, troubleshoot, and resolve any IT/networking issues during the event.&lt;br /&gt;
* Liaising with venue IT if issues arise.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Post-Con Teardown&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Do registration computer setup in reverse&lt;br /&gt;
* Decommission the &amp;quot;At-Con&amp;quot; server, a 20-step process that needs to be documented and followed precisely. (Causes about 20 minutes of downtime to Registration.)&lt;br /&gt;
* If no internet is available at the venue, manual backup and transfer of data should be done before storing servers.&lt;br /&gt;
* Ensure that the database is synced properly after the event to avoid months-long delays (as occurred in prior years).&lt;br /&gt;
[[Category:IT Department]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=IT_Processes_and_Responsibilities&amp;diff=1775</id>
		<title>IT Processes and Responsibilities</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=IT_Processes_and_Responsibilities&amp;diff=1775"/>
		<updated>2024-09-29T04:22:47Z</updated>

		<summary type="html">&lt;p&gt;Beta: created page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The IT department at the convention is responsible for setting up and maintaining the core technology infrastructure, including the registration server, network systems, and payment platforms like PayPal. They ensure reliable internet access, manage on-site equipment such as laptops and printers, and troubleshoot any technical issues that arise during the event. Post-con, IT handles server decommissioning, data syncing, and backups to keep the registration and other systems running smoothly.&lt;br /&gt;
&lt;br /&gt;
IT may provide assistance to our Tech (A/V) team, and vice versa when relevant and available.&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Key Skills for IT&#039;&#039;&#039; ==&lt;br /&gt;
Key skills an IT staff member needs include &#039;&#039;&#039;general Linux administration&#039;&#039;&#039; for managing servers and systems, &#039;&#039;&#039;networking&#039;&#039;&#039; to set up and troubleshoot internet and Wi-Fi connections, and &#039;&#039;&#039;DevOps automation&#039;&#039;&#039; skills (preferably with tools like Ansible) for software deployment and maintenance. They should also be proficient in &#039;&#039;&#039;hardware troubleshooting&#039;&#039;&#039; (printers, laptops, networking equipment), familiar with &#039;&#039;&#039;cloud services&#039;&#039;&#039; (such as Cloudflare for syncing and security), and have strong &#039;&#039;&#039;problem-solving&#039;&#039;&#039; and &#039;&#039;&#039;communication skills&#039;&#039;&#039; to assist users and work with other departments efficiently.&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Processes and Responsibilities&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Server Maintenance (Year-Round)&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Maintain the main server, Yuzuki on VPS Dime.&lt;br /&gt;
* Regular package updates for GitLab, MediaWiki, OS, and any other software. (Every two weeks in a perfect world, but this world ain&#039;t that perfect.)&lt;br /&gt;
* Maintain email systems via MX Route.&lt;br /&gt;
* Manage Cloudflare setup&lt;br /&gt;
* Update other web properties and ensure uptime.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Pre-Con IT Prep&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Negotiate and plan with the venue regarding internet and wireless setup.&lt;br /&gt;
* Pull out laptops and other IT equipment from storage, check them over.&lt;br /&gt;
** Reinstall or update operating systems, ensure readiness for use.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;At-Con IT Responsibilities&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Set up the &amp;quot;At-Con&amp;quot; registration server, network, and other IT systems.&lt;br /&gt;
* Work with venue IT and AV teams for power drops, network setup, and printer/server setups on our stringer.&lt;br /&gt;
* Set up and manage Scylla, our at-con server, including ensuring syncing/access to the internet is working&lt;br /&gt;
* Manage in-person network and printer support (desktop support) for other staff and departments.&lt;br /&gt;
* Monitor, troubleshoot, and resolve any IT/networking issues during the event.&lt;br /&gt;
* Liaising with venue IT if issues arise.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Post-Con Teardown&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
* Do registration computer setup in reverse&lt;br /&gt;
* Decommission the &amp;quot;At-Con&amp;quot; server, a 20-step process that needs to be documented and followed precisely. (Causes about 20 minutes of downtime to Registration.)&lt;br /&gt;
* If no internet is available at the venue, manual backup and transfer of data should be done before storing servers.&lt;br /&gt;
* Ensure that the database is synced properly after the event to avoid months-long delays (as occurred in prior years).&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1774</id>
		<title>Onboarding: Logistics Head</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1774"/>
		<updated>2024-09-29T03:30:38Z</updated>

		<summary type="html">&lt;p&gt;Beta: more bullet points&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Software Access/Training Needed==&lt;br /&gt;
*Wiki for updating procedures and adding relevant notes&lt;br /&gt;
*Bitrix24 for accessing inventory spreadsheets and scans&lt;br /&gt;
==Tasks Needing Training==&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;IMPORTANT:&#039;&#039;&#039; The logistics head should be able manage people effectively, directing them as they load and unload equipment, or directing them for inventory&lt;br /&gt;
* General safety regarding proper lifting techniques, and how to watch volunteers and train/correct as needed&lt;br /&gt;
* Stacking policies for ensuring longevity of our boxes (and their lids)&lt;br /&gt;
* Box labeling policies&lt;br /&gt;
&lt;br /&gt;
=== Pre-Con ===&lt;br /&gt;
&lt;br /&gt;
* How to access our inventory spreadsheets&lt;br /&gt;
* How we do inventory and why we track inventory how we do, needs, goals, pain points&lt;br /&gt;
&lt;br /&gt;
=== Load In and Out ===&lt;br /&gt;
&lt;br /&gt;
* Familiarity with the load in/out timeline&lt;br /&gt;
* How to load and unload the truck&lt;br /&gt;
* How to load/unload storage&lt;br /&gt;
* Familiarity with ratchet straps and ensuring items are secured safely in the truck&lt;br /&gt;
* Knowing how to handle inventory, track what’s been packed, and ensure safe storage of fragile or sensitive items.&lt;br /&gt;
* What is our tape color system&lt;br /&gt;
* Familiarity with the con map and con locations&lt;br /&gt;
&lt;br /&gt;
===Post-Con Activities===&lt;br /&gt;
*Reaching out to people who participated in logistics task - ask for feedback, issues they saw, and suggestions. &lt;br /&gt;
*Handling post-con inventory sheets &amp;amp; prep for next year&lt;br /&gt;
[[Category:Onboarding Plans]]&lt;br /&gt;
[[Category:Logistics Department]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1773</id>
		<title>Onboarding: Logistics Head</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1773"/>
		<updated>2024-09-29T03:28:22Z</updated>

		<summary type="html">&lt;p&gt;Beta: add topic&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Software Access/Training Needed==&lt;br /&gt;
*Wiki for updating procedures and adding relevant notes&lt;br /&gt;
*Bitrix24 for accessing inventory spreadsheets and scans&lt;br /&gt;
==Tasks Needing Training==&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;IMPORTANT:&#039;&#039;&#039; The logistics head should be able manage people effectively, directing them as they load and unload equipment, or directing them for inventory&lt;br /&gt;
&lt;br /&gt;
=== Pre-Con ===&lt;br /&gt;
&lt;br /&gt;
* How to access our inventory spreadsheets&lt;br /&gt;
* How we do inventory and why we track inventory how we do, needs, goals, pain points&lt;br /&gt;
&lt;br /&gt;
=== Load In and Out ===&lt;br /&gt;
&lt;br /&gt;
* Familiarity with the load in/out timeline&lt;br /&gt;
* How to load and unload the truck&lt;br /&gt;
* How to load/unload storage&lt;br /&gt;
* Familiarity with ratchet straps and ensuring items are secured safely in the truck&lt;br /&gt;
* Knowing how to handle inventory, track what’s been packed, and ensure safe storage of fragile or sensitive items.&lt;br /&gt;
* What is our tape color system&lt;br /&gt;
* Familiarity with the con map and con locations&lt;br /&gt;
&lt;br /&gt;
===Post-Con Activities===&lt;br /&gt;
*Reaching out to people who participated in logistics task - ask for feedback, issues they saw, and suggestions. &lt;br /&gt;
*Handling post-con inventory sheets &amp;amp; prep for next year&lt;br /&gt;
[[Category:Onboarding Plans]]&lt;br /&gt;
[[Category:Logistics Department]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1772</id>
		<title>Onboarding: Logistics Head</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1772"/>
		<updated>2024-09-29T03:25:39Z</updated>

		<summary type="html">&lt;p&gt;Beta: cats&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Software Access/Training Needed==&lt;br /&gt;
*Wiki for updating procedures and adding relevant notes&lt;br /&gt;
*Bitrix24 for accessing inventory spreadsheets and scans&lt;br /&gt;
==Tasks Needing Training==&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;IMPORTANT:&#039;&#039;&#039; The logistics head should be able manage people effectively, directing them as they load and unload equipment, or directing them for inventory&lt;br /&gt;
&lt;br /&gt;
=== Pre-Con ===&lt;br /&gt;
&lt;br /&gt;
* How to access our inventory spreadsheets&lt;br /&gt;
* How we do inventory and why we track inventory how we do, needs, goals, pain points&lt;br /&gt;
&lt;br /&gt;
=== Load In and Out ===&lt;br /&gt;
&lt;br /&gt;
* How to load and unload the truck&lt;br /&gt;
* How to load/unload storage&lt;br /&gt;
* Familiarity with ratchet straps and ensuring items are secured safely in the truck&lt;br /&gt;
* Knowing how to handle inventory, track what’s been packed, and ensure safe storage of fragile or sensitive items.&lt;br /&gt;
* What is our tape color system&lt;br /&gt;
* Familiarity with the con map and con locations&lt;br /&gt;
&lt;br /&gt;
===Post-Con Activities===&lt;br /&gt;
*Reaching out to people who participated in logistics task - ask for feedback, issues they saw, and suggestions. &lt;br /&gt;
*Handling post-con inventory sheets &amp;amp; prep for next year&lt;br /&gt;
[[Category:Onboarding Plans]]&lt;br /&gt;
[[Category:Logistics Department]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1771</id>
		<title>Onboarding: Logistics Head</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Onboarding:_Logistics_Head&amp;diff=1771"/>
		<updated>2024-09-29T03:25:02Z</updated>

		<summary type="html">&lt;p&gt;Beta: created page from notes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Software Access/Training Needed==&lt;br /&gt;
*Wiki for updating procedures and adding relevant notes&lt;br /&gt;
*Bitrix24 for accessing inventory spreadsheets and scans&lt;br /&gt;
==Tasks Needing Training==&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;IMPORTANT:&#039;&#039;&#039; The logistics head should be able manage people effectively, directing them as they load and unload equipment, or directing them for inventory&lt;br /&gt;
&lt;br /&gt;
=== Pre-Con ===&lt;br /&gt;
&lt;br /&gt;
* How to access our inventory spreadsheets&lt;br /&gt;
* How we do inventory and why we track inventory how we do, needs, goals, pain points&lt;br /&gt;
&lt;br /&gt;
=== Load In and Out ===&lt;br /&gt;
&lt;br /&gt;
* How to load and unload the truck&lt;br /&gt;
* How to load/unload storage&lt;br /&gt;
* Familiarity with ratchet straps and ensuring items are secured safely in the truck&lt;br /&gt;
* Knowing how to handle inventory, track what’s been packed, and ensure safe storage of fragile or sensitive items.&lt;br /&gt;
* What is our tape color system&lt;br /&gt;
* Familiarity with the con map and con locations&lt;br /&gt;
&lt;br /&gt;
===Post-Con Activities===&lt;br /&gt;
*Reaching out to people who participated in logistics task - ask for feedback, issues they saw, and suggestions. &lt;br /&gt;
*Handling post-con inventory sheets &amp;amp; prep for next year&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Logistics:_Load_In_and_Load_Out&amp;diff=1770</id>
		<title>Logistics: Load In and Load Out</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Logistics:_Load_In_and_Load_Out&amp;diff=1770"/>
		<updated>2024-09-29T01:39:18Z</updated>

		<summary type="html">&lt;p&gt;Beta: added truck loading diagram on the loading section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Departments]][[Category:Logistics_Department]][[Category:Policies]]&lt;br /&gt;
Logistics operates mainly at the beginning and end of con. We pick up the truck from the rental place around 3pm on Wednesday, load everything in the storage unit into it, and park it at Thomas&#039; house overnight. Setup starts as soon as the venue will let us, typically early Thursday in recent years. We unload the truck as quickly as possible, then it goes to the arcade department for their load-in. The table vendor generally delivers the eight foot tables for the merchants in early afternoon and we have to unload their truck, but sometimes they can&#039;t deliver and we have to pick the tables up with the truck. When arcade gets back with the truck full of cabinets we may have to help them unload. Once everything is unloaded Logistics is responsible for moving everything to where it needs to go and setting up the artist alley tables. Once that&#039;s done we don&#039;t have a lot of work during con apart from resetting rooms from time to time.&lt;br /&gt;
Load-out starts around 5pm on Sunday at the beginning of Closing Ceremonies, and more-or-less runs in reverse of load-in.&lt;br /&gt;
&lt;br /&gt;
See [[Reserving the Truck]]&lt;br /&gt;
==Time Table==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; |Event&lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; |2019&lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; |2021&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; |Average&lt;br /&gt;
|-&lt;br /&gt;
!Start Time&lt;br /&gt;
!End Time&lt;br /&gt;
!Total&lt;br /&gt;
!Start Time&lt;br /&gt;
!End Time&lt;br /&gt;
!Total&lt;br /&gt;
|-&lt;br /&gt;
|Load Truck from Storage&lt;br /&gt;
|3:30 pm&lt;br /&gt;
|6:15 pm&lt;br /&gt;
|2:45&lt;br /&gt;
|3:31 pm&lt;br /&gt;
|5:30 pm&lt;br /&gt;
|1:59&lt;br /&gt;
|2:22&lt;br /&gt;
|-&lt;br /&gt;
|Unload Truck at Venue&lt;br /&gt;
|8:45 am&lt;br /&gt;
|10:15 am&lt;br /&gt;
|1:30&lt;br /&gt;
|9:30 am&lt;br /&gt;
|11:03 am&lt;br /&gt;
|1:33&lt;br /&gt;
|1:32&lt;br /&gt;
|-&lt;br /&gt;
|Load Truck from Venue&lt;br /&gt;
|9:56 pm&lt;br /&gt;
|2:07 am&lt;br /&gt;
|4:09&lt;br /&gt;
|10:32 pm&lt;br /&gt;
|12:16 am&lt;br /&gt;
|1:44&lt;br /&gt;
|2:56&lt;br /&gt;
|-&lt;br /&gt;
|Unload Truck at Storage&lt;br /&gt;
|9:34 am&lt;br /&gt;
|1:06 pm&lt;br /&gt;
|3:32&lt;br /&gt;
|10:26 am&lt;br /&gt;
|12:32 pm&lt;br /&gt;
|2:06&lt;br /&gt;
|2:49&lt;br /&gt;
|}&lt;br /&gt;
==Loading==&lt;br /&gt;
It is bet to have two people managing and organizing things. One in the truck and one out of the truck. When loading into the truck, the person in the truck has command. When loading into storage, the person off the truck is in command. Command meaning requesting which items are needed next. It is best to not have the two managers in the truck together.&lt;br /&gt;
[[File:Truck-Loading-Diagram.png|alt=Truck Loading Diagram|thumb|How we load the truck. This may not be the best way, but it&#039;s the way we&#039;ve come to do it and it seems to work pretty well for us.]]&lt;br /&gt;
===Thing to remember when loading the truck===&lt;br /&gt;
* Stanchion carts first on opposite walls.&lt;br /&gt;
** Misc small boxes can be stacked on the stanchion carts.&lt;br /&gt;
* Death carts (pipe and drape bases) either next or last.&lt;br /&gt;
* Stack plastic totes up to the top ratchet points.&lt;br /&gt;
** Typically for clear top black handles, 5 high.&lt;br /&gt;
** Strap the top row to the wall to prevent falling.&lt;br /&gt;
* Keep similar type of boxes together.&lt;br /&gt;
* Misc cardboard and non-totes fill the center.&lt;br /&gt;
* Long stock lays on top of that down the center.&lt;br /&gt;
* Leave room near the door for Shoji screen.&lt;br /&gt;
** The A-frame cork board can be used to protect the shoji screen.&lt;br /&gt;
** Other flat stock can be strap to it.&lt;br /&gt;
* In the cab&lt;br /&gt;
** Mirror&lt;br /&gt;
** Large mixer&lt;br /&gt;
** Flat screen TV&lt;br /&gt;
===Things to remember when loading storage===&lt;br /&gt;
*When stacking totes, heavy on bottom and light on top.&lt;br /&gt;
*Cash box boxes go on very back top, left&lt;br /&gt;
*Board games very back top, right&lt;br /&gt;
*Dollar store poster next to board game&lt;br /&gt;
* Wagon standing full upright next to shelf in back right&lt;br /&gt;
*Grid cubes on the floor on the back right, just in front of the wagon&lt;br /&gt;
*Tech cardboard under back shelf and under table&lt;br /&gt;
*Misc tech and cords and things in middle shelf&lt;br /&gt;
*Green top stacked to the ceiling on left table.&lt;br /&gt;
*Clear totes on floor in front of left table stacked near to the ceiling.&lt;br /&gt;
*Misc boxes on right shelves&lt;br /&gt;
*Smaller long stock between left table and shelf&lt;br /&gt;
*Projector screen in front of left table*Sandbags (team lift) right right bottom&lt;br /&gt;
*Shoji screen laying on its side in front of right shelf&lt;br /&gt;
*Stanchion carts carefully against the shoji screen&lt;br /&gt;
*Chairs can be put upside down on the black road case near the front.&lt;br /&gt;
*Things that expire should be near the front&lt;br /&gt;
**Food&lt;br /&gt;
**Hand sanitizer&lt;br /&gt;
*Things we will need before con should be at the front&lt;br /&gt;
**Filing cabinet front left&lt;br /&gt;
**Tape boxes front right&lt;br /&gt;
**Tabling box and button box near front right&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=File:Truck-Loading-Diagram.png&amp;diff=1769</id>
		<title>File:Truck-Loading-Diagram.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=File:Truck-Loading-Diagram.png&amp;diff=1769"/>
		<updated>2024-09-29T01:38:01Z</updated>

		<summary type="html">&lt;p&gt;Beta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Instructional image on how we load our truck&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=List_of_Departments&amp;diff=1768</id>
		<title>List of Departments</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=List_of_Departments&amp;diff=1768"/>
		<updated>2024-09-28T13:55:37Z</updated>

		<summary type="html">&lt;p&gt;Beta: fix category link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Departments]][[Category:Con Info]]&lt;br /&gt;
* [[Artist Alley]]&lt;br /&gt;
* [[Contracts]]&lt;br /&gt;
* [[:Category:Cosplay_Department|Cosplay]]&lt;br /&gt;
* [[Dance]]&lt;br /&gt;
* [[Gaming]]&lt;br /&gt;
** [[Arcade]]&lt;br /&gt;
** [[Board Gaming]]&lt;br /&gt;
** [[Console Gaming]]&lt;br /&gt;
** [[PC Gaming]]&lt;br /&gt;
** [[Tabletop]]&lt;br /&gt;
* [[:Category:Guest Department|Guests]]&lt;br /&gt;
* [[HR|Human Resources]]&lt;br /&gt;
** [[Volunteers]]&lt;br /&gt;
* [[:Category:Logistics_Department|Logistics]]&lt;br /&gt;
* [[Marketing]]&lt;br /&gt;
** [[Club Outreach]]&lt;br /&gt;
** [[Con Outreach]]&lt;br /&gt;
** [[Design]]&lt;br /&gt;
** [[Distribution]]&lt;br /&gt;
** [[Photography]]&lt;br /&gt;
** [[Press]]&lt;br /&gt;
** [[Social Media]]&lt;br /&gt;
** [[Sponsorship]]&lt;br /&gt;
* [[Philanthropy]]&lt;br /&gt;
* [[Programming]]&lt;br /&gt;
** [[Hentai]]&lt;br /&gt;
** [[Karaoke]]&lt;br /&gt;
** [[Main Stage]]&lt;br /&gt;
** [[Panels]]&lt;br /&gt;
** [[Video Programming]]&lt;br /&gt;
* [[Registration]]&lt;br /&gt;
* [[Rovers]]&lt;br /&gt;
* [[Swap Meet]]&lt;br /&gt;
* [[Tech]]&lt;br /&gt;
* [[Vendors]]&lt;br /&gt;
* [[BACON#Team_BACON.21|Website &amp;amp; Reg Admin]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Main_Page&amp;diff=1767</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Main_Page&amp;diff=1767"/>
		<updated>2024-09-28T13:55:14Z</updated>

		<summary type="html">&lt;p&gt;Beta: fix category link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--        BANNER ACROSS TOP OF PAGE        --&amp;gt;&lt;br /&gt;
{| id=&amp;quot;mp-topbanner&amp;quot; style=&amp;quot;width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:61%; color:#000;&amp;quot; |&lt;br /&gt;
&amp;lt;!--        &amp;quot;WELCOME TO&amp;quot;       --&amp;gt;&lt;br /&gt;
{| style=&amp;quot;width:280px; border:none; background:none;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:280px; text-align:center; white-space:nowrap; color:#000;&amp;quot; |&lt;br /&gt;
&amp;lt;div style=&amp;quot;font-size:162%; border:none; margin:0; padding:.1em; color:#000;&amp;quot;&amp;gt;Welcome to the [[Meta:About|SNAFU Con Wiki]],&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;top:+0.2em; font-size:95%;&amp;quot;&amp;gt;a resource for our staff and those interested in how we work.&amp;lt;/div&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;!--        PORTAL LIST ON RIGHT-HAND SIDE        --&amp;gt;&lt;br /&gt;
| style=&amp;quot;width:13%; font-size:95%;&amp;quot; |&lt;br /&gt;
* [[Programming]]&lt;br /&gt;
* [[Gaming]]&lt;br /&gt;
* [[:Category:Cosplay_Department|Cosplay]]&lt;br /&gt;
* [[Rave]]&lt;br /&gt;
| style=&amp;quot;width:13%; font-size:95%;&amp;quot; |&lt;br /&gt;
* [[Registration]]&lt;br /&gt;
* [[Tech]]&lt;br /&gt;
* [[Rovers]]&lt;br /&gt;
* [[:Category:Logistics_Department|Logistics]]&lt;br /&gt;
| style=&amp;quot;width:13%; font-size:95%;&amp;quot; |&lt;br /&gt;
* [[Artist Alley]]&lt;br /&gt;
* [[Vendors]]&lt;br /&gt;
* [[:Category:Guest Department|Guests]]&lt;br /&gt;
* &#039;&#039;&#039;[[List of Departments|All departments]]&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
== Welcome ==&lt;br /&gt;
This is a PUBLIC wiki and is primarily for staff usage. Any staff member may update this site using their [[BACON]] username and password. Feel free to add information on your department at any of the links above.&lt;br /&gt;
&lt;br /&gt;
General attendees will not find much use from this site.&lt;br /&gt;
&lt;br /&gt;
== New Staff Members ==&lt;br /&gt;
This section is WIP but hopefully we can get you the information you need to succeed. &lt;br /&gt;
&lt;br /&gt;
* First, check out our [[Staff Resources]] page to get an idea of the different systems we use&lt;br /&gt;
* Next, find your department in the list (click on &amp;quot;All departments&amp;quot; if you don&#039;t see it) and read what information we&#039;ve put together for your department&lt;br /&gt;
* Finally, log into the wiki using your registration username and password and edit the wiki to help yourself and others have a full and useful knowledge resource&lt;br /&gt;
&lt;br /&gt;
== 2024 Planning ==&lt;br /&gt;
&lt;br /&gt;
* [[2024 Meeting Notes]] - Meeting notes for our 2024 con year meetings&lt;br /&gt;
&lt;br /&gt;
== 2023 Planning ==&lt;br /&gt;
&lt;br /&gt;
* [[2023 Meeting Notes]] - Meeting notes for our 2023 con year meetings&lt;br /&gt;
* [[2023 Notes to Selves]] - Notes we made in 2021 for the 2023 con&lt;br /&gt;
&lt;br /&gt;
== Where to Start with this Wiki ==&lt;br /&gt;
*&#039;&#039;&#039;[[Updating This Wiki |How to Update this Wiki]]&#039;&#039;&#039; We really want you to update this wiki!&lt;br /&gt;
*[[Staff Resources]] - What tools you may need as staff&lt;br /&gt;
*[[Special:Categories |List of Page Categories]]&lt;br /&gt;
*[[List of Departments]]&lt;br /&gt;
*[[Special:AllPages |List of all Pages]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Historical Conventions ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
select badge.year, count(*) as attendees&lt;br /&gt;
from reg_badges as badge&lt;br /&gt;
where badge.checkin_date is not null&lt;br /&gt;
group by badge.year&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align: right;&amp;quot;&lt;br /&gt;
 ! Year&lt;br /&gt;
 ! Venue&lt;br /&gt;
 ! Theme&lt;br /&gt;
 ! Start&lt;br /&gt;
 ! End&lt;br /&gt;
 ! Attendees&lt;br /&gt;
 |-&lt;br /&gt;
 | 2023&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Folklore&lt;br /&gt;
 | Nov 17&lt;br /&gt;
 | Nov 19&lt;br /&gt;
 | &#039;&#039;upcoming&#039;&#039;&lt;br /&gt;
 |-&lt;br /&gt;
 | 2021&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Time Travel&lt;br /&gt;
 | Oct 28&lt;br /&gt;
 | Nov 1&lt;br /&gt;
 | 1536&lt;br /&gt;
 |-&lt;br /&gt;
 | 2020&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Time Travel&lt;br /&gt;
 | Nov 13&lt;br /&gt;
 | Nov 15&lt;br /&gt;
 | &#039;&#039;cancelled&#039;&#039;&lt;br /&gt;
 |-&lt;br /&gt;
 | 2019&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Adventure&lt;br /&gt;
 | Nov 15&lt;br /&gt;
 | Nov 17&lt;br /&gt;
 | 2187&lt;br /&gt;
 |-&lt;br /&gt;
 | 2018&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Paranormal&lt;br /&gt;
 | Nov 16&lt;br /&gt;
 | Nov 18&lt;br /&gt;
 | 2107&lt;br /&gt;
 |-&lt;br /&gt;
 | 2017&lt;br /&gt;
 | Nugget&lt;br /&gt;
 | Multiverse&lt;br /&gt;
 | Oct 6&lt;br /&gt;
 | Oct 8&lt;br /&gt;
 | 1843&lt;br /&gt;
 |-&lt;br /&gt;
 | 2016&lt;br /&gt;
 | Nugget&lt;br /&gt;
 | Suits&lt;br /&gt;
 | Oct 7&lt;br /&gt;
 | Oct 9&lt;br /&gt;
 | 1639&lt;br /&gt;
 |-&lt;br /&gt;
 | 2015&lt;br /&gt;
 | Nugget&lt;br /&gt;
 | Mystery&lt;br /&gt;
 | Oct 30&lt;br /&gt;
 | Nov  1&lt;br /&gt;
 | 1865&lt;br /&gt;
 |-&lt;br /&gt;
 | 2014&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Magic&lt;br /&gt;
 | Oct 24&lt;br /&gt;
 | Oct 26&lt;br /&gt;
 | 1902&lt;br /&gt;
 |-&lt;br /&gt;
 | 2013&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Apocalypse&lt;br /&gt;
 | Oct 25&lt;br /&gt;
 | Oct 27&lt;br /&gt;
 | 1628&lt;br /&gt;
 |-&lt;br /&gt;
 | 2012&lt;br /&gt;
 | GSR&lt;br /&gt;
 | IN SPACE!&lt;br /&gt;
 | Sep 28&lt;br /&gt;
 | Sep 30&lt;br /&gt;
 | 1284&lt;br /&gt;
 |-&lt;br /&gt;
 | 2011&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Cyberpunk&lt;br /&gt;
 | Sep  9&lt;br /&gt;
 | Sep 11&lt;br /&gt;
 | 1025&lt;br /&gt;
 |-&lt;br /&gt;
 | 2010&lt;br /&gt;
 | GSR&lt;br /&gt;
 | &lt;br /&gt;
 | Oct 22&lt;br /&gt;
 | Oct 23&lt;br /&gt;
 | 700&lt;br /&gt;
 |}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Attendance is counted by warm bodies.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: 2022 was an intentional skip&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Main_Page&amp;diff=1766</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Main_Page&amp;diff=1766"/>
		<updated>2024-09-28T13:54:52Z</updated>

		<summary type="html">&lt;p&gt;Beta: move Logistics link to the category page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--        BANNER ACROSS TOP OF PAGE        --&amp;gt;&lt;br /&gt;
{| id=&amp;quot;mp-topbanner&amp;quot; style=&amp;quot;width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:61%; color:#000;&amp;quot; |&lt;br /&gt;
&amp;lt;!--        &amp;quot;WELCOME TO&amp;quot;       --&amp;gt;&lt;br /&gt;
{| style=&amp;quot;width:280px; border:none; background:none;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:280px; text-align:center; white-space:nowrap; color:#000;&amp;quot; |&lt;br /&gt;
&amp;lt;div style=&amp;quot;font-size:162%; border:none; margin:0; padding:.1em; color:#000;&amp;quot;&amp;gt;Welcome to the [[Meta:About|SNAFU Con Wiki]],&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;top:+0.2em; font-size:95%;&amp;quot;&amp;gt;a resource for our staff and those interested in how we work.&amp;lt;/div&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;!--        PORTAL LIST ON RIGHT-HAND SIDE        --&amp;gt;&lt;br /&gt;
| style=&amp;quot;width:13%; font-size:95%;&amp;quot; |&lt;br /&gt;
* [[Programming]]&lt;br /&gt;
* [[Gaming]]&lt;br /&gt;
* [[:Category:Cosplay_Department|Cosplay]]&lt;br /&gt;
* [[Rave]]&lt;br /&gt;
| style=&amp;quot;width:13%; font-size:95%;&amp;quot; |&lt;br /&gt;
* [[Registration]]&lt;br /&gt;
* [[Tech]]&lt;br /&gt;
* [[Rovers]]&lt;br /&gt;
* [[Category:Logistics_Department|Logistics]]&lt;br /&gt;
| style=&amp;quot;width:13%; font-size:95%;&amp;quot; |&lt;br /&gt;
* [[Artist Alley]]&lt;br /&gt;
* [[Vendors]]&lt;br /&gt;
* [[:Category:Guest Department|Guests]]&lt;br /&gt;
* &#039;&#039;&#039;[[List of Departments|All departments]]&#039;&#039;&#039;&lt;br /&gt;
|}&lt;br /&gt;
== Welcome ==&lt;br /&gt;
This is a PUBLIC wiki and is primarily for staff usage. Any staff member may update this site using their [[BACON]] username and password. Feel free to add information on your department at any of the links above.&lt;br /&gt;
&lt;br /&gt;
General attendees will not find much use from this site.&lt;br /&gt;
&lt;br /&gt;
== New Staff Members ==&lt;br /&gt;
This section is WIP but hopefully we can get you the information you need to succeed. &lt;br /&gt;
&lt;br /&gt;
* First, check out our [[Staff Resources]] page to get an idea of the different systems we use&lt;br /&gt;
* Next, find your department in the list (click on &amp;quot;All departments&amp;quot; if you don&#039;t see it) and read what information we&#039;ve put together for your department&lt;br /&gt;
* Finally, log into the wiki using your registration username and password and edit the wiki to help yourself and others have a full and useful knowledge resource&lt;br /&gt;
&lt;br /&gt;
== 2024 Planning ==&lt;br /&gt;
&lt;br /&gt;
* [[2024 Meeting Notes]] - Meeting notes for our 2024 con year meetings&lt;br /&gt;
&lt;br /&gt;
== 2023 Planning ==&lt;br /&gt;
&lt;br /&gt;
* [[2023 Meeting Notes]] - Meeting notes for our 2023 con year meetings&lt;br /&gt;
* [[2023 Notes to Selves]] - Notes we made in 2021 for the 2023 con&lt;br /&gt;
&lt;br /&gt;
== Where to Start with this Wiki ==&lt;br /&gt;
*&#039;&#039;&#039;[[Updating This Wiki |How to Update this Wiki]]&#039;&#039;&#039; We really want you to update this wiki!&lt;br /&gt;
*[[Staff Resources]] - What tools you may need as staff&lt;br /&gt;
*[[Special:Categories |List of Page Categories]]&lt;br /&gt;
*[[List of Departments]]&lt;br /&gt;
*[[Special:AllPages |List of all Pages]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Historical Conventions ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
select badge.year, count(*) as attendees&lt;br /&gt;
from reg_badges as badge&lt;br /&gt;
where badge.checkin_date is not null&lt;br /&gt;
group by badge.year&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align: right;&amp;quot;&lt;br /&gt;
 ! Year&lt;br /&gt;
 ! Venue&lt;br /&gt;
 ! Theme&lt;br /&gt;
 ! Start&lt;br /&gt;
 ! End&lt;br /&gt;
 ! Attendees&lt;br /&gt;
 |-&lt;br /&gt;
 | 2023&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Folklore&lt;br /&gt;
 | Nov 17&lt;br /&gt;
 | Nov 19&lt;br /&gt;
 | &#039;&#039;upcoming&#039;&#039;&lt;br /&gt;
 |-&lt;br /&gt;
 | 2021&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Time Travel&lt;br /&gt;
 | Oct 28&lt;br /&gt;
 | Nov 1&lt;br /&gt;
 | 1536&lt;br /&gt;
 |-&lt;br /&gt;
 | 2020&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Time Travel&lt;br /&gt;
 | Nov 13&lt;br /&gt;
 | Nov 15&lt;br /&gt;
 | &#039;&#039;cancelled&#039;&#039;&lt;br /&gt;
 |-&lt;br /&gt;
 | 2019&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Adventure&lt;br /&gt;
 | Nov 15&lt;br /&gt;
 | Nov 17&lt;br /&gt;
 | 2187&lt;br /&gt;
 |-&lt;br /&gt;
 | 2018&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Paranormal&lt;br /&gt;
 | Nov 16&lt;br /&gt;
 | Nov 18&lt;br /&gt;
 | 2107&lt;br /&gt;
 |-&lt;br /&gt;
 | 2017&lt;br /&gt;
 | Nugget&lt;br /&gt;
 | Multiverse&lt;br /&gt;
 | Oct 6&lt;br /&gt;
 | Oct 8&lt;br /&gt;
 | 1843&lt;br /&gt;
 |-&lt;br /&gt;
 | 2016&lt;br /&gt;
 | Nugget&lt;br /&gt;
 | Suits&lt;br /&gt;
 | Oct 7&lt;br /&gt;
 | Oct 9&lt;br /&gt;
 | 1639&lt;br /&gt;
 |-&lt;br /&gt;
 | 2015&lt;br /&gt;
 | Nugget&lt;br /&gt;
 | Mystery&lt;br /&gt;
 | Oct 30&lt;br /&gt;
 | Nov  1&lt;br /&gt;
 | 1865&lt;br /&gt;
 |-&lt;br /&gt;
 | 2014&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Magic&lt;br /&gt;
 | Oct 24&lt;br /&gt;
 | Oct 26&lt;br /&gt;
 | 1902&lt;br /&gt;
 |-&lt;br /&gt;
 | 2013&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Apocalypse&lt;br /&gt;
 | Oct 25&lt;br /&gt;
 | Oct 27&lt;br /&gt;
 | 1628&lt;br /&gt;
 |-&lt;br /&gt;
 | 2012&lt;br /&gt;
 | GSR&lt;br /&gt;
 | IN SPACE!&lt;br /&gt;
 | Sep 28&lt;br /&gt;
 | Sep 30&lt;br /&gt;
 | 1284&lt;br /&gt;
 |-&lt;br /&gt;
 | 2011&lt;br /&gt;
 | GSR&lt;br /&gt;
 | Cyberpunk&lt;br /&gt;
 | Sep  9&lt;br /&gt;
 | Sep 11&lt;br /&gt;
 | 1025&lt;br /&gt;
 |-&lt;br /&gt;
 | 2010&lt;br /&gt;
 | GSR&lt;br /&gt;
 | &lt;br /&gt;
 | Oct 22&lt;br /&gt;
 | Oct 23&lt;br /&gt;
 | 700&lt;br /&gt;
 |}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Attendance is counted by warm bodies.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Note: 2022 was an intentional skip&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=List_of_Departments&amp;diff=1765</id>
		<title>List of Departments</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=List_of_Departments&amp;diff=1765"/>
		<updated>2024-09-28T13:54:31Z</updated>

		<summary type="html">&lt;p&gt;Beta: move Logistics link to the category page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Departments]][[Category:Con Info]]&lt;br /&gt;
* [[Artist Alley]]&lt;br /&gt;
* [[Contracts]]&lt;br /&gt;
* [[:Category:Cosplay_Department|Cosplay]]&lt;br /&gt;
* [[Dance]]&lt;br /&gt;
* [[Gaming]]&lt;br /&gt;
** [[Arcade]]&lt;br /&gt;
** [[Board Gaming]]&lt;br /&gt;
** [[Console Gaming]]&lt;br /&gt;
** [[PC Gaming]]&lt;br /&gt;
** [[Tabletop]]&lt;br /&gt;
* [[:Category:Guest Department|Guests]]&lt;br /&gt;
* [[HR|Human Resources]]&lt;br /&gt;
** [[Volunteers]]&lt;br /&gt;
* [[Category:Logistics_Department|Logistics]]&lt;br /&gt;
* [[Marketing]]&lt;br /&gt;
** [[Club Outreach]]&lt;br /&gt;
** [[Con Outreach]]&lt;br /&gt;
** [[Design]]&lt;br /&gt;
** [[Distribution]]&lt;br /&gt;
** [[Photography]]&lt;br /&gt;
** [[Press]]&lt;br /&gt;
** [[Social Media]]&lt;br /&gt;
** [[Sponsorship]]&lt;br /&gt;
* [[Philanthropy]]&lt;br /&gt;
* [[Programming]]&lt;br /&gt;
** [[Hentai]]&lt;br /&gt;
** [[Karaoke]]&lt;br /&gt;
** [[Main Stage]]&lt;br /&gt;
** [[Panels]]&lt;br /&gt;
** [[Video Programming]]&lt;br /&gt;
* [[Registration]]&lt;br /&gt;
* [[Rovers]]&lt;br /&gt;
* [[Swap Meet]]&lt;br /&gt;
* [[Tech]]&lt;br /&gt;
* [[Vendors]]&lt;br /&gt;
* [[BACON#Team_BACON.21|Website &amp;amp; Reg Admin]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Logistics&amp;diff=1764</id>
		<title>Logistics</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Logistics&amp;diff=1764"/>
		<updated>2024-09-28T13:53:42Z</updated>

		<summary type="html">&lt;p&gt;Beta: Beta moved page Logistics to Logistics: Load In and Load Out: This is only load in and out and logistics has other pages. Going to use the logistics category as the main page instead of this one&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Logistics: Load In and Load Out]]&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Logistics:_Load_In_and_Load_Out&amp;diff=1763</id>
		<title>Logistics: Load In and Load Out</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Logistics:_Load_In_and_Load_Out&amp;diff=1763"/>
		<updated>2024-09-28T13:53:41Z</updated>

		<summary type="html">&lt;p&gt;Beta: Beta moved page Logistics to Logistics: Load In and Load Out: This is only load in and out and logistics has other pages. Going to use the logistics category as the main page instead of this one&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Departments]][[Category:Logistics_Department]][[Category:Policies]]&lt;br /&gt;
Logistics operates mainly at the beginning and end of con. We pick up the truck from the rental place around 3pm on Wednesday, load everything in the storage unit into it, and park it at Thomas&#039; house overnight. Setup starts as soon as the venue will let us, typically early Thursday in recent years. We unload the truck as quickly as possible, then it goes to the arcade department for their load-in. The table vendor generally delivers the eight foot tables for the merchants in early afternoon and we have to unload their truck, but sometimes they can&#039;t deliver and we have to pick the tables up with the truck. When arcade gets back with the truck full of cabinets we may have to help them unload. Once everything is unloaded Logistics is responsible for moving everything to where it needs to go and setting up the artist alley tables. Once that&#039;s done we don&#039;t have a lot of work during con apart from resetting rooms from time to time.&lt;br /&gt;
Load-out starts around 5pm on Sunday at the beginning of Closing Ceremonies, and more-or-less runs in reverse of load-in.&lt;br /&gt;
&lt;br /&gt;
See [[Reserving the Truck]]&lt;br /&gt;
==Time Table==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; |Event&lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; |2019&lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; |2021&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; |Average&lt;br /&gt;
|-&lt;br /&gt;
!Start Time&lt;br /&gt;
!End Time&lt;br /&gt;
!Total&lt;br /&gt;
!Start Time&lt;br /&gt;
!End Time&lt;br /&gt;
!Total&lt;br /&gt;
|-&lt;br /&gt;
|Load Truck from Storage&lt;br /&gt;
|3:30 pm&lt;br /&gt;
|6:15 pm&lt;br /&gt;
|2:45&lt;br /&gt;
|3:31 pm&lt;br /&gt;
|5:30 pm&lt;br /&gt;
|1:59&lt;br /&gt;
|2:22&lt;br /&gt;
|-&lt;br /&gt;
|Unload Truck at Venue&lt;br /&gt;
|8:45 am&lt;br /&gt;
|10:15 am&lt;br /&gt;
|1:30&lt;br /&gt;
|9:30 am&lt;br /&gt;
|11:03 am&lt;br /&gt;
|1:33&lt;br /&gt;
|1:32&lt;br /&gt;
|-&lt;br /&gt;
|Load Truck from Venue&lt;br /&gt;
|9:56 pm&lt;br /&gt;
|2:07 am&lt;br /&gt;
|4:09&lt;br /&gt;
|10:32 pm&lt;br /&gt;
|12:16 am&lt;br /&gt;
|1:44&lt;br /&gt;
|2:56&lt;br /&gt;
|-&lt;br /&gt;
|Unload Truck at Storage&lt;br /&gt;
|9:34 am&lt;br /&gt;
|1:06 pm&lt;br /&gt;
|3:32&lt;br /&gt;
|10:26 am&lt;br /&gt;
|12:32 pm&lt;br /&gt;
|2:06&lt;br /&gt;
|2:49&lt;br /&gt;
|}&lt;br /&gt;
==Loading==&lt;br /&gt;
It is bet to have two people managing and organizing things. One in the truck and one out of the truck. When loading into the truck, the person in the truck has command. When loading into storage, the person off the truck is in command. Command meaning requesting which items are needed next. It is best to not have the two managers in the truck together.&lt;br /&gt;
===Thing to remember when loading the truck===&lt;br /&gt;
* Stanchion carts first on opposite walls.&lt;br /&gt;
** Misc small boxes can be stacked on the stanchion carts.&lt;br /&gt;
* Death carts (pipe and drape bases) either next or last.&lt;br /&gt;
* Stack plastic totes up to the top ratchet points.&lt;br /&gt;
** Typically for clear top black handles, 5 high.&lt;br /&gt;
** Strap the top row to the wall to prevent falling.&lt;br /&gt;
* Keep similar type of boxes together.&lt;br /&gt;
* Misc cardboard and non-totes fill the center.&lt;br /&gt;
* Long stock lays on top of that down the center.&lt;br /&gt;
* Leave room near the door for Shoji screen.&lt;br /&gt;
** The A-frame cork board can be used to protect the shoji screen.&lt;br /&gt;
** Other flat stock can be strap to it.&lt;br /&gt;
* In the cab&lt;br /&gt;
** Mirror&lt;br /&gt;
** Large mixer&lt;br /&gt;
** Flat screen TV&lt;br /&gt;
===Things to remember when loading storage===&lt;br /&gt;
*When stacking totes, heavy on bottom and light on top.&lt;br /&gt;
*Cash box boxes go on very back top, left&lt;br /&gt;
*Board games very back top, right&lt;br /&gt;
*Dollar store poster next to board game&lt;br /&gt;
* Wagon standing full upright next to shelf in back right&lt;br /&gt;
*Grid cubes on the floor on the back right, just in front of the wagon&lt;br /&gt;
*Tech cardboard under back shelf and under table&lt;br /&gt;
*Misc tech and cords and things in middle shelf&lt;br /&gt;
*Green top stacked to the ceiling on left table.&lt;br /&gt;
*Clear totes on floor in front of left table stacked near to the ceiling.&lt;br /&gt;
*Misc boxes on right shelves&lt;br /&gt;
*Smaller long stock between left table and shelf&lt;br /&gt;
*Projector screen in front of left table*Sandbags (team lift) right right bottom&lt;br /&gt;
*Shoji screen laying on its side in front of right shelf&lt;br /&gt;
*Stanchion carts carefully against the shoji screen&lt;br /&gt;
*Chairs can be put upside down on the black road case near the front.&lt;br /&gt;
*Things that expire should be near the front&lt;br /&gt;
**Food&lt;br /&gt;
**Hand sanitizer&lt;br /&gt;
*Things we will need before con should be at the front&lt;br /&gt;
**Filing cabinet front left&lt;br /&gt;
**Tape boxes front right&lt;br /&gt;
**Tabling box and button box near front right&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Category:Logistics_Department&amp;diff=1762</id>
		<title>Category:Logistics Department</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Category:Logistics_Department&amp;diff=1762"/>
		<updated>2024-09-28T13:50:17Z</updated>

		<summary type="html">&lt;p&gt;Beta: created category page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Logistics Department ensures that things get from point A to point B at con. &lt;br /&gt;
We handle loading and unloading of the truck, getting boxes to the correct locations, and then doing it all in reverse at the end of con. We also handle inventorying our supplies. Acquisitions and receiving is part of this department, too. &lt;br /&gt;
&lt;br /&gt;
For several of our annual tasks we ask for as many staff members as can show up. Can you count? Help us with annual inventory. Can you move a box? Help us with load in/out.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Logistics_Inventory&amp;diff=1761</id>
		<title>Logistics Inventory</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Logistics_Inventory&amp;diff=1761"/>
		<updated>2024-09-28T13:47:12Z</updated>

		<summary type="html">&lt;p&gt;Beta: add cat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Logistics_Department]]&lt;br /&gt;
== Policies ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Everything gets inventoried, but not everything gets counted.&#039;&#039;&#039; Some boxes may have different instructions. But in general, take pictures of what&#039;s in the DNI box, and post it to the logistics channel you have access to, or somewhere relevant per the instructions on the DNI sheet, along with what box it came from. Even though we don&#039;t want written inventory, we still need a rough idea as to what&#039;s in the box. Ideally spread the stuff around a little so we know what we have. This is especially important for prize boxes. &lt;br /&gt;
* &#039;&#039;&#039;If we decide we don&#039;t need a sheet for something, we need a picture of it.&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Color spikes go on opposite corners of a box, with the location written on the spike.&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Box labels go on the short ends of the box, on white duck tape.&#039;&#039;&#039; Technically we only need them on one side, and logistics staff want it on the side opposite the sterilite label, but it&#039;s far easier to tell a volunteer to just label both ends.&lt;br /&gt;
* &#039;&#039;&#039;All sheets go back to Beta.&#039;&#039;&#039; I don&#039;t care what happens to them, I want them all back&lt;br /&gt;
* &#039;&#039;&#039;As much as reasonable, one box to one sheet.&#039;&#039;&#039; Exceptions can be made&lt;br /&gt;
* &#039;&#039;&#039;Every box needs a unique name.&#039;&#039;&#039; Ideally a descriptive unique name, but you can also just append &amp;quot;A&amp;quot;, &amp;quot;B&amp;quot; etc. as needed. &lt;br /&gt;
* &#039;&#039;&#039;Any loose paper goes home with Beta.&#039;&#039;&#039; It may need to be scanned, it may need to be recycled, but it must come home with me!&lt;br /&gt;
&lt;br /&gt;
== Procedure ==&lt;br /&gt;
&lt;br /&gt;
=== Prep ===&lt;br /&gt;
&lt;br /&gt;
* Have upper staff involved in the process read this procedure as a refresher; discuss and updated as needed&lt;br /&gt;
* Organize and print sheets (inventory sheets and DNI list)&lt;br /&gt;
* Print a list of things that need to be respiked&lt;br /&gt;
* Update and print instructions&lt;br /&gt;
* Print tape key&lt;br /&gt;
* Print this procedure&lt;br /&gt;
* Make sure to set out anything that needs to go in the morning (like scales, or those damn stickers I bought 2 years ago)&lt;br /&gt;
&lt;br /&gt;
=== Plan for ===&lt;br /&gt;
&lt;br /&gt;
* Someone to bring ice chests&lt;br /&gt;
* Someone to bring ice&lt;br /&gt;
* Consider if we need snacks/water. There is likely some in storage.&lt;br /&gt;
* Who&#039;s in charge of the inventory day - who will be assigning people to places, ensuring they&#039;ve read the instructions, and helping when needed&lt;br /&gt;
&lt;br /&gt;
=== At Storage Prep before counting ===&lt;br /&gt;
These can mostly be done in any order&lt;br /&gt;
&lt;br /&gt;
* Have everyone read the instructions, discuss as needed&lt;br /&gt;
* Get counting supplies out of filing cabinet&lt;br /&gt;
** clipboards&lt;br /&gt;
** pens&lt;br /&gt;
** binder clips for completed sheets&lt;br /&gt;
* Match pieces of tape to the tape key to help people match them&lt;br /&gt;
* Have everyone read the instructions, discuss as needed&lt;br /&gt;
&lt;br /&gt;
* Post tape key and instructions in a central location&lt;br /&gt;
&lt;br /&gt;
=== Empty Storage and organize boxes and sheets ===&lt;br /&gt;
&lt;br /&gt;
# Pull everything out of storage and organize boxes by tape color. Spread out as needed along the wall to give plenty of space between color stacks. This helps get boxes together so all cosplay boxes will be together when we start for example. It will also help with respiking, which we had some issues getting corrected this year. Tape color piles may need to be split further into locations if there are a lot to a color (Light green and purple, are each 4 locations).&lt;br /&gt;
# Organize sheets with their colored box stacks. &lt;br /&gt;
# Match sheets to individual boxes. Do not separate out highlighted / precounted sheets, they still need to be verified.&lt;br /&gt;
# Respike then relocate boxes as needed, based on what the sheets say to do.&lt;br /&gt;
&lt;br /&gt;
=== Count, minion, count! ===&lt;br /&gt;
Two people to a box, one person handles the sheet, one person handles the box, and otherwise work together to get through the box faster&lt;br /&gt;
# Put both your names on the sheet&lt;br /&gt;
# Check color tag, location, box name&lt;br /&gt;
## Respike or relabel as needed. Update sheet as needed.&lt;br /&gt;
# Empty the box&lt;br /&gt;
# Count things as they are going back into the box&lt;br /&gt;
# If the count doesn&#039;t match expected to actual - &lt;br /&gt;
## Is this a consumable item that you may be able to refill? Pens, for example, you could pull more of from the misc office supplies boxes&lt;br /&gt;
## If it&#039;s not an item that can be refilled easily today at storage, just write in the actual quantity&lt;br /&gt;
# Put actual quantity in the &amp;quot;Actual Quantity&amp;quot; field &lt;br /&gt;
## Make sure to put in &amp;quot;0&amp;quot; if there were 0 there. That will either get refilled or removed from the sheet later.&lt;br /&gt;
# When box is done, set aside in a &amp;quot;done&amp;quot; pile, keeping it next to your &amp;quot;todo&amp;quot; color pile. The colors should still stay grouped.&lt;br /&gt;
# Put sheets with that color&#039;s &amp;quot;done&amp;quot; sheets. Use a clipboard or binder clip to keep them together and separated from the &amp;quot;todo&amp;quot; sheets.&lt;br /&gt;
&lt;br /&gt;
==== Notes ====&lt;br /&gt;
&lt;br /&gt;
* Do Misc Office Supplies LAST, we likely need to pull from these boxes to restock others&lt;br /&gt;
* We should consider having most people focus on one color at a time, as space allows, so that a color can be reviewed by upper staff and things tweaked in the boxes as needed&lt;br /&gt;
&lt;br /&gt;
==== Verification Process ====&lt;br /&gt;
If a box was counted on the way out, plan for a quicker review&lt;br /&gt;
&lt;br /&gt;
# Look at sheet, look in box. &lt;br /&gt;
# If necessary, empty the box&lt;br /&gt;
# For each item on the sheet, look at the corresponding items in the box and &#039;&#039;eyeball&#039;&#039; if the count is plausible&lt;br /&gt;
# If the count is plausible, put a checkbox in &amp;quot;Actual Quantity&amp;quot;&lt;br /&gt;
# If the count looks wrong, count the items and put the actual quantity in the &amp;quot;Actual Quantity&amp;quot; field&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Completed Box Review ===&lt;br /&gt;
Upper staff (Logistics head, Sammich, Beta) reviews the sheets for a color stack, thinks about how they need to be for con, and makes any changes necessary. Could direct a second person to make changes to boxes while they update the sheets. Buddying up here also makes sense.&lt;br /&gt;
&lt;br /&gt;
=== After Inventory ===&lt;br /&gt;
&lt;br /&gt;
# Determine a place to have lunch - the company pays for lunch&lt;br /&gt;
# Take attendance for who is going to the lunch for tax and record purposes&lt;br /&gt;
# Company pays for lunch&lt;br /&gt;
# Discuss how inventory went and take notes. Focus on&lt;br /&gt;
## What were the pain points? How can we fix them&lt;br /&gt;
## What went wrong? How can we prevent it&lt;br /&gt;
## What when right? Lets make sure we do it again&lt;br /&gt;
## Any lessons learned?&lt;br /&gt;
# Update documentation and resources as needed&lt;br /&gt;
&lt;br /&gt;
=== After-After Inventory ===&lt;br /&gt;
&lt;br /&gt;
# Reorder the sheets&lt;br /&gt;
# Scan the sheets&lt;br /&gt;
# Update the inventory spreadsheet - USING A WORKSHEET COPY. Do not edit the originals as they were before inventory&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1760</id>
		<title>RT</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1760"/>
		<updated>2024-09-24T03:11:37Z</updated>

		<summary type="html">&lt;p&gt;Beta: put formatting back&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Procedures]][[Category:Third Party Software]]&lt;br /&gt;
==Request Tracker==&lt;br /&gt;
RT (Request Tracker) is the ticketing system the con uses to handle email requests. As of 2016, &#039;&#039;&#039;all&#039;&#039;&#039; departmental emails are handled in RT. &lt;br /&gt;
&lt;br /&gt;
The best way to think of RT is like a really fancy group email system. Queues are the group email boxes. Multiple people can see and handle emails, and everyone who is involved with that box gets updated on everything going on so that everyone is on the same page.&lt;br /&gt;
==Video Tutorials==&lt;br /&gt;
Beta made a four-part video tutorial series, which is posted on our YouTube:&lt;br /&gt;
https://www.youtube.com/playlist?list=PLnJMQShIVjsl4XuTJJ4bPEYWDJJowhEN0&lt;br /&gt;
==Logging in ==&lt;br /&gt;
You can access RT from https://tickets.snafucon.com/&#039;&#039;&#039;.&#039;&#039;&#039; Your account is linked to [[BACON]] so log in with your current username and password. However, you will need to have privileges set up by the admin or you will only be able to see your previous tickets (if any) but not actually be able to see or answer any from the queue.&lt;br /&gt;
== Setting your Signature ==&lt;br /&gt;
When logged in: &lt;br /&gt;
# Hover over &amp;quot;Logged in as {you}&amp;quot;&lt;br /&gt;
# Hover over Settings&lt;br /&gt;
# Click &amp;quot;About Me&amp;quot;&lt;br /&gt;
# Your signature box is on the lower left. Edit as you see fit.&lt;br /&gt;
# Click &amp;quot;Save Preferences&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Signature Format ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;{Your Name}&lt;br /&gt;
&lt;br /&gt;
{Your Title or Department, as relevant}&lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite!&lt;br /&gt;
&lt;br /&gt;
https://snafucon.com&lt;br /&gt;
&lt;br /&gt;
{Optional relevant message}&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Example Signature ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Beta&lt;br /&gt;
&lt;br /&gt;
SNAFU Con Human Resources &lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite! &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;https://snafucon.com&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Apply now! &amp;lt;nowiki&amp;gt;https://register.snafucon.com/staff/apply/&amp;lt;/nowiki&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Queues==&lt;br /&gt;
Most users will only have one Queue, but some users will have multiple ones. The easiest way to navigate RT is by queue. The Queues you have access to are listed on the right-hand side of the screen under &amp;quot;Quick Search.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Click on the queue name to see all the tickets in a queue.&lt;br /&gt;
==Reply/Comment to a Ticket==&lt;br /&gt;
When you reply to a ticket it is sent to all of the people who administer the queue that it is in, and the requester (the person who sent the email in the first place.)&lt;br /&gt;
&lt;br /&gt;
When you comment on a ticket, it is only sent to the people who administer the queue.&lt;br /&gt;
&lt;br /&gt;
There are two ways of replying to and commenting on tickets. &lt;br /&gt;
===Reply by Email ===&lt;br /&gt;
You should only reply by email if you aren&#039;t closing or resolving the ticket. &#039;&#039;&#039;You can not resolve the ticket by email.&#039;&#039;&#039;&lt;br /&gt;
#Simply respond to the email that was sent to you.&lt;br /&gt;
Notice that the email you&#039;re sending goes back to the queue email. So, if you&#039;re responding to an email that originally went to [[/cdn-cgi/l/email-protection|[email protected]]], then the email you send will also go to [[/cdn-cgi/l/email-protection|[email protected]]] It is important that you do not alter the [SNAFU #(number)] part of the subject. RT will look at the subject to put the reply in the right ticket. &lt;br /&gt;
&lt;br /&gt;
The information that is added to the beginning of the email you received (the ticket information with Queue info and Ticket URL, etc.) &#039;&#039;&#039;WILL be included in your email if you don&#039;t delete it&#039;&#039;&#039;. It is up to you if you want that information in your email, but it should probably be removed before sending to minimize confusion.&lt;br /&gt;
===Comment by Email===&lt;br /&gt;
Comment by replying and changing the email to (queue email)[[/cdn-cgi/l/email-protection|[email protected]]] snafucon.com&lt;br /&gt;
So if the queue email was registration, you can comment by sending an email to [[/cdn-cgi/l/email-protection|[email protected]]]&lt;br /&gt;
&lt;br /&gt;
As before, keep the [SNAFU #(number)] part of subject the same so RT can route your comment correctly. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reply/Comment by Logging In===&lt;br /&gt;
To reply to a ticket you need to get into a ticket to view it. You can click on a ticket from your dashboard, or from your queue.&lt;br /&gt;
#To reply/comment to the ticket, scroll down to the &#039;&#039;&#039;History&#039;&#039;&#039; section. You can view all history for this ticket (emails in and out).&lt;br /&gt;
#Click Reply or Comment [[File:History.png]]&lt;br /&gt;
#If you are the first reply, on the right-hand side you may want to update the &#039;&#039;&#039;Status to Open&#039;&#039;&#039; and the &#039;&#039;&#039;Owner to you&#039;&#039;&#039;. RT should update it for you after your reply if you don&#039;t make any settings. &#039;&#039;&#039;If you are closing the ticket&#039;&#039;&#039; you will want to change the status to &#039;&#039;&#039;resolved&#039;&#039;&#039; (or rejected as applicable). [[file:Ticket and Transactions.gif]]&lt;br /&gt;
#Type your reply in the box (if you have one set up, your signature is automatically added to the end of the message - if you are replying at the top of the message make sure your signature is at the top. If you are replying in-line, your signature stays at the bottom).&lt;br /&gt;
# If you want to add a person as a one-time cc or bcc, then do that in the applicable fields&lt;br /&gt;
#When you are ready to send your reply (or add your comment), click &amp;quot;Update Ticket&amp;quot; and your reply will be sent and will show in the ticket history&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; The reply box is exactly the same for reply or comment except it will be pink if you are replying. If you want to change your reply to a comment (or vice versa) on the right-hand side of the screen there is a drop-down menu and you can change whether the message you are writing is a reply or a comment. The color of the text area will change accordingly.&lt;br /&gt;
[[file:Reply-vs-comment.png]]&lt;br /&gt;
==Creating a Ticket/Emailing Out==&lt;br /&gt;
[[File:How to send emails.png|845x845px]]&lt;br /&gt;
==Bulk Update==&lt;br /&gt;
To do a bulk update (&#039;&#039;&#039;most useful for deleting spam&#039;&#039;&#039;):&lt;br /&gt;
#From the landing page, click on the queue you want to update (right-hand side of the screen)&lt;br /&gt;
#In the upper-right corner, click on &#039;&#039;&#039;Bulk Update&#039;&#039;&#039;&lt;br /&gt;
#Uncheck the messages you want to leave alone, or use the &#039;&#039;&#039;Clear All&#039;&#039;&#039; button at the bottom if that&#039;s faster.&lt;br /&gt;
#Once you have only the messages checked that you want to update, scroll to the bottom&lt;br /&gt;
#In the form at the bottom make the changes that you want to apply to all the messages checked. To set them to &amp;quot;deleted,&amp;quot; you pull down the drop-down next to &#039;&#039;&#039;Make Status&#039;&#039;&#039; and choose deleted.&lt;br /&gt;
#Once you have filled the form with all the changes you want to make, click &#039;&#039;&#039;Update.&#039;&#039;&#039;&lt;br /&gt;
You can also use Bulk Update to merge tickets (see below) or do many other maintenance tasks. Deleting is the most common.&lt;br /&gt;
&lt;br /&gt;
[[file:Bulk_Update.gif]]&lt;br /&gt;
==Updating a Ticket==&lt;br /&gt;
Once you are in a ticket you will see a header with all sorts of information you can change. &#039;&#039;&#039;Every section had things you can modify by clicking on its header.&#039;&#039;&#039;&lt;br /&gt;
So, if you want to update who owns the ticket and whether it&#039;s open/closed, you can click on &#039;&#039;&#039;The Basics&#039;&#039;&#039; and update those things from there. &#039;&#039;&#039;If you have multiple queues&#039;&#039;&#039; you can change what queue the ticket is in from The Basics section, because people often send requests to the wrong email.&lt;br /&gt;
===Statuses===&lt;br /&gt;
;Initial Phase (search &amp;lt;code&amp;gt;__initial__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket is new and hasn&#039;t yet been reviewed by department staff.&lt;br /&gt;
:;&amp;lt;code&amp;gt;triage&amp;lt;/code&amp;gt;&lt;br /&gt;
::The initial status for tickets created via email. These tickets are waiting for triage, and may be spam.&lt;br /&gt;
:;&amp;lt;code&amp;gt;new&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket has been triaged and is not spam, but has not yet been reviewed by department staff.&lt;br /&gt;
:&lt;br /&gt;
;Active Phase (search &amp;lt;code&amp;gt;__active__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket has been reviewed by a staffer at least once and is actively being worked on.&lt;br /&gt;
:;&amp;lt;code&amp;gt;review&amp;lt;/code&amp;gt;&lt;br /&gt;
::Something has happened (usually a reply) and the ticket needs the attention of a staffer.&lt;br /&gt;
:;&amp;lt;code&amp;gt;working&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket has been reviewed, but the Owner still needs to reply. This should only be set by the ticket owner, and indicates that they&#039;re working on a reply and so it doesn&#039;t need to be reviewed by anyone else.&lt;br /&gt;
:;&amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;&lt;br /&gt;
::We&#039;re waiting for the Requestor to reply. No action is needed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;timeout&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket was &amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;, but the Requestor hasn&#039;t responded for too long. Either send a reminder or set to &amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;.&lt;br /&gt;
:;&amp;lt;code&amp;gt;hold&amp;lt;/code&amp;gt;&lt;br /&gt;
::No one needs to do anything, but we don&#039;t want the ticket to be closed for some reason.&lt;br /&gt;
:&lt;br /&gt;
;Inactive Phase (search &amp;lt;code&amp;gt;__inactive__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket does not require more work and should not normally be shown. Inactive tickets can still be found via the search system.&lt;br /&gt;
:;&amp;lt;code&amp;gt;resolved&amp;lt;/code&amp;gt;&lt;br /&gt;
::The Requestor&#039;s objective has been achieved and the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;rejected&amp;lt;/code&amp;gt;&lt;br /&gt;
::We declined to do what the Requestor wanted and the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;&lt;br /&gt;
::The Requestor took too long to respond and we gave up, so the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket isn&#039;t spam, but we want it to go away and there&#039;s no reason to keep it as a permanent record. This will be used most often for automated notifications from various systems. Tickets in the &amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt; status aren&#039;t actually deleted immediately: they stick around for at least 30 days before being shredded.&lt;br /&gt;
:;&amp;lt;code&amp;gt;spam&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket is spam and should go away. Tickets marked spam will be kept for at least 30 days, then used to train the spam filter and shredded.&lt;br /&gt;
&lt;br /&gt;
==Merging Tickets==&lt;br /&gt;
Sometimes the way someone replies to a thread opens a new ticket. Sometimes people email multiple times. Sometimes you just need to merge everything together. &lt;br /&gt;
&lt;br /&gt;
If you have two or more tickets that are really all part of the same thread then they should be merged into the same ticket. Luckily, merging is really easy (a little TOO easy).&lt;br /&gt;
===Merging One Ticket===&lt;br /&gt;
#In the ticket view click on &amp;quot;Links&amp;quot;&lt;br /&gt;
#Fill out the Merge Into field the bottom&lt;br /&gt;
#Click Save Changes&lt;br /&gt;
The ticket is now merged.&lt;br /&gt;
===Merging by Bulk Update===&lt;br /&gt;
The way you merge tickets is:&lt;br /&gt;
#Determine the id number of the main ticket you want to merge into.&lt;br /&gt;
#Go to bulk update for that queue and select the other ticket(s) you want to merge&lt;br /&gt;
#Scroll to the bottom and enter the id number of the main ticket&lt;br /&gt;
#Click Update.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:RT_Merge.png]]&lt;br /&gt;
&lt;br /&gt;
You should now have the whole thread in one.&lt;br /&gt;
Notice that it warns that the process is not reversible, so don&#039;t mess it up!&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CAUTION: If you do any more bulk updating RT will continue to merge tickets until you either navigate to another page or clear out the merge field!&#039;&#039;&#039;&lt;br /&gt;
==For the Admin==&lt;br /&gt;
===Create a Privileged User===&lt;br /&gt;
#Admin-&amp;gt;Users-&amp;gt;Select&lt;br /&gt;
#Put user in the go to user box.&lt;br /&gt;
#*If the user does not exist, it needs to be created. So you can create the user by sending them an email from RT letting them know they can log into RT. It&#039;s freaking magic!&lt;br /&gt;
#Open the user account&lt;br /&gt;
#Check the box to make the user a privileged user&lt;br /&gt;
#Save Changes at the bottom&lt;br /&gt;
===Add a user to a queue===&lt;br /&gt;
#Admin-&amp;gt;Queues-&amp;gt;Select&lt;br /&gt;
#Select the queue&lt;br /&gt;
#Click &amp;quot;Watchers&amp;quot;&lt;br /&gt;
#enter the user&#039;s name in the &amp;quot;Find People whose&amp;quot; box and hit Go - The user will show up in the lower right area&lt;br /&gt;
#Select &amp;quot;AdminCC&amp;quot;&lt;br /&gt;
#Click &amp;quot;Save Changes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===Merging users where the good email is on the account not connected to BACON===&lt;br /&gt;
This is a common but really, really annoying condition where RT will will not email to the BACON email because the BACON account is already linked to a different email. It is common when people change their email address, though. &lt;br /&gt;
&lt;br /&gt;
====Beta&#039;s Method====&lt;br /&gt;
I don&#039;t know if this is the best way but here&#039;s how I&#039;m handling it on an old ticket and a way that Sammich seems to believe will work. &lt;br /&gt;
&lt;br /&gt;
#Copy good and bad emails to a third location like notepad so I have them safe for this process. I like to be very clear in my notes &amp;quot;good email: (email)&amp;quot; and &amp;quot;bad email:(email)&amp;quot; along with links to each user so if I messed up I had all the information still available.&lt;br /&gt;
#On the bad account, set the email address (and possibly the username if it&#039;s the same as the email address) to something unique but bogus. I used &amp;quot;x@gmail.com&amp;quot; because the email in question was @gmail and it was temporary and easy.&lt;br /&gt;
#On the good account, set the email address to what you want it to be: the &amp;quot;good&amp;quot; email address&lt;br /&gt;
#Save&lt;br /&gt;
#On the bad account, set the email address to what the good account use to have: the &amp;quot;bad&amp;quot; email address&lt;br /&gt;
#Save&lt;br /&gt;
#Merge the &amp;quot;bad&amp;quot; user into the &amp;quot;good&amp;quot; user&lt;br /&gt;
&lt;br /&gt;
====Sammich&#039;s Method/note====&lt;br /&gt;
&amp;lt;blockquote&amp;gt;What I did is change the non-BACON-linked account with the new email to have no email, change the BACON-linked account to the correct email, and then merge the non-BACON account into the BACON account. If they&#039;re still going to use the old address you&#039;d either need to swap the addresses as you said, or create a new account for the old email and immediately merge it into their main account.&amp;lt;/blockquote&amp;gt;&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1759</id>
		<title>RT</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1759"/>
		<updated>2024-09-24T03:08:08Z</updated>

		<summary type="html">&lt;p&gt;Beta: formatting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Procedures]][[Category:Third Party Software]]&lt;br /&gt;
==Request Tracker==&lt;br /&gt;
RT (Request Tracker) is the ticketing system the con uses to handle email requests. As of 2016, &#039;&#039;&#039;all&#039;&#039;&#039; departmental emails are handled in RT. &lt;br /&gt;
&lt;br /&gt;
The best way to think of RT is like a really fancy group email system. Queues are the group email boxes. Multiple people can see and handle emails, and everyone who is involved with that box gets updated on everything going on so that everyone is on the same page.&lt;br /&gt;
==Video Tutorials==&lt;br /&gt;
Beta made a four-part video tutorial series, which is posted on our YouTube:&lt;br /&gt;
https://www.youtube.com/playlist?list=PLnJMQShIVjsl4XuTJJ4bPEYWDJJowhEN0&lt;br /&gt;
==Logging in ==&lt;br /&gt;
You can access RT from https://tickets.snafucon.com/&#039;&#039;&#039;.&#039;&#039;&#039; Your account is linked to [[BACON]] so log in with your current username and password. However, you will need to have privileges set up by the admin or you will only be able to see your previous tickets (if any) but not actually be able to see or answer any from the queue.&lt;br /&gt;
== Setting your Signature ==&lt;br /&gt;
When logged in: &lt;br /&gt;
# Hover over &amp;quot;Logged in as {you}&amp;quot;&lt;br /&gt;
# Hover over Settings&lt;br /&gt;
# Click &amp;quot;About Me&amp;quot;&lt;br /&gt;
# Your signature box is on the lower left. Edit as you see fit.&lt;br /&gt;
# Click &amp;quot;Save Preferences&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Signature Format ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;{Your Name}&lt;br /&gt;
&lt;br /&gt;
{Your Title or Department, as relevant}&lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite!&lt;br /&gt;
&lt;br /&gt;
https://snafucon.com&lt;br /&gt;
&lt;br /&gt;
{Optional relevant message}&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Example Signature ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Beta&lt;br /&gt;
&lt;br /&gt;
SNAFU Con Human Resources &lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite! &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;https://snafucon.com&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Apply now! &amp;lt;nowiki&amp;gt;https://register.snafucon.com/staff/apply/&amp;lt;/nowiki&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Queues==&lt;br /&gt;
Most users will only have one Queue, but some users will have multiple ones. The easiest way to navigate RT is by queue. The Queues you have access to are listed on the right-hand side of the screen under &amp;quot;Quick Search.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Click on the queue name to see all the tickets in a queue.&lt;br /&gt;
==Reply/Comment to a Ticket==&lt;br /&gt;
When you reply to a ticket it is sent to all of the people who administer the queue that it is in, and the requester (the person who sent the email in the first place.)&lt;br /&gt;
&lt;br /&gt;
When you comment on a ticket, it is only sent to the people who administer the queue.&lt;br /&gt;
&lt;br /&gt;
There are two ways of replying to and commenting on tickets. &lt;br /&gt;
===Reply by Email ===&lt;br /&gt;
You should only reply by email if you aren&#039;t closing or resolving the ticket. &#039;&#039;&#039;You can not resolve the ticket by email.&#039;&#039;&#039;&lt;br /&gt;
#Simply respond to the email that was sent to you.&lt;br /&gt;
Notice that the email you&#039;re sending goes back to the queue email. So, if you&#039;re responding to an email that originally went to [[/cdn-cgi/l/email-protection|[email protected]]], then the email you send will also go to [[/cdn-cgi/l/email-protection|[email protected]]] It is important that you do not alter the [SNAFU #(number)] part of the subject. RT will look at the subject to put the reply in the right ticket. &lt;br /&gt;
&lt;br /&gt;
The information that is added to the beginning of the email you received (the ticket information with Queue info and Ticket URL, etc.) &#039;&#039;&#039;WILL be included in your email if you don&#039;t delete it&#039;&#039;&#039;. It is up to you if you want that information in your email, but it should probably be removed before sending to minimize confusion.&lt;br /&gt;
===Comment by Email===&lt;br /&gt;
Comment by replying and changing the email to (queue email)[[/cdn-cgi/l/email-protection|[email protected]]] snafucon.com&lt;br /&gt;
So if the queue email was registration, you can comment by sending an email to [[/cdn-cgi/l/email-protection|[email protected]]]&lt;br /&gt;
&lt;br /&gt;
As before, keep the [SNAFU #(number)] part of subject the same so RT can route your comment correctly. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reply/Comment by Logging In===&lt;br /&gt;
To reply to a ticket you need to get into a ticket to view it. You can click on a ticket from your dashboard, or from your queue.&lt;br /&gt;
#To reply/comment to the ticket, scroll down to the &#039;&#039;&#039;History&#039;&#039;&#039; section. You can view all history for this ticket (emails in and out).&lt;br /&gt;
#Click Reply or Comment [[File:History.png]]&lt;br /&gt;
#If you are the first reply, on the right-hand side you may want to update the &#039;&#039;&#039;Status to Open&#039;&#039;&#039; and the &#039;&#039;&#039;Owner to you&#039;&#039;&#039;. RT should update it for you after your reply if you don&#039;t make any settings. &#039;&#039;&#039;If you are closing the ticket&#039;&#039;&#039; you will want to change the status to &#039;&#039;&#039;resolved&#039;&#039;&#039; (or rejected as applicable). [[file:Ticket and Transactions.gif]]&lt;br /&gt;
#Type your reply in the box (if you have one set up, your signature is automatically added to the end of the message - if you are replying at the top of the message make sure your signature is at the top. If you are replying in-line, your signature stays at the bottom).&lt;br /&gt;
# If you want to add a person as a one-time cc or bcc, then do that in the applicable fields&lt;br /&gt;
#When you are ready to send your reply (or add your comment), click &amp;quot;Update Ticket&amp;quot; and your reply will be sent and will show in the ticket history&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; The reply box is exactly the same for reply or comment except it will be pink if you are replying. If you want to change your reply to a comment (or vice versa) on the right-hand side of the screen there is a drop-down menu and you can change whether the message you are writing is a reply or a comment. The color of the text area will change accordingly.&lt;br /&gt;
[[file:Reply-vs-comment.png]]&lt;br /&gt;
==Creating a Ticket/Emailing Out==&lt;br /&gt;
[[File:How to send emails.png|845x845px]]&lt;br /&gt;
==Bulk Update==&lt;br /&gt;
To do a bulk update (&#039;&#039;&#039;most useful for deleting spam&#039;&#039;&#039;):&lt;br /&gt;
#From the landing page, click on the queue you want to update (right-hand side of the screen)&lt;br /&gt;
#In the upper-right corner, click on &#039;&#039;&#039;Bulk Update&#039;&#039;&#039;&lt;br /&gt;
#Uncheck the messages you want to leave alone, or use the &#039;&#039;&#039;Clear All&#039;&#039;&#039; button at the bottom if that&#039;s faster.&lt;br /&gt;
#Once you have only the messages checked that you want to update, scroll to the bottom&lt;br /&gt;
#In the form at the bottom make the changes that you want to apply to all the messages checked. To set them to &amp;quot;deleted,&amp;quot; you pull down the drop-down next to &#039;&#039;&#039;Make Status&#039;&#039;&#039; and choose deleted.&lt;br /&gt;
#Once you have filled the form with all the changes you want to make, click &#039;&#039;&#039;Update.&#039;&#039;&#039;&lt;br /&gt;
You can also use Bulk Update to merge tickets (see below) or do many other maintenance tasks. Deleting is the most common.&lt;br /&gt;
&lt;br /&gt;
[[file:Bulk_Update.gif]]&lt;br /&gt;
==Updating a Ticket==&lt;br /&gt;
Once you are in a ticket you will see a header with all sorts of information you can change. &#039;&#039;&#039;Every section had things you can modify by clicking on its header.&#039;&#039;&#039;&lt;br /&gt;
So, if you want to update who owns the ticket and whether it&#039;s open/closed, you can click on &#039;&#039;&#039;The Basics&#039;&#039;&#039; and update those things from there. &#039;&#039;&#039;If you have multiple queues&#039;&#039;&#039; you can change what queue the ticket is in from The Basics section, because people often send requests to the wrong email.&lt;br /&gt;
===Statuses===&lt;br /&gt;
&lt;br /&gt;
====Initial Phase (search &amp;lt;code&amp;gt;__initial__&amp;lt;/code&amp;gt;) ====&lt;br /&gt;
The ticket is new and hasn&#039;t yet been reviewed by department staff.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;triage&#039;&#039;&#039;&amp;lt;/code&amp;gt; The initial status for tickets created via email. These tickets are waiting for triage, and may be spam.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;new&#039;&#039;&#039;&amp;lt;/code&amp;gt; The ticket has been triaged and is not spam, but has not yet been reviewed by department staff.&lt;br /&gt;
&lt;br /&gt;
====Active Phase (search &amp;lt;code&amp;gt;__active__&amp;lt;/code&amp;gt;)====&lt;br /&gt;
The ticket has been reviewed by a staffer at least once and is actively being worked on.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;review&#039;&#039;&#039;&amp;lt;/code&amp;gt; Something has happened (usually a reply) and the ticket needs the attention of a staffer.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;working&#039;&#039;&#039;&amp;lt;/code&amp;gt; The ticket has been reviewed, but the Owner still needs to reply. This should only be set by the ticket owner, and indicates that they&#039;re working on a reply and so it doesn&#039;t need to be reviewed by anyone else.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;waiting&#039;&#039;&#039;&amp;lt;/code&amp;gt; We&#039;re waiting for the Requestor to reply. No action is needed.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;timeout&#039;&#039;&#039;&amp;lt;/code&amp;gt; The ticket was &amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;, but the Requestor hasn&#039;t responded for too long. Either send a reminder or set to &amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;hold&#039;&#039;&#039;&amp;lt;/code&amp;gt; No one needs to do anything, but we don&#039;t want the ticket to be closed for some reason.&lt;br /&gt;
====Inactive Phase (search &amp;lt;code&amp;gt;__inactive__&amp;lt;/code&amp;gt;)====&lt;br /&gt;
The ticket does not require more work and should not normally be shown. Inactive tickets can still be found via the search system.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;resolved&#039;&#039;&#039;&amp;lt;/code&amp;gt; The Requestor&#039;s objective has been achieved and the ticket is closed.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;rejected&#039;&#039;&#039;&amp;lt;/code&amp;gt; We declined to do what the Requestor wanted and the ticket is closed.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;abandoned&#039;&#039;&#039;&amp;lt;/code&amp;gt; The Requestor took too long to respond and we gave up, so the ticket is closed.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;deleted&#039;&#039;&#039;&amp;lt;/code&amp;gt; The ticket isn&#039;t spam, but we want it to go away and there&#039;s no reason to keep it as a permanent record. This will be used most often for automated notifications from various systems. Tickets in the &amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt; status aren&#039;t actually deleted immediately: they stick around for at least 30 days before being shredded.&lt;br /&gt;
*&amp;lt;code&amp;gt;&#039;&#039;&#039;spam&#039;&#039;&#039;&amp;lt;/code&amp;gt; The ticket is spam and should go away. Tickets marked spam will be kept for at least 30 days, then used to train the spam filter and shredded.&lt;br /&gt;
&lt;br /&gt;
==Merging Tickets==&lt;br /&gt;
Sometimes the way someone replies to a thread opens a new ticket. Sometimes people email multiple times. Sometimes you just need to merge everything together. &lt;br /&gt;
&lt;br /&gt;
If you have two or more tickets that are really all part of the same thread then they should be merged into the same ticket. Luckily, merging is really easy (a little TOO easy).&lt;br /&gt;
===Merging One Ticket===&lt;br /&gt;
#In the ticket view click on &amp;quot;Links&amp;quot;&lt;br /&gt;
#Fill out the Merge Into field the bottom&lt;br /&gt;
#Click Save Changes&lt;br /&gt;
The ticket is now merged.&lt;br /&gt;
===Merging by Bulk Update===&lt;br /&gt;
The way you merge tickets is:&lt;br /&gt;
#Determine the id number of the main ticket you want to merge into.&lt;br /&gt;
#Go to bulk update for that queue and select the other ticket(s) you want to merge&lt;br /&gt;
#Scroll to the bottom and enter the id number of the main ticket&lt;br /&gt;
#Click Update.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:RT_Merge.png]]&lt;br /&gt;
&lt;br /&gt;
You should now have the whole thread in one.&lt;br /&gt;
Notice that it warns that the process is not reversible, so don&#039;t mess it up!&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CAUTION: If you do any more bulk updating RT will continue to merge tickets until you either navigate to another page or clear out the merge field!&#039;&#039;&#039;&lt;br /&gt;
==For the Admin==&lt;br /&gt;
===Create a Privileged User===&lt;br /&gt;
#Admin-&amp;gt;Users-&amp;gt;Select&lt;br /&gt;
#Put user in the go to user box.&lt;br /&gt;
#*If the user does not exist, it needs to be created. So you can create the user by sending them an email from RT letting them know they can log into RT. It&#039;s freaking magic!&lt;br /&gt;
#Open the user account&lt;br /&gt;
#Check the box to make the user a privileged user&lt;br /&gt;
#Save Changes at the bottom&lt;br /&gt;
===Add a user to a queue===&lt;br /&gt;
#Admin-&amp;gt;Queues-&amp;gt;Select&lt;br /&gt;
#Select the queue&lt;br /&gt;
#Click &amp;quot;Watchers&amp;quot;&lt;br /&gt;
#enter the user&#039;s name in the &amp;quot;Find People whose&amp;quot; box and hit Go - The user will show up in the lower right area&lt;br /&gt;
#Select &amp;quot;AdminCC&amp;quot;&lt;br /&gt;
#Click &amp;quot;Save Changes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===Merging users where the good email is on the account not connected to BACON===&lt;br /&gt;
This is a common but really, really annoying condition where RT will will not email to the BACON email because the BACON account is already linked to a different email. It is common when people change their email address, though. &lt;br /&gt;
&lt;br /&gt;
====Beta&#039;s Method====&lt;br /&gt;
I don&#039;t know if this is the best way but here&#039;s how I&#039;m handling it on an old ticket and a way that Sammich seems to believe will work. &lt;br /&gt;
&lt;br /&gt;
#Copy good and bad emails to a third location like notepad so I have them safe for this process. I like to be very clear in my notes &amp;quot;good email: (email)&amp;quot; and &amp;quot;bad email:(email)&amp;quot; along with links to each user so if I messed up I had all the information still available.&lt;br /&gt;
#On the bad account, set the email address (and possibly the username if it&#039;s the same as the email address) to something unique but bogus. I used &amp;quot;x@gmail.com&amp;quot; because the email in question was @gmail and it was temporary and easy.&lt;br /&gt;
#On the good account, set the email address to what you want it to be: the &amp;quot;good&amp;quot; email address&lt;br /&gt;
#Save&lt;br /&gt;
#On the bad account, set the email address to what the good account use to have: the &amp;quot;bad&amp;quot; email address&lt;br /&gt;
#Save&lt;br /&gt;
#Merge the &amp;quot;bad&amp;quot; user into the &amp;quot;good&amp;quot; user&lt;br /&gt;
&lt;br /&gt;
====Sammich&#039;s Method/note====&lt;br /&gt;
&amp;lt;blockquote&amp;gt;What I did is change the non-BACON-linked account with the new email to have no email, change the BACON-linked account to the correct email, and then merge the non-BACON account into the BACON account. If they&#039;re still going to use the old address you&#039;d either need to swap the addresses as you said, or create a new account for the old email and immediately merge it into their main account.&amp;lt;/blockquote&amp;gt;&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1758</id>
		<title>RT</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=RT&amp;diff=1758"/>
		<updated>2024-09-24T02:53:59Z</updated>

		<summary type="html">&lt;p&gt;Beta: added signature format and example&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Procedures]][[Category:Third Party Software]]&lt;br /&gt;
==Request Tracker==&lt;br /&gt;
RT (Request Tracker) is the ticketing system the con uses to handle email requests. As of 2016, &#039;&#039;&#039;all&#039;&#039;&#039; departmental emails are handled in RT. &lt;br /&gt;
&lt;br /&gt;
The best way to think of RT is like a really fancy group email system. Queues are the group email boxes. Multiple people can see and handle emails, and everyone who is involved with that box gets updated on everything going on so that everyone is on the same page.&lt;br /&gt;
==Video Tutorials==&lt;br /&gt;
Beta made a four-part video tutorial series, which is posted on our YouTube:&lt;br /&gt;
https://www.youtube.com/playlist?list=PLnJMQShIVjsl4XuTJJ4bPEYWDJJowhEN0&lt;br /&gt;
==Logging in ==&lt;br /&gt;
You can access RT from https://tickets.snafucon.com/&#039;&#039;&#039;.&#039;&#039;&#039; Your account is linked to [[BACON]] so log in with your current username and password. However, you will need to have privileges set up by the admin or you will only be able to see your previous tickets (if any) but not actually be able to see or answer any from the queue.&lt;br /&gt;
== Setting your Signature ==&lt;br /&gt;
When logged in: &lt;br /&gt;
# Hover over &amp;quot;Logged in as {you}&amp;quot;&lt;br /&gt;
# Hover over Settings&lt;br /&gt;
# Click &amp;quot;About Me&amp;quot;&lt;br /&gt;
# Your signature box is on the lower left. Edit as you see fit.&lt;br /&gt;
# Click &amp;quot;Save Preferences&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Signature Format ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;{Your Name}&lt;br /&gt;
&lt;br /&gt;
{Your Title or Department, as relevant}&lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite!&lt;br /&gt;
&lt;br /&gt;
https://snafucon.com&lt;br /&gt;
&lt;br /&gt;
{Optional relevant message}&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Example Signature ===&lt;br /&gt;
&amp;lt;blockquote&amp;gt;Beta&lt;br /&gt;
&lt;br /&gt;
SNAFU Con Human Resources &lt;br /&gt;
&lt;br /&gt;
Sierra Nevada Anime Fans Unite! &lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;https://snafucon.com&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Apply now! &amp;lt;nowiki&amp;gt;https://register.snafucon.com/staff/apply/&amp;lt;/nowiki&amp;gt;&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Queues==&lt;br /&gt;
Most users will only have one Queue, but some users will have multiple ones. The easiest way to navigate RT is by queue. The Queues you have access to are listed on the right-hand side of the screen under &amp;quot;Quick Search.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Click on the queue name to see all the tickets in a queue.&lt;br /&gt;
==Reply/Comment to a Ticket==&lt;br /&gt;
When you reply to a ticket it is sent to all of the people who administer the queue that it is in, and the requester (the person who sent the email in the first place.)&lt;br /&gt;
&lt;br /&gt;
When you comment on a ticket, it is only sent to the people who administer the queue.&lt;br /&gt;
&lt;br /&gt;
There are two ways of replying to and commenting on tickets. &lt;br /&gt;
===Reply by Email ===&lt;br /&gt;
You should only reply by email if you aren&#039;t closing or resolving the ticket. &#039;&#039;&#039;You can not resolve the ticket by email.&#039;&#039;&#039;&lt;br /&gt;
#Simply respond to the email that was sent to you.&lt;br /&gt;
Notice that the email you&#039;re sending goes back to the queue email. So, if you&#039;re responding to an email that originally went to [[/cdn-cgi/l/email-protection|[email protected]]], then the email you send will also go to [[/cdn-cgi/l/email-protection|[email protected]]] It is important that you do not alter the [SNAFU #(number)] part of the subject. RT will look at the subject to put the reply in the right ticket. &lt;br /&gt;
&lt;br /&gt;
The information that is added to the beginning of the email you received (the ticket information with Queue info and Ticket URL, etc.) &#039;&#039;&#039;WILL be included in your email if you don&#039;t delete it&#039;&#039;&#039;. It is up to you if you want that information in your email, but it should probably be removed before sending to minimize confusion.&lt;br /&gt;
===Comment by Email===&lt;br /&gt;
Comment by replying and changing the email to (queue email)[[/cdn-cgi/l/email-protection|[email protected]]] snafucon.com&lt;br /&gt;
So if the queue email was registration, you can comment by sending an email to [[/cdn-cgi/l/email-protection|[email protected]]]&lt;br /&gt;
&lt;br /&gt;
As before, keep the [SNAFU #(number)] part of subject the same so RT can route your comment correctly. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Reply/Comment by Logging In===&lt;br /&gt;
To reply to a ticket you need to get into a ticket to view it. You can click on a ticket from your dashboard, or from your queue.&lt;br /&gt;
#To reply/comment to the ticket, scroll down to the &#039;&#039;&#039;History&#039;&#039;&#039; section. You can view all history for this ticket (emails in and out).&lt;br /&gt;
#Click Reply or Comment [[File:History.png]]&lt;br /&gt;
#If you are the first reply, on the right-hand side you may want to update the &#039;&#039;&#039;Status to Open&#039;&#039;&#039; and the &#039;&#039;&#039;Owner to you&#039;&#039;&#039;. RT should update it for you after your reply if you don&#039;t make any settings. &#039;&#039;&#039;If you are closing the ticket&#039;&#039;&#039; you will want to change the status to &#039;&#039;&#039;resolved&#039;&#039;&#039; (or rejected as applicable). [[file:Ticket and Transactions.gif]]&lt;br /&gt;
#Type your reply in the box (if you have one set up, your signature is automatically added to the end of the message - if you are replying at the top of the message make sure your signature is at the top. If you are replying in-line, your signature stays at the bottom).&lt;br /&gt;
# If you want to add a person as a one-time cc or bcc, then do that in the applicable fields&lt;br /&gt;
#When you are ready to send your reply (or add your comment), click &amp;quot;Update Ticket&amp;quot; and your reply will be sent and will show in the ticket history&lt;br /&gt;
&#039;&#039;&#039;NOTE:&#039;&#039;&#039; The reply box is exactly the same for reply or comment except it will be pink if you are replying. If you want to change your reply to a comment (or vice versa) on the right-hand side of the screen there is a drop-down menu and you can change whether the message you are writing is a reply or a comment. The color of the text area will change accordingly.&lt;br /&gt;
[[file:Reply-vs-comment.png]]&lt;br /&gt;
==Creating a Ticket/Emailing Out==&lt;br /&gt;
[[File:How to send emails.png|845x845px]]&lt;br /&gt;
==Bulk Update==&lt;br /&gt;
To do a bulk update (&#039;&#039;&#039;most useful for deleting spam&#039;&#039;&#039;):&lt;br /&gt;
#From the landing page, click on the queue you want to update (right-hand side of the screen)&lt;br /&gt;
#In the upper-right corner, click on &#039;&#039;&#039;Bulk Update&#039;&#039;&#039;&lt;br /&gt;
#Uncheck the messages you want to leave alone, or use the &#039;&#039;&#039;Clear All&#039;&#039;&#039; button at the bottom if that&#039;s faster.&lt;br /&gt;
#Once you have only the messages checked that you want to update, scroll to the bottom&lt;br /&gt;
#In the form at the bottom make the changes that you want to apply to all the messages checked. To set them to &amp;quot;deleted,&amp;quot; you pull down the drop-down next to &#039;&#039;&#039;Make Status&#039;&#039;&#039; and choose deleted.&lt;br /&gt;
#Once you have filled the form with all the changes you want to make, click &#039;&#039;&#039;Update.&#039;&#039;&#039;&lt;br /&gt;
You can also use Bulk Update to merge tickets (see below) or do many other maintenance tasks. Deleting is the most common.&lt;br /&gt;
&lt;br /&gt;
[[file:Bulk_Update.gif]]&lt;br /&gt;
==Updating a Ticket==&lt;br /&gt;
Once you are in a ticket you will see a header with all sorts of information you can change. &#039;&#039;&#039;Every section had things you can modify by clicking on its header.&#039;&#039;&#039;&lt;br /&gt;
So, if you want to update who owns the ticket and whether it&#039;s open/closed, you can click on &#039;&#039;&#039;The Basics&#039;&#039;&#039; and update those things from there. &#039;&#039;&#039;If you have multiple queues&#039;&#039;&#039; you can change what queue the ticket is in from The Basics section, because people often send requests to the wrong email.&lt;br /&gt;
===Statuses===&lt;br /&gt;
;Initial Phase (search &amp;lt;code&amp;gt;__initial__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket is new and hasn&#039;t yet been reviewed by department staff.&lt;br /&gt;
:;&amp;lt;code&amp;gt;triage&amp;lt;/code&amp;gt;&lt;br /&gt;
::The initial status for tickets created via email. These tickets are waiting for triage, and may be spam.&lt;br /&gt;
:;&amp;lt;code&amp;gt;new&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket has been triaged and is not spam, but has not yet been reviewed by department staff.&lt;br /&gt;
:&lt;br /&gt;
;Active Phase (search &amp;lt;code&amp;gt;__active__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket has been reviewed by a staffer at least once and is actively being worked on.&lt;br /&gt;
:;&amp;lt;code&amp;gt;review&amp;lt;/code&amp;gt;&lt;br /&gt;
::Something has happened (usually a reply) and the ticket needs the attention of a staffer.&lt;br /&gt;
:;&amp;lt;code&amp;gt;working&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket has been reviewed, but the Owner still needs to reply. This should only be set by the ticket owner, and indicates that they&#039;re working on a reply and so it doesn&#039;t need to be reviewed by anyone else.&lt;br /&gt;
:;&amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;&lt;br /&gt;
::We&#039;re waiting for the Requestor to reply. No action is needed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;timeout&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket was &amp;lt;code&amp;gt;waiting&amp;lt;/code&amp;gt;, but the Requestor hasn&#039;t responded for too long. Either send a reminder or set to &amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;.&lt;br /&gt;
:;&amp;lt;code&amp;gt;hold&amp;lt;/code&amp;gt;&lt;br /&gt;
::No one needs to do anything, but we don&#039;t want the ticket to be closed for some reason.&lt;br /&gt;
:&lt;br /&gt;
;Inactive Phase (search &amp;lt;code&amp;gt;__inactive__&amp;lt;/code&amp;gt;)&lt;br /&gt;
:The ticket does not require more work and should not normally be shown. Inactive tickets can still be found via the search system.&lt;br /&gt;
:;&amp;lt;code&amp;gt;resolved&amp;lt;/code&amp;gt;&lt;br /&gt;
::The Requestor&#039;s objective has been achieved and the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;rejected&amp;lt;/code&amp;gt;&lt;br /&gt;
::We declined to do what the Requestor wanted and the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;abandoned&amp;lt;/code&amp;gt;&lt;br /&gt;
::The Requestor took too long to respond and we gave up, so the ticket is closed.&lt;br /&gt;
:;&amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket isn&#039;t spam, but we want it to go away and there&#039;s no reason to keep it as a permanent record. This will be used most often for automated notifications from various systems. Tickets in the &amp;lt;code&amp;gt;deleted&amp;lt;/code&amp;gt; status aren&#039;t actually deleted immediately: they stick around for at least 30 days before being shredded.&lt;br /&gt;
:;&amp;lt;code&amp;gt;spam&amp;lt;/code&amp;gt;&lt;br /&gt;
::The ticket is spam and should go away. Tickets marked spam will be kept for at least 30 days, then used to train the spam filter and shredded.&lt;br /&gt;
==Merging Tickets==&lt;br /&gt;
Sometimes the way someone replies to a thread opens a new ticket. Sometimes people email multiple times. Sometimes you just need to merge everything together. &lt;br /&gt;
&lt;br /&gt;
If you have two or more tickets that are really all part of the same thread then they should be merged into the same ticket. Luckily, merging is really easy (a little TOO easy).&lt;br /&gt;
===Merging One Ticket===&lt;br /&gt;
#In the ticket view click on &amp;quot;Links&amp;quot;&lt;br /&gt;
#Fill out the Merge Into field the bottom&lt;br /&gt;
#Click Save Changes&lt;br /&gt;
The ticket is now merged.&lt;br /&gt;
===Merging by Bulk Update===&lt;br /&gt;
The way you merge tickets is:&lt;br /&gt;
#Determine the id number of the main ticket you want to merge into.&lt;br /&gt;
#Go to bulk update for that queue and select the other ticket(s) you want to merge&lt;br /&gt;
#Scroll to the bottom and enter the id number of the main ticket&lt;br /&gt;
#Click Update.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:RT_Merge.png]]&lt;br /&gt;
&lt;br /&gt;
You should now have the whole thread in one.&lt;br /&gt;
Notice that it warns that the process is not reversible, so don&#039;t mess it up!&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CAUTION: If you do any more bulk updating RT will continue to merge tickets until you either navigate to another page or clear out the merge field!&#039;&#039;&#039;&lt;br /&gt;
==For the Admin==&lt;br /&gt;
===Create a Privileged User===&lt;br /&gt;
#Admin-&amp;gt;Users-&amp;gt;Select&lt;br /&gt;
#Put user in the go to user box.&lt;br /&gt;
#*If the user does not exist, it needs to be created. So you can create the user by sending them an email from RT letting them know they can log into RT. It&#039;s freaking magic!&lt;br /&gt;
#Open the user account&lt;br /&gt;
# Check the box to make the user a privileged user&lt;br /&gt;
# Save Changes at the bottom&lt;br /&gt;
===Add a user to a queue===&lt;br /&gt;
#Admin-&amp;gt;Queues-&amp;gt;Select&lt;br /&gt;
#Select the queue&lt;br /&gt;
# Click &amp;quot;Watchers&amp;quot;&lt;br /&gt;
# enter the user&#039;s name in the &amp;quot;Find People whose&amp;quot; box and hit Go - The user will show up in the lower right area&lt;br /&gt;
#Select &amp;quot;AdminCC&amp;quot;&lt;br /&gt;
#Click &amp;quot;Save Changes&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Merging users where the good email is on the account not connected to BACON ===&lt;br /&gt;
This is a common but really, really annoying condition where RT will will not email to the BACON email because the BACON account is already linked to a different email. It is common when people change their email address, though. &lt;br /&gt;
&lt;br /&gt;
==== Beta&#039;s Method ====&lt;br /&gt;
I don&#039;t know if this is the best way but here&#039;s how I&#039;m handling it on an old ticket and a way that Sammich seems to believe will work.&lt;br /&gt;
&lt;br /&gt;
# Copy good and bad emails to a third location like notepad so I have them safe for this process. I like to be very clear in my notes &amp;quot;good email: (email)&amp;quot; and &amp;quot;bad email:(email)&amp;quot; along with links to each user so if I messed up I had all the information still available.&lt;br /&gt;
# On the bad account, set the email address (and possibly the username if it&#039;s the same as the email address) to something unique but bogus. I used &amp;quot;x@gmail.com&amp;quot; because the email in question was @gmail and it was temporary and easy. &lt;br /&gt;
# On the good account, set the email address to what you want it to be: the &amp;quot;good&amp;quot; email address&lt;br /&gt;
# Save&lt;br /&gt;
# On the bad account, set the email address to what the good account use to have: the &amp;quot;bad&amp;quot; email address&lt;br /&gt;
# Save&lt;br /&gt;
# Merge the &amp;quot;bad&amp;quot; user into the &amp;quot;good&amp;quot; user&lt;br /&gt;
&lt;br /&gt;
==== Sammich&#039;s Method/note ====&lt;br /&gt;
&amp;lt;blockquote&amp;gt;What I did is change the non-BACON-linked account with the new email to have no email, change the BACON-linked account to the correct email, and then merge the non-BACON account into the BACON account. If they&#039;re still going to use the old address you&#039;d either need to swap the addresses as you said, or create a new account for the old email and immediately merge it into their main account.&amp;lt;/blockquote&amp;gt;&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
	<entry>
		<id>https://wiki.snafucon.com/mw/index.php?title=Dorms&amp;diff=1757</id>
		<title>Dorms</title>
		<link rel="alternate" type="text/html" href="https://wiki.snafucon.com/mw/index.php?title=Dorms&amp;diff=1757"/>
		<updated>2024-09-22T00:32:44Z</updated>

		<summary type="html">&lt;p&gt;Beta: Also don’t sleep in your car&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Staff Dorms / Housing ===&lt;br /&gt;
SNAFU Con does not yet have the budget to outright purchase hotel rooms for the staff. However, we are able to offer a discounted rate for the staff, and group the staff in rooms.&lt;br /&gt;
===Eligibility===&lt;br /&gt;
If you are a staff member you are eligible to use the staff dorms. We also occasionally have special cases stay in the staff dorms.&lt;br /&gt;
&lt;br /&gt;
We do not offer this to volunteers, you must have full staff status.&lt;br /&gt;
&lt;br /&gt;
If you are removed as staff for any reason, you will no longer be eligible for the staff dorms. If this happens during the convention itself it is up to the discretion of the convention chairs as to whether you may continue to stay in the dorms. &lt;br /&gt;
&lt;br /&gt;
Refund may only be given if a staff member cancels or is removed from the dorms earlier than 1 week before the convention starts. After that point, refund is increasingly unlikely, but is up to the discretion of the convention chairs.&lt;br /&gt;
===Placements===&lt;br /&gt;
We group staff together by gender. &lt;br /&gt;
&lt;br /&gt;
We group staff up to 4 in a single room. There are two beds in a room. It is up to the members of the room to determine who gets beds, who shares beds, and who sleeps on the floor. You’re adults – work it out. &lt;br /&gt;
&lt;br /&gt;
Generally we do not let staff choose what room they will be in or who they will be with. However, requests to be housed with a certain staff member or to *not* be housed with a certain staff member will be considered. We may not be able to accommodate all requests.&lt;br /&gt;
&lt;br /&gt;
A staff member may pay for all four person slots and stay with their significant other or family at the staff dorm rates. Other members of the room need not be staff. One must take and pay for all four person-slots to be able to do this. If you do take a full room, you will likely have to check in and out your own room (it will be determined immediately before the convention). &lt;br /&gt;
===Check In, Keys===&lt;br /&gt;
Beta checks in the staff rooms and distributes keys. Beta has a key for each room and might periodically check on the room. If you lose your key, Beta will be able to get another one.&lt;br /&gt;
&lt;br /&gt;
If a person has paid for all four slots, they might have to check in their own room (this will be determined immediately before the convention). The company owners can get into any room in our room block, and still might periodically check in on that room.&lt;br /&gt;
=== Check Out ===&lt;br /&gt;
If the room is booked for longer than you are staying, you can just leave when you have the chance at any point that morning. If the room is booked until the morning you&#039;re planning to leave, you need to be completely out by 11am.&lt;br /&gt;
===Rates===&lt;br /&gt;
* 2015-2019 the rate was $15/person/night. &lt;br /&gt;
* 2021 was going to be $25 but due to a misquote it became $20/person/night. &lt;br /&gt;
* 2022+ is $25/person/night.&lt;br /&gt;
If you truly cannot afford the current rate, please contact us anyway. We have allowed staff to stay in the dorms for lesser rates up to and including $0 because they just couldn’t afford anything and would have been sleeping under tables otherwise. Please be honest about what you can afford.&lt;br /&gt;
===How To===&lt;br /&gt;
At least 1 month before con (ASAP), PM Beta in chat or via email and let her know that you want to be in the staff dorms for that year. Please include what nights you need. Be as clear as possible. It is recommended to state when you will need the room and what morning you are leaving. Eg: “Need a room starting Thursday night and leaving Sunday morning.”&lt;br /&gt;
===Special At-Con Situations===&lt;br /&gt;
It is up to you to plan how you sleep and shower during con. However, if you find yourself without a place to sleep or shower, please contact Beta and we might be able to temporarily accommodate you. &lt;br /&gt;
&lt;br /&gt;
We sometimes have extra dorm space, and we often have a non-committed room that we can allow people to use temporarily for a nap or a shower. We can’t promise that we can help you, but please reach out to us and we will do what we can. &lt;br /&gt;
&lt;br /&gt;
Please do not sleep under tables or in your car. =(&lt;br /&gt;
=== How to Pay ===&lt;br /&gt;
Bring cash or a check to con. Ideally put it in an unsealed envelope with your name and the amount on it and the word &amp;quot;Dorms.&amp;quot; We will verify the money at con and put the envelope away. It helps me with the books post-con to keep the payment separate. &lt;br /&gt;
&lt;br /&gt;
The reason we do cash/check is because just about any other method will cost us in processor fees and we&#039;re already losing money on this deal. &lt;br /&gt;
===VIP Eligibility===&lt;br /&gt;
You do not receive VIP status if you use the staff dorms. You must reserve your own room through our hotel link if you want VIP status.&lt;/div&gt;</summary>
		<author><name>Beta</name></author>
	</entry>
</feed>