bounty: fix the god damn rule pages!

[I.M.O.G.]

I don't mean this in a hostile sense, but I hope it farms attention.

The rules for benchmarks are inaccurate, out of date, and sometimes the rules just don't exist. Massman posted in his mission article this year that we are trying to make the project easier to get involved and further reaching. Accurate rules are important, easy to do, and eternally neglected here for whatever reason - it is a silly problem to have.

My proposal: as a community we pledge bounties on individual rule pages.

This is how this will work.

1. I will post a date deadline for a specific rule page, and start by pledging cash.
2. Others can pledge cash as well
3. I will update this first post with Target rules page, pledges, and results
4. If the rules page is updated by the deadline, a paypal address will be shared to send the money to (money will go to the hwbot staff member who makes the edits to the rules page, or the hwbot general fund, at the staff members discretion)

Bounty #1:

UCBench Rules page - http://hwbot.org/news/4591_application_33_rules/

Current Bounty:
I.M.O.G. - $5
K404 - $10 ($5 bonus for clear consequences for rule violations - What gets blocked? What gets a ban? Etc)

Deadline: July 27th, 2012

[Sam OCX]

Obviously, Massman gives a negative bunny about the rule pages as he's too busy sleeping in Finland.

[K404]

Anything that helps get a comprehensive set of rules, with a list of consequences for willful/repeated/malicious rule-breaking THAT ARE ENFORCED with 100% equality gets my support.

Maybe this comment is now slightly inaccurate or out of date, but I would also like more HWB staff to have access and "permission" to use the ban button, especially when it comes to established HWB users.

[Mr.Scott]

The rule pages are an easy fix. Should have been done as the rules/requirements changed.
The code bugs are a bigger concern. They're multiplying faster than they're getting fixed.
Before anybody gets cranky reading this, yes I know it's only a 2 guy operation, but the existing problems should take precedence over any new projects.

[Bobnova]

It certainly seems like a fairly easy fix.
First you tie massman to a chair, then you torture him to force him to recite the real rules (I think we all know the difference between the rules in text and the Real Rules by now), then convert them to text.

You'd think they would have been fixed by now, they've only been out of date since... oh I don't know, 2010?

I too feel that the current bugs need fixing before additional features are added.

[ARandomOWL]

Originally Posted by Mr.Scott

Before anybody gets cranky reading this, yes I know it's only a 2 guy operation, but the existing problems should take precedence over any new projects.

Originally Posted by Bobnova

I too feel that the current bugs need fixing before additional features are added.

I have nothing further to add.

[I.M.O.G.]

Same.

[knopflerbruce]

We did a fair bit of work on this in January, but nothing has been discussed since then. I just bumped that section, let's see if something happens. I think some of the issue is that no-one knows who is in charge of what Either that, or we're all waiting for massman to do it

[Janus67]

+1 to get the official rules page updated. My team has had various submissions get deleted because they didn't follow the hidden non-posted rule set.

[I.M.O.G.]

I've been at the community leadership summit 2012 in Portland, OR all weekend. I just hosted a conference session which paid homage to the classical artist "ludacris"; it was titled "move b****, get out the way". It's focus was lowering the barriers in your community to empower your members. One of the key takeaways from our discussion was that as community managers, if we do not delegate well and clearly distribute authority, we can become our own worst enemies and hurt our communities.

If you are into reading, if you run a community, or want to start a community, check out "the art of community" by jono Bacon. He manages the Ubuntu community, and the book is freely downloadable.