Jan Jezek wrote:
> Hi,
> I’m the Summer of Code participant. My name is Jan Jezek and I’m working on
> project focused on improvement for coordinate systems transformations. The
> project is mentored by Jesse Eicher.
> The new tools to be implemented are:
>
Welcome,
As Jesse may of informed y
Jody Garnett a écrit :
> This time the GO-1 module is up for a review.txt file, thought I would
> use the occasion to ask after your practice of listing the OGC
> specifications in header files. If this is something that is needed it
> would be good to apply it to sections of the api module wher
Hello Jody
The review of epsg-access and epsg-postgresql look fine and I see nothing to
add.
One note about the readme.txt file in plugin/epsg-hsql: the instructions copied
from the javadoc are
actually for module maintainers; it explain how to upgrate the plugin for
latest EPSG database
rel
Consider changing the directory structure to comply with Maven 2 standard
-
Key: GEOT-887
URL: http://jira.codehaus.org/browse/GEOT-887
Project: GeoTools
Type: Wish
Components: admin
Rep
Andrea Aime wrote:
>If you want to try out jalopy with the current settings on a module, go
>into it and type:
>mvn -Pjalopy jalopy:format
>
>The configuration file is located in the maven/build-configs module (so
>that it can be shared). Note that I disabled jalopy javadoc comment reformat
>b
Hi,
I’m the Summer of Code participant. My name is Jan Jezek and I’m working on
project focused on improvement for coordinate systems transformations. The
project is mentored by Jesse Eicher.
The new tools to be implemented are:
-Transformations parameters calculator – the tool for calculating th
During this weeks meeting we were unable to take action due to a lack of
70% votes for Simboss's
nomination to the PMC. We also received a nomination for Andrea to
resume PMC duties.
So the time has come to change the guard according to the roles and
responsibilities laid out in the
developers
So in today's meeting the issue regarding inactive PMC members was
brought up. The main issue is that having a lot of inactive PMC members
often prevents us from achieving our 70% majority on votes, such as
inviting simboss to the PMC (only four out of nine PMC members responded).
So I have col
Remove Deprecated Code from GeoTools for 2.2 Release
Key: GEOT-886
URL: http://jira.codehaus.org/browse/GEOT-886
Project: GeoTools
Type: Improvement
Versions: 2.2-RC3
Reporter: Richard Gould
Fix F
Update (or purge) user guide and tutorials for 2.2 Release
--
Key: GEOT-885
URL: http://jira.codehaus.org/browse/GEOT-885
Project: GeoTools
Type: Improvement
Components: doc
Versions: 2.2-RC3
Re
Jody Garnett wrote:
> Well I am module maintainer on this one,
>
> And I suppose I need to answer the same distribution and redistribution
> questions as Martin does with the epsg-hsql plugin. I belive my
> situation is slight different as the the original source was PostGIS and
> some hacking
I can't say I'm super impressed with the current state of the
FIDMapper classes. I'm not an expert but your suggestions make sense
to me.
Jesse
On 10-Jul-06, at 7:43 AM, Michael Brasser wrote:
> Hi David,
>
> Just wanted to mention that there was some discussion on the list
> about a month
Hi David,
Just wanted to mention that there was some discussion on the list
about a month ago about refactoring AutoIncrementFIDMapper. It
currently uses "order by" to return a value, but this is problematic
(I've included a problem case from the earlier discussion below). Not
sure if it w
Jody Garnett wrote:
> Yeah it is more the need to bundle that was annoying me, means we need a
> deployment section in our library asking people to bundle that license
> etc a real pain. Would rather ask people to download the driver
> themselves (and thus they can read the instructions fro
Thanks Julian ;-) And twice even for the prompt response.
I will leave the (C) 2004-2005, Julian J. Ray, and then add the GeoTools
(C) for 2006 I love to give credit, but I also want to know we are
cool making decisions on behalf of your module.
Jody
Jody
Julian Ray wrote:
> Hi Jody,
>
> Y
David Adler wrote:
> Hi Jody, what a job to look through the copyright statements!
The joys of being a PMC ;-) It has been a couple months and the module
maintainers are not making leaps
of progress, and I am not sure I want to show my head at any OSGEO
function while we are still mired.
> I wil
Martin Desruisseaux wrote:
> Martin Desruisseaux a écrit :
>> The license is not about the hsql driver (as far as I remember),
>> but rather about the EPSG database itself.
>
> Oups! Sorry. Reading again the license file (and the your review.txt
> file that I can now read), I see the issue you poi
Martin Desruisseaux wrote:
> Jody Garnett a écrit :
>> I would ask you to please read the review.txt I have placed into your
>> module. The hsql plugin may have some license issues, based on a
>> mysterious license included with the epsg-hsql module (that I can
>> only assume is needed for dist
Hi Jody, what a job to look through the copyright statements!
I will see what I can find out from the IBM IP dept. At the time this code
was developed, I thought the copyright statement was ok although I'm not
sure I can find the history on this.
In poking around, there seem to be anomalies in
Martin Desruisseaux a écrit :
> The license is not about the hsql driver (as far as I remember),
> but rather about the EPSG database itself.
Oups! Sorry. Reading again the license file (and the your review.txt file that
I can now read), I
see the issue you point out. Will try to come back with
Jody Garnett a écrit :
> I would ask you to please read the review.txt I have placed into your
> module. The hsql plugin may have some license issues, based
> on a mysterious license included with the epsg-hsql module (that I can
> only assume is needed for distribution of the hsql jdbc driver).
Hi Amr, remember me?
The GeoTools library is undertaking an IP reivew as part of our
participation in the OSGEO incubation process.
I would ask you to please read the review.txt I have placed into your
module. The hsql plugin may have some license issues, based
on a mysterious license included w
Hi Andrea, another module with your name on it ;-)
Your initial commit dates from 2003, but all current headers indicate
2005 ... good old subversion. The directory used to include test-data,
and no longer does. I take it no small smaples of test data can be found
- it would be nice to ensure
On Jun 22, 2006, at 12:01 PM, Bryce L Nordgren wrote:
>
> *snip*
> Patrick, close your eyes.
> Jody:
> public static final String SLAVE_LABOR = "Grad student";
> public static final String SWEAT_SHOP = "University";
> public String PROJECT_WORKER = SLAVE_LABOR + " in " + SWEAT_SHOP ;
> Ok, you
Hi Adrian, I assume you had a bit of fun with the navigation bar? I was
hopeing we could work on your "new users guide" and then just place it
on the navigation bar when ready. If you want to start off public we can
simply remove the links to the old content for now.
I really do need to keep th
Andrea Aime (SATA) wrote:
>> Until we can get Jalopy into common use I figured these may help, at
>> the very least it will help get more header files into the geotools
>> codebase (something I am finding missing during the IP review).
> Don't follow you?
There are two files, one for formatting (
Adrian Custer wrote:
> Hey all,
>
> I made a total hash of the web site by trying to move pages around and
> having Confluence refuse to move children along with the pages. Is
> there any chance one of you could restore the web site to yesterday's
> state? That should clean up the mess I made (and
Andrea Aime wrote:
> Hi all,
> I've managed to get the mojo project provide a public snapshot build of
> the jalopy plugin, and I've then committed changes to the main pom so that
> jalopy can be used if you specify a special profile.
>
Amusing just as I gave up hope and committed eclipse form
Adrian Custer wrote:
> Hey all,
>
>
> I'm wondering about the status of the 2.2 release. It appears there is
> an imminent release of 2.2-RC4. Beyond that, what is required to release
> 2.2? Are the tasks in:
> http://docs.codehaus.org/display/GEOTOOLS/Tasks+for+2.2.0+release
> still valid?
>
Hi Justin,
It has been a couple months since I asked for a review, time waits for
no man - can you please read over the review.txt file I have added to
your module.
I did turn up a couple interesting things - say in StringUtils.java
> Copyright (c) 2003, Ministry of Sustainable Resource Manag
Hi again Martin,
This time the GO-1 module is up for a review.txt file, thought I would
use the occasion to ask after your practice of listing the OGC
specifications in header files. If this is something that is needed it
would be good to apply it to sections of the api module where filter,
an
Hi again David,
No surprises, one missing header etc.. review.txt file has details.
Jody Garnett
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated techn
Hi Bruce,
I am trying to gather up all the IP Review information that has gone
past us on the email list into a series of review.txt files associated
with each module.
And guess what? Your module still confuses me ...
> /*
> * (c) 2004 Mike Nidel
> *
> * Take, Modify, Distribute freely
> * B
Hi Richard,
Is it possible to filter the geomedia module from the release process,
while still having it built by the various cruise control systems?
I have no problem with it being built, and the license is clearly LGPL,
but until I am clear on copyright I do not think the geotools PMC should
Hi Julian, you are listed as the module maintainer of the geomedia plugin.
As you may or may not be aware the GeoTools project is wandering slowly
through an incubation process to facilitate co-operation with the OSGEO
Foundation. One of the first tasks is an IP review, I have not heard
about t
Well I am module maintainer on this one,
And I suppose I need to answer the same distribution and redistribution
questions as Martin does with the epsg-hsql plugin. I belive my
situation is slight different as the the original source was PostGIS and
some hacking by Paul Ramsey with perl. Furthe
Hi again Martin,
No surprises this time around, no data included only instructions etc...
file available as review.txt.
Jody
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quic
Hi again Martin,
As a frequent module maintainer you are going to get a couple of these
messages apparently. The epsg-hsql plugin is troubling as it contains a
LICENSE.TXT entry requiring us to adjust the documentation include with
our binary release. Please read the review.txt for a couple sug
Hi Martin,
I know you sent some email out concerning the IP health of the various
epsg authorities, so I am walking on ground you already covered. You
will find a review.txt file in the epsg-access module where I have
recorded comments, I have also updated the header to reflect the current
yea
Hi Andrea,
I noticed you placed a checkstyle.xml file into trunk/gt, I have chased
it up with two eclipse files for formatting and code templates. These
are the files I use currently, based on the sun standard you were
talking about using with Jalopy as I recall (sun standards with extra
width
No surprises, results.txt available. I would like to revise this
tutorial to encompass FeatureList and so on... it sounds like data store
quality will be a subject for uDig 1.1 so maybe I will get a chance. If
anyone is interested in taking this on I am am more then will to answer
questions if
Hi Andrea,
This time I am the module maintainer, mostly cause I want to set up
Adrian Custer with good examples. But the majority of code seems to be
stuff you have written - possible as far back as 2002. The IP review
checks out okay, but I would like to confirm the date for such things as
t
I have included a review.txt file in your DB2 module, I noticed that all
headers are marked as (C) Copyright IBM Corporation, 2005. All rights
reserved.
Is this code something you wish the geotools community to take
responsibility for distributing? "All rights reserved" may prove
interesting f
Hi James and Cory,
You are the only developers listed on the brewer module, does one of you
want to step forward as the module maintainer? Please update the pom.xml
file
The module is one of the few modules in geotools that is not under a
pure LGPL license, the data files reference an Apac
44 matches
Mail list logo
