Preparations for RELEASE on F-Droid and Aptoide #156
Comments
|
For release tagging, it's only important going forward. F-Droid likes tags that are consistently formatted, e.g. "v0.1.24-alpha". I see that current tags already conform to this, so keep doing what you're doing :) |
|
Thanks, that makes one point less. Hope that you're not overwhelmed by all the others. ^^ |
|
Regarding the FOSS part, we have some binary JAR files in the libs folder that need to be removed and included from Maven Central, namely. RootTools.jar, open-csv.jar, httpmime.jar. Please add that as an issue. |
|
For Android package ID - I believe we are good there. It is unique. Not having the signing key from previous builds is not an issue, since the app hasn't been uploaded to play store yet (I assume?). |
|
At command injector - I thought the issue #23 was closed - what needs to happen there? |
|
I have opened a fresh Issue for the FOSS part - see Issue #157. As for the Android Package ID: Would we get another one when uploading to Google Play? Since we deeply believe in open-source software and FOSS, GooglePlay has been neglected numerous times, that is also why we removed Google Play Services (#121). As far I know, Google is not supporting our approaches and does not have the same philosophy like we have. I guess we would be kicked from GooglePlay within 24 hours. I would like to not support Google and avoid an upload of our App there at all costs. About the AT Command Injector: Last I checked, it still did not work as supposed to. Hope @E3V3A will elaborate on this a bit in #23. |
|
I disagree - I can't see why the app would get booted off the play store, and I think ultimately, once it's ready for beta-testing, you should put it in the Play store. You wouldn't need to get a different package id for that. |
|
Hm.. I will reconsider that. Are there any special things we'd need to fulfill for GooglePlay, @tobykurien? |
|
Nope, just need to create a Google Play account, which costs $25 once-off, last I checked. |
|
Hmm, many things here. Let me try to respond briefly, and please move longer developer only discussion to our chat forums...
@tobykurien Just to better understand your point of view. Why do you think it should be in Play Store? I really find it hard to see any reason to further support that, while having a long list of reasons why it shouldn't be there. I think we're a few people who still need some compelling reasons why this would be a good, and why/how it would benefit anyone else than Google? |
|
I've already said why the AT command injector doesn't work HERE. Please have a second look. On the latest build 13 I don't get anything, just the screen title. Not even the text box. |
|
The reason I think the app should be in the Play store is simply for reach. People will benefit from being able to freely install the app from the Play store and be able to check for IMSI-catcher attacks. The majority of users do not have F-Droid or Aptoide installed. Also, this improves fhe likelihood of finding the App via a Google search. I can't see any downside to putting it in the Play store. |
|
@tobykurien, as much as I can understand your point of putting our App on GooglePlay could be another way of reaching a broader audience, I must admit that I am fully against doing so. I am furthermore enforcing my standpoint against GooglePlay through stating here that I will personally pursue any people publishing our App there. Why do I have such a negative feeling about GooglePlay? First of all, Google has done nothing to solve Issue 5353 (Ciphering Indicator) even though users screamed since 2009 to have that feature implemented. Furthermore, none of our team members agrees with their creepy terms and conditions. Our project is not just here to provide countermeasures for the innocent people out there, but also to make people use their brains to get the idea behind free, open-source and unchained software - which GooglePlay does not promote nor support at all.
Have you ever had a search for "IMSI-Catcher" on Google? Which project pops up first? 😺 People interested in IMSI-Catchers and/or countermeasures will inevitably find us. No way around that. And having to pay $25 for an account there just to make our beautiful App become a slave there? Those folks are kidding me! When I add the banners for the download links on F-Droid (if applicable) and Aptoide, I will make damn sure to include one that clearly states we are AGAINST GooglePlay. Hope you don't get mad about that now, but we (and hopefully you too) strongly believe in FOSS. Thank you. |
|
The downside of being on Google Play is that we'd be supporting all the privacy violations that Goggle stand for, and completely contradict all the independence that we've been working for. We just got rid of Google Apps/Maps dependence, so why keep them happier by also having to pay for their spam bullshit. Really!? Put in this context, also having to pay 25 USD should be considered a rape on the Android community. No thanks. But this is just my opinion. But let's save this Google political discussion for some other place, and get back on topic and try to fix more issues than we currently produce. |
|
@tobykurien, @E3V3A and @He3556, seems we are close to another public WIP-Release. Would you please help me ticking off this list in the Issue? Also, our App is still in the Submission Queue on F-Droid. Before we finally launch a public release and opening up our stores, #132 should be solved. |
|
I am overwhelmed by all the various issues everywhere, which is why I requested #166 - that's the only issue I will be paying attention to, until I end up with more free time. |
|
@tobykurien, you are absolutely right. At this moment, our Project is having too many Issues in multiple places. Please don't get discouraged by all this, you are doing it just the right way setting priorities. 👍 |
This Issue shall serve as the central TODO for the public release of
WIP-Release v0.1.24-alphato F-Droid (fulfilling #3 by @PowerPress) and Aptoide. Both stores have already been created by myself and are ready to be published so that our project will gain much more momentum than ever before. Once all the points in this Issue have been solved, the links to both stores will be published on ourREADMEhere on GitHub. It is now upon you, how fast we will reach this goal. Spread the word!I have reviewed all open Issues and linked everything that we have to solve until officially publishing AIMSICD to avoid as much trouble as possible. I would like to see all of our silent followers, forkers and watchers to contribute to achieve all points here: So please chime in with code, stop your silence and TALK TO US here. This is YOUR chance to polish up our App before releasing it into the wild!
@E3V3A, @tobykurien, @andr3jx, @He3556 and of course also to our beloved @xLaMbChOpSx: These are the things to achieve before launching the rocket - let's all work on these, please:
All applications in the repository must be Free and Open Source software – for example, released under a GPL or Apache license. Every effort is made to verify that this is actually the case, both by visual inspection of the source, and by building the application from the published source.- done since our project is fully licensed under GPL v3+.For software to be FOSS, the software in its entirety must be so - including all libraries and dependencies used.- @tobykurien, please grab a coffee and do a full review of our code.The source code for the application must be maintained in a publicly accessible Version Control System which we have support for (git, hg, svn, bzr), and the source code needs to be maintained in an up to date state.- done since we are using the awesome @github.The software should not download additional executable binary files (e.g. non-free addons, auto-updates, etc)- @E3V3A, please re-check how this point conflicts with Automatic Updates from GitHub Release Page #118.The software should use its own unique Android package ID. Where the application is a fork of another (even one not included in the F-Droid repository) it must have a new ID, different from the original.- another point I'd like @tobykurien to inspect. We currently lack the API key that @xLaMbChOpSx used to create the previous builds - another challenge?Although not ideal, "non-functional" assets (e.g. artwork) may be acceptable under less permissive licenses than functional code - an example would be artwork assets that are licensed only for use with that particular game. In any case though, they must be included under some kind of license, and not be copyright violations- done since @SgtObst did an awesome job to create all artwork contained on our repository under GPL v3+.Trademarks must not be infringed, and any other legal requirements must be adhered to- @He3556 please verify that we do not infringe any trademarks. Thank you.Releases should be clearly tagged (or otherwise marked)- I will personally clean up our Releases-Page as per Issue Reformatting and cleanup of the releases page #149. Can you re-check all taggings, @tobykurien? Not sure if all the alpha-builds we had until now have to be re-tagged somewhere or if it is good as it is?WIP-Release v0.1.24-alpha:WIP-Release v.0.1.24-alpha(Issue Bug Report for WIP-Release v.0.1.24-alpha #105).WIP-Internal v0.1.24-alpha-build-13(Issue Bug report: 0.1.24.alpha-b13 #153).Make AT Command Injector finally usable (Issue AT Command Interface #23) - @tobykurien, please review that again.Build: Automatic version and app name update with Gradle (Issue Build: Automatic version and app name update with Gradle #147).Build: Automatic upload of Travis-CI build to GitHub (Issue Build: Automatic upload of Travis-CI build to GitHub #148).Detection 1: Changing LAC (Issue Changing LAC on same CID #91).With this Issue we now have a clear Roadmap of when
WIP-Release v0.1.24-alphawill be published. Please do NOT add any new Issues in new posts here, rather let me know in our internal chat and I will add them to the OP. I want this list to be stable and clean so that everyone can monitor progress using the features of nested task lists. Feel free to make us aware of any other important things here.The text was updated successfully, but these errors were encountered: