Proposal: implementation roadmaps#284
Proposal: implementation roadmaps#284mnm678 wants to merge 1 commit intotheupdateframework:masterfrom
Conversation
Signed-off-by: Marina Moore <mnm678@gmail.com>
mnm678
changed the title
| The following are links to roadmaps for various TUF implementations. These roadmaps are maintained by the projects. If you have a TUF implementation, feel free to open a pr to add it here. | ||
|
|
||
| * **python-tuf**: | ||
| * **go-tuf**: https://github.com/orgs/theupdateframework/projects/3 |
There was a problem hiding this comment.
I know we don't have a dedicated roadmap yet, but it's worth noting - should we assume that a roadmap (something more high-level) would be the same as a project plan (i.e. like what we have so far in go-tuf which is a bit more detailed)?
There was a problem hiding this comment.
I would like go-tuf to have a higher-level roadmap. I think that would serve a different-but-important use compared with the project board.
There was a problem hiding this comment.
+1 for that 👍 I imagine the roadmap as a high-level plan that is being revisited every quarter or so.
znewman01
left a comment
znewman01
left a comment
There was a problem hiding this comment.
I think this is a great idea. Once question: is there a process by which we can make sure these don't get too stale? (Including the TUF-wide one above.) I think "review the roadmap every month at the meeting" doesn't work. Maybe an automatic issue every 6 months or so?
IMO
related example: https://github.com/theupdateframework/python-tuf/blob/develop/.github/workflows/maintainer-permissions-reminder.yml |
|
I created #theupdateframework/community#4 to supersede this issue. |
5 participants
This is a proposal for organizing a place to collect roadmaps from different TUF implementations to provide discoverability of these projects and their plans.
Once this idea (and the location of this list) is discussed with the community, I will follow up with projects to collect an initial list of roadmaps.