Hello,
I have now finalized my draft for the admin meeting this weekend. You
can find it at
http://pad.documentfoundation.org/p/infra
Feedback is highly appreciated!
As you can see, I have put the focus on SaltStack and virtualization
technologies, as I think those are the two main items everyone involved
with infrastructure should be aware of.
As for the remote participation: So far, I have received no feedback on
people's availability, so I have planned it in for the introduction
round in the morning, which sounds like a good match.
In my experience it's really distracting if we have IRC or phone
conferences open during the full meeting, and pretty exhausting for
everyone. Still, I'd like to leave that door open, so we can give it a
try. However, in case it makes the productive work at the weekend
complicated, we will stop it - the remote participation during the
introductory part is promised, however. ;-)
I hope that's a good compromise, and I'm looking forward to your feedback!
Florian
--
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
- [libreoffice-website] admin meeting agenda · Florian Effenberger
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.