How to be a developer of ROS
Moderator: Moderator Team
How to be a developer of ROS
I'm new to open source and is interested in joining the development of ROS. This may be a question asked but I did a search and found alot of junks rather than answer, so I just thought that I should save the trouble and post.
Anyway, I registered in sourceforge and here, read some of the information found in this website but just can't get the answer.
I'm a C/C++ programmer. I know Java, VB.Net, PHP, ASP.Net, JSP and others which I think not really worth mentioning. Although, I don't know how Windows works to the bottom, but I'm willing to learn. Used Windows Since 97. Programs in WinAPI, WinSock and Recently, DirectX. I hope to contribute my part in the development in ROS, could someone show me the way? Thanks...
Anyway, I registered in sourceforge and here, read some of the information found in this website but just can't get the answer.
I'm a C/C++ programmer. I know Java, VB.Net, PHP, ASP.Net, JSP and others which I think not really worth mentioning. Although, I don't know how Windows works to the bottom, but I'm willing to learn. Used Windows Since 97. Programs in WinAPI, WinSock and Recently, DirectX. I hope to contribute my part in the development in ROS, could someone show me the way? Thanks...
I think this should help you to get started: http://www.reactos.org/xhtml/en/dev.html
-
- Developer
- Posts: 66
- Joined: Tue Jan 11, 2005 1:42 am
Hey there....
Well this is how I got started.
I lurked in IRC for about 2 months.
Then i started talking with people once i got a feel for our things worked in there. I read a lot of info on the site, started reading through the code.; A lot, and i still do. Even if I dont understand(which is a lot of it) I still read it.
Then i picked an area that I thought looked interesting to me to work on and was EASY. Make sure you dont get a head of yourself. I picked CMD. I read that code over and found things that were finished, never started, or not working. I worked at them and fixed them, slowly. Small things at a time.
I talked with GreatLord on IRC though seemed to be most familair with this area the code. Everyone seems to have their own little areas. I worked with him and i tried to learn from all the mistakes in my code. Slowly but surely my code was added.
After a while, I asked if I could have commit access. I was granted access and I continued to work on CMD for a while. I have no started to move into new areas and try to fix things I can.
I think my method for getting involved is pretty much the best. I strongly suggest coming into IRC and talking wth developers, reading code, and working slowly at an area you like. Dont go all out in the start, i see people come here all the time that just get burned out and fustrated. If you really want to do this then start from the begining, dont jump ahead and try to write kernel code(unless you are actually that skilled already )
If you want to work on CMD, myself and GreatLord know it inside out and both of us are always willing to help in IRC. If you think you want a little more chanllenge but still in the command line area, you can try working on some of our networking apps, in that case Ged is the guy you want to speak with. If you think you are even more skilled then that, I would suggest working on GUI apps like msconfig/regedit, in that case maybe Chris or Nathan are better to speak with. Hope that helps.
Well this is how I got started.
I lurked in IRC for about 2 months.
Then i started talking with people once i got a feel for our things worked in there. I read a lot of info on the site, started reading through the code.; A lot, and i still do. Even if I dont understand(which is a lot of it) I still read it.
Then i picked an area that I thought looked interesting to me to work on and was EASY. Make sure you dont get a head of yourself. I picked CMD. I read that code over and found things that were finished, never started, or not working. I worked at them and fixed them, slowly. Small things at a time.
I talked with GreatLord on IRC though seemed to be most familair with this area the code. Everyone seems to have their own little areas. I worked with him and i tried to learn from all the mistakes in my code. Slowly but surely my code was added.
After a while, I asked if I could have commit access. I was granted access and I continued to work on CMD for a while. I have no started to move into new areas and try to fix things I can.
I think my method for getting involved is pretty much the best. I strongly suggest coming into IRC and talking wth developers, reading code, and working slowly at an area you like. Dont go all out in the start, i see people come here all the time that just get burned out and fustrated. If you really want to do this then start from the begining, dont jump ahead and try to write kernel code(unless you are actually that skilled already )
If you want to work on CMD, myself and GreatLord know it inside out and both of us are always willing to help in IRC. If you think you want a little more chanllenge but still in the command line area, you can try working on some of our networking apps, in that case Ged is the guy you want to speak with. If you think you are even more skilled then that, I would suggest working on GUI apps like msconfig/regedit, in that case maybe Chris or Nathan are better to speak with. Hope that helps.
-
- Developer
- Posts: 66
- Joined: Tue Jan 11, 2005 1:42 am
I think that CMD.exe is the easiest part of the code to work on. It is a simple commandline C program that after taking one course on C/C++ you can probably looks through and start working on to some extent.lXciD wrote:I'm pretty new to open source and big project like ReactOS. Is cmd the easiest to work with? or are there even easier one. I agree with what you say, start from the beginning and work my way up.
Something else that's needed and sounds like it is well within your reach: the Virtual Memory dialog where you can select the size and location of paging files (in Windows, Control Panel/System/Advanced/Performance and then in XP Advanced/Change). I can help you with how to get the data to display and what action to take, other than that it's basically coding a straightforward dialog using WinApi. Drop me (gvg@reactos.org) a note if you're interested.
Of course, if you decide to work on cmd.exe that's fine too.
Of course, if you decide to work on cmd.exe that's fine too.
i know this is out of thread, but thank you very much! i'm a dos enthusiast (sadly, i don't code in anything i can help ros with) and if follows that cmd is one of the most important parts of ros to me. yeah, i like freedos too, but freedos won't run notepad, eh? i really appreciate what you're doing. and then, it's worth noting that if someone has trouble with the floppy someone on the forum says "try it from cmd."BrandonTurner wrote:I picked CMD. I read that code over and found things that were finished, never started, or not working. I worked at them and fixed them, slowly.
FOSS="MY Computer"
drm="NOT My Computer" http://eff.org
drm="NOT My Computer" http://eff.org
Who is online
Users browsing this forum: No registered users and 25 guests