mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #1109] Archive Project If Discontinued #888
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#888
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 @ThePieMonster on GitHub (Oct 13, 2024).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1109
Originally assigned to: @jberkel, @kurahaupo on GitHub.
If this project is discontinued then a link to a replacement should be posted and then archive the project to prevent further confusion.
@kurahaupo commented on GitHub (Oct 28, 2024):
@ThePieMonster I've been bug wrangling for a while, hoping that @jberkel would return, but it's been a few years now.
I've been delegated the ability to wrangle bugs and accept patches here, but I don't have access to the Google Play publisher account, or the F-Droid publisher account, so those have stagnated.
(I'm also completely lost when it comes to fixing the automated build process. I could really do with some help with that.)
@kurahaupo commented on GitHub (Oct 28, 2024):
There's already #1104 "removal from Play Store"; I know this isn't strictly about the same thing, but I'm going to close this as a duplicate because the same action will resolve both, one way or the other.
@ThePieMonster commented on GitHub (Oct 29, 2024):
@kurahaupo I can understand the frustration with the owner being gone. As its been more than a year, I would close everything down entirely. If you want to keep working on it then starting your own repo (and G-Play app) would be the next step. Keeping this up is just causing confusion, and honestly, after a few years the chance is almost zero there will be a return. You can see on projects I have, that I archive them if I know my time is up. That lets other people take over with their own forks. If they reach out I will put a link to their fork in the main readme on my project so others know where to go from there. If you make your own repo, put a link to it in this repo first and then archive. I'm sure the community can come together and help fix what ever is broken. All the best.