PetRoadMap

First of all, the list of all completed items:

• converge main & cm into one new main branch

• [http://pet.opendfki.de/wiki/Programming%20Style%20Guide code style recommendations fixed]

• poll for functionality, esp. in input part, has been done

• no need for a ticketing system other than trac

This is a list of possible topics to discuss in this session. Please add topics freely that you feel are missing.

• after that: refactoring the code

  • have a sub-group working out a list of deprecated things
  • get rid of ECL as much as possible
    • remove input modes that rely on ECL, complete MRS treatment as far as necessary
  • remove as much of the load on "item" as possible
  • encourage developers to remove obsolete code and merge similar functionality where possible
  • refactoring into new code style, once it is fixed
  • documentation of (especially new) modules,
    • add scripts to illustrate use
    • necessary resources (data to train / models, training scripts, etc)
  • copyright notice updates ?

• GUI: which one, desired functionality?

• XML-RPC / API enhancments

• put the road map and TODO into the PET trac

• implement Lohuizen unifier to enable multi thread operations

• release plans / procedures (LOGON?)

• include C++ REPP implementation (RebeccaDridan has working code

  • --- not 100% LISP compatible yet --- differences not necessarily bugs)

Wishlist

• generation
  • MRS equivalence test
  • MRS rewriting (for trigger rules), also used in idiom checking
• unique output separation for standard-io server mode (requested many times in the past)