The Sims Wiki talk:Community Portal/Archive 12

Archived page

This page is an archive. Please do not edit the contents of this page. Direct any additional comments to the current talk page.

Archive Pages for The Sims Wiki talk:Community Portal:
1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 · 9 · 10 · 11 · 12 · 13 · 14 · 15 · 16 · 17 · 18 · 19 · 20

New background?

There has been a bit of discussion on the IRC channel about the background; many users feel the repeating PlumbBobs are boring. I'd like to propose we update the background... to what, I don't know. I particularly like the background on Les Sims Wiki, and after a short discussion about it I asked a question on the forum, which you can view here. What I said asks what program they used... really couldn't think of a question, honestly. I just wanted more information on the background, haha. Does anybody else think that the background should be changed, and if so, are there any suggestions to what? Don't forget, one or more users can create background, so it doesn't necessarily have to be an image already on the web. Thanks, --Bleeh^{(talk) (blog)} 01:18, April 8, 2011 (UTC)

I agree with Bleeh. Our plumbob background is getting a bit dull, and it would be good to refresh it. With what, I don't know. I do like the one on Les Sims Wiki, but I don't think we can use that without getting them angry at us. Anyone have any ideas? --WoganHemlock ^{(talk) · (blog)} 01:03, April 11, 2011 (UTC)

I agree with Bleeh too. The PlumbBobs are repetitive and boring. Maybe our background could be the Sim images on the box art of TS3, or maybe a static image of Sunset Valley or something? —Random Ranaun ^{(Talk to me!)} 04:27, April 23, 2011 (UTC)

Hmm... I don't know what we could make it. I'll have a look, and post some in a few days. --WoganHemlock ^{(talk) · (blog)} 08:02, April 23, 2011 (UTC)

I found this on Community Central. Wikia has a team which can be used to redesign main pages, themes, etc. If we can get some ideas, we could ask them to implement a new background for us. --WoganHemlock ^{(talk) · (blog)} 00:26, April 27, 2011 (UTC)

Addressing The Sims Medieval Wiki split

I've mostly maintained my silence on this issue, at least here on TSW. However, as I was partly facilitating the merge of The Sims Medieval Wiki into this one, I feel it is now my responsibility to bring you all up-to-speed and determine a way to move forward.

The Sims Medieval wiki is not merging with The Sims Wiki at the present time, and is not likely to support a merge in the foreseeable future. Within the past few weeks, an active and passionate editor base has developed there, and the new community has decided - some more vocally than others - that they wish for The Sims Medieval Wiki and The Sims Wiki to remain separate. As a bureaucrat here, I respect their right to make that decision and ask that our community members and administrators respect that right as well.

Unfortunately, a divisive exchange, largely between members of this wiki and the Medieval wiki has arisen as has the debate over merging or not merging. To ease this, I would like to make the following fact as plain as possible: The two wikis are not merging, and no amount of debate will change that until the communities of both wikis agree to merge; this is a simple and unchangeable fact. Further, continuing to give the suggestion that a merge should happen is counterproductive when the community there has resoundingly rejected the idea.

As a bureaucrat, I have tried not to put my direct opinion or ideas into community decisions. However, at this point I think that we have reached an impasse and are seeing a breakdown in cooperative, constructive communication between this wiki and The Sims Medieval Wiki. To that end, I am formally proposing the following, to be agreed upon by the communities of both The Sims Wiki and The Sims Medieval Wiki:

1. The Sims Medieval Wiki and The Sims Wiki are affiliate wikis that will cooperate when necessary, but will also focus on information relevant to the wiki's respective series. Neither wiki is superior or inferior to the other - the wikis are sister wikis, not parent/child wikis.
2. The Sims Medieval Wiki and The Sims Wiki agree that, aside from broad articles that cover in a topical nature information highly relevant to the topic of the other wiki, or articles which are of importance to the topics of both wikis, that neither wiki will feature articles highly relevant to the other wiki's topic. For instance, The Sims Medieval Wiki may have an article describing The Sims series of games, but may not have an article for Miss Crumplebottom, as the topic of that article is highly relevant to the topic of The Sims Wiki. The Sims Wiki may have an article describing (topically) The Sims Medieval, but may not have an article describing the Judgement Zone as this article is highly relevant to The Sims Medieval Wiki's topic.
3. Members who are predominantly associated with one or the other wiki will not overly interfere in discussions or decisions made by the sister community.
4. Adoption of this agreement, as well as changes to this agreement, must be supported by community consensus from both wikis.
5. Merging of the two wikis may be considered from time to time, but the decision to merge must be highly supported by both communities before a merge may take place. If a proposal to merge the wikis is unsuccessful, a similar proposal may not be made for at least six months.

So my question to you all: Do you agree or disagree with the proposal? Please also leave comments. -- LostInRiverview ^{talk · blog} 07:21, April 9, 2011 (UTC)

I agree with this proposal. The merge discussion on TSMW did break down significantly and they're better off being their own wiki. Lost Labyrinth • (c) • (b) 08:20, April 9, 2011 (UTC)

I agree. Zombie ^{talk • blog} 08:28, April 9, 2011 (UTC)

I partially agree with the proposal. The only part I don't agree with is 2. If anything, TSW should be able to cover anything in The Sims Medieval. Take the Final Fantasy Wiki for example. They cover both FFXI and FFXIV, even though those games both have their own wikis. So, the Final Fantasy Wiki does cover them, but their individual wikis go into much more detail. I think that is what should happen here. —Random Ranaun (Talk to me!) 15:14, April 9, 2011 (UTC)

I partially agree with the proposal, and generally agree with the point Random Ranaun raised above. I think we can cover, or at least mention, something, and then link to a (hopefully) more detailed article on The Sims Medieval Wiki. Since there's not going to be a merger, redundant coverage is redundant, and detailed articles are likely to diverge over time. Still, people will probably look here for info about The Sims Medieval, so we should be able to say something about aspects of it, even if it's mostly to say that more info is available elsewhere. Dharden (talk) 16:05, April 9, 2011 (UTC)

I partially agree with the proposal and I agree with the points Random Ranaun and Dharden mentioned. --Bleeh^{(talk) (blog)} 16:17, April 9, 2011 (UTC)

Response: The TSMW discussion of this proposal in some ways addresses the idea of content sharing. A user there proposed a system which, if thought out correctly and if it is actually possible through MediaWiki, would be (I think) a good settlement to having articles hosted here. If that system described were set up, it would be much easier for us to refer or redirect users looking for Medieval information over to TSMW based on what they search for. I'm not sure I'm quite doing that person's idea justice, so go over to TSMW and take a read. -- LostInRiverview ^{talk · blog} 17:00, April 9, 2011 (UTC)

I agree and mostly with Random Ranaun's point. --Guilherme Guerreiro (talk here) 10:02, April 10, 2011 (UTC)

I agree with LiR, but disagree with Random's point. Ѧüя◎ґ 21:17, April 10, 2011 (UTC)

I agree with LiR, except for point two, as we should be able to write articles on The Sims Medieval, as it is a sims game and their wiki is not well known. I think Random's point is a good idea, and agree with it. we should have a redirect system. --'''WoganHemlock ^{(talk) · (blog)} 09:14, April 11, 2011 (UTC)

Update

I'd like to re-activate this conversation. I need to know, however, if the community will support this proposal if the second point is removed? I think we should reach some sort of formal agreement soon, and if that means waiting before we resolve specific content questions, I think that's acceptable. What are your thoughts? -- LostInRiverview ^{talk · blog} 05:19, May 5, 2011 (UTC)

If we remove point two, I don't see any problems with the proposal. --WoganHemlock ^{(Talk to meeee!!)} 05:23, May 5, 2011 (UTC)

In case point 2 is removed, is see a bright future for both of the wikis. \_Andronikos Leventis ^Talk 16:39, May 5, 2011 (UTC)

Fanon policies

This discussion has been moved in its entirety to the Creation Policies talk page. -- LostInRiverview ^{talk · blog} 08:04, May 29, 2011 (UTC)

Sims YouTube Video Contest

I was recently notified that we have a YouTube account, which made me think that maybe we should use it. It's only a rough idea, but I thought we could have a contest where users make videos using the Sims games and upload them to the site. We could then have a contest, with awards such as most viewed video, highest rated video, etc, as well as awards voted by for the wiki community, that is, users here. The winners of the different categories could be rewarded with a special userbox or something similar. So, the question is, what does the community think about this? --WoganHemlock ^{(talk) · (blog)} 04:32, April 26, 2011 (UTC)

I really like the idea. --Zombie ^{talk • blog} 09:40, May 8, 2011 (UTC)

Yeah, it would be something good for the community. The only issue I can think of is a poor connection speed to upload the video to a server and/or a data cap, as some countries (*cough*UK*country*) employ them, reducing internet usage. Other than that, I'm in favor of this. Lost Labyrinth • (c) • (b) 10:04, May 8, 2011 (UTC)

So, if the idea is put forward, I was thinking we hand out awards, similar to the fannies idea which was proposed a couple of months ago. The only problem that I could see is no one submitting videos, but I suppose we could only have a few, and forget the category thing. I hope it doesn't end up like the first fanon logo contest, though. --WH ^(Talk) 05:15, May 9, 2011 (UTC)

Staff Page

I noticed we seem to lack a staff page on this wiki. I realize that there is a small page that lists the admins, however, this page is different. It includes a list of active rollbacks, active/semi active admins, and bureaucrats (active or inactive, they still must be credited). I have seen these kind of staff pages on a lot of wikis, and it would make us look more professional, I believe. --XoTulleMorXo (Talk and Contributions♥) 01:05, April 30, 2011 (UTC)

I agree with this proposal. It would make it easier for new users to find admins, crats, etc. If this does get created, I suggest that if we do make such a page, we place a link at the top of the main page, so it will be easier for users to find it. --WoganHemlock ^{(Talk to meeee!!)} 01:19, April 30, 2011 (UTC)

So, it seems this page is more or less a staff page. I suppose that makes this discussion pretty pointless, although I do think we could put a link to it on the main page. --WoganHemlock ^{(Talk to meeee!!)} 09:28, April 30, 2011 (UTC)

Yes, but it doesn't include rollbacks or fanon admins. I am sure that a staff page is really needed for this wiki now, since it is growing and so does the staff number.|_Andronikos Leventis ^Talk 16:01, May 1, 2011 (UTC)

According to this blog, Auror is working on a page, which is here, that is more or less a staff page. I suggest we slightly modify it to include rollbacks, and we can use that. --WoganHemlock ^{(Talk to meeee!!)} 05:42, May 2, 2011 (UTC)

I think we could just use Auror's staff page and, if the community agrees, adding a list of users with the ability to rollback edits. Though, I can think of many disadvantages to that so I support continuing to use the Administrators page, or Auror's staff page as it is currently. --Bleeh^{(talk) (blog)} 23:53, May 2, 2011 (UTC)

I agree with the points made above. I don't think we really need a page with the rollbackers. Lost Labyrinth • (c) • (b) 06:22, May 3, 2011 (UTC)

I believe that we don't need a page for rollbackers, but not because they don't work hard and such. Zombie ^{talk • blog} 16:26, May 3, 2011 (UTC)

I suppose you're right. Let's keep it the way it is. --WoganHemlock ^{(Talk to meeee!!)} 00:14, May 4, 2011 (UTC)

If you say so, I just don't think they get credit. But, whatever. --XoTulleMorXo (Talk and Contributions♥) 01:16, May 4, 2011 (UTC)

Well, they do get the credit of being called more-trusted members of the community, and they should know, and most of them do, that we value their hard work and presence. And before anyone asks why admins "get credit", the page exists so that people can easily see who is active, inactive, and which admin they need to contact about a certain thing they need help with. Another thing: If we do have a page for rollbacks, newbies will think that they have administrator tools and will report vandalism and arguments there instead. Yes, we can make a notice, but to tell you the truth people don't read, understand or care about those things, so they'll ignore it. --Zombie ^{talk • blog} 13:13, May 4, 2011 (UTC)

Fanon-sysop class

I think that the time has come to discuss the creation of a fanon-sysop user class. First of all, for those who aren't familiar with user classes, they are groups of users who receive special abilities, and can be seen here. There are user classes for rollbackers, administrators (sysops), and bureaucrats. When the applications for Fanon admins were opened, we did not have a user class for them, so, they were just placed in the sysop user class. Therefore, they received the same rights as regular admins. While I did not have a problem with this at first, I began to get concerned when Fanon admins began applying for regular administratorship. Since they technically already had the same rights, I could only see the process as moot, and I don't think it's fair for them to apply again for something they already have. So, that's why I'm proposing that we create a fanon-sysop user class. If we proceed with its creation, I have thought of a set list of abilities that Fanon admins would receive. Now, I believe that fanon admins should receive just enough abilities to manage the Fanon namespace, so that they won't end up losing sight of their objective and start spending all their time editing canon pages. I am not sure if all of these are possible, so please, bare with me.

Deleting fanon pages: Fanon admins should be able to delete fanon pages that do not meet our standards. This does not mean deleting all articles, just fanon ones.

Protecting fanon pages: Fanon admins should be able to protect fanon pages from being edited by non-admins, especially if the fanon page is repeatedly vandalized. This does not mean being able to protect all articles, just fanon ones, although they should be able to edit protected main articles.

Renaming files: Fanon admins should be able to rename files, especially because users will most likely end up uploading badly named files, usually starting with "snapshot" or "screenshot."

Reverting (rollbacking): Fanon admins should already have this since they would have applied for rollback rights before.

I'm still not sure if they should be able to block users or not. So, what do you think about creating a fanon-sysop class with these abilities? —Random Ranaun ^{(Talk to me!)} 04:17, May 4, 2011 (UTC)

I think part of the versatility of the current setup is that fanon admins can take over the role of administrators when necessary, if for instance all the regular admins or bureaucrats are offline. I think an easier solution (and a more preferable one) would be to dissolve the Fanon Administrator positions, make our Fanon Administrators admins in full, and delegate them as our designated Fanon leaders, as a condition of them accepting their position. -- LostInRiverview ^{talk · blog} 06:15, May 4, 2011 (UTC)

I agree with LiR, as admins are not always around, and fanon sysops could help out with their duties, e.g. blocking mass vandals, etc. Also, I don't feel that wikia would be willing to make a new user class for just one wiki. --WoganHemlock ^{(Talk to meeee!!)} 08:12, May 4, 2011 (UTC)

Well, I don't agree. I mean, I like our Fanon Admin system. The Fanon namespace is big and important enough to have it's own list of admins, and I think it's good for Fanon Admins to stay separate from regular Admins. If we dissolve the Fanon Admin positions, and make them regular admins, where would they edit? If we do that, then our admins would most likely just edit either the main articles or the fanon ones, leaving the other in the dust. Also, if we do combine them, they would have a large array of articles to edit, whereas if they stayed as Fanon Admins, they would just have the fanon articles to worry about. And Wogan, it's okay, they've created plenty of user classes for other wikis before. —Random Ranaun ^{(Talk to me!)} 11:47, May 4, 2011 (UTC)

I think we should merge the two sysop classes. Even though I have been promoted to a full time admin, I still delete fanon as well as fix fanon pages where neccessary. It would also make things a lot easier for when other sysops aren't about. I think this is the best option we could go for. Lost Labyrinth • (c) • (b) 15:20, May 4, 2011 (UTC)

If an administrator has in their responsibilities a duty to monitor the fanon namespace specifically, then Bureaucrats would be able to discipline them if they weren't fulfilling that responsibility. Also, the way you talk RR, it's as if you don't want a fanon administrator to ever edit anything else on the wiki - administrators are members too and should be able to edit anywhere they want. -- LostInRiverview ^{talk · blog} 16:43, May 4, 2011 (UTC)

LiR, I'm not saying that they shouldn't be able to edit anywhere else on the wiki, I'm just saying that their main priority should be to maintain the Fanon namespace, and they should only have admin powers on the FN. Since the Fanon Namespace has different policies and guidelines, so, it should have it's own admins. However, the fanon admins should have less abilities than full admins, but more than rollbackers. So, they should have less abilities, but just enough to manage the Fanon namespace, especially in the absence of a full administrator. —Random Ranaun ^{(Talk to me!)} 20:40, May 4, 2011 (UTC)

I don not really agree with RR's point. Fanon admins should be as handy as others, a merge seems to me the best option. Thank you. --Guilherme Guerreiro (talk here) 20:43, May 4, 2011 (UTC)

I agree with what RandomRanaun is proposing. In response to WoganHemlock saying that he does not believe that Wikia would create a user class just for one wiki, I believe that each Wikia is allowed to request up to a specific number of user classes just for their wiki. --Bleeh^{(talk) (blog)} 03:15, May 5, 2011 (UTC)

After reading the comments, I think we should go for a merge of the two classes, or leave it the way it is. --WoganHemlock ^{(Talk to meeee!!)} 04:22, May 5, 2011 (UTC)

As a resolution to the question of whether Wikia can/will do this, I know as fact that something similar to this has been done for other wikis. So it's not a question of if it can be done, but if it should be done - I don't believe that it should, and it seems that others agree with me. -- LostInRiverview ^{talk · blog} 05:13, May 5, 2011 (UTC)

Well, I don't see why we can't merge the sysop class into normal admins, and their task is specifically Fanon related, but not restricted to it, like me with the newsletter, and Bleeh as a community director, etc. Zombie ^{talk • blog} 15:18, May 5, 2011 (UTC)

Well, as the only active fanon admin, I do think we should just merge the fanon class with the full sysop class. I still do want full access to the original sysop tools I.E. blocking, deleting articles, deleting redirects and all that. [Ѧüя◎ґ]

FWIW, the full sysop tools which are used everyday on TSW are applicable to fanon admins. If we did put restrictions in for fanon admins and there was an issue in the mainspace that needed sorting urgently and a fanon admin, with restricted rights, was the only sysop about, how could it be sorted effectively? This is why I think we should merge the two classes, it just makes things a lot easier. Lost Labyrinth • (c) • (b) 11:04, May 7, 2011 (UTC)

We have a lot of sysops and bureaucrats, so I don't think we have to worry about that. —Random Ranaun ^{(Talk to me!)} 20:06, May 7, 2011 (UTC)

Consensus

This section is for gathering consensus for the idea put forward by Random Ranaun above. Please state your specific reason(s) for support/opposition/neutrality/etc. As Random Ranaun proposed the idea, he is obviously in support. If he wishes, he may edit immediately below this line to briefly sum up support for the proposal. -- LostInRiverview ^{talk · blog} 01:11, May 16, 2011 (UTC)

---

Place your decision below - please provide justification for your decision, and sign using four tildes (~~~~)

Strong Oppose - I am opposed to the idea of making a separate fanon-admin class. It would mean that they would not be able to take action against vandals when no other users are around and not able to delete spam and vandalism in the main namespace. I feel the best option would be to keep the current system or merge the classes. --WH ^(Talk) 05:29, May 16, 2011 (UTC)

---

Oppose - per WoganHemlock. Everything that a fanon sysop would need is available in the sysop class anyway. Lost Labyrinth • (c) • (b) 06:30, May 16, 2011 (UTC)

---

Strong Support - I believe that creating a fanon-sysop class would be much easier for regulating fanon. The Fanon Namespace is large and important enough to warrant it's own group of administrators, and I would prefer them to stay separate from regular sysops. They should only have administrator rights in the Fanon Namespace to make it easier for them to have one priority, which is editing the Fanon Namespace, just to make sure that they are not swamped when trying to edit both the mainspace and the fanonspace. If we have sysops exclusive to the Fanon Namespace, the Fanon Namespace will become much stronger, and vandalism and poorly-written pages in the fanonspace will become less frequent. —Random Ranaun ^{(Talk to me!)} 04:44, May 19, 2011 (UTC)

---

Oppose - More problems arise with creating a different class then keeping them more like regular admins with interest in working with Fanon. --Zombie ^{talk • blog} 12:35, May 16, 2011 (UTC)

---

Full Oppose - I do not feel that creating this class will improve (if something) much the "admin jobs", I feel like this will limit fanon admins too much, while their main "job" must be fanon I see no reason for why they can't regulate the main namespace as well, limiting them will not make the fanon namespace stronger, and many fanon admins will actually want to have normal sysop rights to be able to regulate both namespaces, this ambition will not definitely make them interested in regulating the fanon. Thank you. --Guilherme Guerreiro (talk here) 16:37, May 19, 2011 (UTC)

Archive (no longer) pending

As you may have noticed, this page is getting excessively long. To that end, all conversations that have not been active in at least two weeks of the date I choose to archive will be archived. I plan on archiving on May 11 - if you want a conversation to remain on this page, make sure to contribute to the topic before then. Thanks! -- LostInRiverview ^{talk · blog} 05:17, May 5, 2011 (UTC)

As promised, the page has been archived. If a conversation was on this page but is no longer, check this page. -- LostInRiverview ^{talk · blog} 02:10, May 11, 2011 (UTC)

Images Policy

This discussion has been moved in its entirety to the policy proposal page. -- LostInRiverview ^{talk · blog} 08:04, May 29, 2011 (UTC)

New way of voting for Featured Articles

Hey guys and gals. I've been working on a brand new way to vote for Featured Articles on The Sims Wiki. The template I wish to put in action uses some of the code used for the battles voting template. Here's the main idea:[1].

This template has a drastic change on voting: It features an "oppose" column. The specific reason I included this was because currently, any article can be nominated, and at the same time, any article can be featured. A prime example of a featured article that was nowhere near one of the best on the Wiki was Sarah Crittur. While we have taken action to get users to vote for articles on a basis of quality and not popularity, I fear it just isn't enough.

The template has the following things:

1. Simple to use. Anybody who has voted in a battles will be able to use this easily.
2. Has a link to the page on the one side, a reason to be featured in the center and on the other side the nominator can sign their name.
3. Support section and Oppose section are neatly organized.
4. Bottom has a place for comments that can be made.

Any opinions? Thanks! --Zombie ^{talk • blog} 11:39, May 15, 2011 (UTC)

I really agree with, though the template could be improved, if this was implemented I think we could review the list of featured articles on this wiki, and see if they fulfill certain conditions, otherwise the article would be not be considered featured anymore. Thank you! --Guilherme Guerreiro (talk here) 12:11, May 15, 2011 (UTC)

The link Bob provided led to a deleted page. Here's the actual page (I think) he was referring to. Now, a specific question: will administrators be allowed to moderate submissions? So if, for example, a person nominates a Sarah Crittur-like article, will the administrators be able to remove it from the list or somehow make it ineligible until the article is improved? One of my criticisms of the current system is that we are largely locked down to whatever is decided, and we really have no control over which articles get chosen as our "best" articles. -- LostInRiverview ^{talk · blog} 12:12, May 15, 2011 (UTC)

I also thought about each having to be moderated by an administrator. There should be a criteria, and failing it = failing featured article nominations, for being, for example, too short, too long, too little images, etc. Basically, I I wanted a low-quality to be featured at this moment, all I have to do is wait till it gets featured, and a criteria would help the situation. Zombie ^{talk • blog} 12:20, May 15, 2011 (UTC)

I think the idea could work well, though honestly I don't really like the template. If we just added an Oppose option to the current style of voting and let administrators moderate the submissions, then I think that could work out better. --Bleeh^{(talk) (blog)} 14:59, May 15, 2011 (UTC)

Mmm, then an article can be nominated, an admin can moderate it and if it fails, voting is not allowed, but if it succeeds, users can fully give their opinion instead of being restricted to ignoring it or voting for it. Zombie ^{talk • blog} 15:41, May 15, 2011 (UTC)

I like this idea. It's very similar to the one large sties like Wikipedia and Uncyclopedia have, and more feedback on the articles. As a side note, this system could also be used for featured editor voting. --WH ^(Talk) 05:29, May 19, 2011 (UTC)

Consensus for Fanon Article comments

A previous Community Portal discussion posed the idea of implementing comments sections to the bottom of articles. While the community was generally opposed to article comments, there was an exception to this opposition for articles in the Fanon Namespace. One main argument for Fanon namespace comments was that it allowed more direct feedback from readers (versus making posts on the talk pages of articles) and might serve to encourage users to continue writing. So, I would like to determine whether there is or is not community consent for activating the article comments feature in the Fanon Namespace.

---

Place your decision below - please provide justification for your decision, and sign using four tildes (LostInRiverview ^{talk · blog} 20:28, May 16, 2011 (UTC))

:

- Strong Opposition - No, it would rather look like a blog, vandalism would be easier and more difficult to caught and I don't want to loose talk pages anyway. --Guilherme Guerreiro (talk here) 20:43, May 16, 2011 (UTC)

My mistake, this topic was already discussed here -- LostInRiverview ^{talk · blog} 20:45, May 16, 2011 (UTC)

Anyway, I don't think the other consensus was very conclusive. --Guilherme Guerreiro (talk here) 20:54, May 16, 2011 (UTC)

Why were the article comments enabled? We didn't really get a consensus, article comments should be enabled just after a consensus. --Guilherme Guerreiro (talk here) 20:31, May 17, 2011 (UTC)

Guilherme, we already had consensus reached, and the majority of users supported it. Even if this doesn't work out, we can easily turn it off and switch back. --Zombie ^{talk • blog} 20:35, May 17, 2011 (UTC)

But we have a problem with it, talk pages and discussions on fanon have disappeared, I wouldn't really support this since the current discussions will be lost (fanon). Thanks. --Guilherme Guerreiro (talk here) 20:36, May 17, 2011 (UTC)

No, they're still around, just a bit harder to reach. Here's one. Zombie ^{talk • blog} 06:52, May 18, 2011 (UTC)

There is no link to get to the talk pages, soI presume you just type "Fanon talk:<article name> to get to the page. --WH ^(Talk) 07:02, May 18, 2011 (UTC)

We can add links to the talk page by editing certain templates. Zombie ^{talk • blog} 05:08, May 19, 2011 (UTC)

Unexperienced users will probably not figure it out, this is an issue. --Guilherme Guerreiro (talk here) 16:24, May 19, 2011 (UTC)

Well, as far as I can see, unexperienced users coming here to make Fanon barely (though I've never seen it) used the talk page anyway, and we can still, as I said, add a link in the respective templates. Zombie ^{talk • blog} 16:39, May 19, 2011 (UTC)

World Adventures

• Recently i have realised that a majority of the families of the destinations have very little information or none at alll and i think it is a issue that needs sorting and quite a few need pictures so i think this is something people need to address now i know i'm just a rondom wiki contributer but i have uploaded a few WA pictures to families and ghosts so please help. 109.153.78.39 14:43, May 21, 2011 (UTC)

Your help is appreciated :). Most, to all of us, know that we've been lacking in quality for WA townies, but the problem is that there isn't much to add. --Zombie ^{talk • blog} 15:53, May 21, 2011 (UTC)

I made this a major project of mine quite some time ago - when I first arrived here, in fact. There is information there to add, but it is substantially less that the more fleshed out personalities of the main hoods. I simply haven't had the drive to complete it. I think most of what's there is my work. If anyone wants to help complete it, that would massively restore my motivation. It's hard work, gathering all those pictures and all that info. (Kiwi tea 15:47, May 25, 2011 (UTC))

Notice: Policy discussions

Please note all that the Policy page has been redone, and we now have a dedicated page to discuss policy proposals. I've relocated a couple discussions from this page to their relevant pages, and I ask that policy discussions from now on be conducted on the appropriate talk pages. I may come up with some sort of noticeboard system on this page so users starting discussions elsewhere can notify readers of this page, so keep posted.

The fanon policies discussion and images policy proposal have been moved as a result of this change. -- LostInRiverview ^{talk · blog} 08:10, May 29, 2011 (UTC)

Noticeboard has now been added, along with a general redesign of this talk page. This notice here is now completely irrelevant. -- LostInRiverview ^{talk · blog} 08:55, May 29, 2011 (UTC)

Trait Images for TS3: Console Versions

Could someone please try to find/upload the images for Wii and DS The Sims 3 traits? We're in need of them. Thanks! --Zombie ^{talk • blog} 15:21, May 29, 2011 (UTC)

Whatever traits are the same can stay the same but I am aware that there are some standalone traits for the Wii version. They may be hard to get as the Wii discs are propreitary technology, meaning they can't be read by a PC and extracting the images can be hard without a third-party mod. I've seen screenshots from the DS version on the wiki so however they're captured, I guess the same method is used. Lost Labyrinth • (c) • (b) 23:01, May 29, 2011 (UTC)

On a related note, we need images of Rebellious and Nutruing for Generations. I'd get them myself, but I don't have Generations yet. --WH ^(Talk) 08:10, June 3, 2011 (UTC)

As soon as I posted, I realised we already have the images, haha. --WH ^(Talk) 00:04, June 4, 2011 (UTC)

New spotlight request

I believe it's almost time for a new spotlight request to be made. Yeah, the last one didn't work out to well, but if I may, I believe the problem was the blog contest that gave out badges. It got out of control, but I think that a spotlight would be perfect for bringing up the Wiki's activity, and this time, we'll advertise the Wiki and not a blog.

Now, there are two reasons I believe we should do this in July. Firstly, because there's bureaucrat voting going on now which'll have a ton of contributers possibly voting in without really having true say in why/why not the user should/shouldn't get the rights, and secondly because there may be a higher risk of vandalism and many admins are currently busy with exams.

So..yeah. My idea is we should request a spotlight to promote the Wiki in July. Any opinions? Thanks! --Zombie ^{talk • blog} 20:08, May 17, 2011 (UTC)

It would be cool if we timed our spotlight to tie into a game release. We've missed the boat for spotlighting Generations, but perhaps we can catch the traffic from a fall expansion release (there will probably be one in October or November, by the current rate). This would be especially useful if the game to be released is of a particular popular nature (you know what I mean). So, perhaps we wait until the new EP is announced, then we reqest? -- LostInRiverview ^{talk · blog} 20:11, May 17, 2011 (UTC)

Get exactly what you mean. I just want some more takes, but I like your idea. --Zombie ^{talk • blog} 20:19, May 17, 2011 (UTC)

I too think it would be good if we could time the spotlight with a game release, but I don't see a problem with getting one at any time, because, face it, a spotlight is a spotlight, and people will check the spotlights regardless of game releases. --WH ^(Talk) 08:15, May 24, 2011 (UTC)

I think a game release would be a great time to plan a spotlight, since there needs to be many admins when both are happening. You might want to see if you could get one soon though, as Generations comes out next week! --Bleeh^{(talk) (blog)} 03:22, May 25, 2011 (UTC)

Just a note - Wikia needs substantial notification for spotlights, i.e. more than a week, so we can't do one for Generations. However, we could get one for a later expansion, there will probably be one around November. --WH ^(Talk) 05:03, May 25, 2011 (UTC)

It's too late to ask for a Spotlight to tie in with Generations now, as it is released like, tomorrow! :P But if The Sims 3: Unleashed or whatever EP is confirmed for October/November then we should easily be able to get one for then,, as we could benefit from it if we asked ourselves unlike one EP ago where all we got were IP vandals. Lost Labyrinth • (c) • (b) 22:58, May 29, 2011 (UTC)

OK, The Sims 3: Pets has been announced and confirmed by EA and it is likely that the game will be released in October, with one source saying October 29th. I think we should plan how we're going to go through with this. After some discussion on IRC, we've accepted that we are likely to notice an increase in vandalism either way and it's something that our rollbackers and administrators are just going to have to deal with, but it should be easier to patrol this time round as a) we have more admins and b) we're actually planning it ourselves rather than having the Achievements feature activated and us being spotlighted out of nowhere. Any suggestions on how we go through with this? Lost Labyrinth • (c) • (b) 20:17, June 3, 2011 (UTC)

Ok, update. The way things stand, we have 3 active bureaucrats, 5 or 6, active admins, 1 active rollback and 2 active fanon admins. Note - I'm going off how recently the users have contributed. I think that should be enough to cope with a wave of vandalism, and, let's face it, that will happen. We have a sysop on around the clock usually, so not much will happen. I think we should just take it as we go, for now. --WH ^(Talk) 00:11, June 4, 2011 (UTC)

Requests for administratorship and fanon administratorship are also open currently, but no one has applied yet. If we get applicants that ultimately become (fanon) administrators, that will only help when traffic increases. I support a spotlight request for the month of October, even with the present number of administrators. -- LostInRiverview ^{talk · blog} 00:30, June 4, 2011 (UTC)

Should we make the request soon? I think we should get this confirmed, because these spotlights can be really difficult to get. --WH ^(Talk)

I've just checked on community central and we need to meet these reqirements. WH ^Talk 01:58, June 12, 2011 (UTC)

We should meet those requirements anyway, though we may need to close the Requests for administratorship, as we shouldn't be in the middle of choosing new admins. Lost Labyrinth • (c) • (b) 10:28, June 12, 2011 (UTC)

I've already submitted a request for spotlight, and have not seen any response yet. We'll see! -- LostInRiverview ^{talk · blog} 21:10, June 13, 2011 (UTC)

Administrator Selection Process

Alright, I want to propose a new method for selecting our Administrators. This would not change the requirements for applying or make it any more or less difficult to apply for. It would, however, ensure that all our administrators have tasks and duties to perform that are specific to them, and so we can manage parts of our wiki that have been forgotten or ignored. To that end, I am proposing the following (with justification provided in italics).

1. The Fanon Administrator class is to be combined with the Administrator class. This allows the Fanon Administrators to function as full administrators without limit. There has been difficulty in finding users to permanently fill Fanon Administrator positions because many view it as a step on a latter, being that Administrators are somehow "higher" on the latter than Fanon Administrators. Merging the class would solve that issue as well.
2. All Administrators must sign up or choose a select number (I'm thinking two each) Administrative Projects to lead. The projects are:
   • Image and file maintenance - Responsible for keeping our images neat, organized and copyright compliant.
   • Fanon Administration - Responsible for maintaining an orderly Fanon namespace and working with fanon editors.
   • Categorization and layout - Responsible for improving wiki navigation and layout for users and readers.
   • Visual improvement - Responsible for making the wiki visually appealing and for bringing the wiki under a unified visual theme.
   • Community involvement - Responsible for communicating to readers and editors on the projects of the wiki, and in planning wiki events.
   The logic behind this is that each administrator will have pet areas they are responsible for working on. The Bureaucrats would, when placing an administrator, ask what jobs the admin would like, then act accordingly. This also allows us to focus on which areas need improvement (and thus, administrators) and which areas do not.
3. Administrators are required to make meaningful contributions in their Administrative Project areas. Administrators are encouraged to edit across all spectrums of the wiki, but must be sure to perform their required duties for their AP.
4. Bureaucrats may determine that an administrator is not working sufficiently within their AP and request that the administrator address the issue. If an administrator, within two weeks of this request, cannot show improvement, they may risk action including possible removal of administrator rights.
5. Administrators may request a temporary (not to exceed one month at a time) break from an AP due to real-life circumstances. Administrators may also request a change to a different AP. Requests must be approved by a bureaucrat, and requests to change APs will be dependent on the number of administrators working in each project area.---- Thoughts? -- LostInRiverview ^{talk · blog} 23:47, May 31, 2011 (UTC)

   I think that it's a good idea to merge the two user classes as it solves the shortage of fanon admins and introducing the new APs allows for admins to work more efficiently in a specific area of the wiki. Lost Labyrinth • (c) • (b) 00:01, June 1, 2011 (UTC)

   I agree with Georgie, though I have a question: What will happen if there's too many administrators in one AP? --Bleeh^{(talk) (blog)} 00:20, June 1, 2011 (UTC)

   Since bureaucrats would be responsible for determining who serves in which AP, bureaucrats would prevent one AP from having too many administrators working in it. -- LostInRiverview ^{talk · blog} 00:42, June 1, 2011 (UTC)

   I like this idea. However, will administrators be able to choose more than two APs? —Random Ranaun ^{(Talk to me!)} 00:56, June 1, 2011 (UTC)

   The potential issue with that is that if we allowed everyone to choose more than two, there may not be enough APs for everyone. Lost Labyrinth • (c) • (b) 00:58, June 1, 2011 (UTC)

   I don't think you can have too many people working on an AP, only too few people on an AP. So I think admins should be able to choose as many as they want, so long as we have enough people working on each AP. -- LostInRiverview ^{talk · blog} 01:07, June 1, 2011 (UTC)

I do like this idea. With it, we will be able to make sure that specific areas are taken care of. I presume that, if a merge between the classes happens, the Fanon Admins would still have fanon as one of their projects. --WH ^(Talk) 05:13, June 1, 2011 (UTC)

At the start, yes the Fanon Administrators would. They could request to pick up other APs and drop the Fanon one if they wanted, depending on which APs need more administrators and which do not. -- LostInRiverview ^{talk · blog} 18:01, June 1, 2011 (UTC)

This is a pretty cool idea, but what will happen to the Special positions once APs are implemented? —Random Ranaun ^{(Talk to me!)} 19:41, June 3, 2011 (UTC)

I reckon that the special positions will probably remain, as they don't reflect on wiki editing as a whole. I know one of them which "someone" has doesn't even have anything to do with editing the wiki! ;) Lost Labyrinth • (c) • (b) 20:07, June 3, 2011 (UTC)

The special positions may be phased out eventually, with a special process to select the Ombudsman (since they don't need to be administrators). It's been too difficult to get administrators to apply for these positions. -- LostInRiverview ^{talk · blog} 21:56, June 3, 2011 (UTC)

Proposal consensus

It seems as if most response so far has been positive and supportive. Therefore, I will open this up for official consensus. -- LostInRiverview ^{talk · blog} 05:47, June 6, 2011 (UTC)

Support - --WH ^(Talk) 07:15, June 6, 2011 (UTC)

---

Strong Support - It will help maintain order on the wiki, and increase interest in Fanon administratorship and special positions. —Random Ranaun ^{(Talk to me!)} 08:43, June 6, 2011 (UTC)

---

Support - --Guilherme Guerreiro (talk here) 11:51, June 14, 2011 (UTC)

Scratch this actually. Since I have seen no opposition, I'm going to presume support and begin implementation. If there is any significant opposition to the proposal, I will seek formal consensus. -- LostInRiverview ^{talk · blog} 15:29, June 6, 2011 (UTC)

- The proposal is adopted.

List of Objects in Various EPs

There are so many Categories: Objects in (Expansion Pack), while many objects in the categories are incomlpete, e.g. Category:Objects in Apartment Life only contains 2 objects, while there are many objects with special purposes shipped in the game! And also, all the object pages are stubs. It only contains 1 or 2 paragraphs, leaving the page to be inevitable as a stub. Pictures of the objects also don't match with others, because they're taken by different people in different situations. Details of objects are also... not detailed. It lacks information like price, type of objects, etc.

I suggest that we create a list page that instead of making Category, the page itself is a list of objects with special purposes for each EPs. The objects are for example instruments, gym equipment, and bubble blower that only came from University, or sewing machine, restorable car, and train set from FreeTime. I have suggestion that the page design should be like this. Info on the left, picture and details on the right.

I know this means we'll be deleting the object pages, but I think that's better because those pages are not well-organized anyway. This page will make the list of those objects more well-organized.

What do you think of the idea? (I'll make the page if no one minds) Nikel23 01:00, June 2, 2011 (UTC)

If you are proposing to make a list of objects, I think that's a great idea. We have lists of heaps of other things, e.g. List of Moodlets. As fr why some objects have their own pages, they are usually notable objects, e.g. things like cars, or they are an official EA object. I agree, it is a bit iffy about what deserves a page and what doesn't, but I see no problems with a list of objects. --WH ^(Talk) 04:17, June 2, 2011 (UTC)

It's true, some objects are notable (I don't intend to add ALL objects though). But those objects like pirate ship couldn't be elaborated more than one paragraph, so it would waste a page. Cars are different as they're quite special objects. Also, we don't really have to explain everything about one certain object. Just the main point, or the summary. Nikel23 05:56, June 2, 2011 (UTC)

True, there isn't much to write about for many objects. I say the list seems fine, but I don't really want to delete all the pages on things like the pirate ship, even if they are stubs. I think that we should have a page like the list of moodlets one, but for objects. We would then let special objects (haven't thought of a definition for what we can call spacial, any ideas?) have their own page. Thoughts? --WH ^(Talk) 05:29, June 3, 2011 (UTC)

I think common objects such as chairs, desks, or desks don't need to be on the list, as we could assume the function are just the same. In my opinion, "special objects" means objects that come only from one or some EPs. We (might) know pirate ship only comes from BV, right? And chopper only from AL. That's what I think of "special objects". How about that? Nikel23 12:29, June 3, 2011 (UTC)

I made an example of the page at the sandbox. Will you check it out and give your opinion? Of course the images will need cleanup too. Nikel23 14:14, June 3, 2011 (UTC)

I like it. As for the definition of special objects, that makes sense. I think that you intend to only make a section for special objects on the page, as the load time on slower browsers would be horrid if you did it for every object. I think you should make it, but maybe wait a bit or feedback from other users. --WH ^(Talk) 00:15, June 4, 2011 (UTC)

Allright, I start thinking the title is sort of... discriminating. Of course this page list is intended for TS3 too (though I believe there are more special objects come with it), but I don't have TS3. That's why I made title like that at the first place. If anyone wants to consider it about TS3, feel free to give your opinion. Nikel23 07:26, June 4, 2011 (UTC)

A suggestion

We can bring the Wikia live chat to the wiki, it will help connecting all users together like the one in L.A Noire Wiki.Mr.Wikia 16:26, June 13, 2011 (UTC)

There's an above thread on this page. We're planning to gain consenseus first so we can enable it when it goes live to Wikia Labs. You're welcome to voice your opinion if you wish. Lost Labyrinth • (c) • (b) 16:29, June 13, 2011 (UTC)

Question

Are we allowed to add pages to this wikia? I would love to see a 'Bugs and Glitches' page for this game that isn't on the official Sims 3 site where entire threads and posts looking for help get swallowed up by constantly similar queries or are simply moved by webstaff there. I don't know what the policies are on that but I didn't see an 'Add Page' option here so I'm either blind or it doesn't exist! Thanks. MiyuEmi 12:58, June 17, 2011 (UTC)

There's already a Glitches page. The "add a page" should in reecent wikia activity, if you do not see it use Special:CreatePage. --Guilherme Guerreiro(talk here) 13:09, June 17, 2011 (UTC)

I am blind! Thanks for that. I've found the glitches page too. Thanks again. 193.120.145.210 14:22, June 17, 2011 (UTC)