I'm taking the easy way out and responding to everyone on the list this way.
So, it sounds like there are no real disagreements on the concept other
than the time it would take for people to maintain such a calendar.
Here are my thoughts after reading all of the responses:
NOTE: I maintain the "Events Calendar" (found in the "About Us" section
of our website) and I really only spend, at the most, maybe 15 minutes a
week or two updating the calendar. I also cruise ALL of the EN lists;
the FR, ES users/discuss lists; DE discuss list -- for any mention of
any events that I may have missed. The BR-PT is very vocal about any
events happening in Brazil and the community participate very well on
our Marketing pages -- so there is no real need to monitor their list
(besides, my PT is awful).
So the time spent at keeping the "Events Calendar" is quite small. The
only worry I have is that Florian is the other admin (he is quite busy
with important TDF/LibreOffice work) and we should really have one more
member offer to help out -- one extra person would guarantee the
continuation of the Events calendar page should one of us drop out of
the admin role. Lift your hand up if you are interested! [*smile*]
* We should try to keep the admin of the "LibreOffice in the Press"
calendar down to the most basic common denominator for potential admins.
A great many users will have a G-Account and will have already seen/used
a G-Calendar. The learning curve is quite short and we really only need
about a total of 3-4 people to maintain the calendar; if it got busier,
then we could ask for more help. I also think that the marketing team
should take care of the admin/update of these calendar/pages, just as we
have undertaken with the "Events" calendar pages. I would, of course,
offer my help as an admin on the "LibreOffice in the Press" calendar page.
* The "LibreOffice in the Press" would be a calendar where our website
visitors click on a date->copy-paste a link to the original article
website (live links are not yet possible, but I believe Google is
working on making the links live in a later version).
Let's just say that, that particular area would be our "magazine rack"
of TDF/LibreOffice and not every single mention of TDF/LibreOffice would
be mentioned, but, some of the more important ones. If people think that
our choices are too one-sided on this calendar, then, they will
certainly let us know of it -- critics are always vocal.
* we should keep the admin as simple as possible to maximize the number
of potential helpers
Re: Fabian's proposal of a LibreOffice+Zotero combo to do the heavy
lifting: this does sound like quite a great suggestion. We should try to
set it up to see how much work this would involve as well as the
learning curve for admins. I personally would like to see a demo of it,
and maybe decide to use this method to upkeep the calendar page.
But ... in the meantime, we could just go ahead and set up the Google
Calendar for both wiki/Website. We can still keep the wiki "LibreOffice
in the Press" page for others to update, and, the calendar version
admins could keep an eye on the page and update the calendar as changes
are made to the wiki page.
How does that sound?
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
- Re: [libreoffice-marketing] LibreOffice in the Press -- Proposal (continued)
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