Shared from Reddit. DIscussion is on-going there.
tmjaea 23 points 18 hours ago
My serious advice to nextcloud after submitting a bug: Maybe teach the existing devs to behave in a respectful manner and treat other human beings with respect. If I were to work at nextcloud and would see how people reporting bugs are treated by my future colleagues, I would really have to think twice if that are the people I want to work with.
msic 0 points 14 hours ago
Respectful how? I’m not a dev, but curious to hear what you mean with actual examples.
tmjaea 3 points 6 hours ago
https://github.com/nextcloud/mail/issues/4758
lihaarp 16 points 17 hours ago
And for gods sake, reign in that stale bot!
Stale bots are bad and discourage contribution.
[–]lihaarp 1 point 3 hours ago
Don’t let stalebot carpetbomb issues, use tags. When a maintainer has looked at an issue that still needs additional info from the reporter, he sets a needsinfo tag. Automatically clear the tag when an user replies. The stale bot may only close issues that had this tag for more than x weeks. It’s not perfect but should avoid false positives.
[–]fermulator 10 points 12 hours ago
disable it - if an issue is reported there’s an issue
i had the bot try to mark my ticket as stale when there was an OPEN PR against it! really silly
only humans have the necessary context to determine if an issue should be closed or not
perhaps there could be more intelligent criteria for it, examples 1) if an issue is “/stale” (3 months?) and a human triaged and labelled as “not enough info” and the author hasn’t replied ever 2) if a human triaged as “backlog” and priority is “low” and there are less than 5 votes
etc
Developer response on stalebot
As one of the app developers that uses stalebot largely my opinion is this: if nobody bothered to do anything with an issue for a long time, it’s not an issue, it’s a minor annoyance and people can live with it.
Let me just comment on this.
i had the bot try to mark my ticket as stale when there was an OPEN PR against it! really silly
So there was a resolution and the issue wasn’t needed anymore then.
perhaps there could be more intelligent criteria for it, examples
That depends on the way it’s set up by the maintainers. For there are labels you can define to avoid stalebot closing issues.
dugite-code 9 points 11 hours ago
Anyone who has tried creating an app for Nextcloud would have quickly discover the Development documentation is quite lacking. Not to mention there is a complete lack of any easy to follow how-to tutorials to get you comfortable with development.
There are a bunch of common things needed for apps that could be easily demonstrated by a knowledgeable dev in a step-by-step manner that would fast track a majority of applications. Just look at this list, most of them are not unusual and it should be easy to just point someone somewhere to get the answer or at least the start of an answer.
[–]highedutechsup 1 point 8 minutes ago
How about encouraging old developers to keep up with the ever changing version numbers… or implement a system that works regardless of nextcloud version.