Tovid Wiki
Advertisement

If you like tovid, please show your appreciation by giving something back to the community that developed it. Some of the ways you can contribute are listed below.


Participate

This is the easiest way to contribute, involving no long-term commitment, no obligation, and no responsibility for anything! Bug reports, success stories, ideas and criticisms are all welcome. Get in touch with other tovid users and developers, to brainstorm or shoot the breeze.


Hack

If you have any coding experience (or would like to start learning), you're encouraged to hack the tovid code, and share your improvements with others. Open-source software flourishes when many people study and tinker with the source code.

To work on the tovid code directly, you may become a tovid developer. Here's how:

  • Participate a little bit first. The only requirement for being a tovid developer is a demonstrated interest, so stop by the IRC channel or forum and make your interest known.
  • Get a free account on BerliOS, where the tovid project is hosted.
  • Tell wapcaplet your BerliOS username, and ask him to make you a developer.


Wikify

The tovid wiki (which you are currently reading) has lots of room for growth and improvement. Wikis are a great way to publish, exchange, and revise ideas; they're also perfect for FAQs, HOWTOs, and other community-authored documents. Feel free to start your own articles or expand upon existing ones in the wiki.


Translate

If you would like to help translate the tovid documentation into another language, first download the txt2tags sources for one of the existing translations:


Extract the tarball with a command like this:

$ tar -xzvf tovid_t2t_en.tar.gz
t2t/en/
t2t/en/manual.t2t
t2t/en/makeslides.t2t
t2t/en/install.t2t
...

Each .t2t file is written in the plain-text txt2tags format, which you can read and modify with any text editor. Translate as many or as few of them as you like (we can always combine the work of several translators) and contact wapcaplet to submit your completed work.


Package

There are so many packaging formats (.rpm, .deb, and .ebuild to name a few), the tovid project could really use a packaging specialist--someone who could be responsible for keeping the various packages in sync with the most recent source distribution of tovid. If you are such a person, we'd love to hear from you!

If you are just interested in maintaining a tovid package for your favorite distribution, see Become a packager, and add yourself to the List of packagers.

Advertisement