Board Orientation - Revision history

Rdoeksen: /* Handling Cash Payments */

2018-12-12T22:43:57Z

Handling Cash Payments

← Older revision		Revision as of 22:43, 12 December 2018
Line 109:		Line 109:
	All cash payments are to be deposited in the dropbox in the safe; it's currently mounted on the wall. On the envelope should be their name and the date of the deposit.		All cash payments are to be deposited in the dropbox in the safe; it's currently mounted on the wall. On the envelope should be their name and the date of the deposit.

	'''Members should be informed that cash payments can take a while to be processed and that they really ~~should~~ ~~pay~~ ~~with~~ ~~paypal~~ if ~~possible~~'''		'''Members should be informed that cash payments can take a while to be processed and that they really establish recurring payments through the member management system - [[Wild Apricot]] and [[Stripe]].'''

	==== Processing the Payments ====		==== Processing the Payments ====

	'''This is sort of outdated. The board has been working on a better process for this involving RT. Please update this page once you have it worked out.'''

	For each cash payment, update the member's record in ~~not~~ ~~zoho~~.		For each cash payment, update the member's record in Wild Apricot.

			NOTE INSTRUCTIONS WERE FOR ZOHO, NOT WILD APRICOT, VERY OUTDATED

	* Set their membership level to their payment amount (if applicable.)		* Set their membership level to their payment amount (if applicable.)

Rdoeksen: /* Credentials */

2017-11-23T02:27:27Z

Credentials

← Older revision		Revision as of 02:27, 23 November 2017
Line 93:		Line 93:
	* Online banking		* Online banking
	* PEX Cards		* PEX Cards
	* ???

	== Annual Report ==		== Annual Report ==

Esp: /* Running Votes */

2017-02-25T23:16:07Z

Running Votes

← Older revision		Revision as of 23:16, 25 February 2017
Line 155:		Line 155:
	** Don't forget to change the dates in the email subject line!		** Don't forget to change the dates in the email subject line!
	* In addition to a proxy statement announcement, it's helpful to send out a reminder email the day before proxies are due.		* In addition to a proxy statement announcement, it's helpful to send out a reminder email the day before proxies are due.
	* Proxies are sent to the votes@ account. Try to check this account before the deadline for proxy votes; if a proxy is incorrectly completed, you can let people know that they can re-send a proxy.		* Proxies are sent to the votes@ account. (Credentials in LastPass) Try to check this account before the deadline for proxy votes; if a proxy is incorrectly completed, you can let people know that they can re-send a proxy.
	* Copy one of the spreadsheets in the Google Drive to track proxy votes. There's also a space there to track who voted in person and vote totals.		* Copy one of the spreadsheets in the Google Drive to track proxy votes. There's also a space there to track who voted in person and vote totals.
	* At the meeting for the in-person vote, have all full members sign in on a [[https://drive.google.com/open?id=0ByyGnsLiSGNWRkhnLU1YY2J3WjQ Vote Roll Call Sheet]]		* At the meeting for the in-person vote, have all full members sign in on a [[https://drive.google.com/open?id=0ByyGnsLiSGNWRkhnLU1YY2J3WjQ Vote Roll Call Sheet]]

Esp: /* Running Votes */

2017-02-25T23:14:19Z

Running Votes

← Older revision		Revision as of 23:14, 25 February 2017
Line 147:		Line 147:
	== Running Votes ==		== Running Votes ==

	Most of the business conducted by PS:1 is decided by member votes. ~~The~~ ~~burden~~ ~~of most of~~ the ~~record~~ ~~keeping is on~~ the ~~secretary~~.		Most of the business conducted by PS:1 is decided by member votes. Running votes is the responsibility of the Secretary.

	* A new vote should go here: [[2017 Votes]] (or the equivalent page for the current year)		* A new vote should go here: [[2017 Votes]] (or the equivalent page for the current year)
Line 161:		Line 161:
	** Record which members are present for the vote.		** Record which members are present for the vote.
	* Once the voting is done, update [[2017 Votes]] as well as the votes page. I also generally note whether a vote passed in the minutes and on the vote page. Mailing list announcement also isn't a bad idea.		* Once the voting is done, update [[2017 Votes]] as well as the votes page. I also generally note whether a vote passed in the minutes and on the vote page. Mailing list announcement also isn't a bad idea.


	== Task Management ==		== Task Management ==

Esp at 23:13, 25 February 2017

2017-02-25T23:13:55Z

← Older revision		Revision as of 23:13, 25 February 2017
Line 141:		Line 141:

	'''To add''': how to handle members who spend member points on a temporary upgrade instead of a refund		'''To add''': how to handle members who spend member points on a temporary upgrade instead of a refund
		⚫	=== Checks ===
		⚫	Need to pass along the blank checks.


	== Running Votes ==		== Running Votes ==
Line 159:		Line 162:
	* Once the voting is done, update [[2017 Votes]] as well as the votes page. I also generally note whether a vote passed in the minutes and on the vote page. Mailing list announcement also isn't a bad idea.		* Once the voting is done, update [[2017 Votes]] as well as the votes page. I also generally note whether a vote passed in the minutes and on the vote page. Mailing list announcement also isn't a bad idea.

⚫	=== Checks ===
⚫	Need to pass along the blank checks.

	== Task Management ==		== Task Management ==

Esp: /* Task Management */

2017-02-25T23:13:25Z

Task Management

← Older revision		Revision as of 23:13, 25 February 2017
Line 168:		Line 168:
	RTs can have attachments, comments, email replies, and statue changes. It is good to record status updates in tickets so that there is no bottleneck in case someone else needs to pick up the ticket, or has a question.		RTs can have attachments, comments, email replies, and statue changes. It is good to record status updates in tickets so that there is no bottleneck in case someone else needs to pick up the ticket, or has a question.

	[[RT ~~Management~~]] documents RT basics as well as how to handle the most common RT tickets (general questions, new members, paypal cancellations, member points, etc.)		[[RT Procedures]] documents RT basics as well as how to handle the most common RT tickets (general questions, new members, paypal cancellations, member points, etc.)

	== Meetings ==		== Meetings ==

Esp: /* Running Votes */

2017-02-25T23:12:49Z

Running Votes

← Older revision		Revision as of 23:12, 25 February 2017
Line 142:		Line 142:
	'''To add''': how to handle members who spend member points on a temporary upgrade instead of a refund		'''To add''': how to handle members who spend member points on a temporary upgrade instead of a refund

	=== Running Votes ===		== Running Votes ==

	Most of the business conducted by PS:1 is decided by member votes. The burden of most of the record keeping is on the secretary.		Most of the business conducted by PS:1 is decided by member votes. The burden of most of the record keeping is on the secretary.

Esp: /* Running Votes */

2017-02-25T22:57:00Z

Running Votes

@@ Line 146: / Line 146: @@
 Most of the business conducted by PS:1 is decided by member votes. The burden of most of the record keeping is on the secretary.
 * This email needs to be sent at least 5 days before the vote - so the Thursday before a Tuesday vote.
-* To send the vote notification email, select "Mass Mail" from the dropdown menu when logged in to the members.pumpingstationone.org. Edit an existing vote email changing the dates (they're in bold), save, and send to full members.
+* To send the vote notification email, select "Mass Mail" from the dropdown menu when logged in to the members.pumpingstationone.org. Edit an existing vote email changing the link to the vote and the dates (they're in bold), save, and send to full members.
 === Checks ===

Esp: /* Google Groups/Mailing Lists */

2017-02-25T22:26:48Z

Google Groups/Mailing Lists

← Older revision		Revision as of 22:26, 25 February 2017
Line 50:		Line 50:
	We have two main mailing lists that our members use to interact with each other online. The [[https://groups.google.com/forum/#!forum/pumping-station-one-public public list]] and the [[https://groups.google.com/forum/#!forum/pumping-station-one private list]]. All board members should at least get the '''Manager''' role to be able to do moderation and to approve join requests and such.		We have two main mailing lists that our members use to interact with each other online. The [[https://groups.google.com/forum/#!forum/pumping-station-one-public public list]] and the [[https://groups.google.com/forum/#!forum/pumping-station-one private list]]. All board members should at least get the '''Manager''' role to be able to do moderation and to approve join requests and such.

	When handling a request to join the member's group, check the member's site. If the requester is a member, [[https://support.google.com/groups/answer/2465464?hl=en \| approve them]]. Proposed procedure: after adding somebody to the list, reply to the directors-only@ list letting others know that the member has been added.		When handling a request to join the member's group, check the member's site. If the requester is a member, [[https://support.google.com/groups/answer/2465464?hl=en approve them]]. Proposed procedure: after adding somebody to the list, reply to the directors-only@ list letting others know that the member has been added.

	During orientation, new board members will need to be shown the interface for managing membership of these lists and how to approve posts to the public list. They should also be given some rough guidelines on what to approve or not approve on the public list. Generally anyone can post to it (member or not) and we'll only block them from posting if their message is obvious spam.		During orientation, new board members will need to be shown the interface for managing membership of these lists and how to approve posts to the public list. They should also be given some rough guidelines on what to approve or not approve on the public list. Generally anyone can post to it (member or not) and we'll only block them from posting if their message is obvious spam.

Esp: /* Google Groups/Mailing Lists */

2017-02-25T22:26:32Z

Google Groups/Mailing Lists

← Older revision		Revision as of 22:26, 25 February 2017
Line 48:		Line 48:

	== Google Groups/Mailing Lists ==		== Google Groups/Mailing Lists ==
	We have two main mailing lists that our members use to interact with each other online. The [[https://groups.google.com/forum/#!forum/pumping-station-one-public public list]] and the [[https://groups.google.com/forum/#!forum/pumping-station-one private list]]. All board members should at least get the '''Manager''' role to be able to do moderation and to approve join requests and such. During orientation, new board members will need to be shown the interface for managing membership of these lists and how to approve posts to the public list. They should also be given some rough guidelines on what to approve or not approve on the public list. Generally anyone can post to it (member or not) and we'll only block them from posting if their message is obvious spam.		We have two main mailing lists that our members use to interact with each other online. The [[https://groups.google.com/forum/#!forum/pumping-station-one-public public list]] and the [[https://groups.google.com/forum/#!forum/pumping-station-one private list]]. All board members should at least get the '''Manager''' role to be able to do moderation and to approve join requests and such.

			When handling a request to join the member's group, check the member's site. If the requester is a member, [[https://support.google.com/groups/answer/2465464?hl=en \| approve them]]. Proposed procedure: after adding somebody to the list, reply to the directors-only@ list letting others know that the member has been added.

			During orientation, new board members will need to be shown the interface for managing membership of these lists and how to approve posts to the public list. They should also be given some rough guidelines on what to approve or not approve on the public list. Generally anyone can post to it (member or not) and we'll only block them from posting if their message is obvious spam.

	* Moderating a member: Occasionally there is a need to require moderation for a member for some period of time and follows this process:		* Moderating a member: Occasionally there is a need to require moderation for a member for some period of time and follows this process: