Talk:Stefan's Proposal to Change the Hierarchy - Revision history

TheKillerRabbit: /* Signatures */

2007-05-16T21:59:25Z

‎Signatures

TheKillerRabbit: Signatures

2007-05-16T21:59:02Z

Signatures

Bfoo2: /* PR Director and Tech Director */

2007-05-11T16:52:38Z

‎PR Director and Tech Director

Bfoo2 at 16:52, 11 May 2007

2007-05-11T16:52:10Z

Stefanido: /* Mission Commander - Rank 2 and Subcommander - Rank 3 */ Deleted. Superfluous. Does not add anything to the discussion.

2007-05-11T04:05:26Z

‎Mission Commander - Rank 2 and Subcommander - Rank 3: Deleted. Superfluous. Does not add anything to the discussion.

Anthony: /* Webmaster */ added signature

2007-05-11T01:35:34Z

‎Webmaster: added signature

Anthony: /* Webmaster */

2007-05-11T01:35:13Z

‎Webmaster

Conformer at 01:23, 11 May 2007

2007-05-11T01:23:57Z

Conformer at 01:19, 11 May 2007

2007-05-11T01:19:16Z

Anthony: /* Role of SubCmdr */

2007-05-11T01:16:57Z

‎Role of SubCmdr

← Older revision		Revision as of 21:59, 16 May 2007
Line 110:		Line 110:
	== Signatures ==		== Signatures ==

−	JEFF! SIGN YOUR POSTS! (By typing <~~nowik~~>~~[[User:TheKillerRabbit\|<font color="green">The</font> <font color="#0099CC">Killer</font> <font color="red">Rabbit</font>]] <font size="1">[http://vv.carleton.ca/~~~~~nhotson aka Nevin]</font> 17:59, 16 May 2007 (EDT)~~</nowiki> after the post) --[[User:TheKillerRabbit\|<font color="green">The</font> <font color="#0099CC">Killer</font> <font color="red">Rabbit</font>]] <font size="1">[http://vv.carleton.ca/~nhotson aka Nevin]</font> 17:59, 16 May 2007 (EDT)	+	JEFF! SIGN YOUR POSTS! (By typing <nowiki>~~~~</nowiki> after the post) --[[User:TheKillerRabbit\|<font color="green">The</font> <font color="#0099CC">Killer</font> <font color="red">Rabbit</font>]] <font size="1">[http://vv.carleton.ca/~nhotson aka Nevin]</font> 17:59, 16 May 2007 (EDT)

← Older revision		Revision as of 21:59, 16 May 2007
Line 107:		Line 107:

	Brian Foo		Brian Foo
		+
		+	== Signatures ==
		+
		+	JEFF! SIGN YOUR POSTS! (By typing <nowik>[[User:TheKillerRabbit\|<font color="green">The</font> <font color="#0099CC">Killer</font> <font color="red">Rabbit</font>]] <font size="1">[http://vv.carleton.ca/~nhotson aka Nevin]</font> 17:59, 16 May 2007 (EDT)</nowiki> after the post) --[[User:TheKillerRabbit\|<font color="green">The</font> <font color="#0099CC">Killer</font> <font color="red">Rabbit</font>]] <font size="1">[http://vv.carleton.ca/~nhotson aka Nevin]</font> 17:59, 16 May 2007 (EDT)

← Older revision		Revision as of 16:52, 11 May 2007
Line 105:		Line 105:

	In addition, I would like to propose the position of a technical director. I believe that such a job cannot be fulfilled by the sub commander because the SC is not selected on the criteria of tech-saviness, but rather experience and leadership skills. In addition, the maintainence and upgrade of SpaceSIm's hardware is a perpetual job, and thus cannot be fulfilled by temporary appointments. I would like to clairify that the TD is not only responsible for the network, but also the physical hardware of the hab--stereo system and doors to name a few.		In addition, I would like to propose the position of a technical director. I believe that such a job cannot be fulfilled by the sub commander because the SC is not selected on the criteria of tech-saviness, but rather experience and leadership skills. In addition, the maintainence and upgrade of SpaceSIm's hardware is a perpetual job, and thus cannot be fulfilled by temporary appointments. I would like to clairify that the TD is not only responsible for the network, but also the physical hardware of the hab--stereo system and doors to name a few.
		+
		+	Brian Foo

← Older revision		Revision as of 16:52, 11 May 2007
Line 91:		Line 91:
	== General Members ==		== General Members ==
	Though they do not have a formal rank, general members should comprise the majority of Space Sim, and contribute significantly to its work and success. They are also encouraged to serve in a leadership capacity through Task Forces, EEP Stations, Mission positions, and any of their own planned and approved initiatives.		Though they do not have a formal rank, general members should comprise the majority of Space Sim, and contribute significantly to its work and success. They are also encouraged to serve in a leadership capacity through Task Forces, EEP Stations, Mission positions, and any of their own planned and approved initiatives.
		+
		+
		+	== PR Director and Tech Director ==
		+
		+	As I have often stated, I agre with the fundamental principle of this system, although some of the details may have to be worked out at a later date.
		+
		+	Some things that I would like to be considered are:
		+
		+	The role of the PR director. As it stands, the the article provides muddled information concerning the PR Director, but generally, I get the feeling that the club's PR will be focused more under the EEPs and Planetarium departments. I personally believe that the PR director should and must provide PR to all branches of the club, making such an arangement undesirable. As the role of the traditional PR director is rather large (including not only the execution of PR related events, but the planning of the PR campaign for the year), I believe that such a role should not simply be spread to all three commanders. Alternatively, since a comprehensive year-long PR plan must be designed and carried out, representing a long-term commitment, appointing temporary PR directors whenever an event looms is not acceptable.
		+
		+	Therefore, following the philosiphy that any task whose jurisdiction is ambigious shoul dbe put under the mission commander, I propose the creation of the position of PR directur to be run under the mmision commander.
		+
		+
		+	In addition, I would like to propose the position of a technical director. I believe that such a job cannot be fulfilled by the sub commander because the SC is not selected on the criteria of tech-saviness, but rather experience and leadership skills. In addition, the maintainence and upgrade of SpaceSIm's hardware is a perpetual job, and thus cannot be fulfilled by temporary appointments. I would like to clairify that the TD is not only responsible for the network, but also the physical hardware of the hab--stereo system and doors to name a few.

← Older revision		Revision as of 04:05, 11 May 2007
Line 49:		Line 49:


−	~~== Mission Commander - Rank 2 and Subcommander - Rank 3==~~
−	Their roles remain the same. However, it should be emphasized that what each of them do specifically is up to them to decide. There should be no definite distinction between these two members, besides the fact that one has more power and exterior responsibilities than the other.

@@ Line 75: / Line 75: @@
 *Because most of the information available on the Website is about the Mission, I believe that the Mission Commander should be in charge of the Webmaster.[[User:Stefanido|Stefanido]] 21:10, 10 May 2007 (EDT)
-:*I agree with Stefan. The web master is associated with the mission branch mainly, therefore the web master should fall on under the mission Cmdr.
+:*I agree with Stefan. The web master is associated with the mission branch mainly, therefore the web master should fall on under the mission Cmdr.--[[User:Anthony|Anthony]] 21:35, 10 May 2007 (EDT)
 *So instead of the Webmaster, the Planetarium Commander should be in charge on an additional assistant. That works out well.

← Older revision		Revision as of 01:35, 11 May 2007
Line 75:		Line 75:

	*Because most of the information available on the Website is about the Mission, I believe that the Mission Commander should be in charge of the Webmaster.[[User:Stefanido\|Stefanido]] 21:10, 10 May 2007 (EDT)		*Because most of the information available on the Website is about the Mission, I believe that the Mission Commander should be in charge of the Webmaster.[[User:Stefanido\|Stefanido]] 21:10, 10 May 2007 (EDT)
		+	:*I agree with Stefan. The web master is associated with the mission branch mainly, therefore the web master should fall on under the mission Cmdr.

	*So instead of the Webmaster, the Planetarium Commander should be in charge on an additional assistant. That works out well.		*So instead of the Webmaster, the Planetarium Commander should be in charge on an additional assistant. That works out well.

@@ Line 75: / Line 75: @@
 *Because most of the information available on the Website is about the Mission, I believe that the Mission Commander should be in charge of the Webmaster.[[User:Stefanido|Stefanido]] 21:10, 10 May 2007 (EDT)
 ===Quartermaster===
@@ Line 81: / Line 83: @@
 *Because the Subcommander, and not the Mission Commander is in charge of TFs, and therefore needs the tools more, the Subcommander should be in charge of the Quartermaster. [[User:Stefanido|Stefanido]] 21:10, 10 May 2007 (EDT)
 == Task Force Leaders ==

← Older revision		Revision as of 01:19, 11 May 2007
Line 44:		Line 44:

	*Remember that we DO want as many leadership positions as possible to give every member a chance to lead the direction of the club, and thereby fulfill our [[Mission Statement]].[[User:Stefanido\|Stefanido]] 21:04, 10 May 2007 (EDT)		*Remember that we DO want as many leadership positions as possible to give every member a chance to lead the direction of the club, and thereby fulfill our [[Mission Statement]].[[User:Stefanido\|Stefanido]] 21:04, 10 May 2007 (EDT)
		+
		+	*There will be many other leadership positions. The ones I'm listed are only all the permanent ones that will be in place throughout the entirety of next year. Positions like Task Force Leaders, EEP Station Leaders, Simulator/Planetary Surface Commander, and other Assistants will all be temporary and informal, but they still are important leadership positions.

← Older revision		Revision as of 01:16, 11 May 2007
Line 34:		Line 34:

	*If we are creating two different positions, then they need to have different responsibilities. If not, then how do we choose who's SCmdr. as opposed to MCmdr.? The bulk of what I think about, as MC this year, pertains to Task Forces. However, there is a whole other range of things I should have been and should be more responsible for including PR, Training, the Website, the Galileo Challenge, the Office, branching out, finding sponsors, making sure the EEP and Planetarium Commanders were happy, making sure the general membership was happy, etc... In any case, if we dedicate one of the M-Branch Commanders to Task Forces, this frees the other for general planning and all the tasks listed above, and much much more! Call now, and we'll throw in a free PR Director![[User:Stefanido\|Stefanido]] 21:00, 10 May 2007 (EDT)		*If we are creating two different positions, then they need to have different responsibilities. If not, then how do we choose who's SCmdr. as opposed to MCmdr.? The bulk of what I think about, as MC this year, pertains to Task Forces. However, there is a whole other range of things I should have been and should be more responsible for including PR, Training, the Website, the Galileo Challenge, the Office, branching out, finding sponsors, making sure the EEP and Planetarium Commanders were happy, making sure the general membership was happy, etc... In any case, if we dedicate one of the M-Branch Commanders to Task Forces, this frees the other for general planning and all the tasks listed above, and much much more! Call now, and we'll throw in a free PR Director![[User:Stefanido\|Stefanido]] 21:00, 10 May 2007 (EDT)
		+	:*Form another point of view, the lack of attention to the things mentioned above is partially due to having the TFs taking up too much attention and time. The worksessions need not to be filled with TFs. By putting a Cmdr just for TFs (kinda resemble the TF Commander doesn't it) is one way to address the problem, but one might also consider the de-emphisising of TFs. Adding an Cmdr just for TFs just puts more emphasis on the TFs and they probably will end up taking a larger chuck of the work sessions since their is some one devoted to organizing them now. Also, the majority of this year's TFs was overseen by one MC was it not?--[[User:Anthony\|Anthony]] 21:16, 10 May 2007 (EDT)

	== Jeff's Proposed Changes ==		== Jeff's Proposed Changes ==