Summit

851 readers

145 users here now

Community to discuss Summit, a Lemmy reader for Android.

App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit

APK: https://github.com/idunnololz/summit-for-lemmy/releases

Support the app

Website: https://summit.idunnololz.com/

founded 2 years ago

MODERATORS

[email protected]

Open sourcing Summit? (lemmy.world)

submitted 1 day ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

From what I understood, you didn't want to open-source Summit because you don't want to allocate your resources to managing issues and reviewing pull requests amongst other reasons (correct me if I'm wrong!). I don't know if you can disable Issues/PRs on GitHub, but I think it would give a lot of (potential) users peace of mind if the source code could be reviewed. As far as licensing goes, you could go quite stringent with an AGPL if that is a factor, to prevent closed-source clones.

Anyways, I find it sad to see that Summit often gets bashed in Lemmy application discussions for being "yet another proprietary app, no thanks".

That said, if setting up publishing actions or other packaging shenanigans is a hurdle, I'm sure there's people who would love to help.

all 7 comments

sorted by: hot top controversial new old

[–] [email protected] 4 points 1 day ago (1 children)

https://lemmy.world/post/27182708

[–] [email protected] 3 points 1 day ago

Whoa! That's huge, congrats!

[–] [email protected] 8 points 1 day ago* (last edited 1 day ago) (3 children)

I've been giving this thought here and there. I was planning on making a decision by the end of the year but I guess I can expedite the decision.

Below are some very disorganized thoughts I have. I will reply later when I'm more available or make a separate post later today maybe.

So I think I am more ok with open sourcing the project (however it will not accept PRs), but there are some action items I need to get done before I can get there. There is also competing priorities between these three projects:

Implement a sharing system that allow users to share their app settings with others to make setup easier. Also offer some default setting templates.
Implement more user requests.
Open sourcing the app.

As for action items, the main one I need to get done is to replace Firebase. So I did some research a few days ago on this and unfortunately there doesn't appear to be any FOSS alternatives to Crashlytics which is unfortunately. However, my thoughts here is that I should still move away from Crashlytics because it's reliant on Google Play Services and the community seems pretty divided on it.

I could also just open source the app and ask questions later. I need more time to gather my thoughts.

P.S. I had a twisted joke idea to announce that I was going to open source the app on April 1st (April fool's day) and then actually open source it on April 2nd.

[–] [email protected] 3 points 1 day ago

Many, many thanks for your openness and all your efforts! The twisted joke would have been great fun as well 😂

[–] [email protected] 5 points 1 day ago

Thanks for all you do, love the app.

[–] [email protected] 4 points 1 day ago

I don't know if you can disable Issues/PRs on GitHub

Yes.