Write Yourself a Scheme in 48 Hours

This is outdated, not being worked on, and has been incorporated into the far better and already also featured Haskell Wikibook. It is not good to distract from the better book and clutter the bulk by keeping this in the featured list. —Preceding unsigned comment added by Backfromquadrangle (discuss • contribs) 06:04, 20 September 2015

Comment I lean towards support due to outdatedness. It should be noted that Write Yourself a Scheme remains somewhat popular in the Haskell community, and while it largely covers the same ground as Haskell it does so in a very different, even opposite, manner. I believe updating this book would be a worthy endeavour (unfortunately I don't see myself doing much towards that in the near future, as my hands are full with Haskell already).--Duplode (discuss • contribs) 07:03, 23 September 2015 (UTC)

Comment I'm vague on why this would be considered outdated. It's not obvious to me that featured-ness would necessarily come with an expiration date, so to speak, though I acknowledge there are some sorts of information that would, and am willing to keep an open mind on the point. I'd be interested in feedback on this from either of the above commenters, though it looks like one of them might not be around now. --Pi zero (discuss • contribs) 14:32, 30 June 2019 (UTC)

Basic Computing Using Windows

The following discussion has concluded. Please open a new discussion for any further comments.

Genes, Technology and Policy

I nominate this book as this book as featured book is hidden gem and also one of the few books in Wikibooks that are well researched and constructed.

Support As nominator Encik Tekateki (discuss • contribs) 07:55, 30 June 2019 (UTC)

OpenSSH

I've taken the Wikibook on OpenSSH about as far as I can for the time being and would appreciate feed back on taking it further. It's more or less nearing completion in my opinion, and being used, and in need of some review.

Aside from a technical review where I would track down those with domain expertise and check the accuracy of the book, what other actions are needed to make it ready? I'm thinking in particular of whatever wikification remaining or needing fixing. I've recently added some navigation aids, and posted a request to the Textbooks-L mailing list, but what else is needed to ensure that I have all the t's crossed and i's dotted? -- Larsnooden (discuss • contribs) 09:23, 31 July 2016 (UTC)

Personally I've read it one month ago and have found it pretty good, but I didn't have the time to enter each command, which would be the first step to improve it. JackPotte (discuss • contribs) 11:18, 31 July 2016 (UTC)

Ok, at this point it is probably ready for consideration as a Featured Book. Larsnooden (discuss • contribs) 15:45, 6 February 2017 (UTC)

I've now added the "featured book candidate" template to the book's main page to raise discussion. Larsnooden (discuss • contribs) 15:54, 14 April 2018 (UTC)

Support 136 pages without any maintenance left seems good to me. JackPotte (discuss • contribs) 16:51, 14 April 2018 (UTC)

Support These are quite few gems in Wikibooks that are finishing completion Encik Tekateki (discuss • contribs) 16:14, 27 August 2019 (UTC)

Oppose Needs a bit more work. Add at least one tutorial or workflow for one platform, especially Windows. The tutorial should be easy-to-read for users that can't fix tutorials or are compiler devs, but have basic reading comprehension and reasoning ability. Use the scrambled info in https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Public_Key_Authentication and in https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Host-based_Authentication and polish it a bit.

https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files#Managing_Keys needs to be expanded. and currently, it seems to be superficial text.

https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Automated_Backup; first para, line "sudo(8) works just fine -- if properly configured." could be improved. I know what it implies in theory, but in practice?

add missing links to rsync, tar, different ssh implementations; debugging common issues; where it makes sense. especially in https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Automated_Backup

sorry to be so abrupt and extremely succint. I like to improve this wikibook, premature upgrade to "featured books" are not a good gift to the unsuspecting. Retow324 (discuss • contribs) 01:39, 2 April 2020 (UTC)

Data Mining Algorithms In R

Really nice and crisp book. It has the following chapters

Dimensionality Reduction- Principal Component Analysis,Singular Value Decomposition,Feature Selection

Frequent Pattern Mining- The Eclat Algorithm,arulesNBMiner,The Apriori Algorithm,The FP-Growth Algorithm

Sequence Mining- SPADE,DEGSeq

Clustering- K-Means, Hybrid Hierarchical Clustering, Expectation Maximization (EM),Dissimilarity Matrix Calculation,Hierarchical Clustering,Bayesian Hierarchical Clustering,Density-Based Clustering, K-Cores, Fuzzy Clustering - Fuzzy C-means,RockCluster,Biclust, Partitioning Around Medoids (PAM),CLUES,Self-Organizing Maps (SOM), Proximus,CLARA

Classification- SVM,penalizedSVM,kNN, Outliers,Decision Trees,Naïve Bayes,adaboost,JRip

R Packages- RWeka,gausspred,optimsimplex,CCMtools,FactoMineR,nnet

A print version would be easier if the table of content wasn't split into six. JackPotte (discuss • contribs) 11:42, 31 July 2016 (UTC)

Sensory Systems

While this book was started by myself, it now contains chapters written by 18 other authors. It gives a comprehensive overview over sensory systems. Thereby not only the physiological aspects are covered, but also ways of simulating these systems with computers, and - for humans - ways of technically substituting for deficient sensory end organs (e.g. cochlear implants). Recently it has been expanded to include more information about sensory systmes in non-primates (spiders, fish, insects, ...). --Thomas.haslwanter (discuss • contribs) 16:13, 20 July 2014 (UTC)

Neutral I've gone through the book myself to finally put an end to this blankness here, and some problems I've found:

• The navigation contain "underscores", which doesn't seem professional for a featured book.
• Not a lot of pictures, may bore readers.
• Comma problems (Run-on sentences):
  • "In general, bitterness is very interesting because a large number of bitter compounds are known to be toxic, so the bitter taste is considered to provide an important protective function".
  • "The Gustatory System, or sense of taste, allows us to perceive different flavors from substances like food, drinks, medicine etc. Molecules that we taste, or tastants, are sensed by cells in our mouth, which sendsendS information to the brain."
    • ([])
  • "The free receptors, or type 4 joint receptors, are nociceptors"
    • (https://en.wikibooks.org/wiki/Sensory_Systems/Somatosensory_System#Joint_receptors)
  • Navigation for "Sensory Systems/Other Animals" looks unfit for a featured book: "Birds,Fish..." - That's something you'd usually see in developing books.
  • "In a dipole (the arguably most elementary magnet), the northern and southern poles are the sources of the field"
    • (https://en.wikibooks.org/wiki/Sensory_Systems/Other_Animals#The_geomagnetic_field)
• HUGE paragraphs, blocks of texts.

Though very little things for such a huge book, I don't expect a featured book to have this many problems in it. I may have high standards, but hey, an opinion is an opinion! --Atcovi (Talk - Contribs) 12:56, 7 February 2017 (UTC)

Non-Programmer's Tutorial for Python 3

The following discussion has concluded. Please open a new discussion for any further comments.

RAC Attack - Oracle Cluster Database at Home

This is a hands-on lab curriculum for learning about Oracle RAC cluster databases. I am the primary author. Just finished the print/pdf versions this week; finally feel that it's ready to suggest for featuring.

The book differs from most other wikibooks in that it heavily draws on "fair use" images. We discussed this a few years ago when I was first considering if wikibooks would be a good platform for the book. Unfortunately, it's not really possible to do a tutorial on this subject without drawing on fair use images. Not sure how this would impact the decision about whether it should be featured. ArdentPerf (discuss • contribs) 20:43, 5 April 2013 (UTC)

Coaching Youth Middle Distance Runners

The following discussion has concluded. Please open a new discussion for any further comments.

More C++ Idioms

Note: Self nomination. The objective of this book is to help elevate the knowledge of programmers who have moderate level of familiarity with C++ to a level where they feel much friendlier with C++. It provides an exhaustive catalog of modern reusable C++ idioms based on what expert programmers often use while programming/designing using C++. It is an effort to capture their vocabulary and concepts into a single work. Also see Nominations/Addition/More C++ Idioms.

Some facts about the book:

1. It has been translated in Japanese More C++ Idioms
2. It has been cited independently as a "good read" or "reference" 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, and more...

--Sutambe (discuss. • contribs) 20:25, 18 June 2014 (UTC)

• Neutral Yes the book is comprehensive, but looking at some pages to get a feel for the book, I notice examples without explanations to there strengths, weaknesses, and any relevant caveats, such as defining a macro named "break" will break the expected behavior of the "break" keyword. I notice some pages are missing references. I notice some idioms have drawbacks that can be addressed by using newer features of C++, such as deleting copy and assignment constructors rather then making copy and assignment constructors private. Some idioms should recommend using the standard library first, such as std::is_member_pointer, or explain why the standard library isn't being used. --darklama 14:41, 19 June 2014 (UTC)

I agree that explanations of some idioms can be expanded. Some idioms have received more comprehensive treatment than others. Regarding drawbacks of idioms: It is not the goal of this book to use the newest language features. In fact, some language idioms that are described comprehensively in the book will simply vanish in C++11 and C++14. Instead, I like the idea of recommending a language feature or a standard library if it exists in a certain environment (C++11/14). Can you please mention which idioms can use std::is_member_pointer? ----Sutambe (discuss • contribs) 17:18, 19 June 2014 (UTC)

I was thinking the same, that language features or the standard library should be recommended when available in a certain environment, and keep idioms for people that may be using an older environment, or anyone interested in understanding how the standard library might implement an idiom. My thinking is people trying to learn from this book are not being taught enough to make well informed decisions about what idioms to use or not use, and would miss out unless they look beyond this book.

I noticed the Member Detector idiom as one idiom where std::is_member_pointer and friends may be more appropriate than rolling your own, unless you want to understand how the standard library does it or are using an older environment. --darklama 19:03, 19 June 2014 (UTC)

• Neutral This isn't criticism of this book but I just feel there are too many Computing Featured books. Wikibooks needs to show people visiting this site that there is more than just IT books here. We should have a maximum and minimum number of books chosen as Featured books for each subject.--ЗAНИA ^talk 21:00, 19 June 2014 (UTC)

Lua Programming

I am nominating this book, which I have started working on in January 2013, because it is now complete and I think it is a book of sufficient quality to be featured on Wikibooks’ main page and be considered as a quality book. To comment each of the criteria mentioned in Wikibooks:Good books#Criteria:

• I believe this book conforms to all the Wikibooks policies and guidelines in a reasonable way.
• I think it has an appropriate and consistent definition (it is meant to teach the syntax and libraries of the latest version of the Lua programming language to a person with any level of programming experience, with a focus on embedded environments).
• I am certain that “[a]ll current organizational systems are properly and appropriately used.”
• I am absolutely convinced that it is “[a]ccurate, comprehensive, and concise enough to effectively teach and learn from in its current state.”
• It has a table of contents and uses navigational aids to make navigation easier.
• It is “[f]ree of major issues, like reorganization, orphaned or missing material, copyright violations, deletion, unmaintained, and unresolved disputes.”

There is some cleanup left to do, but this cleanup concerns pages of the old Lua Programming book that need to be history merged and manually merged into the main book. --Mark Otaris (discuss • contribs) 04:20, 19 June 2014 (UTC)

I mentioned orphaned material exists in Category:Book:Lua Programming on Lua Programming's discussion page, left over from the recent book merger, because there is some overlap between pages and was better to err on the side of caution.

As I was looking over pages I felt the book was poorly organized, for example the expressions chapter begins with "As explained before" and the chapter's emphases is on types and not on expressions as a person would expect. I also felt coverage was perhaps 50% for someone new to the language, for example when talking about Integers and Floating point numbers there is no mention of any reasonable limitations of supported value ranges or precision, which should be considered for portability, or how the exact range depends on configurations when the Lua interpretor was compiled, which should be understand when Lua is used embedded. I also notice a complete absence of coverage and examples for advance uses of the language, like using tables as classes to provide inheritance, polymorphism, data abstraction, etc. Examples for all the metatable methods seem to be missing as well. --darklama 12:20, 19 June 2014 (UTC)

I think the emphasis in the chapter about expressions is on types and operators, which are largely discussed in the types section (it is logical to discuss them there, since different operators apply to different types of values). And I think this is all fine, because expressions, as I have noted in that chapter, are made of values (with types) and operators.

It is true that the book lacks more technical details about Lua, but I specifically avoided them because a book meant to learn Lua isn’t the right place to teach that numbers are limited to a specific value. I think technical details of this kind belong in the Lua Reference Manual: they aren’t things people will have to know often, and when they’ll need to know them, people will naturally look there. Furthermore, these details are much less relevant in embedded environments. To be honest, in all the programming I’ve done in Lua, I have never needed to know what the limits or precision of numbers were.

I have intentionally avoided talking about objects, inheritance, polymorphism or anything else related to object-oriented programming or other paradigms. The Lua language is designed to allow the use of many paradigms without enforcing or encouraging the use of any of them specifically, and I have followed this design decision by only describing all the mechanisms Lua provides for various programming patterns, without describing how they can be used to enable these patterns (a discussion of object-oriented programming in Lua could easily take an entire chapter and not have much to do with Lua itself).

You are right that there are not examples for all the metamethods. I don’t think they are necessary, but adding one or two more examples could make them clearer. I don’t think it’s a major issue.

Finally, I think the book is largely comprehensive, if we exclude the technical details that someone wishing to embed Lua in an environment needs to know. This is indeed a huge gap that is missing. It is not necessary to have a comprehensive overview of the language itself, but it would interest many readers of the book, although it does not fit directly in the purpose, which is to describe usage of Lua in an embedded environment (and not how to create a such environment in the first place). I would be really glad if someone more experienced than I am with the C API and embedding Lua could fill this gap, but I do not believe I can do it myself. I’d like to thank you for your comments. --Mark Otaris (discuss • contribs) 15:23, 20 June 2014 (UTC)

I’ve just re-thought about what I said about the paradigms Lua enables the use of, and I have changed my mind. If I get the time, I will write an appendix describing how object-oriented programming can be done in Lua. I also wish to write such an appendix about unit testing, and I think there are some other things that could interest readers but that would not fit in the main flow of the book. --Mark Otaris (discuss • contribs) 15:56, 20 June 2014 (UTC)

I'm glad you have reconsidered. Put another way, I think people should be able to learn how to write reusable and portable Lua programs. My intent was not to suggest one paradigm over another. People just often use the OOP paradigm when writing reusable and portable Lua programs, because that paradigm is well suited for tables and metatables. Part of writing Lua programs that will work across different computer systems is knowing what assumptions are safe and unsafe to make. The Number type is represented as a double-precision floating-point number, so assuming that "myInteger = 2^64" means myInteger is an integer with no fractions or exponents is an unsafe assumption to make. I think citing the Lua Reference Manual is great, but people should also be able to learn to write safe and reusable code from reading this book without needing to buy another book to learn it, or have access to a working Internet connection after they are done reading this book. I think a featured computer programming book should make a reasonable attempt to teach everything within the scope of the core language. I would question featuring an English book that decided to leave "Z" or compound sounds to some other book for similar reasons. --darklama 21:02, 20 June 2014 (UTC)

• Neutral This isn't criticism of this book but I just feel there are too many Computing Featured books. Wikibooks needs to show people visiting this site that there is more than just IT books here. We should have a maximum and minimum number of books chosen as Featured books for each subject.--ЗAНИA ^talk 21:01, 19 June 2014 (UTC)

I have noticed this pattern as well, and I agree: Wikibooks seems to me to have more books about computing than anything else. However, I’d like to suggest another solution than limiting the number of featured books about any given subject: we could, instead, make the distinction between featured books about different subjects clearer and change the rotation system on the main page to show an equal number of books about all the eleven major subjects mentioned in the Card Catalog Office. This would have the added advantage of allowing us to show three featured books, all with different subjects, at the same time on the main page, instead of arbitrarily showing a random featured book, a random Wikijunior book and a random recipe (the cookbook would need its own subject, of course, and Wikijunior is already a category in the CCO. This is hard to automate, but that’s another issue, and this isn’t the right place to discuss any of this anyway. --Mark Otaris (discuss • contribs) 15:23, 20 June 2014 (UTC)

I have another solution: Nominate the worst featured computing book for removal. I invite anybody to search the worst ones and nominate it to clean the category. I have already nominated the Basic Computing Using Windows book. I think this one is the least advanced one. Ftiercel (discuss • contribs) 19:19, 21 June 2014 (UTC)

Japanese

The following discussion has concluded. Please open a new discussion for any further comments.

Linear Algebra

It's a very well-written book on linear algebra, with problems and solutions every chapter. It's a rare gem among technical books here: The presentation is clear, the flow is natural (from what I've read so far), and not at the cost of mathematical precision either. I wholeheartedly nominate this book to be featured. Kayau (talk · contribs) 15:44, 11 July 2016 (UTC)

• Support--Jusjih (discuss • contribs) 00:46, 20 December 2017 (UTC)
• Support as well. I'm doing some lite editing myself. —Justin (koavf)❤T☮C☺M☯ 05:09, 20 December 2017 (UTC)

  The LaTeX is not displayed properly into Linear_Algebra/Print_version/Part_1. JackPotte (discuss • contribs) 16:39, 20 December 2017 (UTC)

• Support Encik Tekateki (discuss • contribs) 21:14, 9 July 2019 (UTC)
• Support Nice book --ЗAНИA ^talk 08:58, 28 December 2019 (UTC)

Hypnosis

I came across this Wikibook years ago, and thought it looked well on its way to being featured. It now looks quite well-developed; there are empty subsections, but that just means there's room for further expansion, which is almost always true. Belteshazzar (discuss • contribs) 08:16, 14 April 2018 (UTC)

The fact that half of the TOC is transcluded from Hypnosis/Chapters, and the other half directly into Hypnosis, has prevented me to create an automatic print version (with {{printable}}). JackPotte (discuss • contribs) 13:34, 14 April 2018 (UTC)

Wikijunior:Transport Alphabet

I just cleaned up this Wikijunior book and nominate this book Wikijunior:Transport Alphabet to become featured book on main page

Preface to be put on main page:
People use transportation to move themselves and things everywhere. In this book, we are going to learn about air, land and water transportation types.

11 July 19 - Added the images mash up from OpenClipArt, what do you guys think ?

Proposed images:

• 
  Proposal 1
• 
  Proposal 2

Nominated by Encik Tekateki (discuss • contribs) 02:02, 6 July 2019 (UTC)

That would be "People use transportation [...]". --Pi zero (discuss • contribs) 02:56, 6 July 2019 (UTC)

Also, "to move themselves and things". Chazz (talk) 00:30, 9 July 2019 (UTC)

• I observe a problem with formatting of many of the pages, in which the pictures cover parts of the writing. --Pi zero (discuss • contribs) 01:29, 13 July 2019 (UTC)

Hi, I observed from mobile and desktop and see that there are no pictures covering the text, may know which alphabet is showing these symptoms? Encik Tekateki (discuss • contribs) 02:11, 14 July 2019 (UTC)

Every letter except G and O (and marginally Z). I do see that the mobile views of the pages do not have this problem; interestingly, the mobile view of G and O seems to have a bit too much vertical space. --Pi zero (discuss • contribs) 03:41, 14 July 2019 (UTC)

• I like the ones that are actually vehicles most. "Ostrich riding" is stretching the point quite a lot. I don't really understand "Crane" at all, not seeing its connection to the theme, transport. --Pi zero (discuss • contribs) 01:35, 13 July 2019 (UTC)

Changed as followed:

Crane -> Cable Cars

Ostrich Riding -> Ocean Liner

Note: For some part of Africa and Central Asia, people do actually uses camel and/or ostrich to transport humans and their goods around. I just included this to expand the children minds to world outside. Encik Tekateki (discuss • contribs) 02:28, 14 July 2019 (UTC)

I have no problem with some of those sorts of things; if you're going to have one, though, imho you should have more than one. Ostrich-riding seemed odd as the only animal-riding transport in the set. --Pi zero (discuss • contribs) 03:41, 14 July 2019 (UTC)