How to contribute to the OSDL project ?

Ponctual contribution

If one is the author of new and original content of any kind, or if one would like to join our effort, here are some of the numerous ways to contribute to OSDL:

• We consider that using OSDL (as a tool) for your project (a multimedia application or a game, for example), whatever it may be, is some kind of contribution, and we will do our best to bring you support and advices so that you achieve what you intended: no doubt it will trigger new needs, and discussing them should be useful for both sides
• one could submit new modules, ports, patches, extensions, bug corrections and so on for the OSDL's family (OSDL, Ceylan, and so on)
• there are many things that can be done for the website, the documentation, the translation effort, and so on, so non technical persons should not worry. We can, too, help you learning whatever technical knowledge we already know, in order you to contribute, even if you are rather unsure about your capacities: there is no overwhelming complicated stuff, in what we do, that could not be explained in a few pages. If you do not know C++, we however encourage you to start learning this language as soon as possible if you think it will be relevant for what you want to do (we can advise you): it is not really a short term process indeed !
  [see our technical resources section].
• we welcome any kind of artistic content (pictures, models, musics, artwork, rules, scenarios and so on), which should better be as well submitted to WorldForge or other copyleft-like content websites to ensure a maximal distribution [see our resource section]. Your artwork may therefore make its way in our own content repository [submit].
• you can also send a mail to us in order we help you determining what you could do. In that case, please do your best to explain what you have already done before knowing OSDL, what you are able to do, and what you would like to do. We are sure of two points:
  1. you should not be scared nor shy, cause we are all nice people, and everybody is able to find something he can do in the OSDL project
  2. we can find something which interests both of us !
• last but not least, you are kindly invited to join our little game creation club. This club is intended to gather some people interested in game creation (not only technical game development), and deals with all kinds of games. The club is open to everyone, even to remote members (purely on the Internet), as it is located in Paris, France.
  [all details about the club, mainly in French only for the moment]

What about becoming a member of OSDL project ?

Why would I become an OSDL's member ?

If one wishes to contribute regularly to OSDL, it will soon be necessary to be identified as an OSDL member in order to be given relevant permissions on the project's system (access with write permission for SVN, website, mailing list, trackers or other tools).

How can I become an OSDL's member ?

You have to subscribe to OSDL's general mailing list, and to make yourself know of others members by contributing a bit, your own way, to the project (a kind of short probation period !).

Then, send us a request of membership or ask us directly, and you will receive an answer from us within a few days (keep in mind we form an open community around OSDL, based on good will, so do not worry too much !). You should then register yourself as a SourceForge user (of course it is free), and we will grant you the permissions you need.

This description might seem probably excessively formal, but be confident in the fact that we are running a small, simple and nice project serenely and for fun. Besides, the OSDL project and the OSDL-club are somewhat intricated and overlap themselves, so whatever are your goals in the field of game creation, you should find something of interest either in the project or in the club, if not in both.

In a few words, every contribution is welcome in OSDL, so please do not hesitate and tell us about what you plan to do as soon as possible.

Please react !

If you have information more detailed or more recent than those presented in this document, if you noticed errors, neglects or points insufficiently discussed, drop us a line!