@ainmosni mine are:

No-Gos:

• Operated and/or maintained by known bad actors (i.e. DHH)
• Allowing "#AI" / #AIslop in their codebase / repo / contributions /...
• A malicious "#CoC" that enables and shields abusers and harassers or the E.S. Raymond kind ("Right to be Rude")
• Financed or supported by #GAFAMs / military/intelligence contractors.
• Using #ClownFlare / #CloudFlare or other #RogueISP|s / value removing middlemen.
• Being only source-available, open-core or otherwise doing #OpenWashing or #AssholeLicensing with ie. #SSPL!
• Absurdly wasteful tech stack (i.e. only works on #Memenetes (#Kubernetes) or #WinShit (#Windows11)…
• Extremely long list of issues with no activities.
  • #StaleBot / #StarBit and other bullshit!
  • #Paywalled access to code.

Green flags:

• Operated and/or maintained by trans*, nonbinary and/or furries.
• Clearly banning AI & AIslop if not outright sabotaging /tarpitting / hacking any AI bullshit.
• #Accessibility and #FrugalComputing are part of the goals.
• Active development
  • Active issue tracker
• Regular releases

Yellow Flags (that need context):

• Low/no activity
  • archived repo
• few releases

Down with stale bot! #github #stalebot

Totally normal #Python upstream attitude:

1. Ignore a reply on a bug report for 3+ years.
2. Install a #StaleBot in the middle of the night.
3. 7 minutes after the bug is marked stale, claim that you "never heard back on this" and that "the issue was somewhere downstream", without even checking another linked issue.

https://github.com/matplotlib/matplotlib/issues/23384#issuecomment-3652630086

#Matplotlib

@grishka @Antacon @sjvn Personally I also keep issues open but will give them a specific tag like waiting for reply as a placeholder.

• I really hate the stale shit and espechally #StaleBot (like #StarBot) should be outlawed!

Yaiy, my #Signal desktop client now says: "Unlinked: Click to relink Signal Desktop to your mobile device to continue messaging."
But I can't, because my old phone still has the issue of a broken #sqlite database after a battery failure while messaging. And the ticket for that was closed via a #StaleBot, even though I bumped that ticket... https://github.com/signalapp/Signal-Android/issues/13814
Is the only way to use Signal again to install it without migration on my new phone?

#StaleBot, ale zamiast odgrażać się, że odrzuci przesłaną łatkę, to grozi, że ją włączy do kod. Wszak skoro nikt nie ma uwag, to musi być dobra, nie?!

#GitHub

#StaleBot, except instead of threatening the contributor to close the PR, it threatens the maintainers that it will merge it. Obviously, since there are no remarks, it must be good!

#GitHub

@karlpoe Everyone who uses garbage like #StaleBot, #StarBot and #Copilot should he globally banned from coding!

@pancake Relative.

• I think in that case there's rather a systemic problem of underresourced #FLOSS projects: More funding and personnel would greatly help in said effort.

The only thing #StaleBot generates are #duplicates due to new tickets being opened with the exact same problem…

• It's almost as garbage as using #discord for #documentation and #support when #MkDocs-Material on #GitHubPages would've done a better job and not create yet another #InformationBlackhole!

I don't deny the issue at hand; I just think that such a massive pile needs to be combed through better by using tags and prioritization. Even if that means one has split the backlog into half a dozen different baskets that read "feedback", "suggestion", "bug", "security", "ui/ux", "building", "l18n/i18n", "accessibility", "reproduceability", etc...

@pancake nodds in agreement I think #GitHub should ban #StaleBot & #StarBot!

If a project doesn't want to take in issues via GitHub at all that's fine, but at least they should point towards the proper channel:

• Like #Linux does!

@404mediaco #stalebot comes for open access to information! (this has to be illegal, but why would they care)

@mayank IMHO, #StaleBot|s should be banned because they provide 0 value to any #FLOSS hosting site like #GitHub.

#StalBots #Bots #issues #stale

Смерть конфигурации stale-ботов, которая автоматом закрывает тикеты! Это отвратительно.

https://nostalebots.xyz

#NoStaleBots #StaleBot

I opened a bug ticket on the Homebrew issue tracker. It is a legitimate bug, with a reproducer provided, maintainers agreed.

I managed to keep it open for six weeks by commenting every time #stalebot barged in (just posting a link to Drew Devault's article), before someone showed up to condescend and strawman me, saying I must have bad intentions towards Homebrew if I don't like stalebot.

Then the ticket was summarily closed and locked as unproductive (because I dared criticize their stale policy), and as "hard to debug" (despite being 100% reproducible with the code I provided), proving my point.

Would not recommend contributing to that project. They clearly do not value having a community.

why is #stalebot

do better, @homebrew

Ah yes, the refined way of running an OSS repo. You configure dependabot to keep you up to date, ignore it's PRs and have the stalebot close the PRs 90 days later.

Perfectly in balance, as nature intended.

This revelation brought to you by trying to compile #Ceph and failing because they pin deps from 2022 that won't compile anymore with modern versions of Python, and unsurprisingly never shipped wheels for versions of python that were not really yet mainstream at the time. (py311 was already out, but no grpcio==1.46.5 wheel for it.)

I guess I'll try bumping the dep pins locally and hoping for the best.

#stalebot #OSS

@truh @thcrt @MastodonEngineering @Gargron I think #StaleBot should not be used to closed issues!

• Rather use it to mark posts waiting for a reply from the original poster needed...

@thcrt #stalebot is an agreement by the maintainers to show up in time. If they don't, tag them by name and publically. I didn't get a choice in their artificial time limit, so the least they can do is admit out loud they are being shitty maintainers.