Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Link to Original Source
What I would like to ask the
For the contributors among you:
Assuming that you know how to program, do you find any further impediments contributing patches to a FLOSS community? does the source code organization? helpfulness of current contributors/committer? documentation? or any other factors come into play? Do you find your self sometimes saying, I want to help, but in practice, find that it is impossible to do so? Have you ever showed up to code sprint, only to do nothing, or work on trivial documentation? I would very much appreciate your point of view on the matter to understand what might be wrong, and what would be the solution to making FLOSS development more inclusive?
For the committers among you:
Let me know if this sounds familiar: You find your self overwhelmed with all the requests for assistance (users and developers alike), not to mention the time spent modifying the code contributed by someone, which you could have spent much less time rewriting from scratch than fixing.
Are these problems all too common? What is your experience and solution for making the life of a committer less hectic? and if this problem is all too common, do you think there is a chance of making the development process more inclusive? In addition, what would you say to the complaints of the contributors about: code organization, documentation, helpfulness, and any other factors that might have prevented them from contributing patches. Are these legitimate complaints? Can something be done about it? Or are committers simply too busy?
Please make clear when responding, whether you bring the experience of a committer, or a contributor."