-
Notifications
You must be signed in to change notification settings - Fork 65
Carry forward Open Namespaces goal to 2025H2 #322
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
base: main
Are you sure you want to change the base?
Conversation
|
||
| Metadata | | | ||
| :-- | :-- | | ||
| Point of contact | @epage | |
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.
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'm fine being the overall point of contact and just delegating updates to the specific team currently owning the work.
### The "shiny future" we are working towards | ||
|
||
## Design axioms | ||
|
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.
It'd be good to fill out these two sections.
As a design axiom, I think it'd be good to have something about integrating well with the resolver code, preferably leaving it simpler overall.
| Point of contact | @epage | | ||
| Teams | <!-- TEAMS WITH ASKS --> | | ||
| Task owners | <!-- TASK OWNERS --> | | ||
| Status | Invited | |
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.
assert_eq!(invited, accepted);
| Status | Invited | | |
| Status | Proposed for mentorship | |
We'd like to keep working on Open Namespaces for 2025H2. This copies over the previous goal and makes changes according to our plans for the next six months.
Rendered