Translations of this page:

This is an old revision of the document!


Contributing to SliTaz

SliTaz is made by volunteers and everyone is welcome. Introduce yourself on the forum (Maille) and say what you would like to do. The handbook has a short Contributing section.

Testing

  • Test development images published on 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: TazHelper.
  • Try packages from pkgs.slitaz.org with spk-add and report what is broken.

Reporting bugs

Open Report a bug (Filature report) from the dock or the Dash, describe the problem and send. In text mode:

$ filature-report

Accepted reports become public bugs on filature.slitaz.org/bugs. See Handbook: Reporting a bug. For a question rather than a bug, use the forum and attach the output of trame system report.

Packaging

Packages are built from receipts, small shell files; example using cookutils:

# spk-add cookutils
# cook setup --wok
# cook new mypkg
# nano /home/slitaz/wok/mypkg/receipt
# cook mypkg

When a receipt builds and the package installs, send it to a developer or post it on the forum for review.

Code

The source of every tool, including the handbook is in the Mercurial repositories on hg.slitaz.org. Read the code, fix it and send a patch or ask on the forum who maintains it.

Translations and documentation

  • 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.
 
en/guides/contributor.1792177620.txt.gz · Last modified: by linea