[Suggestion] Maintaining the project

[machiav3lli]

Considering the state of the project being inactive for months and a lot (possible) users lost in the limbo of half-backed/buggy AuroraDroid v1, barebones F-Droid and mythical AuroraDroid v2. I'd like to co-maintain the project. This would naturally come with some more communication effort.

So my questions:

• Are you welling to further maintain the project?
• If yes, would you prefer to only have contributions or to co-maintain with other (e.g. me)?

If there's no wish for external contributions or if you think you won't be able to (co-)maintain the project in the next time, I'll possibly start an independent fork soon enough.

Cheers

[3504k]

Is there a huge benefit to maintaining this vs forking? The app is popular enough where a fork will spread like fire on forums, reddit, discord, etc.

[machiav3lli]

@3504k I'd prefer to co-operate on maintaing the project like what I do on Omega launcher. As considering how many projects am engaged in and OABX being my main project, it'd be hard to maintain the project alone the way I'd like to.

The resonance in the community (FOSS-Community sround OABX and Omega) is pretty positive considering a fork. But as said mentioned above, it'd be better to co-maintain the project.

[another-sapiens]

A new fork just came up on F-Droid today. It's called Droid-ify, and it's actually pretty good.
In case nothing can be done here, it could be a good idea to contribute to that fork instead: https://github.com/Iamlooker/Droid-ify

[another-sapiens]

On the other hand, Foxy supports Android 5, while Droid-ify only supports 9 and up. Maybe a separate fork is not a terrible idea either.

[machiav3lli]

@another-sapiens the mentioned fork is (for now) just a nice paint job for now, I don't how serious is the developer in maintaining functionality.

Nevertheless, I can imagine to work with him/her, as I said, am really open to co-maintaining the project, but I think big parts of the project needs to be re-written and the architecture has to be planned a new. Those are my requirements to work on any downstream/independent fork.

[another-sapiens]

@machiav3lli Well put!
I mentioned it mostly because they'd be more prone to merge any requests, as I don't know if this project will have any activity in the near future.

[ItsHarper]

To me, the fact that Droid-ify doesn't have a shared git history with this repository is a significant downside. It makes it much harder to share code between the different forks.

[Donkey-Doug]

big parts of the project needs to be re-written and the architecture has to be planned a new. Those are my requirements to work on any downstream/independent fork.

The dev of droid-ify seems quite serious about the development.

[Iamlooker]

On the other hand, Foxy supports Android 5, while Droid-ify only supports 9 and up. Maybe a separate fork is not a terrible idea either.

Umm.. Droid-ify supports Android 6+

[triallax]

I've published a fork of Foxy Droid with updated dependencies, and I plan to maintain it for the forseeable future since I use it myself. However, I want to set expectations, so here's what I plan to do for the fork:

• Keep dependencies and target/compile SDK up-to-date
• Accept translations or translation updates (I'll try to merge all the translation PRs open on this repo)
• Fix bugs, as long as it doesn't take too much effort

What I don't plan to do:

• Add any major features
• Make any changes that require a lot of work (especially UI changes, I think the app looks great as-is)

If you're a fan of Foxy Droid's UI, my fork should be perfect for you.

I haven't decided yet on a name for the fork, suggestions are welcome.