This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
musings:tech:software:fossdevs [2022/09/18 21:07] claire created |
musings:tech:software:fossdevs [2022/09/21 16:10] claire ↷ Links adapted because of a move operation |
||
---|---|---|---|
Line 4: | Line 4: | ||
This article was originally published on February 6, 2014. | This article was originally published on February 6, 2014. | ||
</adm> | </adm> | ||
+ | |||
+ | {{section>wiki:software:win32:firefox:start#caution&noheader}} | ||
Quite a few years ago now, a large open-source project called Pidgin fell prey to one of the bigger pitfalls of OSS – developer-user relations. With commercial software development, a company has resources available to do things like usability testing, analysis of interface design, and most importantly – interact with customers through company representatives whose primary role is to address customer concerns and issues. Software developers are famously stubborn and, for lack of a better word, assholes about their work. Customer liaisons protect users from the rough-around-edges aspects of the developers’ personalities and tendencies, and the end result is that the customers are happy, the software satisfies the customers’ needs, and the developers don’t end up in really sticky situations. | Quite a few years ago now, a large open-source project called Pidgin fell prey to one of the bigger pitfalls of OSS – developer-user relations. With commercial software development, a company has resources available to do things like usability testing, analysis of interface design, and most importantly – interact with customers through company representatives whose primary role is to address customer concerns and issues. Software developers are famously stubborn and, for lack of a better word, assholes about their work. Customer liaisons protect users from the rough-around-edges aspects of the developers’ personalities and tendencies, and the end result is that the customers are happy, the software satisfies the customers’ needs, and the developers don’t end up in really sticky situations. |