Hi,
Daniel Gonzalez wrote on 2011-03-22 23.38:
It seems so far that they are interested in having a planet in its
language are
FR
ES
PT-BR
what the next step in defining the planet for each language?
I'll let Sophie coordinate, but from a technical perspective, I need the
following in exactly (!) this format: a RSS or Atom feed of the Blog,
including the category if applicable, and the name of the blog.
Just a few examples out of the current configuration:
==
[http://blog.thebehrens.net/category/libreoffice/feed/atom/]
name = Thorsten Behrens
[http://sophiegautier.com/blog/rss.php]
name = Sophie Gautier
[http://blogs.linux.ie/caolan/b2rss2.php]
name = Caolan McNamara
[http://libobil.blogspot.com/rss.xml]
name = André Schnabel
[http://standardsandfreedom.net/index.php/category/ooo-postings/feed/]
name = Charles Schulz
==
It is important that we
1. need the feed, not the blog URL itself
2. if the blog has various topics, a dedicated feed only with LibO/TDF
posts would be appreciated
Florian
--
Florian Effenberger <floeff@documentfoundation.org>
Steering Committee and Founding Member of The Document Foundation
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Skype: floeff | Twitter/Identi.ca: @floeff
--
E-mail to projects+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://listarchives.libreoffice.org/www/projects/
All messages you send to this list will be publicly archived and cannot be deleted
Context
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.