Difference between revisions of "Officer transition"

Latest revision as of 16:22, 1 July 2017

[edit] New officers

This seems silly to have to say but I will: computer access is not required for members but it IS for officers. I'd like to emphasize that Big technical chops should not be requried as these are business-process jobs, but the more technical the person is the easier of a time they will have. I think at present time all officers of Bloominglabs are either software developers or sysadmins, so technical skills will go a long way here.

The officers that keep Bloominglabs running work as a team. Our bylaws define each role to the minimal extent as required by law. This gives us the ability to easily and quickly adjust each position as our needs change over time. A fuller description of duties expected of officers is found in the Officers Guide.

[edit] Checklist

This is a list of things that the new officer needs in order for them to do their job. At a minumum the old officer needs to work with the new officer to help transition them into the new role being taken over; however ideally it will be a team effort.

1. Add them to the contact at bloominglabs dot org mail alias
2. Get a login to the RFID system
3. Get a login for the wiki - you may need to update policies and rules and these are stored on our wiki
4. Verify they can login to these systems:
   1. Invoice system (Simple Invoices) -- Currently switching to freshbooks as of July 1st, 2017
   2. Asset system (Custom)
   3. Google Drive - we have a number of documents stored here
   4. Box account
   5. If officer is technical, create shell account for access to the Bloominglabs Linode/webserver
5. They should receive a copy of the "Hackerspace" document directory (may move this to Box in the future)
   1. This gets them a full local copy of all our IRS+State legal docs
   2. Gets them past documents we've written: Firehouse RFI, grants, etc.
   3. Gets them a copy of all our business operation documents that may need to be reprinted
6. Officers deal with sensitive accounts so use of encryption is required. All officers must have a PGP key. It does not have to be integrated into their email, but that makes life much easier.
   1. If the new officer has a PGP key, they need to send it to contact at bloominglabs dot org
   2. If they have no key, someone needs to help them generate a key pair, then share their public key - GnuPG is cross-platform and free.
   3. Officers should post their public keys to the wiki (on their wiki account pages)
7. If this is a President/Treasurer position, they will need to be a signatory on the Bloominglabs bank account.
   1. Must be scheduled with an existing signatory to get this transitioned over
   • Additionally they need access to these accounts as well:
   1. Online Banking account
   2. PayPal
   3. Square
8. A list of all of our other passwords needs to be provided securely. Also just like step 7, they should only get financial account access if they are the President or Treasurer or else if they are assisting with some aspect of finances. They need a secure way of storing this info if they don't already have a method for this (Truecrypt/Bitlocker volume or similar).

[edit] Required reading for new officers

1. Skim over our Business Operations to see what processes we have documented for future reference:
   • http://bloominglabs.org/index.php/Business_Operations
2. Need to read this doc (30 pages): IRS Compliance Guide for 501(c)(3) Charities.
   • This gives clear advice on what activities we can and CAN'T engage in, also what reporting we are required to do:
   • http://www.irs.gov/pub/irs-pdf/p4221pc.pdf
3. Should look through our official meeting minutes:
   • http://bloominglabs.org/index.php/Meeting_Minutes
4. Should look through the Bloominglabs Log:
   • http://bloominglabs.org/index.php/Bloominglabs_Log