incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (3980)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Podling name search - early or late?
Date Fri, 27 May 2016 22:37:52 GMT
I’ve always done the podling name search right away. I’m not
sure where that comment came from from Shane - my experience
has been the opposite.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++










On 5/27/16, 3:35 PM, "Stian Soiland-Reyes" <stain@apache.org> wrote:

>I think the point is that name search is not a blocker for doing incubator
>releases - it can be time consuming and there are many other "bureaucratic"
>steps to get through in the beginning like IP clearance and license
>checking.
>
>For brand new projects, name search can therefore be delayed - their name
>is less important as their community will be fully within the incubator to
>start with.
>
>However I think for established distributed projects moving to the
>incubator it is more important to sort name earlier - it can be disruptive
>enough for the community with the change of infrastructure and the
>formalities, so you may might not want to confuse them again with a new
>name many months later - effectively changing all infrastructure again.
>
>Some podlings found their name could be tricky trademark wise and had to
>change, but getting together and deciding a new name can even be a good
>thing, as it breaks any legacy corporate ownership and builds a new
>collective identity.
>On 27 May 2016 7:20 p.m., "Balaji Ganesan" <bganesan@apache.org> wrote:
>
>> 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 <jghoman@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-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>>
Mime
View raw message