Hey Guys, I was talking with Greg, and I think I'm OK with org.apacheextras as the namespace.
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. I'm also of the mindset that the PMC should be the ones saying if they are OK with my oodt-pushpull-plugins Extras name and to me it should be fine if the PMC is OK with that. I can update the FAQ/guidelines to state that. Sound good? Cheers, Chris On Dec 29, 2011, at 9:32 PM, Mattmann, Chris A (388J) wrote: > Hi Nóirín, > > On Dec 29, 2011, at 9:21 PM, Nóirín Plunkett wrote: > >>> >>> Mark Struberg had another concrete suggestion: kudos to him for proposing >>> using >>> org.apachextras.oodt (implied). I could live with that, but don't believe I >>> (or anyone else) >>> should have to. >>> >> >> 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". > > 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. > >> >> 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. > > +1, precisely. > >> >> 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.) > > I've not once proposed to call the code for OODT CAS PushPull on Apache > Extras > 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 code. > I'm not > debating that. > > That doesn't however, mean that it's not strongly related to the > org.apache.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 are > many forks of Apache code, our real projects out there in people's Github > 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 thought > was > the strong closeness with Apache code by declaring that closeness with > the namespace. > > I've created an issue [1] and attached a patch to that issue with a > documentation > update that I feel implements my concrete suggestion #2. > > Cheers, > Chris > > [1] https://issues.apache.org/jira/browse/COMDEV-65 > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
