Hey guys, I am a 2nd year university student on winter break and I am currently learning c# by myself right now. I really learn by writing code (like the rest of us i assume) and I would love to contribute to an open source project using c#. I was really wondering where to start... I've been doing some googling and I have checked sourceforge, and the projects that are looking for help (which seems like a small list) but I really do not know where to begin. I know people say to work in what you are interested in, but I am not sure where to start looking =p. Well anyway, any help you can give me or suggest me to a c# open source project that might accept beginners to the language (but not programming) be my guest thanks!
I'd personally recommend F-spot. Best worked on under a GNU/Linux OS like (K)ubuntu. Check out the source, and have a go!
You could check out http://csharp-source.net/. It is a list open source software written in C#. There has got to be someone there willing to accept your assistance.
You can contribute to my humble attempt at creating a TextMate clone for Linux. The project is at a very early stage, and every contribution will be appreciated.
Here's the GitHub repo: TuxMate.
If you are looking for open source c# projects, check out Codeplex. There are a large number of C#/.NET projects there that you could contribute to.
Also, check out the answers to this question http://stackoverflow.com/questions/43649/how-to-get-involved-in-an-open-source-project
I recommend getting involved with something that's related to Mono. But I think I might be a little biased here, because I really like what the mono people have done, and I'm a big mono fan.
My own personal experience has been that if you want to be involved with an open source project, start with one that you find useful to you personally (or your company). So if there's a C# app, or library that you've used and found useful (or if you can think of ways for it to be more useful), contribute to it! That could be in QA, bug triaging, testing, writing unit tests, submitting patches, and/or working directly on the code (usually that takes a while to build up to though).
Just my 2 cents