project is dead? #208

New Issue

2024-12-31T19:45:35-05:00

EliasTheGrandMasterOfMistakes commented

2024-12-31 19:45:35 -05:00

(Migrated from github.com)

No description provided.

👀 3

Delta0001 commented

2025-01-29 14:39:18 -05:00

(Migrated from github.com)

I actually came here to discuss this. I noticed that none of the pull requests are being merged. Last commit from maintainer is over a year ago.

👍 1 😕 3 👀 5

claui commented

2025-02-20 09:33:52 -05:00

(Migrated from github.com)

Update: Comment now out-of-context because earlier comments have been removed.

@WesleyVanNeck Thanks for maintaining your fork!

I think that commits such as https://github.com/WesleyVanNeck/waydroid_script/commit/d384d7f46b2e875f6146e9b3ba7bd937d9c8af85 and https://github.com/WesleyVanNeck/waydroid_script/commit/9a25328017fdf3c0ebae8dc718cbfa8e7c2019c3 are not quite as transparent as they could be.

I’m convinced that you’re a perfectly trustworthy person, and I’m happy for you to share your work with everyone. But no matter who you are, users shouldn’t really be encouraged to run scripts that download and install a binary blob from an anonymous Dropbox with:

no versioning history,
no attribution as to who controls the Dropbox,
no explanation where the file originally came from, and
lack of clarity in commit messages as to what has caused the checksum of a file to change.

It’s not that you owe us anything. On the contrary, it’s us who have to be thankful to you for sharing your work with everyone! But if you could make the commit messages in your fork just a tiny bit more transparent and give us a little more detail of why an upstream blob was updated, then that would be super helpful. https://github.com/casualsnek/waydroid_script/commit/2e693d03dbe9fb857b77e50dea235090c45e01b7 is an example for a great commit message. And if you could even figure out a way to host the NDK libs at a source that’s a little more stable than an unversioned Dropbox, then that would be outright amazing. ❤

**Update:** Comment now out-of-context because earlier comments have been removed. --- @WesleyVanNeck Thanks for maintaining your fork! I think that commits such as https://github.com/WesleyVanNeck/waydroid_script/commit/d384d7f46b2e875f6146e9b3ba7bd937d9c8af85 and https://github.com/WesleyVanNeck/waydroid_script/commit/9a25328017fdf3c0ebae8dc718cbfa8e7c2019c3 are not quite as transparent as they could be. I’m convinced that you’re a perfectly trustworthy person, and I’m happy for you to share your work with everyone. But no matter who you are, users shouldn’t really be encouraged to run scripts that download and install a binary blob from an anonymous Dropbox with: - no versioning history, - no attribution as to who controls the Dropbox, - no explanation where the file originally came from, and - lack of clarity in commit messages as to what has caused the checksum of a file to change. It’s not that you owe us anything. On the contrary, it’s us who have to be thankful to you for sharing your work with everyone! But if you could make the commit messages in your fork just a tiny bit more transparent and give us a little more detail of why an upstream blob was updated, then that would be super helpful. https://github.com/casualsnek/waydroid_script/commit/2e693d03dbe9fb857b77e50dea235090c45e01b7 is an example for a great commit message. And if you could even figure out a way to host the NDK libs at a source that’s a little more stable than an unversioned Dropbox, then that would be outright amazing. ❤

👍 6 ❤️ 5

ayasa520 commented

2025-09-09 07:33:40 -04:00

(Migrated from github.com)

Many contents in waydroid_script are already severely outdated, and updating them and verifying they actually work might be as troublesome as rewriting a new waydroid_script.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wbruno/waydroid_script#208