Welcome, potential contributors! This is a little guide to get you up to speed on how to contribute to Lips of Suna
- This is a loosely organized project developed by volunteers.
- You can work on anything that interests you and is relevant to the goals of the project.
- Get in contact with us! Join the chatroom or post in the forums.
- Check out any interesting articles in the wiki for ideas and instructions.
A good way to get started is to join the chatroom and introducing yourself there. Don't worry if no one replies immediately. We're busy people so stick around until someone does. Typing someone's name in full will give them an alert, don't be afraid to do so.
Testing the game is a good idea. Download links are in the right hand sidebar of this site. The game is still far perfect, but that’s why you’re here. If you have problems running it, contact us in the chatroom. We usually resolve problems very quickly.
Read articles in this wiki. We keep all the plans for the game here. The design documents, as well as guides for artists and programmers, are all here. If you want to learn how to make graphics, taking a look at the "creating graphics" section should get you started quickly, for example.
Currently we need people to design creatures, items and areas, make concept art of them, and finally model them in 3D and implement them in game. Of course, you don’t need to do all of this yourself. You can stick to what you’re comfortable with doing and let others continue from there.
Any of these works:
- Post the files to the project forums.
- Email the files to amuzen at users.sourceforge.net
- Link to the files in the chatroom.
You should also mention the ''name of the author'' and the ''license'' under which the files are so that we can give appropriate attribution.
Practices and tips
Rule of thumb: be nice to everyone and do not take things too seriously.
Developers and contributors are free to work according to their own schedules. Often, the schedule is affected by real life affairs that take priority, so it is not practical to set any hard rules on it. Since the schedule may vary wildly, it may be useful to occasionally update others about your progress, or lack of it, so that people know how closely you are still involved.
Generally, no one will be pushing you to work on any specific task or forcing you to finish your task. The reason is that everyone is a volunteer and has different preferences and circumstances. Because of this, you often need to take the initiative yourself if you need help or have some other need. By default, you have the freedoms and responsibilities related to working on your own tasks on your own, but, by asking, you will get everything from tips on what to do next to someone whipping you into submission, if that is what helps you get productive.
Since the team is very loosely bound, good communication is appreciated and recommended. Occasional progress reports, discussing future tasks, brainstorming together, presenting new ideas and requesting help are some examples of what can be communicated. Try to keep the tone positive and constructive, particularly when offering criticism, so that it is easy for everyone to stay motivated and enjoy development.