Dev Team Update - Voting Rules & Player Addition

[The Lamb]

My dear sweet fellow seamen..yeah that just happend.

First off, dont tell people what to do, they dont like that, even if they have to do it. You always ask, and thus enlist their help. They still do it, but now they feel they are doing you a favor for you. (change the frame)

Second, when a major change happens in a company (game play) you will always have people who have a hard time with change. The bast way to counter this is by once again enlisting their help. This helps to find people to champion your ideas and also make the staff part of the change, thus engaging the spirit.

Lastly in any divorce there is his side, her side and the correct side. The reason i bring this up is perspective, and no one knows what conversations were had that lead to any decision.

So why did i bring up all these points. CJ has done a great job doing a few things. First, he has enlisted the help of those in the community to help champion the game, furthermore he has allowed some dedicated players to feel a part of the direction of the game.

Second, to me the dev team is like the software that weeds out resumes for HR. Most of us have had ideas and put them out there in the ether, but that is a shart load of forum material for CJ to rummage through, so the dev team weeds through the "junk resumes" and only puts forth the ones that can do the job, what ever that is.

Lastly, no one knows why the structure is such except for the people who put it in place. Maybe Dez threatened to leave if he didnt get a special vote, or maybe he is big and bulgy like a moose and that warranted a vote for him and three more for the impressive stature.

In my humble opinion, worrying about this is may be in vane, as CJ and partners are going to do what they deem necessary for the game. When i enlist my staff, I typically already have a direction, its just a matter at what point they realize its the best way for them self, but they still feel empowered, its a win win. More business lingo... we touch all the bases, put ducks in rows, and try to get a 20k ft view to stave off aggressive mediocrity. I hope we all just had an A-ha moment with that one

We dont need all you seamen getting salty! Yeah, its happened again

[Mack]

i wonder why -1's mean nothing

[DezNutz]

Feniks.. It does not really matter. If I like a feature, I'll use it and if not, I won't. If enough things happen I do not like, I'll move on and if stuff appeals to me, I will use it and encourage others to play as well. What the 'team' one or many decide to propose to development will be dependent upon what they perceive the player base wants. If they miss the mark... enrollment dwindles. Hit a bulls eye and enrollment and retention rises.

I think you are completely missing my point. CJ put the dev team in place for a reason. Now, this suggestion is simply going back towards the way things were before the team was put in place. Whether or not you personally use an approved suggestion has zero bearing g on my point.

My point is the team is not needed based on the new approval rules Dez posted. All that is needed is Dez and for people from the forums to vote yes and a suggestion is approved. ..... even if 50 others vote against it dez and 4 others still enough to approve.

I joined the dev team because of something Dez said to me. He said if you want to make it better then join. So I did. Now being on the team doesn't matter.

The approval rules are no different than they were before this post. You are IMO harping on nothing and just blowing smoke to complain.

The rules set by CJ stipulated 4 votes were required to move a topic forward. As the coordinator, my vote counted as 2 towards suggestions. I however in most circumstances did not use it as such (I usually just counted my vote as 1). Additionally, the previous rules also gave non-dev members no actual say in development. We were to listen to their opinions, but how we voted was how we voted. Our differing points of view were a small counter to this. As we progressed forward, CJ gave us leeway into using select opinions from players. This was initially restrictive to just 1 non-dev member but was expanded to include several long term veterans at our discretion.

NOW, in keeping with the original rules stipulated, we doubled the voting and gave non-dev members a vote into the suggestions. While not perfect, it moves us in a direction that gives more input to the community so that it isn't a unilateral action. My veto power to the stipulated rules is means to prevent suggestions that aren't worked out properly and need further discussion from just being approved willy nilly. This forces the Dev Team to come to a consensus to progress forward on a suggestion.

As for your scenario of me just approving what I want, you can laugh that back were it came from. The initial intent was for the Dev Team to have multiple teams that would by themselves review and approve/disapprove suggestions and the coordinator would oversee the teams and work with CJ to prioritize these suggestions for development. The coordinators vote would be to break ties and to provide counter to incomplete suggestions that are rushed through.

As I said in the initial post, there may and will mostly likely be some updates to the process to fine tune it. I have been extremely busy with work and I am trying to get things back moving. This is just a step in getting things moving. If you do not agree with it, provide an alternate solution. I have yet to see one. I see complaints and nothing beyond that. I've been more than fair with suggestions and if you think you can do a better job, please by all means reach out to CJ and ask him for my responsibilities.

[sXs]

My dear sweet fellow seamen..yeah that just happend.

First off, dont tell people what to do, they dont like that, even if they have to do it. You always ask, and thus enlist their help. They still do it, but now they feel they are doing you a favor for you. (change the frame)

Second, when a major change happens in a company (game play) you will always have people who have a hard time with change. The bast way to counter this is by once again enlisting their help. This helps to find people to champion your ideas and also make the staff part of the change, thus engaging the spirit.

Lastly in any divorce there is his side, her side and the correct side. The reason i bring this up is perspective, and no one knows what conversations were had that lead to any decision.

So why did i bring up all these points. CJ has done a great job doing a few things. First, he has enlisted the help of those in the community to help champion the game, furthermore he has allowed some dedicated players to feel a part of the direction of the game.

Second, to me the dev team is like the software that weeds out resumes for HR. Most of us have had ideas and put them out there in the ether, but that is a shart load of forum material for CJ to rummage through, so the dev team weeds through the "junk resumes" and only puts forth the ones that can do the job, what ever that is.

Lastly, no one knows why the structure is such except for the people who put it in place. Maybe Dez threatened to leave if he didnt get a special vote, or maybe he is big and bulgy like a moose and that warranted a vote for him and three more for the impressive stature.

In my humble opinion, worrying about this is may be in vane, as CJ and partners are going to do what they deem necessary for the game. When i enlist my staff, I typically already have a direction, its just a matter at what point they realize its the best way for them self, but they still feel empowered, its a win win. More business lingo... we touch all the bases, put ducks in rows, and try to get a 20k ft view to stave off aggressive mediocrity. I hope we all just had an A-ha moment with that one

We dont need all you seamen getting salty! Yeah, its happened again

Actually, I do not know what conversations were had leading up to this change. They are in the dev channel chat on slack. I read the whole thing. It seems it was pushed through by Dez and two people who are not officially on the development team.

It all started because "there were rumors" that some were not happy with the development team setup. Of course those starting those rumors wished to remain anonymous. You know,,,,, the unnamed source. Instead of those who wish not to be named stepping up and joining the team to affect change, they instead started rumors about some uprising against the development team.

Our lack of leadership decided to cave instead of addressing concerns individually and head on. You know, the way respected leaders attack such issues.

No discussion on the reasons no discussion regarding the unnamed sources concerns, only a rush to change things, You know because unnamed and anonymous sources are so reliable.

[DezNutz]

Who is a reliable source for you Feniks?

Is SHM a reliable source? Or is only your opinion reliable?

[sXs]

Feniks.. It does not really matter. If I like a feature, I'll use it and if not, I won't. If enough things happen I do not like, I'll move on and if stuff appeals to me, I will use it and encourage others to play as well. What the 'team' one or many decide to propose to development will be dependent upon what they perceive the player base wants. If they miss the mark... enrollment dwindles. Hit a bulls eye and enrollment and retention rises.

I think you are completely missing my point. CJ put the dev team in place for a reason. Now, this suggestion is simply going back towards the way things were before the team was put in place. Whether or not you personally use an approved suggestion has zero bearing g on my point.

My point is the team is not needed based on the new approval rules Dez posted. All that is needed is Dez and for people from the forums to vote yes and a suggestion is approved. ..... even if 50 others vote against it dez and 4 others still enough to approve.

I joined the dev team because of something Dez said to me. He said if you want to make it better then join. So I did. Now being on the team doesn't matter.

The approval rules are no different than they were before this post. You are IMO harping on nothing and just blowing smoke to complain.

The rules set by CJ stipulated 4 votes were required to move a topic forward. As the coordinator, my vote counted as 2 towards suggestions. I however in most circumstances did not use it as such (I usually just counted my vote as 1). Additionally, the previous rules also gave non-dev members no actual say in development. We were to listen to their opinions, but how we voted was how we voted. Our differing points of view were a small counter to this. As we progressed forward, CJ gave us leeway into using select opinions from players. This was initially restrictive to just 1 non-dev member but was expanded to include several long term veterans at our discretion.

NOW, in keeping with the original rules stipulated, we doubled the voting and gave non-dev members a vote into the suggestions. While not perfect, it moves us in a direction that gives more input to the community so that it isn't a unilateral action. My veto power to the stipulated rules is means to prevent suggestions that aren't worked out properly and need further discussion from just being approved willy nilly. This forces the Dev Team to come to a consensus to progress forward on a suggestion.

As for your scenario of me just approving what I want, you can laugh that back were it came from. The initial intent was for the Dev Team to have multiple teams that would by themselves review and approve/disapprove suggestions and the coordinator would oversee the teams and work with CJ to prioritize these suggestions for development. The coordinators vote would be to break ties and to provide counter to incomplete suggestions that are rushed through.

As I said in the initial post, there may and will mostly likely be some updates to the process to fine tune it. I have been extremely busy with work and I am trying to get things back moving. This is just a step in getting things moving. If you do not agree with it, provide an alternate solution. I have yet to see one. I see complaints and nothing beyond that. I've been more than fair with suggestions and if you think you can do a better job, please by all means reach out to CJ and ask him for my responsibilities.

I did propose an alternative in dev chat channel sir. A good leader would read up on everything that has transpired before commenting. I also addressed this directly to you in private conversation. I gave alternatives and you know it. Don't come in here and try and say I haven't. And what you fail to understand is 4 votes out of 5 people is 80%. now you add in the playerbase each getting 1 vote..... 100 people could vote but only requires 8? Seriously. That was not the intent of CJ. Dont try and sugarcoat this as something that has not changed from what it was.

[DezNutz]

So you are privy to all the discussions that I have had with CJ?

Please tell me more about what I know in regards to the intent of the Dev Team.

[sXs]

"As for your scenario of me just approving what I want, you can laugh that back were it came from. The initial intent was for the Dev Team to have multiple teams that would by themselves review and approve/disapprove suggestions and the coordinator would oversee the teams and work with CJ to prioritize these suggestions for development. The coordinators vote would be to break ties and to provide counter to incomplete suggestions that are rushed through."

Tell me this as written, is it possible for you to bypass the rest of the team. Whether you would or not does not matter, Is it possible for you alone to fulfill the development team requirement?

As written, my point is spot on sir.

4 points required from dsevelopment team.
Coordinator vote counts as 4 points.

No one can "veto" the development coordinator, but the development coordinator can veto any and every other proposal. Yes there is a check in place to prevent it, but requires 4 members of the development team. In other words 100% of everyone else is required to override.

[DezNutz]

"As for your scenario of me just approving what I want, you can laugh that back were it came from. The initial intent was for the Dev Team to have multiple teams that would by themselves review and approve/disapprove suggestions and the coordinator would oversee the teams and work with CJ to prioritize these suggestions for development. The coordinators vote would be to break ties and to provide counter to incomplete suggestions that are rushed through."

Tell me this as written, is it possible for you to bypass the rest of the team. Whether you would or not does not matter, Is it possible for you alone to fulfill the development team requirement?

As written, my point is spot on sir.

4 points required from dsevelopment team.
Coordinator vote counts as 4 points.

No one can "veto" the development coordinator, but the development coordinator can veto any and every other proposal. Yes there is a check in place to prevent it, but requires 4 members of the development team. In other words 100% of everyone else is required to override.

In the pre-this setup, the Dev Team could approve any suggestion they wanted without me voting.

My veto can be overturned simply by 4 Dev Team Members voting in a particular manner. This is no different than before. I cannot unilaterally approve or disapprove suggestions (although CJ has given leeway on archiving or disapproving duplicates). You are making a complaint about a rule that was in place before hand. You are arguing just for the sake of arguing.

Nothing changes, except the voting count doubles from 4 votes to 8 votes, the dev team vote value doubling from 1 to 2 and 2 to 4 for the coordinator, a minimum of 2 Dev Team members must vote, non-dev members having a vote, and veto ability to force the original 4 vote rule (1 dev member = 1 vote with 4 votes approving/disapproving).

I don't see the issue.

[Stan Rogers]

Feniks...currently, its not a real problem. If there were some instances where Dez shows bad judgement or starts vetoing suggestions out of hand, then you might have to re-visit this topic but for now, it is not really a problem and I'll bet the times it does becomes a problem will be far and few. At that point the player base may or, may not squawk their opinion and be more in line with your complaint.