Using upstream issues a personal TODO lists

[pmario]

Related to: [IDEA] Stop $eventcatcher propagation only when actions are actually executed #8998

pmario wrote

IMO reopen and adjust the Status should work too. So we do not need to create a new issue

@saqimtiaz wrote

@pmario some contributors use their issue and PRs as a checklist of things they are working on. Therefore forcing someone to have an issue or PR open seems illadvised, and I would recommend erring on the side of caution and avoid re-opening an issue or PR without agreement from the contributor.

[pmario]

Then I have to say "they are using it wrong".

IMO there are 2 ways to track issues you want to work on.

• The Assignees list in upstream repo, on the top right of the issue.
  • IMO Contributors are allowed to assign users to every issues
  • If the repository settings allow it, users can assign themself as assignees too
• Use your own TiddlyWiki fork, to have the full power of the GitHub UI
  • Projects, Kanban boards issues and so on

Since with a fork the use has full access, managing todo lists is simple and completely independent of the main repo here.

IMO issues created here, belong to this upstream repo. Just because a user does not want to work on an issue, does not mean the issue goes away (is closed as "not planned"). It is still an issue. Especially if it is a bug.

---

Close as not planned is like a Wont Fix label, which we did remove on purpose.

[pmario]

This is an example of a Project to manage my TODOs for whatever upstream repo I want to contribute to.

[pmario]

@yaisog ... What's your thoughts about this?