MapServer Janitorial
Some of the MapServer developers may have been getting more than their share of trac notifications this week. This is partly because I’ve taken the last few days to sift through many tickets which have no milestone attached to them. Between old issues, bugs that have since been fixed, etc., it was nice to clean house a bit. They contributed to ~20 tickets being closed just this week! It’s amazing to see how many old school tickets there are lying around in trac. I try to commit to a once a month sift of trac for the oldies, but sometimes goodies 🙂
Other MapServer thoughts:
- I love the OpenLayers and GeoServer blogs. In addition to annoucements, they also convey useful information about features, demos, etc. It would be great if MapServer had a blog. Something like COREBlog could be used within the existing Plone-based website. Or, as discussed with hobu on IRC earlier this week, maybe the entire MapServer website can be based on trac. Existing pages could be ported to trac, as well as having a unified username/password, leveraging the OSGeo infrastructure. Food for thought 🙂
- OGC Web Services Workshop: I have been thinking about moving this to MapServer’s OSGeo infrastructure. This way, it matures with the MapServer project as a whole. This would include a dedicated component in trac, as well as a module in svn. Well, it turns out that Steve, who is doing a MapServer tutorial, is into this as well. This could lead to perhaps shared mapfiles and datasets for the various MapServer demos/tutorials/workshops. Stay tuned!
- I’ll say this again: I think a better organized codebase would result in more intuitive, componentized development. For example, it’s so easy to peruse the GDAL codebase thanks to the directory structuring of the code, IMHO
That’s it from here. Time to kickoff the weekend and start up the BBQ (yes, in this tundra-like weather — I’m an all year BBQ guy). Have a great weekend everyone!
