Skip to content
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

Redocument this proposal better #3

Open
Jack-Works opened this issue Nov 19, 2020 · 1 comment
Open

Redocument this proposal better #3

Jack-Works opened this issue Nov 19, 2020 · 1 comment

Comments

@Jack-Works
Copy link
Member

The presentation at the meeting is quite a hurry and I guess many delegates (including me) didn't understand this proposal well.

Based on the reaction to the meeting, I suggest restructuring the proposal in the following way.

  1. Cite the problems this proposal is intending to resolve
  2. Splitting the design into orthogonality parts if possible and mark them as "core" or "better to have" (many raise concerns about isolation namespace)
  3. Explain how each design resolve the motivation and work with other parts of this proposal
  4. Explain the relationship between this proposal, the current bind proposal, and the pipeline operator proposal, how they are overlapping, and how they are irrelevant.
@MrXploder
Copy link

Can we all cooperate? can I make a pull-request addressing this issues?

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

No branches or pull requests

2 participants