User:Paulmnguyen/sandbox

Bruno Lanteri
I launched a project in late 2013 to start a biographic article on the Italian priest-founder Fr. Bruno Lanteri, currently Venerable. Visit the project page here: User:Paulmnguyen/Lanteri. I hope the writing will proceed smoothly and it can quickly be made available in the various languages indicated on that project page.

GNOME
The following suggestions were generated by a semi-automatic javascript program, and might not be applicable for the article in question. You may wish to browse through User:AndyZ/Suggestions for further ideas. Thanks, Emx 22:18, 14 November 2006 (UTC)
 * ✅ The lead of this article may be too long, or may contain too many paragraphs. Please follow guidelines at WP:LEAD; be aware that the lead should adequately summarize the article.
 * ✅ Per WP:WIAFA, Images should have concise captions.
 * ✅ Per WP:MOS, headings generally should not repeat the title of the article. For example, if the article was Ferdinand Magellan, instead of using the heading  ==Magellan's journey== , use  ==Journey== .
 * ✅ Please reorder/rename the last few sections to follow guidelines at WP:GTL.
 * ✅ Please alphabetize the interlanguage links.
 * There are a few occurrences of weasel words in this article- please observe WP:AWT. Certain phrases should specify exactly who supports, considers, believes, etc., such a view.
 * ✅ Please make the spelling of English words consistent with either American or British spelling, depending upon the subject of the article. Examples include: meter (A) (British: metre), center (A) (British: centre), organize (A) (British: organise), organise (B) (American: organize), ization (A) (British: isation), isation (B) (American: ization), analyse (B) (American: analyze), aging (A) (British: ageing), ageing (B) (American: aging).
 * Watch for redundancies that make the article too wordy instead of being crisp and concise. (You may wish to try Tony1's redundancy exercises.)
 * Vague terms of size often are unnecessary and redundant - “some”, “a variety/number/majority of”, “several”, “a few”, “many”, “any”, and “all”. For example, “ All pigs are pink, so we thought of a number of ways to turn them green.”
 * ✅ Please provide citations for all of the s.
 * Please ensure that the article has gone through a thorough copyediting so that it exemplifies some of Wikipedia's best work. See also User:Tony1/How to satisfy Criterion 1a.

Remaining tasks
Duplicated from above: You may wish to browse through User:AndyZ/Suggestions for further ideas. Thanks, Emx 22:18, 14 November 2006 (UTC)
 * Please ensure that the article has gone through a thorough copyediting so that it exemplifies some of Wikipedia's best work. See also User:Tony1/How to satisfy Criterion 1a.
 * Watch for redundancies that make the article too wordy instead of being crisp and concise. (You may wish to try Tony1's redundancy exercises.)
 * Vague terms of size often are unnecessary and redundant - “some”, “a variety/number/majority of”, “several”, “a few”, “many”, “any”, and “all”. For example, “ All pigs are pink, so we thought of a number of ways to turn them green.”
 * There are a few occurrences of weasel words in this article- please observe WP:AWT. Certain phrases should specify exactly who supports, considers, believes, etc., such a view.

GNOME
This peer review discussion has been closed. WP:LINUX wishes to take this article to FA quality. I copyedited the article recently but received no attention at Talk:GNOME. I just finished rearranging the sections in order to convey a stronger article structure and I would like some outside input on the scope and depth of coverage in this article. I think it is sourced fairly well, but I do not know what all is expected of an FA-class article in terms of what is already present in this article and what else should be added. A quick glance at current FAs would lead me to believe this one is short.
 * Previous peer review

Many thanks, –Paul M. Nguyen (chat&#124;blame) 02:49, 10 November 2010 (UTC) Shii (tock) 00:20, 13 November 2010 (UTC)
 * What is the GPL and why is it important? (Yes, I know the answer to this)
 * The third paragraph of the History section is actually about KDE and appears to be taken from an article about KDE or desktops
 * ✅ I don't think having a gallery in the body of the text is stylistically acceptable
 * ✅ The "Future developments" section appears vestigial and extraneous.
 * ✅ The "GNOME 3.0" section does not explain why this is an important version that deserves inclusion in the article, considering the main History header is only 3 paragraphs. Remove it?
 * ✅ PMN: could be blended and the section break removed. Consider better organization of History content.
 * PMN: need to expand the pre-3.0 releases section to discuss major breakthroughs then. move graphics to each section once written
 * The article should not be primarily constructed around primary sources. Please find outside sources such as Ars Technica or reliable Linux news sites, and fix fact tags
 * Too many lists in the "Project structure" section
 * Too many one-sentence paragraphs
 * Screenshots are too squinty and could be improved
 * Thank you! I'll be going over all of that and any dangling issues from the previous PR on my way to FA. Thanks, again! –Paul M. Nguyen (chat&#124;blame) 02:43, 13 November 2010 (UTC)

I think it would be useful to explain what KDE is in the start of the History section. The text presupposes a knowledge of these projects. Maury Markowitz (talk) 02:51, 26 November 2010 (UTC)

From Pnm
Pnm made some structural edits to the release history and had two suggestions relating to the release gallery:
 * Provide in the caption a highlight from each release
 * Add an entry for the upcoming 3.0 release (maybe the existing screenshot can just be moved).
 * Also, how about combining the numerous citations to GNOME press releases (in the release table) to one citation that points to http://www.gnome.org/press/releases/ ? Having so many makes the references section more difficult to use, and as primary sources, those citations aren't especially important.

Dashes

 * hyphen: -
 * n-dash: (Unicode: –; HTML: –)
 * m-dash: (Unicode: —; HTML: &mdash;)

GOCEreviewed test
Nothing:

User:

Date:

User, Date: