Open Meridian Project Forums

  • May 27, 2017, 07:59:59 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: The winds of change....  (Read 3036 times)

Daenks

  • Lord Master of the Universe
  • Administrator
  • Hero Member
  • *****
  • Karma: +46/-1
  • Posts: 438
    • View Profile
    • Open Meridian Home
The winds of change....
« on: September 22, 2014, 02:51:24 PM »

Announcement:

As some of you have relentlessly pointed out in the past, our team thus far--though doing some amazing things--has had some serious problems with our communication both internally and externally, our decision making processes, and a host of other smaller issues. We have needed clear definitions and restrictions since our inception, and today's announcement is the first part of this process.

As the de-facto team leader, I have been negligent in some of my responsibilities, mostly due to the sheer volume of items that needed to be accomplished. I have been overwhelmed, the team has been overwhelmed, and with today's release of our new team structure and charter, I hope we can overcome these challenges and move forward with our shared goals--to expand and grow our beloved game, Meridian 59.

Moving forward from today, we as a team, will have a defined software development life cycle, with pre-defined roles for individuals willing and able to contribute to the team, as well as clear accountability structures that are spearheaded by the community. For example, moderators will now be able to squelch developers, not only in game, but on IRC and the Forums as well, if/when we get unruly. We are in the process of finalizing the development cycle, but it will be made public in the very near future. Until these policies are in place, no changes will be made to the game that affect play in any fashion.

As a symbol of our renewed dedication to these tasks, I am declaring amnesty to anyone previously banned from our project, these people are welcomed and encouraged to return. I hope those who do choose to return do so with the best intentions, resulting in a net positive effect on our community; and if they choose to be a negative, they will answer to the community-nominated moderators, not to a team of developers.

We are going to need your help in fulfilling all the new roles. If any of these positions look fun/rewarding to you, please get involved.

-Daenks

Team Structure Document:

   * Lead Administrator
      * All responsibilities, restrictions, and privileges of Administrator
      * Has access to Production server backups
      * Controls, grants, and removes root/administrator access to all project resources including
         * Domain Name Registrars
         * Web Hosting
         * Wiki
         * Forums
         * Wordpress
         * Servers
      * Build Server
         * Makes changes to production workflows
      * Chooses/Removes Administrators
      * Moderates the actions of Moderators, Guides, Administrators
      * Makes policy changes
         * Consensus among active team needed for major changes
      * Is Daenks

   * Administrator
      * Handles server administration
         * Maintenance
         * Patch deployment
               * Informs community and team when completed
         * Log Rotation
      * Handles forum and game administration
         * Grants/Removes Developer/Moderator privileges as instructed by team/community
         * Enforces punishments (bans) as directed by Guides and Moderators
      * Build Server
         * Runs builds
         * Makes changes to test workflows
      * Handles wiki maintenance
      * In-game admin account, actions restricted by Admin Contract, God Log
      * Operator in IRC, receives relayed admin commands via IRC bot, has founder level access to IRC channel (can give others op/voice)
      * Developer-Only Forum access
      * Can dual-role as Designer and Developer
         * No other Lead Positions
      * Must have demonstrated long-term reliability and trust to the project as a whole for at least 6 months

   * Lead Designer
      * All responsibilities, restrictions, and privileges of Designer
      * Decides if/when changes go into production or not.
      * Must demonstrate capability of logical analysis of ideas.
      * Must demonstrate capability of personal detachment from ideas.
      * Must demonstrate project management skills.
      * Sets project milestones, game design goals
      * Creates issues (to be used to track tasks and task assignments).
      * Operator in IRC
      * No in-game privileges
         * Lead Developer psHonor string
      * Assigns tasks to Designers, Developers, Artists
      * Can dual-role as a Developer
      * Chosen/Removed by Developers and Designers
         * by vote, 75% majority

   * Designer
      * In charge of creating, modifying, or maintaining a game-system.
         * Quests
         * Items
         * Schools
         * Zones
         * Events
         * New Things we have yet to think of
         * Etc.
      * Will document and plan out changes before coding is started.
         * Includes lore to back up any proposed changes.
         * Includes projections of possible consequences, positive and negative.
         * Includes thought about interactions with other systems, positive and negative.
      * Will seek review of his or her ideas from the rest of the team members, and once team-vetted, from the rest of the community
      * Alterations made by team or community suggestion will be documented as such.
      * No in-game privileges
         * Designer psHonor string
      * Developer Only forum access, no forum moderation
      * Voice in IRC
      * Developer-Only Forum access
      * Can dual-role as a Developer
      * Volunteer position
         * must have at least 1 month of activity on the forums and IRC before access is given
         * no Development experience is required
         * must be decent at writing in English
         * must be willing to learn how and then use the wiki for all documentation

   * Developer
      * Writes code to satisfy a design document.
      * Writes code to fix a bug.
      * Submits pull requests.
      * Developer Only forum access, no forum moderation
      * Voice in IRC
      * No in-game privileges
         * Developer psHonor string
      * Developer-Only Forum access
      * Can dual-role as a Designer
      * Volunteer position
         * Must have at least two pull requests (non-simple 1 task items) approved, and have been active for 1 month before given access

   * Artist
      * Creates or obtains free artwork for use in the game
      * Developer only forum access, no forum moderation
      * Voice in IRC
      * Developer-Only Forum access
      * No in-game privileges
         * Artist psHonor string
      * Volunteer position
         * must have at least 1 month of activity on the forums and IRC and in game before access is given

   * Moderator
      * Is in charge of keeping all other team and community member's responses on-topic and without vitriol.
      * Has the authority to censure all other positions
         * Censured team/community member will not be allowed to speak in IRC, on the Forums, or publicly within the game for a period between 1 and 30 days.
         * Censured member will not be allowed to submit pull requests.
         * Censures that last more than 7 days need to be approved by a committee consisting of at least 3 team members.
         * Can censure Administrators
      * Assists Guides in community management activities
      * In-game moderator account
         * squelch only
      * Operator in IRC
      * Moderator-Only forum access
      * Can dual-role as a Developer, Guide, Designer
      * Community nominated and seconded
         * must have at least 1 month of helpful activity on the forums and IRC and ingame before nomination allowed
         * can not be nominated or seconded by current team member

   * Guide
      * Assists with in-game problems
      * Acts as community manager
         * Runs in-game events
         * Handles player complaints
               * collects objective data where possible
         * Generates media for social outreach
               * videos
               * screenshots
      * In-game dm account
         * squelch
         * can teleport to rooms, but not to players
         * fun-only spells (morph, bonk, etc.)
      * Actions restricted by Admin Contract, God Log
      * Operator in IRC
      * Moderator-Only forum access
      * Can dual-role as Developer, Designer
         * Is also a Moderator
      * Picked by Lead Administrator
         * must be a Moderator and have demonstrated long-term reliability and trust to the project as a whole

   * QA Team
      * Player title, "QA Team" and psHonor string given to members for being useful in the testing process over several months
      
   * Wiki Contributor
      * Player title, "Wise of the Wiki" and psHonor string given to members for being useful in populating, moderating and managing the wiki over several months

New Charter:

What is the Open Meridian Project about? Succinctly, we are the promise of Open Source. 101 and 102 are a decade and a half old now, and they were not constructed from the ground up with Open Source in mind. We will start fresh, with foundations lain specifically to take advantage of everything the Meridian community has to offer. Better policies for administration, bug fixes, content implementation, and player interaction are all core to what we’re trying to do.

Section 1: Atmosphere and Administrators

   1. The social atmosphere is the most important factor to a healthy server. We will constantly promote a healthy atmosphere, and by joining us, you agree to do the same.
   2. Administrators (Purple or Green Names) will not handle petty player problems. Administrators will be primarily concerned with the heath and welfare of the server at large. They will have access to the Admin window and back-end server access.
   3. Guides (Blue Names) will generally only have the power to squelch. They will not have access to the admin window, to create items, spawn monsters, become invisible, or otherwise interfere with game play in any manner. They will act as community ambassadors that hang out, enjoy their time on-line and interact with the player base in a calm and friendly manner.
   4. Squelches will be freely given, since they do not affect PvP. There will be no unending stream of troll posts and broadcasts. Action will be taken swiftly to resolve any instances of this behavior.
   5. To prevent Administrator and Guide corruption, all Admin and Guide actions are publicly logged in the God Log, which can be found from the front page of our web site. We encourage all players to review this log, and ask questions about what is going on there.

Section 2: Cheating, Banning, Account Security

   1. There will be no permanent bans for anything within the context of the game, as long as the action does not affect the server, its hosting provider, or players real lives, you will not be permanently banned.
   2. Players caught cheating, duplicating items, exploiting bugs or speed hacking will have all of their accounts (and any account they have ever logged into) deleted.
   3. This means that if your friend cheats, and has ever logged on to your account, your account may be deleted. There is no way to recover a deleted character, so please take care who you share your account information with.
   4. The cheats, hacks, or exploits will be fixed through code as swiftly as they are discovered.
   5. In return for helping us to discover and fix these problems, the caught player will be allowed to return immediately to game play on new accounts and with new characters.
   6. The caught players' actions and punishment will be posted for the world to see, with full details, and what happens then will be up to the community.
   7. We do not perform password resets for any reason. If you lose access to your account for any reason, there is no way for you to get it back.
   8. We do not condone the sale of accounts, characters, items, shillings, or any other in-game resource for external currency. Advertisement of such services will lead to your communication privileges being revoked, and could lead to your accounts being deleted.

Section 3: User Experience and Competition

   1. We will continue to place a strong priority on improving the user interface, building process, and the learning experience for new players.
   2. We will also place a priority on creating new content, this means new maps, new monsters, new systems and scenarios that will allow all players to build, compete, and have fun all at the same time.
   3. We will continue to reduce and eliminate muling in all its forms, through systems that reduce the usefulness of them.

Section 4: Content

   1. School re-balancing and completion will continue to be a big priority. We will strive to add new spells and skills to existing schools, and create new ones as needed.
   2. Expanding the world of Meridian is one of our chief goals and we will continue to add maps as we progress.
   3. Lore will remain consistent with the Meridian storyline, though we plan to advance it over time.

Section 5: Spirit of Meridian

   1. We will keep to the core spirit of the game. We realize this has a different meaning to different people, suffice it to say that we we would like a former 3do player to be able to log on today (and in the future) and be able to start playing immediately without having to learn everything from scratch.
   2. We will ensure there is always free-world PvP in some fashion.
   3. We will ensure the character progression scheme remains true to its roots.
   4. We will avoid the 'pirate server' feel, essentially we will ensure our changes are well thought out and not arbitrary additions for convenience.

Section 6: Growing the Game

   1. We will work with the Trademark holders to publish the game on Steam, GoG.com, and other game/software services.
   2. We will use social media tools and SEO to engage former and new players.
   3. We will work to make running, configuring, and customizing a Meridian server as easy as possible, in order to grow diversity.
   4. We will offer tools to potential Meridian server hosts to facilitate ease of deployment and to make quick connections to the potential player base.

Section 7: Communication

   1. We want the community involved in our decision making process. We welcome all opinions and criticism at all times. Our forums will be the primary location of this interaction, as well as in-game communication, IRC chat, and other forms.
   2. We respectfully insist that your communication with our volunteer team remain about ideas and not people. We reserve the right to moderate unhealthy, pointless, rude, or disrespectful comments.

Section 8: Rules
        1. In addition to these guidelines, players in game are also bound by the forum rules and ToS which can be seen here: http://openmeridian.org/forums/index.php/topic,4.0.html
« Last Edit: February 10, 2016, 03:51:52 PM by Daenks »
Logged
Open Meridian Administrator

Daenks

  • Lord Master of the Universe
  • Administrator
  • Hero Member
  • *****
  • Karma: +46/-1
  • Posts: 438
    • View Profile
    • Open Meridian Home
Re: The winds of change....
« Reply #1 on: September 22, 2014, 08:12:27 PM »

Edited the Moderators section slightly.

Quote
         * must have at least 1 month of helpful activity on the forums and IRC and ingame before nomination allowed
         * can not be nominated or seconded by current team member
Logged
Open Meridian Administrator

Daenks

  • Lord Master of the Universe
  • Administrator
  • Hero Member
  • *****
  • Karma: +46/-1
  • Posts: 438
    • View Profile
    • Open Meridian Home
Re: The winds of change....
« Reply #2 on: February 10, 2016, 03:52:18 PM »

Added some to the charter:

Quote
Section 8: Rules
        1. In addition to these guidelines, players in game are also bound by the forum rules and ToS which can be seen here: http://openmeridian.org/forums/index.php/topic,4.0.html
Logged
Open Meridian Administrator
Tags: