Date: prev next · Thread: first prev next last
2022 Archives by date, by thread · List index

Hi Sophie,

I prefer the mailing list. I can download all mails and then I can
answer/read them offline, e. g. during a train run or just sitting on a
bench in a park and enjoy the nice weather. The internet connection is
not always well. So I would have problem to anwser/read the mails then.
If I am back at home, I can send the anwsered mails. I use Thunderbird
for the mails. In this program I can mark them with different tags. This
is very useful for me.

Annabelle Wübbelsmann

Member of the German translation team
Hi all,

Of course this applies to the l10n group too. So big question :) would
you be interested in using Discourse instance instead of the mailing
list? what is your opinion? what advantages would that bring to us?

Le 28/04/2022 à 15:50, sophi a écrit :
Hi all,

As you are aware, we are conducting a test on Discourse to move on
some mailing lists. It is not possible to bridge mailing lists and
have a Nabble like gateway.

Here are the options:

- have a Discourse category only hosting a project (like
Documentation, UX/Design). Contributors can post directly in the forum
or follow the discussion and participate via notifications (received
by mail). Subscribers to the mailing list can be mass subscribed to
Discourse and the mailing list will be closed

- for Native Language Projects: we could have the same as above with
sub categories per sub projects, see for example pt-BR who has Docs -
Qualidade - Geral as sub categories

- have both mailing list and the corresponding Discourse category with
no cross communication channel between the two.

- have Discourse read-only category mirroring a mailing list for
example the Announce lists.

- have only a mailing list and nothing on Discourse.

- for users@mailing lists, we won't create a user category on
Discourse Community because it will be redundant with the Discourse
Ask instance. So either you keep the mailing lists or if your language
is not yet there, we create a corresponding category on Ask.

This decision shall be taken by project and by each native language
community. For example the Brazilian and the Spanish communities have
already decided to go to the first option (Discourse only). It seems
that Documentation will have both for the moment.

Discourse Community test instance is here:
Please have a look at the archives we imported and let us know if you
see issues or if you want to see how it works for your project.

Redmine ticket with all the details:
(and a *big thanks* to Guilhem for all his great work on this)
Please read
and further on archives migration.

How to proceed next?
Discuss with your project or your native language community and let us
know what you decided among the above options. I've set the reply to
this mail to go on the website list.

When you let us know your decision, I'll send you another mail
containing several questions about the migration type we need to
proceed (mass subscribing list subscribers to the forum, import
archive or not, retain addresses, etc.)

We would like to launch the instance at the beginning of June (as some
communities are really impatient after the test ;) but of course if
you are not decided at that moment, it's still possible to create new
categories once the instance is in production.

Don't hesitate to come back to me if you have questions.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.