Best way to get involved with coding?

[Caleb K]

I'm hoping that posting not only helps me, but helps others who haven't been apart of an open source project get started with this one - so please be nice :)

What is the best way to start getting involved with development of this project (specifically for me, the c++ coding side)? 

I've never done collaborative programing before, so I'm not 100% sure how to find my "place" and proceed in a project like this.  Also, I think I'm having some trouble understanding the development process of an open-source project like this and how it is managed.

Some questions I have:

- As mentioned on pages in the Wiki, there is a lot to be done to make the game playable.  Is there a place to see what aspects are being activity developed?  What things are more important than others? A place to mention that I'm working on one aspect so if someone else is too we don't end up doing double the work? 

- Or am I thinking about this wrong? Maybe instead of seeing the project as something that 'manages' itself (aka the project asking its contributors for something specific to be developed), should I think of it as something that is molded by many sculptors who come up as they please, add their contribution, and may or may not ever be herd from again?

- Is it possible that me trying to get involved in this project would be more harmful than helpful (Too many cooks in the kitchen type situation)?

I've downloaded the source, compiled it, and have seen the game in its current state.  I'm currently taking time to look at the source code and see what areas I might be able to help with.  Hopefully I'll find a use for my programing skill level here. I really want to see this project fully come to life and would love to know I helped! :)

[Zuu]

I would recommend joining the IRC channel: #freerct on oftc.net (Webchat)

You can there ask about what is being developed on or just tell what you are interested in and check if its known that someone else is working on the same thing.


I don't think it will be harmful if you try to get involved in the project. As you've seen there is plenty to do.

[Alberth]

Hi,

On Wednesday, February 19, 2014 5:00:36 PM UTC+1, Crof wrote:

I'm hoping that posting not only helps me, but helps others who haven't been apart of an open source project get started with this one - so please be nice :)

What is the best way to start getting involved with development of this project (specifically for me, the c++ coding side)?

Euhm, download the source, have a look, find an itch that you want to fix, and code it in a good way with the code style of the project, let the devs know by creating an issue with a patch, or through irc. Then find new itch to fix, and repeat the process :)

I've never done collaborative programing before, so I'm not 100% sure how to find my "place" and proceed in a project like this.  Also, I think I'm having some trouble understanding the development process of an open-source project like this and how it is managed.

The svn repository is the only true source of code, every change is a patch file, a proposal of changes to make wrt to that repository (to be precise, a revision of that repository). There is not much management of who codes what. It's nice if you let know what area you like to work on, in practice, it's highly unlikely that you will get in the way of someone else, even if you don't tell anyone what you are working on.
After you created a patch file, devs will do a review of your patch file, and probably tell you it needs to be changed/enhanced. You make the changes, and re-apply.
At some point, everybody is happy, the change gets added to the svn repository, change done.
 

Some questions I have:

- As mentioned on pages in the Wiki, there is a lot to be done to make the game playable.  Is there a place to see what aspects are being activity developed?  What things are more important than others? A place to mention that I'm working on one aspect so if someone else is too we don't end up doing double the work? 

Have a look at the SVN log messages and/or areas of code changes. It's not always a good prediction though. There are very few people making active changes, no real need to keep track of it.
 

- Or am I thinking about this wrong? Maybe instead of seeing the project as something that 'manages' itself (aka the project asking its contributors for something specific to be developed), should I think of it as something that is molded by many sculptors who come up as they please, add their contribution, and may or may not ever be herd from again?

Asking to develop "X" is generally not working, people have their preferred corners cq favorite itches. It's much better to let people do what they like doing.
The many sculptors idea comes close :)

- Is it possible that me trying to get involved in this project would be more harmful than helpful (Too many cooks in the kitchen type situation)?

Nah. There is still room for cooks. Most cooks never finish their first meal :(

 

I've downloaded the source, compiled it, and have seen the game in its current state.  I'm currently taking time to look at the source code and see what areas I might be able to help with.  Hopefully I'll find a use for my programing skill level here. I really want to see this project fully come to life and would love to know I helped! :)

Nice. Please find an itch you want to fix, and try to code it. Visit IRC to discuss stuff, and get feedback.