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


On Wed, 13 Sep 2017 at 23:20:36 +0200, Guilhem Moulin wrote:
The next infra call will take place at `date -d 'Tue Sep 19 16:30:00 UTC 2017'`
(18:30:00 Berlin time).

Reminder: that's tomorrow!
 
See https://pad.documentfoundation.org/p/infra for details; agenda TBA.

Here is what we currently have in the pad:                                                          
                                                                          

  * Salt refactoring
    + G. didn't find time to review Brett's branch unfortunately, will try
      to make it happen before LibOCon
    + Refactoring of base/mail vs. tdf/postfix is blocking on rdm#2256 hence
      postponed to after the conference
  * LDAP/SSO
    + deployed LDAP-based auth on the wiki and silverstripe test instances
    + deployed per-service ACLs (groups) for fine-grained access control
    + deployed an internal access log to audit DIT modifications and auth
      attempts
  * Pootle migration
  * LibOCon preparation

-- 
Guilhem.

-- 
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

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.