[xwiki-devs] [VOTE] Move from our mailing lists and use Discourse instead
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
I guess we can try it. Thanks, Caty On Fri, Feb 24, 2017 at 1:18 PM, 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
FWIW, I am an admin over a private Discourse forum as far as forum software goes, it's pretty darn good and as Vincent said, I do use the mailing list option, so most of the time I just keep up to date via email, but then have the power discussion options of the forum when needed. On Fri, Feb 24, 2017 at 5:45 AM, Ecaterina Moraru (Valica) < [email protected]> wrote:
I guess we can try it.
Thanks, Caty
On Fri, Feb 24, 2017 at 1:18 PM, 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
-- Keith Davis 214-906-5183
+1, looks awesome and can be SSO integrated I hope it will give us the best of both worlds. I wonder if we can also reintegrate the archives. -- Denis Gervalle SOFTEC sa - CEO On Fri, Feb 24, 2017 at 13:43, Keith Davis <[email protected]> wrote: FWIW, I am an admin over a private Discourse forum as far as forum software goes, it's pretty darn good and as Vincent said, I do use the mailing list option, so most of the time I just keep up to date via email, but then have the power discussion options of the forum when needed. On Fri, Feb 24, 2017 at 5:45 AM, Ecaterina Moraru (Valica) < [email protected]> wrote:
I guess we can try it.
Thanks, Caty
On Fri, Feb 24, 2017 at 1:18 PM, 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
-- Keith Davis 214-906-5183
Hi, Sounds interesting. Hope it won`t be complicated to host it ourselves and that we won`t have service interruptions due to hosting problems. Also, it would be interesting if it would also accept guest posts (i.e. no registration just to ask a question). +1 from my side to try it out. Thanks, Eduard On Fri, Feb 24, 2017 at 3:55 PM, Denis Gervalle <[email protected]> wrote:
+1, looks awesome and can be SSO integrated I hope it will give us the best of both worlds. I wonder if we can also reintegrate the archives.
-- Denis Gervalle SOFTEC sa - CEO On Fri, Feb 24, 2017 at 13:43, Keith Davis <[email protected]> wrote: FWIW, I am an admin over a private Discourse forum as far as forum software goes, it's pretty darn good and as Vincent said, I do use the mailing list option, so most of the time I just keep up to date via email, but then have the power discussion options of the forum when needed.
On Fri, Feb 24, 2017 at 5:45 AM, Ecaterina Moraru (Valica) < [email protected]> wrote:
I guess we can try it.
Thanks, Caty
On Fri, Feb 24, 2017 at 1:18 PM, 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
-- Keith Davis 214-906-5183
Looked over the features, seems to cover most of my concerns except one: migrating the current mailing list archives (at least I couldn't see it in the features list). Do we care about that? Can it be scripted using the API? Anyway, +1. On 02/24/2017 06:18 AM, Vincent Massol 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
-- Sergiu Dumitriu http://purl.org/net/sergiu
Interesting plugin: * Solved plugin: https://meta.discourse.org/t/discourse-solved-accepted-answer-plugin/30155 @Sergiu: here’s a script to import from mailman mbox files: https://meta.discourse.org/t/import-mailman-archives-into-discourse/18537/9 However I’m not sure if it’s a good thing or not, see https://meta.discourse.org/t/import-mailman-archives-into-discourse/18537/2. We could try and see what it gives us. 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
+1 2017-02-25 14:44 GMT+01:00 Vincent Massol <[email protected]>:
Interesting plugin: * Solved plugin: https://meta.discourse.org/t/discourse-solved-accepted- answer-plugin/30155
@Sergiu: here’s a script to import from mailman mbox files: https://meta.discourse.org/t/import-mailman-archives-into- discourse/18537/9
However I’m not sure if it’s a good thing or not, see https://meta.discourse.org/t/import-mailman-archives-into- discourse/18537/2. We could try and see what it gives us.
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
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
Looks good. As long as I can continue using it as a mailing list and not forced to go to some forum to know if there is new messages I'm fine. On Mon, Feb 27, 2017 at 10:02 AM, Guillaume Delhumeau <[email protected]> wrote:
+1
2017-02-25 14:44 GMT+01:00 Vincent Massol <[email protected]>:
Interesting plugin: * Solved plugin: https://meta.discourse.org/t/discourse-solved-accepted- answer-plugin/30155
@Sergiu: here’s a script to import from mailman mbox files: https://meta.discourse.org/t/import-mailman-archives-into- discourse/18537/9
However I’m not sure if it’s a good thing or not, see https://meta.discourse.org/t/import-mailman-archives-into- discourse/18537/2. We could try and see what it gives us.
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
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
-- Thomas Mortagne
+1 to try it out. Thanks, Marius On Fri, Feb 24, 2017 at 1:18 PM, 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
https://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-communit... They offer free hosting to open source projects if the repo has more than 30 contributors and 2000+ stars. We have 55 contributors and 214 stars. We could make a campaign to get more stars :) On Wed, Mar 1, 2017 at 11:18 AM, Marius Dumitru Florea < [email protected]> wrote:
+1 to try it out.
Thanks, Marius
On Fri, Feb 24, 2017 at 1:18 PM, 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
On 3 Mar 2017, at 22:20, Ecaterina Moraru (Valica) <[email protected]> wrote:
https://blog.discourse.org/2016/03/free-discourse-forum-hosting-for-communit... They offer free hosting to open source projects if the repo has more than 30 contributors and 2000+ stars.
We have 55 contributors and 214 stars. We could make a campaign to get more stars :)
It could be interesting but I think we'd be better off hosting it ourselves since that allows us more control: plugins we install, config, etc. Now it would certainly relieve us from some maintenance such as upgrades! A campaign to get more stars wouldn't hurt anyway ;) Thanks -Vincent
On Wed, Mar 1, 2017 at 11:18 AM, Marius Dumitru Florea < [email protected]> wrote:
+1 to try it out.
Thanks, Marius
On Fri, Feb 24, 2017 at 1:18 PM, 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
It looks really interesting and I trust our community governance to take an amount of advantages of it. My +1 too. paul
On 01 Mar 2017, at 10:18, Marius Dumitru Florea <[email protected]> wrote:
+1 to try it out.
Thanks, Marius
On Fri, Feb 24, 2017 at 1:18 PM, 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
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
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
* 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
-- Thomas Mortagne
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so: " You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category. Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email. Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.” From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6 Thanks -Vincent
* 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
-- Thomas Mortagne
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
Thanks -Vincent
* 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
-- Thomas Mortagne
-- Thomas Mortagne
On Fri, Apr 28, 2017 at 4:55 PM, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]>
wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
Not sure the best idea is to have 2 Discourses, but we can surely create a special category for users. Mailinglist doesn't allow categorization, so we don't need a 1-1 translation from mailinglist to discourse. Thanks, Caty
Thanks -Vincent
* 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
-- Thomas Mortagne
-- Thomas Mortagne
On 28 Apr 2017, at 15:55, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
I thought about this but AFAIU this wouldn’t work. The email address used to reply to posts is of the form: <prefix>+<topickey>@<domain name> For example: [email protected] So I don’t think it would work to POP [email protected] (and we don’t have a POP-able inbox for users mail either AFAIK). Thanks -Vincent
Thanks -Vincent
* 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
-- Thomas Mortagne
-- Thomas Mortagne
On Fri, Apr 28, 2017 at 3:58 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:55, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
I thought about this but AFAIU this wouldn’t work.
The email address used to reply to posts is of the form:
<prefix>+<topickey>@<domain name>
For example: [email protected]
For replies sure but for new topics ?
So I don’t think it would work to POP [email protected] (and we don’t have a POP-able inbox for users mail either AFAIK).
This is not really an issue. You just need to setup a regular mail account behind [email protected] instead of a mailing list, exactly like what Kevin is probably currently doing for whatever mail address you decided to use for Discourse replies.
Thanks -Vincent
Thanks -Vincent
* 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
-- Thomas Mortagne
-- Thomas Mortagne
-- Thomas Mortagne
On 28 Apr 2017, at 16:05, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:58 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:55, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
I thought about this but AFAIU this wouldn’t work.
The email address used to reply to posts is of the form:
<prefix>+<topickey>@<domain name>
For example: [email protected]
For replies sure but for new topics ?
I’m not sure I understand. If the idea is to use [email protected] instead of [email protected] then yes it’s possible but this means the user list is no longer accessible, even in readonly (we need to configure mailman and mail servers inside XWiki SAS to not go to mailman) and we cannot have a special list user inside discourse posting to the user list and thus we won’t have markmail/nabble/gmane/etc archiving the new posts Thanks -Vincent
So I don’t think it would work to POP [email protected] (and we don’t have a POP-able inbox for users mail either AFAIK).
This is not really an issue. You just need to setup a regular mail account behind [email protected] instead of a mailing list, exactly like what Kevin is probably currently doing for whatever mail address you decided to use for Discourse replies.
Thanks -Vincent
Thanks -Vincent
* 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 >
-- Thomas Mortagne
-- Thomas Mortagne
-- Thomas Mortagne
On Fri, Apr 28, 2017 at 4:14 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 16:05, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:58 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:55, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
I thought about this but AFAIU this wouldn’t work.
The email address used to reply to posts is of the form:
<prefix>+<topickey>@<domain name>
For example: [email protected]
For replies sure but for new topics ?
I’m not sure I understand. If the idea is to use [email protected] instead of [email protected] then yes it’s possible but this means the user list is no longer accessible, even in readonly (we need to configure mailman and mail servers inside XWiki SAS to not go to mailman)
The archive and the mail address are two different things. It's not because [email protected] is redirected to something else that the old mailman archive is not accessible anymore, it's just a web page. I'm not proposing to replace [email protected] here. Again the idea is to have mails sent to [email protected] create new topics on Discourse instead of returning errors, nothing else, mailman won't accept any registration and it won't sent any mail anymore.
and we cannot have a special list user inside discourse posting to the user list and thus we won’t have markmail/nabble/gmane/etc archiving the new posts
Thanks -Vincent
So I don’t think it would work to POP [email protected] (and we don’t have a POP-able inbox for users mail either AFAIK).
This is not really an issue. You just need to setup a regular mail account behind [email protected] instead of a mailing list, exactly like what Kevin is probably currently doing for whatever mail address you decided to use for Discourse replies.
Thanks -Vincent
Thanks -Vincent
> * 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 >> >
-- Thomas Mortagne
-- Thomas Mortagne
-- Thomas Mortagne
-- Thomas Mortagne
On 28 Apr 2017, at 16:29, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 4:14 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 16:05, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:58 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:55, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote:
> On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote: > > On Fri, Apr 28, 2017 at 3:43 PM, 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. > > Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
I thought about this but AFAIU this wouldn’t work.
The email address used to reply to posts is of the form:
<prefix>+<topickey>@<domain name>
For example: [email protected]
For replies sure but for new topics ?
I’m not sure I understand. If the idea is to use [email protected] instead of [email protected] then yes it’s possible but this means the user list is no longer accessible, even in readonly (we need to configure mailman and mail servers inside XWiki SAS to not go to mailman)
The archive and the mail address are two different things. It's not because [email protected] is redirected to something else that the old mailman archive is not accessible anymore, it's just a web page.
I'm not proposing to replace [email protected] here. Again the idea is to have mails sent to [email protected] create new topics on Discourse instead of returning errors, nothing else, mailman won't accept any registration and it won't sent any mail anymore.
So if I understand you’re proposing to: 1) Decommission the [email protected] route since right now it leads to mailman in the infra 2) Make [email protected] an alias for [email protected] You still haven’t replied to me how the list user inside discourse will be able to post to the users mailing list if we decommission the [email protected] that goes to the users list. You’re proposing to create a new route to the users list for that? Thanks -Vincent
and we cannot have a special list user inside discourse posting to the user list and thus we won’t have markmail/nabble/gmane/etc archiving the new posts
Thanks -Vincent
So I don’t think it would work to POP [email protected] (and we don’t have a POP-able inbox for users mail either AFAIK).
This is not really an issue. You just need to setup a regular mail account behind [email protected] instead of a mailing list, exactly like what Kevin is probably currently doing for whatever mail address you decided to use for Discourse replies.
Thanks -Vincent
Thanks -Vincent
> >> * 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
On Fri, Apr 28, 2017 at 4:35 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 16:29, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 4:14 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 16:05, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:58 PM, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:55, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:53 PM, Vincent Massol <[email protected]> wrote: > >> On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote: >> >> On Fri, Apr 28, 2017 at 3:43 PM, 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. >> >> Does it also support starting new discussion by mail or only reply ? > > It seems so: > > " You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category. > > Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email. > > Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.” > > From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
In that case another idea for the migration would be to make Discourse monitor [email protected] instead of making it readonly.
I thought about this but AFAIU this wouldn’t work.
The email address used to reply to posts is of the form:
<prefix>+<topickey>@<domain name>
For example: [email protected]
For replies sure but for new topics ?
I’m not sure I understand. If the idea is to use [email protected] instead of [email protected] then yes it’s possible but this means the user list is no longer accessible, even in readonly (we need to configure mailman and mail servers inside XWiki SAS to not go to mailman)
The archive and the mail address are two different things. It's not because [email protected] is redirected to something else that the old mailman archive is not accessible anymore, it's just a web page.
I'm not proposing to replace [email protected] here. Again the idea is to have mails sent to [email protected] create new topics on Discourse instead of returning errors, nothing else, mailman won't accept any registration and it won't sent any mail anymore.
So if I understand you’re proposing to:
1) Decommission the [email protected] route since right now it leads to mailman in the infra 2) Make [email protected] an alias for [email protected]
You still haven’t replied to me how the list user inside discourse will be able to post to the users mailing list if we decommission the [email protected] that goes to the users list. You’re proposing to create a new route to the users list for that?
The idea is only to not loose all the mails sent to [email protected], as I said mailman would not do anything anymore so the old mailing list won't exist from mail server point of view. If you want to receive mails you will need to tell Discourse to send them to you I guess. Maybe Discourse can do more (like some way import mail addresses from mailman) I don't know, I'm not the one proposing to use it :)
Thanks -Vincent
and we cannot have a special list user inside discourse posting to the user list and thus we won’t have markmail/nabble/gmane/etc archiving the new posts
Thanks -Vincent
So I don’t think it would work to POP [email protected] (and we don’t have a POP-able inbox for users mail either AFAIK).
This is not really an issue. You just need to setup a regular mail account behind [email protected] instead of a mailing list, exactly like what Kevin is probably currently doing for whatever mail address you decided to use for Discourse replies.
Thanks -Vincent
> > Thanks > -Vincent > >> >>> * 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
-- Thomas Mortagne
On 28 Apr 2017, at 15:53, Vincent Massol <[email protected]> wrote:
On 28 Apr 2017, at 15:49, Thomas Mortagne <[email protected]> wrote:
On Fri, Apr 28, 2017 at 3:43 PM, 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.
Does it also support starting new discussion by mail or only reply ?
It seems so:
" You can start topics, reply to topics, have a mailing list mode where you get an email per post on the forum or post on the category.
Longer term we plan to add some "secret commands" that allow you to like a post or flag a post via email.
Overall mailing list parity is pretty high here and we support a bunch of stuff mailing lists do not.”
From https://meta.discourse.org/t/start-a-new-topic-via-email/12477/6
And https://meta.discourse.org/t/start-a-new-topic-via-email/12477/22?u=vmassol (apparently each category can provide an email address) Thanks -Vincent
Thanks -Vincent
* 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
-- Thomas Mortagne
On Fri, Apr 28, 2017 at 4:43 PM, 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.
ok
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 can have a transitional period and not make it readonly immediate after the announcement.
* 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.
ok, because of the searching all part. Thanks, Caty
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
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
On Mon, May 15, 2017 at 3:44 PM, Vincent Massol <[email protected]> wrote:
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).
Should also probably redirect http://dev.xwiki.org/xwiki/bin/view/Community/Forum to http://dev.xwiki.org/xwiki/bin/view/Community/Discuss.
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
-- Thomas Mortagne
I'm fine by the way, hope we'll have answer by mail quickly. The most important for me is to receive mails so that I don't miss conversations and that part is working well as far as I can see. On Mon, May 15, 2017 at 3:50 PM, Thomas Mortagne <[email protected]> wrote:
On Mon, May 15, 2017 at 3:44 PM, Vincent Massol <[email protected]> wrote:
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).
Should also probably redirect http://dev.xwiki.org/xwiki/bin/view/Community/Forum to http://dev.xwiki.org/xwiki/bin/view/Community/Discuss.
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
-- Thomas Mortagne
-- Thomas Mortagne
On Mon, May 15, 2017 at 4:44 PM, Vincent Massol <[email protected]> wrote:
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?
+1 Thanks, Caty
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
On 15 May 2017, at 15:44, Vincent Massol <[email protected]> wrote:
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).
Done. I’ve also redirected http://dev.xwiki.org/xwiki/bin/view/Community/Forum to https://discourse.xwiki.org. Note: I’ve asked xwiki sas infra to create https://forum.xwiki.org.
2) I send a mail to users & devs @xwiki.org to announce the new forum.
Doing in a few minutes.
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?
Keep the feedback coming! :) Thanks -Vincent
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
participants (10)
-
Denis Gervalle -
Ecaterina Moraru (Valica) -
Eduard Moraru -
Guillaume Delhumeau -
Keith Davis -
Marius Dumitru Florea -
Paul Libbrecht -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol