What Aspects of Open Source Projects Do You Avoid?

paulproteus writes "I'm a Debian developer and a part-time contributor to a few smaller projects. I do a lot of free software-y and open source-y things. Sometimes, though, I don't do them. I figure some other Slashdotters might have similar hang-ups — we contribute to a project, but there are parts that we really dread thinking about. So I wrote a post about having these hang-ups, and I made a place on the web to share how others can help your project. What are the parts that, in your projects, you would be relieved if someone else looked at for you?"

Comments

Re:Ego

[digitig]

You need to remove or conceal the features that are rarely used.

Goodness, where have you been? If you conceal features then you get pestered with tech support calls and requests to implement stuff that's already there! What you should do is dump everything on the UI all the time in a ribbon across the top (remembering to license it from MS). The user sucks bigtime, but users can't complain about not being able to find anything because it's all there in plain view, so they know they'll be made to feel stupid if they query your design.