GNOME developers seem to have some sort of a weird “vision” for their software. If your bug report falls within their vision, good for you. When your bug report doesn’t, it’s insta WONTFIX.
The FDO icon theme fiasco occurred merely a few days ago.
People who do work for themselves and share it with other people don’t do work for other people, big shocker.
Like, seriously, if your Neighbor makes a cake and shares it with you, do you also ask them “that’s nice but can you next time make [cake i like]?”? no! you say thank you and you’re grateful someone is sharing their hard work with you!
Did you notice that I said “merge request” earlier? Your neighbours were kindly helping you to make a cake and you responded to their kindness with GTFO.
If your code isn’t up to par, or your feature isn’t relevant enough and doesn’t fit “the vision”, it’s correct to deny it. On top of diluting the project contributed code add a maintainership cost that the random contributor will probably not be footing.
Accept everything in your cake and tomorrow it’ll be an inedible mess that nobody wants. It’s ok for software to be aimed at different people.
Yes i did. Reported a Bug relating to the workspace switcher and a bugfix got merged withing 24 hours.
Did I say “some”? I think I did.
GNOME developers seem to have some sort of a weird “vision” for their software. If your bug report falls within their vision, good for you. When your bug report doesn’t, it’s insta WONTFIX.
The FDO icon theme fiasco occurred merely a few days ago.
People who do work for themselves and share it with other people don’t do work for other people, big shocker.
Like, seriously, if your Neighbor makes a cake and shares it with you, do you also ask them “that’s nice but can you next time make [cake i like]?”? no! you say thank you and you’re grateful someone is sharing their hard work with you!
Did you notice that I said “merge request” earlier? Your neighbours were kindly helping you to make a cake and you responded to their kindness with GTFO.
If your code isn’t up to par, or your feature isn’t relevant enough and doesn’t fit “the vision”, it’s correct to deny it. On top of diluting the project contributed code add a maintainership cost that the random contributor will probably not be footing.
Accept everything in your cake and tomorrow it’ll be an inedible mess that nobody wants. It’s ok for software to be aimed at different people.