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

It might help if each list focussed on working in it's own area.  For example 
there is a design team so marketting could send discussions about design to that 
team.  The same for website.  It doesn't make sense for the documents team to 
take over details of running the website when the website team is doing that.  
Similarly for these discussions about strategy and overview = do they really 
belong in marketing?
Regards from
Tom :)

From: Marc Paré <>
Sent: Tue, 4 January, 2011 6:45:56
Subject: [libreoffice-marketing] Re: Release tasks for Marketing

Le 2011-01-04 01:09, Sophie Gautier a écrit :
Hi Marc,
On 04/01/2011 03:49, Marc Paré wrote:

Would it also be a good idea to have monthly reports on achieved goals
from the different groups? We would then have a report giving a short
detailed list of what the membership had achieved throughout the month.
This information could then be used for SC tracking purposes as well as
short/long range planning. This information would also be important in
gauging our growth ability dependent on our work results and membership

We could also use this information in our marketing section where we
could add, where applicable, any details to our feature list. This would
be a kind of collection pot of details that could be used by different
arms of LibreOffice and to bring everyone up to speed as to what has
been happening from the contributors.

We would not have to make it a microscopic report, but just a short
overview of the month's achievements.If more details were needed, then
this could be provided by one of the section's leads (there are always
2-3 members who seem to be in the "total know" of the group's work).

Yes, that would be a good idea, see this with the marketing team and the
other teams.
But what might be the most important is to find somebody to do it, we
have no leads (fortunately!) in our project, only people doing things,
but they may be to busy to do more actually.

I'm only tracking what is mandatory for the release date. From what I
see, there is a lot of discussions every where but very few done on what
is needed to be done *now* if we release sometime in the next 10 days.

Kind regards

Yes, maybe we could suggest this for the next release. This would be a 
great entry level task for someone who would seriously want to 
familiarize her/himself with teams.

I'll try to bring it up again after the release.



Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***

Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


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.