====== 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! Post a quick message to the forum or mailing list if you're unsure about anything. We don't bite! We have a [[http://scn.slitaz.org/|Community Network]] 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! \\ ===== Developers & Hackers ===== === Packaging === If you are comfortable with the Linux compiling process (//configure, make, make install//), you can help by creating SliTaz packages. We have an automated tool to build packages from source called [[http://doc.slitaz.org/en:cookbook:wok|Tazwok]]. All SliTaz packages contain a [[en:cookbook:receipt|receipt]] - a text file where you control the building process using some variables and functions. You can browse the [[http://hg.slitaz.org/wok|wok]] to see some receipts and understand how they work. Please take time to read the [[en:cookbook:devcorner|Developer's]] page beforehand and practice locally with some new or existing packages. When you feel ready to start cooking, read the [[http://labs.slitaz.org/projects/distro/wiki/Pkgscooklist|packages cooklist]], pick one and test. You can submit your receipts to the Mailing List or contact a SliTaz dev, so that we can review the work and give you access to the repos. === Package Testing and Debugging === You can help SliTaz by testing packages and reporting bugs on the [[http://bugs.slitaz.org/|Bug Tracking System]]. We have some [[http://labs.slitaz.org/wiki/packages|Package Testing Guidelines]]. You can use the testing project on the Labs, the forum or the mailing list to report any missing dependencies, unexpected package behavior, or wrong configurations, etc. \\ ===== Writers & Translators ===== Take a look at the [[en: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. There's many areas in which you can help: * **Are you experienced with SliTaz?** 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! * **Are you a general Linux user?** 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?** 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! \\ ===== Artists & Designers ===== [[http://community.slitaz.org/image/tid/2|Wallpapers]] make a huge impact on the first impression users receive. Some reviews barely comment further on artwork than the wallpaper! \\ ===== PR & Journalism ===== //(Could we put together some blurbs or short pieces of writing for the press & community? Maybe contacts for them?)// \\ ---- \\ ^ Page Review Section ^^ |Quality| Low | |Review| Major Updates FIXME | |Priority| High | |Problems| add a [[http://forum.slitaz.org|forum post link]]| |::: | OR add a [[http://labs.slitaz.org/issues |lab issue tracker link ]]| |How to Improve| Suggest briefly, e.g.,| |::: | [[en:guides:start | Add link]]| |::: | Add new rows like this ;-) | \\ ----