-
Notifications
You must be signed in to change notification settings - Fork 134
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
Merge protocols
and roles
workspaces
#1126
Conversation
a320023
to
1766776
Compare
This commits removes the `protocols` and `roles` workspaces and creates a new shared workspace for both of them. In practice we dont have a need to maintain two different workspaces and no benefit is derived from that. With moving to a shared workspaces, the naming of the parent folders was changed as will with `roles` becoming `stratum-roles` and `protocols` becoming `stratum-protocols` and same for `common` crate. This required a fix a across the codebase of the imports inside the different `Cargo.toml`s.
1766776
to
8465b1f
Compare
Bencher
🚨 6 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 7 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
see my comment on related issue |
@Fi3 I dont honestly remember when we talked about splitting them into different git repos, but anyhow thats a much bigger task than just combining them into a single workspace. Things are way over-engineered at the moment without any justification. Whats wrong with combining them together? |
I think there is also an open issue about that by @plebhash ?
What do you mean by that? Btw we splitted the workspaces with the goal of putting protocols and roles in separate repos. The plan was somthing like that:
|
There is this proposal discussion for a repository split: #1069 (comment) But I'm not in a rush to execute this split just yet, because this has many implications and needs to be properly planned. For now, I'd be happy to keep the discussion going on a conceptual level, so we get consensus on the best repository structure and we can eventually plan accordingly for the execution in the future.
I think we are in the middle of 3 right now, via #845 And also #1120 will help bring more stability into the work that was done on 2, because we will be able to get more confidence that the roles implementations are correctly implementing the protocol spec. Once we move into 4 in the future, we will basically be trying to bring the work that was done in 2 into production readiness. Which ones we will focus first is a future discussion, and hopefully by that time we will also have more feedback from industry adopters, which will help us make those decisions. with regards to this actual PR, I'm not very opinionated in case I come across something that makes me realize this is needed I'll come back here and elaborate, but for now I'll focus on other tasks |
concept nack |
#1125
This commits removes the
protocols
androles
workspaces and creates a new shared workspace for both of them. In practice we dont have a need to maintain two different workspaces and no benefit is derived from that.With moving to a shared workspaces, the naming of the parent folders was changed as will with
roles
becomingstratum-roles
andprotocols
becomingstratum-protocols
and same forcommon
crate. This required a fix a across the codebase of the imports inside the differentCargo.toml
s.