← Back to context

Comment by chii

9 hours ago

> i've heard it as a dismissal countless times.

a project owner have the right to be dismissive about anything regarding their own project. This is why "just fork it" is both dismissive, but also power.

If you are simply asking a project owner to do somethings you wanted (often for free, i might add), then why shouldn't they be dismissive?

If you have an idea for said project that the owner is dismissive about, then you fork it - prove that the idea is good.

i disagree with that stance. an open source project is made up of contributions by dozens, maybe thousands of people, and they almost always only contributed to that one specific repository under that one specific person's control due to game theoretical processes that are mostly random, such as first-mover advantage, schelling points, etc. the collective effort of those people usually far outweighs what the controlling person usually contributed to ostensibly earn this sort of privilege. if talking about a FOSS repository, that person cannot be correctly described as "the owner" of that work, as the work is owned by the public, i.e. anyone who is provided access to the code. the person you are describing is merely the current maintainer of the project and the fact that most of the work they are maintaining is not theirs, but comes from the public, and is meant for the public, immediately puts a burden of responsibility on them of acting in a way that is much better than "a project owner have the right to be dismissive about anything regarding their own project" - a mode of operation which, if you pull in all the considerations i presented here, sounds childish. a much better way is to talk about this like you would about an old watch: you are merely maintaining it for future generations. that puts you in a more humble and less combative mindset.