docs: remove docs/ROADMAP.md (or update it) #1525
Comments
|
No, I think we should keep it. Let's make a process to update the roadmap once a quarter/year? We can talk about it in the next community meeting. @mnm678 |
|
I'm going to push back on this on principle. We have too much documentation (in comparison to maintenance resources). In this case, there are many ways to document future plans, a text file is one possibility. Someone should show that ROADMAP.md is useful for the project and is being maintained, then I'm all for keeping it. |
|
Let's discuss this at the next meeting. |
jku
pushed a commit
to jku/python-tuf
that referenced
this issue
Sep 29, 2021
This file is out of date to the point of being obsolete. An updated ROADMAP document would be warmly welcome but an out of date roadmap is worse than nothing. Fixes theupdateframework#1525 Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
jku
pushed a commit
to jku/python-tuf
that referenced
this issue
Nov 30, 2021
This file is out of date to the point of being obsolete. An updated ROADMAP document would be warmly welcome but an out of date roadmap is worse than nothing. Fixes theupdateframework#1525 Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
Merged
MVrachev
pushed a commit
to MVrachev/tuf
that referenced
this issue
Dec 1, 2021
This file is out of date to the point of being obsolete. An updated ROADMAP document would be warmly welcome but an out of date roadmap is worse than nothing. Fixes theupdateframework#1525 Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm updating some documentation and noticed our installation document refers to ROADMAP.md.
This file is not updated and does not seem to have a lot of useful information: I suggest we remove it and links to it.
The text was updated successfully, but these errors were encountered: