Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Last revision Both sides next revision
slackdocs:news [2012/08/25 08:44 (UTC)]
alienbob Remove first-person phrasing. 		slackdocs:news [2012/10/14 13:02 (UTC)]
alienbob [Wiki structure] Explain why some parts of the Wiki are read-only
Line 1: Line 1:
 ====== News from the site admins ====== ====== News from the site admins ======
  
-<note>This page will be expanded further in the next couple of days.</note>+ 
 +====== Project Charter ====== 
 + 
 +Knowledge is power. Scattered and unfocused power is useless. To state it plainly, the vision and the ultimate goal of the //Slackware Linux Documentation Project// is to become the primary worldwide resource for all Slackware related information. This is a lofty goal, indeed. However, there is confidence that venerable [[http://slackware.com/|Slackware Linux]], the oldest actively maintained distribution of [[https://www.gnu.org/|GNU/Linux]], has the user base to accomplish this goal. You are invited to [[http://docs.slackware.com/start?do=register|join]] and be a partner in this endeavor.  
 + 
 +Who can help? Anyone can, from your uncle Ed who tinkers with Slackware on his old laptop to Linux gurus with development level skill sets. All are welcome. All can [[slackdocs:contributing|contribute]] something of value to this project. A wiki type resource such as this thrives on community. You've seen for yourselves what the GNU/Linux and [[http://www.thefreedictionary.com/open-source|Open Source]] communities have done in the past and are still doing today. Working together, the potential for success is greatly increased. 
 + 
 +This project will need article submissions that run the entire gamut of Slackware knowledge. There will be a need for serious technical articles on hardware control, software applications, Slackware Linux implementations in business and personal computing, system administration, etc. Articles will also be needed from the every day [[https://www.linuxquestions.org/questions/slackware-14/so-you-want-to-be-a-slacker-what-do-i-do-next-644746/|Slacker]] on topics ranging from simple howtos to complicated resolutions and workarounds.  
 + 
 +Submitted articles, as with most wiki type resources, will be peer reviewed. Corrections may be needed, amendments added, and so forth. No article should be deemed unimportant. If it has relevance to Slackware Linux and will assist someone somewhere to better utilize this operating system, then it is a worthwhile article. What is being done here is being done for others. This is an archive of knowledge being built for the future. Your participation will be the mortar that holds the bricks in place. 
 + 
 +In order to fulfill the goals of this project, a reliance on civil discourse and the presence of a strong spirit of cooperation will be necessary. The rules here are simple. Be kind and considerate in your dealings with others. This project is not about individuals. It's about a community sharing and working together toward a goal. Your ego will not be a part of the //Slackware Linux Documentation Project//. Please leave it in the coat closet by the front door before you login. 
 + 
 +That is the our contract with one another and with the future.  
  
 ======= The choice of software ======= ======= The choice of software =======
Line 19: Line 33:
  
 To the left of the page you will find a sidebar with several boxes which can be edited (by the admins). Only the "toolbox" box is part of the wiki's //[[https://www.dokuwiki.org/template:monobook | monobook]]// template, and can not be modified. More specifically,modifying the content of that toolbox would make future upgrades a pain. \\ If you have suggestions about entries which should absolutely be in one of those boxes, let us know (use the [[talk:slackdocs:news|discussion page]]). To the left of the page you will find a sidebar with several boxes which can be edited (by the admins). Only the "toolbox" box is part of the wiki's //[[https://www.dokuwiki.org/template:monobook | monobook]]// template, and can not be modified. More specifically,modifying the content of that toolbox would make future upgrades a pain. \\ If you have suggestions about entries which should absolutely be in one of those boxes, let us know (use the [[talk:slackdocs:news|discussion page]]).
- 
-====== Project Charter ====== 
- 
-FIXME 
- 
-This is going to be the paragraph which explains the goals of and vision behind this documentation project, and the "rules" that are applying to its content. Call it a "social contract" if you decide you want to contribute to the project. 
- 
-<note warning>First Draft 082412 -vtel</note> 
- 
-Knowledge is power. Scattered and unfocused power is useless. To state it plainly, our vision and our ultimate goal for the //Slackware Linux Documentation Project// is to become the primary worldwide resource for all Slackware related information. This is a lofty goal, indeed. However, [[slackdocs:contact|we]] believe that venerable [[http://slackware.com/|Slackware Linux]], the oldest living actively maintained distribution of GNU/Linux, has the user base to accomplish this goal. We urge you to join us in this endeavor.  
- 
-Who can help? Anyone can, from Uncle Ed who tinkers with Slackware on his old laptop to GNU/Linux gurus with development level skill sets. All are welcome. All can contribute something of value to this project. A wiki type resource such as this thrives on community. We all know what the GNU/Linux and Open Source communities have done in the past and are still doing. Together, the possibilities are endless. 
- 
-This wiki will need articles on the entire gamut of Slackware knowledge out there. We'll be requesting serious technical articles on hardware control, software applications, Slackware implementations in business or personal computing, system administration, etc. We will also need articles from the every day Slacker on topics ranging from simple howtos to complicated resolutions and workarounds.  
- 
-Articles, as with all wiki type resources, will be peer reviewed. Corrections may be needed, amendments added, and so forth. No article should be deemed unimportant. If it has relevance to Slackware and will assist someone somewhere to better utilize Slackware, then it is a worthwhile article. What we do here we do for others. We're building for the future. Your articles will be the backbone of this project. 
- 
-We are all here to build for the tomorrow by filling this wiki today with every bit of Slackware and relevant Linux knowledge that we, as a world community, have to share. The rules here are simple. Be kind and considerate in your dealings with others here. We are all a part of the whole. Your ego will not be a part of the //Slackware Linux Documentation Project//. Please leave it in the coat closet by the door before you login. 
- 
-That is our contract with one another and with the future.  
- 
-<note>This is a first draft. Discussion is welcome and encouraged via the Discussion Page. Thank you.</note> 
  
  
Line 50: Line 42:
 ====== Wiki structure ====== ====== Wiki structure ======
  
-The core structure of the Wiki will be maintained by the site admins. That means: [[https://www.dokuwiki.org/namespaces | namespaces]], visual identity, access controls and the like. Ideas for changing the core structure of the Wiki can be submitted through our mailing list ([[http://lists.alienbase.nl/mailman/listinfo/slackdocs | http://lists.alienbase.nl/mailman/listinfo/slackdocs]]) or by editing the [[talk:slackdocs:news|discussion page]]. //__The actual content is all up to you!__// We will not refuse any article.+The core structure of the Wiki will be maintained by the site admins. That means: [[https://www.dokuwiki.org/namespaces | namespaces]], visual identity, access controls and the like. It also means that the namespaces "[[slackware:|slackware:]]", "[[slackdocs:|slackdocs:]]" and "[[slackbook:|slackbook:]]" are read-only for everyone except the editor/admin team. 
 + 
 +Ideas for changing the core structure of the Wiki can be submitted through our mailing list ([[http://lists.alienbase.nl/mailman/listinfo/slackdocs | http://lists.alienbase.nl/mailman/listinfo/slackdocs]]) or by editing the [[talk:slackdocs:news|discussion page]]. //__The actual content is all up to you!__// We are open to good ideas for enhancement of the existing structure and content, and will not refuse any article in the "[[howtos:|howtos:]]" section.
  
  
Line 56: Line 50:
  
 [//Not implemented yet//] [//Not implemented yet//]
-Our goal is to give you total creative freedom when writing content for the Wiki. But for the sake of quality assurance, we ask you to co-operate with one of our editors. \\ He or she may be able to offer suggestions about tags to use in your article so that it gets properly listed in the TOC. We also have tag categories that allow you to indicate your article applies to certain versions of Slackware only. You get the idea? You can also discuss an appropriate namespace to put your article in (consider a namespace as a wiki equivalent of a subdirectory - actually that is how it is implemented in the server's filesystem). The editor's primary role is to advise you on the structure of your article, ensure that it looks good, uses well-formed sentences - essentially that what any book editor would also do for you. You (the author of the article) will remain in control over the technical content! The editor will not enter into discussions about the (technical) content of yur article, unless he spotted blatant errors of course. We assume that since you wrote it, you know better what you are talking about than do we...+Our goal is to give you total creative freedom when writing content for the Wiki. But for the sake of quality assurance, we ask you to co-operate with one of our editors. \\ He or she may be able to offer suggestions about tags to use in your article so that it gets properly listed in the TOC. We also have tag categories that allow you to indicate your article applies to certain versions of Slackware only. You get the idea? You can also discuss an appropriate namespace to put your article in (consider a namespace as a wiki equivalent of a subdirectory - actually that is how it is implemented in the server's filesystem). The editor's primary role is to advise you on the structure of your article, ensure that it looks good, uses well-formed sentences - essentially that what any book editor would also do for you. You (the author of the article) will remain in control over the technical content! The editor will not enter into discussions about the (technical) content of your article, unless he spotted blatant errors of course. We assume that since you wrote it, you know better what you are talking about than do we...
  
 In order to assist the editor with his work, the Wiki implements a mechanism of "publishing a page". This means that the creation of a new page, or editing an existing page, will automatically put that page in "Draft" mode. The "Draft" message will be prominently visible on the page. If you are editing an existing page, then the original (approved) page will remain be visible to visitors of our Wiki. Only the registered users of the wiki (i.e. your fellow authors) will be able to see the draft instead of the approved version. \\ You have to consult one of our editors to get your page revision approved. That action will make it visible to the world. In order to assist the editor with his work, the Wiki implements a mechanism of "publishing a page". This means that the creation of a new page, or editing an existing page, will automatically put that page in "Draft" mode. The "Draft" message will be prominently visible on the page. If you are editing an existing page, then the original (approved) page will remain be visible to visitors of our Wiki. Only the registered users of the wiki (i.e. your fellow authors) will be able to see the draft instead of the approved version. \\ You have to consult one of our editors to get your page revision approved. That action will make it visible to the world.
Line 69: Line 63:
 ====== Sources ====== ====== Sources ======
   * Original author: [[wiki:user:alienbob|Eric Hameleers]]   * Original author: [[wiki:user:alienbob|Eric Hameleers]]
-  * Contributors: [[wiki:user:nocturnal.slacker|Eric Layton]]+  * Contributors: [[wiki:user:nocturnal.slacker|V. T. Eric Layton]]
  
 <!-- Please do not add anything below, except additional tags.--> <!-- Please do not add anything below, except additional tags.-->

In Other Languages
QR Code
QR Code slackdocs:news (generated for current page)