-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

my 2 cents :

I agree with Reza. It seems to me the code can be polished,
re-polished and tweaked, the issue is, as it was : the data.
The evolution there is that there appears to be general consensus on
the fact that DeviceMap will have to maintain its own data and that
the it's main source is the OpenDDR contributions.

The fact that I have the 'infrastructure' [code, db ,site, not the
bandwidth] for such maintenance is not really relevant : it's .Net and
I continue to think that for me to 'publish' such a thing, while
actively involved in getting DeviceMap going, well...that's just not
cricket, is it.
And like Reza, I remain committed to the DeviceMap project.
Unlike Reza I have more time I can commit, so I can get the .Net
'clone' ready with the "paperwork" etc.

With regard to the data maintenance infrastructure, I have data,
models and a list of does-and-donts [stuff I ran into] I'll gladly share.

esjr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTrbCbAAoJEOxywXcFLKYcI3UH/3zzABExVBHrHbMRk/nOQv8A
3lL+XaIoQehCcMOXeQe1KCxRT7rjxPreFEN4wmi9DKRC8DG1p/ph2wsqzTsApxT8
B3IvXanvKTjKzlTDfCg/cOxYPdYOYXz6wfJLLqGyLOJA6FJkQ6raqcwY8ATNpdYU
ln8D0f/IMgiIAn/SfEIunEg5CDq4WE3VyArbXiHltbmcFNwy1AxnFPny7JgaFicp
KS8zywHZ4KPgpX1VZchsGttMI96GRfRnoTn+5mky621MAhUTOS0tvm4HKBS+vOwu
9A8FVX2D3GnmfjEnXcIUGRjBMMpYpdVxd3oYyLONTGz8POvtqOsFIa8xBEYIJP0=
=PZx2
-----END PGP SIGNATURE-----

Reply via email to