Strikeforces

SkullSpace members occasionally come together to work on special tasks. These strikeforces are usually formed on-the-fly.

Protocol

SkullSpace strikeforces are fairly casual—we create them any time we want to come together and solve a problem, and they end whenever that problem is solved or becomes too trivial to care about.

To create a strikeforce, add it below with a name, a leader, a description, and a list of members. The leader will be responsible for making sure all members are in the loop, and will be the contact point for anyone else interested in their work.

If you want to join, add your name into the list of members and send the leader a message. Ask some of the other members what's gone on so far.

Current Strikeforces

(For freshness, newer or updated Strikeforces are closer to the top and will be moved upwards as news comes in.)

Events

• To organize more events, coordinate scheduling, and increase awareness for events of all kinds.
• Leader: Alex
• Members: Alex, AMichael
• Unscheduled/Possible Projects:
  • Justin - Possibly a course on Eagle
  • Adrian - Possibly a course on making music
  • AMichael - Planning a Meme Fundraiser Dinner in early October, with meals from our meme cookbook, "Cook All the Things".
  • Colin - Crypto Party -> https://cryptoparty.org (ready to go, October 6th Weekend)
• Scheduled:
  • OpenChaos Night - Monday Sept 17th
  • Software Freedom Day Hackathon - Saturday Sept 15th

Cleaning

• To assign chores to members, in order to keep the space clean and functional
• Leader: ...Justin? As Operations Manager?
• Members: Justin, Siu, AMichael, Dave...
• Main areas:
  • Kitchen: Siu will make sure the dishes are cleaned, and will scold members who have no put theirs away.
  • Fridge: AMichael will eat throw out all food left in the fridge for more than a week or so, if there's no expiry date, or will remove items that are past their expiry date.
  • X: Fill your role in here.
• Others:
  • Bathrooms: A quote will be gotten for cleaning staff. These are the only parts of the space we won't be able to have volunteer help for.

Advertising/Media

• To announce our existence to the world, and help people find us.
• Leader: None, at the moment
• Members: None, at the moment
• Ideas:
  • Get a bill-board or sign outside, so people can find us
  • Directions inside, like 'EXIT' signs and Washroom signs.

Meme Dinner

• To organize and execute the SkullSpace Meme Dinner on October 20th.
• Leader: AMichael
• Members: AMichael, Nate, Siu

Cookbook

• THIS IS A STUB. THE LEADER SHOULD VERIFY THE STRIKEFORCE INFO
• To compile meme-based recipes into a cookbook called "Cook All the Things".
• Leader: Nate?
• Members: Nate, Siu, AMichael

Metastrikeforce

• To examine the creation and upkeep of strikeforces, in order to determine what procedures must be in place for them to function efficiently
• Leader: AMichael
• Members: AMichael
• So far: I've created this page to make it easy to create a strikeforce in a centralized location.
• Problems: It still might be a little difficult for leaders to gather the email addresses of everyone interested, which is why I've suggested that people who join should contact the leader. We might be able to fix this by making a forum for strikeforces, so that anyone interested could subscribe to topic updates with a single click.

Strikeforce Blade

• Discussing the merits of a blade server, and potentially pooling some money towards a full set
• Leader: Chris Kluka (asdlkf@asdlkf.net)
• Members: Chris, AMichael, ...[Mark? Etc?]
• Objective: As a result of the power and heat/cooling requirements, and also a lack of remote monitoring and services modules, SkullSpace would like to aquire or build a mainframe-type system. This system would consist of one(or more) hypervisors hosting one(or more) virtual machines.
• Possible Scope: Either one large VM server, or, a cluster of servers (such as a blade center) to be built/aquired and configured for SkullSpace member access. Key goals include remote system restart, multitenancy, and power usage reduction (compared to the current solution of several individual servers).
• End Result: A single large VM server is likely to fulfill many of our needs—and use less electricity. A debate may be held in the future to determine how blades or a single server would help us.

Server Room / Networking

• Members: CStanners, AlexWeber, MarkJenkins
• Todo:
  • Rack between racks
  • Buy patch cables, install the patch panel, terminate all lines to it
  • make sure all lines are labeled and wikied
  • Enclosed area behind racks so hot air goes outside
  • Put strikes on battery backup or built-in voltage upconverter so the cheap chinese strikes get the 15v they need to work from the 12v supply - I got $3 step-up converter from ebay to fix this.
  • ac/fan situation
  • Get huge ups working or buy another
  • Install electrical lines for UPS, AC
  • put camera in server room?
  • Networking - get cisco switches working as internet-side switches instead of limited dlinks
  • Get public server going with traffic graphs from routers, switches, monitoring of which services are up, alerting on failure.
  • Some type of power/temperature/smoke alerting that can also kill the breaker
  • make sure there's a fire extinguisher, check if there's any possible way to have cheap/safe halon-like system.

Others

[Please add any other strikeforces!]