Octavi00 commented on issue #9836:
URL: https://github.com/apache/gravitino/issues/9836#issuecomment-5148969705

   > [@Octavi00](https://github.com/Octavi00) 
[@Vonna9](https://github.com/Vonna9) 
[@jujusjuicebox](https://github.com/jujusjuicebox)
   > 
   > Hi all, you've been putting real work into this, and it deserved a roadmap 
it never had. I'm proposing one now: 
[#9836](https://github.com/apache/gravitino/issues/9836) becomes the epic, with 
concrete milestones (M0–M5) attached as subtask issues, each small enough to 
review in one sitting. I'm aligning on it with 
[@roryqi](https://github.com/roryqi).
   > 
   > What this means for you:
   > 
   > * Once Rory and I sign off on the shape, work starts immediately. and we'd
   >   love to have you contribute.
   > * The work you've already done maps onto these milestones, the server tests
   >   are essentially M1, and the client layer is most of M2. This is
   >   reorganization, not a restart, and we'd welcome the contribution.
   > * In the meantime, no need to keep merging main into [[Improvement] Add 
tlsConfigurer for Gravitino #9836 
#10975](https://github.com/apache/gravitino/pull/10975). we can shuffle the 
work into new PRs and review that way.
   > 
   > Let us know if you'd like to keep going. happy to point you at the first 
milestone when it opens.
   > 
   > Thanks, Nevin
   
   Hi @nevzheng, me and @Vonna9 are happy to keep working on this issue. We 
really do find this particular issue interesting and would hate to give up now. 
One question I did have was about M0: is that a module you'd like for us to 
complete, or is that something you will complete so that it will become a 
guideline for our work? I do like the idea of splitting the work up, and it 
should hopefully help with keeping track of all the small changes that I often 
stumble upon. Thank you


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to