Difference between revisions of "Strikeforces"

From SkullSpace Wiki
Jump to navigation Jump to search
(Current Strikeforces)
Line 1: Line 1:
 
SkullSpace members occasionally come together to work on special tasks. These Strikeforces are usually formed on-the-fly.
 
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.
 +
 +
==Current Strikeforces==
 
(For freshness, newer or updated Strikeforces are closer to the top and will be moved upwards as news comes in.)
 
(For freshness, newer or updated Strikeforces are closer to the top and will be moved upwards as news comes in.)
  
==Current Strikeforces==
 
 
'''Events'''
 
'''Events'''
 
* To organize more events. Adrian is planning a music-making course, Justin might run a course on Eagle. Take donations for talks?
 
* To organize more events. Adrian is planning a music-making course, Justin might run a course on Eagle. Take donations for talks?
 
* Leader: Alex
 
* Leader: Alex
 
* Members: Alex, [Justin?], [Adrian?]
 
* Members: Alex, [Justin?], [Adrian?]
 +
 +
'''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
  
 
'''Strikeforce Blade'''
 
'''Strikeforce Blade'''

Revision as of 01:04, 6 September 2012

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.

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. Adrian is planning a music-making course, Justin might run a course on Eagle. Take donations for talks?
  • Leader: Alex
  • Members: Alex, [Justin?], [Adrian?]

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

Strikeforce Blade

  • Discussing the merits of a blade server, and potentially pooling some money towards a full set
  • Leader: Chris Kluka
  • Members: Chris, AMichael, ...[Mark? Etc?]
  • End Result: A single large VM server would probably fulfill all our needs, and use less electricity. A debate may be held in the future.

Others [Please add any other strikeforces!]