Help us

Version 9 (katriell, 05/09/2010 04:55 pm)

1 9 katriell
h1. Help Us
2 1 vl
3 2 sfb
This project requires a lot of work and this page will list in order of importance what you can do to help us:
4 1 vl
5 2 sfb
h2. Promoting The Project
6 1 vl
7 9 katriell
If you like this project please tell your friends, post on forums, blog about it, tweet about it, and do whatever else you can to spread the word.
8 1 vl
9 4 vl
h2. Porting Ryzom on GNU/Linux and MAC OS X
10 3 vl
11 9 katriell
Currently Ryzom is working on Windows, but we already have a native version of NeL:http://dev.ryzom.com/projects/nel/wiki for *GNU/Linux* and an X11 version of NeL for *MAC OS X*. We are looking for people who want to port Ryzom to their preferred operating system.
12 3 vl
13 6 vl
h2. Porting Tools
14 1 vl
15 9 katriell
* 3D objects were made with 3dsmax. Work is already underway to eliminate that dependency and use free software alternatives like Blender.
16 6 vl
17 6 vl
* [[Georges]], the tool used to describe all items in the world (monsters, npc, items, stats) was written for Windows with MFC. So it needs to be adapted to work on GNU/Linux using Qt.
18 6 vl
19 6 vl
* [[ObjectViewer]] will be adapted to work on GNU/Linux using Qt thanks to a trainee from the Google Summer of Code but the task is big and help is welcome.
20 6 vl
21 9 katriell
* [[WorldEditor]] is also made with MFC and only for Windows. We have a very precise vision of what we want to do to replace this tool. Using new web technology and "some tools":http://maps.bmsite.net already made by some Ryzom fans, we want to create collaborative online tools to directly edit and apply world modification into the servers. This will require lot of knowledge in Javascript and PHP.
22 6 vl
23 9 katriell
These are the next big tasks that need to be done to make Ryzom even more useful to the free software community, so if you'd like to help, please [[Contact_the_community|contact us]].
24 1 vl
25 2 sfb
h2. Source Code Packaging
26 1 vl
27 2 sfb
One of the first big changes to the Ryzom project will be to eliminate the build-specific files. Currently Ryzom uses a custom Makefile system for building on Linux and Visual Studio solutions and projects to build on Windows. The goal is to unify all of the disparate build environments under the CMake umbrella.
28 2 sfb
29 2 sfb
CMake provides a certain level of automated packaging through CPack. We would like to start harnessing CPack to generate releases so that the release cycle can be shorter and easier. In addition we are seeking Debian and Fedora package maintainers to help build and maintain Ryzom packages for the various Debian-based distributions and the RedHat-based systems.
30 2 sfb
31 2 sfb
Packagers for other distributions and distribution systems are eagerly welcomed as well. We would like to release often and to as many platforms as possible.
32 2 sfb
33 1 vl
h2. Documentation
34 1 vl
35 9 katriell
Documentation is something we readily admit is a weak point for us. If you're good at technical writing but not confident in your programming skills this could be a great way for you to contribute. We have a variety of documentation tasks including these examples:
36 2 sfb
37 2 sfb
* Convert existing "NeL":http://dev.ryzom.com/projects/nel/wiki documentation to the new site.
38 2 sfb
* Convert the "OpenNeL Handbook":http://www.opennel.org/confluence/display/~mattr/MtrNelManualNotes to this site.
39 2 sfb
* Write tutorials on basic usage.
40 2 sfb
* Create simple sample demonstrations.
41 2 sfb
* Create tutorials and videos on things such as using the tools, creating content, etc.
42 2 sfb
43 2 sfb
In addition to these examples we also very much need a developer willing to dig through obscure code and work on understanding how much of the lesser known pieces of code and functionality work and document them as well.
44 2 sfb
45 2 sfb
h2. Security Reviews and Patches
46 2 sfb
47 2 sfb
The Ryzom Project has gone through lengths in an attempt to mitigate as many of the potential security threats as possible but we know we're not perfect. We seek eager individuals to help us identify potential or actual security problems and work with us to resolve them.
48 2 sfb
49 2 sfb
h2. Bug Slaying
50 2 sfb
51 2 sfb
Every project has bugs and we are no exception. It takes a special person to catch those little flaws in code and figure out the right way to fix the problem.