Grad Student Looking To Contribute To Open Source
An anonymous reader writes "I'm an Applied Math grad student who knows a bit of Mathematics and a bit of programming. C++ is my first programming language — I am decent at it. I wish to start contributing to a numerical library with two purposes — contribute to open source and develop my C++ skills at the same time. I looked at the Boost libraries and joined the developer list. However, I have no idea on how to start contributing. I'm not an expert in template programming, having written only toy programs to understand that concept. I've used some of the OOP constructs like inheritance,but only for very small projects. Do you have any tips on how to get started on contribution? Are there any other emerging numerical libraries to which I can contribute? Are there any other avenues where I can contribute to open source and improve programming skills?"
You did try googling for, say, 'open source c++ numerical library' right?
I ask because that yields a fair few that welcome contributions; maybe if you told us what your issues with them are then that would help us find you some alternatives.
To understand most boost modules, you definitely need a thorough understanding of templates.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
The KDE C++ math classes are "eigen": http://eigen.tuxfamily.org/index.php?title=Main_Page
This is just a library (well actually a set of inline header files)
More generally, there are programs like "maxima" (symbolic manipulation, integration, etc) and "octave" (like mathlab).
I would love to see more work go into maxima :)
1. Join a big open source project.
2. Read the bug reports
3. Start churning out fixes for bugs
4. Profit!
Just saying it like it are.
Boost (boost.org) is broad and pretty fancy. Eigen (eigen.tuxfamily.org) is narrower in scope - linear algebra - and just might be closer to your interests. To learn the details of templates, Alexandrescu's book -- Modern C++ design -- is a way of diving in deep quickly. Reading the Loki sources is also a good way of going about it ( http://en.wikipedia.org/wiki/Loki_(C++) ). Those are resources I can come up with off the top of my head. And general advice also hold: try stuff. Make a source repo for yourself (git, mercurial, darcs, whatever) and pick a small problem to solve and hack at the templates there. Use version control so you can come up with one solution and refine it and look over your own development history.
I work in air traffic control and kinematics are a big deal for us. This is the software which takes care of coordinate systems, motion and transformations. Say you have a vehicle with a particular WGS84 coordinate. Its moving at a particular speed in a particular direction relative to true north. After one hour where will it be in three dimensions relative to its original position? How much distance will it have covered? What happens if its trajectory went within two metres of the south pole? What path in 3D will it follow if it maintains a constant altitude above the datum along the way?
Ok now say it is not allowed to fly into (say) North Korea which has a particular shape. How can you project its path forwards to determine if it goes into the air space over that country?
And so on. Its bloody complicated stuff and I reckon a lot of open source software would benefit from a library which did this. Ideal for a maths guy.
http://michaelsmith.id.au
Is there a bug tracker on this project? Tracking down and fixing bugs will force you to become familiar with the codebase, and hopefully, expose you to code from which you can learn. Also, find projects that you will use personally on a regular basis--i.e. "scratch your own itch". You'll do better work if the end result is not just some code somewhere, but something that you need and make use of frequently.
You are best off asking this question on the mailing list/irc/whatever of the community you want to contribute to. They'll know what needs fixing, and nurse you through submitting a few patches to them.
Don't take this the wrong way, but you're in math, not CS. Call the CS department, find someone who's willing to team up with you on this and work together on turning the mathematical end of your contributions into good code. You'll come out of it with a better understanding of how software should go together, your CS cohort will get some insight into applied math and both of you will be better for the experience.
The easiest way to enter Open Source to write patches for existing software. Learn how to communicate with other developers, how to be flexible and adopt their coding styles and practices. Chances are this will help you learn the most, because you'll be writing smaller amounts of code and it will always be under review by someone else. Once you've shown your competency, you're usually given commit access to the project.
Boost can be a very helpful community. Submitting a new library to Boost typically follows a few steps: gauge interest, put up code/examples/documentation for informal comments, submit for review. It sounds like you've got a lot to learn in C++ so it might be a long road (Boost has a very high bar to meet), but if you've got perseverance and are eager to learn, you can make it happen.
Applied math student...knows C++...dude. Contribute to Sage.
The goal of the Sage project is to creating a viable free open source alternative to Magma, Maple, Mathematica and Matlab. It is based on Python, but has many components written in C and C++. It has good capabilities for numerical computation, but more help is needed. It's pretty easy to dive in and start fixing bugs, and your work would immediately benefit thousands of mathematicians and mathematics students.
Sign up for the sage-devel list and start with Sage!
Your intended point (while you stated it rather poorly, since it's stupid to suggest someone couldn't be a good programmer in a language simply because it's their first - I am still a "decent" BASIC programmer despite learning many languages since) is understandable and probably something that we all thought when reading the summary, but it does depend on your definition of "decent", and the poster's ability to self evaluate. Usually I take "decent" to mean "average to good". As an "Applied Math grad student" he has already demonstrated good logical ability and therefore probably has the makings of a good programmer.He didn't claim he was amazing, but presumably he can write code that works even if it's not amazingly efficient, and he clearly knows he has much to learn and is looking for avenues to improve.
Rather than simply making obvious criticisms, you could try to help. I unfortunately have very little experience with helping out in open source projects, and have no clue about Mathematics libraries so I can't offer any useful advice, but I'm certainly not just going to sit here and watch while some smug AC takes immature pot shots at a guy who is trying seriously to both better himself and help out other people in the process.
which is totally what she said
Hi,
please contribute to the Boost Linear Algebra library, uBLAS.
You or any other interested in contributing new algorithms can contact me directly on the boost ublas developpers mailing list.
I'm the new maintainer of this library and will be happy to talk about any new contributions you want to make.
This library is great and need serious love.
Which is why I said:
Your intended point is understandable and probably something that we all thought when reading the summary
Still, being decent at a language and it being your first language are not contradictory things. Thinking he's decent at the language and not knowing much about templates is of course more contradictory, but you certainly don't have to be an expert to be "decent" at something.
Anyway, my point was that guy is obviously aware he has more to learn and is humbly asking us how he can do so. It's an attitude that should be encouraged, and it's sad that the first post is someone trying to insult him, with no actual helpful advice.
which is totally what she said
Extrapolating from how #2 smells relative to #1, NUMBER TEN must smell really awful.
You're an amateur, like the thousands of others on the net, like me. This is not a programming skill problem - that comes from either practice or aptitude, not pure willing. This is a contribution problem. You're looking for a project that has many skilled users and also has a very, very basic need they have to meet but at a basic level and that they haven't already done themselves and probably won't take too long. See the problem?
You're asking entirely the wrong questions - I would suggest that instead of trying to add something to Boost or similar, that you try to do something yourself and thus work out why Boost and similar projects are quite complex, have certain standards, etc. The problem of patch submission, new features and bug-fixing is not one of people willing to write the code that fixes the problem - that part's easy, and the fun part - it's finding something interesting that fits within the scope of the project and it's the problem of getting that code into the shape that the project would be happy with too. Thus bug-identification and lots of the hard slog-work (test suites, etc.) are much more useful than anything else you can come up with. I guarantee that the first few ideas you have to contribute to a large project will be knocked back because a) they've been suggested a million times, b) they don't WANT to do it that way, c) they CAN'T do it that way for some reason or d) they just don't trust your code and would spend longer fixing it than just writing it themselves.
I would suggest that you do one of the following:
1) Write your own library, for something you know intimately. Publish it on a website, document it well, do it under a loose license. Chances are it will overlap with other projects but they are always alternatives for everything and if your library is BETTER than the others, it will be used in preference, code will be absorbed from it into other projects, or people will ask you to for more of it. Chances are that it will take you a LONG time to make it better than even the bare basic libraries you find on the net.
(I'll use an example that I'm familiar with - SDL has lots of graphics primitive libraries, but SDL_gfx is one of the best despite not being the only "big" one, despite being unofficial, despite being a one-man operation and yet is used in thousands of projects. All it does is draw circles and polygons and rotate images, for God's sake, but it works and it's simple and it's fast and it's documented so it gets followers)
I know that when I go looking for a library to solve my problems, I am happier with something tiny and in my language of preference (C instead of C++) than some huge generic library that does a million and one other things. I have been on hundreds of tiny sites and found some absolute gems where the author just knocked up the exact piece of code I was after and nothing more and then I've used it, extended it, reported bugs in it and it becomes part of my standard toolchain (as an example, I use LodePNG to save PNG images from SDL_Surfaces, not because that's the only way, or even the easiest way, but because I found it easier than trying to get libpng to do it for me - some of my projects actually use libpng for loading and LodePNG for saving PNG's!).
2) Meld into the community - hunt for bugs, be active on discussions, suggest features (after reading the FAQ's about what not to ask for, etc.), maybe even implement a few test routines to show how useful your feature-X would be. Produce test suites (horrible, horrible job that's incredibly boring but serves a useful purpose). Run valgrind, or some kind of mathematical analysis, on the code and report your fixes for anything found back to the community. The hard-slog but useful stuff that nobody really wants to do.
Everybody would love to be chosen to just insert thousands of lines of code into a big famous project - it very, very, very rarely happens. More likely is that you have a small project of your own that others find useful (because it avoids t
Octave is a Matlab clone that now works pretty well. Go make a toolbox or two for octave.
Are there any other avenues where I can contribute to open source and improve programming skills?"
The internet is drowning in code and starving from lack of decent documentation on how to use it. if you want to transform a mediocre, existing OSS project into a world-class, standing head and shoulders above everything else in its field piece of exemplary work, then take ANY numerical library and write some examples for it, write explanations on how it works, what its limitations are (hell: even comment some of the source code itself). Write user guides, API guides, put together a FAQ or a Wiki. List the mistakes and create some workarounds.It's not sexy, but it's what we need most.
The other thing that inspecting other people's work will do (apart from really honking-off some of the more protective - read; poor - software authors) is to show you, close up and in the real world, some of the constructs and techniques that are employed. For better or worse, this will give you a lot of experience in good and bad techniques and will give you a much larger palette to choose from when you decide to endow the planet with yet another piece of OSS of your won making.
politicians are like babies' nappies: they should both be changed regularly and for the same reasons
I am not a strong programmer, although I can at least code my way out of a wet paper bag, if given enough time. Similarly, math is not my strong suit.
I have a personal programming project which I will eventually end up releasing to the open-source community for several reasons;
The idea may actually already be patented, but I have a 1970's science-fiction story that contains the "prior art" if anyone wants to challenge me. I don't actually think there are any patent issues, but that doesn't necessarily mean that I'm correct, especially since I haven't done any actual research along those lines. I can say without a doubt that I don't believe the concept is currently in use in any field that I'm aware of.
I haven't released the details "into the wild" yet because I want my name attached to the end product (for portfolio reasons, I guess, or maybe I'm just proud of the idea). I'm not entirely sure how to go about protecting my interests in this matter.
It deals heavily with prime factors of extremely long numbers (so long, in fact, that I believe I will eventually require 128-bit computing for efficiency with my current algorithm ideations; it appears that it would be best to work with 120 binary bits at a time (or some multiple thereof, but quantum computing is still a good ways off from consumer-grade products, I fear). I will still need to work with strings (as opposed to pure numerical constructs) due to the immense size of the numbers involved. I initially came up with the concept while reading about a related idea in a sci-fi novella from 40 or so years ago, and I started toying with it as a... well, I guess the best thing to call it would be an informal feasibility study. After some research and some limited testing, it seems to be holding up to my initial ideations, other than length of time involved to actually perform the process. It seems the process is a bit cpu-intensive, and my initial estimates of "several hours" for completion appear to have jumped several orders of magnitude. Distributed processing should ease that quite a bit, although threads are a bit out of my scope. I do have some good ideas on how the process might be parallellized (is that even a word?).
I have a basic grasp on most of the algorithm, but I am (go ahead, laugh) primarily a VB coder, and I believe this project would be better suited to C, or perhaps python (I have heard something about sci-py?) I am not going to trumpet about my skill set, obviously, but I do believe I can eventually finish this project on my own - I've bounced the idea around in my head for several years, and only recently started actually working on the code. Unfortunately, as I said earlier in this post, I think I'm using the wrong language; and I'm not currently in the best position to be learning a new one. I also seem to have some sort of mental block for languages other than VB (even .NET is problematic, most of my coding has been VB4 and VB5) or so-called "scripting" languages.
I'm not sure how best to get someone to contact me via slashdot, but if anyone is interested in a (probably) not-for-profit endeavor, and can throw me some contact info, I would cheerfully find a means of communication to give this project a productivity boost. I would be requiring an initial non-disclosure agreement, of course, but am totally willing to share credit (and any profit that may arise) from any actual release.
This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Have a look at R, http://www.r-project.org/, which is math related.
Their developers page is at http://developer.r-project.org/
The R Project has again participated in the Google Summer of Code during 2010 http://www.r-project.org/soc10/index.html which had several projects in C++
I think R could be nice as it combines a high level approach with the lower level of C++.
They also have forum at http://groups.google.com/group/gsoc-r/topics
As a C++ developer and boost user, I advise against starting to code for it. API design and implementation are quite hard as opposed to "normal" programming, as you need to factor several other problems: building a easy-to-use generic interface, mandatory in a library, is much more difficult to code than in project that works with specific data models. Also, I had specific problems with boost::filesystem API so I can tell you getting a bug acknowledged and fixed in a particular version might be frightening at first(no, I don't want to update my boost version to get it... I want it backported). I suggest you find a piece of code that you are interested and find useful and follow this simple roadmap:
1.Install it and use it
2.Subscribe to user/devel mailing lists
3.Write missing documentation and unit tests for components
4.Offer to implement features/fix bugs that have been appearing for some time but have a low priority.
In addition to BOOST, you might want to consider looking at other projects. Some that might be a good fit, and might need developers are :
- GSL : The GNU Scientific Library is a scientific toolset for C and C++. These tools are quite modular, and you might be able to find your own module to code.
- Plotting software : Help to any of the plotting programs would be a real boon for all scientists. This could involve developing non-linear fitting algorithms, GUI, or statistical analysis. Look at SciDAVis and possibly GRACE.
- non-linear fitting : C++ Minuit, or a CERNlib project may be a good match--I'm not sure whether these are only developed internally.
good luck!
Knowing a bit about the Boost libraries, he's probably talking about template METAprogramming instead of mere template programming. The former is quite a bit larger of a bitch than the latter. You can be a quite decent C++ developer without ever having done template metaprogramming.
Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
C++ doesn't teach you anything, you study it.
From the summary it sounds like he learned C, not C++. There's a huge, grand-canyon-sized difference between the two.
C++ is a safe, expressive, modern language - like Java but without all the horrible limitations. Yes it takes a bit of study and it's not for casual programmers, but the results are worth it.
C is much lower level, unsafe language. Good for what it does but dangerous and a very bad choice for large projects.
No sig today...
Not taking the side of the parent, but from reading the summary I get the idea that the person asking *isn't* decent at C++ (at least by your definition of average-good). I base that only on the statement that they've used "some" OOP concepts in toy projects. To be decent at C++ you need to be able to understand the implications of the fact that it is statically bound. If you don't, you're not going to be able to write decent C++ code. You might be able to "make things work". A good programmer in C++ should also be able to grok most of the template code in Boost.
Having said all that, I think this person has picked a good project to work with. They can move from being a beginner in C++ and move through being decent to even being good. This is especially true because they are likely more than decent in the subject matter in the Boost library.
For advice, I recommend to keep following the development list. Check out all the changes and read them. Try to understand what they are doing. If you don't understand, it might be possible to ask specific questions to the person who wrote it (be diplomatic, though, as they may be tremendously busy). Try to fix a bug yourself. Send in a patch with the disclaimer that you are a beginner and would like feedback. There are many people who will be happy to help you.
There are some good books that explain how to do the template stuff that Boost is doing. Unfortunately it's been a donkey's age since I did any C++, so I can't remember the names of any. Perhaps someone here can help. If not, I'm sure you can post on the Boost mailing list that you want to find a book on C++ templates and are looking for suggestions.
C++ is a safe, expressive, modern language - like Java but without all the horrible limitations. Yes it takes a bit of study and it's not for casual programmers, but the results are worth it.
C is much lower level, unsafe language. Good for what it does but dangerous and a very bad choice for large projects.
It's good you've been rated funny rather than insightful. C++ is every bit as unsafe as C.
Yes, they are very different languages, as C is intended for low-level systems programming, managing individual memory locations and stuff like that, whereas C++ has modern OO concepts badly tacked on top of that in a wrong way. It combines all the problems of Java with all the problems of C, and then adds some more. The end result is quite powerful, but not something I'd ever dare to call "safe".
The answer to your question is quite easy. Take whatever your thesis is, and create high quality software tools to help you to that end. Work where you're (trying to be) an expert. If tools already exist, expand those tools in the direction of your thesis.
If you know the math, you should be able to come up with regression tests and find corner cases and invalid approximations and so forth. In other words, you should be able to find bugs, or prove that certain bugs aren't present. This is a very valuable service, and you can get familiar with the code by writing the tests that use it and understanding the ways it implements the algorithms involved.
PHEM - party like it's 1997-2003!
Most projects love off-loading working onto eager, but inexperienced, contributors. You can't go wrong with most groups by going to them with a good attitude, stating what you can do and asking what you can do to help out. If you get grief from them for that, you can safely write them off as terminal assholes because no reasonably well-balanced human being would slap down someone who approaches them like that.
I've been contributing to a project for a while where the core contributors are far better and more knowledgeable than the average contributor. The community has an elitist reputation, but what I've found from watching how others are treated is that those core contributors will treat the small time contributors very well if they contribute according to their abilities (meaning they don't flood the core contributors with trashy git commits for obviously complicated problems) and work as a team.
Part of the problem is that a lot of people don't like hierarchies and resent the hell out of them. The fact is, however, that they not only exist, but are necessary for social organization.
everything that was "unsafe" about good old C is still there.
So, um, don't use those bits...use std::vector and std::string instead.
This is where 'learning' C++ comes into play, as opposed to just hacking around and copying/pasting C source code until it works.
If you're doing it right the only problems you should have in C++ are null pointer exceptions - just like Java.
Any real safety still needs to come from the experience of the programmer
That, and having a teacher who smacked you down every time you tried to use a C-style array or didn't do RIAA.
No sig today...
I see a lot of posts from non-mathematicians here. Most are correct and useful, but not necessarily fitted to your situation. As a fellow mathematician who has dabbled in this stuff over the years, I can think of a few projects where your particular skills may be helpful:
(1) Work on the GSL. This is the highest-quality numerics library out there. I'm not aware of particular weaknesses - it's really great - but I'm sure there's something.
(2) Work on the open-source spreadsheets. These are basically OpenOffice, Gnumeric and KSpread. All three lack some numerical routines that could be useful.
(3) Work on Scipy/Numpy, R, Octave or Maxima. The numerics routines in these libraries are not always GSL-quality, particularly special functions. The built-in optimization routines tend to be basic and sometimes light on features. Even translating unit tests between packages would be a useful, enlightening and somewhat interesting project that I believe no one has ever undertaken.
(4) Work on an open-source optimization library, such as OpenOpt.
(5) Performance/accuracy comparisons of existing spreadsheets, libraries, and programs.
Perhaps you might be interested in a smaller project where the number of developers is also small, but quite open to new blood. All of the current developers would be very happy to get you started with the ooRexx project. The source code is mostly C++ and we do not use templates, mainly because we have no need of them for our requirements.
ooRexx is an interpreter for multiple platforms and has a very interesting math library. All interpreter calculations are done in floating decimal, not binary. The current library supports most typical math functions (add, subtract, divide, multiply, remainder) but it lack higher order functions such as trig functions.
If this sounds interesting to you feel free to use the contact list at http://www.oorexx.org/contact.html to email one of us and we can get you started or supply you with more information.
David Ashley
Project Leader, ooRexx Project
The end result is quite powerful, but not something I'd ever dare to call "safe".
C++ is as safe as you want to make it.
eg. Did you know that Visual C++ operator[] does range checking in all standard container classes/strings?
If you do stuff like that and ban raw pointers (ie. all pointers have to be objects and thus subject to RIAA) then most of your traditional C++ problems disappear. It just takes a bit of practice and getting over the C mentality.
In return you get multiple inheritance, timely freeing of resources, operator overloading and much more expressive power than Java.
A good portion of Java code is just copy/paste because you can't inherit implementation and try/finally blocks to get your files closed at the end of functions, not just when the garbage collector feels like it (which might be 'never'). In C++ you write code once in a library and it stays written.
No sig today...
Hello, anonymous submitter,
About I year ago I've started a small project with a friend, written in C++, that does some improvements to lossless audio compression (currently to FLAC). It calculates the autoconvolution of the audio signal to find similar parts in the audio. Especially for electronically generated music, this can be used to predict other parts in the audio, and thus reduce the entropy of the signal (i.e. compress the file better).
If you (or anybody else) are interested in further development, I would open-source the project, and may be start working on it again a bit myself. Just drop me a line, at polarspaceflo (at) googlemail (dot) com.
Did I really type RIAA instead of RAII? Oh, dear...
No sig today...
Improve Octave. Specifically, for ARM. Remember that open-source does not necessarily mean architecture independent. Practically all software is written with the perception that the compiler optimizes any poorly written C / C++ code and that the target is a PC. While this is good for x86, relying on hardware instruction rescheduling to make code more 'efficient', it's pretty awful for anything else. Having done a lot of work with ARM / NEON optimizations myself, I can tell you first-hand that gcc does not do a great job of optimizing C code at all. This is going to become increasingly important as ARM outpaces x86, so please do everyone a favour, and write the code correctly the first time. There are several books about why this is so important, e.g. this one, but you'll probably find that its easier to just dive right in. Look at the Android source code, that's always a good example. uClibc / uClibc++ are also good examples.
OK, you had me until there. If you are using multiple inheritance you have a flaw at the architectural level. There is a saying among Software Engineers: "Just because you can do it, doesn't mean you should do it." Multiple Inheritance is the poster concept for this statement.
Other than that, as a SE versed in numerous languages of all types, including C and C++, I can attest that every person saying "C" is better, or "C++" is better, or "C" is unsafe, etc. are simply people that lack a basic understanding of software engineering on some level, and completely lack an understanding of the language they are criticizing. Neither is "safe", or "better", or "implemented incorrectly", etc. (I promise you if you are one of these critics that Bjarne Stroustrop, Dennis Ritchie, and Brian Kernigan are smarter than you, and know much, much, much more than you do about language design.)
I especially love it when people cite bad code as proof of poor language design. It is like saying you can prove that English is a horrible language by referencing a Rap song. Any good language can be misused, misunderstood, and abused and said abuse is not proof that the language itself is inferior or flawed.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
Trying to implement new functionalities is not easy if you're not an experience programmer.
I recommend starting with an existing program or lib and try to fix the memory leaks. By doing that you will look at many lines of code, learn about coding standards, and still be able contribute. You'll also learn how to debug, which is the hard way to learn. And write proper code. Use valgrind.
Hint: start with libxml2. And good luck.
Next time you start your car, try to not to think of all these ECU using pure, clean and unsafe C code.............
It's actually uglier than "just trigonometry and vectors". If you're willing to use a spherical approximation to the globe then yes, but WGS84 is an ellipsoid. To get an idea of how complicated it is, check out this paper (and note the references to numerical analysis).
Good points. But we're talking about the actual programming, and then it really boils down to doing a lot of template stuff.
The ideas behind Boost are great, but I really hope that somebody, somewhere, will sooner than later invent a new generic-programming language that will allow an implementation of the Boost ideas without the major ugliness of abusing C++ templates to the max.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
Here's an example of what the ledow is talking about with point #1. Or at least a corollary of his point in action. About a decade ago, I wanted to play with XML files in C++. There were no good, small libraries to do that. There were a couple of ridiculously large, complicated libraries that would handle XML files, but you'd lose more time learning the library than you would ever put into your actual code. So I created libxml++, to scratch my own personal itch. It was, at the time, a small but useful wrapper around libxml. Very basic, and demonstrated mostly that I knew less about either C++ or XML than I thought I did.
But people used it. (They also used my CLI Yahoo Messenger client, but that became defunct after I handed it off to other developers, due to the then-rapidly changing Yahoo protocol. The single most touching e-mail I have ever received was from a user of that client.) One of them submitted some patches, and eventually in 2002 I passed off ownership of the libxml++ project to him. I don't code in C++ much anymore, so I don't use my own library, but I do check in on it every so often. There are regular commits, including one last week, and an active mailing list, with several thousand messages. It's in Debian's main package repository and a number of diverse other packages depend on it.
All of this is the result of an itch I had ten years ago. Don't let anyone tell you that this kind of thing never happens and that there are just a billion useless libraries and programs half-written out there. There are a billion of those, but if you have a need for something that nothing on the market seems to fill, the chances are good that you're not alone in that unfilled need. Fill it and make it easy for others to use it and contribute to it, and see where it ends up in 2020.
What seems pretty obvious is that the guy's question is about how to get involved in an OSS initiative, not how to find one. Cultural barriers aside, the perception from the outside is that many existing communities are closed, elitist kingdoms that are unwelcoming and intimidating to newbies. So, while providing a helpful search query may be clever, it does not address the essence of the question and serves to perpetuate the stereotype.
Most communities seem closed because the internet is vast and there are a lot of idiots and trouble makers out there who at best waste time and at worst wreak havoc with a project. Since FOSS projects don't have employment processes and hiring forms, they need mechanisms to make sure they are working with the right people for the job.
Here are some hints to help you get through the initial barrier of egotism end rudeness that many projects use to protect themselves:
1. Join the mailing lists.
2. You may if you like, send an introduction to the mailing lists, but do not say anything else until you get an idea of the culture of the community, what netiquette guidelines do they follow, who is who, and the general tone that people use to address each other. Aslo try to figure out if there is certain sorts of questions the project doesn't like to answer. It's possible they deliberately obscure certain configurations, etc. in order to guarantee consulting income. If you think this wrong, and you want to be some kind of maverick coder vigilante, call them out and publish the tricks widely. If on the other hand you want to be a dev on the project, accept that this is the real world, and these devs are doing enormous good giving this volume of code away, free to use for anybody smart enough and interested enough to figure it out and at small once of consulting fees to those who aren't so inclined. Be kind to them, don't answer questions that seem to fit into this category, don't publish the fixes anywhere, think of it as a gift and keep it in your pocket for your own consulting career.
3. How long you lurk varies greatly from project to project, but it will always be longer for dev lists than for user lists. Once you have figured out the community a bit, start showing your worth by being helpful on those questions that come in to the user list that you can answer. A community is not going to accept code contributions from someone who can't figure out the part of their project that they expect users to be able to understand. So show you understand what they are doing.. At this point, it's probably best to be friendly and helpful, but if it is one of those lists where a lot of the popular (not to be confused with profusive) posters are boastful and have a bit of a bite, it's probably safe to start showing a bit of a swagger already.
You can also use this time to start climbing into the code, get to understand the architecture of the project, the existing coding culture (is code readably formatted, is code commented well, are they cowboys or nazis? When reading about fixes or changes in the dev list, look at the code, try to understand what they are talking about, how it all hangs together.
4. Once you have demonstrated that you understand their project well, are helpful and involved. You have mirrored their preferred modes of behaviour! You already seem like one of them just waiting to be adopted! You start contributing to the dev lists when you've understood the code sufficiently to make a contribution. It doesn't have to be a particularly brilliant contribution. It could be something a 5 year old could have spotted, and you just happen to be the first one to see the incoming mail. Don't write out the full function in perfect code with every excpetion caught, all nicely commented and logging in all the right places. Don't try get commit writes to the project, just formulate a solution, implement rought it in your local copy to make sure it works and describe it on the mailing list. If you've solved the problem correc