Submitted by quidam on Fri, 02/12/2010 - 21:56
Revision of How to help from Fri, 02/12/2010 - 21:56
The revisions let you track differences between multiple versions of a post.
There are a lot of thinks you can do to help the Trisquel project, and you do not need programming skills to perform most of them:
- Improve this wiki. We need more documentation, tutorials, screencasts, and everything that could be useful to the users.
- Translate the web content. We can reach more people if you help us.
- Help other users. Join the forum, the mailing lists or the #trisquel channel at irc.freenode.org and help others in their Trisquel usage.
- Spread Trisquel. Invite others to our community, talk about free software and Trisquel in your school or job, write about your experience with it in your blog or social network!
- Seed our torrents. If you have good network connection with some spare upload bandwith, you can seed our torrents to make iso downloads work faster.
- Serve as a mirror. If your company or university have a public software mirror, or you have a high bandwith server available, you can also serve our files and be listed in our download page.
- Become a Trisquel developer. If you have programming, sysadmin or packaging skills, get in contact with us to help with development tasks.
Community driven tasks
We get a lot of requests from the users, with ideas that could improve our software. Many of them are very good ideas, but in most cases we just don't have the time to do them. But we can apply your ideas to the distro if you have the time to make them real.Some examples of requests we cannot fulfill:
- I'd like the package foobar to be in the repository.
- I want a $usage oriented version of the distro.
- I want the foo package translated to the bar language.
- I want this version of foo to be updated/backported.
If you want to spend some of your time doing such a task, please join the development mailing list, and tell us about your project. We can give you advice, and we will include your work in our project when it is finished.
Revisions
02/12/2010 - 21:56
02/15/2010 - 21:31
04/25/2010 - 16:51
06/09/2012 - 22:45
06/11/2012 - 08:25
06/13/2012 - 01:16
01/21/2013 - 01:59
09/26/2013 - 00:46
01/06/2014 - 15:49
02/28/2014 - 07:50
03/19/2014 - 11:29
04/16/2014 - 04:19
04/18/2017 - 15:23
02/17/2022 - 13:54