search

joaomneto / TitanCompanion

Android app to support Fighting Fantasy gamebook playing without the use of additional pen, paper and dice. The objective is for the reader to immerse himself fully on the book and let the app do the rest of the work. The objective of this application is to support the distinct rules of each Fighting Fantasy gamebook.
GNU Lesser General Public License v3.0
14 stars 4 forks source link

Inclusion in F-Droid #136

Closed Poussinou closed 6 years ago

Poussinou commented 6 years ago

Hi,

Since this app is LGPLv3 licensed, are you considering the fact to add it to F-Droid? There is a strong community behind, that do not use Google Play nor anything else, except F-Droid.

You can find some documentation here.

Otherwise, if you don't want to work on the inclusion of this app by yourself, would it be ok for you if someone else do it for you?

joaomneto commented 6 years ago

It's an excellent idea. I always forget F-Droid. Are you aware of an automated release procedure to do so?

On Tue, May 15, 2018, 13:43 Poussinou notifications@github.com wrote:

Hi,

Since this app is LGPLv3 licensed, are you considering the fact to add it to F-Droid https://f-droid.org/? There is a strong community behind, that do not use Google Play nor anything else, except F-Droid.

You can find some documentation here https://f-droid.org/docs/.

Otherwise, if you don't want to work on the inclusion of this app by yourself, would it be ok for you if someone else do it for you?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/joaomneto/TitanCompanion/issues/136, or mute the thread https://github.com/notifications/unsubscribe-auth/AFTNQn5Pn2ABNyJARZ7CqWCjEd0qa5myks5tys1_gaJpZM4T_eWR .

--

João Neto

Poussinou commented 6 years ago

There isn't really an automated procedure to release an app on F-Droid. First, I opened a Request For Packaging.

The best way to have it included ASAP is to install the fdroid server tools on your computer(doc here), to write the small "build metadata reference" (here are some examples 😄 )

The problem now is that some of your dependencies aren't open-source, right? Which exactly?

joaomneto commented 6 years ago

All the dependencies are open-source:

    implementation 'com.android.support:support-v4:27.1.0'
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version"
    implementation "org.jetbrains.kotlin:kotlin-reflect:$kotlin_version"
    implementation 'commons-io:commons-io:2.6'
    implementation 'androidx.core:core-ktx:0.2'
    androidTestImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'
    androidTestImplementation 'com.android.support.test:runner:1.0.1'

The only thing that is not open and I do not own is some book covers that are included as low res jpegs.

Poussinou commented 6 years ago

Oops sorry, I just read play in this line com.github.triplet.gradle:play-publisher:1.1.5 . I tough it was in relation with google play, which is something that's often problematic (didn't notice the word github)

The book covers as low res jpegs should be ok.

The inclusion of this app should be pretty easy, I'll have a look this week.