Apparently, only I am not allowed to make certain decisions, citing
maintainability concerns and past history of disasters on
projects that I have maintained almost alone for 4+ years while
everyone else can do the exact same thing, for example, block
the inclusion of webengines or drop webengines citing, suprise,
maintenance and CI concerns, and for which other people will get
spammed with issues whenever private ABI goes out of sync and crashes
apps to kingdom come.
If I dare, I will have my authority to reject a change questioned on a
project that I maintained or will be told to “take a holiday”
or get shouted at publicly.
I was not aware that, project maintainers weren’t allowed to
“out-of-scope” certain changes or give a direction to the project.
It seems to be a common practice everywhere else. So common infact,
might I say, some specific projects overuse it!
I’m sorry that I am sceptical about some things, that I didn’t
drink the kool-aid of “progress”, that I wanted stability, that I
wanted to sleep in peace, and that I am suspicious of hypothetical
“paid work promises” after 7+ years of unpaid volunteer effort.
I wouldn’t have to vent if I thought any of this was fair to me.
I guess I learnt my lesson. Next time, either I’ll move away sooner or
if the instance and permissions allow, ban certain people right
away, instead of arguing for days. The constant stream of “AI slop”
leads me to use the ban hammer way more often than before anyways, so
it’s not a problem.