<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.openoffice.nativelanguage">
    <title>gmane.comp.openoffice.nativelanguage</title>
    <link>http://blog.gmane.org/gmane.comp.openoffice.nativelanguage</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9013"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9012"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9011"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9010"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9009"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9008"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9007"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9006"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9005"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9004"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9003"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9002"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9001"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9000"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8999"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8998"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8997"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8996"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8995"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8994"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9013">
    <title>[native-lang-dev] Re: Let's move on</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9013</link>
    <description>&lt;pre&gt;
To complete what Louis wrote: the infrastructure migration will see 
major steps in the next few days/weeks, so even if you are not 
interested in following the evolution of the openoffice.org 
infrastructure it could be useful that you follow
http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/
to make sure that historical (but valuable) content is not lost.

Regards,
   Andrea.
&lt;/pre&gt;</description>
    <dc:creator>Andrea Pescetti</dc:creator>
    <dc:date>2011-12-26T17:24:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9012">
    <title>[native-lang-dev] Re: Migration of OOo mailing lists to Apache</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9012</link>
    <description>&lt;pre&gt;
I've already let you know, but if you need a confirmation now you have it.

I would urge all other active volunteers on this list to help in the 
migration, as a service to our users, who will need a properly managed 
transition of the main N-L support channels (forums, now migrated, and 
mailing lists).

The Italian version is below, but please use it only if I am 
unavailable; otherwise I would prefer to send the notices myself. The 
note has been slightly shortened since I'm already posting regularly 
about the migration, see 
http://openoffice.org/projects/it/lists/utenti/archive/
   ---
Leggete con attenzione questo messaggio, perche' contiene informazioni 
importanti su questa lista e su come continuare ad utilizzarla dopo la 
migrazione ad Apache Foundation.

Nello scorso mese di giugno Oracle ha passato la gestione del codice di 
OpenOffice.org ad Apache Foundation, dove OpenOffice.org e' ora nella 
fase di "incubazione", quella che portera' alla prima release 
nell'infrastruttura di Apache (OOo 3.4.0).

Oltre al codice, e' in corso una migrazione dell'intera infrastruttura, 
che potete seguire alla pagina 
https://cwiki.apache.org/confluence/display/OOOUSERS/OpenOffice.org+Migration+Status

Potete anche seguire il blog del progetto all'indirizzo 
http://blogs.apache.org/OOO/

Tra i servizi che devono essere migrati ci sono anche oltre 300 mailing 
list, tra cui la presente &amp;lt;insert-legacy-mailing-list-name&amp;gt;. Per 
mantenere la vostra iscrizione, dovete seguire queste istruzioni:

    1. Inviare un messaggio vuoto a &amp;lt;subscribe-address-for-new-list&amp;gt;, 
ovviamente dall'indirizzo che volete usare per la mailing list.
    2. Attendere un messaggio di conferma che arrivera' dopo pochi 
minuti, e rispondere a quel messaggio. Basta una risposta vuota, 
l'importante e' cliccare sul tasto "Rispondi" e inviare il messaggio.
    3. La nuova mailing list sara' disponibile all'indirizzo 
&amp;lt;post-address-for-new-list&amp;gt;
    4. Sara' possibile cancellarsi dalla nuova mailing list scrivendo a 
&amp;lt;unsubscribe-address-for-new-list&amp;gt; e confermando come al punto 2.

Per richiedere ulteriori informazioni basta rispondere a questo messaggio.

Note

    1. Evitate di iscrivervi alle nuove liste con un indirizzo 
&amp;lt; at &amp;gt;openoffice.org, non e' chiaro se verranno mantenuti.
    2. Gli archivi delle liste in chiusura rimarranno disponibili su 
http://openoffice.markmail.org/
    3. Gli archivi delle nuove liste saranno su &amp;lt;list-archives-url&amp;gt;
    4. E' possibile anche l'accesso via GMane; nel caso, richiedetelo e 
provvederemo.
   ---
Regards,
   Andrea.
&lt;/pre&gt;</description>
    <dc:creator>Andrea Pescetti</dc:creator>
    <dc:date>2011-11-05T22:20:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9011">
    <title>[native-lang-dev] new Apache OpenOffice.org mail list to replace this list</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9011</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>KS&lt; at &gt;apache.org</dc:creator>
    <dc:date>2011-11-02T16:23:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9010">
    <title>[native-lang-dev] Re: Migration of OOo mailing lists to Apache</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9010</link>
    <description>&lt;pre&gt;Hello!
I mainly translate the template 1 (switching Background and 
Resubscribing parts) to Finnish. Raw text is shown below.

There is five old mailing lists. Only users-list urgently needs Finish 
text I think.
announce&amp;lt; at &amp;gt;fi.openoffice.org 
commits&amp;lt; at &amp;gt;fi.openoffice.org 
dev&amp;lt; at &amp;gt;fi.openoffice.org 
issues&amp;lt; at &amp;gt;fi.openoffice.org  
users&amp;lt; at &amp;gt;fi.openoffice.org  

If there is need for better formatted or otherwise corrected text I am 
willing to try do what I can do.

Regards
Risto Jääskeläinen
OOo localization team in Finland

Subject: OOo-postituslistojen siirto Apachelle

----------------message part start-------------------
Lue tämä tärkeä ilmoitus kokonaisuudessaan ja toimi sitten parhaaksi 
näkemälläsi tavalla. Tässä viestissä on tärkeää tietoa käyttämästäsi 
postituslistasta, sen siirtymisestä Apache Software Foundationin 
alaisuuteen ja siitä, mitä nykyisen listan tilaajan on tehtävä 
varmistaakseen tilauksensa jatkumisen.
Tilauksen jatkaminen
Oraclen on tarjonnut ylläpidon aiemmin käytetyille yli 300 
OOo-postituslistalle, joiden joukossa on myös nyt lukemasi postituslista 
&amp;lt;insert-legacy-mailing-list-name&amp;gt;.
Tilauksen jatkamiseksi sinun on toimittava seuraavasti:
1. Lähetä sähköpostiviesti osoitteeseen 
&amp;lt;subscribe-address-for-new-list&amp;gt;. Käytä lähettämiseen sellaista 
sähköpostitiliäsi, johon haluat listan viestit vastaanottaakin.
2. Saat sähköpostiisi vahvistusviestin, johon sinun pitää vastata, jotta 
tilaus tulee voimaan.
3. Viestien lähettämiseksi uudelle postituslistalle käytät osoitetta 
&amp;lt;post-address-for-new-list&amp;gt;.
4. Mikäli haluat myöhemmin peruuttaa postituslistan tilaamisen, lähetä 
viesti osoitteeseen &amp;lt;unsubscribe-address-for-new-list&amp;gt;.

Toivotamme sinut osallistumaan Apachen OpenOffice.org-projektiin! Jos 
sinulla on kysyttävää, voit lähettää kysymykset (englanniksi) 
osoitteeseen ooo-dev&amp;lt; at &amp;gt;incubator.apache.org.
Taustaa
Oracle luovutti OpenOffice.orgin (OOo) lähdekoodin Apachelle kesäkuussa. 
Apachessa kaikki uudet projektit alkavat "hautomossa". Tässä Apachen 
erityisosassa uudet projektit ("kuoriutujat") ja niiden yhteisöt saavat 
erityishuomiota Apachen "mentoreilta". Näin aloittajille annetaan tietoa 
Apachesta, varmistetaan, että lähdekoodi täyttää Apachen 
lisenssivaatimukset ja ohjataan heitä kohti ensimmäistä Apachen alaista 
julkistusta.

Ennen uuden Apache OpenOffice.org 3.4.0-version julkistusta tarvitaan 
ohjelmointia, mutta samaan aikaan tehdään infrastruktuurin muuttoa 
Sun/Oraclen ylläpitämistä palveluista Apachen palvelimille. Tämä on 
valtava urakka, jota tekevät Apache OpenOffice.org-yhteisö ja Apache 
Infrastructure -työryhmä. Hanke onkin edennyt jo monilla osa-alueillaan.

Lisätietoja siirtymisprojektin etenemisestä saa wiki-sivulta: 
https://cwiki.apache.org/confluence/display/OOOUSERS/OpenOffice.org+Migration+Status
Huomautuksia
1. Suosittelemme, ettet tilaa postituslistaa vanhan 
openoffice.org-sähköpostiosoitteen kautta. Tässä vaiheessa on epävarmaa, 
tuetaanko sitä tulevaisuudessa.
2. Vanhojen postituslistojen arkistot löytyvät sivustolta 
http://openoffice.markmail.org/
3. Uusien postituslistojen arkistot löytyvät sivustolta &amp;lt;list-archives-url&amp;gt;
4. Jos haluat käyttää postituslistaa Gmanen kautta, lähetä pyyntö siitä 
uudelle listalle ja yritämme vastata sinulle.

The Apache OpenOffice.org (Incubating) Project Management Committee
----------------message part end---------------------


__
Saunalahdelta mullistava uutuus Nokia N97 ja kaiken kattava TotaaliMAX nyt ennakkomyynnissä uskomattoman edullisesti! Paketissa puhelut ja viestit (3000 min/kpl/kk), huippunopea mobiililaajakaista sekä Nokia N97 yhdellä kk-maksulla vain 59,95 e/kk (24 kk sopimus).
Katso http://saunalahti.fi/totaalimax

&lt;/pre&gt;</description>
    <dc:creator>Risto I. Jääskeläinen</dc:creator>
    <dc:date>2011-11-01T09:45:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9009">
    <title>[native-lang-dev] Re: Migration of OOo mailing lists to Apache</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9009</link>
    <description>&lt;pre&gt;У чет, 27. 10 2011. у 12:48 +0000, robweir&amp;lt; at &amp;gt;apache.org пише:


Hi Rob,

I am sending you email text that should be posted to the
&amp;lt;dev&amp;lt; at &amp;gt;sr.openoffice.org&amp;gt; mailing list about planed migration to the new
list &amp;lt;ooo-general-sr&amp;lt; at &amp;gt;incubator.apache.org&amp;gt;.

Please give me further instructions if I should post this message to the
wiki or somewhere else.


Message text as follows:


End of the message text.


Best regards,
Goran Rakic
Former Serbian OpenOffice.org
native-language project lead




&lt;/pre&gt;</description>
    <dc:creator>Goran Rakic</dc:creator>
    <dc:date>2011-10-27T15:41:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9008">
    <title>[native-lang-dev] Migration of OOo mailing lists to Apache</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9008</link>
    <description>&lt;pre&gt;The legacy OpenOffice.org servers have been hosted by Oracle.  These
servers will soon be shut down.  We are working to re-host the most
important websites and services at Apache.  This includes the most
critical mailing lists.

We are sending notes to the individual mailing lists, inviting them to
join the matching Apache OpenOffice lists.  You can read a copy of this
email here:

https://cwiki.apache.org/confluence/display/OOOUSERS/Email+Migration+Po
st

As you can see, this email is in English.  We would like to send a
similar note, translated into the native language, for the various NLC
project lists.We need help with these translations and with helping
subscribers migrate over to the Apache list infrastructure.  

If you can help with this, to be a liaison between an NLC project and
Apache OpenOffice, please let me know.

Thanks,

Rob (Apache OpenOffice.org (Incubating) Project Management Committee)
&lt;/pre&gt;</description>
    <dc:creator>robweir&lt; at &gt;apache.org</dc:creator>
    <dc:date>2011-10-27T12:48:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9007">
    <title>[native-lang-dev] Re: [discuss] OpenOffice.org Product Roadmap: made by whom ? was: Re: remove of binfilter module</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9007</link>
    <description>&lt;pre&gt;Hi Martin and all,

Thank you, Martin, for posting this to dev&amp;lt; at &amp;gt;native-lang.openoffice.org
:)

As OpenOffice.org Japanese Language Project is planning to make an
announcement on announce&amp;lt; at &amp;gt;ja.open.office.org about the accepted
proposal &amp;lt;http://wiki.apache.org/incubator/OpenOfficeProposal&amp;gt; which I
translated into Japanese
&amp;lt;http://wiki.apache.org/incubator/OpenOfficeProposal/ja&amp;gt;, we would
like to include Team OpenOffice.org e.V.'s plan or preparation in our
announcement.

On Fri, Jun 17, 2011 at 1:39 AM, Martin Hollmichel
&amp;lt;martin.hollmichel&amp;lt; at &amp;gt;googlemail.com&amp;gt; wrote:

Right.  And we have to tell community members, users, companies, local
governments and organizations about our perspective.


I agree with you.  And we have to tell them and listen to them about
future of the product.


What has Team OOo prepared so far?
What is the link Team OOo will offer?

Thanks,
khirano
&lt;/pre&gt;</description>
    <dc:creator>Kazunari Hirano</dc:creator>
    <dc:date>2011-06-27T10:44:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9006">
    <title>[native-lang-dev] OpenOffice.org Product  Roadmap: made by whom ? was: Re: [discuss] remove of binfilter module</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9006</link>
    <description>&lt;pre&gt;Hi Sam,
yes, I have.

First, I do not have any problems with the Apache style of decision
making, lazy consensus sounds perfectly reasonable to me. I like that
style. This fits perfectly to the "meritocracy" principle.

My understanding is, that this principle is based on
* contributing individuals
* organizations/institutions contributing developers and/or money for
the infrastructure/governance, these organizations contribute because
they have derived products or other business around the regarding software.
So users are represented in this model by own work power or indirectly
by companies.
This principle has been proven to work quite well for many open source
projects.

I think this principle may get enhanced by enabling a non profit
organization to have their own resources on a project (This might fit
into the Apache philosophy considering this organization as an
contributing institution). I think this is necessary because there is
already a lot of business happening around OpenOffice, but most of these
businesses are just to small or have not the right expertise to execute
on the "meritocracy" principle.
So what the OOo project missed most was to have a path to get product
feature or tasks done (or just 4th level support) with the help of money
offered.

So my proposal is continue project decisions the Apache Style but also
to find a framework to make product decisions in a manner that also the
concerns of Users, local communities, QA, business partners, etc. get
honored. This framework also should enable to collect money so that
development (committer) resources can be found to get the issues
addressed in an equitable process.

We already have thousands of feature requests and enhancements in the
queue, we are putting a new bunch of requirements on top of it through
the current transition to Apache, I think we should seek the power of
_all_ OOo communities, users and businesses to achieve significant
growth to make OOo a better and successful product. And I did not even
included wishes like ODF Viewers, mobile and Cloud services around OOo.

My offer is to develop (with all concerned parties) a new charter for
all the groups mentioned above (as a successor of the Community Council
Charter) and enable the project to have own development resources. The
non profit organization Team OpenOffice.org e.V. played in the past just
the role of being the cash box of the CC in a quite defensive way
(http://download.openoffice.org/contribute.html, will you find the path
to donate ??), now Team OOo is preparing to offer a link between
business, communities, users and developers to enable growth on the new
futile ground we are now moving on.

Martin




&lt;/pre&gt;</description>
    <dc:creator>Martin Hollmichel</dc:creator>
    <dc:date>2011-06-16T16:39:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9005">
    <title>[native-lang-dev] Re: Fwd: [marketing-dev] Why TDF should be the place for one united Community</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9005</link>
    <description>&lt;pre&gt;
OK, let's stick to these topics then. The last information we had from
Oracle dates from more than one month ago, and was about turning
OpenOffice.org into a "purely community-based project": vague at least,
since it said nothing about what Oracle's commitment in terms of
workforce would be in future.

Since then, the only things I can see are a noticeable slowdown (albeit
not a complete stop) in development and a general lack of response to
community requests.

Dozens of Italian translators are still waiting for the l10n build
scheduled for May 5th and postponed to May 12th on May 9th, see
http://wiki.services.openoffice.org/wiki/OOoRelease34 and I'd like to
reassure them that their work won't be lost.

Everybody would like to know if, after releasing a very impressive,
solid, innovative 3.4 beta release, the OpenOffice.org projects is going
to release 3.4 stable, and if there is a timeframe for it.


Sure, but we can't have a proper discussion unless we get to know what
Oracle means by "purely community-based project" and especially about
its involvement and investments in the project: the experienced
StarDivision/Sun/Oracle developers cannot be replaced without a huge
technical loss for the project, and knowing whether we can still count
on them affects the whole discussion.

Regards,
  Andrea Pescetti - Italian N-L Project Lead.

&lt;/pre&gt;</description>
    <dc:creator>Andrea Pescetti</dc:creator>
    <dc:date>2011-05-27T22:17:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9004">
    <title>[native-lang-dev] Re: Fwd: [marketing-dev] Why TDF should be the place for one united Community</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9004</link>
    <description>&lt;pre&gt;hi all,

On 2011-05-26, at 17:34 , Simon Brouwer wrote:


I don't wish to be misunderstood. My point is not that having a good discussion about OpenOffice.org is out of the question here, on OOo lists. I find that fine, and the location quite proper. But such a discussion ought to be—must be—about OOo, its NLCs, its contributors, its goals, its options. Such a discussion, in other words is not really about TDF or LO, and to understand our options as only being one or the other is really to cut short what could otherwise be a really healthy reassessment of opportunities. 

Naturally, I also believe that any discussion in which we begin to lay out approaches to the future of OOo development—and there is a future—really needs to be done carefully, as it's *easy* to be misunderstood by others, however good willing they be, when the context is so very charged. 

-louis



&lt;/pre&gt;</description>
    <dc:creator>Louis Suarez-Potts</dc:creator>
    <dc:date>2011-05-27T03:48:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9003">
    <title>[native-lang-dev] Re: Fwd: [marketing-dev] Why TDF should be the place for one united Community</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9003</link>
    <description>&lt;pre&gt;Op 26-5-2011 21:39, Louis Suarez-Potts schreef:
Why not? What better place than the OOo lists for discussion how to 
proceed with our project. It's been too silent in the discussion lists, 
people appear hit by fear, uncertainty and doubt, the project is dead in 
the water. After Oracle giving up, where are we standing? For instance, 
are we still able to release version 3.4?

&lt;/pre&gt;</description>
    <dc:creator>Simon Brouwer</dc:creator>
    <dc:date>2011-05-26T21:34:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9002">
    <title>[native-lang-dev] Re: Fwd: [marketing-dev] Why TDF should be the place for one united Community</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9002</link>
    <description>&lt;pre&gt;I think we are aware enough of Florian's post. :-)

As I mentioned a couple of days ago on the marketing list, I would much rather have a neutral space made available for this sort of discussion, and do not want OOo lists to be dominated by this sort of post. If someone wants to suggest a neutral space, that's great: go ahead. 

best
Louis


On 2011-05-26, at 10:24 , Volker Merschmann wrote:


&lt;/pre&gt;</description>
    <dc:creator>Louis Suarez-Potts</dc:creator>
    <dc:date>2011-05-26T19:39:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9001">
    <title>[native-lang-dev] Fwd: [marketing-dev] Why TDF should be the place for one united Community</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9001</link>
    <description>&lt;pre&gt;Hi,

I am forwarding this also to this list as there had been zero response
on discuss&amp;lt; at &amp;gt;openoffice.org and dev&amp;lt; at &amp;gt;openoffice.org.
As there have been some answers on dev&amp;lt; at &amp;gt;marketing, please follow-up there.

Thx

Volker


---------- Forwarded message ----------
From: Florian Effenberger &amp;lt;floeff&amp;lt; at &amp;gt;documentfoundation.org&amp;gt;
Date: 2011/5/25
Subject: [marketing-dev] Why TDF should be the place for one united Community
To: dev&amp;lt; at &amp;gt;marketing.openoffice.org


Hello everyone,

I have not been subscribed to this list for months, but due to Louis'
recent Cc, I was made aware of the discussion going on -- so, as a
representant of TDF, but also as someone for whom personally the
community means a lot, let me say a few words.

I indeed see the current situation as an ideal basis for uniting
things. The diversity the Community is in now doesn't help anyone. If
you now think we, TDF, are happy and get satisfaction out of the
current situation, you are terribly wrong. Even if we expected
something like that to happen, our intention was to safeguard the
project from this eventuality, not to profit from it.

We all have similar goals: a free office suite, available to everyone.
So let's not discuss about the past, about what has happened and about
the reasons that led to this, but rather focus on the future.

I want to openly repeat our invitation to everyone to join The
Document Foundation and the LibreOffice Community. Why do I think that
we are the right place to continue the work?

In yesterday's blog post, we summed up where we stand, and reading it
will help to understand the current situation:


http://blog.documentfoundation.org/2011/05/24/updates-on-the-foundation/

1. We are vendor neutral. I am sorry that I have to object to Louis'
statement of us being a proxy for Microsoft -- nothing can be further
from the truth. I must confess, that by statements like these, I feel
even personally insulted. I spend many hours per day on a pure
volunteer basis, and if anyone can point on those of my doings that
are proxying for Microsoft, I would be interested to hear them.
Otherwise, I'll ask to stop spreading those wrong assumptions -- as
they are simply that: wrong.

2. We have a strong legal backing, not only by the German nonprofit
"Freies Office Deutschland e.V.", but also by the Software in the
Public Interest (SPI), and we are on track with establishing the
Foundation as a legal entity. Even right now, we have all options
needed for dealing with legal aspects, accepting and spending money.
We already can and do maintain trademarks, brands and other assets.

3. We have an independent infrastructure that works and is not
controlled by nor depends on a single entity. In addition, as we are
not using a fixed web framework, we are very flexible in what we do.

4. We have not only gained a lot of momentum, but also a strong
developer base of more than 200 volunteers, amongst them 40 who
contribute on a very regular basis. Yes, of course, any contribution
corporations with paid developers do are highly welcome and help a lot
&lt;/pre&gt;</description>
    <dc:creator>Volker Merschmann</dc:creator>
    <dc:date>2011-05-26T14:24:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9000">
    <title>[native-lang-dev] L10N delivery deadline</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/9000</link>
    <description>&lt;pre&gt;Hello,
I see on Wiki that deadline is targeted to 04/27/2011.
In french language, we have many strings not translated for 3.4 release.
I had open issue #117851 but still unconfirmed.
What is the process to make a good localization?


&lt;/pre&gt;</description>
    <dc:creator>OOo forum</dc:creator>
    <dc:date>2011-04-25T18:12:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8999">
    <title>[native-lang-dev] Re: New Project Lead role for the Chinese (Traditional) Native-Language team</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8999</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi
On 2011-04-12, at 23:45 , imacat wrote:


I can do that, as I'm the lead of that super-project. I should re-introduce myself, but will do so on another thread.

I'd be curious to learn—also on another thread—why your team found it hard to contribute. If there are problems in that area, I want to resolve them. We've had enough misunderstandings, splits, mistakes and now is—now is always—the time to resolve them.

best
louis

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEVAwUBTaWc2h4a7NiL73tZAQJr8gf+ML3HaFJ5BEFyUVM0dGAAt5b/ian0HhH3
CNwFJS6O17A0owab/yLNHliKrrihWw75pp16ETk6UlwGhPm/1Y79AFU7NMFNZjJM
YnnIXUt6sFWM9mEmvEiuGeMKaLVy/6aiN5+J3/UD/oeQ88ce7eJs4HX6dIsyNYU3
xdOZ5bgtSdFkVIP9e78dGAijp22PmWUNKRACWCKeVkOb0FLF/PxEMWHaHJ7HUUrC
M/R8dQqs61/Y9NcJhlVXX+gfGKaH8jme0cV0wDbfLYjhihb+QzmbBmiLtMulwSAq
Oip6a8s27ifVwqow54cXiM33u20EA0CweFU7NHv8L1rJddSYbJUmag==
=fxu3
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Louis Suarez-Potts</dc:creator>
    <dc:date>2011-04-13T12:53:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8998">
    <title>[native-lang-dev] Re: New Project Lead role for the Chinese (Traditional) Native-Language team</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8998</link>
    <description>&lt;pre&gt;H all,
I'm sorry for the late reply—I was doing some local travelling today.  


On 2011-04-12, at 09:33 , RAFAELLA BRACONI wrote:


Welcome!


Done. Imacat is now an Administrator of the zh.openoffice.org project; she joins some others in this role.

"Administrator" is the same as "project lead" or "project owner." Basically, the role gives you the duty of having duties.



Best,
louis-- 
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe&amp;lt; at &amp;gt;native-lang.openoffice.org
For additional commands send email to sympa&amp;lt; at &amp;gt;native-lang.openoffice.org
with Subject: help

&lt;/pre&gt;</description>
    <dc:creator>Louis Suarez-Potts</dc:creator>
    <dc:date>2011-04-13T04:19:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8997">
    <title>[native-lang-dev] Re: New Project Lead role for the Chinese (Traditional) Native-Language team</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8997</link>
    <description>&lt;pre&gt;    Thank you all.  I'm imacat from Taiawan.  We our Taiwan local
community team urged to contribute to OOo zh-tw translation for years,
and were unable to find a way to do this due to some reason.  Most of
our members are from the educational domain, including teachers,
students and promoters.  OOo is always an important part in our daily
work to promote OSS.  We are very happy that we can work together with
you from now on.  Hope that our joint effort makes OOo flourish.

    Please let me know when we are ready to edit the content.

    Also, Rafaella, could you please also update the information on this
page http://projects.openoffice.org/native-lang.html ?  I missed that.
Thank you very much.

On 2011/4/12 21:33, RAFAELLA BRACONI said:

&lt;/pre&gt;</description>
    <dc:creator>imacat</dc:creator>
    <dc:date>2011-04-13T03:45:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8996">
    <title>[native-lang-dev] New Project Lead role for the Chinese (Traditional) Native-Language team</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8996</link>
    <description>&lt;pre&gt;Dear All,

I would like to officially welcome Imacat in her new project lead role 
for the zh-tw OOo native language team.

&amp;lt; at &amp;gt;Stefan/Louis: can you please grant her project lead permissions 
including admin access to the zh.openoffice.org web pages?
For Chinese the zh.openoffice.org home page is a single point that hosts 
the links to the Chinese (Simplified) and Chinese (Traditional) pages.
Imacat will take care of the maintenance of the Traditional Chinese ones.

For the more dynamic content, I'd suggest the usage of the 
http://wiki.services.openoffice.org/wiki/Zh-TW .

Thank you in advance for all your efforts!

Kind Regards,
Rafaella

&lt;/pre&gt;</description>
    <dc:creator>RAFAELLA BRACONI</dc:creator>
    <dc:date>2011-04-12T13:33:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8995">
    <title>[native-lang-dev] Re: [qa-dev] BugZilla: Lost old canconfirm-rights re-activated</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8995</link>
    <description>&lt;pre&gt;
Thanks, works for me!

Actually there is still one bug that I cannot modify or see, and it is
http://openoffice.org/bugzilla/show_bug.cgi?id=117513 ; but I assume
this is being kept hidden for some good reasons (security, spam...) and
that's OK with me.

Regards,
  Andrea Pescetti - Italian N-L Project Lead.

&lt;/pre&gt;</description>
    <dc:creator>Andrea Pescetti</dc:creator>
    <dc:date>2011-04-09T08:36:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8994">
    <title>[native-lang-dev] BugZilla: Lost old canconfirm-rights re-activated</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8994</link>
    <description>&lt;pre&gt;Hi,
the old canconfirm-rights in IssueZilla were re-activated on the new 
BugZilla. Means in detail, everyone within the old granted 
canconfirm-group should be enabled to edit every bug on the 
Kenai-BugZilla instance. If you have any issues please let me know,

Thank you,
Frank
--
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe&amp;lt; at &amp;gt;native-lang.openoffice.org
For additional commands send email to sympa&amp;lt; at &amp;gt;native-lang.openoffice.org
with Subject: help

&lt;/pre&gt;</description>
    <dc:creator>Frank Mau</dc:creator>
    <dc:date>2011-04-01T09:58:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8993">
    <title>[native-lang-dev] ssh2key submission for webcontent commits</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.nativelanguage/8993</link>
    <description>&lt;pre&gt;Hi,

I have been asked where one would submit his ssh2key nowadays with the 
new infrastructure in place.

The quick answer is that there is no key needed if you use your 
project's SVN webcontent repository via the https URL.

e.g. you can checkout and commit with your username/password via
https://svn.openoffice.org/svn/de~webcontent or
https://svn.openoffice.org/svn/nl~webcontent or...

If you really prefer to work without password but with public key 
instead you need to add your public key to your profile
http://openoffice.org/projects/help/pages/ProfileSettings#SSH_Keys

Greetings
Stefan
--
-----------------------------------------------------------------
To unsubscribe send email to dev-unsubscribe&amp;lt; at &amp;gt;native-lang.openoffice.org
For additional commands send email to sympa&amp;lt; at &amp;gt;native-lang.openoffice.org
with Subject: help

&lt;/pre&gt;</description>
    <dc:creator>Stefan Taxhet (sonews</dc:creator>
    <dc:date>2011-03-22T17:44:56</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.openoffice.nativelanguage">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.openoffice.nativelanguage</link>
  </textinput>
</rdf:RDF>

