@ainmosni mine are:

No-Gos:

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

[TST] test_backends_interactive.py::test_figure_leak_20490 failures with py3.11/PyQt5: AttributeError: 'QShowEvent' object has no attribute 'pos' · Issue #23384 · matplotlib/matplotlib

Bug summary Two tests of the matplotlib's test suite are failing with Python 3.11.0b3: FAILED tests/test_backends_interactive.py::test_figure_leak_20490[time_mem1-{'MPLBACKEND': 'qtagg', 'QT_API': ...

GitHub

@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?
Signal keeps crashing a second after opening · Issue #13814 · signalapp/Signal-Android

Guidelines I have searched searched open and closed issues for duplicates I am submitting a bug report for existing functionality that does not work as intended This isn't a feature request or a di...

GitHub

#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

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: