Just found the rudest possible way to interact with an open source project:
1. open an issue
2. put only a link to a commit in a fork hosted somewhere else in the issue description
3. refuse to elaborate
Don't do this. Ever.
Just found the rudest possible way to interact with an open source project:
1. open an issue
2. put only a link to a commit in a fork hosted somewhere else in the issue description
3. refuse to elaborate
Don't do this. Ever.
James Henstridge
in reply to Emmanuele Bassi • • •Zeeshan Ali Khan 🇺🇦
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to Zeeshan Ali Khan 🇺🇦 • • •@zeenix no, that's just another level of rudeness; it means you didn't even care about reading the contribution guide, or following the rules. What do you expect me to do? Download the commit and apply it myself?
At least people opening a merge request and then abandoning it have *tried* to follow the proper process, and then gave up; people can pick up their work. A random commit on a random downstream fork on a different forge is just lazy and rude as fuck.
Tim-Philipp Müller
in reply to Emmanuele Bassi • • •tbf, I think this is missing some context, namely that there's an infrastructure restriction on fdo where users can't fork repos by default (needed to submit MRs), but need to request special access first.
Are there docs on the cairo website or in the project repo that document the rules and point people in the right direction, or are they supposed to just find the right fdo docs somehow?
Tim-Philipp Müller
in reply to Tim-Philipp Müller • • •Emmanuele Bassi
in reply to Tim-Philipp Müller • • •Tim-Philipp Müller
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to Tim-Philipp Müller • • •@tp_muller AFAIK, the freedesktop gitlab has a banner when you open an account that points you to the wiki with all the instructions for people who want to contribute.
It still does not excuse opening an issue with zero description and just a link.