Hi Joe, It would be great to get them in JIRA b/c then they will appear here:
http://s.apache.org/gsoc2012tasks Be sure to "label" or "tag" them in JIRA with the tag: "gsoc2012" Cheers, Chris On Mar 9, 2012, at 6:31 AM, Joe White wrote: > Chris, > After giving it some thought, I think there are a certain number of basic > features that could conceivably be completed by a GSoC student. Would you > like them in Jira, or just in an email? > Joe > On Mar 5, 2012, at 5:24 PM, Mattmann, Chris A (388J) wrote: > >> Hey Joe, >> >> No worries, happy to have help and yes, happy to do it, a step at a time. >> Right now, the near term >> goal is to update the SIS website with a fresh design for our 0.2-incubating >> release. In fact, it's not >> a blocker in my mind and if I don't see any updates by the end of the week, >> I'll roll a 0.2-incubating release >> candidate with the fixes already present and save the website update for >> later. >> >> Then in 0.3-incubating, we've got a set of JIRA issues to work on that I >> think will add great value. I also >> tagged the SIS CLI as a Google Sumer of Code project. Do you think you could >> help cruft some JIRA issues >> and ideas for the first parts of polygon support and other features that you >> think would be completable in >> a summer by a GSoC student? Or any other SIS features that you think we >> should tackle next? >> >> Cheers, >> Chris >> >> On Mar 5, 2012, at 2:04 PM, Joe White wrote: >> >>> Trust me, Chris, I'm not arguing with the goals. It's just a lot of work. >>> Taken in pieces, it's not so bad, but in toto, it's a lot. I look forward >>> to helping out any way I can. There's only one way to eat an elephant… One >>> bite at a time. >>> >>> Joe >>> >>> On Mar 5, 2012, at 5:01 PM, Mattmann, Chris A (388J) wrote: >>> >>>> Hi Joe, >>>> >>>> Well that's the goal, for when Patrick and I started the project with Sean >>>> and Paul. I'd seen enough >>>> of the LGPL libraries out there for spatial and set out to grow up an ALv2 >>>> version, so that downstream >>>> users who expect the type of legal framework and quality that the ASF >>>> provides would find no surprises. >>>> I don't think those goals have changed in the least. >>>> >>>> I'm really supportive of what Ryan is doing with spatial4j. If there is >>>> any way that we can join the communities >>>> here, that would be awesome, I would just strongly advocate for not doing >>>> it in a way that includes any LGPL >>>> components, even optionally. >>>> >>>> Cheers, >>>> Chris >>>> >>>> On Mar 5, 2012, at 1:55 PM, Joe White wrote: >>>> >>>>> That definitely sounds like you are advocating writing a complete >>>>> projection engine, as well as geospatial raster and vector support with >>>>> AL licensing. That would be pretty ambitious, although not as bad when >>>>> taking a (much) longer view. >>>>> >>>>> Joe >>>>> >>>>> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote: >>>>> >>>>>> Chris, >>>>>> >>>>>> Optional support today means that it could potentially be deprecated in >>>>>> later releases, right? The same is true with including GDAL and Proj4. >>>>>> Both >>>>>> of them are very liberally licensed but have to buckle down because of >>>>>> EPSG >>>>>> support. Thoughts on that? >>>>>> >>>>>> Adam >>>>>> >>>>>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Greg, >>>>>>> >>>>>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote: >>>>>>> >>>>>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <[email protected]> >>>>>>> wrote: >>>>>>>>> http://www.apache.org/legal/resolved.html From there it looks like >>>>>>> LGPL is >>>>>>>>> a definite no no...Does this mean that it can't be included as an >>>>>>>>> option >>>>>>>>> when being built? >>>>>>>> >>>>>>>> I think it is a definite no no for "inclusion" in a project, meaning >>>>>>>> we can't include any LGPL wok in SIS. But I think we are talking about >>>>>>>> an optional dependency here. See the following blurb from the >>>>>>>> above-linked page: >>>>>>>> >>>>>>>> "Can Apache projects rely on components whose licensing affects the >>>>>>>> Apache product? >>>>>>>> Apache projects cannot distribute any such components. However, if the >>>>>>>> component is only needed for optional features, a project can provide >>>>>>>> the user with instructions on how to obtain and install the >>>>>>>> non-included work. Optional means that the component is not required >>>>>>>> for standard use of the product or for the product to achieve a >>>>>>>> desirable level of quality. The question to ask yourself in this >>>>>>>> situation is: >>>>>>>> >>>>>>>> Will the majority of users want to use my product without adding the >>>>>>>> optional components?" >>>>>>>> >>>>>>>> So, if I understand everything correctly, I don't see this as a >>>>>>>> roadblock. It is possible that I don't understand it correctly though >>>>>>>> :-) >>>>>>> >>>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write >>>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which >>>>>>> in my mind does *not* include any dependencies (even optional) on >>>>>>> LGPL components. >>>>>>> >>>>>>> As I understand it, in this case, JTS is providing the polygon support. >>>>>>> Polygon support is something we'd really like to support in SIS, so >>>>>>> to me, this dependency (though optional in e.g., Lucene) is a core >>>>>>> feature of SIS and something most of the eventual users of the system >>>>>>> would want. >>>>>>> >>>>>>> Cheers, >>>>>>> Chris >>>>>>> >>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>>> Chris Mattmann, Ph.D. >>>>>>> Senior Computer Scientist >>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>>>>> Office: 171-266B, Mailstop: 171-246 >>>>>>> Email: [email protected] >>>>>>> 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: [email protected] >>>> 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: [email protected] >> 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: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
