Lack of collaborators limits community development

[rkokkelk]

Hi,

I've been a user of todo.txt for a while now using it many different devices but never using the Android application. This is because I'm using Owncloud for synchronization instead of Dropbox. As an open-source developer I was determining whether I can make a contribution for providing this functionality into the Android App.

However, the amount of open pull requests which dates back several years have discouraged me into taken any actions. These pull requests are still open without any further progress, there are new issues posted with or without additional solutions which are not being resolved. In general, the entire development of the todo.txt android application is at a halt, as can be seen by the last commit at the master branch which is more than 2 years old. This is a shame because I think that there are numerous developers, me including, which are ready to extend the current functionality, resolve the issues and in general improve the application.

So, I'm requesting that more collaborators will be added to this repository in order for new pull requests to be handled in a timely manner. This in turn will ensure to other developers that this is still an active project and that new additions are being welcomed.

[renemo]

+1

[schilke]

:+1: if this counts (unfortunately my own Android dev skills are limited to compiling an app :grimacing: ) I'd love to see any active development for Todo.txt Touch again as it's still my No. 1 productivity tool and its' flexibility will never be beaten by any other app or service.

[ggbc]

@rkokkelk why don't we fork the project and start our own todo-txt* ? By the punchcard seems that gina and the others abbandonned the project a long time ago.

[rkokkelk]

Given the reactions of them on this issue I totally agree with you. Forking this project and trying to continue the work is definitely possible. But given the fact that there also exists other similar apps who are compatible with todo.txt, such as Simpletask. I'm wondering whether the community will appreciate a fork of this app.

Can anyone affirm whether a fork of the app will be appreciated by the community?

[mikeofmany]

Just getting time to comment on this. While I don't know Gina's task list or stance I can say that to me, it seems many in the community are either going to jump to use a more GUI'd fork and some will stay. At the same time, somehow it seems that this community doesn't have a lot of developer hours or even minutes to contribute -- especially with so many finding what's in the main script working for them now. So, a fork probably will not drum up any additional support other than what you, yourselves bring to it.

[karbassi]

@rkokkelk, I wanted to give an update to this:

First, the project as a whole as moved to an ORG. Read more here: http://blog.todotxt.org/post/164525181522/community-and-the-future-of-todotxt

Second, we're still looking for active developers to join the team. If you or others are willing to come on board to help build Version 2.0.0, we're eager to onboard you.

I'm leaving this issue open to allow discussion and/or others to chime in.

[evanp]

@karbassi is there a way to put out a call for Android developers to help out? It'd be great to see the critical bugs in this app fixed soon.