Difference between revisions of "ArchWiki talk:Contributing"

From ArchWiki
Jump to navigation Jump to search
(History clarity: re)
(Declaring scope: rm closed)
Line 1: Line 1:
== <s>Declaring scope</s> ==
Our current scope definition "what others may want to read" is too vague. Following [[Help talk:Template#Creation of Template:Out of scope]], I propose we add a Scope section to prevent scope creep.
Content on the ArchWiki needs to be about [[Arch Linux]] or software available through the [[official repositories]] or the [[AUR]].
Do not add content about:
* other operating systems
* software not available through the official repositories or the AUR
* third party network services
Articles currently violating this proposed blacklist: [[Haiku]] & [[Alternative DNS services]]
--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 06:44, 14 July 2018‎ (UTC)
:Scope is shortly mentioned in [[ArchWiki:About]] as ''anything Arch Linux can achieve'' and [[Help:Editing#Creating pages]] as ''relevant to Arch Linux''. It would be nice to expand what those mean, possibly on [[ArchWiki:About]] as it was supposed to answer those questions and [[Special:Diff/527598/next|intros always say the truth]] ;). Then we can link from other mentioned articles for explanation what content is welcome on ArchWiki. -- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 19:22, 30 July 2018 (UTC)
::Actually [[Help:Editing#Creating pages]] might be a better place, as it is specifically about adding new content to the wiki. -- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 19:33, 30 July 2018 (UTC)
::Thank you for finding these! I agree that [[ArchWiki:About]] is a better place and have opened [[ArchWiki talk:About#Refining scope]] with a new proposal. --[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 03:04, 31 July 2018 (UTC)
== History clarity ==
== History clarity ==

Revision as of 20:23, 15 September 2018

History clarity

about ArchWiki:Contributing#Always_properly_use_the_edit_summary note to ease searchability and history readability

  • auto summary the section title by clicking it's [Edit] button instead of the Edit on top of the page
  • in case of title/section rename also add to summary (after the above): rename [[#section title]] to [[#new section title]]

Ubone (talk) 05:40, 16 August 2018 (UTC)

That's a good idea but I prefer the comment syntax over regular section links in edit summaries. Draft:
When editing a section use its [Edit] link to automatically prefix /* Section name */ to the edit summary. The text between /* and */ becomes a section link in the edit summary. You can also use this syntax to make your edit summary more accessible, e.g. rename /* Install */ to standard /* Installation */.
--Larivact (talk) 06:15, 16 August 2018 (UTC)
The text between /* and */ becomes a section link
it... does? ― Ubone (talk) 07:00, 16 August 2018 (UTC)
oh, that little arrow... never knew it was clickable, it's a bit hardly visible tho ― Ubone (talk) 07:04, 16 August 2018 (UTC)
It would keep summaries cleaner if /* */ remains only as auto summary for the section being edited. To correct my initial example: /* (auto) section title */ rename to [[#new section title]]. I wouldn't use /* */ simply because it's easier for me to press [ or ] than shift-8 for * ― Ubone (talk) 07:36, 16 August 2018 (UTC)
A problem with /* */ is that if there's a space after it, it adds a colon. That makes it look weird if it's in the middle of a sentence. -- nl6720 (talk) 07:48, 16 August 2018 (UTC)
Good points, everybody. Updated draft:
To edit a section use its [Edit] link to automatically prefix /* Section name */ to the edit summary. When mentioning section names, link them using [[#Section links]]. Example: /* Install */ rename to standard [[#Installation]].
--Larivact (talk) 08:22, 16 August 2018 (UTC)
I would drop standard because while being a common mistake is not the point of the example. ― Ubone (talk) 08:08, 17 August 2018 (UTC)
I included it because the ideal edit summary contains a reason. --Larivact (talk) 08:18, 17 August 2018 (UTC)