Last modified: 2014-07-02 12:18:13 UTC
WikibaseLib is currently a "kitchen sink" of things used by both client and repo. This is quite bad. It should be split up into modules with clear boundaries. For now, they can stay in the same git repository, but they should be moved to separate directories, on the same level as "repo", "client", "lib", etc. Some possible new modules: * engine (the mediawiki independent part of the repo) * core (basis for the engine - maybe already covered by DataModel) * formatters (could go into DataValue/xxx) * parsers (could go into DataValue/xxx) * validators (can they go into the repo module) * storage (read-only) * serializers (already being moved/replaced) One thing to consider is also that the repo wiki would almost always want to also have (at least some) client functionality. The repo being its own client is really the standard use case. So it would be fine for the repo module to depend on the client module, so things like language fallback could just be defined in the client. Side note: we may want to move messages to the new components. That needs to be coordinated with the i18n folks (Siebrand, in particular).
