DPChallenge Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
==== Site Council Policies ====

Document covering all the SC policies that we've not got written down anywhere yet :o)

=== DQs ===

What we DQ for, what we don't, and why.

== Self DQ's ==

Most self-DQ requests will come in via the ticket system. When you receive such a request, you should first confirm that the person is eligible. To do this, go to the photographer's profile and check whether any of their 24 entries prior to the one requested were disqualified (be sure to check "show greens" to confirm entries currently in voting). Also, check whether the requested entry is currently being reviewed for disqualification.

If the user has a disqualification in the past 24 entries (the current entry makes 25), the photographer is ineligible for a self-DQ. It is possible to grant an exception to this in highly unusual circumstances, but this can be done only after Site Council discussion, and typically involves penalties to the photographer. Such circumstances include situations where the photograph presents a legal or employment issue for the photographer, or for a model appearing in the photograph. These same conditions also apply to requests to remove images from completed challenges.

A normal DQ takes precedence over a self-DQ request. If the entry is already under review for disqualification, the request cannot be honored until the DQ review is complete.  There have been occasions where the photographer himself admits a rule violation (an example: s/he accidentally submitted an advanced edited pic to a basic editing challenge).  In cases such as these, leniency is warranted provided that the photographer meets the other criteria for a self-disqualification.  If in doubt, bring it up in the forums for debate.

If the person is eligible, please reply to the photographer to confirm that they are aware that the self-DQ counts as a disqualification, and that additional DQ's in their next 25 entries would lead to suspensions as outlined in the Challenge Rules (if the person has confirmed that they are aware of the penalties in their request, you can skip this step). Once we receive a confirmation back from the photographer, the request may be processed via the disqualification system.

In the event of a DQ under this procedure, a post MUST be made to the relevant Site Council challenge thread alerting the rest of Site Council to the DQ. 

  * Mulligans, copyright issues, and suchlike

== Unilateral DQ's ==

A brief list of guidelines for processing DQ's is posted at the bottom of the DQ processing and voting pages. DQ's typically require a unanimous 6-0 vote or a majority vote (after SC discussion) for split decisions. There are limited cases, however, where it is appropriate to disqualify an entry without waiting for the required vote. Any Site Council member may disqualify an entry without waiting for the usual 6-0 vote if:

  * the photographer is requesting DQ on his or her own entry, and is eligible for a self-DQ.

  * the entry clearly violates the Nudity section of the Challenge Rules.

  * the entry clearly violates the "no added text" section of the Challenge Rules (example: a copyright statement appears on the shot).

  * the entry clearly violates any of the following sections of the ToS: 4.2(ii), 4.2(v), 4.2(vi), 4.2(vii), 4.3(ii).

  * in the opinion of the Site Council member effecting the DQ, leaving the entry in place for the length of the typical DQ process will cause harm to DPChallenge or to any person.

If practical the Site Council member effecting the DQ should attempt to contact one or more other SC members for discussion (via phone, IM, etc). If this is not practical or no one else is available, the DQ may be processed without further discussion.

In the event of a DQ under this procedure, a post MUST be made to the relevant Site Council challenge thread alerting the rest of Site Council to the DQ. 

== Disqualification Announcements ==
If a highly-placed image (10th or above) is disqualified after the challenge results are announced, the person who disqualifies the image should post an "Administrator Announcment" thread with the title "[Challenge Name] Results Recalculated."  The post should explain the situation (i.e. "The 4th place image in [challenge name] has been disqualified for [whatever reason]."  The rest of the post is up to the individual but normally includes a congrats to the new placers (especially if a ribbon is involved) and perhaps a reminder of how the disqualification could have been avoided.  Review the Results Recalculated threads in the Administrator Announcements forum to get the idea.

When to post an announcement is relatively fluid.  If a low-scoring image is disqualified, it probably does not need an announcement.  However, if it is an image that has generated some discussion or controversy in the forums, an announcement may be appropriate.  Use your best judgment.  :)

=== Validations ===
== Pre Challenge ==
Validations are generally not accepted before a challenge goes into the voting stage.  Users can send an original via the ticketing system ahead of time if they will be absent or unable to respond to requests while voting is in progress.  An SC member should confirm receipt of the original by replying to the ticket and leaving it "open."  When the challenge goes into the voting stage, an SC member can upload proof on the user's behalf and validation will proceed normally.

== During Challenge ==
If a voter or voters requests review of an image in a current challenge, the image in question will appear in the "DQ Requests" page for that challenge.  SC member should review the image based on the voters' comments and vote on the image (DQ, No DQ, or Request Proof "RP").  If an image receives 3 "RP" votes -- even if there are other DQ or No DQ votes-- the person casting the third vote should click the "Request Proof" button.  This moves the image into the "Pending Response" queue for that challenge.

Once the proof file for the image has been received, the SC members review the original file as compared to the final entry and votes either DQ or No DQ.  If there are 6 "No DQ" votes and no DQ votes, the image can be "validated."  The SC member casting the 6th "No DQ" vote should press the "Validate" or the "Validate with Note" button.  If the "Validate with Note" button is selected, the voting page for the image will display a "This image has been validated" message for voters to see.

NOTE: An image is ONLY validated with a note if someone OTHER THAN THE PHOTOGRAPHER has requested validation for the image.  If the photographer requests validation of his or her own photograph, it does not receive the validation notice on the voting page.  This is to prevent individuals from requesting validations unnecessarily.

== Post Challenge ==
Images can still be reviewed up to a week after the end of the challenge (i.e. while that challenge is "on the front page.")  The top 5 finishers for each challenge will automatically be sent a request for their original files.  SC members should review the originals and vote DQ/No DQ accordingly.  Generally, images that are validated after the voting ends (including top 5 finishers) do not receive a validation notice.

=== Suspensions ===
==Types of Suspensions==
A user can be suspended from the site in any of the following ways:
  * Complete Site Ban
  * Cannot Post in Forums
  * Cannot Submit to Challenges
  * Cannot Vote
  * Cannot View Entries
  * Cannot Send Private Messages
  * Cannot Comment On Images
In general, a suspension is enacted only after discussion of the entire SC has occurred and an appropriate suspension type and length has been decided (suspensions due to DQs are discussed below). Once the punishment has been agreed upon, an SC member will enact the appropriate suspension from the user's profile page.

After a suspension has been enacted, the SC member should create a ticket on the user's behalf and then respond to the ticket explaining why the suspension was made.

Occasionally, extreme circumstances warrant enacting a suspension unilaterally.  Cases like these include forum bombing (a user goes berzerk and posts tons of messages at once) or a new registered user immediately posts an obvious Spam message to the forums.  In these cases if you are the only SC online (or the first one to catch it), enact the suspension and then start a user thread (or post to an existing user thread) to explain what happened and why you did it.  Use your best judgment and you should be fine.

In the case of a Spammer, it has been the practice of the SC to just enact a complete site ban on the user.

==Suspensions Due to Disqualifications==
If a user receives a disqualification that results in a suspension (example: 2 DQs within 25 challenges warrants a one-week suspension from submitting to challenges), the site will automatically generate a ticket in the Ticketing System.

The SC member who claims the ticket should go to the photographer's profile page and click the "Edit Suspensions" link on the left-hand side of the screen.  He or she should then check the "Cannot Submit to Challenges" checkbox and ensure that the "Through" date is set correctly (the default is one week; longer suspensions require changing the date accordingly).  A note should be included in the memo box below that indicates why the suspension is in place.  Clicking the "Update Suspension" button will enact the suspension for the user.

The SC member should then respond to the ticket and explain to the user why he or she has been suspended.  Enacting a suspension via the user's profile does not send a notification to the user automatically (I checked this -- muck).


=== Forums ===

==Locking Threads==
Threads should only be locked under the following circumstances:
  * Duplicate thread exists; in this case, post a link to the original thread before locking the dupe
  * The discussion has become too heated; before the thread is locked SC members should have posted warnings to try to stem the conversation
  * The discussion is no longer valid. For example, once an item has sold in a F/S thread, you should update the thread title and lock the thread.


==Hiding Threads==
If a thread is a blatant violation of the Terms of Service, it can be hidden immediately.  If it is an obvious spammer starting a thread, please hide the thread and start a discussion about that user by following the link on the profile page (and deactivate the user). It is important to note that the "Hide Thread" option is listed at the bottom of the threads under administrative options. If you want to "ignore" a thread, hiding is NOT an accepted practice. Instead, please use the "ignore" option at the top of the thread. :)

==Announcements==
Announcement threads can only be started by Administrators or SC members.  These should be used sparingly -- for announcements about new rulesets, special challenges, or anything else that affects the running of the site.  In general, the discussion in these threads should be allowed to continue as in a normal thread.  Announcement threads show up as "green" threads on the home page and the Community page.

==Conflicting SC Opinions==
In the SC forums, hash it out until someone is bleeding and imminent death is forthcoming. :)  In the public forums, smile, nod, and then take it to the SC forums.  Seriously, rather than publicly disagree on policy opinion in public, it is better to bring it up behind the scenes.  Any small disagreement, can and will be held against us. 

It's perfectly acceptable to participate as yourself in the forums.  Sometimes it may be necessary to delineate that you are expressing your PERSONAL opinion and not that of the SC.  However, experience has shown that it's hard to separate the "SC" you from the "Member" you, so you are urged to use care when throwing your weight around.  :)

=== Form Letters ===
  *  **Letter for user violating TOS with regards to idiotic commenting
**
//[User's name here],

It has come to our attention that some of your participation at DPC has been less than constructive. More specifically, you are in violation of the following Terms of Use:

4.1 Generally, you must use the DPChallenge.com Service in a manner that demonstrates good taste and respect for the rights of DPChallenge.com and third parties.

4.2 You will not use the DPChallenge.com Service to post content or to design, manufacture, market or sell a Product that (ix) is generally offensive or in bad taste.

Many of your comments contain foul language, are offensive and/or generally insulting and contain no form of constructive feedback. Please carefully consider your approach to commenting on photos and make sure that you do so in a way that is respectful of the photographer and other members of the site.

You may also notice that your "votes cast" tally is significantly smaller than the actual number of votes you've given. This is because the "vote scrubber" has removed over half the votes you've cast, having deemed them suspiciously low. Out of xxx votes cast, over xxx have been "x." While your vote is your choice, we would hope that you could find some redeeming value within hundreds of photos. If not, perhaps DPC is not the place for you.

We welcome your continued participation at DPC but request and expect that it be done in a constructive and courteous manner. The Terms of Use may be reviewed here: http://dpchallenge.com/terms.php

[your name]
Site Council//

  * Suspension Notices
    
  * Forum Abuse Notices
  * Critique Club (optional)
  * Username Changes

//Now that you've had 24 hours, are you sure that you still want to go ahead with this name change? Just to remind you, you will have to keep this new username for at least the next 6 months, and your old username(s) will always be displayed on your profile. If you're still OK with this, reply to this and we'll make the change for you.

Regards,
DPChallenge Site Council//

  * etc

=== Tickets ===
  *  When to Answer and When to Wait
       Generally, if you know you can answer a question, correctly, claim the ticket and answer as soon as possible.  You can also offer your opinion by commenting.  If it is a user wanting an opinion on a picture, it is better to wait until 4 or 5 opinions (more, ideally) have been given.  <karmat's opinion> In the interest of simplicity, if someone has started corresponding with a user based on a submitted ticket, let that SC member continue answering and corresponding until they can no longer do it (or wants to do it).<end opinion>
  *  Username changes
        Wait 24 hours to answer any of these tickets.  Then, remind the user that the new name will remain in effect for 6 months.  If they still want to change, go ahead and change it, but start a thread (or add to an existing one) for that user.  <I think this is what we decided?> See above for the form letter.