Kullanıcı:Hatas/Wiki experiences for Linux distributions
When we examine the community certification centers (wiki pages) of various Linux distributions serving in Turkish or English language, we see that many of the similar errors are repeated. Some important errors or irregularities can be listed as follows: Not to go down to the end user level in the documents (distribution, targeting the desktop users, but the issues are explained through the command line), the main purpose of the site without questioning the Linux and free software, including all kinds of articles related to the format and expression it speaks different languages.
As a contributor who has worked actively for more than a decade on the community certification sites of various Linux distributions, I would like to share some of my experiences with this article. Wishing to be useful ...
Suggestions
The following list many suggestions on the Ubuntu wiki Turkey in a 'Policy' brought into the matter. In the certification center where you are a contributor, you can transform your principles into written policies.
1. Do not explain the operations that can be done with the interface through the commands
Before you begin the documentation work, start by searching for the answer to this question: Is this deployment targeted at desktop users or a distribution for more professional users (such as Slackware, Arch, Gentoo)?
If the target audience of the distribution is desktop computer users, you should stay away from the command line as much as possible in the documents you will prepare and tell the issues through the graphical interface. For example, you should not describe the installation of an application that can be installed via the package manager graphical interface via the command line. Unfortunately, in the Linux wiki pages of most Linux distributions, we come across documents that describe almost the simple cut-and-paste operations via the command line. " How to install Gimp? " "" Open the terminal and give the command sudo apt-get install gimp...
It may be possible to do a job that can be done with 10 mouse clicks at the interface with two clicks from the command line, but this does not exclude the fact that the command line is an expert user tool. A desktop user who doesn't use the command line all the time will probably forget about the one-line command shown to him after a few minutes. A process that can be done with 5-10 clicks over the interface may not be forgotten for a long time.
2. Do not aim to increase the number of articles, focus on content quality
Article is easy to write; it is difficult to produce an attentive, quality document. Article is easy to write, it is very difficult to keep up to date. If you have fewer articles, you can produce better quality documents and keep them up to date. You don't need hundreds of items to keep your desktop empty-handed, and 30-40 core documents that you need to create will be enough to back your Vikin.
The documentation pages of many Linux distributions, including Ubuntu Turkish Wiki, are often licensed under free content licenses such as Creative Commons and GNU GPL. Therefore, under the terms of the license you can copy the content you like on these sites and adapt it to the Linux distribution you contribute. Some free content licenses require you to refer only to the original source of the copied content and license the content you upload with the same or similar license, while some free software licenses may not allow the content to be copied for commercial purposes. The requirements for commonly used free software licenses for copying are described in the following sections.
If you are documenting a deployment that is addressed to desktop users, such as Ubuntu, you can give priority to the following issues when starting out.
- The definition of distribution, by whom it is developed, whether it is paid or not, license etc. can be accessed from the main page. open a question-and-answer article about topics (examples: What is Ubuntu?, About Debian).
- In a way that a user who has never installed Linux in his life can understand; Prepare documents describing each step of installing the system and provide a link from the main page to access them (see Installation). UbuntuViki contains up to 10 items related to the installation topic, and these are the most frequently clicked items.
- To teach Linux usage to a user who has never used Linux in his life, prepare a tidy - two documents that go down to the end user level, such as Ubuntu getting started guide and Frequently asked questions and link to the home page.
After preparing and completing these documents carefully, you can take a breath, you now have a certification center!
3. Do not rewrite articles in Wikipedia. Give the Interviki connection!
Especially when we look at community-based Linux wiki projects, we see that many of the software and Linux-related concepts that can be used in Linux are tried to be explained repeatedly.
- * Almost all Firefox, LibreOffice, Gimp, VLC, K3b, KolourPaint, Blender, Inkscape We see. For example, for Firefox, five separate Linux distribution communities in the Turkish language open five separate introduction pages. This loss, the loss of free software only in the Turkish language, and multiply it by dozens of languages, can you imagine how much effort is wasted? As a concrete example; Pardus The PardusWiki community site, which is active between 2005 and 2012, is not currently live (see Web archive) around 450 application introduction items were once written.
- The biggest loss of effort in repetitive content in Linux distribution wiki stems from software introduction materials. Of course, we don't have any other lost-illegal items.
- * In many of them we see a page about Linux related or related concepts. For example: Linux, free software, open source, GNU, Unix, KDE, Xfce, Linux distribution, operating system, Android, such as iOS.
- * We see some of them open articles about various free software-content licenses. For example: GPL, LGPL, BSD license, Creative Commons, Apache License, MIT License.
However, there are countless articles in Wikipedia on all these issues. Ubuntu Wiki site in Turkey have taken an important step to put an end to these losses. First, Policies and guidelines by preparing the page we've agreed to the following principles: " 'identification unless the application is not essential in the ubuntuvi on-site material does not include the diverted instead to users on Wikipedia about.' '" In the policy statement, We have also clarified the necessary conditions and explained in which cases a software introduction material can be opened.
To make it easy for users to link to Wikipedia, we've done a little editing (*) in UbuntuViki. This means that when we add the "v:" prefix to the beginning of an internal link in UbuntuViki, we automatically redirect that link to the Wikipedia page. For example, when we want to link to "LibreOffice" in Wikipedia, we write [[v:LibreOffice|LibreOffice]]. When we write this, the result is: LibreOffice. So we don't have to open an item called LibreOffice in UbuntuViki.
 Special:Interwiki page (*) Any contributor with a retainer authority on a Viki site can go to the Special:Interwiki page and make the Turkish Wikipedia an interviki link. However, in order to see and use the Special:Interwiki page, you must have the extension of the site administrator Extension: Interwiki enabled on your wiki. I also need to add the following line to the file LocalSettings.php which is located in the MediaWiki installation folder:
Any user with retainer privileges now enters the Special: Interviki page and defines a prefix for Wikipedia by clicking the corresponding button, enters the URL address, then activates the forwarding option. |