Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27F939548 for ; Fri, 30 Dec 2011 07:09:40 +0000 (UTC) Received: (qmail 44565 invoked by uid 500); 30 Dec 2011 07:09:39 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 44354 invoked by uid 500); 30 Dec 2011 07:09:29 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 44346 invoked by uid 99); 30 Dec 2011 07:09:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Dec 2011 07:09:25 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [128.149.139.106] (HELO mail.jpl.nasa.gov) (128.149.139.106) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Dec 2011 07:09:17 +0000 Received: from mail.jpl.nasa.gov (altvirehtstap02.jpl.nasa.gov [128.149.137.73]) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBU78tME025256 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 29 Dec 2011 23:08:55 -0800 Received: from ALTPHYEMBEVSP20.RES.AD.JPL ([128.149.137.83]) by ALTVIREHTSTAP02.RES.AD.JPL ([128.149.137.73]) with mapi; Thu, 29 Dec 2011 23:08:48 -0800 From: "Mattmann, Chris A (388J)" To: "dev@community.apache.org" CC: Greg Stein Date: Thu, 29 Dec 2011 23:11:22 -0800 Subject: Re: Apache Extras Question Thread-Topic: Apache Extras Question Thread-Index: AczGweABw5eRWzyTQ9y0w/J+MA5QjA== Message-ID: <2C875690-4C6C-48AF-AD30-3F7DE61862E7@jpl.nasa.gov> References: <15F56445-F5E3-4EBB-BAE4-71A7B973F294@jpl.nasa.gov> <8D8C4302-AD75-4AD6-990A-DAAB6098C9E2@jpl.nasa.gov> <002501ccc666$5a3c8020$0eb58060$@acm.org> <003501ccc66c$caa94400$5ffbcc00$@acm.org> <10F7EB13-FA75-4F5B-B7BC-F0445EAE99EB@jpl.nasa.gov> <002f01ccc696$32fff110$98ffd330$@acm.org> <31EB91E3-CE8D-4E74-9F52-0DCC6BF0624D@jpl.nasa.gov> <290EA0D0-4E7D-42A8-85F3-D40E80AC2FDD@jpl.nasa.gov> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Source-IP: altvirehtstap02.jpl.nasa.gov [128.149.137.73] X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized X-Virus-Checked: Checked by ClamAV on apache.org BTW, I just updated the code at [1] to use org.apacheextras and also updated the description of the project to make it clear that it's not Apach= e releases nor is it Apache code.=20 Cheers, Chris [1] http://code.google.com/a/apache-extras.org/p/oodt-pushpull-plugins/ On Dec 29, 2011, at 10:30 PM, Mattmann, Chris A (388J) wrote: > Hey Guys, >=20 > I was talking with Greg, and I think I'm OK with org.apacheextras as > the namespace.=20 >=20 > It sounds like Noirin thought that was cool and so did Mark S. > Are folks here on ComDev cool with that namespace for our Extras > projects? If so, I'll update my COMDEV-65 patch with docs stating that > and document it and move forward.=20 >=20 > I'm also of the mindset that the PMC should be the ones saying=20 > if they are OK with my oodt-pushpull-plugins Extras name and=20 > to me it should be fine if the PMC is OK with that. I can update > the FAQ/guidelines to state that.=20 >=20 > Sound good? >=20 > Cheers, > Chris >=20 > On Dec 29, 2011, at 9:32 PM, Mattmann, Chris A (388J) wrote: >=20 >> Hi N=F3ir=EDn, >>=20 >> On Dec 29, 2011, at 9:21 PM, N=F3ir=EDn Plunkett wrote: >>=20 >>>>=20 >>>> Mark Struberg had another concrete suggestion: kudos to him for propos= ing using >>>> org.apachextras.oodt (implied). I could live with that, but don't beli= eve I (or anyone else) >>>> should have to. >>>>=20 >>>=20 >>> I strongly prefer Mark's suggestion, and I'd like to hear more about >>> why you think you shouldn't have to "live with it". >>=20 >> Because I suggested 2 other concrete alternatives as well and I prefer >> those. I also created an issue [1] and attached a patch there that >> implements my suggested update to the FAQ/Guidelines. >>=20 >>>=20 >>> You question what we are doing "if our own PMCs can't start up a >>> project on Apache Extras and use org.apache.* as a namespace", and I >>> agree that we may not be clear on exactly what the advantage of Apache >>> Extras is over Google Code, GitHub, or wherever else. >>=20 >> +1, precisely. >>=20 >>>=20 >>> But our own PMCs can't start up a project on Apache Extras (or >>> anywhere else) and call it an official Apache release either, and to >>> me, that's the line that decides (socially) what can or can't use the >>> org.apache.* namespace. (And, afaict, this *is* a social/policy >>> question, not a legal or technical one.) >>=20 >> I've not once proposed to call the code for OODT CAS PushPull on Apache = Extras=20 >> an Apache release. In fact, pretty much the whole time, I've stated >> that it's _not_ an Apache release and that it's _not_ official Apache co= de. I'm not >> debating that. >>=20 >> That doesn't however, mean that it's not strongly related to the org.apa= che.oodt >> namespace, and doesn't in my mind mean that we shouldn't be able to use = it >> in a project on extras. Christian G. really summed up my point. There ar= e >> many forks of Apache code, our real projects out there in people's Githu= b >> accounts -- are we really policing them for using the namespace? I'm not= proposing >> anything nefarious here. I'm proposing to leverage Extras for what I tho= ught was >> the strong closeness with Apache code by declaring that closeness with >> the namespace. >>=20 >> I've created an issue [1] and attached a patch to that issue with a docu= mentation >> update that I feel implements my concrete suggestion #2.=20 >>=20 >> Cheers, >> Chris >>=20 >> [1] https://issues.apache.org/jira/browse/COMDEV-65 >>=20 >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: chris.a.mattmann@nasa.gov >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>=20 >=20 >=20 > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: chris.a.mattmann@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >=20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattmann@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++