How to use the community binding phase for good
In the community binding phase students can work on getting up to speed with moin coding, getting in touch with moin community, learn development methods, etc. - below we point to some tasks good for preparation:
DOM converter related projects
For Wiki DOM related projects, some easy but still important smaller tasks could be used for training:
- Documentation. DOM converter isn't well-documented now. So both API doc and some stuff on this wiki describing different aspects of it can be improved.
Transclusion stuff (images, etc). Looks like way of transcluding different sorts of data have many generic parts and it's still incomplete in MoinMoin.converter2. But it's rather complicated, so one can start with implementing only one sort of transclusion.
Smileys. They are still unimplemented, too.
Tests. There already are some tests in http://hg.moinmo.in/moin/2.0-storage-dom-bblank/file/tip/MoinMoin/converter2/_tests, but they are incomplete and rather dirty/inconsistent. This is a good starting point for becoming familiar with code — trying to test it.
converter2.pygments_in also needs more love.
Safe HTML > DOM. Looks like this task heavily overlaps with HTML > DOM converter, but still.
CSV > DOM. Rather simple task, but still important. See also DataBrowserWidget.
DataBrowserWidget > DOM. For now, DBW outputs raw HTML.
Jinja Theming
- have some browsers ready (including the usual troublemaker IE, e.g. in a Windows VM)
- look at 1.9 theme code, css, images to see how it worked
- find out what we already have for theming in moin/2.0 (and what's missing)
LDAP groups / Kerberos
- have some AD server ready (e.g. within a Windows VM)
- look at existing moin ldap_login code, make it work within your test setup