Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:guides:contributor [2010/05/09 16:30] – formatting seawolfen:guides:contributor [2026/10/16 19:10] (current) – linea
Line 1: Line 1:
 ====== Contributing to SliTaz ====== ====== Contributing to SliTaz ======
  
-There are so many ways you can help out with the SliTaz community. If you have a little free time, anything from artwork to package testing would be greatly appreciated!+SliTaz is made by volunteers and everyone is welcome. Introduce yourself on the [[https://maille.slitaz.org/|forum]] (Maille) and say what you would like to do. The handbook has a short [[https://doc.slitaz.org/handbook/help.html#contribute|Contributing]] section.
  
-Post a quick message to the forum or mailing list if you're unsure about anything. We don't bite!+===== Testing =====
  
-<note tip>We have a [[http://community.slitaz.org/|Community Platform]] where you can write blog posts, share wallpapers and images, and more. We encourage anyone that contributes to SliTaz to use this platform to show off their hard work!</note>+  * Test development images published on [[https://lab.slitaz.org/|lab.slitaz.org]]. 
 +  * Use **TazHelper** (on the dock, ''tazhelper'' in text mode): it runs automatic checks, guides you through a checklist and sends an anonymous test report. Manual: [[https://doc.slitaz.org/manuals/tazhelper/tazhelper.en.html|TazHelper]]. 
 +  * Try packages from [[https://pkgs.slitaz.org/|pkgs.slitaz.org]] with ''spk-add'' and report what is broken.
  
-\\+===== Reporting bugs =====
  
-==== Developers & Hackers ====+Open //Report a bug// (Filature report) from the dock or the Dash, describe the problem and send. In text mode:
  
-//(I'll leave this to the devs!)//+<code> 
 +$ filature-report 
 +</code>
  
-\\+Accepted reports become public bugs on [[https://filature.slitaz.org/bugs|filature.slitaz.org/bugs]]. See [[https://doc.slitaz.org/handbook/help.html#bugs|Handbook: Reporting a bug]]. For a question rather than a bug, use the forum and attach the output of ''trame system report''.
  
-==== Writers & Translators ====+===== Packaging =====
  
-Take a look at the [[guidelines| SliTaz Documentation Guidelines]], pick your page and go! At this stage, we just need solid contributions which will then be reviewed and updated. We're undergoing a [[http://listengine.tuxfamily.org/lists.tuxfamily.org/slitaz/2010/04/msg00063.html|Summer of Documentation]], in which we're concentrating on all the docs. You'll be in good company.+Packages are built from //receipts//, small shell files: example using cookutils:
  
-There's many areas in which you can help:+<code> 
 +# spk-add cookutils 
 +# cook setup --wok 
 +# cook new mypkg 
 +# nano /home/slitaz/wok/mypkg/receipt 
 +# cook mypkg 
 +</code>
  
-  * **Are you experienced with SliTaz?** +  * [[https://doc.slitaz.org/handbook/build.html|Handbook: Build your own]] 
-Go for the Guides. They take users through a process and range from customising your desktop to getting networking set-up. If you've had success with a procedure or feel one could be improved, this is the place for you!+  * [[https://doc.slitaz.org/manuals/cookutils/cookutils.en.html|Cookutils manual]] and [[https://doc.slitaz.org/manuals/cookutils/receipts-v2.html|receipt format v2]] 
 +  * Official receipts: the wok on [[https://hg.slitaz.org/|hg.slitaz.org]]. Packages are built on [[https://cook.slitaz.org/|cook.slitaz.org]].
  
-  * **Are you a general Linux user?** +When a receipt builds and the package installs, send it to a developer or post it on the forum for review.
-Take a look at the Handbook. A lot of general introduction to SliTaz, Linux or available software can be written there. Some people find it difficult to write technically, others struggle with more generically informative writing. Both are needed, in describing the topic and scope before brief instructions.+
  
-  * **Do you speak non-English?** +===== Code =====
-Translations are very important to the global audience SliTaz attracts. We need speakers of the above languages to ensure non-English readers experience better translations than automated services can provide! Those are the locales supported by the SliTaz system. We are aiming to add more in the future -- if you can help, please do!+
  
-\\+The source of every tool, including the handbook is in the Mercurial repositories on [[https://hg.slitaz.org/|hg.slitaz.org]]. Read the code, fix it and send a patch or ask on the forum who maintains it.
  
-==== Artists & Designers ====+===== Translations and documentation =====
  
-[[http://community.slitaz.org/image/tid/2|Wallpapers]] make a huge impact on the first impression users recieve. Some reviews barely comment further on artwork than the wallpaper!+  * [[https://doc.slitaz.org/handbook/|doc.slitaz.org]] is the official documentation, written by the developers. To improve the handbook, send a patch against the ''slitaz-doc'' repository or report what is wrong. 
 +  * This wiki holds community guides. Pick a page, check which release it was written for and update it for 5.1. 
 +  * Translations of the tools and of the handbook are welcome: ask on the forum which language and files need help.
  
-\\ 
- 
-==== PR & Journalism ==== 
- 
-//(Could we put together some blurbs or short pieces of writing for the press & community? Maybe contacts for them?)// 
 
en/guides/contributor.1273422634.txt.gz · Last modified: (external edit)