I see that the code in https://github.com/apache/ozone-go repository was
committed without any code reviews and design.
The code was merged without any Apache jira, design or reviews. The
Apache way of code contribution was not followed in this case.
We should revert the repository to no commits, and then start the work
once we have a design and initial patches to push smaller review worthy
changes in the repository.
Currently all the code from the private repository was directly moved
into the Apache repo without any design, code reviews, Apache jira or
any other process.
I am -1 on this approach of getting the changes into this repository.
Thanks,
Mukul
On 16/03/21 2:23 am, Elek, Marton wrote:
Thanks the positive feedback. Will cleanup existing code to create a
proper initial patch, soon.
I created https://issues.apache.org/jira/browse/HDDS-4977 to follow
the progress.
And a quick demo about the current features:
https://youtu.be/ouNxn9i5DcM
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
