User:Johan G/Things I am working on: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(→‎Article/main namespace: + Howto:Improve an aircraft)
(→‎Aircraft development articles: About the additional mess I made and how I intend to fix that and the rest of the mess)
Line 7: Line 7:
* {{progressbar|20}} [[User:Johan G/Synthesising sounds with Audacity|Synthesising sounds with Audacity]] I am a noob on this, but have some ideas I have tested that I could develop further and disseminate.
* {{progressbar|20}} [[User:Johan G/Synthesising sounds with Audacity|Synthesising sounds with Audacity]] I am a noob on this, but have some ideas I have tested that I could develop further and disseminate.
* {{progressbar|10}} [[User:Johan G/Flight computer|Flight computer]] I just can not believe there wasn't an article on this yet.  Will restart this some day.
* {{progressbar|10}} [[User:Johan G/Flight computer|Flight computer]] I just can not believe there wasn't an article on this yet.  Will restart this some day.
* {{progressbar|0}} [[User:Johan G/Howto:Improve an aircraft|Howto:Improve an aircraft]] As a complement to [[Howto:Make an aircraft]], which is maybe 20-30% percent about that instead of about making an aircraft from scratch.
 
=== Aircraft development articles ===
I stumbled upon a stub named [[Creating an aircraft]] not too far ago, which I quickly expanded, just to find out that there already was a [[Howto:Make an aircraft]].
 
My article is now moved to [[User:Johan G/Howto:Create an aircraft]] pending to merging that with [[Howto:Make an aircraft]], which I have multiple issues with:
* Large parts are about improving an existing aircraft.  This should be split off to a separate article.
* Large parts are written like as if the authors was not aware of the more specific articles existing that covers a most of the subjects mentioned.  I feel that the article should only go into the very basics and provide pointer for the rest.  There is much enough ambiguity on this wiki as is.
 
I strongly believe the article structure of the wiki should have very little overlapping except what is needed for context, in essence DRY ({{wikipedia|Don't Repeat Yourself}})
 
* {{progressbar|0}} Merging [[User:Johan G/Howto:Create an aircraft]] with [[Howto:Make an aircraft]].
* {{progressbar|10}} Splitting up parts of [[Howto:Make an aircraft]] to [[User:Johan G/Howto:Improve an aircraft|Howto:Improve an aircraft]]


== Category namespace ==
== Category namespace ==

Revision as of 14:53, 13 May 2019

These are things I am working on, though I might work a lot slower with some than others.

Article/main namespace

Aircraft development articles

I stumbled upon a stub named Creating an aircraft not too far ago, which I quickly expanded, just to find out that there already was a Howto:Make an aircraft.

My article is now moved to User:Johan G/Howto:Create an aircraft pending to merging that with Howto:Make an aircraft, which I have multiple issues with:

  • Large parts are about improving an existing aircraft. This should be split off to a separate article.
  • Large parts are written like as if the authors was not aware of the more specific articles existing that covers a most of the subjects mentioned. I feel that the article should only go into the very basics and provide pointer for the rest. There is much enough ambiguity on this wiki as is.

I strongly believe the article structure of the wiki should have very little overlapping except what is needed for context, in essence DRY (Don't Repeat Yourself This is a link to a Wikipedia article)

Category namespace

Categorization of uncategorized pages

When used well, categories will make it easier to find related articles laterally in the category hierarchy, as well as find more general articles upwards.

Namespace Uncategorized pages 2014 Comments
29 Jan 12 Mar 27 Apr 1 May 4 Jun 8 Jul 1 Aug 1 Sep 1 Oct 1 Nov 29 Nov
Category 2 2 1 1 1 1 1 1 1 Should only contain Category:Root category
Template 6 6 0 0 0 0 0 0 0 0
Main 125 128 105 110 113 114 117 120 122 123 Out of 3,485 articles in total.
Files 865 865 865 824 819 819 704 689 689 689 Out of 8,445 files in total.
Namespace Uncategorized pages 2015 Comments
31 Jan 1 Mar 1 Apr 1 May 27 May 4 Jul 1 Aug 2 Sep 2 Oct 21 Oct
Category 1 1 1 ? 3 3 ? 6 6 6 Should only contain Category:Root category
Template 0 0 0 ? 0 1 ? 1 2 2
Main 144 124 127 ? 126 127 ? 128 130 134 Out of 3,485 articles in total.
Files 679 673 665 ? 623 617 ? 605 605 587 Out of 8,445 files in total.
Namespace Uncategorized pages 2019 Progress Comments
3 May
Category 29 90}% completed Of about 790 categories (3 May 2019). Should only contain Category:Root category
Template 62 80}% completed Of about 490 templates (3 May 2019)
Main 211 60}% completed Out of 3,485 articles in total.
Files 603 90}% completed Out of 8,445 files in total.

Adding structure to the categories

  • Separating images and file from article categories, but linking together image and article categories.
  • Diffusing screenshot categories into a structure mirroring the aircraft category structure, which in turn mirrors Wikipedia's aircraft category structure.

It would also be wonderful if new editors could somehow be educated to understand that categories are not tags. Presumably they expect images to be easier to find if they add as many categories as possible (that still seem at least remotely related).

I would consider that better file names and file descriptions (as well as some linking) probably is more efficient.

Category tree tool shortcuts

Other useful links

Template namespace

Messagebox meta template(s)

  • 90}% completed Playing with the looks of the messageboxes. See Messagebox style sandbox.
  • 70}% completed Documenting related templates to be used by a meta template.
  • 30}% completed {{messagebox}} meta template in sandbox.

Documenting undocumented templates

FlightGear wiki namespace

Policies

There is unfortunately a growing need for policies. Like with categories I strongly believe that they should form a tree, with a general unspecific, very concise and more or less universally agreed on policy at the root.

As these will be used both as guidelines for users, as guidelines for users wanting help from administrators and as guidelines for administrators, there will need to be some form of consensus about them as well as a policy describing how to propose new policies, changes in existing policies and amendments to polices.

User essays