#414328: Converting core modules to provide fields leaves them with no UI showed a consensus on moving the current Field UI in CCK HEAD into core, to make it easier for the community to grasp the current status of the UI and embrace the task of enhancing it.
As I said earlier on, I won't have the bandwidth for the additional tasks of debugging / adding missing features / polishing all by myself.
It's probably easier if I do the initial sorting and roll the initial patch, though...
So a couple questions before I get started:
- should this be a separate module (optional ? required ?), or be merged into field.module ?
- if separate module : what name and namespace ? Field UI / field_ui ?
FWIW, rolling this as a separate module will probably be easier and allow for a faster commit, and we can always revise afterwards...