Add more maintainers

[waldyrious]

There are several issues and PRs that are somewhat stalled due to lack of active maintainers. Would it be possible to give a few more people commit rights, @karbassi? That way the project could continue to evolve; otherwise, people may start looking into forking the repository, which IMO would be bad for the todo.txt ecosystem.

[waldyrious]

Also tagging the other members of the todotxt org: @evanp, @ginatrapani and @inkarkat.

[dessalines]

This format has been unmaintained for years now, and development on most apps (except for one on android) has all but ceased.

I highly suggest switching to https://github.com/tasks/tasks , which has much more development.

I've recently written a todo.txt -> tasks.org importer here: https://github.com/dessalines/tasks-org-todo-txt-import

[inkarkat]

I wouldn't say unmaintained, rather quite mature. That said, @karbassi hasn't responded to anything for many months (even though he's still active on GitHub), which worries me (initially I had just assumed he's currently busy, and will pick up things later), and I fully agree that more maintainers would certainly be welcome (but is there anybody who would volunteer?)

I've been responding to issues and questions on https://github.com/todotxt/todo.txt-cli, and I could integrate outstanding pull requests there; however, the agreement had been that @karbassi would drive this and I'm just providing comments and a bit of help on the side, and I currently also lack knowledge and access rights to do todo.txt-cli releases.

[karbassi]

Hello all! I am still here and reading over all the messages. I am to be more active in the new year, after the holiday season.

I am all for adding more active maintainers, though. Let me know who is interested.

[dessalines]

I wouldn't say unmaintained, rather quite mature

Its definitely unmaintained. Look at the PRs on this repo. None of the maintainers have commented on most of them, and some have been open for 4 years now.

[waldyrious]

Thanks @inkarkat and @karbassi for the update! I would like to propose @clach04 for a maintainer.

I have been watching this repository for a while, and noticed that they have been commenting in several issues and PRs and IMHO demonstrating a good understanding of the project and a thoughtful, prudent approach with their comments and the proposals they put forth.

Not that anyone should make decisions unilaterally, no matter how sensible their reasoning is; but there should be someone actively reacting to the community activity and implementing broad consensus that forms around such discussions, as long as that doesn't go against previous stances of the project.

[clach04]

This format has been unmaintained for years now, and development on most apps (except for one on android) has all but ceased.

I highly suggest switching to https://github.com/tasks/tasks , which has much more development.

I've recently written a todo.txt -> tasks.org importer here: https://github.com/dessalines/tasks-org-todo-txt-import

Tasks looks neat, thanks for sharing. I do use Android so I should check this out. I have different needs for todo lists depending on the arena (I deliberately don't mix home/work for instance as that works better for my brain). I do a lot of todo view/editing on non-Android platforms so I'm unlikely to move away from todo.txt but I like the thought of a nice sync server with existing standards. Good share!

I do really like https://github.com/mpcjanssen/simpletask-android for Android todo.txt management.

[clach04]

Hello all! I am still here and reading over all the messages. I am to be more active in the new year, after the holiday season.

I am all for adding more active maintainers, though. Let me know who is interested.

Yay! I hope all is well with you.

Thanks @waldyrious for the vote of confidence! I appreciate the warm comments :-) I'd be happy to pitch in every now and again. I can't commit to super-fast responses, I'm definitely going to have things that have to take higher priority. I'm sure you are in the same position where one does not had the time and/or energy wanted/needed to devote to projects.

[clach04]

@karbassi I'm only an occasional user of https://github.com/todotxt/todo.txt-cli so for what it's worth the code changes/PRs from @inkarkat that I've seen look clean and clear.

[ghost]

Hi everyone.

I wanted to know if the project is active, because I would like to contribute with some ideas, codes, implementations. Follow the list of ideas:

Idea

todo-txt & yaml-spec 1

---
  title: 'search'
  description: 'search for best website'
  completed: 'yes'

todo-txt & yaml-spec 2

---
A: 'Search for Best Website ::: https://www.google.com/'
B: 'This is effectively the title ::: this is effectively like a newline or "ignorable" area for most clients'
C: 'Register for appointment at DMV ::: https://some.long.dmv.url.gov/form/some-thing/here.cfm'
D: 'A complicated issue ::: { "json": "blob", "goes": "...here..." }'

todo-txt & theme tododoist

todo-txt & github-readme-stats

another idea?

I wanted to create documentation of todo-txt in docsify and an version todo-txt in RFC.

question/feedback

what you all think of the idea?

[inkarkat]

@karbassi commented on Dec 18, 2022

Hello all! I am still here and reading over all the messages. I am to be more active in the new year, after the holiday season.

I don't see any progress, not here nor over at https://github.com/todotxt/todo.txt-cli, where pull requests have been queuing up. Will you be able to dedicate some time to this project in the near future? Or at least officially announce your unavailability and add some more maintainers, as requested in this issue?

[sycam0r-e]

I have been using todo.txts and related applications for some time now. I think todo.txt is an important standard due to its simpicity and versatility.

As a total project outsider and a non-dev, but as an enthusiast for FLOSS software and standards and protocols allow me to add my perspective.

It is an utter shame that todo.txt is slowly dying simply because the original maintainers' vanity prevents them from adding more maintainers. Simple as that. I am really grateful to the original maintainers for having done what they did. However, they are destroying their own work and let others suffer due to their negligence. If you cannot, for whatever reason, maintain this project reasonably, at least be reasonable enough to add some of these motivated and knowledgable folks here as maintainers (not me).

Please.

[karbassi]

@karbassi commented on Dec 18, 2022

Hello all! I am still here and reading over all the messages. I am to be more active in the new year, after the holiday season.

I don't see any progress, not here nor over at https://github.com/todotxt/todo.txt-cli, where pull requests have been queuing up. Will you be able to dedicate some time to this project in the near future? Or at least officially announce your unavailability and add some more maintainers, as requested in this issue?

Hello @inkarkat and others. This is a valid criticism and I hear you. I've been trying hard to carve out time in my life to review and maintain this (and other) projects. However, I have dropped the ball.

@inkarkat, as one of the main (and active) maintainers of the project, can you nominate a few new maintainers and we can review and add them. I want to see this project continue and grow.

[inkarkat]

@karbassi, I know how you feel, how hard it is to realize that despite all the good intentions, it's impossible to make it all fit. Realizing that you have to let go of something you've put so much effort into is hard. You've enthusiastically picked up the entire project when Gina asked for volunteers, and you've done a great job. Since then, the project's pace has slowed down, but as you can see, there's still use and interest. A new approach for the project's stewardship is needed.

@inkarkat, as one of the main (and active) maintainers of the project, can you nominate a few new maintainers and we can review and add them. I want to see this project continue and grow.

For todo.txt-cli, there have been good recent pull requests from @chrysle and @hyperupcall. I think we'd need to spread the word a bit to get more people involved. Merging the outstanding pull requests and (finally) releasing a new version of the CLI would help with that. If you'll add some basic instructions on how to do that to the Wiki (which would be required for a larger set of maintainers, anyway), I could do that (and beta-test your instructions; I'm also not sure if I already have all required permissions for that).

[hyperupcall]

@inkarkat thanks for the mention. Stepping up as some sort of co-maintainer is something I'd be interested in. I do have experience with projects in the same vein - old/mature shell scripts that best be backwards-compatible. For example, contributing heavily to asdf, co-maintaining tj/git-extras, and maintaining autoenv. I'd be happy to help with pull requests, code reviews, and the regular stuff.

[karbassi]

Thanks @inkarkat for nominating @hyperupcall and for @hyperupcall for stepping up.

I'll leave this up for a simple vote and/or discussion.

All in favor of @hyperupcall being added as a co-maintainer of todo.txt / todo.txt-cli?

Please use the thumbs up 👍🏽 or down 👎🏽 to vote.

I'll give until the 2nd week of January for people to vote.

[clach04]

All in favor of @hyperupcall being added as a co-maintainer of todo.txt / todo.txt-cli?

👎 for todo.txt - no contributions to discussions as far as I can see https://github.com/todotxt/todo.txt/issues?q=hyperupcall and https://github.com/todotxt/todo.txt/pulls?q=author%3Ahyperupcall
👍 for https://github.com/todotxt/todo.txt-cli - excellent PRs https://github.com/todotxt/todo.txt-cli/pulls/hyperupcall

[chrysle]

@karbassi Wouldn't want to disturb you, but we're nearing the end of June..

[inkarkat]

@karbassi It's almost a year since the vote, the issue itself is two years old, and no maintainers have been added yet :-(

Rumors about this not being maintained are spreading. Hey, don't feel bad if you just don't have the time 🤷

@clach04 has recently started his own fork of the spec; even though I don't know where he intends to take this, I'd much rather have someone actually drive the main project, participate in discussions, and merge stuff than see this project languish and the community fragment.

So here's my vote for a leap of faith and making @clach04 a maintainer (now, while he's got the momentum going, not in six months!) And the two other candidates I proposed as well...

If you want me to make a release of the CLI (I think my write access will suffice), just give me a quick 👍 and I'll figure it out. I didn't want to step on your toes, but I really think we need a release there to prove that it's not dead yet.