mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #910] Encourage Bountysource? #714
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#714
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jcrben on GitHub (Jul 14, 2018).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/910
I'm thinking we could encourage Bountysource - posted a $10 bounty for https://github.com/jberkel/sms-backup-plus/issues/647
Sustainability of open-source software is a long-term, known problem - the incentives are skewed as the people who put in the work aren't usually rewarded.
I'm noticing that people are struggling with bugs, but these are often difficult to reproduce and the reporters aren't usually up for debugging. If they got together and pooled some money, maybe these bugs could be fixed? Hard to say because they could be device-specific, but perhaps we could prominently encourage people to post Bountysource bounties for their bugs.
This project isn't ideal in some respects for Bountysource because it's got this reproducibility issue - without the specific device, it might be hard to fix the problem.
@kurahaupo commented on GitHub (Dec 27, 2019):
Sounds like a good idea in principle.
An alternative would simply be to pledge to buy a donation/upgrade through Google Play.
The reproducibility is further hampered by:
What happens when a paid bugfix has to be rolled back because it negatively affects more users than it fixes?