Forgot password?
login to RetroAchievements:
User: 
Pass: 

Revision planning

AuthorMessage

RAdmin
Posted: 19 Jan, 2018 10:28
Last Edit: 04 Feb, 2018 20:24
New Revision Approval System — 19 January 2018


Summary

Here is our new revision approval process for making changes to existing sets. It includes the developer posting their plan publicly, giving time for discussion and concerns, if they are had. And when necessary a developer approval/rejection vote which will take place in Discord ( https://discord.gg/TdfC3r7).

Revisions allow for our achievement content to improve over time. They make room for a lower point of entry for newer developers to get add content to new sets (as others can re-work them later if needed), and encourages collaboration so that every game can have the best possible achievements. Revisions aren't taken lightly. Space must me make for rejecting revision plans to existing sets if the changes don't seem to be an improvement. Revisions allow for achievement sets to evolve, even if there is an active developer who originally made the set. This is a check system for devs to the community.

If you are not a developer you can still take part in the process by posting your views in threads where devs are posting their plans.

_______________________________________________________________

Any developer wanting to revise/rework a set needs to

1. prepare a detailed plan*
- Each planned addition
- Each planned demotion
- Each planned achievement rework
- Changes to leaderboards

2. Present the plan
- In the game page forum thread in full
- In #revision-voting post a link to it
- Notify the original developer(s) [no response is needed]

**The plan is automatically approved after 72 hours (if no one objects) after the above notices are posted.**

_______________________________________________________________

For a vote to take place

Anyone in the community can express their concerns or objections. Allow time for discussion and for the developer to adjust their plan if they decide to. If any concerns or objections were expressed, regardless of the developer adjusting the plan, a vote will take place.

Once the discussion has settled a vote should be posted by a developer in the #revision-voting channel.

**The vote is approved/rejected after 72 hours.**
It is pass/fail by simple majority. In case of a tie a strawpoll will be posted in Discord channel #community-news.

_______________________________________________________________

*For developers a plan doesn't need to present a plan for the following

- Reworking any content you've made or posted
- Updating badges (post old badges side-by-side to new)
- Fixing typos (no forum post needed)
- Fixing bugs
- Adding rich presence
- Updating rich presence (post backup of previous)
- Adding battery save, cheat code, or password protections
- Updating game page information and images
- Adding new leaderboards where there is none

**After making these changes always describe them in the game forum thread to notify the community and create backups.**

Posted by

kdecks
Posted: 04 Feb, 2018 20:12
Last Edit: 07 Jun, 2018 01:27
     Summary
  ══════════════

Posted for review
by - 11 Feb 18
by - 11 Feb 18

Approved automatically
by - 22 Jan 18
by - 27 Jan 18

and by - 7 Feb 18

Approved by vote
by - 3 Feb 18

Rejected by vote
-

login

login to RetroAchievements:
User: 
Pass: 
or create a new account