This repository has been archived by the owner on Dec 1, 2023. It is now read-only.
docs: add H2 2023 roadmap #82
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
galargh
commented
Jul 4, 2023
|
|
||
| const children = [] | ||
| for (const {title, body} of milestones) { | ||
| issue = issues.find(issue => issue.title === title); |
There was a problem hiding this comment.
@laurentsenta Here, we're looking for issues by title (extracted from markdown). With your proposal of embedding the linking back into markdown this could be improved. Side note, we won't have to worry about infinite workflow triggers either. GHA will prevent that from happening. When we push to ROADMAP.md as GHA, the workflow will not start again.
SgtPooki
reviewed
Jul 4, 2023
ROADMAP.md
Outdated
|
|
||
| ## Immerse Into the Day to Day of IP JS Developer | ||
|
|
||
| As one of the most underresourced projects within IP Stewards group, we think it is the best target for our research. We want to embed with the team for a while to uncover areas of potential DX improvements. By the end of this excercise we want to have a concrete, prioritised list of improvements that would make life of a IP JS developer easier. |
laurentsenta
reviewed
Jul 5, 2023
laurentsenta
reviewed
Jul 5, 2023
Co-authored-by: Laurent Senta <Laurent.Senta@gmail.com>
galargh
commented
Jul 7, 2023
|
I'm going to merge it now to sync roadmap issue(s) - this does not mean I'm closing the discussion on the roadmap. I do believe it should be a living document, especially in case of our team. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds #81 to the repository as a markdown file. We think it's easier to collaborate on the roadmap if we can comment on any particular line and leave suggestions. The markdown file will be the main source of truth.
This PR also adds automation which, on push to main, reads through the markdown file and creates/updates issues accordingly. The issues will link back to the source of truth. The automation will only update the issue body after the first encountered line separator (
---) - this will allow users to maintain part of the issue content manually if needed.This builds on Laurent's experience with ROADMAP handling in testground org.
Testing