Christoph :
I do not want to spend time writing a bug tracker that is then
rejected because of the way it stores the bug reports.
If you propose a tag/value storage, there is no reason someone would
reject it.
Xav
___
talk mailing list
On Thu, Dec 4, 2008 at 12:10 AM, Christoph Böhme [EMAIL PROTECTED] wrote:
At the moment I am trying to figure out if bug reports reports can be
stored directly in the osm database using standard nodes and tags.
Please, please don't take or advocate this approach. The OSM core
tables should,
Andy Allan [EMAIL PROTECTED] schrieb:
On Thu, Dec 4, 2008 at 12:10 AM, Christoph Böhme [EMAIL PROTECTED]
wrote:
At the moment I am trying to figure out if bug reports reports can
be stored directly in the osm database using standard nodes and
tags.
Please, please don't take or
Richard Fairhurst wrote:
Even when we do use something that wasn't invented here, the best fits are
those which were at least partially developed with OSM in mind - from Mapnik
to the ODbL. TBH I wouldn't have even considered this application as a
bug-tracker had the comparison not been made
Gervase Markham wrote:
Inventing your own stuff makes perfect sense in the area of your
core competency.
Agreed absolutely.
[...]
I agree that where the bug tracker starts being used for mapping-
related things, then the boundaries start to blur. But I'd still suggest
that the only
On 03/12/2008 18:47, Richard Fairhurst wrote:
Gervase Markham wrote:
Inventing your own stuff makes perfect sense in the area of your
core competency.
Agreed absolutely.
[...]
I agree that where the bug tracker starts being used for mapping-
related things, then the boundaries start to
I agree that where the bug tracker starts being used for mapping-
related things, then the boundaries start to blur. But I'd still suggest
that the only difference between an OSB ticket and a software
bug ticket is the method of submission. After that, it's triaged
and managed in the
David Earl [EMAIL PROTECTED] writes:
On 03/12/2008 18:47, Richard Fairhurst wrote:
- the bugtracker will not be the core client for managing the bug, the
usual OSM clients will (Potlatch/JOSM/Merkaartor)
I don't think so, with one exception: you'd like to be able to view the
map from the
Hi!
Donald Allwright [EMAIL PROTECTED] schrieb:
Apart from this, the lifecycle of a bug is essentially the same in
each case so the same tool could be used, but with a different front
end.
You are probably right about the lifecycle. When I wrote the proposal
for an improved bugtracker I
Marc Schütz wrote:
Bugzilla as a backend would certainly be nice, but as a frontend it is
obviously inappropriate. I don't know whether Bugzilla supports alternate
frontends; if so, it could be worthwhile building one that fits our needs.
Modern Bugzillas have an XML-RPC interface, and also
Richard Fairhurst wrote:
I'm not sure why the need to reuse existing software at all. Bugtracking is
the sort of thing you expect to find in 'Rails For Dummies' as My First
Rails App - if you’ve got a decent framework it’s pretty elementary.
As someone who's spent the last nine years working
On 30/11/2008 13:06, Gervase Markham wrote:
Richard Fairhurst wrote:
I'm not sure why the need to reuse existing software at all. Bugtracking is
the sort of thing you expect to find in 'Rails For Dummies' as My First
Rails App - if you’ve got a decent framework it’s pretty elementary.
As
Mikel wrote:
I'd suggest bypassing Trac and looking into RedMine
http://www.redmine.org/
I'm not sure why the need to reuse existing software at all. Bugtracking is
the sort of thing you expect to find in 'Rails For Dummies' as My First
Rails App - if you’ve got a decent framework it’s pretty
Richard Fairhurst wrote:
No need to have geometry drawing, which is the hard bit to code. If you want
to draw ways, you need to make a sufficient commitment to the project to
learn an editor, just as thousands have already done. And if you’ve
progressed through this entry-level editor, you’re
2008/11/27 Lambertus [EMAIL PROTECTED]:
Richard Fairhurst wrote:
No need to have geometry drawing, which is the hard bit to code. If you want
to draw ways, you need to make a sufficient commitment to the project to
learn an editor, just as thousands have already done. And if you've
progressed
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
Unfortunatly this project is quity poor in features like:
- email notification
- duplicate handling
- user handling
- attachements (pictures, links, etc...)
- search
- filters
- reports, charts statistics
etc.
Bug trackers like
On 26/11/2008 16:56, Steffen Vogel wrote:
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
Unfortunatly this project is quity poor in features like:
- email notification
- duplicate handling
- user handling
- attachements (pictures, links, etc...)
- search
- filters
-
On Wed, Nov 26, 2008 at 11:20 AM, David Earl [EMAIL PROTECTED]wrote:
Just a thought - there isn't already a change tracking system for
geographical data out there is there, or an add on or plugin for an
existing system?
No, I don't think there's ever been a use case for what we're talking
Am Mittwoch 26 November 2008 17:56:15 schrieb Steffen Vogel:
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
Unfortunatly this project is quity poor in features like:
- email notification
- duplicate handling
- user handling
- attachements (pictures, links, etc...)
-
On 26/11/2008 17:27, Ian Dees wrote:
On Wed, Nov 26, 2008 at 11:20 AM, David Earl [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Just a thought - there isn't already a change tracking system for
geographical data out there is there, or an add on or plugin for an
existing
Marc Schütz schrieb:
Am Mittwoch 26 November 2008 17:56:15 schrieb Steffen Vogel:
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
Unfortunatly this project is quity poor in features like:
- email notification
- duplicate handling
- user handling
- attachements
On Wed, Nov 26, 2008 at 9:38 AM, John07 [EMAIL PROTECTED] wrote:
Marc Schütz schrieb:
Am Mittwoch 26 November 2008 17:56:15 schrieb Steffen Vogel:
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
Unfortunatly this project is quity poor in features like:
- email
Karl Newman schrieb:
On Wed, Nov 26, 2008 at 9:38 AM, John07 [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Marc Schütz schrieb:
Am Mittwoch 26 November 2008 17:56:15 schrieb Steffen Vogel:
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
I'd suggest bypassing Trac and looking into RedMine http://www.redmine.org/
Trac is wonderful, but convoluted. RedMine is built in Rails and quite easy to
modify.
___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
Hi!
Steffen Vogel [EMAIL PROTECTED] schrieb:
As a user and mapper of OpenStreetMap, I often use OpenStreetBugs.
Unfortunatly this project is quity poor in features like:
- email notification
- duplicate handling
- user handling
- attachements (pictures, links, etc...)
- search
- filters
Mikel Maron wrote:
I'd suggest bypassing Trac and looking into RedMine http://www.redmine.org/
Trac is wonderful, but convoluted. RedMine is built in Rails and quite
easy to modify.
Trac has the massive advantage that we're already using it however...
Being built on rails is no particular
Hi,
Tom Hughes wrote:
Being built on rails is no particular reason to favour something at all
really - quite the opposite in many ways.
Come on, how can you be critical of a project that single-handedly
implements an issue tracker, a wiki, and even forums! It's probably just
a few more
On Thu, Nov 27, 2008 at 01:23:59AM +0100, Frederik Ramm wrote:
Come on, how can you be critical of a project that single-handedly
implements an issue tracker, a wiki, and even forums! It's probably just
a few more lines of rails code and it also has a geo database, then
we'll just drop
28 matches
Mail list logo
