Andrea:
Let me respond to all of your comments.
You wrote: "It was not clear to me that we _had_ to choose a license.
It was a suggestion from
the code sprint team that did the checks, but Jody told us it is
sufficient to locate
any potential issue, not to fix it. Jody and Landon, please clarify
and give us a
definitive direction?"
I'm not sure if this is required. I don't think it is, but I will
double check with the incubation committee. If it is not required,
then I'll I need to know is that you guys don't want to hassle with it
at this point in time.
Having said that, I think anytime you can clear up licensing issues,
its a good thing. :]
You wrote: "Done for the most part, the only one data that we don't
have confirmation about is
States, asked around, while people believe it's Census data we have no direct
confirmation. Chris, I believe the dataset was added to GeoServer back when you
were actively coding against the project, any more precise memory?
Another avenue that we can pursue is look into GeoTools, as far as I remember
States comes from the GeoTools test data, that was already vetted when GeoTools
itself graduated.... which is here:
https://github.com/geotools/geotools/blob/master/modules/library/sample-data/src/site/apt/review.apt
It says the origin of that "statepop" dataset is unknown... a possible
hint that vetting is all that
is required, since GeoTools graduated with that assesment?"
So GeoTools shares the same datasets? If that is the case, this
shouldn't be a big deal. Let me know. If the datasets aren't shared by
GeoTools, we may just need to note that the source and licensing of
the sample data is unknown.
Is the sample data deeply integrated into project documentaiton and
tutorials, and therefore hard to replace?
You wrote: "This one is completely new to me, or at least, I can't
remember about it off the top of my head.
We do have code contribution procedures already in place, what was
found that is not ok in them?"
Code contribution procedures was just one of the items on my
checklist. I think the Incubation Committee just wants to know that
some procedures are in place. I'll review the links and then document
(somewhere) that the project has completed that item of the incubation
checklist.
I appreciate your patience as I try to tie up these loose ends. I'm
learning the incubation process with you.
Landon
On Fri, Dec 28, 2012 at 1:22 PM, Andrea Aime
<andrea.aime@anonymised.com> wrote:
It was not clear to me that we _had_ to choose a license. It was a
suggestion from
the code sprint team that did the checks, but Jody told us it is sufficient
to locate
any potential issue, not to fix it. Jody and Landon, please clarify and give
us a
definitive direction?
Regardless, this one requires a GSIP, so it cannot be addressed until we
have again
all hands on deck, say January 7th?