[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-marketing] LibreOffice events on the wiki - cleaning up duplicated content?

Hi Robinson, everyone,

On 16/08/2017 17:09, Robinson Tryon wrote:
> Perhaps all events should start as an entry on the calendar with date,
> time, location, title, and a blurb. If we need to keep track of any
> additional information for an event -- e.g. for a hackfest or
> conference with volunteers -- we can create a wiki page for it, and
> link it with the event on the calendar.

Yes, that makes sense to me.

> The top-level Events page on the wiki currently displays a handy
> overview of all the events for the year, broken down by region. If
> that table could be automatically generated from the calendar entries,
> that'd be really slick!

That would be great -- although I've been investigating this and it
doesn't look possible, at least without a lot of work. We can get the
calendar data in .ics format, but I haven't found a MediaWiki method or
extension to process the content.

If anyone else has any ideas, let me know...


To unsubscribe e-mail to: marketing+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/marketing/
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.