SNAFU Con Wiki - User contributions [en]

My Emergency Is (FAQ)

2025-11-02T01:49:46Z

Tainsouvra: Update for RSCC info.

For emergencies and "emergencies" of all kinds. Most important at the top, please.

== Medical Emergency of any kind ==

* Medical emergency should call 911 and then call security directly at 775-229-7629. They will assist if able and work to direct medical responders where they can.
* @Hot Coffee in discord. Preferably Rovers head will contact emergency, but use your best judgement.

== Fight, Shoplifting, any other reason to call police or 911 ==

* @Hot Coffee in discord. Rovers head will contact security.
* Regarding shoplifting or a fight notify venue security first (775-229-7629). If needed they will be in direct contact with RPD.

== I need something moved ==
Ping @Logistics Staff in Discord. Can use #staff channel.

Main Stage

2025-08-25T20:04:46Z

Tainsouvra: /* Literal Stage */

[[Category:Departments]][[Category:Policies]]
Main Stage crew operates during the convention. We are there to entertain and inform the audience. At no time should the stage be quiet with nothing on the projector. If there are no activities planned or going on, play some music or videos.
Main Stage crew is there to relay announcement to the convention. Announcements should be given to a person off stage, transcribed into writing, and then announced over the speakers. Some announcements do not need to be written, i.e. promote the vendor’s room before it closes in 10 minutes.
At no time should Main Stage crew touch or mess with Tech’s equipment, i.e. Speakers or projectors. The exception to this rule is unmuting microphones and other small things. When in doubt, ask tech.
== Requirements ==
*Be able to speak in front of crowds
*Know how to use a microphone
*Have the ability to get peoples attention when needed
*Interact with other Main Stage crew
== Responsibilities ==
# Assist panelist on main stage.
#*Inform people going on main stage about proper mic usage and the stage rules
# Relay important announcements
# Make sure there is something going on at all times
#*Entertain the crowd
#*If there is no crowd, get one
#*If you cannot get one, then play some music or videos
==Literal Stage==
2016: 40' Wide, 12' Deep

RSCC: 2' high (higher will cost much more money)
== Stage Rules ==
# Use stairs
# Max number of people (10-20?)
# PG (PG-13 after 10pm)
# No rough behavior
# Do not touch tech’s equipment
# Host is in control (Stage GOD)
# Tech can and will mute you if they deem it necessary.
# Only Main Stage staff and authorize personnel are allowed to use microphones.
# We have prizes!
== Filler Ideas ==
* Audience participation
** Games
*** Jan Ken Pon
*** Artist drawing competition(whiteboards)
*** Trivia
*** Ninja
** D&D (keep it PG)
** Improv games
* Videos
** AMVs
** Any approved anime (PG)
** Video game speed run
* Music
** Anime music
** Any approved music (ASCAP?)

Onboarding: Programming Director

2024-09-11T03:38:47Z

Tainsouvra: /* Marketing / Getting Panel Applications */

[[Category:Onboarding Plans]]
The Programming Director is responsible for overseeing the scheduling and execution of all convention panels and programming events. They coordinate with panelists, guests, and various teams to ensure smooth operations, including managing schedules, handling last-minute changes, and ensuring all programming aligns with the convention’s standards. Additionally, the director works closely with tech and guest liaison teams to address panelists' needs and ensure proper room setups and equipment.

== Software Access/Training Needed ==

* Reg.Works for managing the programming schedule and panelists.
** Note: Thomas (tjsomething) handles management and coding for Reg.Works, the Programming Director uses it to manage panel submissions and schedules.
* [[RT]] (Request Tracker) for handling inquiries, managing panelist communications, and processing guest panel submissions.
* BACON for administrative access related to panel and guest management.
* Wiki for updating procedures and adding relevant notes.
* Mailchimp (through collaboration with the marketing team) for programming-related communications, including sending blast emails.
* Discord (no access needed, but understanding how to navigate/communicate regarding programming)

== Tasks Needing Training ==

=== Pre-Con Tasks ===

==== Marketing / Getting Panel Applications ====

* How to collaborate with the social media team to draft and schedule posts for panelist applications.
* How to garner interest and encourage panelist applications
* How to create Mailchimp campaigns related to programming (See [[Copying A Mailchimp Campaign]]).
* Updating panel submission instructions or general programming information on the webpage (See [[Updating The Website Content]])

==== Handling Panelist Applications ====

* How to manage and approve panel submissions in Reg.Works.
** Complete before schedules are sent to print.
* How to decide whether or not to approve a panel submission
* How to use RT to communicate with panelists and guests about missing or incorrect information (See [[RT]]).
** How to reach out via RT for clarifications, corrections, and confirmations.
** How to differentiate 16+, 18+, and general audience ratings for panels and communicate these requirements to applicants who submit it under the wrong rating.
** How to handle very specific requests regarding time, location, etc. of submitted panels.

==== Creating/Editing theSchedule ====

* Putting events/panels into reg.works
* Coordinating the schedules of guests with events they need to be at
* Preventing back-to-back events for guests/panelists where possible

==== Panelist Communication ====
* How to ensure that panelist information (e.g., approval and scheduling) is sent out correctly through RT and Mailchimp.
* How to handle manual emails for panel confirmations and scheduling
* Ensuring you have received confirmation from panelists on their schedules.

=== At-Con Tasks ===

==== Programming Room Setup ====

* Making sure that rooms are unlocked/accessible at the appropriate times.
* Coordinating with tech and logistics staff to ensure panel rooms are appropriately laid out and equipped (e.g., projectors, sound systems).
** Physically verify panel setups are correct. Double check against panels running in the room for equipment requirements.

==== Panelist Check-In Procedures ====

* How to check in panelists and ensure they have any necessary materials.
* How to handle last-minute changes or issues with panelists (cancellations, substitutions)
* How to train volunteers on panel room management (counting rooms, flagging panelists with time notifications)
* How to train volunteers regarding feedback slips

==== On-Site Management ====

* Using Reg.Works for live scheduling changes and communication.
* Working with social media and main stage teams to ensure schedule changes are communicated appropriately.
* Managing and resolving programming issues in real-time, including scheduling conflicts or changes in room setups.
* Working with the volunteers department and helping as needed with watching doors/entry points, especially for 18+ panels.
* Working with guest liaisons to ensure guest panels are handled correctly and guests' needs are met.
* Managing feedback slips, data entry

=== Post-Con Tasks ===

==== Feedback and Follow-Up ====

* How to solicit and process feedback from panelists and guests using email, surveys, or post-con meetings.
* How to review programming feedback and provide recommendations for improvements to future conventions.
* Entering any feedback slips that didn't get handled at-con.

== Additional Responsibilities ==

==== Working with Development Team ====

* Collaborating with Thomas on updates or bug fixes for Reg.Works.
* Assisting in testing new Reg.Works features.

==== Guest Management ====

* Ensuring guest panels are prioritized and scheduled appropriately.
* Coordinating with the guest liaison team, or the guests directly, to handle guest panel scheduling, requirements, and last-minute changes.
** Ensuring that all guests have been scheduled for their contracted amount of panels

Onboarding: Programming Director

2024-09-11T02:33:52Z

Tainsouvra: /* Handling Panelist Applications */ s

[[Category:Onboarding Plans]]
The Programming Director is responsible for overseeing the scheduling and execution of all convention panels and programming events. They coordinate with panelists, guests, and various teams to ensure smooth operations, including managing schedules, handling last-minute changes, and ensuring all programming aligns with the convention’s standards. Additionally, the director works closely with tech and guest liaison teams to address panelists' needs and ensure proper room setups and equipment.

== Software Access/Training Needed ==

* Reg.Works for managing the programming schedule and panelists.
** Note: Thomas (tjsomething) handles management and coding for Reg.Works, the Programming Director uses it to manage panel submissions and schedules.
* [[RT]] (Request Tracker) for handling inquiries, managing panelist communications, and processing guest panel submissions.
* BACON for administrative access related to panel and guest management.
* Wiki for updating procedures and adding relevant notes.
* Mailchimp (through collaboration with the marketing team) for programming-related communications, including sending blast emails.
* Discord (no access needed, but understanding how to navigate/communicate regarding programming)

== Tasks Needing Training ==

=== Pre-Con Tasks ===

==== Marketing / Getting Panel Applications ====

* How to collaborate with the social media team to draft and schedule posts for panelist applications.
* How to garner interest and encourage panelist applications
* How to create Mailchimp campaigns related to programming (See [[Copying A Mailchimp Campaign]]).
* Updating panel submission instructions or general programming information on the webpage (See [[Updating The Website Content]])

==== Handling Panelist Applications ====

* How to manage and approve panel submissions in Reg.Works.
** Complete before schedules are sent to print.
* How to decide whether or not to approve a panel submission
* How to use RT to communicate with panelists and guests about missing or incorrect information (See [[RT]]).
** How to reach out via RT for clarifications, corrections, and confirmations.
** How to differentiate 16+, 18+, and general audience ratings for panels and communicate these requirements to applicants who submit it under the wrong rating.
** How to handle very specific requests regarding time, location, etc. of submitted panels.

==== Panelist Communication ====

* How to ensure that panelist information (e.g., approval and scheduling) is sent out correctly through RT and Mailchimp.
* How to handle manual emails for panel confirmations and scheduling.

=== At-Con Tasks ===

==== Programming Room Setup ====

* Coordinating with tech and logistics staff to ensure panel rooms are appropriately laid out and equipped (e.g., projectors, sound systems).
** Physically verify panel setups are correct. Double check against panels running in the room for equipment requirements.

==== Panelist Check-In Procedures ====

* How to check in panelists and ensure they have any necessary materials.
* How to handle last-minute changes or issues with panelists (cancellations, substitutions).
* How to train volunteers on panel room management (counting rooms, flagging panelists with time notifications)
* How to train volunteers regarding feedback slips

==== On-Site Management ====

* Using Reg.Works for live scheduling changes and communication.
* Working with social media and main stage teams to ensure schedule changes are communicated appropriately.
* Managing and resolving programming issues in real-time, including scheduling conflicts or changes in room setups.
* Working with guest liaisons to ensure guest panels are handled correctly and guests' needs are met.
* Managing feedback slips, data entry

=== Post-Con Tasks ===

==== Feedback and Follow-Up ====

* How to solicit and process feedback from panelists and guests using email, surveys, or post-con meetings.
* How to review programming feedback and provide recommendations for improvements to future conventions.
* Entering any feedback slips that didn't get handled at-con.

== Additional Responsibilities ==

==== Working with Development Team ====

* Collaborating with Thomas on updates or bug fixes for Reg.Works.
* Assisting in testing new Reg.Works features.

==== Guest Management ====

* Ensuring guest panels are prioritized and scheduled appropriately.
* Coordinating with the guest liaison team, or the guests directly, to handle guest panel scheduling, requirements, and last-minute changes.

2024 Meeting Notes

2024-08-13T04:58:49Z

Tainsouvra: /* General Meeting Logistics */

== Staff Meeting Summary 2024-06-22 ==

=== Convention Updates ===

* '''Convention Announcement:'''
** We're having a convention! The contract is signed with the '''Reno Sparks Convention Center''' for a '''Nov 1-3''' convention. We have the space from Wednesday to Monday.
* '''Website and Registration:'''
** Convention dates updated on the website.
** Additional updates needed.
** General registration expects to open by the end of the weekend.
** Staff registration will open alongside general registration, even without the staff contract being ready.
** Staff contract is being worked on by Natasha.
* '''Need for Staff:'''
** Emphasis on the need for more staff.
** Encouragement for current staff to recruit friends.

=== Staff Recruitment ===

* '''Introduction of New Staff Member:'''
** TheUltimateDragon (William) introduced as the new head of the game room.
** Plans to involve the local fighting game community, with 20 to 30 active members.

=== Department Updates ===

* '''Game Room Logistics:'''
** William plans to bring in his community for the game room.
** Discussion on the availability of consoles and other equipment. We may need to source consoles.
* '''Separation of Main Stage and Gaming Areas:'''
** Main stage and gaming areas will be separated at the new venue.
* '''Beta's Role Change:'''
** John has stepped down as vice chair and gaming head.
** Beta has stepped down as vice chair and is stepping back from some responsibilities.
** Beta's focus will largely be on continuous improvement and documentation to streamline processes.
** Tim is now a vice chair and will be more involved in ensuring tasks are completed.
* '''Recognition of Efforts:'''
** Cupcake Doll recognized for consistent efforts in keeping things moving.

=== Pricing and Budget ===

* '''Convention Pricing:'''
** Weekend passes likely $60.
** Individual day passes expected to be $30, with possible higher price for Saturday.
* '''Vendor Pricing:'''
** Vendor table prices will increase slightly.
* '''Prize Procurement:'''
** Discussion on handling prizes for the convention.
** Tighter budget than usual this year, need for smart procurement.

=== Marketing and Promotion ===

* '''Marketing Efforts:'''
** Urgent need to start marketing the convention.
** Plans to distribute business cards and possibly larger flyers or posters.
* '''RAGECON Presence:'''
** Potential for having a table at RAGECON to promote the convention.
** Discussion on staffing the table and badges.
* '''Community Engagement:'''
** Importance of engaging with the local community through various events.

=== Social Media and Streaming ===

* '''Social Media Activity:'''
** Current presence on Facebook and Twitter (X).
** Need to boost activity on these platforms.
* '''Streaming Ideas:'''
** Streaming tournaments and other events to generate hype.
** Use of Twitch and YouTube for streaming and promoting the convention.
* '''Social Media Management:'''
** Fae offered to help with social media posts and engagement.
** Discussion on using Social Pilot for automated posts, with manual posts for Instagram.

=== Venue and Logistics ===

* '''New Venue Details:'''
** New venue is the convention center, more expensive but possibly a better fit.
** Concerns about lighting at the new venue and potential solutions.
* '''Security Requirements:'''
** Need to hire ESI security, details still unclear.

=== Miscellaneous ===

* '''Communication and Collaboration:'''
** Encouragement for effective communication and collaboration.
** Importance of being proactive in managing tasks and responsibilities.

== Staff Meeting Summary 2024-07-14 ==

=== Welcome and Introduction ===

* The meeting was initiated to discuss updates and plans for SNAFU Con, emphasizing the importance of recruiting more staff.

=== Website and Marketing Updates ===

* The website is nearly ready for directing traffic, with social media updates to follow soon.
* Business card-sized flyers are ready, and 4x6 flyers are being prepared for distribution.
* Marketing efforts are expected to kick off in August. Flyers and posters will be distributed at local nerdy businesses.
* Posters will be available closer to the event, no later than the con book release.

=== Upcoming Conventions and Events ===

* A list of upcoming conventions and events was provided to schedule possible promotional efforts:
** August 16-18: GalaxyCon San Jose
** August 17-18: Con for a Cause (formerly Aerie-Con) in Reno
** August 30-Sept 1: SacAnime
** September 7-10: Kaboom Con in Carson City
** October 14-17: BLFC at GSR
** October 26-27: YumeConUSA in San Jose
** November 2-3: Reno Toy Con at GSR
* Additional local events and new shops were suggested as potential flyer distribution points.
** Kobold’s Keep in Reno
** New shop in Sparks called "The Coffer"
** Warhammer store at Summit
* Cosplay meetups and other geek clubs were identified as good opportunities for promotion.
** Local libraries often have anime and gaming clubs that could be reached out to for promotion.
** South Reno Library, which has regular Pokémon days for kids.
** Cosplay for Kindness, a group that runs various events in town and was suggested for potential collaboration.

=== Staff Recruitment and Contracts ===

* Emphasis on the prompt signing of staff contracts to avoid last year's issues.
* Encouragement for staff to recruit friends and acquaintances to join the team.
* Discussion on the contract checking process using the existing HR system. (We have to actually make phone calls again to catch stragglers.)

=== Venue and Layout Plans ===

* The new convention layout at the Reno-Sparks Convention Center was discussed, including the need for large signs to guide attendees.
* We have all of C, D and E rooms.
* Initial maps were shared, highlighting the layout of C and D halls and the ballroom for vendors and artists.
* Focus on controlling badge points and managing the flow of attendees.
** We expect to need 5 badge controlled spots

=== Food and Concessions ===

* Concerns were raised about the availability of substantial food options at the venue.
** If you have a request for the concessions stand, send it to Tim.
** Coordination with Aramark for concessions and the possibility of vendors providing snacks were discussed.

=== Merchants and Artist Contracts ===

* Merchant and artist contracts are in progress and will be opened soon.
* A first-come, first-serve approach was proposed for artist alley applications.
* Emphasis on adhering to city deadlines for paperwork submission.
** City deadline is now 30 days before con instead of the 15 day deadline we used to have.

=== Partnering with Local Organizations ===

* Plans to reach out to local professors, science museums, and other educational organizations for panel presentations and partnerships.
* Contact with the Discovery Museum for potential collaboration was initiated.

=== General Meeting Logistics ===

* At least one future in-person meeting will be held at libraries to facilitate face-to-face interactions. Possibly more.
* Potential venues for these meetings include South Valleys Library and Sparks Library.

=== Miscellaneous ===

* Updates on social media graphics and preparations for the convention were shared.
* A press release will be drafted following the guidelines on the SNAFU Con wiki.
* Reminder to be cautious about staff burnout and to maintain a balanced workload.

== Staff Meeting Summary - In Person Meeting 2024-08-10 ==

=== General Meeting Logistics ===

* '''Meeting Issues:'''
** Attendance was taken manually due to errors in logging into the system.

* '''Introductions:'''
** Staff members introduced themselves, their roles, and their previous experience with the convention.

=== Event Planning and Roles ===

* '''Staffing:'''
** There are several open positions that need to be filled.
** Current staff are encouraged to take on multiple roles due to the shortage.
** Beta is stepping back but will still assist with HR, graphics, documentation, and continual improvement.
** The chair is Tim, who will oversee various departments and tasks.
** Registration and contract signing for staff will be done online, with no in-person signings allowed.

* '''Convention Layout:'''
** Overview of the venue layout:
*** Artist Alley and Vendor spaces will be located in D1-D3 ballrooms.
*** E1-E3 for video gaming, E9-E10 for tabletop gaming.
*** Main stage, panels, cosplay, and manga library also mapped out.
** Discussions on the potential need for more lighting in certain rooms, particularly for the Artist Alley.
** A walkthrough is needs to be scheduled to assess lighting and other venue specifics.
** 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.

=== Programming and Features ===

* '''Gaming Room:'''
** William (Derp) is the new head of the gaming room and is planning a retro gaming corner.
** The retro gaming corner will feature classic consoles like PS2, SNES Classic, etc.
** A tournament is being planned, potentially requiring more PS5 consoles.
** Volunteers are needed to help with the gaming room.
** A spreadsheet may be created to track who is bringing what equipment (consoles, TVs, etc.).

* '''Artist Alley and Vendor Contracts:'''
** Artist Alley and Vendor space has been slightly reduced
** Contracts are almost ready, pending some final details.

* '''Cosplay:'''
** The main lobby area and ballroom lobby are potential spaces for cosplay meetups.
** Discussion on the benefits of high visibility areas for cosplay meetups.

=== Marketing and Outreach ===

* '''Marketing Initiatives:'''
** There is a strong need for increased marketing due to the new venue and the desire to attract a larger audience.
** Social media efforts need to ramp up, with plans to highlight artists, vendors, and panels.
** There is a call for everyone to contribute to marketing, especially on social media.
** Short science videos and other creative content ideas were discussed as potential marketing tools.
** Plans to advertise on local event pages, including Nevada Appeal and RGJ Events.
** Potential collaboration with other local events (e.g., toy fair, punk rock market) to cross-promote.

* '''Outreach to Other Communities:'''
** UNR (University of Nevada, Reno) clubs and groups are potential targets for outreach.
** Suggestions to connect with local businesses like Cap'n Games for retro gaming partnerships.
** Discussed using UNR’s radio station and event calendars for advertising.

=== Other Discussions ===

* '''Venue Logistics:'''
** Badge-controlled areas were discussed, and it's determined that certain doors may be monitored by ESI security.
** 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.

* '''Miscellaneous:'''
** Questions were raised about the availability and acquisition of CRTs (for retro gaming), with some potential leads mentioned.
** Mention of potential storage issues if the con were to acquire CRTs.

* '''Next Steps:'''
** Finalization of contracts and opening up vendor applications.
** Continued efforts in staff recruitment and training.
** Preparation for the next walkthrough of the venue.
** Further development of marketing strategies, including social media engagement and partnerships.

* '''Mingle Time:'''
** After the meeting, there was a designated time for staff to network and discuss roles and tasks further.

=== Closing Remarks ===

* The meeting concluded with an open call for any additional questions or ideas from the attendees.
* Those interested in specific roles or tasks were encouraged to speak with Tim or other department heads.

The meeting wrapped up with a reminder that continued collaboration and communication will be key as the convention date approaches.

Pipe and Drape

2023-11-06T01:52:29Z

Tainsouvra: /* 2023 Count */

[[Category:Purchasing]][[Category:Equipment]][[Category:Research]]
==2023 Count==
Reg:

* 16 pair pole 48+46.5"
* 8 crossbars 71/94/118 in, ~73 for storage
* 16 kraken bases

2x bags:

* 19 poles 96"
* 15 crossbars
* 19 EEI bases

==2014 Purchase==
[http://www.amazon.com/50ft-Wide-Drape-Black-Premier/dp/B00G2BDML0/ref=sr_1_1?s=arts-crafts&ie=UTF8&qid=1437018483&sr=1-1&keywords=Pipe+and+Drape Purchased from Amazon]

50ft long, 8ft high.

*5 rods
*6 posts
*6 plates
*15 premier black drape panels (60" x 95" or 5' x 7.9')

This was the cheapest pipe and drape solution in 2014.

==2016 Purchase==
===Pipe and Drape===
[http://www.amazon.com/50ft-Wide-Drape-Black-Premier/dp/B00G2BDML0/ref=sr_1_1?s=arts-crafts&ie=UTF8&qid=1437018483&sr=1-1&keywords=Pipe+and+Drape Purchased from Amazon] (same as 2014)

50ft long, 8ft high.

*5 rods
*6 posts
*6 plates
*15 premier black drape panels (60" x 95" or 5' x 7.9')

===Stanchions===
We bought 40 stanchions from StanchionDepot.com in 2016. Black post and bases with red retractable belts.

* '''EQCCPRO-BB''' Signature Series - Proline 40" High Retractable Belt Stanchion. Black Post black 2" wide belt with patented slow retract cassette with safety brake and locking end. 21lb 14" wide concrete filled base with black no-scuff base cover... $50
*'''EQCCPRO-CASS-R''' Signature Series Crowd Control Pro Replacement Cassette. Red 2' wide belt. $14.95

With tax, this worked out to $70.21/stanchion.

The stanchion carts Sam built us hold 20 stanchions each.

==Options==
We did not purchase anything this year?

The exact same thing available on Amazon is available through the [http://www.onlineeei.com/drapes.cfm#pipe-and-drape-quick-backdrop-kit supplier's site]. It's $738 after shipping through the manufacturer, vs $740 on Amazon.

[http://www.pipeanddrapeonline.com/ Pipe and Drape Online] Seems to have free shipping (temporarily?) and is a bit cheaper than Online EEI especially when shipping is considered (NOTE: The only reason it's cheaper is a sale "Save 10% off an order with a subtotal of $500.00 or more. *Offer excludes Clearance Items, skirts, clips, hangers, toppers, sign hooks, carts, storage bags, stanchions, and replacement base pins.
Valid from: 5/8/2014 - 12/31/2015").

==Fabric Panel ==
[http://bingbanners.com/fabric-banner/ Check out this] for a custom print panel (or several)
a 5x8 banner would be about $160

Pipe and Drape

2023-11-06T01:51:51Z

Tainsouvra: 2023 count

[[Category:Purchasing]][[Category:Equipment]][[Category:Research]]
==2023 Count==
Reg:

* 16 pair pole 48+46.5"
* 8 crossbars 71/94/118 in, ~73 for storage
* 19 EEI bases

2x bags:

* 19 poles 96"
* 15 crossbars
* 16 kraken bases

==2014 Purchase==
[http://www.amazon.com/50ft-Wide-Drape-Black-Premier/dp/B00G2BDML0/ref=sr_1_1?s=arts-crafts&ie=UTF8&qid=1437018483&sr=1-1&keywords=Pipe+and+Drape Purchased from Amazon]

50ft long, 8ft high.

*5 rods
*6 posts
*6 plates
*15 premier black drape panels (60" x 95" or 5' x 7.9')

This was the cheapest pipe and drape solution in 2014.

==2016 Purchase==
===Pipe and Drape===
[http://www.amazon.com/50ft-Wide-Drape-Black-Premier/dp/B00G2BDML0/ref=sr_1_1?s=arts-crafts&ie=UTF8&qid=1437018483&sr=1-1&keywords=Pipe+and+Drape Purchased from Amazon] (same as 2014)

50ft long, 8ft high.

*5 rods
*6 posts
*6 plates
*15 premier black drape panels (60" x 95" or 5' x 7.9')

===Stanchions===
We bought 40 stanchions from StanchionDepot.com in 2016. Black post and bases with red retractable belts.

* '''EQCCPRO-BB''' Signature Series - Proline 40" High Retractable Belt Stanchion. Black Post black 2" wide belt with patented slow retract cassette with safety brake and locking end. 21lb 14" wide concrete filled base with black no-scuff base cover... $50
*'''EQCCPRO-CASS-R''' Signature Series Crowd Control Pro Replacement Cassette. Red 2' wide belt. $14.95

With tax, this worked out to $70.21/stanchion.

The stanchion carts Sam built us hold 20 stanchions each.

==Options==
We did not purchase anything this year?

The exact same thing available on Amazon is available through the [http://www.onlineeei.com/drapes.cfm#pipe-and-drape-quick-backdrop-kit supplier's site]. It's $738 after shipping through the manufacturer, vs $740 on Amazon.

[http://www.pipeanddrapeonline.com/ Pipe and Drape Online] Seems to have free shipping (temporarily?) and is a bit cheaper than Online EEI especially when shipping is considered (NOTE: The only reason it's cheaper is a sale "Save 10% off an order with a subtotal of $500.00 or more. *Offer excludes Clearance Items, skirts, clips, hangers, toppers, sign hooks, carts, storage bags, stanchions, and replacement base pins.
Valid from: 5/8/2014 - 12/31/2015").

==Fabric Panel ==
[http://bingbanners.com/fabric-banner/ Check out this] for a custom print panel (or several)
a 5x8 banner would be about $160

RT

2023-09-03T02:04:19Z

Tainsouvra: fixed rt link

[[Category:Procedures]][[Category:Third Party Software]]
==Request Tracker==
RT (Request Tracker) is the ticketing system the con uses to handle email requests. As of 2016, '''all''' departmental emails are handled in RT.

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.
==Video Tutorials==
Beta made a four-part video tutorial series, which is posted on our YouTube:
https://www.youtube.com/playlist?list=PLnJMQShIVjsl4XuTJJ4bPEYWDJJowhEN0
==Logging in ==
You can access RT from https://tickets.snafucon.com/'''.''' 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.
== Setting your Signature ==
When logged in:
# Hover over "Logged in as {you}"
# Hover over Settings
# Click "About Me"
# Your signature box is on the lower left. Edit as you see fit.
# Click "Save Preferences"
==Queues==
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 "Quick Search."

Click on the queue name to see all the tickets in a queue.
==Reply/Comment to a Ticket==
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.)

When you comment on a ticket, it is only sent to the people who administer the queue.

There are two ways of replying to and commenting on tickets.
===Reply by Email ===
You should only reply by email if you aren't closing or resolving the ticket. '''You can not resolve the ticket by email.'''
#Simply respond to the email that was sent to you.
Notice that the email you're sending goes back to the queue email. So, if you'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.

The information that is added to the beginning of the email you received (the ticket information with Queue info and Ticket URL, etc.) '''WILL be included in your email if you don't delete it'''. It is up to you if you want that information in your email, but it should probably be removed before sending to minimize confusion.
===Comment by Email===
Comment by replying and changing the email to (queue email)[[/cdn-cgi/l/email-protection|[email protected]]] snafucon.com
So if the queue email was registration, you can comment by sending an email to [[/cdn-cgi/l/email-protection|[email protected]]]

As before, keep the [SNAFU #(number)] part of subject the same so RT can route your comment correctly.

===Reply/Comment by Logging In===
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.
#To reply/comment to the ticket, scroll down to the '''History''' section. You can view all history for this ticket (emails in and out).
#Click Reply or Comment [[File:History.png]]
#If you are the first reply, on the right-hand side you may want to update the '''Status to Open''' and the '''Owner to you'''. RT should update it for you after your reply if you don't make any settings. '''If you are closing the ticket''' you will want to change the status to '''resolved''' (or rejected as applicable). [[file:Ticket and Transactions.gif]]
#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).
# If you want to add a person as a one-time cc or bcc, then do that in the applicable fields
#When you are ready to send your reply (or add your comment), click "Update Ticket" and your reply will be sent and will show in the ticket history
'''NOTE:''' 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.
[[file:Reply-vs-comment.png]]
==Creating a Ticket/Emailing Out==
[[File:How to send emails.png|845x845px]]
==Bulk Update==
To do a bulk update ('''most useful for deleting spam'''):
#From the landing page, click on the queue you want to update (right-hand side of the screen)
#In the upper-right corner, click on '''Bulk Update'''
#Uncheck the messages you want to leave alone, or use the '''Clear All''' button at the bottom if that's faster.
#Once you have only the messages checked that you want to update, scroll to the bottom
#In the form at the bottom make the changes that you want to apply to all the messages checked. To set them to "deleted," you pull down the drop-down next to '''Make Status''' and choose deleted.
#Once you have filled the form with all the changes you want to make, click '''Update.'''
You can also use Bulk Update to merge tickets (see below) or do many other maintenance tasks. Deleting is the most common.

[[file:Bulk_Update.gif]]
==Updating a Ticket==
Once you are in a ticket you will see a header with all sorts of information you can change. '''Every section had things you can modify by clicking on its header.'''
So, if you want to update who owns the ticket and whether it's open/closed, you can click on '''The Basics''' and update those things from there. '''If you have multiple queues''' you can change what queue the ticket is in from The Basics section, because people often send requests to the wrong email.
===Statuses===
;Initial Phase (search <code>__initial__</code>)
:The ticket is new and hasn't yet been reviewed by department staff.
:;<code>triage</code>
::The initial status for tickets created via email. These tickets are waiting for triage, and may be spam.
:;<code>new</code>
::The ticket has been triaged and is not spam, but has not yet been reviewed by department staff.
:
;Active Phase (search <code>__active__</code>)
:The ticket has been reviewed by a staffer at least once and is actively being worked on.
:;<code>review</code>
::Something has happened (usually a reply) and the ticket needs the attention of a staffer.
:;<code>working</code>
::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're working on a reply and so it doesn't need to be reviewed by anyone else.
:;<code>waiting</code>
::We're waiting for the Requestor to reply. No action is needed.
:;<code>timeout</code>
::The ticket was <code>waiting</code>, but the Requestor hasn't responded for too long. Either send a reminder or set to <code>abandoned</code>.
:;<code>hold</code>
::No one needs to do anything, but we don't want the ticket to be closed for some reason.
:
;Inactive Phase (search <code>__inactive__</code>)
:The ticket does not require more work and should not normally be shown. Inactive tickets can still be found via the search system.
:;<code>resolved</code>
::The Requestor's objective has been achieved and the ticket is closed.
:;<code>rejected</code>
::We declined to do what the Requestor wanted and the ticket is closed.
:;<code>abandoned</code>
::The Requestor took too long to respond and we gave up, so the ticket is closed.
:;<code>deleted</code>
::The ticket isn't spam, but we want it to go away and there'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 <code>deleted</code> status aren't actually deleted immediately: they stick around for at least 30 days before being shredded.
:;<code>spam</code>
::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.
==Merging Tickets==
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.

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).
===Merging One Ticket===
#In the ticket view click on "Links"
#Fill out the Merge Into field the bottom
#Click Save Changes
The ticket is now merged.
===Merging by Bulk Update===
The way you merge tickets is:
#Determine the id number of the main ticket you want to merge into.
#Go to bulk update for that queue and select the other ticket(s) you want to merge
#Scroll to the bottom and enter the id number of the main ticket
#Click Update.

[[File:RT_Merge.png]]

You should now have the whole thread in one.
Notice that it warns that the process is not reversible, so don't mess it up!

'''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!'''
==For the Admin==
===Create a Privileged User===
#Admin->Users->Select
#Put user in the go to user box.
#*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's freaking magic!
#Open the user account
# Check the box to make the user a privileged user
# Save Changes at the bottom
===Add a user to a queue===
#Admin->Queues->Select
#Select the queue
# Click "Watchers"
# enter the user's name in the "Find People whose" box and hit Go - The user will show up in the lower right area
#Select "AdminCC"
#Click "Save Changes"

=== Merging users where the good email is on the account not connected to BACON ===
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.

==== Beta's Method ====
I don't know if this is the best way but here's how I'm handling it on an old ticket and a way that Sammich seems to believe will work.

# 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 "good email: (email)" and "bad email:(email)" along with links to each user so if I messed up I had all the information still available.
# On the bad account, set the email address (and possibly the username if it's the same as the email address) to something unique but bogus. I used "x@gmail.com" because the email in question was @gmail and it was temporary and easy.
# On the good account, set the email address to what you want it to be: the "good" email address
# Save
# On the bad account, set the email address to what the good account use to have: the "bad" email address
# Save
# Merge the "bad" user into the "good" user

==== Sammich's Method/note ====
<blockquote>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're still going to use the old address you'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.</blockquote>

Handling Harassment Reports

2021-10-24T17:34:03Z

Tainsouvra:

[[Category:Policies]]
==Warnings==
*Any rover, HR staff, department head, or chair of the con may issue a verbal warning to a participant that their behavior violates the con's policies. Warnings should be reported to HR as soon as practical.
*Any staff member or volunteer who is unauthorized to issue a verbal warming, but who witnesses an incident, must report to rovers or HR immediately.
*Due to the perceived "gruffness" of some staff members, we ask that individuals who are not authorized, have had any complaints against them, or do not feel comfortable issuing a verbal warning to not issue a verbal warning themselves. Please submit a report instead.
==Presentations==
Presentations or similar events should not be stopped for one-time gaffes or minor problems. A staff member should speak to the presenter afterward. However, staff should take immediate action to politely and calmly stop any presentation or event that repeatedly or seriously violates con policies. As an example, a staff member should say "I'm sorry. This presentation cannot be continued at the present time" with no further explanation.
==Taking reports==
When taking a report from someone experiencing harassment, a staff member shall make a record of what they say and reassure the reporter that they are being taken seriously.

When making a report a staff member shall do the following:
#Take down the name and badge number of the participant.
#Take down the time when the warning was issued.
#Summarize the behavior that was in violation.
#Take down the approximate time of the behavior (if different than the time of warning).
#Note the circumstances surrounding the incident.
#Take down their own name and badge number.
#Take down the name and badge number of other people involved in the incident.

*Avoid making specific promises about what actions will be taken.
*Ask for all required information from the reporter if it has not been volunteered, but do not pressure them to provide it if they are reluctant. Even if a report lacks information, it should still be recorded and passed along to the appropriate staff member(s).
*If the reporter desires it, arrange for an escort by con staff or a trusted person, contact a friend, or contact local law enforcement.
*Do not pressure the reporter to take any action if they do not want to do it.
*Respect the reporter's privacy by not sharing unnecessary details with others, especially individuals who were not involved with the situation or non-staff members.
After a staff member has received all of the information they can acquire, they must submit their information and report to con ops.
==Expulsion==
A participant may be expelled by the decision of the chairs for whatever reasons they deem sufficient.

==Public statements==
Con staff should not make any public statements about the behavior of individual people during or after the con.

==References==
*This text was modified from: [http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy Policy] Which has also been used by many other cons.
*Also see this text: [http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports Responding to Reports] to further build this page to what we need it to be.

Safety Concern

2021-10-24T17:21:42Z

Tainsouvra: link staff codes, add discord along with radio

[[Category: Procedures]]
==There is NEVER an "Ask Someone Else" For A Safety Concern==
Let me say that again - There is never ever a "Ask Someone Else" if an attendee brings you a safety concern. Don't just send them to ask someone else: if they came to you, '''you''' need to help them.
===Your Safety Concerns===
Report it to rovers. If you feel it is a [[Staff Codes|Hot Coffee]], then call it over the radio / discord as such.
===Attendee Concerns: General Staff / Lower Staff / Volunteers===
# If you can, ask the attendee to go with you to another location. Ops would be IDEAL. If you can't, do your best to make sure your immediate surroundings, you, and the attendee are safe. You will need to get another staffer to come to you.
# If you can not go anywhere :
## Find out the basic details of the concern. Is it an emergency ("Hot Coffee")?
## Call for a rover, or an HR over the radio / discord. You can code it "Hot Coffee," ONLY IF NEEDED.
##* Minor concerns: "This is (name) at (location), I need a rover or HR at (location) to address a safety concern." Repeat it twice.
##* Major or immediate concerns: "This is (name) at (location), I need a rover or HR at (location) to address a '''possible hot coffee'''." Repeat it twice. Then "This hot coffee is a Safety Concern"
#If you can take them:
##Take them to Ops. Find a Rover or upper HR - someone qualified to take a report.
##If you did find someone to take care of the attendee you may now return to what you were doing before they approached you as long as the attendee is comfortable with that. You may stay with the attendee as long as needed to address the concern.
##If you can not find someone who can handle the attendee you will need to get on a radio /discord and call for one
##* Minor concerns: "This is (name) at (location), I need a rover or HR at (location) to address a safety concern." Repeat it twice.
##* Major or immediate concerns: "This is (name) at (location), I need a rover or HR at (location) to address a '''possible hot coffee'''." Repeat it twice. Then "This hot coffee is a Safety Concern"
'''WHATEVER you do, DO NOT SEND THE ATTENDEE AWAY. They came to YOU so YOU need to make sure that they are taken care of. '''
===Rover/HR===
Please [[Handling_Harassment_Reports | follow the steps outlines in out Harassment Procedure for taking a report]]. All the steps are basically the same.