Re: Podling names pre code transfer

2019-10-17 Thread Justin Mclean
Hi, > Hmm..., I thought that all podlings should call themself Apache XXX > (Incubating) before graduation. Am I being wrong? You not wrong. During incubation podlings should call themselves Apache XXX, but only after then have donated code.Currently, in practice, its generally been done once

回复:Re: Podling names pre code transfer

2019-10-17 Thread Liu Ted
Hmm..., I thought that all podlings should call themself Apache XXX (Incubating) before graduation. Am I being wrong? Best regards, Ted Liu, ASF Member 2019 年 10 月 17 日周四 23:05,York Shen 写道: Agreed, remove "or pre-code-drop process” would be much more clear. FYI: I always have the wrong

Re: Podling names pre code transfer

2019-10-17 Thread York Shen
Agreed, remove "or pre-code-drop process” would be much more clear. FYI: I always have the wrong impression that podlings are encouraged to call themself Apache Incubator-PodlingName before they graduates. Now, a lesson is learned for me, thanks. Best Regards, York Shen 申远 > 2019年10月17日 22:42

Re: Podling names pre code transfer

2019-10-17 Thread John D. Ament
Hi, I've always read this as "some code" rather than "all code" since "all code" is a completely unbounded endpoint which no project could ever reach until it retires. So as long as some code is in our repos, they must be called "Apache " My $0.02 John On Thu, Oct 17, 2019 at 8:36 AM Justin Mc

Podling names pre code transfer

2019-10-17 Thread Justin Mclean
Hi, I was reviewing this page [1] and noticed that what is current states is not what happens in practice. Podlings are encouraged to called themselves "Apache XXX" fairly early on and it takes some podlings a while to get all the code submitted the ASF repositories. In particular some projects