Podling namesearch is essential step that needs to be completed before the podling graduates. There is no specific guidance, as far as i know, on what stage of podling you should do it.
That said, it would be better to do this early enough and get approval on the name. If there is any reason to change name, due to a conflict, it is better to do it before releases are made and community starts building around. Name change is always a pain. On Fri, May 27, 2016 at 11:07 AM, Jakob Homan <jgho...@gmail.com> wrote: > We were getting ready to start the PNS for Airflow when I came across > this comment from Shane in regards to Kudu: > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-93 > "This looks like a pretty good set of search data, but we usually > don't work on resolving PODLINGNAMESEARCHES until a podling is clearly > established, has a release, community is building, etc." > > This is surprising to me and different than the last time I was > involved in an incubating project. Is this correct? > > It seems more useful to determine if a name can be used early in the > incubation, before releases, talks, thousands of lines code, package > names, emotional attachments, etc. In the event that a podling fails, > nothing is lost by okaying the name early, assuming we don't attempt > to trademark (which we haven't been for non-TLPs, I believe). > > Any thoughts? Any reason not to start doing the PNS for Airflow now? > > Thanks, > Jakob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
