photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

247
active users

#bugreports

0 posts0 participants0 posts today

(1/2) It's very good to report #bugs in #FOSS projects. Services like #github, #gitlab, #codeberg and so forth makes it easy to do so without creating a new account for each report.

My recommendations:

- be polite - people are spending their spare time to help you

- explain it thorough: exact steps to reproduce, difference between actual result and expected result, mention exact version numbers, surrounding environments with their versions, background stories (maybe in an extra section at the end), ...

Fun fact: many(!) of my #bugreports get aborted during that phase because while explaining it properly, I did find out where my mistake was. Maybe improve the documentation afterwards.

...

#kdeneon #bugreports #kdeplasma6

Bug Reports nach Suche mit Stichwort "KDE Neon".

bugs.kde.org/buglist.cgi?quick

Sieht so aus, als wenn ich mindestens noch einen Monat warte. Und dann nochmal nachschauen.
Aktuell liest sich das wie "dein Laptop ist tot nach dem Upgrade" 😬😳
Aber ich bin neugierig. Vllt zieh ich mir ne USB Live Version für den Stick, nur um mal n Blick reinwerfen zu können, ohne es zu installieren.
Mal schauen.

bugs.kde.orgBug List
Continued thread

To clarify a bit, the reason I don't argue with #stalebot more than once is simple: Filing a good bug report is hard work. (I'm not referring to feature requests, although those can be hard work too.)

A project that uses #stalebot invariably accumulates tons of valid but closed bugs. A few of them will get accidentally fixed, but most remain real and get lost. (A closed bug looks fixed, so users tend to open a new one.) This feeds the "need" for stalebot because "omg too many bugs!" even though they are just noise generated by stalebot to begin with.

Back to #esphome: Why should I spend at least 30 mins searching their junk pile, plus at least an hour of gathering logs, experimenting, etc?

The humans involved will never look at it, and eventually their robotic receptionist will tell me to go away. I refuse to put more effort into this than they do.

If you want to report bugs or make suggestions about Mastodon or the rest of the Fediverse, the best place to do it is on whatever platform the developers use for source code publication and bug tracking.

Developers spend lots of time on these platforms, and they're way more likely to respond there.

For example, Mastodon is developed on Github at github.com/mastodon/mastodon, so this is the best place to report Mastodon bugs.

Places like Github can be a bit intimidating because they are designed for programmers. However, you only need to use the "issues" section for bugs/suggestions/etc, and that's pretty much just a normal forum.

One golden rule: search for bugs in issues BEFORE you report them. If someone's already reported a bug, give their report post a thumbs up so the developers know that more people want it fixed.

If you aren't comfortable doing any of this, let me know and I'll try to help.

Your self-hosted, globally interconnected microblogging community - mastodon/mastodon
GitHubmastodon/mastodonYour self-hosted, globally interconnected microblogging community - mastodon/mastodon