| abstract | - New projects do not need to be approved by the community. However, in order to ensure that projects are being actively worked upon instead of being largely ignored, a few key guidelines have been established to help users when they are thinking of creating a new project. 1.
* Check to see if there are any current projects about your topic. If you are looking into creating a project based on the Unfication Wars that created the Galactic Republic but there is already a Unification Wars project, it is strongly recommended that you bring your ideas to that project instead of creating a competing one. 2.
* Generate interest among people you know on the wiki before creating the project. A project should have, at the very least, three people in it to warrant being a FanonProject as opposed to a non-FanonProject personal storyline. 3.
* Develop a set of goals for the project. What these goals are will depend on the project members, but it should be focused on the amount of articles, amount of good and featured articles, and other things of that nature. 4.
* Once the project is created, begin a discussion about the basic storyline so the members can decide where they want to go with it and what they want to accomplish before conflicting articles are written by the project members. 5.
* The project must not be part of any user's existing personal fanon storyline, as it is meant to foster community collaboration in the creation of a new storyline that all members can claim ownership over. 6.
* Create a project talk page template identifying it as a FanonProject. These templates should be of professional and engaging quality. 7.
* Users cannot be barred from entering the project, as all projects are open to anyone who wishes to join. Project leaders have no authority to remove any user from the project for any reason, nor do they have the authority to tell someone that they cannot join without the approval of the project leader. 8.
* The user who creates a project will, by default, be considered the project leader of said project. The project leader is not the boss, nor is he or she the one to make all of the decisions or give a final approval on all of the decisions. The project leader does not have anymore influence than any other project member. The role of the project leader is to essentially act as a discussion leader, ensuring that the discussions stay on track and that the FanonProject guidelines, as well as the individual project guidelines, are followed. If a majority of project members disapprove of the project leader's handling of the project, they can remove him or her as the project leader and appoint someone else.
|
