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


Hi there,

We now have a second Discourse site at https://community.documentfoundation.org/
which we aim to use as a discussion platform and optional complement /
replacement for public mailing lists.  See Sophie's announcement message at
https://listarchives.tdf.io/i/gSTx-FM1v85zgOVNSSUPIsRW and the Redmine
ticket at https://redmine.documentfoundation.org/issues/3567#note-15 for
background.

So what to do about website@g.l.o?  Should we keep it as is or import
archives to Discourse and close the list?  (Note that in the later case
it'll still be possible to post and reply by email.  But the “primary”
workflow will be web-based not email-based.)  Personally I'm quite
comfortable with the existing email-based workflow and I'm happy to keep
things as is since it means less work for me :-)  But if folks here
think moving over to Discourse would improve visibility and
participation I'm open to that.  The one thing I don't want is to keep
the list *and* open a category on Discourse — it'll only duplicate
things and dilute information.

-- 
Guilhem.

-- 
To unsubscribe e-mail to: website+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/website/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


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.