Helping out and triaging

Following up on my offer to help triage @jberkel -

I think I’d need project permissions, yep (dunno much about matrix permissions, some stuff at https://github.com/isaacs/github/issues/311 and https://help.github.com/articles/repository-permission-levels-for-an-organization/). I’m a developer without Android or Java skills so I can ask the right questions and maybe take a glance at a log here or there but don’t expect to contribute code anytime soon.

I’d like to see more labels and close more issues. It’s best if users report bugs against later versions than the 2015 one in the Play store, and if they can’t provide a log, I’m inclined to close after a period of time… for example https://github.com/jberkel/sms-backup-plus/issues/380

Also, we could add a .github/ISSUE_TEMPLATE and add a code helpers badge https://www.codetriage.com/ maybe?

Anyhow, no pressure - I can’t promise I’d be very active - possibly only spending an hour or two a month, especially after or while checking my backups 😆

[kurahaupo]

As I indicated in #985, I’m also helping out where I can. Lately I’ve been adding new labels where there’s commonality between issues; let me know if this is helpful. (I figure the text of a label can be changed, so they’re merely my own suggestions.)

I’ve also added a few technical feature requests that should help fulfil various user functionality requests.

[jberkel]

I think SMS will still be around for a while, there are still many markets with low smartphone usage/bad internet. it’d be nice if Android offered a common storage protocol for all the different messaging solutions, then SMS Backup+ could just hook into that.

re: restoring, this should probably be addressed seriously in a future release. I think there’s definitely a way to make it faster and more reliable (even if it fails with a temp error it could pick up where it stopped on the next run)

anyway, thanks for your help, it allows me to focus more on the development part 👍