Hello! First of all, I'd like to ask you to communicate using English, it's more convenient for everyone, thank you!
Secondly, as far as I know, any member of the community can work on any issues, and the code will then be discussed and committed into a main branch, if approved by a *committer*. This includes issues from the aforementioned IEP. If that's your first step with developing Apache Ignite, I would recommend starting with something that doesn't require as much knowledge of product internals, and then eventually move to features like this one. What's described in IEP is quite tricky from the implementation point of view. сб, 10 авг. 2024 г. в 14:37, jh w <jh2310237...@gmail.com>: > 请问提交多少代码有希望成为apache commit呢？ > > jh w <jh2310237...@gmail.com> 于2024年8月10日周六 19:34写道： > > > You mean I can develop this requirement? > > > > > > Ivan Bessonov <bessonov...@gmail.com> 于2024年8月8日周四 16:23写道： > > > >> Hello Igniters! > >> > >> I prepared an IEP for Ignite 3 disaster recovery basic features and API, > >> please take a look. > >> > >> [1] > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493878 > >> > >> -- > >> Sincerely yours, > >> Ivan Bessonov > >> > > > -- Sincerely yours, Ivan Bessonov
