Proposed achievements
This is a system for proposed achievements, for turning ideas into achievement ribbons.
Contents
Why
We need this system:
- To preserve good ideas and get them turned into ribbons when their proposers don't know how.
- To ensure that every new achievement is well thought out, clearly described and free of controversy.
- To block the creation of stupid ribbons (the same ideas can still be Gratuitous Ribbons).
- To ensure that newly created ribbons comply with naming conventions and are properly listed and categorized.
- To make it easy for people to find out about new ribbons.
- To save time on "we already talked about that and no one liked it" discussions.
A couple of examples: One achievement that could have used such a process is the Speed racer achievement, which to discourage lawbreaking, specifies that achievers must drive the speed limit, but is now controversial when there is no speed limit (Autobahn, unofficial road) or a very low speed limit. Meanwhile the First Geohasher award (now renamed the Earliest geohasher achievement because of this confusion) was originally intended for the purpose now served by the Virgin Graticule, but was poorly defined and ended up meaning something else.
Proposing a new achievement
Anyone can propose a new achievement. All they need to do is make a page for it, even if the page is a one line description of what the achievement should consist of. The page should be given only the category Proposed achievements. If someone has an idea but doesn't want to create a proposal page, they can put the idea on the talk page for this category and see if anyone else is intrigued enough to create a proposal.
Discussing a proposal
Others comment on the proposed achievement's talk page, or directly edit the proposed achievement, to flesh it out or to remove ambiguity. Those commenting should indicate whether they
- Support the proposal - love it, like it, approve it, feel the sport will be better for its existence
- Do not oppose - think it's a bit dumb, boring, meh, or of no personal interest, but won't hurt anything
- Oppose - there is a specific stated reason why this ribbon should not exist
- Needs work - this might be viable but has problems the way it is
Valid reasons for rejection are
- The activity proposed is illegal, offensive, intrinsically dangerous, or contrary to the spirit of geohashing. That is, no achievements for theft, vandalism, rudeness, environmental damage or the like.
- The ribbon is a subset of, or has a large overlap with, an existing ribbon, such that everyone who won one would win both.
- The ribbon is for a trivial activity that almost anyone could do at almost any geohash without preparation.
- The ribbon depends on the coordinates falling at some very specific place. Existing exceptions include Golf Geohash, Restricted Area Geohash and Pub Geohash. Golf courses and restricted areas generally cover very large areas
Passing the proposal stage
When the achievement
- has been open for discussion for at least ten days
- has a complete page including a ribbon
- has supporters from different graticules, and
- is no longer opposed by anyone
... then the Proposed achievement category is replaced by New achievement plus the page and template get proper categories and a listing in the appropriate section of the Achievements page. The person who removes it from the Proposed achievements category shouldn't be the same person as the one who proposed it, to ensure real support.
If the ribbon celebrates a cool but specific and unlikely achievement that is not overly dependent on lucky coordinates, it may be left as "you achieve it, we'll make it." It would be really cool if ...
Failing the proposal stage
If an achievement has strong opposition and the reasons for opposition are not resolved through discussion, then the Proposed achievements category is replaced with the Rejected achievements category, the reason explained succinctly on the page, and the page otherwise marked to make sure it isn't confused with an achievements page.
Falling into limbo
Proposed achievements that receive neither support nor opposition will fall into limbo and remain in the proposed achievements category forever, or until someone resurrects them just as they do now, but they will be more easily identified.
I hope this process will ensure that new ribbons are unique, celebrate the spirit of geohashing, require some effort or ability on the part of the geohasher, are achievable in different parts of the world, and be fun. It isn't much more than a codification of what is already happening in the good cases, with Boats are for sissies! achievement being an example of a proposal that was rejected for too much overlap and the Tron achievement to find wide support.
Template
The template Template:Proposal talk puts a link to the talk page if it is on a main page, or asks for comments below if it is already on a talk page.
- Support - you think this proposal should be added with zero or minor changes
- Do not oppose - you think it's boring/meh/not for you, but it wouldn't harm to have it created
- Oppose - you have a specific reason as to why this ribbon should not exist (state this reasoning in your comment)
- Needs work - you think the achievement should be created after more significant changes have been made
See Proposed achievements for more information on this process.
The template Template:Rejected puts a message box on the page, detailing the reasons for rejection and adding the page to the respective category
This achievement was proposed in the past, but has been rejected, because it was too good to be true. Please read the discussion page for more details.
As per the page proposed achievements: If an achievement has strong opposition and the reasons for opposition are not resolved through discussion, then the proposed achievements category is replaced with the rejected achievements category, the reason explained succinctly on the page, and the page otherwise marked to make sure it isn't confused with an achievements page.
For proposals that have fallen into limbo for a considerable time, you might want to add the following template:
