Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

eholk
Copy link

@eholk eholk commented Jun 26, 2025

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


| Metadata | |
| :-- | :-- |
| Point of contact | @epage |
Copy link
Author

@eholk eholk Jun 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@epage - are you still the best point of contact for this? If you'd like a break I'd be happy to put my name instead. Or @b-naber would be a good choice.

Copy link
Contributor

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.

Comment on lines +33 to +36
### The "shiny future" we are working towards

## Design axioms

Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants