Date: prev next · Thread: first prev next last

Hi :)
I agree that monthly would be easier for people to collaborate with.

There is the other way around of people just contributing and if they miss
one deadline for 1 week they hopefully catch the next weeks' issue.  But
people seldom think like that so a monthly release might be easier to cope
with.  Also although a LOT happens in a week it might be better to be a bit
more selective and only include a fairly random smattering of what goes
on.  If people want the full play-by-play then they can join more
mailing-lists/irc channels and this wiki-newsletter migth help pique
people's interest more if it is monthly.

I think it was quite heroic to start it as a Weekly and i think that helped
"get the ball rolling".  I think we need to advertise it more within the
community = and that might be better done monthly rather than weekly to
avoid spamming the mailing-lists tooo often.
Regards from
Regards from
Tom :)

On 8 September 2014 13:00, Charles-H. Schulz <> wrote:

Hello William, Sophie,

Le 08.09.2014 13:49, Sophie a écrit :

Hash: SHA1

Hi William,
Le 08/09/2014 13:40, William Gathoye a écrit :

Hi *,

I've just finished writing the fourth LOWN edition. [1]

Comments are, as always, welcome.

As I wrote in the introduction, I still need to catch up +700
mails (most are technical dev oriented) and summarize the
slides/videos from the LibreOffice conference for LOWN 5.

If you get involved at the conference and had a talk there, please
provide your slides on your blog (if you have any) or any social
network. I'm following the most "influential" on each social
networks, if you published your slides there, I will find them.

They are currently collected on the conference list, and will be
uploaded asap on the conference site, the users track is already
available. Same for the videos.

As a reminder, if you have suggestions of topics non mentioned in
the mailing lists, do not hesitate to put a note in the next issue

Some things on top of my mind:
- - MC elections
- - certification
- - Android tender
- - infra migration

 LOWN basically consists in writing a summary which could be
reused: * for the annual report The Document Foundation has to
provide to German authorities,

the pad will be mostly used for that, so don't hesitate to add your
own infos on it, collecting all in one place is easier for the report

Yes indeed, which prompts me to note that, while I'm thankful for your
work on LOWN, it does not look at all like anything collaborative.
Here are some additional suggestions to make this a community effort and
to improve the content.

+ turn LOWN into a LOMM = montly basis
+ have one set day when the newsletter edition is being started, announce
it to the marketing list, the projects list, the native-lang projects
+ set deadlines to report news and content
+ everything should be done collaboratively on the pad or on the wiki.

 * by the marketing team; * and also by IT news like NextInpact,
Phoronix, etc if they want to cover LibreOffice development.

The newsletter is of primary internal importance, to keep everyone
informed. But it can be used for other purposes, such as to feed some
contextual content to journalists (journalists don't really care about
newsletter, you must bring some specific message to them).

Thank you again for your work,


Kind regards
Version: GnuPG v1


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.