DemesneGH commented on PR #123:
URL: 
https://github.com/apache/incubator-teaclave-trustzone-sdk/pull/123#issuecomment-1933841412

   @b49020 Thanks for your proposal!
   Let me clarify our goal first:
   We absolutely understand the stability and efficiency of `no-std` for OPTEE 
Rust TAs, and are willing to switch to `no-std` and set it as `default` branch. 
The `std` feature are also planned to be added upon the that branch.
   
   For the transition period:
   Considering some of our legacy developers may don't want to switch to new 
branch due to maintainability of their projects, we still keep the legacy 
`master` branch and accept PRs upon that. It would be better if developers 
contribute on the new default branch but it depends on them . If the update 
also makes sense on `no-std` branch, we can sync that. 
   
   For speeding up the transition period, can we have some description on our 
README main page which recommend using no-std and it's benefits? If the 
`no-std` is ready (seems there are some CI error), feel free to open the PR of 
updated README, the `default` branch will be set after the documentation is 
ready. I believe more developers will choose the `no-std` then.
   
   Regarding this PR: 
   I understand the benefit of separate repo which would be clean when we 
publish it on `crate.io` but it's not mandatory for published crates.
   I choose not to merge this PR for now because:
   1. The "transition period" still exists and the separate repo may not speed 
that up.
   2. The `optee-utee` and `optee-teec` are core modules of 
`incubator-teaclave-trustzone-sdk` repo, if they're moved outside, the 
`incubator-teaclave-trustzone-sdk` repo may be useless (examples and tests can 
also go with the separate crates).
   3. Since we are project under the Apache Community, creating a new repo 
needs to involve them in.
   
   Please correct me if I misunderstand, thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org
For additional commands, e-mail: dev-h...@teaclave.apache.org

Reply via email to