Prioritizing next batch of improvements, cleanups

[emiliom]

Let's see if using Milestones can help us organize our distributed contributions. These are my suggestions, not a definitive, consensus Milestone features. Some of these may already be implemented, but either the corresponding issue isn't closed or I didn't check thoroughly.

For Milestone 0.6.0:

Assessment and extension of class inheritance

• It seems to have been implemented successfully for SamplingFeatures and Results. Are there any concerns or problems with extending it to other entities?

RDBMS packages as optional installs

• Make specific RDBMS packages optional rather than required installs #44 Is it implemented in the pip install setup and conda recipe?

Removing unused or tangential code

• Can we delete the odm2api/ODM1_1_1 code? #38, Can we delete the odm2api/ODM1_1_1 code? (https://github.com/ODM2/ODM2PythonAPI/tree/master/odm2api/ODM2/LikeODM1 is still there, too)
• What are the Forms and doc/wxFormBuilder folders? #17, What are the Forms and doc/wxFormBuilder folders?

Python 3 readiness

• Not necessarily an immediate priority, but it's gotten a lot of recent attention
• python 3.x compatibility  #58, python 3.x compatibility
• Geoalchemy-ODM2 issues
  • Python 3.4.3 Geoalchemy Error #59, Python 3.4.3 Geoalchemy Error
  • python 3 support Geoalchemy supporter geoalchemy#2
  • Update base.py geoalchemy#3

[lsetiawan]

@emiliom Do you know if most of these issues/pr's have been addressed? Seems like some of them are not. This is the only thing in milestone 0.6.0.

[emiliom]

It's a mixed bag. I'll assess this later in the month, after we issue the next odm2api release (it's not like anyone paid any attention to this milestone wish list from 19 months ago!). In the meantime, I'll delete the milestone I had created for it way back then.