• Feb. 23, 2023, 4:24 p.m.

    I've decided to abandon the plan to just hide in the cave for a few years and write next version of Misago from scratch. I've got quite a lot done, but to build it all it would take me years of having to split my attention between 0.x line and future line.

    Luckily in the meantime the world has caught up and Django naw supports enough of asynchronous Python and the ASGI protocol that makes it possible to port over a hefty amount of work that was done for v4.

    My current plan is to complete the work on improvements for 0.x line: update the posting UI, add in-app notifications, advanced search screen + few other small tweaks and changes. After this work is done, I will release Misago 1.0.

    After Misago 1.0 is complete, I will focus on porting the improvements and changes from Misago v4 back to current version. Top priority for me is to simplify user permissions because its source of major pain when working with features.

    After user permissions and groups my next focus would be updating Misago's HTTP stack to make it work with ASGI. This will let me start working on GraphQL API for future client.

    My long-term goal for Misago is to reduce Python's codebase to headless API doing forum software, with separate JavaScript application doing both server-side and client side rendering.

  • bookmark_border

    Thread has been pinned in category.

  • Members 148 posts
    Feb. 24, 2023, 1:26 p.m.

    My ill informed view, for what it's worth, is that this sounds like a good (better!) plan. It means misago continues to evolve and receive more active maintenance, and transitions it to a modern asynchronous model.

  • Feb. 24, 2023, 1:57 p.m.

    Yup! That posting UI update coming in next feature release relies heavily on know-how from v4 + parts of implementation were copied over from it with changes to work with existing codebase.

    There's bunch other things in v4 that I want to eventually port back:

    • AST-based markup parser
    • GraphQL API
    • Plugin system that supports client plugins
    • Simplified permissions system

    I guess the very rough roadmap is new posting UI -> Alerts/Notifications -> Advanced search -> Few extra UI changes/improvements -> v1.0 -> AST parser backport -> groups and permissions as v 2.0 -> basic support as v3 + moving features to async as v3.1, v3.2

  • May 25, 2023, 3:36 p.m.

    I’ve stopped obsessing about „Misago v1” release and deleted the milestone from GitHub.

    Instead v1 will happen when backwards compat of the database will be broken. I have planned quite a few big changes to the database:

    • notifications
    • new message parser
    • simpler permission system
    • thread accurate reads tracker
    • simpler cache versioning
    • simpler dynamic settings storage
    • simpler categories tree

    All those changes are currently done in backwards compatible way: new database tables and columns are added next to old ones. This way old data is left there in case update goes wrong and site owner needs a downgrade.

    Misago v1 only difference from v0 will be set if upgrade operations deleting those old unused tables and colums with their data.