Difference between revisions of "Notes for the Scribe"

From MIT Assassins' Guild
(Created page with "== Things to check before releasing the schedule == * Are the dates correct in the top section? * Do the dates in the body of the email match the dates in the top section? *...")
 
Line 1: Line 1:
== Things to check before releasing the schedule ==
+
== Scribe's Duties ==
 +
 
 +
From the original [https://web.mit.edu/assassin/HighCouncil/Greensheets/scribe.pdf Greensheet]. Needs to be updated.
 +
 
 +
: "He who controls the past controls the future. He who controls the present controls the past." -- George Orwell
 +
 
 +
=== Your Mission ===
 +
 
 +
==== Minutes ====
 +
Take minutes at all meetings. Especially the main guild meetings. Send them out to the list. File copies in the locker.
 +
Try hard to make minutes entertaining so people will bother reading them. Beat your predecessor until you get the minutes
 +
of the meeting at which you were elected.
 +
 
 +
==== Email ====
 +
Send/answer all general email regarding the Guild. Maintain the mailing list and make sure people are added and removed in a timely fashion. Keep stock answers to send to people about what the Guild is (the discuss archive is a useful tool for this one, though there are a few in the Scribe directory). Remember to send recent applications to people being added to the list.
 +
 
 +
==== Paper Mail ====
 +
We don’t get too much of this, but it should be showing up in the ASA office.
 +
 
 +
==== High Council's scheduling ====
 +
Make sure that the High Council as a whole does the things it needs to when it needs to. Scheduling meetings and games is the big one here to keep an eye on. If your predecessor hasn’t scheduled Summer, get on that.
 +
 
 +
==== Web Site ====
 +
Maintain and update the web site.  Use of RCS has been somewhat spotty during different eras; a lot of files aren’t
 +
actually checked in – by all means, consider upgrading to a better version control system. Things to maintain include:
 +
* the lists of current and past High Council members
 +
* the schedule, and the list of upcoming games
 +
* the list of past games
 +
 
 +
==== Mailing List Reminder ====
 +
Sometime in early Spring, you should send out a reminder mail to the Guild about the assorted mailing lists that the Guild maintains. A sample email can be found in /mit/assassin/Scribe/StandardEmails/GuildBusiness/mailing-list-reminder.txt.
 +
 
 +
==== Sanity Checking ====
 +
Though not specifically the job of the Scribe, all members of the High Council should keep an eye out to make sure that the High Council doesn’t make any stupid decisions. Precedent doesn’t matter nearly as much as common sense.
 +
 
 +
== Other Notes ==
 +
 
 +
=== Things to check before releasing the schedule ===
  
 
* Are the dates correct in the top section?
 
* Are the dates correct in the top section?
Line 6: Line 43:
 
* Is there any weird spacing in the copied blurbs?
 
* Is there any weird spacing in the copied blurbs?
  
== Things to schedule around ==
+
=== Things to schedule around ===
  
 
As of 2014ish or 2019ish, try to schedule around:
 
As of 2014ish or 2019ish, try to schedule around:

Revision as of 02:39, 27 February 2019

Scribe's Duties

From the original Greensheet. Needs to be updated.

"He who controls the past controls the future. He who controls the present controls the past." -- George Orwell

Your Mission

Minutes

Take minutes at all meetings. Especially the main guild meetings. Send them out to the list. File copies in the locker. Try hard to make minutes entertaining so people will bother reading them. Beat your predecessor until you get the minutes of the meeting at which you were elected.

Email

Send/answer all general email regarding the Guild. Maintain the mailing list and make sure people are added and removed in a timely fashion. Keep stock answers to send to people about what the Guild is (the discuss archive is a useful tool for this one, though there are a few in the Scribe directory). Remember to send recent applications to people being added to the list.

Paper Mail

We don’t get too much of this, but it should be showing up in the ASA office.

High Council's scheduling

Make sure that the High Council as a whole does the things it needs to when it needs to. Scheduling meetings and games is the big one here to keep an eye on. If your predecessor hasn’t scheduled Summer, get on that.

Web Site

Maintain and update the web site. Use of RCS has been somewhat spotty during different eras; a lot of files aren’t actually checked in – by all means, consider upgrading to a better version control system. Things to maintain include:

  • the lists of current and past High Council members
  • the schedule, and the list of upcoming games
  • the list of past games

Mailing List Reminder

Sometime in early Spring, you should send out a reminder mail to the Guild about the assorted mailing lists that the Guild maintains. A sample email can be found in /mit/assassin/Scribe/StandardEmails/GuildBusiness/mailing-list-reminder.txt.

Sanity Checking

Though not specifically the job of the Scribe, all members of the High Council should keep an eye out to make sure that the High Council doesn’t make any stupid decisions. Precedent doesn’t matter nearly as much as common sense.

Other Notes

Things to check before releasing the schedule

  • Are the dates correct in the top section?
  • Do the dates in the body of the email match the dates in the top section?
  • Are all of the names spelled correctly, and without any typos? (Extra commas, etc?)
  • Is there any weird spacing in the copied blurbs?

Things to schedule around

As of 2014ish or 2019ish, try to schedule around:

  • Mystery Hunt! (this is critical)
  • Arisia
  • Intercon (spring)
  • MIT's academic schedule: finals, parents weekend, CPW, rush, breaks
  • East Side Fair (R.I.P. steer roast)
  • Splash (November. eats a bunch of rooms; plus, there's Splash patrol)
  • Spark (March, afternoon to early evening)
  • CPW

Also be aware of: