SufficientlySecure/document-viewer

Project seems abandoned... Move along, folks.

Closed this issue · 8 comments

Deleted user commented

See my comment at issue #318 .

This project seems to be abandoned. No updates and serious issues have remained open with not a peep from the repo owner @dschuermann.

Since this app is based upon mupdf, I will be installing the vanilla, upstream version which is in active development, instead.

Thus the sorry state of open source. Again, I say this without apology. Some open source projects are great--I use quite a few of them, and regularly, every day.

I wish I knew modern programming languages so I could fork this and keep it updated, but I only know BASIC (the Tandy Color Computer Extended dialect... Don't laugh) and enough HTML, CSS and PHP because I run a WordPress site which takes most of my time.

Thanks @dschuermann for a good app but if you moved on, I'd recommend that this repo be read only and someone can hopefully take it over.

73 de W9JYD

matsievskiysv commented

I've forked this project and changed it a bit (updated libs etc). I will request adding it to f-droid if @dschuermann won't mind or will not reply.

  • 👍2
dschuermann commented

@matsievskiysv sure I am always happy if someone takes ownership. You also invited you to this github repo, but do however you like, this is open source :)

  • 👍1
hwasiti commented

Thanks @dschuermann and @matsievskiysv
Finally, somebody could take ownership. I can see my pull request merged after 1 year.

matsievskiysv commented

@dschuermann How exactly f-droid pulls new releases? Does it detect changes to master?

ildar commented
ericwa commented

@matsievskiysv

How exactly f-droid pulls new releases? Does it detect changes to master?

When I was doing releases I had to:

Typically it would take a few days for the update to show up in f-droid (sometimes the build would fail)

matsievskiysv commented

@ericwa Maybe you know why compilation config of the package is different for each architecture? Is this a f-droid thing or maybe an old gradle version?

matsievskiysv commented

@ericwa Maybe you know why compilation config of the package is different for each architecture? Is this a f-droid thing or maybe an old gradle version?

Found the answer: https://gitlab.com/fdroid/fdroiddata/-/issues/2115