Losing the biggest developer and having to fork hurt; let's do better to work together #39
Replies: 5 comments 9 replies
-
I started to open PRs when I first found a bug in the Gallery app. Since then I was somewhat active (my PRs). |
Beta Was this translation helpful? Give feedback.
-
Well, my experience with developer experience turned into "you do not have enough RAM for Android development." Google says 8GB is enough. It is not. I subjected Android Studio to a 5.5 GB resident size limit by using systemd (which is a thing you can try) and that stopped thrashing from negatively affecting the rest of the system, but Android Studio still tends too OOM itself. So I wish I could actively participate but it's just not happening with this computer. Sorry |
Beta Was this translation helpful? Give feedback.
-
I agree with the message in thread. To prevent this project from dying out, we need more active developers. |
Beta Was this translation helpful? Give feedback.
-
Since I don't know how to code and I'm older I'm not sure what you guys consider a bug? But I will try to explain a problem with Gallery and file's vs Amazon drive or photos are devices that Google loaded with security features that will try and sway you from downloading a 3rd party app they've made it so permission of media & file's are removed if you haven't used the app for a while which the phone doesn't know since it doesn't recognize the app like f-droid in the first place kept saying it wasn't installed, I've turned off the button allowing Google to remove permission for file's and Media and to delete any file's and the switch is back on it's infuriating that I have to spend hours going through the phone and finding all the ways Google can remove permission as it's in other places like other app's that use location for example, trying to update the app's is another challenge since the device turns off the app's ability to install unknown app's & updates are like a new download, I'm not sure if Amazon stay's open because of internet access? I believe they figured out a way around the devices supposed security setting's? What's amazing is I might not check Google file's for 6mth unless I get a notification to free up storage and the permissions are never removed! Main device Motorola Edge Android 13 Google owned Motorola back in 2012 not sure when they sold it to Leveno? Hopefully you guys can figure a work around also |
Beta Was this translation helpful? Give feedback.
-
I came across this project fairly recently ans assumed it to be fairly active. I would be very disappointed if it has stalled due to lack of developer interest. What is the current status? There are a few bugs that are affecting me but it looks like they have been open for quite some time without any action and I'm concerned I've switched into a dying project 😥 |
Beta Was this translation helpful? Give feedback.
-
Linux is immune to corporate buyouts. Here's why - look at how many different people have contributed large amounts of code.
The same logic applies to Blender. There are too many people who would need to be bought out.
Contrast Simple Gallery, the flagship app before the fork. A reasonably likely downside scenario for Zipoapps was that they might get a C&D and have to remove a few hundred lines of translations here and there. But as long as they got Tibbi's permission they were 99% clear. (And, like, don't blame Tibbi for selling. The option existed because there wasn't a high volume of community code.)
So, how does a project transition from a single large contributor to many smaller contributors? The self-evident answer is we can't just make Naveen do it. Even if you financially support the project (please do!) hiring one person to do everything doesn't make it a many-person effort.
I would like to suggest a bazaar-style of development, which means anyone can identify problems and suggest solutions - Naveen's essential role would be to listen, evaluate, and make things official. Other kinds of work can and should be done by anyone who finds motivation and makes the time. These three tasks seem particularly important to me:
Eliminate new-developer friction
A technically curious user should be able to go from "hey what if the app did XYZ?" to "my phone is running a development build" as easily as possible. The jump from user to developer is already difficult enough if people need to learn Kotlin and Android APIs. Ideally the effort required to set up tools should be as little as possible.
Take Wikipedia as an example. Even if you don't know how to write in encyclopedic style you can still click the "Edit" tab and holy cow there's the markdown. "Install the app from source code" should be a task that someone can do even without knowing Kotlin or Android development. Playing with an existing open source app may be their first real programming project.
I'll try setting up a dev environment. I'm pretty weak in Kotlin and haven't done Android dev - the fact that I don't know actually helps me give a realistic assessment of how difficult it is to set up. More perspectives are needed.
Support users and identify pain-points
The SimpleMobileTools repository could go dark at any moment and take hundreds of issues down - those are hundreds of issues for people to work on. Someone should archive those - maybe try this software.
(To be polite to GitHub's servers we don't need to scrape the issues 200 times. Maybe, like, 6 is reasonable. Comment if you work on this.)
We need to replace that infrastructure, at the very least breathe life into the Fossify issue trackers. If you think you can troubleshoot or try to reproduce bugs, go ahead and watch the projects now. If there are too many issues you can unwatch or change settings later.
User spaces on Discord or Matrix (Matrix is cool but most users will be more familiar with Discord) seem like a good idea too. If you set something up, remember that you're not official but your moderation choices do have an impact on the community's reputation.
Work on issues if you can contribute anything; you don't have to code a solution
Fixing a bug is like a relay race. If you know how to code and test you're able to run those last segments, but there are other important steps, especially "Document steps to reproduce an issue" (Drupal Contributor Guide). Often a user will identify something that frustrates them, but they don't know enough or have the time or energy to figure out specifically when it breaks.
An issue that caught my attention says that some Calendar years are missing Easter. The reporter has given useful details - the years, some other holidays are missing, they're in Portugal. This is a pretty good bug report but it can be better. How can a developer sitting in Canada see the localized behavior for Portugal? There has to be a setting in Android Studio...
Example: Find the setting. Make a quick note where it is, so that a new developer or tester can get up to speed. Verify issue in Portugal. Try other locales that follow Roman Catholic holidays. Try locales that don't. Post a clear and concise follow-up.
Drupal has a guide to their entire issue lifecycle. It's not necessary to adopt the whole thing, but I think it's full of good ideas.
Beta Was this translation helpful? Give feedback.
All reactions