Re: [steering-discuss] Candidacy for Board: Michael Meeks
Sorry, I just want to add this small comment/question to my preceding
posts in this thread:
I have been searching around, and I have not been able to find an
official development roadmap of any kind. For sure, there's detailed
information about planned release dates going far into the future .
But I don't find any information about what changes are planned to the
general architecture of LibreOffice.
If our leading devs stopped coding on LibreOffice tomorrow, not only
would we not have any design documentation explaining how the beast is
architectured and how it works, but we wouldn't have any idea of what
kind of future plans they'd been working on implementing, and how far
they'd advanced in the process.
Does the engineering steering committee have any kind of formal
methodologies, and any kind of formal documents that it maintains?
Or is the future of LibreOffice simply stored in a myriad of post-its
on your computer monitors, and in your minds, and in a tenuous web of
discussion threads on the devs mailing list?
Unsubscribe instructions: E-mail to email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/steering-discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [steering-discuss] Candidacy for Board: Michael Meeks · Cor Nouws
Re: [steering-discuss] Candidacy for Board: Michael Meeks · Tom Davies
Impressum (Legal Info)
: 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