How to participate

From Linux-VServer

Revision as of 20:40, 21 October 2011 by Glenn (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing.

We in the open source community have learned that this rapid evolutionary process produces better software than the traditional closed model, in which only a very few programmers can see the source and everybody else must blindly use an opaque block of bits.

Whether you're an experienced Linux developer or an end user just getting started with Linux-VServer, there are many ways for you to participate in the Linux-VServer project. Join the mailing list to get help or help others, find and report bugs, review the documentation, send your wish list for new features, create and submit patches, or find other creative ways to contribute.


Improve the Wiki

As long as you edit anything on the wiki you are de facto member of the Wiki Team.

This page is built with MediaWiki. The concept of a Wiki is that anybody may add and modify content. Please see the Wiki Team page if you want to contribute to our Wiki. Refer to the Wikimedia Manual for instructions how to create and format wiki pages. Please make sure that you follow overall look and feel of the wiki.

We added a Sandbox and we would kindly ask all that wannabe hackers use that page for the very challenging task of wiki hacking (TIA:).

Help other users

There are many ways to help other Linux-VServer users. Take a look at Communicate to learn about all our communication methods.

Test new releases

You can help improve Linux-VServer by finding and reporting bugs. Like many other projects we don't maintain Bugzilla or similar but instead handle bugs on the mailing list. If you have never written a bug report, please refer to Report a Bug to learn what kinds of information make the report most useful.

The experimental releases can be found here.

Help narrow down problems

If there's a problem the developers cannot reproduce, the Debugging page shows how to proceed to help them get to that point.

Suggest new features

If you feel like a feature is missing feel free to contact the Linux-VServer community with your wishlist. Take a look at Communicate to learn about all our communication methods.

Review or write new documentation

Visit the Documentation page to contribute or read articles and manuals. If you've got instructions, solutions to common problems, neat tips and tricks, or just a good way to explain something, we'd love to hear from you.

Send patches

The most obvious way to participate in the development of Linux-VServer is to post a patch as a suggested solution to an existing bug on the mailing list.

Personal tools