Hi Sergio. Kakao repo was not fork out of Apache in parallel. Just to be clear, there are many specific codes only for kakao's deployment, so the code has been different to Apache. what I meant earlier was we found bug and improvements through our deployment and open up issues to Apache Jira based on our finding. The actual code we pushed into Apache is actually different so I don't think there is any problem.
But I agree with your point on two issues. so we deprecated kakao repo from last week. it is reset to the commit we imported to Apache. also we updated our read me to redirect visitor into apache repo. so from now on, we can only works on Apache repo. Thanks for let us know about issues. Best Regards. Doyung Yoon On Mon, Mar 21, 2016 at 7:23 PM Sergio Fernández <[email protected]> wrote: > Ok, I think the message has got through. Thanks. > > But... > > On Fri, Mar 18, 2016 at 4:24 AM, DO YUNG YOON <[email protected]> wrote: > > > > There has been lots of code changes on kakao repo since initial code > import > > and I wanted apache repo to catch up this changes. > > Honestly I felt bad on initial code base since it is not organized at all > > and there has been critical bug, so I was in a hurry to conceal my bad > > code. > > In this catch up period, most of committers at Kakao already know what > each > > issues are about so there is no explanations and I think this was worst > > part. > > > > So, if I understood correctly, you're keeping your own fork our of Apache > in parallel?!? > > There are two issues with that: > > 1) Technically it's quite confusing then what the project target. > 2) Legally Kaka has done a code donation that is just valid for that > concrete code, not for any code the company has put there afterwards. > > So we need to sort this our ASAP! > > > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 > e: [email protected] > w: http://redlink.co >
