Difference between revisions of "User talk:Thayer"

From ArchWiki
Jump to: navigation, search
(xmonad)
 
m
 
(19 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== [[XMonad]] ==
+
Why the renaming to include 'ArchLinux' in the titles?  We discussed this a bit before (been awhile to find the link though).  Basically what our conclusion became to be is that because this is the Arch Linux wiki, titles with the name as such would be as unnecessary repetition ([[ArchWiki_Tutorial#Adding_a_new_page]]), or did I miss something?
  
Hola: so your article came up on #xmonad. I noticed a few things, that it was slightly out of date and didn't warn about defaultGaps removed. I've updated it.
+
--[[User:Gen2ly|Gen2ly]] 01:10, 10 March 2010 (EST)
  
However, I'm still a little bothered about it. A project like XMonad absolutely requires good documentation, since it's chosen to go the first-class extension language route. As it is, we've got docs scattered across source code repos, Haddock documentation, the Haskell wiki, and Xmonad.org. I just feel a little uncomfortable adding yet another page to the spectrum.
+
:I wasn't aware the topic came up before. I marked the articles with the prefix to indicate that these are official articles--they will be linked from the homepage (and locked by default), replacing the existing pages currently in Django. Wikipedia uses a similar Wikipedia: prefix to denote WP site pages and internal policy.  Is this the same context of the previous discussion?
 +
:--[[User:Thayer|thayer]] 10:19, 10 March 2010 (EST)
  
Now, sections 1, 2, & 3 don't bother me. They're quite an alright summary or they deal with Arch matters. But "Tips & Tricks" seems to me to be both not comprehensive and vulnerable to bitrot. What do you say to moving ' Making room for conky or tray apps' and ' Dzen & conky-cli' into sections of the [http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions XMonad FAQ] wiki page (or maybe [http://haskell.org/haskellwiki/Xmonad/General_xmonad.hs_config_tips config tips])? --[[User:Gwern|Gwern]] 18:24, 30 March 2008 (EDT)
+
::Thanks for clarifying, Thayer. I, too, was wondering what was happening here. <tt>;-)</tt>
 +
 
 +
::Is there any reason you've chosen to use "ArchLinux" instead of "Arch Linux"? For consistency, I would prefer to see a space; but this is just me nit-picking. Also, I note that a few website resource pages duplicate existing wiki articles. Should we consider merging duplicates, or would you prefer to keep things separate?
 +
 
 +
::For example,
 +
 
 +
::* [[ArchLinux:About]] = [[Arch Linux]]
 +
::* [[ArchLinux:SVN Repositories]] = [[Getting PKGBUILDS From SVN]]
 +
 
 +
::-- [[User:Pointone|pointone]] 14:47, 10 March 2010 (EST)
 +
 
 +
:::I figured *someone* would bring up the whole name thing LOL
 +
 
 +
:::It's consistent with ArchWiki and DeveloperWiki. I also think it looks better both in the title and in the URL. Being that it's a wiki, camelCase is commonly used to join two separate words so I doubt many users will interpret it as, "ZOMG, I thought Arch Linux was two words!".
 +
 
 +
:::Regarding similar articles, yes once the new website design is in place we'll probably want to start cleaning up and/or condensing some articles. I think that the official pages should remain brief and to the point, whereas community pages can run the full gamut of topic and coverage, so some articles may be more suitable to community documentation. --[[User:Thayer|thayer]] 15:18, 10 March 2010 (EST)
 +
 
 +
----
 +
 
 +
You'll need to move i18n articles too if you're moving things around.
 +
 
 +
Also, you should really write the distro name as 'Arch Linux'. I don't believe keeping the prefix in CamelCase is a good practice. Why not make the whole title in CamelCase then? Articles should be written with proper punctuation, capitalisation, and spacing.
 +
 
 +
I really don't understand the need to prefix every article with the name either.
 +
I also don't believe that any article should be locked at all, unless there's been a history of vandalism or abuse. This is supposed to be a wiki after all.
 +
 
 +
Cheers.
 +
-- [[User:Louipc|louipc]] 08:53, 15 April 2010 (EDT)
 +
 
 +
:Which i18n article(s) were you referring to?  I wasn't aware of international pages for the press coverage and nearly every other page was created from scratch.
 +
 
 +
:With respect to the ArchLinux: vs. Arch Linux: debate and why they're prefixed at all, see my comments to Pointone (above).
 +
 
 +
:Regarding the locking, I agree for the most part. They are locked at the moment because I didn't want anyone mucking about while I was getting things organized.  Once published, I don't see a need to lock them down until someone gets stupid. --[[User:Thayer|thayer]] 12:29, 15 April 2010 (EDT)
 +
:: ArchLinux looking better than 'Arch Linux' is a matter of opinion and I believe the proper punctuation should be used. Spaces between words, spaces after colons, semi-colons, commas, periods, etc. Consistency is of no value if you're consistently wrong. -- [[User:Louipc|louipc]] 19:09, 15 April 2010 (EDT)
 +
::: I have to disagree there, it's a consistent naming convention of mediawiki (and is used in other wikis). By that rationale the use of ArchForums, ArchWiki:, DeveloperWiki: and more are all consistently wrong. --[[User:Thayer|thayer]] 19:49, 15 April 2010 (EDT)
 +
:: Concerning the i18n issue: [[Arch Linux]] is the original title, and all i18n pages are named after that format. With the new title, [[ArchLinux:About]], you will have to update all i18n pages to reflect the change. Nevermind that the 'About' is horribly redundant.
 +
::: [http://archlinux.org/about/ About Arch Linux] is the original source and title of the document.  There were no i18n pages for the django site.  Condensing all of the related About/History pages is definitely on the todo list, but it had to start somewhere so I chose to the official web page vs. the community article. --[[User:Thayer|thayer]] 19:49, 15 April 2010 (EDT)
 +
:: Maybe the 'ArchLinux' prefix would be better replaced by 'Official' for your intents. -- [[User:Louipc|louipc]] 19:21, 15 April 2010 (EDT)
 +
::: That's definitely an option I've considered.  It's early days still...the new design hasn't gone up yet and Dan is busy incorporating cloud hosting too, so there's certainly room for improvements along the way. --[[User:Thayer|thayer]] 19:49, 15 April 2010 (EDT)

Latest revision as of 23:49, 15 April 2010

Why the renaming to include 'ArchLinux' in the titles? We discussed this a bit before (been awhile to find the link though). Basically what our conclusion became to be is that because this is the Arch Linux wiki, titles with the name as such would be as unnecessary repetition (ArchWiki_Tutorial#Adding_a_new_page), or did I miss something?

--Gen2ly 01:10, 10 March 2010 (EST)

I wasn't aware the topic came up before. I marked the articles with the prefix to indicate that these are official articles--they will be linked from the homepage (and locked by default), replacing the existing pages currently in Django. Wikipedia uses a similar Wikipedia: prefix to denote WP site pages and internal policy. Is this the same context of the previous discussion?
--thayer 10:19, 10 March 2010 (EST)
Thanks for clarifying, Thayer. I, too, was wondering what was happening here. ;-)
Is there any reason you've chosen to use "ArchLinux" instead of "Arch Linux"? For consistency, I would prefer to see a space; but this is just me nit-picking. Also, I note that a few website resource pages duplicate existing wiki articles. Should we consider merging duplicates, or would you prefer to keep things separate?
For example,
-- pointone 14:47, 10 March 2010 (EST)
I figured *someone* would bring up the whole name thing LOL
It's consistent with ArchWiki and DeveloperWiki. I also think it looks better both in the title and in the URL. Being that it's a wiki, camelCase is commonly used to join two separate words so I doubt many users will interpret it as, "ZOMG, I thought Arch Linux was two words!".
Regarding similar articles, yes once the new website design is in place we'll probably want to start cleaning up and/or condensing some articles. I think that the official pages should remain brief and to the point, whereas community pages can run the full gamut of topic and coverage, so some articles may be more suitable to community documentation. --thayer 15:18, 10 March 2010 (EST)

You'll need to move i18n articles too if you're moving things around.

Also, you should really write the distro name as 'Arch Linux'. I don't believe keeping the prefix in CamelCase is a good practice. Why not make the whole title in CamelCase then? Articles should be written with proper punctuation, capitalisation, and spacing.

I really don't understand the need to prefix every article with the name either. I also don't believe that any article should be locked at all, unless there's been a history of vandalism or abuse. This is supposed to be a wiki after all.

Cheers. -- louipc 08:53, 15 April 2010 (EDT)

Which i18n article(s) were you referring to? I wasn't aware of international pages for the press coverage and nearly every other page was created from scratch.
With respect to the ArchLinux: vs. Arch Linux: debate and why they're prefixed at all, see my comments to Pointone (above).
Regarding the locking, I agree for the most part. They are locked at the moment because I didn't want anyone mucking about while I was getting things organized. Once published, I don't see a need to lock them down until someone gets stupid. --thayer 12:29, 15 April 2010 (EDT)
ArchLinux looking better than 'Arch Linux' is a matter of opinion and I believe the proper punctuation should be used. Spaces between words, spaces after colons, semi-colons, commas, periods, etc. Consistency is of no value if you're consistently wrong. -- louipc 19:09, 15 April 2010 (EDT)
I have to disagree there, it's a consistent naming convention of mediawiki (and is used in other wikis). By that rationale the use of ArchForums, ArchWiki:, DeveloperWiki: and more are all consistently wrong. --thayer 19:49, 15 April 2010 (EDT)
Concerning the i18n issue: Arch Linux is the original title, and all i18n pages are named after that format. With the new title, ArchLinux:About, you will have to update all i18n pages to reflect the change. Nevermind that the 'About' is horribly redundant.
About Arch Linux is the original source and title of the document. There were no i18n pages for the django site. Condensing all of the related About/History pages is definitely on the todo list, but it had to start somewhere so I chose to the official web page vs. the community article. --thayer 19:49, 15 April 2010 (EDT)
Maybe the 'ArchLinux' prefix would be better replaced by 'Official' for your intents. -- louipc 19:21, 15 April 2010 (EDT)
That's definitely an option I've considered. It's early days still...the new design hasn't gone up yet and Dan is busy incorporating cloud hosting too, so there's certainly room for improvements along the way. --thayer 19:49, 15 April 2010 (EDT)