• Members 7 posts
    July 9, 2015, 12:49 p.m.

    Hi, first I want to tell, that I like Misago, it looks really nice and it seems, that Misago is what I'm looking for.

    I'm planning to migrate ubuntu.lt forum spanning 10 years of chat history. Forum has 6308 registered users and 67091 posts. Daily we have about 500 unique visitors.

    Is it safe to migrate ubuntu.lt forum to Misago 0.5.x version? It looks like 0.6 will not be released any time soon. But when 0.6 finally will be released, does migration scripts will be provided and all existing features in 0.5 will be available?

    While 0.6 is not released, I'm thinking to lift 0.5 a bit, by moving it to Django 1.8, because Django 1.6 is no longer supported.

  • July 10, 2015, 8:54 a.m.

    Misago 0.5 has quirks and small gotchas here and there, but there are none known data loss bugs or vulnerabilities. Piotr (@Orange) ran pretty active forum (100 signed in online, 1k posts daily) and was happy with it.

    There are small bugs like unability to remove prefix from threads on threads list or some views working on one Jinja version but erroring on other. If you update 0.5 codebase to work with latest dependencies (may be tricky, we have plenty of features and no tests coverage for 0.5) without showstoppers and maybe backport few small security improvements from 0.6 (singing preparsed posts content is superinportant against defaces) and commit and takeover bug/security fixing, I would actually greenlight that as 0.6 backposting Ember.js rewrite for 0.7.

  • Members 7 posts
    July 28, 2015, 2:37 p.m.
  • Members 7 posts
    July 31, 2015, 8:49 a.m.

    @rafalp I just created Misago fork with default branch ubuntu-lt based on 0.5.x branch.

    First we are going to write some tests to raise test coverage. Then we will do the transition to Django 1.8 and later to Python 3.

    The questions is, what is the best way to work on this quite big change in order for you to be easier to merge it?

    Would you like to do frequent pull request reviews or you would like to review whole 1.8 transition when it will be ready?

  • July 31, 2015, 9:19 a.m.

    Eh, don't bother with me merging it, it'll live on its own branch. My master branch is de-facto rewrite of Misago so 0.5 isn't mergeable with it either. Just make sure its possible to update forum from latest 0.5 release to yours, and when its time I'll make sure its possible to update from yours release to mine. :]

    Also loving what you doing for this project <3

  • Members 7 posts
    July 31, 2015, 10:14 a.m.

    So in the end, there will be two versions of Misago, one based on master and other on 0.5.x?

  • July 31, 2015, 10:40 a.m.

    I wouldn't be such an optimist about 0.6 release date. ;) I am making progress with Ember.js, but getting everything done in 4 versions makes everything slow. For example users list needs following: API endpoint, Ember.js view, Emberj.js loader, Django view, Ember.js, API and Django tests. Getting this done is time consuming job, but effect makes efforts worth it. :]

  • July 31, 2015, 10:49 a.m.

    Afaik, 0.5.x branch will be discontinued when 0.6 (or "Ember.js Misago") matures enough. There will be a migration tool to move to newest codebase. 0.6 is so much different, upgrade will be very significant.

    So, for me, 0.5 should be considered legacy, but more or less completed. 0.6 is not ready for any real usage, as it's currently missing basic features.

  • July 31, 2015, 11:05 a.m.

    Outdated fox is outdated.

    0.6 release will be next feature release. If @sirex finishes his Misago with Django 1.8 and tests and etc ect before I finish mine (which is super propable), it will be released as 0.6 thus pushing mine away to next free version number (like 0.7).

  • Members 7 posts
    July 31, 2015, 11:13 a.m.

    In this case, maybe it is worth helping you with the master, instead of working on 0.5.x?

    I think, to migrate 0.5.x to Django 1.8, we will need ~2-3 weeks. How much work left on new version that you currently work on? And is new version of Misago will support database migration from 0.5.x?

    In addition we are planning to add django-allauth for password-less registration, because we don't want to store passwords in our server.

  • July 31, 2015, 12:43 p.m.

    Emberized Misago is very unlikely to happen this year. I'll wont offer DB migration, but I will offer data migration, so your content can be moved and preserved between old and new site.

    So yeah, unless you are fluent with Ember.js 1.12, theres little up for takers there, but you may give a look to pre-ember branch that contains great lot of features for 0.6 already implemented and tested with mostly static html for interface. Thats the codebase I have branched off for ember.js inclusion, but it still has some things missing like search, subscriptions, reports, changelogs and attachments.

  • Members 7 posts
    July 31, 2015, 12:52 p.m.

    I just checked Misago master and I see, that there is a lot of JavaScript involved. Since I don't like JavaScript so probably there will be nothing I could help with master version. From the development/contributing point, I like 0.5.x version much more.

    So I will take 0.5.x and will try up upgrade it to Django 1.8 and Python 3. Also I will look into master, maybe I can take something from there too.

    We will do all development in this fork and finally, when everything works, I will create huge pull request to be released as 0.6.x.