Eventually. Not quickly as it'll need to be done carefully (and I've not seen any confirmation that Marius/Ed are working on it). Steps:

1. Make the auto-builder do it if XS-Maemo-Optify is set to auto. This will insert a call to maemo-optify at the right point in the build process, if the package doesn't already use /opt and some other tests (perhaps runtime Python dependency, depending on what the outcome of Python optification is).
2. Ask some developers to set this and test. Notify that if testing goes well, developers not wanting auto-optification should start using XS-Maemo-Optify: none.
3. If all goes well, change the default for XS-Maemo-Optify from none to auto.

Possible values for XS-Maemo-Optify could be:

• none: no optification should be done, or considered, by the autobuilder.
• manual: the application author will do optification manually. If the package contains no entries under /opt it would be considered a build failure.
• auto: maemo-optify would be run if certain heuristics were met (e.g. no entries in /opt, no Python dependency)
• force: maemo-optify would always be run.