PathfinderWiki talk:Policies and guidelines

From PathfinderWiki

Policy change

Transcribed from: Forum:Revising policies

In the last few weeks, we've seen a huge influx in activity here on the wiki. And that's great! Really, I couldn't be happier about it. But along with new faces and more frequent edits, some policy revisions have come up or I'm seeing places that I think we could clarify or establish guidelines to better serve the community as we grow and evolve. There has been some talk several times on setting up a method of proposing new policies or changing existing ones, but we have never really established a way to do so to the completion of the process. Obviously this is sort of a chicken and the egg scenario, but it is what it is. To date, many of our "official" policies are a hodge podge of a single person or several people piecing together policies from various other wikis and adapting them as best as they could. I think that we need to revisit many of them and make them our own, the first of which should be how to do just that. So let's discuss it here and try to come up with a way that the community can evolve and grow without working forever under the guidelines decided on by just a few people. I want this to be an open community, so anyone who wants to offer a suggestion or participate in the discussion is welcome to do so. --yoda8myhead 05:48, 10 July 2009 (UTC)

I've given myself a fair bit of time to think the matter over, and have a few ideas. They're in no way complete, and there's plenty of room for improving them, but they'll serve to start the discussion along:
General Thoughts
  • We currently have an article for Policies and Guidelines, but in its current state it's inadequate for the project and sorely lacking in functionality. It should be directly linked from both the sidebar and the front page, most likely as part of the Pathfinder Wiki Portal. It should link directly to every accepted policy in the project, and possibly proposed policies as well. And of course it'll need rewritten once we're done with this line of discussion.
  • Whenever possible, changes in policy should be decided by consensus of those who decide to take part in the discussion. However, in situations where such agreement can't be reached it would fall to the Admins to decide among themselves the course of action that will be best for the project. If the Admins cannot come to a consensus, a vote among them should serve to decide the issue. We need to address how to nominate new Admins anyway, and expand their numbers accordingly as the project grows; you've done a great job piloting the project, Mark, and I've been able to help out when things get busy, but if the interest in the setting continues to increase we'll soon need more to handle the workload.
  • Any case of revising a current policy or proposing a new policy should be discussed at least two weeks before any decision is made, in order to allow anyone who might have something to say on the matter the opportunity to do so. As a fairly casual project, it's important to remember that even our best contributors will from time to time take a break for several days to several weeks at a time. They should have as much an opportunity as any to provide input on such matters, but we also need to try and handle such matters as quickly as possible; unless the topic is still being actively discussed, two weeks should be long enough to come to a conclusion.
Revisions to Existing Policies
  • Anyone should be able to recommend a revision to an existing policy, regardless of how long they've been part of the project or how active they've been.
  • Each policy should have it's own article, and that article should be locked. To recommend a change to an existing article, one would start a new section heading on the article's Talk Page, followed immediately by the Policy Change Template and the proposed revision. This not only creates a space to discuss the proposal, but will add the article to the category Policies with Suggested Changes. Once a desicion regarding the proposal is made, the template would be removed.
  • We should try to keep all discussion about a proposal on the article's Talk Page, and anything discussed elsewhere should be moved. If such discussions cause the Talk Page to become too lengthy, we can utilize archival subpages to alleviate the text, but I think it's vitally important that all such discussion be kept with the policy itself.
  • Changes to existing policies should not be implemented until a decision is reached.
Proposing New Policies
  • Anyone should be able to propose new policies.
  • Each proposed new policy should have its own article. The article's title should take the form PathfinderWiki Proposal:Proposal Title, and must include the Proposal Template in its body followed by the idea itself. If the proposal is accepted as Policy, the template can be changed to the Policies Template, and the article itself finalized and renamed to reflect existing policy articles.
  • Any discussion regarding the proposal should take place on the article's Talk Page, as with proposed revisions to existing policies. Once again, sub pages could be utilized to archive discussions should the prove too lengthy in the long run.
  • Proposed new policies can be enacted in the project, so long as they don't impact any policy that's already been put in place and provided their implementation is documented in the proposal's Talk Page. As long as all instances are noted, it should be a small matter for the Admins to clean up anything that needs tidying and putting such a proposal into practice is a good way to provide support for and/or against such a proposal.
--Heaven's Agent 02:22, 14 July 2009 (UTC)
That's a pretty thorough overview you put together there. I tend to agree with all of it. It's not that different from the little bit we have up now, but it is concise, clear and organized and that's what we need. Just a few remarks:
  • Linking to the policies from the sidebar is an excellent idea, I'm just not sure where we'd put it in the current setup. Either in "Contributing" or "Help" I assume.
  • Adding the Policy Change Template to a talk page would add the talk page to the category, no? In either case, the onus of then adding the template to the policy itself would fall on an admin, who would have the privileges to edit a protected page.
  • Protecting the policies seems a logical thing to do. I think we should edit the Policy Template to indicate that pages on which it appears are protected and linking to the Policies and guidelines stating to look there to find out how to propose a change to it.
  • I think the concensus > Admin > Admin vote hierarchy for making a final decision is a good one that clearly defines what role Admins will play within the governing of the project as opposed to just maintaining and enforcing the agreed-upon policies. We should try to establish Admin nomination policies in earnest, however, as we ourselves (as the two active Admins) have had our own disagreement regarding subarticles and were it to come to a vote we'd need a tie-breaker.
  • I do have concerns about your final bullet, that policies can be enacted before being officially put in place. While this seems ok in theory, on the grounds that an Admin could simply rollback all the edits of a contributor making these edits, the way people in this project (myself included) tend to get distracted and work on many things at once might make it hard to distinguish what changes were made. This is especially true if it is a minor change affecting a large number of pages or changes being implemented by multiple editors. In this instance an Admin would need to spend a lot of time weeding through the changes. That said, one of the best ways to see if a policy will adversely affect the project or to work out kinks is to put it into practice and test it out, so I do see the advantage of this element.
So let's see if we can't use this particular policy as a test of the system. I will add the Change template to the Policies and Guidelines page and let's give it two weeks. If we encounter problems in the process as we go, we will already be discussing the very policy that would need to be changed to lessen them. And We should test out the policy creation guidelines on the Admin issue.
--yoda8myhead 04:07, 14 July 2009 (UTC)}}
  • To be honest, I can see benefits for linking to the policies from both the Contributing and Help sidebars, and little reason not to include them in either. They're the foundation on which the project's built; there's little harm in giving them a little additional face time, so to speak.
  • Adding the Policy Change Template to a Talk Page will only drop that Talk Page itself into the category, but even that alone should be sufficient from a category perspective to let folks know what's going on.
  • The edit to the Policy Template to denote protected status sounds good. Composing my thoughts for this thread made me realize the policy templates could use a face lift anyway.
  • You're thoughts mirror my own regarding the Admin nomination; the subarticle discussion came to my mind as well. I'm researching what's used elsewhere and organizing my thoughts on the matter now, and I hope to have a post on the matter up by midweek. In any case, I agree that using the new policy procedures for the topic will be a good test of the system.
  • You're not the only one with concerns about that final bullet. Ultimately, though, if a new policy proposal doesn't fly against what's already in place there's little reason not to allow its use. And ultimately we'd have to go through and fix things anyway. If we ask that its usage be documented, then we might at least have something to start with if we need to revert edits.
Sounds like we've got something to run with, then. Once the Change Template's been added, I'll start transcribing our discussion here onto the Talk Page. Since it's the king of all our policies, I'm going to go ahead and make use of the Site Notice system as well, to make sure everyone realizes that we're addressing it now. Actually composing the new policy page will be a good use of our Sandboxes, too.
--Heaven's Agent 05:24, 14 July 2009 (UTC)
End transcription

(Resetting Indent)
I've set the Site Notice to direct anyone interested in contributing to the discussion to this Talk Page. -- Heaven's Agent 20:57, 14 July 2009 (UTC)

Just adding this to bump the discussion back into the recent edits page in case anyone has overlooked the site notice or forgot to contribute. Just another day before the two week period is up to discuss. Unless changes are made or concerns are raised, this proposal will become policy on 24 July. --yoda8myhead 17:05, 23 July 2009 (UTC)
Since this discussion began on 10 July, today is the two week mark. It does not appear that there are any outstanding discussions on the table, so I think we've got ourselves a new policy and as such a new way of making and updating policies. It seems to be working well in the Administrator and Canon discussions. All that remains now is to update the main policy page itself and anything linking to it that might reference the old content and we're set to go.--yoda8myhead 18:47, 24 July 2009 (UTC)
This policy has been formatted and updated to reflect the above discussion. Remaining tasks are
  • Adding language to {{Policy}} to indicate article lock (and possible facelift for all policy templates).
  • Determining the best place in the sidebar to place these policies and editing the MediaWiki code to do such.
  • Archival of above discussion to clear talk page for future use or questions regarding policy.

Distinguishing between "policy" and "guideline"

I think it is in the community's best interest to distinguish between official policies and less strict but still preferred guidelines. I think we can be more lax on less pertinent issues and will come across as more welcoming if we don't present such a LN face to n00bs. I think we can probably take a note from larger, more established projects like WoWWiki and Wookieepedia in this regard. —yoda8myhead 07:04, February 23, 2010 (UTC)

I'm open... do you have thoughts about what current policies would become guidelines? Also, how would they be different in practice? —aeakett 14:04, February 23, 2010 (UTC)

Proposed Change: Additions to revision process

Green check.svg

Changes Accepted
This section contains a discussion about changes to this policy that have been accepted.

Once the comment period is over, and discussion has settled, the template at the top of the section should be changed to indicate if the proposal was accepted or rejected. The template should include an admonition not to continue or renew the discussion whitout good reason. I'd suggest that we simply add arguments to the {{Change policy}} template, perhaps {{Change policy|accepted}} and {{Change policy|rejected}}. —aeakett 17:50, March 18, 2010 (UTC)

I corrected minor typos in your above post and linked to the suggested template.
I think denoting resolved discussions an excellent suggestion, though, I'm not quite sure what you mean by "simply add arguments to {{Change policy}}." You mean that discussion after a decision is reached should be carried out on the Template talk page instead of the Policy talk page? If so, I disagree. I think that a new revision should be suggested from step one in the specific policy discussion. If we "admonish" users from starting new discussion, we are not encouraging the community to evolve or grow. Some policies we decide on may actually benefit from changes down the road, and giving the impression that changes are final isn't something I want to do.
Additionally, the way {{Change policy}} currently works is to add pages to Category:Policies with suggested changes and we should make sure that only open discussions are maintained in this category. If we add additional variables to the template, the template should only be included when these variables are absent.—yoda8myhead 18:57, March 18, 2010 (UTC)
Thanks for the fixes. By "arguments", I meant what you've called variables... sorry for the jargon. Finally, you're right that we should be careful to make sure that category only gets added in the one specific case. —aeakett 19:04, March 18, 2010 (UTC)
I've tried to mock up the changes I've suggested here, but as with most things I try to do quickly at lunch time, it is broken. However, I think that if you look at the code, you'll get the gist of what I'm suggesting. I'll try fixing it later. —aeakett 16:57, March 25, 2010 (UTC)
OK, this has been forever, and I don't think there is any dissent. I've managed to fixed up the {{Change policy}} template, and I'm going to update the policy next. —aeakett 21:10, July 10, 2010 (UTC)


I've recently noticed the Disclaimer link in the footer points to an empty page, PathfinderWiki:General disclaimer. I've adapted a disclaimer from a similar fan project ( and propose using it as our own:

PathfinderWiki is a collaborative project to document the setting and products of the Pathfinder Roleplaying Game, using material allowed under the Paizo Inc. Community Use Policy. All information in PathfinderWiki is collected or written by volunteers and shared as a collective work by and for Pathfinder fans.

Information in this wiki has not necessarily been reviewed by employees of Paizo Inc. or members of the Pathfinder development team, Paizo's licensors or collaborators, or PathfinderWiki's administrators. PathfinderWiki cannot guarantee the accuracy or quality of the information, and any article can be modified or changed at any time by any registered PathfinderWiki member. Any wiki page has a risk of becoming vandalized or improperly altered by users at any given time; none of the contributors, administrators, developers, or anyone else connected with the PathfinderWiki in any way whatsoever can be held responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these Web pages.

As a community-operated resource, PathfinderWiki encourages all users who encounter improper, offensive, or otherwise incorrect information to edit the article in question. Any situations that warrant further involvement should be reported directly to the PathfinderWiki administrators for review.

By using PathfinderWiki, you confirm that you understand that the information provided here is provided freely under the terms of Paizo's Community Use Policy, and that no kind of agreement or contract is created between you and PathfinderWiki, between you and the users of this site, between you and Paizo Inc., or between you and anyone else who is in any way connected with this project or sister projects subject to your claims against them directly. Your use of this site does not create or imply any contractual or extracontractual liability on the part of PathfinderWiki or any of its members, administrators, or other users.

Providing content for the PathfinderWiki must be done voluntarily with no assumptions of content preservation or compensation. To comply with the noncommercial requirements of Paizo's Community Use Policy, any funds collected by PathfinderWiki must go toward maintaining the site and cannot be distributed to members, administrators, or other users. We are expressly prohibited from charging you to use or access this content.

There is no agreement or understanding between you and the PathfinderWiki regarding your use or modification of this information beyond the Community Use Policy, nor is anyone at PathfinderWiki responsible if any contributor should change, edit, modify, or remove any information that you have posted on PathfinderWiki.

This website uses trademarks and/or copyrights owned by Paizo Inc. under Paizo's Community Use Policy. It should be understood that all Pathfinder content and materials are trademarks and copyrights of Paizo Inc. and/or its licensors. This website is not published, endorsed, or specifically approved by Paizo Inc. Unless otherwise stated, PathfinderWiki is neither endorsed nor affiliated with any of the holders of any such rights, and as such PathfinderWiki cannot grant any additional rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk.

For more information about Paizo's Community Use Policy, please visit For more information about Paizo Inc. and Paizo products, please visit

--Oznogon (talk) 23:01, 17 December 2014 (UTC)

Looks good, Oznogon. I'll have my attorney spouse take a quick peek at it, just to be sure. --Brandingopportunity (talk) 16:36, 18 December 2014 (UTC)
She took a look at it and proclaims it good! --Brandingopportunity (talk) 06:18, 19 December 2014 (UTC)
Awesome, thanks! If there's no further discussion or any opposition, I'll add this on Monday. --Oznogon (talk) 20:41, 19 December 2014 (UTC)
Done! --Oznogon (talk) 22:02, 22 December 2014 (UTC)