Erika Fae Ottsune @Erika@awoo.space

hile in this case, yes Hiveway did decide to use github, this is still a good idea. There are lots of other VCS and lots of other platforms and pretending that git metadata is a good enough show of credit is ABSURD.

We need to make it so that everyone that works on these projects gets the credit they deserve, even in snapshots, even when it is eventually hosted on other VCS.

Seriously pondering making an issue on Mastodon & Glitchsoc that is as follows:

* Create a Contributors file

create a file which contains the name, optionally email/handle of every single person who has contributed code to this project. This will help keep contributors having credit even if the project is hosted on other platforms than github or using different VCS systems than git. It is a silly assumption to assume that everyone is going to use the same VCS platform and hosting.

@Elizafox both kari and reszera are sometimes bee-wah hybrids

With it leaning either way tbh. It’s surprisingly cute

@Elizafox @bhtooefr

Since this is mastodon what about GNU Octave

@kaniini@mastodon.dereferenced.org And i guess you could blame the reporters for not titling it right, or blame the dev responsible for not renaming it in a way that clearly communicates whats going on. or any number of this pointing fingers...

but it makes me wish that they were just using... something else that made it clearer and easier to report them.

@kaniini@mastodon.dereferenced.org sure, I use it for a lot of my personal projects where i its just me and i don't expect hundreds of issues.

I think that using it starts to really fall apart when the report load starts to increase, and it becomes hard to search if people haven't directly written a title in a well defined way.

n general i see so many projects where it just is so not enough for the load that are still using it.

@floatoverblow maybe many devs outside of this, don't care but they seem to very often if not always have this boilerplate text of "you must search for this issue and ensure its not duplicate" and stuff.

its just, *shrug*

its very high spoons

Maybe github issues was literally the worst thing to happen to open source development.

@floatoverblow see: mastodon.

granted this is mostly because they use github issues.

i agree here, and back when I was running projects we /did/ actually use mantis as our bug tracker.

i say "well me" in the CW, but i know its far far more than just me.

the number of people i've ran into who just have basically spoken and said they've outright not reported bugs because of this is actually extremely high.

heck. some of my best bug reports came from /IRC/ and people complaining about my software's issues. I literally copied the log into our bug tracker and used it to actually figure stuff out.

my recommendation would to be, for projects to assign someone to do bug triage, yes, its very boring work, but expecting the person reporting the bug to do it, only results in poorer quality original reports that result in someone who could give better reports not bothering or bugs to not be reported at all

imo both of those options are worse than having one of your volunteers to sit down and just, sift through the new reports every night and close the dups

Bug trackers, especially those with more than a few bugs... are extremely overwealming.

When you expect people to not only report bugs, but ALSO do all the bug triage themselves, it literally becomes so overwealming that even trying to report a bug is not worth the effort.

Yes i understand that its hard for devs to wade through many duplicates, but it is often much harder for non-technical, burned out, and disabled people to do that whole process.

@rey @Erin @mxsparks

I see them on awoo, yeah. Same mute list here though as on vulpine.club

@Erin @rey @mxsparks

Hi on our vulpine.club account we are also not getting Erin’s statuses so I can attest to this being the case even after a refollow

@nightpool@cybre.space @SystemDemon@vulpine.club that’s not the only accessibility need???