ThomasWaldmann
commented
5 years ago ### New validation library
tickets: #618
flatland was pretty dead over the last years and py27 only, but might get reanimated / ported to py3 now.Removed this from the top post:
- flatland has a new home there now: https://github.com/discorporate/flatland
- did some modernization and a 0.8.1 release: https://github.com/discorporate/flatland/releases/tag/0.8.1
- i did a new py3 port, all tests work, merged into master, released as 0.9.0. https://github.com/discorporate/flatland/pull/48
So guess this counts as undead now.
Names / Namespaces
tickets: #364 #363 #194 #139 #107 #81 Names (esp. multiple) of items and namespaces need more thoughts / work / fixes.
storage / database?
tickets: #715 #743 Do we continue with our self-made storage system, including whoosh-based indexing/search/lookup (
moin.storagepkg) or migrate to a database approach (postgresql, sqlalchemy or django orm, zodb)?stay with flask or move to django web framework?
tickets: #742 we use flask, moving to django would be quite some work.
Converters: xpath testing / xml library
tickets: #639 #619 we need more xpath-based testing and maybe we want to move from unmaintained emeraldtree to lxml.
Converters: create a separate pypi package?
tickets: #714 a separate pypi package might attract more developers/maintainers, if they adapt our transformation pipeline into their projects.
Editor related
tickets: #310 #460 #461 #280 #302 #133 we currently have simple html textedit field (for text items of any type) and ckeditor (html-items-only) as editors. if a collab editor would be required, it would remove the need for item locking and conflict management.
E-Mail related
tickets: #382 #383 #338 we have some code in moin 1.9 for "sending an email to the wiki", needs porting / testing.
UI / UX redesign: do it completely differently / from scratch?
Like e.g. some UI js app talking to a moin backend service?
How to find someone who is good with UI / UX and would work on that?