This forum is exclusively for existing and potential contributors to introduce themselves, give a bit of background, note interests, related skills, and so on. Please use the other forums for any other topics.
If you're interested in becoming a contributor for Terasology, you're in the right place! While anybody can fork and tinker with the project (it is open source after all!) we appreciate those who are willing to contribute to the core project. To join up please post a thread here with your name (real name or nickname, as long as it uniquely identifies you in the thread title), copy pasting the template below to your thread, and completing the few steps if able/willing/interested.
Over time the thread can be your home away from home, feel free to update it with your experiences, focus areas for the project, what you've gotten done, etc
Suggested steps to "sign up":
If you're interested in becoming a contributor for Terasology, you're in the right place! While anybody can fork and tinker with the project (it is open source after all!) we appreciate those who are willing to contribute to the core project. To join up please post a thread here with your name (real name or nickname, as long as it uniquely identifies you in the thread title), copy pasting the template below to your thread, and completing the few steps if able/willing/interested.
Over time the thread can be your home away from home, feel free to update it with your experiences, focus areas for the project, what you've gotten done, etc
Suggested steps to "sign up":
- Sign up for the forum - top right corner. Yep, need to do that first of all!
- Note: Emails from the forum can get marked as junk mail, especially seen frequently with @gmail addresses. If you use a local mail client don't forget to check your online junk folder.
- Follow us on Twitter, and Like us on Facebook and Circle (I guess?) us on Google+ (if you're into that kind of thing). We also have a subreddit
- Follow the Dev Setup steps on our GitHub Wiki to get set up locally to do development work. You might want to do this last and feel free to do it in pieces, it might look like a bit much if you don't already have a "typical" development setup on your machine.
- Note: This is optional if you're not intending to submit code. But even if you don't code, it might be very handy to have a local setup anyway, so you can easily pick and choose what branch to test. Artwork and such also goes this route, it isn't just code. Even if you're wanting to do pure design it helps to have somewhere to see the relevant bits of the game that relates.
- Consider "Following" other contributors and/or "Watching" their Terasology forks on GitHub
Code:
[list]
[*] [b]Name:[/b] _Your name here (real and/or nickname, suggested: "[First] '[Nick]' [Last]", example "Rasmus 'Cervator' Praestholm")_
[*] [b]Social:[/b] _Your GitHub, IRC, etc if other than your forum nick. Also Twitter, FB, G+ etc in case you'd like to post them. If posted we might try to tag you when posting relevant stuff_
[*] [b]From:[/b] _Briefly describe where you're from - country is fine_
[*] [b]Skills / Tools:[/b] _What have you worked with? Programming languages, artsy stuff, development areas / tech, etc_
[*] [b]Found via:[/b] _How'd you find Terasology?_
[*] [b]Interests:[/b] _What are your interests that relate to Terasology/ developing games / similar; and are you interested in working on a particular part of Terasology?_
[*] [b]Extra:[/b] _Any additional information you'd like to share_
[/list]