Skip to content

PSC Meeting 2012 02 23

Jim Klassen edited this page Jun 12, 2017 · 1 revision

2012 02 23 Meeting

Meeting

2.6 progress (coding, testing, tickets, etc)

  • Most Tickets in Testing Phase (consider adding to OSGeo status)
  • Chrome mouse pointer many not be fixable.
  • Undefined points on edited drawn polygons is only show stopper. Ticket
  • TinyOWS still being worked on. Possible same projection only work around

2.6 testing (where, when?)

  • Tentatively Brian providing MS4W stable
  • Trunk on geomoose.org - Week of March 12thish
  • Consider dns trickery to make it look like it is all geomoose.org (i.e. point ms4w.geomoose.org to Brian's IP).
  • LiveDVD work could be reused
  • .sh for install now, maybe .deb too
  • Consider Ubuntu ppa?
  • Separate out demos from GM distro (terraserver url updates)? Demos somewhat version dependent.

2.6 RFCs (Brent) - RoadMap in Trac?.

  • Alert Public to changes.
  • Short list is already started.
  • Layer management in general (WMS, WFS, WFS-T, MapServer Protocol, etc)
  • See also, change list

Release process, even is Brian is the release manager, it will take effort from all of us and particularly documenting and remember all the things will be a group effort.

  • RFC partly done, but I'll need help since I don't know the process very well
  • Version docs
  • Version demo
  • Package MS4W (for each beta/RC?)
  • Release Manager per release
  • Other installs, forthcoming as people interested and list is faq: Ubuntu linux install guide, LiveDVD, etc
  • Timeline?
  • Bug releases by PSC (no specific Release Manager)

Website/documentation plans (more detail following from Dan's email)

  • Eli's assumptions correct. Versioned docs coming. snapshot going

Overview of build system (which I sort of fear was covered in a previous conversation which I perhaps forgot)

  • Ideally more easily configured js distribution (only distribute used modules to user).
  • Probably too much complexity for return for many users.
  • Default build that 'works' and tools to build if you want.

RFC updates

  • Email coming. Many areas of strong consensus.

Packaging might be a good thing to discuss (Or at least other discussions with Bob suggest that)

  • Discussed in Release process above.
  • Jim made improvements.
  • Overall looks great and gives us good exposure.
  • Some minor things still.
  • DOQ and DRG display (no pink tile display).
  • DOQ and DRG print blank.
  • Radar printing works partly (prints radar, blacks other stuff
  • Parcels and Cities don't print.
  • Search exactly works best.
  • Report prints black.

OSGeo Incubation (Data and Code Provenience review)

  • Dan to check headers (some more needed).
  • Brian and Brent to look into data. Should include backlinks to source if possible.
  • Wiki status page (probably needs a new Code Provenience page)

Action items

  • TinyOWS minimally working in 1 projection (Brent - Windows, Dan - Linux) Completed with #36 and document that. TinyOWS still to go
  • Brian to determine if he can host MS4W and GM stable and suggest date of that see [1]
  • Jim and Dan linux trunk demo (week of march 12th-ish) see also #60
  • Brent will add to change log and make it more prominent and well know to users (RoadMap?)
  • Eli to work on Release Process RFC after finishing Mission RFC
  • Eli, Jim, and Dan to work on website doc updates (basically cron, svn, make html but probably harder) This is apparently done by Jim and Dan but needs documentation and publicizing. See for example, 2.4, trunk
  • Eli to complete RFC2 (mission) in next two weeks
  • Dan to keep working on Code Provenience (file headers) Much of this appears done too, see revision log 'license' commits
  • Brian and Brent to work on Code Provenience (data)
Clone this wiki locally