The other day at work one of our interns wrote the most beautiful code ever. She concicely solved a resoruce-contention issue that was causing a massive performance bottleneck. Of course, now the code does random things because it is no longer thread-safe. Millions of dollars in lost business, one fired senior dev that signed off on the change, a heart attack, a liability suit, and a few hundred man-hours of emergency fixes later, the code is no longer elegant, but produces the desired result.
I'm not so foolish as to think that all OSS projects care about elegance before functionality, but you would have to be pretty braindead to insist that elegance is more important than actually performing the task correctly. You also have to have a pretty low self-worth to think that producing software only for people that can produce software is a good idea. Have some pride in your work and realize that you can affect a positive change in the lives of others--you can make their lives easier and more fulfilling. If you only write software for the people that could do it themselves, you're not really adding any value and your project is actually worthless. Your design is bad and you should feel bad.