Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of phil.steitz@gmail.com
 designates 209.85.192.177 as permitted sender)
Message-ID: <5495FA1F.7040705@gmail.com>
Date: Sat, 20 Dec 2014 15:37:19 -0700
From: Phil Steitz <phil.steitz@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: Commons RDF
References: <54935148.3010409@apache.org>
	<CALvhUEW94RRj6-Tr3U-5ppXO8EbM1a20A6ARQcO+S1Spi0FayQ@mail.gmail.com>
	<549467CD.8080600@apache.org>
 <CAB917RKxa2Afew1Uwk+1PAsLrdK+N==SUPPv-ZFSNqAS_mqVjA@mail.gmail.com>
 <54955D50.5030102@apache.org> <5495B7AB.7000702@gmail.com>
 <5495C159.4010609@apache.org>
In-Reply-To: <5495C159.4010609@apache.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 12/20/14 11:35 AM, Andy Seaborne wrote:
> Phil Steitz wrote:
>>  The question we always ask
>> about new component ideas is can we grow and sustain a community
>> around them.
>
> Couldn't agree more.  As you may have noticed, there is a
> community and it's been arguing for years!
>
> >> >We came here originally.  We found that there is a Commons way of
>>> >doing things.  Collaborating with those external people was not
>>> >going to work within the confines of Apache Commons - nothing
>>> >wrong with that, Commons isn't aiming to be a sole place of
>>> >collaboration anywhere.
>> How exactly did you come to that conclusion?  The only things I see
>> in the archives are*ASF*  "ways of doing things" - using ASF SCM
>> repos - now Git is available, discussion on mailing lists, etc.
>
> There was a stated use of this list [1].
>
> Our goal/hope/aspiration is collaboration inside and outside Apache.
>
> Asking people from other places to come over to this list is a
> significant barrier.

Really?  That sounds kind of silly to me, frankly.  I guess if what
you are saying is that having a project mailing list and having
discussion there is a show-stopper, then, yes, you are right the ASF
is not the right place to do it. =20
>
> I'm glad to see git is now available.
>
>> Great, but irrelevant to the question of whether there is community
>> interest in a Commons RDF component (I mean an Apache Commons
>> component named commons-rdf.  In retrospect, we should have
>> anticipated the name disambiguation problem.  At this point, users
>> may end up confused if we move forward in Commons and the community
>> does not end up combining.)
>
> How does Commons normally handle potential name clash matters? or
> maybe it has not occurred before?

It has not happened before.  At the ASF level, projects sometimes
end up choosing cutesy names to work around trademark issues.=20
Unfortunately, we like to avoid the cutesy names in Commons,
preferring simple names that describe the components.  The package
names are different, so this may not be that bad.

Phil

>
>     Andy
>
> [1]
> http://markmail.org/message/jfl5nm6nyfj3zxgd
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org