Diseased Open Source Software Community - it's about ethics in Code of Conducts

All the sperginess can be explained away by him being German.
Or autistic, but that's a given. The whole sperge out can be covered in one simple sentence: "This software does not have or want a community, it's also built to cover my specific needs - if that works for you, great".

The massive essays and walls of text that say a lot but actually say nothing is kinda astounding. And all of it for.....selfhosted robot vacuums? Open source never disappoints.
 
This old post by Drew explains so much about Wayland and Wlroots in general.
Devault said:
I maintain a lot of open source projects. In order to do so, I have to effectively manage my time. Most of my projects follow this philosophy: if you want something changed, send a patch. If you are running into an annoying bug, fix it and send a patch. If you want a new feature, implement it and send a patch. It’s definitely a good idea to talk about it beforehand on the issue tracker or IRC, but don’t make the mistake of thinking this processes ends with someone else doing it for you.

So what does this mean for you, user whose problem no developer is interested in? Well, it’s time for you to step up and work on it yourself. I don’t really care if your problem is “a showstopper” or “the only thing preventing you from switching to my software”, or any of a number of other excuses you may have lined up for getting someone else to do it for you. None of the other regular contributors really care about your interpretation of what their priorities should be, either. We aren’t a business. We aren’t making a sale. We’re just making cool software that works for us and publishing it in the hopes that you’ll find it useful, too.
Devault said:
It might be hard, but hey, it’d be hard for us too. You’ll learn and be better for it. Wouldn’t it be nice to add [language you don’t know] or [library you don’t know] to your resume, anyway? If you’re concerned about the scope of your problem, how about asking about the low hanging fruit so you have easier tasks to learn with?

The cards are stacked in your favor. The only problem is your defeatist attitude. Just do it!
 
Sorry to double post, but I'm so annoyed by this guy
Nice upstream developer: If you like my software, let other people know about it! I'm welcome to accepting pull requests, package managers and contributors.
Shitty upstream wayland developer: I have a bug or feature you want? Too bad. Fix it yourself. Your pull request is outside the scope of this project, and doesn't have a use case. Make a fork.
 
Or autistic, but that's a given. The whole sperge out can be covered in one simple sentence: "This software does not have or want a community, it's also built to cover my specific needs - if that works for you, great".

The massive essays and walls of text that say a lot but actually say nothing is kinda astounding. And all of it for.....selfhosted robot vacuums? Open source never disappoints.
Are you belittling the philosophical implications of an open source Cloud API emulator and its effects on human society?
 
  • Like
Reactions: skunt
This old post by Drew explains so much about Wayland and Wlroots in general.
You have to appreciate the part that goes unstated. This issue is not a priority for any of the devs, make your own fix. Of course we won't accept your patch, this issue is not a priority for us, do you expect us to just trust your fix? The question is if he left it unstated because he's retarded, or because he knows that it is unstated.
 
Back