[geomoose-psc] Trac notifications?

Fri Apr 12 09:24:48 PDT 2013

I think python (or ruby or potentially node.js) would be much better.  But
also that we should decouple them a bit from the JS and from MapServer
rather than make a direct port.

For instance, I'd like GeoMoose to be able to work against GeoServer or
anything that produces valid WMS/WFS-T.  I think this means moving some
more from the services into JS and making the remaining of the services
more data source agnostic.
On Apr 12, 2013 11:18 AM, "Brian Fischer" <bfischer at houstoneng.com> wrote:

>  Sounds like we need some funding to try to port the PHP services to
> Python J ****
>
> ** **
>
> *Brian Fischer, CFM*
>
> Principal | GIS Project Manager ****
>
> Houston Engineering, Inc.****
>
> *O* 763.493.4522 | *D* 763.493.6664 | *M* 763.229.2734****
>
> ** **
>
> *From:* geomoose-psc-bounces at lists.osgeo.org [mailto:
> geomoose-psc-bounces at lists.osgeo.org] *On Behalf Of *James Klassen
> *Sent:* Friday, April 12, 2013 11:11 AM
> *To:* Bob Basques
> *Cc:* geomoose-psc at lists.osgeo.org
> *Subject:* Re: [geomoose-psc] Trac notifications?****
>
> ** **
>
> The big problem with more than one GeoMoose version at a time is mod_php
> isn't very flexible.****
>
> GeoMoose JavaScript has no problem with multiple versions.****
>
> The problem is the PHP code is coupled to the JS version and is also
> coupled to the MapServer version.  We tend to target the latest MapServer
> available in MS4W to make life easy for our windows running users.****
>
> So we end up needing multiple MapServer versions to run multiple GeoMoose
> versions  (which is easy enough for Perl/python/ruby MapScript and also
> easy enough if we would decouple the (PHP) services from the JS code
> similar to how things originally worked at the city) but with PHP where
> everything essentially gets linked into Apache at runtime it makes life
> very difficult.****
>
> On Apr 12, 2013 11:01 AM, "Basques, Bob (CI-StPaul)" <
> bob.basques at ci.stpaul.mn.us> wrote:****
>
> All,
>
> I have an interest in working on the "Demo" side of things, but I would
> prefer to work in a separate container of sorts, maybe more of a sandbox
> environment to be able to try different things, and to also possibly leave
> them in place between versions, at least for a couple of versions out.  I
> really like the sandbox approach used by OpenLayers for demos of particular
> capabilities.  Using this sort of model, it might be nice to see demos from
> more than one organization for different types of things over the long run.
>
> The current demo looks to be tightly integrated with the GeoMoose website
> on the whole, and based on the distribution methods that are needed, this
> is probably a good thing.
>
> So the question is, is there room for an extended set of demos, possibly
> housed somewhere besides the GeoMoose web site and tied in as a linked
> resource? This may be something that has some slight dependency on the
> future abstraction of some of the GeoMoose tools as well, at least in order
> for the idea to take off quicker.
>
> bobb
>
>
>
> >>  -----Original Message-----
> >>  From: geomoose-psc-bounces at lists.osgeo.org [mailto:geomoose-psc-
> >>  bounces at lists.osgeo.org] On Behalf Of Eli Adam
> >>  Sent: Friday, April 12, 2013 10:48 AM
> >>  To: James Klassen
> >>  Cc: geomoose-psc at lists.osgeo.org
> >>  Subject: Re: [geomoose-psc] Trac notifications?
> >>
> >>  Our docs partially suggest to confirm the bug on the list,
> >>  http://geomoose.org/trunk/docs/faq.html?highlight=faq#how-should-
> >>  i-report-a-bug
> >>  and
> >>  http://geomoose.org/trunk/howto/testing_reporting_ticketing.html#<http://geomoose.org/trunk/howto/testing_reporting_ticketing.html>
> >>  testing-reporting-ticketing
> >>
> >>  I like the idea of confirming bugs in advance but think that in
> >>  practice we will have to in some way deal with bugs that don't
> >>  first go through the list.
> >>
> >>  I've taken default ownership of the 'Docs' and 'Website'
> >>  components, is anyone interested in any of these components and
> >>  following up on list or ticket?
> >>      BuildTools
> >>      Demo
> >>      GeoMOOSE/JS
> >>      GeoMOOSE/PHP
> >>      Infrastructure
> >>      UserExtensions
> >>
> >>  Eli
> >>
> >>
> >>  On Tue, Apr 9, 2013 at 6:53 PM, James Klassen
> >>  <klassen.js at gmail.com> wrote:
> >>  > Generally, the owner of the ticket will get a notification.
> >>  The
> >>  > default owner is set at the component level.
> >>  >
> >>  >
> >>  > On Tue, Apr 9, 2013 at 8:46 PM, Brian Fischer
> >>  > <bfischer at houstoneng.com>
> >>  > wrote:
> >>  >>
> >>  >> I don't get any notification.
> >>  >>
> >>  >> I kind of like Jim's point that it would be nice to be
> >>  discussed on
> >>  >> the list first, but also see the point it would be nice to be
> >>  >> notified if someone does enter a ticket so we can follow up
> >>  >> immediately for clarification if the ticket is not clear and
> >>  saves
> >>  >> time later trying to sort that out.
> >>  >>
> >>  >> Brian Fischer, CFM
> >>  >> Principal | GIS Project Manager
> >>  >> Houston Engineering, Inc.
> >>  >> O 763.493.4522 | D 763.493.6664 | M 763.229.2734
> >>  >>
> >>  >> -----Original Message-----
> >>  >> From: geomoose-psc-bounces at lists.osgeo.org
> >>  >> [mailto:geomoose-psc-bounces at lists.osgeo.org] On Behalf Of Eli
> >>  Adam
> >>  >> Sent: Tuesday, April 09, 2013 5:29 PM
> >>  >> To: geomoose-psc at lists.osgeo.org
> >>  >> Subject: [geomoose-psc] Trac notifications?
> >>  >>
> >>  >> Does anyone get Trac notifications when new tickets are
> >>  opened?  The
> >>  >> reason I ask is that if people enter tickets and don't get any
> >>  >> response at all, it can be discouraging.
> >>  >>
> >>  >> I'm the default owner for Docs and website components so I get
> >>  those
> >>  >> notices.
> >>  >>
> >>  >> We could make this list the default owner, I also use
> >>  >> http://trac.osgeo.org/geomoose/report/9 as a tab on my
> >>  homepage to do
> >>  >> it the manual way.  Other ideas?
> >>  >>
> >>  >> Eli
> >>  >> _______________________________________________
> >>  >> geomoose-psc mailing list
> >>  >> geomoose-psc at lists.osgeo.org
> >>  >> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
> >>  >> _______________________________________________
> >>  >> geomoose-psc mailing list
> >>  >> geomoose-psc at lists.osgeo.org
> >>  >> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
> >>  >
> >>  >
> >>  _______________________________________________
> >>  geomoose-psc mailing list
> >>  geomoose-psc at lists.osgeo.org
> >>  http://lists.osgeo.org/cgi-bin/mailman/listinfo/geomoose-psc
>
> ****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20130412/0243f2e0/attachment-0001.html>