New KML Bug Tracking/Feature Requests Interface

[Roman N]

Hi everyone,

I've just finished setting up a new interface for submitting KML bugs
and feature requests (see links below).

If you were involved with a feature request or bug report on the old
KML Feature Requests or KML Bugs pages, please find it in the new
interface and 'Star' it by clicking the empty star icon to the left of
the issue. This will help us prioritize features and bugs as well as
allow you to receive notifications when your starred issues are
updated.

Also, if you think an feature or bug should be renamed or changed in
some way, let us know by responding to this thread.

***
KML Feature Requests and Bugs: http://code.google.com/p/kml-samples/issues/list

Shortcut to post a new Feature Request:
http://code.google.com/p/kml-samples/issues/entry?template=Feature%20Request

Shortcut to post a new Bug (please discuss at the relevant group
first):
http://code.google.com/p/kml-samples/issues/entry?template=Bug
***

- Roman

[barryhunter [KML Guru]]

Hi Roman,

this is certainly a welcome step! Perhaps could I just clarify the
expected reach of this tracker?

It seems to replace the two pages on this group, so that encompasses
the 1) KML file format itself, 2) the Google hosted documentation for
it,

But there other areas that KML is closely related (at least in a
Google Context), and they are mentioned occasionally on the above
issues, namely 3) Google Earth Client itself and 4) Google Maps
support for KML. This two do have their own groups, but neither have a
nice interface for reporting bugs (but do have sub-groups for feature
suggestions).

Lastly there is the Google Maps API, that does have its own tracker,
which as far as I know seems to work well.


So I guess my question is, should bugs and features for GEarth and
GMaps - when they are clearly related to KML and the file format* - be
posted in this new tracker, or should they be delt with via their
respective groups? (and ideally pushed to setup their own tracker)


(and taking it that the COM API really is unsupported)

* eg that fact that the overview map in GEarth is not showing is
clearly nothing to do with KML.


It's also worth noting (only just figured this out myself) the Earth
API, has its own interface at
http://code.google.com/p/earth-api-samples/issues/list

Barry

On Aug 15, 12:40 am, Roman N wrote:
> Hi everyone,
>
> I've just finished setting up a new interface for submitting KML bugs
> and feature requests (see links below).
>
> If you were involved with a feature request or bug report on the old
> KML Feature Requests or KML Bugs pages, please find it in the new
> interface and 'Star' it by clicking the empty star icon to the left of
> the issue. This will help us prioritize features and bugs as well as
> allow you to receive notifications when your starred issues are
> updated.
>
> Also, if you think an feature or bug should be renamed or changed in
> some way, let us know by responding to this thread.
>
> ***
> KML Feature Requests and Bugs:http://code.google.com/p/kml-samples/issues/list
>

> Shortcut to post a new Feature Request:http://code.google.com/p/kml-samples/issues/entry?template=Feature%20...

[Roman N]

Barry,

Great question! Bugs and feature requests related to Google Earth's
(client app. and API) and Google Maps' (maps.google.com and Maps API)
implementations of KML can definitely go in the new issue tracker.

Earth bugs unrelated to KML should still be posted at the Earth group
thread at http://groups.google.com/group/earth-free/browse_thread/thread/7983db1784017a10.

- Roman

On Aug 16, 8:23 am, barryhunter [KML Guru] wrote:
> Hi Roman,
>
> this is certainly a welcome step! Perhaps could I just clarify the
> expected reach of this tracker?
>
> It seems to replace the two pages on this group, so that encompasses
> the 1) KML file format itself, 2) the Google hosted documentation for
> it,
>
> But there other areas that KML is closely related (at least in a
> Google Context), and they are mentioned occasionally on the above
> issues, namely 3) Google Earth Client itself and 4) Google Maps
> support for KML. This two do have their own groups, but neither have a
> nice interface for reporting bugs (but do have sub-groups for feature
> suggestions).
>
> Lastly there is the Google Maps API, that does have its own tracker,
> which as far as I know seems to work well.
>
> So I guess my question is, should bugs and features for GEarth and
> GMaps - when they are clearly related to KML and the file format* - be
> posted in this new tracker, or should they be delt with via their
> respective groups? (and ideally pushed to setup their own tracker)
>
> (and taking it that the COM API really is unsupported)
>
> * eg that fact that the overview map in GEarth is not showing is
> clearly nothing to do with KML.
>
> It's also worth noting (only just figured this out myself) the Earth

> API, has its own interface athttp://code.google.com/p/earth-api-samples/issues/list