Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

57%
+2 −1
Q&A Is it wrong to demand features in open-source projects?

"Demanding features" falls under an umbrella called "design". Design work doesn't show up directly in the commits (unless you maintain a design doc) but it is work nonetheless. Suggesting features ...

posted 1y ago by matthewsnyder‭  ·  edited 1y ago by matthewsnyder‭

Answer
#2: Post edited by user avatar matthewsnyder‭ · 2023-08-21T16:08:45Z (over 1 year ago)
  • "Demanding features" falls under an umbrella called "design". Design work doesn't show up directly in the commits (unless you maintain a design doc) but it is work nonetheless. Suggesting features is volunteer design work.
  • In principle, the maintainer should welcome such work just as they would welcome code contributions, but there are many reasons why they might not. Code contributions aren't always welcomed either, quality matters to some. Moreover, it is silly to spend a bunch of time implementing a feature when the maintainer will ignore or reject your PR - it makes sense to discuss the planned addition first.
  • Some developers just want to "put their code out there", on public display as it were, without much concern for who uses it. It is evident that for these it would be silly to demand features.
  • Other developers are motivated in some part by users. They want people to use their software a lot, from which they may derive a personal feeling of accomplishment, professional fame, future income material, volunteer beta testers, volunteer collaborators or something else. This makes the exchange transactional even though no actual money is changing hands. Thus in exchange for *using* the software the user does get to demand things (small though they may be), because usage has a cost, and the developer derives a benefit from it. Features requests are a great way to handle this exchange - they help not only the user, but the developer, by making the program more appealing to users and growing the userbase.
  • Unfortunately some developers do not see it this way and assume that since they are giving something away for "free", the user has no right to complain or demand anything. Sometimes their programs become popular in spite of their attitude and they are able to tyrannize the users with abandon. Often, they wonder why nobody wants to use it and become frustrated. Some bemoan the lack of contributors, but of course contributors often come from happy users. In any case, the negative feedback loop is quite wide and because of this such developers rarely seem to think, "Maybe I would have more users if I was nicer to them?". They instead seem to prefer writing blogs about how open source is unpaid labor and sucks.
  • I think logically, there is nothing inappropriate about suggesting features in a reasonably polite tone. The exchange from developer to user is obviously not so one-sided as some claim. However, many developers have different opinions and in practice you will always have to see if the person is open to suggestions or not. And if the latter, though you are right to suggest features, the realities of the matter will preclude exercising that right successfully.
  • "Demanding features" falls under an umbrella called "design". Design work doesn't show up directly in the commits (unless you maintain a design doc) but it is work nonetheless. Suggesting features is volunteer design work.
  • In principle, the maintainer should welcome such work just as they would welcome code contributions, but there are many reasons why they might not. Code contributions aren't always welcomed either, quality matters to some. FOSS devs can also be quite creative with how they understand "quality". It is silly to spend a bunch of time implementing a feature when the maintainer is just going to ignore or reject your PR - it makes sense to discuss the planned addition first.
  • Some developers just want to "put their code out there", on public display as it were, without much concern for who uses it. FOSS is more of a self-expression, similar to art, for these. It is evident that it would be silly to demand features from them.
  • Other developers are motivated in some part by users. They want people to use their software a lot, from which they may derive a personal feeling of accomplishment, professional fame, future income material, volunteer beta testers, volunteer collaborators or something else. This makes the exchange transactional even though no actual money is changing hands. Thus in exchange for *using* the software the user does get to demand things (small though they may be), because usage has a cost, and the developer derives a benefit from it. Feature requests are a great way to handle this exchange - they help not only the user, but the developer, by making the program more appealing to users and growing the userbase.
  • Unfortunately some developers do not see it this way and assume that since they are giving something away for "free", the user has no right to complain or demand anything. Sometimes their programs become popular in spite of their attitude and they are able to tyrannize the users with abandon. Often, they wonder why nobody wants to use it and become frustrated. Some bemoan the lack of contributors, but of course contributors often come from happy users. In any case, the negative feedback loop is quite wide and because of this such developers rarely seem to think, "Maybe I would have more users if I was nicer to them?". They instead seem to prefer writing blogs about how open source is unpaid labor and sucks.
  • I think logically, there is nothing inappropriate about suggesting features in a reasonably polite tone. The exchange from developer to user is obviously not so one-sided as some claim. However, many developers have different opinions and in practice you will always have to see if the person is open to suggestions or not. And if the latter, though you are right to suggest features, the realities of the matter will preclude exercising that right successfully.
#1: Initial revision by user avatar matthewsnyder‭ · 2023-08-19T07:53:16Z (over 1 year ago)
"Demanding features" falls under an umbrella called "design". Design work doesn't show up directly in the commits (unless you maintain a design doc) but it is work nonetheless. Suggesting features is volunteer design work. 

In principle, the maintainer should welcome such work just as they would welcome code contributions, but there are many reasons why they might not. Code contributions aren't always welcomed either, quality matters to some. Moreover, it is silly to spend a bunch of time implementing a feature when the maintainer will ignore or reject your PR - it makes sense to discuss the planned addition first.

Some developers just want to "put their code out there", on public display as it were, without much concern for who uses it. It is evident that for these it would be silly to demand features.

Other developers are motivated in some part by users. They want people to use their software a lot, from which they may derive a personal feeling of accomplishment, professional fame, future income material, volunteer beta testers, volunteer collaborators or something else. This makes the exchange transactional even though no actual money is changing hands. Thus in exchange for *using* the software the user does get to demand things (small though they may be), because usage has a cost, and the developer derives a benefit from it. Features requests are a great way to handle this exchange - they help not only the user, but the developer, by making the program more appealing to users and growing the userbase.

Unfortunately some developers do not see it this way and assume that since they are giving something away for "free", the user has no right to complain or demand anything. Sometimes their programs become popular in spite of their attitude and they are able to tyrannize the users with abandon. Often, they wonder why nobody wants to use it and become frustrated. Some bemoan the lack of contributors, but of course contributors often come from happy users. In any case, the negative feedback loop is quite wide and because of this such developers rarely seem to think, "Maybe I would have more users if I was nicer to them?". They instead seem to prefer writing blogs about how open source is unpaid labor and sucks.

I think logically, there is nothing inappropriate about suggesting features in a reasonably polite tone. The exchange from developer to user is obviously not so one-sided as some claim. However, many developers have different opinions and in practice you will always have to see if the person is open to suggestions or not. And if the latter, though you are right to suggest features, the realities of the matter will preclude exercising that right successfully.