opentasks
opentasks copied to clipboard
dmfs
Release plan / further development opentasks?
Good question.
As you may have noticed (on my GitHub profile) we're currently very busy with other tasks and don't have the manpower to spend much time on OpenTasks. That being said, this project is not abandoned. It's still an important part of our portfolio.
I know that a lot of issues and pending PRs have piled up, including emails of developers offering to help out with some of the issues. I'll try to respond to all of them during next week. Please contact me again if I missed someone.
The current roadmap looks sort of like this (aside from all the open bugs that need to be fixed):
- integrate opentasks-provider as a module into the OpenTasks repo. Although there are some good reasons to develop it separately it's probably easier to maintain in future if they are in the same repo. Also the chances that this will ever by part of AOSP are close to 0 so there is no need to maintain a separate provider component (like Android does it with calendars and contacts).
- Recurring tasks (long standing feature request), a lot of changes have already been made towards this (including a recurrence rule parser and iterator) but ultimate support is still not done yet. I've spend much time thinking about how to implement this, i.e. expand all instances on insert vs. just calculate the next instance and how to deal with recurrence excludes and exceptions. Not all other clients support all that for tasks (namely Apple clients).
- Custom alarms (the provider already has some preparations for this).
- Task relations (most importantly sub-tasks, but also other relationships). I think this is already supported by the provider, just the UI part is missing.
- Refactor the task editor ("Materialize" it).
For obvious reasons I hesitate to put a date next to each item. However, I think I can spend a few days per month to work on this, review PRs and give guidelines on how to approach certain issues (we have concrete design plans for many of the open issues).
:+1: Thanks for this detailed description of the situation! I'm very happy to read that you plan to invest some time in this great app (IMHO this doesn't need to be in implementing many new features, but with the highest priority in reviewing PRs and publishing releases with the work already done in order to keep the app alive -- and also giving guidelines on how to approach certain issues (as you wrote)).
Thank u for detailed answering. What is with #37 Subtasks?
I think this app is unique. Have you think about to ask owncloud/nextcloud for help? Perhaps they can miss somebody for some weeks to push opentasks little bit. I would also help u but my Java knowledge tends agisnst 0
I absolutely love this project and hope that it will take up some steam again, since it is rather dead, at least judged by the commits / releases in the last year, which is a long time in the mobile world. Is there any way to throw some money your way to further motivate you? Maybe you should add some sort of donation link (PayPal, Bitcoin, etc.)? Money is probably not solving the issue, but for me it has always been a nice motivation to see that people are willing to donate on a voluntarily basis.
@kbabioch It's not so much a matter of money, unless a donation button would return enough to pay a developer to work on this (but I doubt that). If someone would volunteer to do code reviews it would certainly help a lot.
@Bullnados Some of the "non coding" tasks on such a project are
- monkey testing
- adding/fixing translations
- coming up with new ideas/improvements
The last point also includes new UX concepts that users might benefit from.
Okay. I could help u with all three points. Translations I could help with english/german or transifex. UI would be mostly new land
