-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move 2023 roadmap to archive and update 2024 roadmap #35
Conversation
@in-toto/in-toto-steering-committee-itsc please review. 🙏 For those available, we can also discuss and review on Friday's community meeting. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! Just need more links as supporting evidence 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great summary, overall very good and captures a lot of key moments.
I've proposed a few links, please do check them for accuracy. Open to thoughts on pinning them as permalinks to commits.
Also interested to hear if people prefer inline links vs footnote links.
- RubyGems | ||
|
||
## Recently Completed Work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trying to understand the intent, does this belong in a roadmap doc vs a retrospective / review doc? I'm not saying we should take it out, but if the idea is to combine those for discoverability and maintainability, I wonder if we want to make that explicit. FWIW, it's probably a good idea.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. Since this roadmap is at a pretty macro-level (yearly or more), the intent to give unfamiliar folks a consolidated place to understand the activity of the projects. As far as making it explicit any suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it's as simple as making a note of the intent of this document at the top as well as in the repo README. That way we'd also have a pointer to the roadmap, which we currently lack. Surfacing it better would be good?
cc @in-toto/in-toto-steering-committee-itsc
Signed-off-by: John Kjell <[email protected]>
Co-authored-by: Trishank Karthik Kuppusamy <[email protected]> Signed-off-by: John Kjell <[email protected]>
Signed-off-by: John Kjell <[email protected]>
Co-authored-by: j-k <[email protected]> Signed-off-by: John Kjell <[email protected]>
Co-authored-by: Aditya Sirish <[email protected]> Signed-off-by: John Kjell <[email protected]>
Co-authored-by: Aditya Sirish <[email protected]> Signed-off-by: John Kjell <[email protected]>
Co-authored-by: Aditya Sirish <[email protected]> Signed-off-by: John Kjell <[email protected]>
Signed-off-by: John Kjell <[email protected]>
LGTM! |
Discussed and approved during community meeting. |
This is a proposed update the Roadmap and it's format. I'm familiar with but, not an expert in many of the subprojects and other activities occurring with the project. If the community or ITSC has any proposed updates or contributions, that would be great!