Hi Jody,
I'd say, since we never had a supported mongodb store, I'd go for replacing
it instead
of making a "ng" of something very few people used so far anyways (my 2
cents).
Our plan was actually to patch the existing one to make it a
contentdatastore based one
anyways.
Cheers
Andrea
On Wed, J
Clarification: Thanks for offering, but Tyler or myself will need to move
the code over (as boundless representatives we need to fix up the headers
and stuff)
Question: Did you have any feedback on if we should request to replace the
contents of gt-mongodb or create a gt-monodb-ng ?
(Your answer
Thanks Stefano:
We are aware of your timeframe and apologize for the delay on our end.
I am going to talk with Tyler first and then one or the other of us will
send a request for community module shortly.
I hope your contract could be used to review the codebase and improve the
test coverage. Bu
Sorry, there was a spelling error in my previous e-mail: I meant "we
(GeoSolutions) have been contRacted", not just "contacted" :-)
Da: "stefano.costa" [email protected]
A: "Geotools-Devel list" [email protected]
Cc:
Data: Wed, 10 Jun 2015 10:50:48 +0200
Oggetto
Hello,
we (GeoSolutions) have been contacted by a customer who is having issues
with the community MongoDB plugin for geoserver to improve it in terms
of features, performance and alignment with the GeoTools latest changes.
I would be happy to become the module maintainer as well.
This morning I r
