Hi devs, New status as of 15 May 2017:
* Categories created, see https://discourse.xwiki.org/ * Still missing ability to reply by mail (waiting for Kevin on this). Since I have no idea when this can be implemented, I think we shouldn’t block on this to get started * I’ve created a discourse user with an email of [email protected] so that we can continue archiving everything posted on discourse. In short we’re ready to start using discourse.xwiki.org. So what I propose now is that: 1) I document it on http://dev.xwiki.org/xwiki/bin/view/Community/MailingLists. I’ll also rename the page to http://dev.xwiki.org/xwiki/bin/view/Community/Discuss (with a redirect). 2) I send a mail to users & devs @xwiki.org to announce the new forum. 3) After 1-2 days, I’ll configure the users @ xwiki.org mailing list to reject all posts with a message explaining the move to the forum. Ok with everyone? Thanks -Vincent > On 28 Apr 2017, at 15:43, Vincent Massol <[email protected]> wrote: > > Status > ====== > > So I’ve progressed in this with Kevin (who’s an infra admin at XWiki SAS). > > We now have an instance ready. > > What’s left to do: > > * Configure reply by email. I’m currently trying to do that with Kevin. The > principle is that you receive mail from discourse and we set in discourse a > reply-to email address so that when you reply to the mail, it goes to a mail > inbox somewhere (some gmail account for example). Then discourse is > configured to check (using POP3, they don’t seem to support IMAP ATM) that > inbox and to process mails found in it and update the topics. Note that even > if we don’t configure this, users can still receive emails for all posts but > they will just need to click on the link to go the webpage and answer. It’s > not the end of the world either. > > * Decide on the migration path. See below > > * Decide if we migrate only users or also devs. FTM I suggest that we do only > users and see how it goes and if we’re happy we can decide to move devs data > too. > > Migration Path > ============ > > I propose the following: > > * On a given date that we advertise on the users list, we configure this list > to be readonly and not allow more posts. We invite users to register on our > discourse instance and use that. > * We don’t import our archives since it’s complex > (https://meta.discourse.org/t/howto-import-mbox-mailing-list-files/51233) and > there’s not a perfect mapping. We can always do that in the future if someone > really wants to work on that. > * We create a markmail user in our discourse instance and configure it to > receive all posts. We set its email address to be [email protected] and we > configure the users list to accept mail from our discourse instance. This > allows to keep having a place where we can search in all places by using > markmail. Incidentally this also means that nabble and gmane will continue to > archive our mails which is nice. > > WDYT? > > Thanks > -Vincent > > >> On 24 Feb 2017, at 12:18, Vincent Massol <[email protected]> wrote: >> >> Hi devs, >> >> I’m proposing to vote for moving away from our users and devs mailing list >> and instead to use the Discourse open source tool: >> >> * Home page: http://www.discourse.org/ >> * License: GPL v2 >> * FAQ: http://www.discourse.org/faq/ >> * Awesome feature list: http://www.discourse.org/about/ >> >> What is especially interesting for us: >> * It works with mailing lists (you can receive mails and send mails to the >> forum). >> * Works as a forum. BTW if you want to see a real life instance, check the >> gradle instance at https://discuss.gradle.org/ >> >> Nice things: >> * Works on mobile >> * Comprehensive API (would allow us to integrate it with xwiki.org) >> * Badges/user metrics >> >> So here’s my +1 to try it out and ask XWiki SAS if they could host an >> instance. >> >> WDYT? Do you see any negative point (I don’t ATM)? :) >> >> Please cast your votes! >> >> Thanks >> -Vincent >> >
