Hi all,
Bridging mailing lists to Discourse is something requested by the
community since Nabble is no more working for us. The goal is to be able
to post from the mailing lists and from Discourse, it is *not* to
replace mailing lists.
Guilhem (thanks a lot!) has deployed a test instance that you can find here:
https://communitytest.documentfoundation.org/
Note: this is a test instance only, if we go in production, all what has
been posted in this test instance will be deleted.
The ticket describing how it works:
https://redmine.documentfoundation.org/issues/3567
Category1 and Category2 have corresponding mailing lists where you can
post from Discourse.
Category3 is the only one bridged and is a read-only mirror of the list
archives. The intention with the two previous categories is to test
different bridging methods.
Please help us to test the instance and give your feedback on Discourse
site feedback category or in the ticket.
Cheers
Sophie
--
Sophie Gautier sophi@libreoffice.org
GSM: +33683901545
IRC: soph
Foundation coordinator
The Document Foundation
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- [libreoffice-l10n] Discourse instance to test bridges to mailing lists · sophi
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.