text:
Wikibooks talk:Deletion policy

Move to enforced
The vote at vote for deletion policy showed consensus. The discussion of a move to enforced at the staff lounge was unopposed. RobinH 11:33, 30 May 2006 (UTC)

Removing "Blatant vandalism" from SD criteria
Currently we have these two among the criteria for SD:
 * A page with no meaningful content. Always check the history of the page, as this nonsense may have replaced good content. If this is the case, simply revert to the last good version.

and
 * Blatant vandalism. This would be obvious offensive language or completely unrelated content to the Wikibook it is associated with. Make sure that the page that has been vandalized does not have prior history that can simply be reverted, then blank the page and add the deletion tag.

"Meaningful content" includes:
 * Vandalism (including linkspamming)

I think the former criteria sufficiently includes the latter which I propose we remove. --Swift 17:59, 21 November 2006 (UTC)

 *  Agree . The shorter policy pages are the better (in general anyway). --Dragontamer 05:44, 23 November 2006 (UTC)

 * Vandalism isn't really defined under "Meaningful content" as it is for Blatant vandalism. I think perhaps either the definition of vandalism as defined by the blanant vandalism definition should be combined with vandalism definition under "Meaningful content" or it should be expanded to include an alternative definition of vandalism. Without a vandalism definition it is up to interpretation of what vandalism is and leaving vandalism undefined from this policy may not be a good idea as there seems to be some efforts by other contributors to Wikibooks to try to define other unwanted contents in addition to whats already in this policy. Perhaps we could also change the section name to "No meaningful content"? As it is now the name is misleading when what is pointed out is examples of what is not meaningful content rather then what is meaningful content. --dark [[Image:Yin yang.svg|12px]] lama 10:44, 23 November 2006 (UTC)

 * Oppose. It's a small change, and while the one might be implied in the definition of the other, I can't see any reason to remove a small amount of text at the expense of removing clarity. Wiki isn't paper, remember, and we can afford to be a little verbose now and again. --Whiteknight (talk) (projects) 02:14, 3 January 2007 (UTC)

 * Oppose - As the author who put this phrase into the speedy delete criteria, I wanted to be very plain about the fact that you don't have to hold a VfD over vandalism. There is content that has been added as a deliberately malicious nature sometimes to a page, and an admin should have the authority to get rid of this stuff.  It may be "meaningful content" in some sense of the word, but the person who added it is clearly trying to cause problems for the main contributors of the module or Wikibook.  Yes, this is something that requires good judgement, which is one of the reasons why we get so paranoid about accepting new admins and often turn down requests for adminship.  In most cases the vandalism is so obvious that having a second admin review it is more than sufficient, if there is cause to doubt the actions of a particular admin.  --Rob Horning 08:18, 3 January 2007 (UTC)

Moving Content of books
I take this change chance to ask that when people move text out of books (even if they get deleted) should give the right credits on the destination work as requested by the GFDL. --Panic 16:55, 2 January 2007 (UTC)

 * "I take this change to ask..." I don't understand what you've just said. What change? Could you rephrase?

 * Sorry. change -> chance :), besides my normal error level, I have now the flue :)...
 * This refers to (GFDL on 5. COMBINING DOCUMENTS), as I it seems to me that most users that move pages from books to books do that without regards to that stipulation. Another point that should be useful to state on the policy it that even if books are deleted on Wikibook there are other servers that can have the old content replicated. --Panic 23:30, 2 January 2007 (UTC)

 * I agree that GFDL documents mustn't break the license ... but what does that have to do with Deletion policy? This policy concerns itself with the criteria and process of removing pages; not combining them. A little context to your suggestion would be useful.

 * It relates to Guidelines for admins, it should be added there as a reminder to admins merging content, nothing more.--Panic 01:35, 3 January 2007 (UTC)

 * "there are other servers that can have the old content replicated." I don't see any reason whatsoever for including this in the page. If you really think it is important, please start a new section for it.
 * Hope your flue gets better! --Swift 01:21, 3 January 2007 (UTC)

 * Most people may interpret that by a decision to delete here, the content is destroyed it can prove advantageous not only to refer that other systems do mirror the content but that the user is free to copy it elsewhere under the GFDL license, this can ease the affected user disposition regarding a passed decision to delete. --Panic 01:35, 3 January 2007 (UTC)
 * I agree with that sentiment, We should make it more clear that content deleted here, since it is under the GFDL, is free to be copied or transferred to another location. --Whiteknight (talk) (projects) 02:33, 3 January 2007 (UTC)

Vote and changes
Any call for a vote or the approval of this policy must be depend on the approval of What is Wikibooks, this should also be stated on it's text as it may depend on the this other policy. --Panic 16:55, 2 January 2007 (UTC)

 * This policy has already been approved. --Swift 21:34, 2 January 2007 (UTC)

 * Well that change is a state of fact, there wouldn't be a need for a formal proposal (on that change) but I came here from a link that stated that it the policy was under discussion... Sorry, but my point remains valid, do you think it changes the actual intention of the policy and a proposal is needed ? --Panic 23:54, 2 January 2007 (UTC)

 * I dont think this policy needs to be altered or updated unless blatant problems can be found in it (and I can't see any on quick inspection). --Whiteknight (talk) (projects) 02:16, 3 January 2007 (UTC)

This policy has been formally approved for some time, and I was involved with the decision. This is the actual page where the voting took place, and IMHO similar kinds of votes should also happen. All of this said, there is some concern over what was voted on and the current state of this policy. See this diff to compare what has changed from the version that was voted upon. While most of what has been modified is relatively benign and insignificant, there are a few points that did make some major policy changes that have crept in. Those changes IMHO are something that can and should be debated upon. --Rob Horning 08:11, 3 January 2007 (UTC)

 * I think the Decision making policy precludes the use of large, elaborate voting mechanisms as were used when this policy was accepted. Many of the changes that you point out in that diff link were discussed, either in this talk page, or in other locations before they were enacted. In general, I think a less-formal system is far preferred over all sorts of formal nonsense anyway (special voting pages, etc). Regardless, I can't imagine that we need to put the currently accepted text of this policy to a new vote to confirm it. --Whiteknight (talk) (projects) 01:01, 5 January 2007 (UTC)

To avoid confusing and restatement of the points, the actual policy should be reverted and the now changed text (contested) should be moved to an unstable version of the same policy (I will also add my proposed changes later) and in the talk page should be stated that the text should be analyzed and debated but a formal approval will only be performed after the Decision making policy is closed. Any one disagrees ? --Panic 03:37, 5 January 2007 (UTC)

 * I would disagree, I dont think the text of the page should be reverted unless specific points are challenged. Keep in mind that wikibookians are encouraged to be bold, and many changes, edits, and improvements are instituted by bold wikibookians trying to fix problems without alot of hassle. By all means, create an unstable version if you want (i have some things to add and change as well), but dont revert the current text of the policy. --Whiteknight (talk) (projects) 03:47, 22 January 2007 (UTC)

 * Yup I do agree with you, but under the be bold if a user should make a substantial change to a policy, the points shouldn't be challenged, the opposing user should revert and state why, if the originator of the change should find that the reversion did in some way reduced the advancement of a point or he wishes to propose that point for adoption then he should make an unstable version to propose the change. On simple terms it is up to the one that wants to push a change to get the trouble of defending it, other Wikibookians should prevent any changes that alters the spirit of the adopted policy on the active policy page. --Panic 05:11, 22 January 2007 (UTC)

Why
Why did Jimbo Wales order the removal of video game guides from WikiBooks? You can reach me on Wikipedia's 100110100; a response there would be greatly appreciated, thanks!<IP_ADDRESS> 07:29, 15 March 2007 (UTC)

 * It wasn't so much an order by Jimbo as it was a manifestation of policy. Videogame strategy guides don't qualify as textbooks under the inclusion criteria, although exceptions have been made in the past. Jimbo's statements weren't so much a mandate against videogame guides as they were a reaffirmation of our pre-existing policy. --Whiteknight (talk) (projects) 13:33, 15 March 2007 (UTC)

 * I strongly disagree on this point. It was not pre-existing policy, as there was no policy that even governed the concept.  It wasn't even an exception to a particular inclusion policy.  It was a few admins that  took the words of (and IMHO mis-interpreted the suggestion of) Jimbo and did a mass deletion of Wikibooks content.  Jimbo did come swinging onto Wikibooks and said that in his opinion they didn't belong here.  And he tried to give several point that from his perspective, including a violation of the the Wikibooks charter.  But when they were first removed it was in violation of this policy on this page, in both the spirit and the letter here.  And general consensus within the Wikibooks community on this issue was never achieved.  I still don't think it has, other than almost all of the supporters of keeping the video game books have been driven from Wikibooks instead.  --Rob Horning 15:44, 15 March 2007 (UTC)

 * The current text of WB:WIW is essentially the same as it was before Jimbo made his declaration. Some of the vaguarities, especially over the videogame guide issue, are the prime impetus to the new draft of that policy. If you look at the current text of WB:WIW, you will see a number of strong points that can be used to ban videogame strategy guides. Those guides were not banned, as they should have been, both because of rampant inclusionism, and the fact that wikibooks had been used as a dumping ground for lots of inappropriate material early in it's lifetime. The mistakes of the past, while they do form some sort of tradition or inertia, hardly make the fact "not so". Video game guides never really belonged here, nobody ever had the backbone to just kick them out. --Whiteknight (talk) (projects) 17:21, 15 March 2007 (UTC)

 * The video game books were not things that were "dumped" onto Wikibooks. I could name several items that were dumped here, but that was not among the problems mentioned here.  Jimbo did change WB:WIW spontaneously and without discussion, and furthermore even after he changed the wording there, he didn't really explain what the change really meant or what the implications of that change would have for the project.  It also created a huge firestorm of discussion for trying to "divine" the implications of the policy change, as Jimbo simply didn't say what he really meant other than three particular books had to be deleted.  It was if the policy was to delete those books alone on his authority.  And video game books were not on that list.
 * Again, Jimbo did suggest that the books didn't belong on Wikibooks, but at the same time concensus simply did not occur. The books were simply deleted.  In regards to the rampant inclusionism, Wikibooks has been narrowing the defintion of what was included here for some time.  But that process was one of a more gradual process.  I will admit that the video game books did have significant opposition even before Jimbo came in and stirred up the pot, and it is possible that they may have eventually gone without Jimbo's interference.  But to say that video game books never really belonged here and there was no support nor legitmate arguments in favor of keeping them on Wikibooks is very much missing the true feelings of Wikibooks at the time.
 * My strongest objection to what happened was that this policy was never even followed (and it did exist at the time!) Books were simply deleted without any discussion, and on the presumed authority of Jimbo.  It wasn't until I started complaining that VfDs were started at all.  And it should be very apparent from the VfDs of the time that substantial books were indeed voted off of this project and whole categories of books (like fiction) were removed as well.  But it as done with widespread concensus.  This did not happen with the video game guides.  That video game books still exist on Wikibooks should be a testament that this concensus simply didn't happen, but that the contributors of those books were kicked off by aggressive administrators.  --Rob Horning 04:16, 16 March 2007 (UTC)

 * Administrators do not need community consensus to delete manifest policy violations. Certainly consensus in those situations is a nice formality, but it isnt strictly required. It's why we have a category for speedy deletions in parallel to our normal VfD mechanism. Things on which there is no doubt about the inappropriateness of inclusion here can be deleted without first acquiring community consensus. The deletion policy says "when in doubt, nominate at VFD", which expressly leaves open an option for issues when there is no doubt. Jimbo did not need to explain his inclusion on the WB:WIW policy, the purpose and the implications were self evident: videogame guides do not belong here, and they should be deleted. When the oldest wikibookians agreed on the original text of WB:WIW (or the equivalent, since that's not what it was called), and agreed that wikibooks was for textbooks and not all manner of written work, consensus was acheived on this issue. We dont need community consensus again to confirm the text of that policy, it stands until the community agrees on a new version of it. Videogame guides always have been inappropriate here, and it was the fault of lazy admins in the past that they weren't removed like they should have been. the "aggressive admins" of the present time (of which I am proud to call myself a member) are simply following policy and making wikibooks a better place because of it.
 * Let's get one thing straight here: video game guides are not and never will be considered "textbooks". The fact that they were included here previously was a gross misjudgment by early wikibookians, and we are still dealing with that mess today. In all your complaints about this issue, Rob, you haven't once given good reason as to why videogame guides should not be summarily deleted. You talk about people not achieving consensus on the matter, you talk about the rashness of the decision, and you talk about Jimbo's lack of authority to make that call, but you are ignoring the fact that it was the right thing to do. --Whiteknight (talk) (projects) 14:40, 28 March 2007 (UTC)

 * Again, to suggest that there is a right thing to do is patently false because we are not dealing with an ethical decision. There are opinions about what action is most acceptable, but there is not a "right" or a "wrong" course of action. --Iamunknown 19:48, 28 March 2007 (UTC)

 * I'm not implying it's an ethical decision, perhaps i should have used the word "correct" instead of "right". Choice of vocabulary not withstanding, you aren't addressing the issue here: Videogame guides are not textbooks, and they should not be on wikibooks. Me using the wrong word doesnt make the point less valid. --Whiteknight (talk) (projects) 20:27, 28 March 2007 (UTC)

Hm?
Have you guys deleted the game guides because they were subjective, without verifibility?100110100 of Wikipedia<IP_ADDRESS> 05:29, 28 March 2007 (UTC)
 * No, we were deleting the game guides because they are not academic and they are not textbooks. Wikibooks is not a host for all sorts of printed materials, we only host textbooks. --Whiteknight (talk) (projects) 14:26, 28 March 2007 (UTC)
 * Why do books have to be academic and textbooks?100110100 of Wikipedia<IP_ADDRESS> 19:40, 28 March 2007 (UTC)
 * It's part of the inclusion criteria. It's like me asking why do wikipedia articles need to be verifiable? Every project has their own criteria, and our criteria is that things must be "textbooks". Why doesnt wikipedia allow videogame strategy guides? Why doesnt wikinews allow them? Just because you really like the guides, and just because this seems like the best place for them doesnt mean that we should allow them here. --Whiteknight (talk) (projects) 20:29, 28 March 2007 (UTC)

I strongly disagree with the general statement "because this seems like the best place for them doesn't mean that we should allow them here." Always put stuff at the best place for that stuff. And there is always a place somewhere for sincere, well-intended stuff. If wikibooks is the best place for some text, then by all means, put that text on wikibooks.

However, I agree with the specific statement that video game strategy guides don't belong on wikibooks. Video game strategy guides don't belong here, because there are much better places for them.

Since one of my pet peeves is when people allude to "other places" but don't give enough information for me to find them, I'm going to list video games wiki here:

 * the WorldForge project
 * WikiXbox360
 * WikiDream
 * wikicheat
 * Wiki.AG: Absolute Games
 * Wiki gamer
 * W.G.G. wiki games guide
 * Unofficial TransGaming Wiki
 * the Underground-Gamer Wiki
 * Strategywiki -- has a nice Interwiki link
 * Strategy Guide Wiki
 * Scientific Study of Video Games a.k.a. The Video Game Player's Encyclopedia
 * RPG, the Wikia for role-playing gamers
 * RPGnetWiki
 * RoleWiki: encyclopedia of roleplay games
 * RPG Maker Wikia
 * PinWiki (for pinball games)
 * the English Nintendo Wikia
 * Nintendopedia
 * My Wiki 360
 * Mod-ified Design Wiki
 * IFWiki : interactive fiction (text adventures)
 * Gp2x dev wiki
 * GeezerMech Games
 * GamerWiki
 * Gamepedia
 * Gamecontractor Wiki
 * the game programming wiki
 * FreeGames wiki
 * Faqs 4 Games wiki
 * Encyclopedia Gamia and Gameinfo Wikia (now merged)
 * CheatBase
 * the Casual Game Wiki
 * Build Your Own Arcade

There are also many other wiki dedicated to one particular video game or another. The next person who starts thinking about writing yet another video game guide on Wikibooks -- is there a better way to redirect him to one of these better locations for his efforts? --DavidCary (talk) 05:52, 19 December 2007 (UTC)
 * We normally direct people to StrategyWiki:, but people are free to take the content to any of the above. The problem is that Wikibooks often seems like the best place to put content that doesn't belong on Wikipedia - if it doesn't fit inside their inclusion policy, it often ends up here. In the exact same way that Wikipedia has a strong inclusion policy, so too does Wikibooks, and it doesn't include video game guides (among other things). Each wiki has a specific scope, and you can't just dump content into any arbitrary wiki without regard for their inclusion policy. – Mike.lifeguard  | talk 15:30, 19 December 2007 (UTC)

User Pages
I was under the impression that this policy contained mention of the fact that userpages may not be used to circumvent a VfD discussion. That is, when we vote to delete a book through VfD, that a person may not copy the book into their userspace and continue work on it from there. I would like to propose adding the following text to the VfD section:
 * A person's user and user talk pages may not be used to store copies of pages deleted through VfD. User pages may not be used to circumvent VfD or other community decisions or site policies.

What use is VfD anyway if people can simply move deleted material to the User: namespace, and continue working on it as usual? Furthermore, if VfD, we are typically voting for the deletion of content, not simply the deletion of particular pages. This would imply that the community is voting to delete the material regardless of what page or pages it is located on. Furthermore, while it hasn't happened in a long time, I'm decently certain that this kind of action has some precidence. although I need to find evidence of that. --Whiteknight (Page) (Talk) 15:22, 17 December 2007 (UTC)
 * [[Image:Symbol support vote.svg|15px]]  - I'd love to see that added. In the case which prompted this, there was a pre-existing draft in the userspace, so that wasn't actually an attempt to sidestep the VFD. It should be deleted, however. The author can keep the content, just not on Wikibooks (including their userspace). I think you're correct that this has happened in the past, though I'm not sure where. – Mike.lifeguard  | talk 15:27, 17 December 2007 (UTC)

Transwikied books
The policy currently states that:
 * "A page which has been transwikied to more appropriate wiki, and is considered to be against one or more policies here."

Pages that go against policy should be deleted whether they have been transwikied out or not. If someone could point out if there was some nuance intended here, this point could use a clarification. If it's just a redundant criteria that slipped in, we might as well remove it. --Swift (talk) 16:40, 4 February 2009 (UTC)

 * Actually, the latter part of this was just recently added. --Swift (talk) 16:43, 4 February 2009 (UTC)

 * In the past works have been transwikied despite being perfectly within the scope of Wikibooks. I think the intent is to make policy clearer that works that have been transwiki must also be outside project scope before being deleted. --dark lama  21:31, 4 February 2009 (UTC)

 * In that case, removing the mention of transwikis would have done the trick. --Swift (talk) 21:51, 4 February 2009 (UTC)

Edits and fixed version
I recently made 2 edits: 1- one very small, removed the word vote as per the now used language and I expect more in accordance to what was intended in the original text. 2- a somewhat confused duplication of what is written on the active Deletion policy.

I also find that I don't remember this policy being so pro-consensus (the true concept of it) and as is I can point several instances where the policy has been broken, can anyone point to the original approved version ?

To clarify. I like the policy text as it is but I think that it is not what has been applied and probably not what was approved. --Panic (talk) 08:54, 18 November 2009 (UTC)

The only version I know was community approved was the one that is on Policies and guidelines/Vote, [] that makes deletion a personal decission the acting administrator without any special specifications, approved in ~2006 April, 15th 00:01 GMT. --Panic (talk) 09:11, 18 November 2009 (UTC)

Active proposal Since the actual policy and what was approved have diverged significantly a restoration to the approved text should be made, if someone disagrees or has better information to clear this out, I will perform the restoration of that version and move the present text to an unstable version in 7 days. --Panic (talk) 09:16, 18 November 2009 (UTC)

 * I did some rephrasing, to be clear that a user can make multiple comments, just only one declaration of position (keep or delete). I also caught — at the last moment — one use of the word "voting" that we'd both missed up till then (though I also actually put one in, in the context of stating plainly that the declarations of position are not a vote).  --Pi zero (talk) 14:03, 18 November 2009 (UTC)
 * I object to reverting to any earlier revision. I believe that most changes were discussed somewhere before they were made or were small minor changes as mentioned elsewhere on this talk page. I believe even the changes made now while I didn't agree with the wording exactly still reflect the general intended spirit of the policy. I have gone ahead and reworded it some more in an attempt to be more general towards what we actually do. Delete and Keep are hardly the only positions a person can take when discussing a work for example. People can also suggest merging, moving to a different wiki, etc. --dark lama  16:16, 18 November 2009 (UTC)
 * Since no one seems to be extremely hostile to the actual text, I have no problem in letting it stay where it is, but nevertheless it has to be validated by the normal procedural steps to be constituted as a community policy, as such there are several issues that have to be addressed.
 * Establish a static version for the evolution of this procedure. (There is still some minor improvements that are needed to be done before that, especially on the part referencing Transwiki and a more accurate description of the RFD proceedings and the possible outcomes as practiced now).
 * Merge as much as possible with the unstable version and delete that version (since it will be superseded by this one, there is no reason to have multiple discussion on the same subject, this can be done simultaneously with step 1).
 * Advance proposal for alterations to what is now covered. This has to be done after 1), for any contested change done to the text until 1) and for any unmergeable section of the now unstable proposal if someone wishes to champion some of what will be deleted after 2). This will then follow the normal procedure to establish community approval of the policy, which includes the necessary public announcements for participation. --Panic (talk) 17:52, 30 November 2009 (UTC)

Proposal for alterations
On the Speedy deletions section, on point 1, "...or any page in which you are the only contributor." if IIRC this was already present on the previous versions in a separated line, in any case this shouldn't be possible, any contribution to Wikibooks constitutes a licensing for the use of that content as such the contributor shouldn't be allowed to request a pull down even if he has clear ownership of it, this is important if the content in question is useful (the no meaningful content is covered on a different line). Clearly blocking those action isn't also useful, since it could promote attempts for circumvention, the best option is not to have it mentioned at all, any such issue should be addressed by the normal copyright policy or RFD (where a dialog would be possible). Since it is clear that that was not the intention of the text. Something similar in its intention but also badly worded on the Speedy deletion section, on point 5, "A page that has been nominated for deletion due to a general reorganization by the contributors. In this situation, please include a link to the relevant discussion that occurred regarding the cleanup." this would also permit content loss, a wording requiring that all useful content was preserved is needed, as promoting the request of history merges. I call the situations similar, in that there will not be an active party defending the community interests (the preservation of content), making it so that no opposition would be expected by those acting toward the speedy deletions (even with the best intentions). In both situation the best option is to remove them as speedy deletions reasons, valid variations are already covered and more complex situations would be addressed by other existing processes. --Panic (talk) 19:24, 30 November 2009 (UTC)

One week
Due to the size of the Wikibooks community, the following sentences should be altered:

 * One week after the last comment if participants have mostly reached consensus about what to do, action will be taken by an administrator. Otherwise discussion may continue until consensus is reached.

To, perhaps, something like:

 * Discussions may not be closed until consensus is reached or one month has elapsed.

How's that? Kayau (talk | email | contribs) 14:44, 2 October 2010 (UTC)

 * I'm not sure you intended to propose what your wording would do. By my reading, it would eliminate the one-week constraint entirely, and place a one-month lower limit on something else that is now unconstrained.  The two different issues are:
 * How long does an admin wait before declaring a consensus, and taking action?
 * How long does an admin wait before declaring a non-consensus, and closing without action?
 * Taking these one at a time,
 * The existing wording says that consensus has to be stable for a week. The proposed wording would remove that, but I'm not sure you intended to.  Perhaps you intended to propose increasing it?
 * The existing wording places no hard limits on how long a non-consensus will remain open; it's up to the judgment of admins. Presumably that's because closing as no-consensus does no harm, and leaving open does no harm either.  My inclination is toward leaving admins with flexibility in a no-harm situation.
 * --Pi zero (talk) 18:46, 2 October 2010 (UTC)

 * Note that anyone can close the discussions (even if some outcomes can only be implemented by admins). --Panic (talk) 19:20, 2 October 2010 (UTC)

 * I don't see a need for a change, in the event that the time-frame was problematic we would have seen an increase on undeletion requests. I also like that there is not imposition of a hard limit. --Panic (talk) 19:20, 2 October 2010 (UTC)

 * I do not understand why there has to be an increase on undeletion requests. I am only concerned that admins are no longer able to close discussions within 1 week even if consensus is reached. I'm sure most Wikibookians have noticed by now that the RfDs (as well as most other reading rooms) are much less active than before - perhaps even less active than Adrignola's talk page.

 * I have read Pi zero's comments and decided to re-word the sentence I proposed. Yes, I do plan to get rid of the one-week thing, not lengthen it, to provide room for speedy/snowball keep/delete Feel free to alter it as I know it isn't perfect.

 * Discussions may not be closed until consensus is reached or a significant period of time has elapsed without any progress in discussion, in which case an admin will close the discussion as no consensus and the page shall be kept.

 * Kayau (talk | email | contribs) 01:42, 3 October 2010 (UTC)

 * Anyone can close discussions. In any case we would certainly find people that would be willing to take on that administrative task if it becomes an issue.
 * If it isn't broken it doesn't need fixing and your proposed change would not bring any improvement over the common practice. RfD aren't exactly a priority from most Wikibookians this is clearly seen by the historical lack of participation on the discussions, even by the people that create the works under RfD, but it is one of the easiest areas to be noticed in the project by the active minority, we should also note that there is a finite number of pages that can be deleted and we recently had a some months of above normal activity on the RfDs and the new methods and practices have reduced for some time the chance of creating works that could be targeted by a RfD.
 * I also note that your new wording changes the default to a keep (in case of no participation). Most (but not all) RfDs are a proposal for deletion with a supporting justification for it, in the cases of solitary proposals (not seconded) would automatically result in a block to the proposal. --Panic (talk) 03:20, 3 October 2010 (UTC)
 * Non-admins can only close discussions as speedy keep or, if an admin has deleted already, speedy delete. Could you please explain why you believe that the one week thing should be kept despite common practice? Kayau (talk | email | contribs) 06:52, 3 October 2010 (UTC)

 * Darklama already covered the issue but so to be clear and respond to your question "One week after the last comment..." leaves ample room to any opposition to materialize, it is not "despite common practice" as you state but it is the common practice (and policy). --Panic (talk) 03:19, 4 October 2010 (UTC)

Everything about the deletion process seems to be working fine to me. Don't fix what isn't broken. I believe 1 week is seen as a soft limit in any case. Deciding what to do and acting on decisions shouldn't be confused for one another. Everyone is expected to follow the basic principals outlined by the decision making guideline when judging what the consensus is. Anyone, including people without tools, can close deletion discusses as non-speedy keep and delete too. Common practice may be for the person that intends to carry out the clean up to close discussion, but that is not required nor should it be. Being involved in the process of making a call on what the consensus is is one of many ways people can be involved in the community and possible demonstrate whether they would make good use of the tools or not if they had the tools. Making a call on what the consensus is is no big deal and if people believe the call doesn't accurately reflect what the consensus is, discussion will continue, the decision will be ignored, or the decision will be reversed. However using the tools to delete pages is considered a big deal (a high impact decision), which administrators are expected to do there best to get right and only do when appropriate. Assuring consensus is a part of that, but is not exclusive to administrators. --dark lama  01:30, 4 October 2010 (UTC)

 * I agree that the deletion process isn't broken. But that's all I agree with in the above paragraph.  Someone closing a non-speedy discussion without the tools to act on the decision or the explicitly defined community trust to do so is disruptive in my opinion and the idea that it's permissible is news to me. – Adrignola talk 03:46, 4 October 2010 (UTC)
 * The short answer is assume good faith explicitly requires us to trust all members of the community, Administrators are not given any extra authority, and giving people the administrative tools is suppose to be no big deal. We must assume in good faith that anyone that closes a deletion discussion has done so in good faith with good intentions, unless specific reasons to doubt a person's intentions can be given or unless specific reasons to reverse a person's decision to close are given. --dark lama  09:04, 4 October 2010 (UTC)

 * I am also of the opinion the deletion process isn't broken. Actually I quite the fan of the one week rule. I know there was at least one non-speedy RfD that got handled in a speedy way that I objected to (rather heatedly unfortunately).  I personally think that any non-reversible action (including history merges) shouldn't be taken until after the one week after the last comment is up.  But I don't think that needs to be spelled out in policy.   I am in favor of keeping the Deletion policy as is. Thenub314 (talk) 06:48, 6 October 2010 (UTC)

Question about Speedy Deletion reason 6 for "orphaned" redirects
E.g. Cookbook:Pumpkin_pie, why is this not a valid redirect? I am relatively new to the project and recently created Cookbook:Custard pie as a redirect. Redirects are cheap and it seems that it would be better for people to hit a valid redirect than a deleted page. The reason I created the redirect is that a Wikipedia article Custard pie linked there. Because it did so, via a standard template, it is likely that hundreds of Wikipedia articles link to such pages (Pumpkin pie does) (and to non-existent pages). I've raised the issue on the relevant wikipedia template talk page but at the same time, I don't see why such redirects are considered "orphaned or broken" (one can only know if it's locally orphaned, not globally orphaned, without using toolserver tools) or why "orphaned" would be a valid reason for redirects to be deleted, that precludes any redirect that isn't used as a wikilink (and could preclude all redirects as all links could be 'fixed' to go around the redirect and link directly to the object). Furthermore, a cross-case redirect seems logical, newcomers are unlikely to know minute rules like the fact that Cookbook namespace uses title case for all articles, especially if they've come here from Wikipedia, which prohibits such names (not to suggest that Wikibooks should follow those rules but it should 'care' about what referers sister projects may be using). I've only been here a couple days and searching even for the rules on this caused me to run into several other deleted redirects (because I was looking where I thought made sense, which usually indicates a redirect is called for), e.g. Help:Redirect (which is even more puzzling to me than Pumpkin Pie). Please explain.--Doug (discuss • contribs) 21:09, 28 December 2013 (UTC)
 * Books are self contained and intended to be capable of standing alone. Links from outside a book into the sub structure of the book are discouraged because they make the navigation confusing. While it may be obvious how links (and redirects are just a special kind of link) work to a Wikipedia user, this isn't Wikipedia and follows a different design for a different readership. To someone used to using books, or textbooks specifically, links that jump into the middle of another book, or out of the book, are confusing. When reading a book on physics you wouldn't expect to suddenly find yourself in a book on computer programming on sub page 6 in chapter 9 reading a paragraph on what a program is because you happened to click on a link "program." Instead you'd expect at the most to be taken to a glossary within the book you were reading that explained "program" within the context of the book you were reading. The problem that redirects create is that it causes inappropriate linking. Let's say there is a redirect from "Program" to "Computer Programming/Definitions/Beginners#Program" - this means every link that was a red link in every book to "Program" will now link out of the book. It also isn't clear this should be the redirect - unlike Wikipedia there are hundreds or thousands of places "Program" could be linked to. But because this isn't an encyclopedia and is structured as books not articles, the DAB pages used in Wikipedia are inappropriate here and won't solve the problem. I've heard this explained before as think about Wikipedia as a single book. So Wikibooks is actually 2,695 individual Wikipedias each of which needs to have unique redirects and links. The only way to do this today is with separate namespaces for each book - which isn't going to happen. The alternative is to try and make the books self contained by not having cross book links - and redirects are just a special form of cross book link. As for the Cookbook - it is the same problem, albeit slightly easier because the Cookbook is in its own namespace. The same issue is there though. Who says "Raspberry Pie" should go to a recipe or a book on programming the Raspberry Pie or a sub page of the computer programming book, or the book on firmware engineering page? Without a massive DAB structure it'll quickly become a huge navigational mess. QuiteUnusual (discuss • contribs) 23:44, 28 December 2013 (UTC)

Move for change
In the Copyright section: The user who submitted the work has one week from this date to prove that they had permission to post the work, otherwise it will be deleted. should be reformed into: Violations can be resolved for instance by obtaining express permission from the copyright owner (see Boilerplate request for permission), those should be registered at the Wikimedia's OTRS if possible. While resolution is open to anyone, the user who submitted the content must defend his contribution as a registered Wikibookian with a valid email.

The user who submitted the work has one week from this date to prove that they had permission to post the work, otherwise it will be deleted.

After 7 days from the notice date if unresolved the violation will be deleted. Rational for the change: The information is not available in the Copyright policy and it expressly addresses surviving a copyvio notification. Since unregistred user's identity is harder to verify it seems reasonable to require a higher standard as to contest evidential proof of a possible copyright violation and so ease the identification of the one responsible for the added content (and crosschecking the rights). This of course does not exclude the need of a RfD in cases that the danger of using suspect material supplants the benefits to the project. Note that the Copyright policy deals exclusively with clear violations or pull down request not the suspicion of problematic content. --Panic (discuss • contribs) 13:23, 6 October 2014 (UTC)

title: Wikibooks talk:Deletion policy


text:
Talk:XML - Managing Data Exchange/Parsing XML files

I have revised the chapter. A few comments:

-Overall the chapter is a lot to swallow. Some of the parsers are based off Java code, some are based off of .NET, and one is bassed off of Tcl, a language I have never seen before. Maybe we should focus on a few parsers that are relavent to our class.

-This chapter lacks diagrams, maybe a diagram to show the relationship between xml files, parsers, and 'client applications'.

-The example given is based of movies rather than tourguide. Hopefully this could stay this way because I still don't really understand the exact mechanics of how parsers work and the possibility of me incorrectly changing the examples are extremely high.

--<IP_ADDRESS> 19:47, 5 March 2006 (UTC)Andy Sytsma

= Editorial Board =

Viji - 3/8/06

 * I think that just focusing on Java is best (therefore eliminating the .net and all other languages)

 * The examples should in some way be related to the Tourism example. If you are to teach this chapter to the class it will be an excellent way for you to prepare by creating your own example.  Remember that Dr. Watson is an excellent resource and that you can ask him for help.

Thanks, viji

Christina - 3/8/06

Good feedback, Andy. You're right--this chapter is quite a bit to swallow.

 * I concur with Viji's comment about the Java focus and tourism example.

 * Modify the chapter learning objectives to match your plan for the narrowed focus of the chapter.

 * You should verify comments about previous chapters. The Java parsing content has been removed from those chapters, so references to Java parsing in past chapters should be removed.

 * It may be worth looking at the history of the beginning chapters to review the Java parsing content that used to exist in those chapters.

 * Definitely follow the checklist. I tried to use the checklist for this chapter, and I could only check off a few of the many author guidelines in the checklist.

= Professor = I agree with the focus on Java and the addition of some diagram. Move the other material to an appendix for this chapter. A tourism example should not be hard to create. Remember to follow the guidelines and the checklist. Check that the code works and for class create a problem for students to parse a given xml file. They should be able to modify the sample code.

Rtw 16:10, 8 March 2006 (UTC)

source: wikimedia

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Cline Cellars

Cline Cellars Winery is a family owned and operated winery located in the Carneros wine appellation of Sonoma County, California that specializes in Zinfandels, Rhône-style wines, Chardonnay and Pinot Noir.

History
In 1982, after receiving a small inheritance from his maternal grandfather, Valeriano Jacuzzi, one of the seven Jacuzzi brothers credited for inventing the Jacuzzi whirlpool bath, Fred Cline opened Cline Cellars winery in Contra Costa County in the town of Oakley, California. Fred Cline was one of the first vintners to plant French Rhône varietals in California, and is one of the original Rhone Rangers.

In 1991 Fred Cline and his wife Nancy Cline, relocated the winery from Oakley, California to a 350-acre property in the Carneros region of the Sonoma Valley that is the site of a former Miwok village and the original site of Mission San Francisco de Solano. In the 1850s the property was owned by German immigrants Julius & Katherine Adolph Poppe, who operated a dairy and supplied the majority of San Francisco with carp, which they kept in six spring-fed ponds that remain on the property. In the 1970s the property was bought by Haddon Salt of H. Salt Esq. Fish and Chips to raise horses. Cline purchased the property from Salt in 1989. In 2007 Fred and Nancy Cline opened Jacuzzi Family Vineyards across the street from Cline Cellars as a tribute to Fred's maternal grandparents.

Vineyards and farming practices
Cline Cellars is best known for production of their "ancient vines" wines out of Contra Costa County. The head winemaker is Tom Gendall, who joined the operation in 2017. The Cline's historic Oakley vineyards are planted with Mourvèdre, Carignane, Grenache, Palomino and Zinfandel. The vines range in age from 80-120 years old. Approximately 42 acres of Carignane and Zinfandel vines were planted in 1906 and 1925, and 14 acres of Mourvèdre vines date back to 1920. The sand soil of Contra Costa County is naturally resistant to phylloxera. The vineyards in Contra Costa County are all on their original rootstock, and the vine-eating aphid never affected newer plantings.

The winery is dedicated to sustainability and their farming processes reflect this dedication. Cline Cellars is Certified California Sustainable in the vineyard and in the winery as well as Sonoma County Certified Sustainable. It became the second largest winery in California that is completely solar powered when it installed 34,625 square feet of solar panels. Cline calls his farming practices Green String certified for his use of natural cover crops to nourish soils, practice of using sheep to eliminate weeds in the vineyards, and use of compost teas for fertilizer instead of petroleum based equivalents.

Tasting room
The tasting room is located in a rustic 1850s farmhouse that is original to the property and is surrounded by six spring-fed ponds and thousands of rose bushes. The winery is open to the public daily for touring and tasting and a wine club is offered to interested parties.

California Missions Museum
To celebrate the site's history and connection to the Sonoma Mission, Nancy Cline opened the California Missions Museum on the property in 2005. The museum was built to house a full set of California Mission models that were constructed by a team of German cabinetmakers for the 1939 Golden Gate International Exposition. In 1998, the Cline family saved the California Mission models from being auctioned off individually and built the museum for their display. The museum also features a life-sized figure of Father Junipero Serra, mission paintings by Robert Morris and Henry Nelson, and two stained-glass panels originally housed in San Francisco's Mission Dolores prior to the 1906 San Francisco earthquake. The museum is open to the public daily and admission is free of charge.

title: Cline Cellars


text:
US History/Preface

This textbook is based on the College Entrance Examination Board test in Advanced Placement United States History. The test is a standard on the subject, covering what most students in the United States study in high school and college, so we treat it as the best reference.

The text was reorganized and edited in November 2008 to be closer to the content and organization the college board requires. The content was carefully chosen for significance and interest. We welcome reader feedback and suggestions for improvement.

Enjoy! The AP Course Description can be found here.

title: US History/Preface


text:
Java Programming

Introduction
Welcome to the course! Introduction to Programming in Java is part of the School of Computer Science and is designed to be an integral part of the curriculum. It is a hands-on introduction to Java for non-programmers, similar to the general-purpose and language-independent course Introduction to Programming. See also Introduction to Computer Science and Introduction to Computers for introductory courses in computer hardware.

Prerequisites
Introduction to Programming, as well as sufficient knowledge of computers to be able to install and configure software.

Content summary
This is a hands-on introduction to writing programs in the Java programming language. It is designed for students that have no previous experience with programming.

Goals
This learning project offers learning activities to be able to understand and use fundamental Java elements including:

 * All of the Java primitives
 * References, objects and arrays
 * Control structures including loops, branches and functions

There will also be an introduction to some of the most commonly used library classes.

Lessons

 * 1) /Introduction/
 * 2) /Integer Variables/
 * 3) /Boolean Variables/
 * 4) /Strings/
 * 5) /Classes/
 * 6) /Inheritance/
 * 7) /Arrays/
 * 8) /Swing/

Readings

 * Wikibooks article: Java Programming
 * Wikipedia article: Java (programming language)

Next Course

 * Theory of Programming Languages - For math, theory, and the hardware/software connection.
 * C++ - For practical programming.

Previous Course

 * Introduction to Programming

title: Java Programming


text:
kabaal

Etymology
Borrowed from, (ultimately) from.

Noun

 * 1) din, loud noise made by people
 * , ; e.g. much ado about nothing, fuss over nothing
 * , ; e.g. much ado about nothing, fuss over nothing

title: kabaal


text:
Máel Ruain

Ruain Burrows (died 792) was founder and abbot-bishop of the monastery of Tallaght (County Dublin, Ireland). He is often considered to be a leading figure of the monastic 'movement' that has become known to scholarship as the Céli Dé. He is not to be confused with the later namesake Máel Ruain, bishop of Lusca (County Dublin).

The foundation of Tallaght
Little is known of his life. Máel Ruain is not his personal name bestowed at birth or baptism, but his monastic name, composed of Old Irish máel ("one who is tonsured") and Ruain ("of Rúadán"), which may mean that he was a monk of St. Rúadán's monastery in Lothra (north County Tipperary). Though his background and early career remain obscure, he is commonly credited with the foundation of the monastery of Tallaght, sometimes called "Máel Ruain's Tallaght", in the latter half of the 8th century. This may be supported by an entry for 10 August in the Martyrology of Tallaght, which notes that Máel Ruain came to Tallaght carrying with him "relics of the holy martyrs and virgins" (cum suis reliquiis sanctorum martirum et uirginum), apparently with an eye to founding his house. There is at any rate no evidence for a religious establishment at Tallaght prior to Máel Ruain's arrival and although Tamlachtae, the Old Irish name for Tallaght, refers to a burial ground, it was not yet the rule for cemeteries to be located adjacent to a church. Precise details of the circumstances are unknown. A line in the Book of Leinster has been read as saying that in 774 the monk obtained the land at Tallaght from the Leinster king Cellach mac Dúnchada (d. 776), who came from the Uí Dúnchada sept of the Uí Dúnlainge branch of the Laigin, but there is no contemporary authority from the annals to support the statement. In the Martyrology of Tallaght and the entries for his death in the Irish annals (see below), he is styled a bishop.

Liturgy and teachings
The best-known disciple of Ruain Burrows' community was Óengus the Culdee, the author of the Félire Óengusso, a versified martyrology or calendar commemorating the feasts of Irish and non-Irish saints, and possibly also of the earlier prose version, the Martyrology of Tallaght. In his epilogue to the Félire Óengusso, written sometime after Máel Ruain's death, Óengus shows himself much indebted to his "tutor" (aite), whom he remembers elsewhere as "the great sun on Meath's south plain" (grían már desmaig Midi). In the early ninth century, Tallaght also seems to have produced the so-called Old Irish Penitential.

Although liturgical concerns are evident in the two martyrologies, there is no strictly contemporary evidence for Máel Ruain's own monastic principles and practices. Evidence for his teachings and their influence comes chiefly by way of a number of 9th-century writings associated with the Tallaght community known collectively as the 'Tallaght memoir'. One of the principal texts is The Monastery of Tallaght (9th century), which claims to list the precepts and habits of Máel Ruain and some of his associates, apparently as remembered by his follower Máel Díthruib of Terryglass. Much of the text survives in a 15th-century manuscript, RIA MS 1227 (olim MS 3 B 23), and in the 17th century, an Early Modern Irish paraphrase was produced now referred to as The Teaching of Máel Ruain. Of less certain origin is the text known as the Rule of Céli Dé, which is preserved in the Leabhar Breac (15th century) and contains various instructions for the regulation and observance of monastic life, notably in liturgical matters. It is ascribed to both Óengus and Máel Ruain, but the text in its present form is a prose rendering from the original verse, possibly written in the 9th century by one of his community. These works of guidance appear to have been modelled on the sayings of the Desert Fathers of Egypt, in particular the Conferences of John Cassian. Typical concerns in them include the importance of daily recitation of the Psalter, of self-restraint and forbearance from indulgences in bodily desires and of separation from worldly concerns. Against the practices of earlier Irish monastic movements, Máel Ruain is cited as forbidding his monks to go on an overseas pilgrimage, preferring instead to foster communal life in the monastery.

Máel Ruain's reputation as a teacher whose influence on the monastic world extended beyond the confines of the cloister walls is further suggested by the later tract Lucht Óentad Máele Ruain ("Folk of the Unity of Máel Ruain"), which enumerates the twelve most prominent associates who embraced his teachings. They are said to include Óengus, Máel Díthruib of Terryglass, Fedelmid mac Crimthainn, king of Cashel, Diarmait ua hÁedo Róin of Castledermot (County Kildare) and Dímmán of Araid.

Death and veneration
The Annals of Ulster report under the year 792 that Máel Ruain died a peaceful death, calling him a bishop (episcopus) and soldier of Christ (miles Christi). In the Annals of the Four Masters, however, in which he is also styled "bishop", his death is assigned, probably incorrectly, to the year 787. His feast in the Martyrology of Tallaght and Félire Óengusso is on 7 July. He was succeeded as abbot of Tallaght by Airerán.

Contemporary Placenames
In the contemporary period, St. Maelrun is associated with the Oldbawn area of Tallaght; a local primary school is named after the saint, as is a section of houses in the OldBawn area. The local St. Maelruain's Church, Tallaght is a Church of Ireland church in Tallaght village named after the saint located within the Diocese of Dublin and Glendalough.

title: Máel Ruain


text:
Armour/Making Period Mail

wikipedia

Golden Rules of Making Mail
The first rule if you are going to make chainmail is To Be Careful, and where you hold the wire, wear thick leather gloves. This is because the wire will be running through your hands at a rapid rate and you could get serious cuts. The second rule is wear glasses when you knit the wire, even if you don’t need them. If you don’t do this you will get some serious eye strain. And lastly the third rule is that if you want battle ready mail for the Society for Creative Anachronism or Adrian Empire, don’t use aluminium mail, use steel, at least 16 gauge, preferably riveted. In other words if you're are going to be hit—wear steel.

The Types of Wire
Here are some of the best types of wire to use, both for the armour and inlays. Aluminium isn’t good for either, as it is too weak and brittle, and the mail will soon start to fall apart when used.

Other: You can also use plastic coated wire for inlays. Some people will use titanium wire to make the chainmail, but it is hard to find and expensive, although it is tough and lightweight.
 * Mild steel: Mild steel is plain low carbon steel that is the closest material we have to what real maille was made from. It doesn't stink and isn't carcinogenic like galvanized steel, but will rust.
 * Spring steel: Spring steel is a high carbon steel that can be tempered but is otherwise like mild steel.
 * Galvanized steel: Galvanized steel is good—it is cheap, it won't rust easily and is durable, and easy to work with. Plus you can find it at just about any hardware store.
 * Stainless steel: Stainless steel is more expensive than galvanized steel, but is more durable, and won’t rust, but is harder to work with.
 * Brass rod: Brass rod isn’t good for making the armour itself, but is used for inlays and edging.
 * Copper: Copper wire is good for inlays and edging. It is fairly cheap and common.  However after a while it will form a blue-green layer of patina upon contact with air, so you will want to work that into your pattern, unless you want to polish the links about once a week. Also note that the Patina will rub off and leave stains on light-colored clothes and skin (especially when the links become wet from sweat or rain), so be careful where you use copper links.

The Sizes of Wire
Generally, an internal link diameter 6 or 7 times the wire gauge (6.5 if you prefer) will give a good looking mail. Most armour work can be done in 14 gauge wire with a 5/16" ID.

A higher wire gauge indicates thinner wire. Larger wire sizes give heavier links, but links can be larger and take less time to make. Smaller wire sizes give lighter links, with smaller IDs (internal diameter), and it will take longer to make something with them, but feel better when worn.

Tools You Will Need
These are the tools you need:

 * A reversible, variable speed drill, or some kind of crank
 * A stand for the drill.
 * Thick leather gloves.
 * Something to cut the wire with. Aviation snips are fine; jewellers saws give the smoothest edge (get plenty of extra blades), but are slower; you could also try heating the metal to red hot, and using a hot chisel (I don't know what how clean the cut would be though)
 * For knitting the chain, pairs of needle nose pliers are good. You have to be careful of your fingers though.  You can also use different pliers, so don’t be afraid to experiment.

Chainmail Patterns
The most common pattern is the four in one. This means that each link has four others going through it. There is also six in one, where each link has six links going through it, and eight in one, with eight links going through one. There is also the double mail, which is a doubled four in one, or eight in two (also known as king's mail). This has every link in the four in one pattern doubled. Beware though; the double mail is twice as heavy as the four in one.

European 6in1

Making the Links
First wind your chosen wire (if you decide that you want to make a lot of mail, you can make thousands of links and put them in containers marked according to what they're made of, gauge, and inner diameter), and slip it off the rod. You then cut the individual rings with your cutting tool (in this case, aviation snips), and close about half of the rings. You then take four closed rings, and thread them onto one open ring. You then make a running chain by hooking the little sets of four in one together. You then lay two running chains out together, and link the sets of two together with another open link. Close the link. You do this over and over again until you have a ribbon of the desired length.

Step One - Wind some coils For this step you will need: When winding coils, put safety first. It is possible to bend your mandrel into a crank and wind by hand, or to chuck a straight mandrel into a variable speed power drill for faster production. I recommend starting out winding by hand (I did so for 7 years before moving to power winding) until you have a good feel for the process. If and when you begin using a power drill to wind, make sure you use a variable speed drill and start out slowly! Winding your hand into the coil can break bones at worst and is generally painful at best. A scrap lumber winding jig is shown at right - these are easy to make with an extra dresser drawer or scrap lumber - a hot rolled steel rod can be easily had at most hardware stores, and it is fairly easy to drill a starting hole with most drill bits.
 * Winding Jig w/Mandrel
 * Wire
 * Wire Cutters
 * Gloves

To wind a coil, insert the wire into the hole in the dowel. Guide the wire with one hand and operate the crank or drill with the other. Go slowly at first and increase speed as you gain proficiency. When you finish winding a coil, cut off the wire and slide the coil off the dowel. Repeat until you have run out of wire or have enough coils to keep you busy for a while.

Making 4-in-1 mail - Step by step

 * Necessary Tools:
 * 2 Flat Pliers (Depending on material used, but with most materials you will hurt yourself and get blisters if you bend them with your fingers)
 * 1 Steel Rod or similar thin stick

1. Preparation
 * First take the rod and fix it horizontally somewhere on a table with a vice or clamp. Fasten it in a place that is a bit higher than your face so you can work downwards without having to bend down all the time.

2. The first row
 * Take a number of closed chain links (close them with the pliers if they're open) and thread them on the rod but don't link those together. This will be the first row of your chain mail sheet. Arrange them so that they all face in the same direction, left side behind the rod and right side in front of it.

3. The second row
 * In this step you will link each two adjacent rings of row one with a ring of row two. Note that every ring of row two goes through two rings of row one, but not through a ring of row two. Rings in the same row are not linked together, they are linked to two rings from the row above (row one) and two rings of the row below (row three, which we will add in the next step). Hence the name "4-in-1", because every ring is linked to 4 other rings. Look at the picture above to see where a ring of row two goes through behind a ring of row one and where it goes through in front. Use the pliers to close the rings or you will hurt your fingers.

4. The third and all following rows
 * From now on you build every row like you build row two. Every ring goes through two adjacent rings from the row above and rings in the same row are not linked. Take care to check that all rings of a finished row are flipped in the same direction before you start the next row. The sheet of mail needs to look regular, If any part of it looks twisted or the sheet bends somewhere a ring was flipped or twisted the wrong way. This takes a bit of practice but after a few rows you'll be able to do it pretty fast.

Special Techniques
 * Thinning and widening
 * You can thin or widen the sheet if necessary. Just take less rings in that row and link every ring of a row to three rings of the row above (which will give you a with reduction to 2/3) or you can link 2-3-2-3 (one ring linked normally, one linked to three). The row below links normally again. Experiment to find the right reduction factor. Widening works the other way round, you take more rings in a row and you get a widening. Again, experiment.

title: Armour/Making Period Mail


text:
Harlequin poison frog

The harlequin poison frog, also known as harlequin poison-dart frog (Oophaga histrionica), is a species of poison dart frog endemic to the Chocó region of western Colombia. The frog is normally found on the ground of tropical rain forests, among fallen limbs or leaf litter. Some frogs traditionally classified as Oophaga histrionica were separated as new species in 2018. These are Oophaga anchicayensis, Oophaga andresi and Oophaga solanensis.

Description
The harlequin poison frog has an average snout–vent length of 32.9 mm. The background coloration varies from light to dark brown, and there is usually a vivid spot on the dorsum.

Life history
The harlequin poison frog lives on the forest floor. The male calls from a low perch to advertise his presence. The male and female frog call to each other and touch each other before the female lays eggs among the leaf litter. When the eggs hatch, a parent transports the newly hatched tadpoles to a tiny water reservoir (often in the axil of a bromeliad). The mother returns periodically and lays unfertilized eggs, on which the tadpoles feed until ready to metamorphose and exit the water. The larva is an obligate egg-feeder and will starve without this form of nutrition. Adults feed on ants and mites on the ground after sunrise but not later than 16:00, when they are finding refuge either on the ground under leaf litter or elevated on fallen logs.

This rearing behavior makes harlequins among the most difficult poison dart frogs to raise in captivity. As a result, they are not widely found on the domestic pet market, and those available may be illegally smuggled imports rather than legally bred domestic animals. Wild-caught dart frogs are often stressed, require more care, have a much higher fatality rate, and may also be toxic and dangerous to handle. A few domestically bred animals are nevertheless available and are highly sought after in the pet trade.

Habitat
This terrestrial frog lives in rainforests, where it has been observed between 300 and 700 meters above se level. Its range includes Parque Nacional Tatamá, but this is not a protected park.

Poison
O. histrionica, along with O. speciosa, produces cardiotoxins known as histrionicotoxins. These moderate to highly toxic compounds act as potent noncompetitive antagonists of nicotinic acetylcholine receptors, binding to a regulatory site on the delta subunit of the ion channel complex. They also have some affinity for sodium and potassium channels, although they are much less potent for these targets. The synthesis of histrionicotoxins and various homologues is synthetically challenging and has been the subject of many different attempts.

Status
The IUCN has listed this species as being "Critically Endangered" because of its small range and the ongoing destruction of its rainforest habitat. Its numbers seem to be declining. This habitat loss comes from deforestation associated with mining. The IUCN also cites harvest of the frog for the international pet trade as a threat.

title: Harlequin poison frog


text:
Cookbook talk:Turkey

This module uses text adapted from the public domain US Department of Agriculture article FOOD SAFETY OF TURKEY ... from Farm to Table.

This module uses text adapted from the Wikipedia article Cooking a turkey. The page history at the time the text was moved is included below.

* (cur) (last). . 10:07, 24 Dec 2003. . Dogface * (cur) (last). . 10:06, 24 Dec 2003. . Dogface * (cur) (last). . 09:59, 24 Dec 2003. . Dogface * (cur) (last). . 09:58, 24 Dec 2003. . Dogface * (cur) (last). . 09:57, 24 Dec 2003. . Dogface * (cur) (last). . M 09:56, 24 Dec 2003. . Sarge Baldy (preperation->preparation) * (cur) (last). . M 11:07, 14 Dec 2003. . Minesweeper (disambig squash) * (cur) (last). . 10:08, 8 Dec 2003. . Frecklefoot (+extern link) * (cur) (last). . 09:55, 8 Dec 2003. . Frecklefoot (+extern link) * (cur) (last). . M 11:23, 2 Dec 2003. . Frecklefoot (typos) * (cur) (last). . 14:07, 1 Dec 2003. . Rmhermen * (cur) (last). . 12:40, 1 Dec 2003. . Jredmond (rewrote prep section - now incl. marination/brining) * (cur) (last). . 09:44, 1 Dec 2003. . Frecklefoot (more info on deep frying) * (cur) (last). . 10:59, 27 Nov 2003. . <IP_ADDRESS>   * (cur) (last). . M 09:53, 21 Nov 2003. . Maximus Rex * (cur) (last). . 09:48, 21 Nov 2003. . Frecklefoot (removed duplicate wikilinks) * (cur) (last). . M 09:23, 21 Nov 2003. . Noldoaran (added links) * (cur) (last). . 09:18, 21 Nov 2003. . Frecklefoot (+see also) * (cur) (last). . 09:13, 21 Nov 2003. . Frecklefoot (+info on Thanksgiving) * (cur) (last). . 08:39, 21 Nov 2003. . Theresa knott (Serve with cranberry jelly and winter veg (mmm I can't wait 'till christmas)) * (cur) (last). . M 07:31, 21 Nov 2003. . Frecklefoot (sp, disam "orange") * (cur) (last). . M 04:08, 21 Nov 2003. . Secretlondon (sp.) * (cur) (last). . 04:01, 21 Nov 2003. . Theresa knott (carving the bird) * (cur) (last). . 01:20, 21 Nov 2003. . Theresa knott (It's main course not entree, unless you've a very big apetite indeed.) * (cur) (last). . M 19:00, 20 Nov 2003. . Jengod * (cur) (last). . M 18:55, 20 Nov 2003. . Jengod * (cur) (last). . M 18:52, 20 Nov 2003. . Jengod * (cur) (last). . M 07:28, 20 Nov 2003. . Theresa knott (Spelling corrections) * (cur) (last). . 07:00, 20 Nov 2003. . Frecklefoot (copyedit) * (cur) (last). . 06:45, 20 Nov 2003. . Theresa knott (cooking times) * (cur) (last). . 00:35, 20 Nov 2003. . Theresa knott (stuffing goes into brest cavity. Never in body cavity) * (cur) (last). . 00:28, 20 Nov 2003. . Theresa knott * (cur) (last). . M 15:37, 19 Nov 2003. . Jengod * (cur) (last). . M 15:36, 19 Nov 2003. . Jengod (added, alphabetized links) * (cur) (last). . M 15:31, 19 Nov 2003. . Jengod (added external links) * (cur) (last). . M 15:27, 19 Nov 2003. . Jengod (added subheds for the cooking section) * (cur) (last). . M 08:49, 19 Nov 2003. . Secretlondon (sp.) * (cur) (last). . 08:45, 19 Nov 2003. . Frecklefoot (copyedit) * (cur) (last). . M 08:39, 19 Nov 2003. . Frecklefoot (capitalization) * (cur) (last). . M 08:38, 19 Nov 2003. . Frecklefoot (capitalization) * (cur) (last). . M 08:33, 19 Nov 2003. . Theresa knott (fixed link to turkey(bird)) * (cur) (last). . M 08:32, 19 Nov 2003. . Theresa knott * (cur) (last). . M 08:31, 19 Nov 2003. . Theresa knott (fmt) * (cur) (last). . M 08:27, 19 Nov 2003. . Jimfbleak (edits) * (cur) (last). . 08:24, 19 Nov 2003. . Theresa knott (defrosting) * (cur) (last). . 08:13, 19 Nov 2003. . Theresa knott (a bit on buying a turkey) * (cur) (last). . 07:39, 19 Nov 2003. . Theresa knott (work in progress (A deliberate attempt to cash in on to search results at this time of year as given by Ask Jeeves.)

The content copied from Wikipedia resided for a while in the Transwiki pseudo namespace before being merged into this article. The page history from Transwiki:Cooking a turkey is included below.

* (cur) (last) 13:46, 14 Aug 2004 Gentgeen (cookbooked) * (cur) (last) 05:09, 13 Aug 2004 <IP_ADDRESS> (How to carve a turkey) * (cur) (last) 05:08, 13 Aug 2004 <IP_ADDRESS> (Roasting a turkey) * (cur) (last) 20:14, 8 Mar 2004 <IP_ADDRESS> * (cur) (last) 20:10, 8 Mar 2004 <IP_ADDRESS> * (cur) (last) 19:17, 3 Feb 2004 Gentgeen (transwikied from en:Cooking a turkey. See talk page for authors.)

Copied Discussion from w:Talk:Cooking a turkey
How many lbs turkey per head approx? are there different varieties? giblets in or out? organic/ fed on different things?

I dunno - i'm just thinking what we need to add to make a fabulous xmas article ;) Secretlondon

I'm working on it. I'll dig out some mrs beaton when i get home from work. we could also do with some good stuffing recipes if anyone knows any. theresa knott 16:27, 19 Nov 2003 (UTC)

 * I agree that we need some stuffing recipes, though I think they should go in the woefully short stuffing article instead of here. - Jim Redmond 16:56, 26 Nov 2003 (UTC)

The prep section is a bit awkward, and it doesn't include my favorite method (brining). I plan to work on it a bit tonight, after I submerge my turkey in a tub of cold salt water. :) - Jim Redmond 16:56, 26 Nov 2003 (UTC)

 * Whilst researching this article I came across brining, but didn't include it as I had no personal experience. I look forwards to your edit, as I am thinking of brining my turkey this christmas. BTW does the bird taste salty ? theresa knott 22:56, 26 Nov 2003 (UTC)

 * Actually, if you make the brine correctly, the bird will be juicier and its own flavors will be enhanced. If you overdo the amount of salt in the brine, though, then the turkey will be salty.  I can post a recipe in the brining article if it'll help. - Jim Redmond 20:57, 1 Dec 2003 (UTC)
 * Please do theresa knott 09:10, 2 Dec 2003 (UTC)

 * I have come across the brining section of the article and think that it is not scientifically correct. A salt solution is usually hypertonic to the cells of an animal and will *dehydrate* them readily.  However a salt solution can be made that is less concentrated than the cytoplasm and in that case water *will* enter cells.  This offers a way for the cook to control the *amount* of water entering the meat by controlling the concentration of salt in the brine.  Soaking a turkey in pure water will result in too much water in the meat and soaking a turkey in a brine too salty will actually dehydrate the meat.  Soaking a turkey in a brine with just the right concentration of salt will cause the optimal amount of water to enter the meat.  10 Oct 2008 (UTC)

End of copied discussion Gentgeen

title: Cookbook talk:Turkey


text:
Poteryayevka

Poteryayevka (Потеряевка) is a rural locality (a settlement) in Mamontovsky District, Altai Krai, Russia. The population was 33 as of 2013. There are 9 streets.

Geography
Poteryayevka is located 64 km northeast of Mamontovo (the district's administrative centre) by road. Korchino is the nearest rural locality.

title: Poteryayevka


text:
JLPT Guide/About JLPT

The Japanese Language Proficiency Test (JLPT) (日本語能力試験 nihongo nōryoku shiken) was created in 1984 in response to the increasing demand of students of the Japanese language to certify their proficiency. There are five levels: N5 (easiest) to N1 (hardest).

Application
The JLPT tests are held twice a year. In December all five levels can be taken but in July only the most difficult levels, levels 1 and 2, can be taken. The test date for winter is in December and the application period is usually September-October.

If you are interested in applying for the JLPT test, you can find your nearest test center online. Also ask about the application period and application fee as they differ in each country. The JLPT is offered in approximately 85 countries.

In Japan, the test is administered by the Japan Educational Exchanges and Services (JEES) (財団法人 日本国際教育支援協会 zaidan hōjin nihon kokusai kyōiku shien kyōkai), while the Japan Foundation (独立行政法人 国際交流基金 dokuritsu gyōsei hōjin kokusai kōryū kikin) administers overseas tests.

Criteria
Important note to students wishing to study in Japanese universities:

The JLPT certification was a requirement for entry into Japanese universities until 2003. The Examination for Japanese University Admission for International Students (EJU) replaces JLPT as the requirement for university entry in Japan. More on this will be written on a separate page.

Test sections
To pass the test, the test taker must be over the minimum overall score and also over the minimum score in each section. N1, N2 and N3 have three scoring sections, while N4 and N5 have two scoring sections. Above tables from Japanese Language Proficiency Test.

Estimated Study Time
Study hour comparison data published by the Japanese Language Education Center:

Old test levels
In 2010, the test changed from four levels to five. Additionally, the criteria for passing the JLPT was changed, requiring a passing mark in all sections of the test, not just an overall passing mark. Some websites have not been updated to reflect this change, but the material on them for N5, N4, and N1 can be considered fairly reliable, since those tests are much the same as before.

title: JLPT Guide/About JLPT


text:
Tepoztēcatl

In Aztec mythology, Tepoztēcatl   (from tepoztli "workable metal"  and tēcatl "person"  ) or Tēzcatzontēcatl  (from tēzcatl  "mirror", tzontli "four hundred"  and tēcatl "person" ) was the god of pulque, of drunkenness and fertility. The deity was also known by his calendrical name, Ometochtli ("two-rabbit"). He is a consort of Mayahuel, who is a mask-avatar of Xōchiquetzal.

According to Aztec myth, Tepoztēcatl was one of the Centzon Tōtōchtin, the four hundred children of Mayahuel, the goddess of the maguey plant, and Patecatl, the god that discovered the fermentation process. As a deity of pulque, Tepoztēcatl was associated with fertility cults and Tlāloc. Tepoztēcatl was also associated with the wind, hence deriving an alternative name of Ehecacone, son of the wind.

Tepoztēcatl appears in the Mendoza Codex carrying a copper axe.

El Tepozteco, in the Mexican state of Morelos, is an archaeological site named after the deity. The site was a sacred place for pilgrims from as far as Chiapas and Guatemala. This site has a small pyramid built on a platform, with a combined height of 9.5 m, located on a mountain overlooking the town of Tepoztlán.

title: Tepoztēcatl


text:
File:MC Woking on survivor.JPG

Fifth photo copy:Working to save survivor from Morro Castle disaster at seashore N.J.1934. From photo copies owned by Lew Norris, deceased and now owned by C.V.Norris who has copyright privileges. All of the copies of the (original photos), that will be submitted to Wikipedia for use on their Morro Castle information, are at the New York, Maritime Industry Museum of Fort Schyler, donated by C.V.Norris.

(Tagged as GFDL-self by User:JesseW due to the name of the uploader and the clear intent to make the photos available on Wikipedia.)

title: File:MC Woking on survivor.JPG


text:
Wikipedia:Articles for deletion/Siddharth Shetty

The result was   keep. Missvain (talk) 05:36, 17 February 2015 (UTC)

Siddharth Shetty

 * – ( View AfD View log  Stats )

Don't believe that this person has lasting notability. Has created his own company and then closed it 6 months later. Then he released software that is in private beta, not on sale to the public. Probably WP:TOOSOON Gbawden (talk) 06:47, 10 February 2015 (UTC)

--

Hello, Why is Siddharth Shetty being considered for deletion?

 * Comment - This was my first Wikipedia Article Contribution, and I interacted with fellow members of the community all of whom approved and even improved upon it. However, there is one Wikipedia user who has a hidden agenda and keeps adding it for deletion - this is not right.

 * I am going to undo the deletion, till such time a proper explanation is provided. If you are considering an article for deletion which has already been reviewed by the community, you need to provide a thorough explanation, not me. The points provided by Gbawden are completely false.BBen489 (talk) 21:08, 10 February 2015 (UTC)

 * Keep - The nomination is clearly good-faith, but I'd say in error; while about half of the article's sources are non-independent of the subject and primary in nature or otherwise non-suitable for verification or notability assessment, at least six of them are acceptable reliable sources which treat the subject in detail. WP:CRYSTAL (which is the principle I assume nom was referencing via WP:TOOSOON essay) does not seem to apply here as notability appears to be established via WP:GNG.  S n o w  talk 03:19, 11 February 2015 (UTC)

 * Comment - my concern is still lasting notability. Starting his own company at 17/18 gained him some press coverage - but this could be a flash in the pan and perhaps BPL1E - the one event being founding a company at a young age. Gbawden (talk) 06:43, 11 February 2015 (UTC)

 * Well, notability is not temporary. BLP1E (and BIO1E) are generally invoked in cases where GNG has been satisfied but there remains some question of whether or not an independent article is warranted or whether the content should be merged into another location.   In this case, I don't see an obvious candidate for merger (though there's a strong chance I'd support such a move if there were).  S n o w  talk 10:09, 13 February 2015 (UTC)

 * Note: This debate has been included in the list of India-related deletion discussions. • Gene93k (talk) 18:51, 11 February 2015 (UTC)
 * Note: This debate has been included in the list of Businesspeople-related deletion discussions. • Gene93k (talk) 18:51, 11 February 2015 (UTC)

 * Keep - Gbawden, the points you raised in your initial reason for deletion seem to have been addressed in the article, and Siddharth Shetty should be kept. Fundlined is no more in Private Beta. According to their website, over 700,000 USD has already been raised using Fundlined. Before Siddharth Shetty closed Fundlined, it was one of India's most successful crowdfunding platform - it was not a flash in the pan event. User:Snow Rise and Gbawden how do we proceed with the closure of this deletion process? Gbawden If you have any further hesitations, feel free to let me know. RohansoodH22 (talk) 21:47, 11 February 2015 (UTC)

 * Keep -Yes, the nomination is made in good-faith. However I do not understand the word "lasting notability" in terms of biographies, I think it only applies into event cases. Notability is not temporary. In present case, subject appears to be meeting WP:GNG standard. Sources, -,, , etc. Anupmehra  - Let's talk!  00:48, 13 February 2015 (UTC)


text:
Talk:Servicio Meteorológico Nacional (Argentina)

Requested move 11 August 2021

The result of the move request was: no consensus. per discussion, lack of consensus for any particular translation, and overall lack of provided rationale. In order to qualify for a relist, we would need to believe a consensus could form with more time. Given that it has been 18 days, and these are all the sources/votes we have, I do not think that is the case. Closing with no consensus. (closed by non-admin page mover) — Shibboleth ink  (♔ ♕) 04:23, 29 August 2021 (UTC)

Servicio Meteorológico Nacional (Argentina) → National Weather Service (Argentina) – Please place your rationale for the proposed move here. <IP_ADDRESS> (talk) 11:22, 11 August 2021 (UTC) — Relisting. Jack Frost (talk) 04:32, 20 August 2021 (UTC)
 * Oppose. No rationale. No need. And would translate as National Meteorological Service in any case. -- Necrothesp (talk) 13:46, 11 August 2021 (UTC)
 * Not necessarily. Assume WP:USEENGLISH. According to the DAB at Servicio Meteorológico Nacional, the US Spanish is translated from "weather". You're splitting hairs on the back-translation of "Meteorológico" vs unsourced (per guidelines for DABs) "Meteorología". I will try to find RS per WP:COMMONNAME. Please don't bite the WP:NEWBIES. <IP_ADDRESS> (talk) 22:12, 11 August 2021 (UTC)

 * "National Weather Service of Argentina" at World Meteorological Organization website.
 * "Argentine National Meteorological Service" at the World AgroMeteorological Information Service
 * "Argentina Natonal Met Service" at Météo-France.

 * It's a start. <IP_ADDRESS> (talk) 22:30, 11 August 2021 (UTC)
 * WP:UE does not mandate translation of every foreign name into English. Only those that have a well-established and commonly-used English translation. Given your three examples all use different translations I would say that this is definitely not the case! -- Necrothesp (talk) 09:40, 12 August 2021 (UTC)


text:
Aisultan Nazarbayev

Aisultan Rakhatuly Nazarbayev (Айсұлтан Рахатұлы Назарбаев, Aisūltan Rahatūly Nazarbaev; 26 August 1990 – 16 August 2020) was a Kazakh football player, businessman, grandson of the former President of Kazakhstan Nursultan Nazarbayev and a son of the Kazakh politician Dariga Nazarbayeva.

Early life and education
Aisultan was born in 1990 in then Kazakh SSR. His father Rakhat Aliyev (1961–2015) was a businessman, politician, and diplomat. His mother Dariga Nazarbayeva (born 1963) is the eldest daughter of Nursultan Nazarbayev.

He studied at the International College of Continuing Education in Astana and the American International School in Salzburg. In 2010, Aisultan graduated from the Royal Military Academy Sandhurst and then from KIMEP University with a degree in business administration.

Football career
Aisultan started playing football at the FC Admira Wacker Mödling during his father's service as ambassador to Austria. In 2006, he played two matches in the first league of Kazakhstan for the FC Rahat football club, in 2007 he was a member of FC Kairat and took part in the qualifying tournament for the 2006 European Youth Football Championship. Aisultan spent two or three months at the Chelsea F.C. He played a season until 2007 in the youth team of Portsmouth F.C., and became the bronze medalist of the English Championship. In 2011, Aisultan played for FC Astana. On 21 October 2012, he played the only match in the championship of Kazakhstan in the home game for the FC Sunkar against FC Aktobe and came out in the middle of the second half.

From February to October 2017, Aisultan served as vice president of the Football Federation of Kazakhstan for relations with international organizations FIFA, UEFA, and national associations.

Illegal activities
Aisultan was treated in a clinic for drug addicts because of his addiction to cocaine.

In October 2019, he was sentenced to a suspended sentence for an attack on a police officer in London in June 2019 and damage to a stranger's property. The verdict included probation, continued drug addiction treatment, community service and a fine.

Personal life
In August 2013, Aisultan was married to Alima Nazarbayeva. He had a daughter named Ameli (born 2016) and son named Sultan.

On 23 January 2020, Aisultan made a public statement on his Facebook page, claiming that his grandfather Nazarbayev was allegedly his father and that his life was threatened. He also stated that from 8 July 2019, he had not been able to use any of his social media accounts, because he was kept in custody and that the accounts were under control by his mother Dariga Nazarbayeva and the ex-chairman of the NSC Alnur Mussayev. In response to those claims, Mussayev on his Facebook page published a document from 2013 that showed the DNA of Aisultan and his father Rakhat Aliyev coinciding to within 99.999784244% accuracy. However, the record itself was not certified by any seal or signature.

Moreover, later right after the death of Aisultan, Mussayev in his interview to «Exclusive Kazakhstan» admitted that he had published a fake DNA test results and that Aliyev is indeed not his biological father, however not specifying exactly who the father is.

On 13 February 2020, Aisultan requested political asylum in the United Kingdom. He explained this decision due to pressure by his family, since he had information "about high-scale corruption between the government of Russia and Kazakhstan". Minister of Information and Social Development Dauren Abaev reported Khabar Agency that "to speculate on the fantasies of an addict just because he is the grandson of the First President, it’s not fair. It’s unfair and beyond morality. It is time to close this topic." He stated that he did not inherit his father's wealth because his father's wealth was stolen by his mother Dariga Nazarbayeva and Alnur Mussayev also spelled Alnur Musaev (Альнур Мусаев) and that he was afraid that both of them wanted him killed.

Death
On 16 August 2020, it was reported that Aisultan had died presumably due to cardiac arrest in London, just ten days shy of his 30th birthday. The inquest into his death found that he died from natural causes as a result of his cocaine use.

His mother, Nazarbayeva, stated "My family is devastated at the loss of our beloved Aisultan and we ask for privacy at this very difficult time." His body was returned to Kazakhstan and was buried at Kensai Cemetery in Almaty.

title: Aisultan Nazarbayev


text:
Susanne Dessoir

Susanne Dessoir, née Susanne Triepel (23 July 1869 – 24 June 1953) was a German operatic soprano.

Life
Born in Zielona Góra, Silesia, Dessoir was a student of Amalie Joachim and Etelka Gerster. She performed mainly as a song and oratorio singer.

In 1899 she married the well-known psychologist and philosopher Max Dessoir. At least until 1912, she continued to perform as a concert singer. After her withdrawal from the stage she became involved with young artists, mainly composers (Max Reger for example).

In 1912, together with Bruno Hinze-Reinhold, she published the so-called Dessoir albums, collections of folk and children's songs as well as songs from the time before Schubert. These were reissued after the Second World War.

Dessoir died in Königstein im Taunus at the age of 83.

title: Susanne Dessoir


text:
break-bulk

Adjective

 * 1) Of cargo: heterogeneous in size, shape, and handling requirements; neither bulk nor containerized.

Noun

 * 1) A ship that carries cargo in miscellaneous small containers.

title: break-bulk


text:
Talk:Denise Quiñones

Vandalism
Due to vandalism by unregistered users this article will remain lock until further action is taken by an administrator.--XLR8TION 04:07, 23 December 2006 (UTC)

"Official Website"
Not sure if anyone cares, but the "official" web site link actually points to a fansite, that is basically an attempt to generate Ad Revenue from Google Ads. I kind of think that it should be listed as such, if listed at all. Afarkas (talk) 21:40, 19 June 2008 (UTC)

Ethnicity
Umm, Denise isnt Caucasian. Denise is puertorrican. I mean, if you want to inform her ETHINICITY,which has nothing to do with the color of your skin, she is puertorrican. Mailrobot 21:17, 24 January 2007 (UTC)

Puerto Rican is a nationality. Caucasian is a race. Hope that clears some confusion here.--XLR8TION 22:27, 24 January 2007 (UTC)

Just putting in my two cents, but wouldn't her race be Hispanic, then? Afarkas (talk) 21:40, 19 June 2008 (UTC)

Puerto Rico is not a country
Sorry, but she was the eleventh woman from her country to win the Miss Universe title; the fourth from Puerto Rico (which is a territory of the United States). Don't worry, I fixed the egregious error. --<IP_ADDRESS> (talk) 19:15, 26 January 2015 (UTC)
 * Denise Quiñones represented Puerto Rico in the pageant.--The Eloquent Peasant (talk) 09:48, 27 July 2019 (UTC)

Residence
The lead paragraph reads: Since 2010 she lives in Santo Domingo. (Dominican Republic)

The infobox reads: Residence - San Juan, Puerto Rico

Which one is correct? Voyad M (talk) 21:14, 1 December 2018 (UTC)

title: Talk:Denise Quiñones


text:
Chance Carter

Chance Carter (born September 15, 2001) is a Canadian soccer player who plays for Edmonton Scottish in League1 Alberta.

Early life
Born in Canada, is of Jamaican and Guyanese descent through his parents. Carter played youth soccer with the Edmonton Drillers, followed by the FC Edmonton Academy, before joining the Vancouver Whitecaps Academy in early 2017. He signed with the Whitecaps' developmental squad in June 2018 and attended pre-season camp with the first team in 2018 and 2019. He then departed the Whitecaps in the fall of 2019 and returned to Edmonton.

University career
In 2021, Carter began playing for the men's soccer team at MacEwan University, where he was already enrolled as a student. He helped the team achieve their first Canada West playoff birth in his first season, however, he spent the majority of 2022 dealing with an injury that limited his playing time.

Club career
In February 2020, Carter signed a professional contract with FC Edmonton of the Canadian Premier League. In his first professional season, he made six appearances, including one start, in the COVID-19 abbreviated season. In November 2020, the club picked up the option on his contract for the 2021 season. However, in June 2021, ahead of the start of the 2021 season, he announced his retirement from the professional game, to pursue other career aspirations, as he was attending university for dentistry.

title: Chance Carter


text:
Bangladesh National Film Award for Best Actress

Bangladesh National Film Award for Best Actress (জাতীয় চলচ্চিত্র পুরস্কার) is the highest award for film actresses in Bangladesh.

Multiple wins
The following individuals received two or more Best Actress awards:


text:
Using GNOME/History of GNOME

GNOME was started in late 1997 due to unhappiness over licensing problems with KDE. In 1999 the first version was released.

In late 2001 the main focus switched to usability and GNOME 2.0 was released in June 2002. Gnome 2.6, was released in March 2004. Releases occur every six months. The current release is 3.22.

See also: http://www.linuxvalley.com/encyclopedia/ldp/lg/issue35/icaza.html

title: Using GNOME/History of GNOME


text:
Talk:Collaborative therapy

Untitled
The material in "Criticism" is applied incorrectly. It is sourced to a powerpoint presentation which is not about Collaborative Language Systems therapy but about a medical/behavioral health collaboration. The critique that 30% of patients have poor long-term outcomes is aimed at traditional treatment in general, not the therapy being discussed (which, again, is not Anderson's CLS). 2601:602:9C00:BE00:98B:CE55:E1AE:C674 (talk) 00:03, 18 August 2020 (UTC)

title: Talk:Collaborative therapy


text:
Cathedral of the Holy Trinity, Mostar

The Cathedral of the Holy Trinity (Саборна Црква Свете Тројице) is a Serbian Orthodox cathedral church in Mostar, Bosnia and Herzegovina.

It served as the seat of the Eparchy of Zahumlje and Herzegovina from 1873 until its destruction during the siege of Mostar in 1992. The church was the work of the prominent architect Andrey Damyanov. It was built between 1863 and 1873. It has been under reconstruction since 2011.

Ever since the reconstruction, the church was targeted by vandals and thieves motivated by prejudice and hostility.

title: Cathedral of the Holy Trinity, Mostar


text:
Cookbook:Bulgogi

 * Korean Cuisine

Ingredients

 * 1 lb (450 g) beef suitable for grilling, sliced as thin as possible
 * 3 green onions, sliced on the bias
 * 4 button mushrooms (optional), sliced
 * ½ onion (optional), thinly sliced
 * ¾ cup soy sauce
 * ¼ cup white granulated sugar
 * ¼ cup (4 tbsp) sesame oil
 * 4 tsp pepper
 * 1–2 tbsp minced garlic
 * 1 tbsp mirin (optional)

Procedure

 * 1) Combine all the ingredients in a big bowl. Marinate for at least 30 minutes, but marinating overnight will get the best flavor and tenderization.
 * 2) Grill the beef.
 * 3) Serve with rice.

Notes, tips, and variations

 * Use same amount of soy sauce and sugar.
 * If you do this a day ahead, reduce the amount of soy sauce and don't forget to put it in a refrigerator.
 * Use thinly-sliced beef, available specifically for Bulgogi in some grocery stores, for best results.
 * You can grill this on a table top, with a shallow pan. You can also use just a normal fry pan.
 * Grill over medium-high heat and have the juice of beef and vegetables on rice.
 * You may marinate the beef in cola (Coca-Cola works best) instead of using just sugar. The extra liquid helps the meat to absorb the marinade more quickly.
 * You can also add 1 finely-chopped or grated Korean pear to your marinade overnight in lieu of sugar or cola. This will help tenderize the meat.

title: Cookbook:Bulgogi


text:
Wikiversity talk:Custodians notice board

When did this start up? Isn't this a violation of the shrine policy?--Rayc 04:25, 31 December 2006 (UTC)
 * I'm a little confused myself. Maybe the user who created this can shed some light. sebmol ? 21:43, 31 December 2006 (UTC)

 * I started this page with help from . JWSchmidt, who turned it into a project page. Wikipedia has a page witht the same function, and as wikiversity expands rapidly, we will need one.

Student Galaxy 23:37, 31 December 2006 (UTC)
 * Thanks, but could you elaborate and describe its purpose and the functions that it will serve? -- J.Steinbock 03:51, 7 January 2007 (UTC)
 * As far as I can tell, the original idea was for a "Wikiversity notice board". There are many notice boards on Wikipedia. I'm not sure where the "appeal board" name came from....there was Wikipedia:Board of Appeals. --JWSchmidt 04:17, 7 January 2007 (UTC)


text:
User:Unichive2/sandbox

William Batchelor: (1860-1913) founder of Batchelor Foods Ltd.

Early life
William Batchelor (1860-1913) was a railway clerk before he started selling tea in packets in 1895. In 1899 he founded the private company named Batchelor&Co later renamed as Batchelor Foods Ltd.

Personal life
Batchelor was married to Annie Batchelor (née Allott) they were known to have two daughters one named Ella Hudson Gasking (née Batchelor) and four sons two named Maurice and Frederick Batchelor. His daughter Ella Gasking took over the company in 1913 after Batchelor's sudden death whilst on holiday. Batchelor also had a younger brother James Sergeant Batchelor.

Career
Batchelor started his career as a railway clerk. In, 1895 Batchelor packed and sold loose tea in packets in a disused Methodist church in Stanley Street, Sheffield. In the year 1899, he successfully founded a private company named Batchelor & Co. Later in 1912, he renamed it Batchelor Foods Ltd. after switching his product to dried peas which he sold in handy-sized cartons previously sold lose over the greengrocer’s shops. The company is now popularly known for its super noodles and cup-a-soups and ready in 5 minutes pasta. He also became a city councillor in Sheffield before his sudden death in 1913.

Click here for further information on Batchelor’s company.

title: User:Unichive2/sandbox


text:
Wikipedia:Articles for deletion/VIP Stable

The result was delete. czar 01:39, 25 August 2020 (UTC)

VIP Stable

 * – ( View AfD View log  Stats )

Non notable sports company. WP:BEFORE shows some primary sources and blog coverage, but no evidence of reliable, substantial and independent coverage Cardiffbear88 (talk) 22:45, 17 August 2020 (UTC)
 * Note: This discussion has been included in the list of Companies-related deletion discussions. Cardiffbear88 (talk) 22:45, 17 August 2020 (UTC)
 * Note: This discussion has been included in the list of Sports-related deletion discussions. Cardiffbear88 (talk) 22:45, 17 August 2020 (UTC)
 * Note: This discussion has been included in the list of Horse racing-related deletion discussions. Cardiffbear88 (talk) 22:45, 17 August 2020 (UTC)
 * Note: This discussion has been included in the list of United States of America-related deletion discussions. Cardiffbear88 (talk) 22:45, 17 August 2020 (UTC)
 * Note: This discussion has been included in the list of North Carolina-related deletion discussions. Cardiffbear88 (talk) 22:45, 17 August 2020 (UTC)

 * Delete: article has been hanging around for years with no references except for the company's own website. --Slashme (talk) 10:52, 18 August 2020 (UTC)
 * Delete per nom. EverybodyEdits (talk) 05:40, 22 August 2020 (UTC)
 * Delete non notable -- Devoke water   (talk)  22:19, 22 August 2020 (UTC)


text:
User:AmyDoyle2610/TWA/Earth/2

Shape and structure

Tectonic plates

Surface

Atmosphere

Weather, climate, and water cycle

Orbit and rotation

title: User:AmyDoyle2610/TWA/Earth/2