CMS diff: DA.OpenOffice - En komplet fri kontorpakke
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top projekt hos Apache/h2 +Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekt + +Pris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012. + +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter og initativer, annoncerede idag at Apache Open Office er overgået fra Apache kuvøse til at blive et Top-Niveau Projekt (TNP), visende at projektets sanfund og produkt er blevet styret godt og korrekt under ASF udvide demokratiske proces og principper. + +Beståelsen er for OpenOffice et bevis på Apache vejens successfulde skalering fra kuvøse til 'indholds branding' til et meget etableret slut-bruger produkt, sagde ASF vice præsidenten og Apache OpenOffice mentor Ross Gardler. Kuvøse processen tillader erfarne Apache bidragsydere at guide projelt, hjælpe både nye og etablerede OpenOffice bidragsydere at bygge et Apache-stil samfund som er både åbent og fordelt. + +OpenOffice beståelsen er den officielle anerkendelse at projektet er nu i stand til at lede sig selv ikke kun i teknisk henseende, men også i samfunds spørgsmål., sagde Andrea Pescetti, vice præsident hos Apache OpenOffice. 'Apache vejen' og den metoder, som f.eks. at tage hver beslutning i offentligheden med total gennemsigtighed, har tilladt projektet at tiltrække og engagere nye frivillige, og til at vælge og fordele Projekt Ledelses Kommitteen som vil garantere en stabil fremtid for Apache OpenOffice. + +Indledningsvis lavet af Star Division in the 1990's, blev OpenOffice code basen købt af Sun Microsystems in 1999 og senere Oracle Corporation in 2010, inden den blev sendt til The Apache Software Foundation kuvøse i Juni 2011. + +Under udviklings perioden i Apache kuvøsen, har Apache OpenOffice projektet overflyttet næsten 10 million kode linier, tilført utallige udvidelser, og fikset dusinvis af bruger-rapporterede fejl i den populære og gratis produktions pakke. Som tilføjelse, har softwaren modtaget 5 industri priser, rangerende fra individuelle komponent top punkter over top downloading til den bedste open source produktions pakke. + +I Maj 2012 blev Apache OpenOffice v3.4 offentliggjort på 20 sprog (redaktør: den danske er ved kvalitetstesten), og downloaded mere end 20 millioner gange af enkelt personer, firmaer, skoler og statslige institutioner i over 228 lande. Siden det, har projektet arbejdet på nye funktioner, innovationer og releases målsat til først og fjerde kvartal 2013. + +It's really cool at OpenOffice er nu et top-niveau projekt hos Apache, siger Juergen Schmidt, Apache OpenOffice Release Chef. Vi har mødt mange milepæle for at nå denne milepæl: vores første OpenOffice 3.4 release krævede af samfundet ikke bare flytning af koden fra Oracle til apache, men også at udskifte ugyldigt licenserede biblioteker for succesfuldt at møde Apache licens krav. Nu er vores Apache OpenOffice kilde code frit tilgængeligt for projekter og organisationer. + +Vi er meget stolte af denne vigtige milepæl og byder OpenOffice velkommen i vores fold af verdens ledende Apache projekter, tilføjer Gardler. + +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. + +Som med al Apache software, er Apache OpenOffice software released under Apache Licens v2.0, og bliver kontrolleret af et selv valgt team af aktive bidragsydere til projektet. En Projekt Ledelses Kommitte (PLK) guidesr Projektets dag-til-dag opgaver, inklusive samfunds udvikling og produkt releases. Information om Apache OpenOffice kilde dode, dokumentation, e-mail lister, dettilhørende resourcer, og veje til at deltage er tilgængelige på http://openoffice.apache.org/. + +Om Apache Software Foundation (ASF) +Etableret i 1999, en helt frivilligt fundament kontrollerer næsten femhundrede ledende Open Source projekter, inklusive
[WWW]: shared ideas and looking for feedback
Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. Regards Juergen
Re: [WWW]: shared ideas and looking for feedback
It would be a good idea to have the same structure and then one directory with country special parts...as you say it makes it easier to maintain, and with the extra directory nobody is limited. jan On 19 October 2012 10:22, Jürgen Schmidt jogischm...@gmail.com wrote: Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. Regards Juergen
Re: [WWW]: shared ideas and looking for feedback
On 10/19/12 10:26 AM, jan iversen wrote: It would be a good idea to have the same structure and then one directory with country special parts...as you say it makes it easier to maintain, and with the extra directory nobody is limited. And I forgot to mention that I would move all existing content that we really want preserve in a backup area not directly linked but available. But new users coming to the page should find a clear page to get information about the product, the download, documentation and help and finally and very important how to participate in the project ;-) Juergen jan On 19 October 2012 10:22, Jürgen Schmidt jogischm...@gmail.com wrote: Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. Regards Juergen
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top projekt hos Apache/h2 +Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekt + +Pris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012. + +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter og initativer, annoncerede idag at Apache Open Office er overgået fra Apache kuvøse til at blive et Top-Niveau Projekt (TNP), visende at projektets sanfund og produkt er blevet styret godt og korrekt under ASF udvide demokratiske proces og principper. + +Beståelsen er for OpenOffice et bevis på Apache vejens successfulde skalering fra kuvøse til 'indholds branding' til et meget etableret slut-bruger produkt, sagde ASF vice præsidenten og Apache OpenOffice mentor Ross Gardler. Kuvøse processen tillader erfarne Apache bidragsydere at guide projelt, hjælpe både nye og etablerede OpenOffice bidragsydere at bygge et Apache-stil samfund som er både åbent og fordelt. + +OpenOffice beståelsen er den officielle anerkendelse at projektet er nu i stand til at lede sig selv ikke kun i teknisk henseende, men også i samfunds spørgsmål., sagde Andrea Pescetti, vice præsident hos Apache OpenOffice. 'Apache vejen' og den metoder, som f.eks. at tage hver beslutning i offentligheden med total gennemsigtighed, har tilladt projektet at tiltrække og engagere nye frivillige, og til at vælge og fordele Projekt Ledelses Kommitteen som vil garantere en stabil fremtid for Apache OpenOffice. + +Indledningsvis lavet af Star Division in the 1990's, blev OpenOffice code basen købt af Sun Microsystems in 1999 og senere Oracle Corporation in 2010, inden den blev sendt til The Apache Software Foundation kuvøse i Juni 2011. + +Under udviklings perioden i Apache kuvøsen, har Apache OpenOffice projektet overflyttet næsten 10 million kode linier, tilført utallige udvidelser, og fikset dusinvis af bruger-rapporterede fejl i den populære og gratis produktions pakke. Som tilføjelse, har softwaren modtaget 5 industri priser, rangerende fra individuelle komponent top punkter over top downloading til den bedste open source produktions pakke. + +I Maj 2012 blev Apache OpenOffice v3.4 offentliggjort på 20 sprog (redaktør: den danske er ved kvalitetstesten), og downloaded mere end 20 millioner gange af enkelt personer, firmaer, skoler og statslige institutioner i over 228 lande. Siden det, har projektet arbejdet på nye funktioner, innovationer og releases målsat til først og fjerde kvartal 2013. + +It's really cool at OpenOffice er nu et top-niveau projekt hos Apache, siger Juergen Schmidt, Apache OpenOffice Release Chef. Vi har mødt mange milepæle for at nå denne milepæl: vores første OpenOffice 3.4 release krævede af samfundet ikke bare flytning af koden fra Oracle til apache, men også at udskifte ugyldigt licenserede biblioteker for succesfuldt at møde Apache licens krav. Nu er vores Apache OpenOffice kilde code frit tilgængeligt for projekter og organisationer. + +Vi er meget stolte af denne vigtige milepæl og byder OpenOffice velkommen i vores fold af verdens ledende Apache projekter, tilføjer Gardler. + +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. + +Som med al Apache software, er Apache OpenOffice software released under Apache Licens v2.0, og bliver kontrolleret af et selv valgt team af aktive bidragsydere til
Re: [WWW]: shared ideas and looking for feedback
On Fri, Oct 19, 2012 at 4:22 AM, Jürgen Schmidt jogischm...@gmail.com wrote: Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. This has certainly been discussed: enforce the same template for NL pages, same look and feel, same base content. But then have a portion of the page be reserved for locale-specific concerns. For example, the Arabic page has a link to Bidi specific issue. Or you might have a locale event or news story. We almost do this today for some languages, but this was based on a one-time copy of the English website. Once the copy is made the sites diverge over time. Truly using a single template, with strings resourced in Pootle, would be ideal. But do you see us integrating with Pootle in a way that allows us to update a webpage without requiring manual steps to extract Pootle resources and bring them into SVN and converted to HTML? This would really need to be automated to work for us. -Rob Regards Juergen
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 1:58 AM, Fernando Cassia fcas...@gmail.com wrote: On Fri, Oct 19, 2012 at 2:01 AM, Alexandro Colorado j...@oooes.org wrote: Found them: :) http://ooocon.kiberpipa.org/media/index-2007.html Excelent resource, thanks. The site is very fast. I´m saturating my FTTH just downloading 3 videos. A good candidate to wget -m -np -k -c http://ooocon.kiberpipa.org/media/; ;) Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? -Rob FC
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. How are the others doing it, do they have commit rights ? rgds jan I. 2012/10/19 Rob Weir robw...@apache.org This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top projekt hos Apache/h2 +Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekt + +Pris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012. + +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter og initativer, annoncerede idag at Apache Open Office er overgået fra Apache kuvøse til at blive et Top-Niveau Projekt (TNP), visende at projektets sanfund og produkt er blevet styret godt og korrekt under ASF udvide demokratiske proces og principper. + +Beståelsen er for OpenOffice et bevis på Apache vejens successfulde skalering fra kuvøse til 'indholds branding' til et meget etableret slut-bruger produkt, sagde ASF vice præsidenten og Apache OpenOffice mentor Ross Gardler. Kuvøse processen tillader erfarne Apache bidragsydere at guide projelt, hjælpe både nye og etablerede OpenOffice bidragsydere at bygge et Apache-stil samfund som er både åbent og fordelt. + +OpenOffice beståelsen er den officielle anerkendelse at projektet er nu i stand til at lede sig selv ikke kun i teknisk henseende, men også i samfunds spørgsmål., sagde Andrea Pescetti, vice præsident hos Apache OpenOffice. 'Apache vejen' og den metoder, som f.eks. at tage hver beslutning i offentligheden med total gennemsigtighed, har tilladt projektet at tiltrække og engagere nye frivillige, og til at vælge og fordele Projekt Ledelses Kommitteen som vil garantere en stabil fremtid for Apache OpenOffice. + +Indledningsvis lavet af Star Division in the 1990's, blev OpenOffice code basen købt af Sun Microsystems in 1999 og senere Oracle Corporation in 2010, inden den blev sendt til The Apache Software Foundation kuvøse i Juni 2011. + +Under udviklings perioden i Apache kuvøsen, har Apache OpenOffice projektet overflyttet næsten 10 million kode linier, tilført utallige udvidelser, og fikset dusinvis af bruger-rapporterede fejl i den populære og gratis produktions pakke. Som tilføjelse, har softwaren modtaget 5 industri priser, rangerende fra individuelle komponent top punkter over top downloading til den bedste open source produktions pakke. + +I Maj 2012 blev Apache OpenOffice v3.4 offentliggjort på 20 sprog (redaktør: den danske er ved kvalitetstesten), og downloaded mere end 20 millioner gange af enkelt personer, firmaer, skoler og statslige institutioner i over 228 lande. Siden det, har projektet arbejdet på nye funktioner, innovationer og releases målsat til først og fjerde kvartal 2013. + +It's really cool at OpenOffice er nu et top-niveau projekt hos Apache, siger Juergen Schmidt, Apache OpenOffice Release Chef. Vi har mødt mange milepæle for at nå denne milepæl: vores første OpenOffice 3.4 release krævede af samfundet ikke bare flytning af koden fra Oracle til apache, men også at udskifte ugyldigt licenserede biblioteker for succesfuldt at møde Apache licens krav. Nu er vores Apache OpenOffice kilde code frit tilgængeligt for projekter og organisationer. + +Vi er meget stolte af denne vigtige milepæl og byder OpenOffice velkommen i vores fold af verdens ledende Apache projekter, tilføjer Gardler. + +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere -
Re: [WWW]: shared ideas and looking for feedback
If pootle used SVN, you would at least have it in SVN automatically :-) jan. On 19 October 2012 13:51, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 4:22 AM, Jürgen Schmidt jogischm...@gmail.com wrote: Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. This has certainly been discussed: enforce the same template for NL pages, same look and feel, same base content. But then have a portion of the page be reserved for locale-specific concerns. For example, the Arabic page has a link to Bidi specific issue. Or you might have a locale event or news story. We almost do this today for some languages, but this was based on a one-time copy of the English website. Once the copy is made the sites diverge over time. Truly using a single template, with strings resourced in Pootle, would be ideal. But do you see us integrating with Pootle in a way that allows us to update a webpage without requiring manual steps to extract Pootle resources and bring them into SVN and converted to HTML? This would really need to be automated to work for us. -Rob Regards Juergen
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
2012/10/19 jan iversen jancasacon...@gmail.com: Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. One thing I didn't mention in the video is we have two main kinds of pages on the website: HTML and mdtext. HTML is HTML, of course. mdtext == Markdown Text, a simplified format that is really easy for simple informational pages with text and headers, lists and hyperlinks. You can read about the syntax here: http://daringfireball.net/projects/markdown/ Or even better, look at a sample page in source: https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/native-lang.mdtext I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. You figured out the web CMS interface, which is a stumbling block for many people. So this is a great start, I think. How are the others doing it, do they have commit rights ? If I'm editing a page or two, I use the same web interface. So what you did was right, except in the syntax. A specific example. You added: +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. But what is really needed is HTML markup, like this: h2Tilgængelighed og Styring/h2 p Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra a href=http://openoffice.org;http://openoffice.org/a. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. /p Does this make sense? You want the diff's to be HTML format as well. The difference for a Committer is they can then check in directly from the web interface, preview how it looks on our staging server, and then publish. Once a page is checked in then the template is applied. Mdtext is converted to HTML, and the HTML is inserted into the skeleton of the template, with standard navigation, headers, footers and other page elements applied. So when you think of a page, concentrate on the content. The rest will come from the template. Regards, -Rob rgds jan I. 2012/10/19 Rob Weir robw...@apache.org This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top projekt hos Apache/h2 +Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekt + +Pris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012. + +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter og initativer, annoncerede idag at Apache Open Office er overgået fra Apache kuvøse til at blive et Top-Niveau Projekt (TNP), visende at projektets sanfund og produkt er blevet styret godt og korrekt under ASF udvide demokratiske proces og principper. + +Beståelsen er for OpenOffice et bevis på Apache vejens successfulde skalering fra kuvøse til 'indholds branding' til et meget etableret slut-bruger produkt, sagde ASF vice præsidenten og Apache OpenOffice mentor Ross Gardler. Kuvøse processen tillader erfarne Apache bidragsydere at guide projelt, hjælpe både nye og etablerede OpenOffice bidragsydere at bygge et Apache-stil samfund som er både åbent og fordelt. + +OpenOffice beståelsen er den officielle anerkendelse at
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
Got it, my failure (it was obvious a bit too late when I made it) I will do a new CMS session after lunch. It seems that mdtext is just an abbreviation of mediaWiki, would life be easy if the gurus of all these different forms could get together and decide on something common. Maybe for us (in the long term) we could simplify thing and e.g. say we use mediaWiki. jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. One thing I didn't mention in the video is we have two main kinds of pages on the website: HTML and mdtext. HTML is HTML, of course. mdtext == Markdown Text, a simplified format that is really easy for simple informational pages with text and headers, lists and hyperlinks. You can read about the syntax here: http://daringfireball.net/projects/markdown/ Or even better, look at a sample page in source: https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/native-lang.mdtext I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. You figured out the web CMS interface, which is a stumbling block for many people. So this is a great start, I think. How are the others doing it, do they have commit rights ? If I'm editing a page or two, I use the same web interface. So what you did was right, except in the syntax. A specific example. You added: +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. But what is really needed is HTML markup, like this: h2Tilgængelighed og Styring/h2 p Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra a href=http://openoffice.org;http://openoffice.org/a. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. /p Does this make sense? You want the diff's to be HTML format as well. The difference for a Committer is they can then check in directly from the web interface, preview how it looks on our staging server, and then publish. Once a page is checked in then the template is applied. Mdtext is converted to HTML, and the HTML is inserted into the skeleton of the template, with standard navigation, headers, footers and other page elements applied. So when you think of a page, concentrate on the content. The rest will come from the template. Regards, -Rob rgds jan I. 2012/10/19 Rob Weir robw...@apache.org This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top projekt hos Apache/h2 +Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekt + +Pris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012. + +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter og initativer, annoncerede idag at Apache Open Office er overgået fra Apache kuvøse til at blive et Top-Niveau Projekt (TNP), visende at projektets sanfund og produkt er blevet styret godt og korrekt under ASF udvide
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 07:53:18AM -0400, Rob Weir wrote: Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? http://support.google.com/youtube/bin/answer.py?hl=enanswer=71673 Regards -- Ariel Constenla-Haile La Plata, Argentina pgp8AjKrC4Jau.pgp Description: PGP signature
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
2012/10/19 jan iversen jancasacon...@gmail.com: Got it, my failure (it was obvious a bit too late when I made it) I will do a new CMS session after lunch. It seems that mdtext is just an abbreviation of mediaWiki, would life be easy if the gurus of all these different forms could get together and decide on something common. Maybe for us (in the long term) we could simplify thing and e.g. say we use mediaWiki. This is the nature of programming, yes? The fame and glory comes form inventing something new, even if not needed. No one ever got promoted for reusing code ;-) -Rob jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. One thing I didn't mention in the video is we have two main kinds of pages on the website: HTML and mdtext. HTML is HTML, of course. mdtext == Markdown Text, a simplified format that is really easy for simple informational pages with text and headers, lists and hyperlinks. You can read about the syntax here: http://daringfireball.net/projects/markdown/ Or even better, look at a sample page in source: https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/native-lang.mdtext I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. You figured out the web CMS interface, which is a stumbling block for many people. So this is a great start, I think. How are the others doing it, do they have commit rights ? If I'm editing a page or two, I use the same web interface. So what you did was right, except in the syntax. A specific example. You added: +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. But what is really needed is HTML markup, like this: h2Tilgængelighed og Styring/h2 p Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra a href=http://openoffice.org;http://openoffice.org/a. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. /p Does this make sense? You want the diff's to be HTML format as well. The difference for a Committer is they can then check in directly from the web interface, preview how it looks on our staging server, and then publish. Once a page is checked in then the template is applied. Mdtext is converted to HTML, and the HTML is inserted into the skeleton of the template, with standard navigation, headers, footers and other page elements applied. So when you think of a page, concentrate on the content. The rest will come from the template. Regards, -Rob rgds jan I. 2012/10/19 Rob Weir robw...@apache.org This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top projekt hos Apache/h2 +Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekt + +Pris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012. + +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 8:38 AM, Ariel Constenla-Haile arie...@apache.org wrote: On Fri, Oct 19, 2012 at 07:53:18AM -0400, Rob Weir wrote: Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? http://support.google.com/youtube/bin/answer.py?hl=enanswer=71673 Cool. That is good to know. Ideally we would go through Youtube's non-profit program, which has additional benefits: http://www.youtube.com/nonprofits It looks like the legal entity (the ASF) must apply, but once that is done we might have a separate account for the AOO project per this: We only allow one membership per organization. However, branches of umbrella organizations that share Employee Identification Numbers (EINs) with their parent organizations are eligible for individual memberships. Branches must indicate that they are applying as a related organization during the application process and go through additional screening. See lower right on this page: http://www.google.com/nonprofits/join/ Would it be worth doing this? If so, what part of Apache would need to be involved? Community development? Communications? -Rob Regards -- Ariel Constenla-Haile La Plata, Argentina
CMS diff: DA.OpenOffice - En komplet fri kontorpakke
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,15 @@ +Hi Rob, + +now I have added the HTML markup, I checked with SVN and index.html is not in mdtext. + +Sorry for the mishap, but thanks for reminding me, instead of just solving it. + +Have a nice day. +Jan. + +Ps. CMS lacks one feature, a possibility to preview the page, that would be nice. + +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +37,54 @@ h2Velkommen til Apache OpenOffice/h2 +h2Apache software Foundation annoncerer Apache OpenOffice™ som et Top-Niveau Projekth2 +pPris vindende førende Open Source produktions pakke bredt brugt i over 228 lande, over 20 millioner download af den seneste version siden maj 2012.br +Forest Hill, MD – 18 Oktober 2012 – Apache Software Foundation (ASF), den udelukkende frivillige udviklere og kuvøser af næsten 150 Open Source projekter +og initativer, annoncerede idag at Apache Open Office er overgået fra Apache kuvøse til at blive et Top-Niveau Projekt (TNP), +visende at projektets sanfund og produkt er blevet styret godt og korrekt under ASF udvide demokratiske proces og principper./p +pBeståelsen er for OpenOffice et bevis på Apache vejens successfulde skalering fra kuvøse til 'indholds branding' til et meget etableret slut-bruger produkt, sagde ASF vice præsidenten og Apache OpenOffice mentor Ross Gardler. Kuvøse processen tillader erfarne Apache bidragsydere at guide projelt, +hjælpe både nye og etablerede OpenOffice bidragsydere at bygge et Apache-stil samfund som er både åbent og fordelt. +OpenOffice beståelsen er den officielle anerkendelse at projektet er nu i stand til at lede sig selv ikke kun i teknisk henseende, +men også i samfunds spørgsmål., sagde Andrea Pescetti, vice præsident hos Apache OpenOffice. 'Apache vejen' +og den metoder, som f.eks. at tage hver beslutning i offentligheden med total gennemsigtighed, har tilladt projektet at tiltrække +og engagere nye frivillige, og til at vælge og fordele Projekt Ledelses Kommitteen som vil garantere en stabil fremtid for Apache OpenOffice./p +pIndledningsvis lavet af Star Division in the 1990's, blev OpenOffice code basen købt af Sun Microsystems in 1999 og senere Oracle Corporation in 2010, +inden den blev sendt til The Apache Software Foundation kuvøse i Juni 2011. +Under udviklings perioden i Apache kuvøsen, har Apache OpenOffice projektet overflyttet næsten 10 million kode linier, +tilført utallige udvidelser, og fikset dusinvis af bruger-rapporterede fejl i den populære og gratis produktions pakke. +Som tilføjelse, har softwaren modtaget 5 industri priser, rangerende fra individuelle komponent top punkter over +top downloading til den bedste open source produktions pakke./p +pI Maj 2012 blev Apache OpenOffice v3.4 offentliggjort på 20 sprog (redaktør: den danske er ved kvalitetstesten), +og downloaded mere end 20 millioner gange af enkelt personer, firmaer, skoler og statslige institutioner i over 228 lande. +Siden det, har projektet arbejdet på nye funktioner, innovationer og releases målsat til først og fjerde kvartal 2013. +It's really cool at OpenOffice er nu et top-niveau projekt hos Apache, siger Juergen Schmidt, Apache OpenOffice Release Chef. +Vi har mødt mange milepæle for at nå denne milepæl: vores første OpenOffice 3.4 release krævede af samfundet +ikke bare flytning af koden fra Oracle til apache, men også at udskifte ugyldigt licenserede biblioteker for succesfuldt at møde Apache licens krav. +Nu er vores Apache OpenOffice kilde code frit tilgængeligt for projekter og organisationer.br +Vi er meget stolte af denne vigtige milepæl og byder OpenOffice velkommen i vores fold af verdens ledende Apache projekter, tilføjer Gardler./p + +h2Tilgængelighed og Styringh2 +pApache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. +Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. +Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, +OpenSocial, og OData.br +Som med al Apache software, er Apache OpenOffice software released under Apache Licens v2.0, og bliver kontrolleret af et selv valgt team af aktive +bidragsydere til projektet. En Projekt Ledelses Kommitte (PLK) guidesr Projektets dag-til-dag opgaver, inklusive samfunds udvikling og produkt releases. +Information om Apache OpenOffice kilde dode, dokumentation, e-mail lister, dettilhørende
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
You are right, even though I have lived a whole life, reusing code and tweaking it to fit my purpose. But honestly the real heroes (and gurus) are who work behind the scenes and get things working. I just had a CMS session, hope you like that better. Jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Got it, my failure (it was obvious a bit too late when I made it) I will do a new CMS session after lunch. It seems that mdtext is just an abbreviation of mediaWiki, would life be easy if the gurus of all these different forms could get together and decide on something common. Maybe for us (in the long term) we could simplify thing and e.g. say we use mediaWiki. This is the nature of programming, yes? The fame and glory comes form inventing something new, even if not needed. No one ever got promoted for reusing code ;-) -Rob jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. One thing I didn't mention in the video is we have two main kinds of pages on the website: HTML and mdtext. HTML is HTML, of course. mdtext == Markdown Text, a simplified format that is really easy for simple informational pages with text and headers, lists and hyperlinks. You can read about the syntax here: http://daringfireball.net/projects/markdown/ Or even better, look at a sample page in source: https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/native-lang.mdtext I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. You figured out the web CMS interface, which is a stumbling block for many people. So this is a great start, I think. How are the others doing it, do they have commit rights ? If I'm editing a page or two, I use the same web interface. So what you did was right, except in the syntax. A specific example. You added: +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. But what is really needed is HTML markup, like this: h2Tilgængelighed og Styring/h2 p Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra a href=http://openoffice.org;http://openoffice.org/a. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. /p Does this make sense? You want the diff's to be HTML format as well. The difference for a Committer is they can then check in directly from the web interface, preview how it looks on our staging server, and then publish. Once a page is checked in then the template is applied. Mdtext is converted to HTML, and the HTML is inserted into the skeleton of the template, with standard navigation, headers, footers and other page elements applied. So when you think of a page, concentrate on the content. The rest will come from the template. Regards, -Rob rgds jan I. 2012/10/19 Rob Weir robw...@apache.org This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html === --- trunk/content/da/index.html (revision 134) +++ trunk/content/da/index.html (working copy) @@ -1,3 +1,4 @@ +Added danish translation to DA page. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html lang=da @@ -25,6 +26,37 @@ h2Velkommen til Apache OpenOffice/h2 + h2Apache Open Office er nu et top
Re: Documentation for writing addins
Hi Christof, On 10/19/12 3:00 PM, Christof Donat wrote: Hi, I am trying to write an addin for AOO writer. Thank google I found a fiew examples for additional calc functions and a bit of interface documentations so I was able to more or less guess how the code for my writer addin should look like. I am sure you have found the DevGuide and the samples in the wiki or the SDK. Nevertheless I would recommend that you subscribe to the ooo-...@incubator.apache.org (in the future a...@openoffice.apache.org) and ask concrete questions there. It's probably easier to answer concrete questions I am assuming that you develop an extension with some UI integration (menu, toolbar) that we call add-on. If yes you should maybe also try the NetBeans plugin that provides a wizard for basic add-ons. But the generated skeleton can be used to add more stuff later on manually. Look at http://wiki.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/Integrating_Components_into_OpenOffice.org and the sub chapter (nav bar on the right side) where you can get more info about ProtocolHanlder and Add-Ons Where I completelly am lost is on the various XML FIles. Is there any document describing the contents of an XCU file and a description.xml? The latter is not that much of a problem, because I can at least get enough of it from some examples I found. The XCU fules are the bug issue. http://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Description_of_XML_Elements I hope this helps a bit Juergen
Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx
On 18.10.2012 14:14, Armin Le Grand wrote: [...] ..but will convert BitmapColor to sal_uInt8 (because there is a inline operator in the class BitmapColor), then casting to sal_uInt32 (since ColorData is a typedef to sal_uInt32) and thus would be wrong. Sigh. Herbert is right, these operators are dangerous. I found two ways: (a) extract RGB by feet from BitmapColor and construct a Color with it (b) use the 'operator Color()' : '== aBitmapColor.operator Color()' Where (a) will need more code, and (b) looks ugly. I tend to (b) currently... Option (c) could be even better: removal of both the dangerous conversion BitmapColor::operator sal_uInt8() and the implicit construction of a BitmapColor from a sal_uInt8. But binfilter depends on their behind the scenes conversions and nobody should or would want to touch binfilter to make it compile again after such a change. Yet another reason to get rid of binfilter... Herbert
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
2012/10/19 jan iversen jancasacon...@gmail.com: You are right, even though I have lived a whole life, reusing code and tweaking it to fit my purpose. But honestly the real heroes (and gurus) are who work behind the scenes and get things working. Yes, I agree. I just had a CMS session, hope you like that better. Thanks. I committed your patch with two changes: 1) It was missing closing tags for the h2 headers. It needs to be: h2My header text here/h2 2) Only put page content in the patch. If you want to add a note to the committers, that should go in the email. I think there is a place for this in the form? I'm not sure. Take a look: http://www.openoffice.org/da/ Regards, -Rob Jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Got it, my failure (it was obvious a bit too late when I made it) I will do a new CMS session after lunch. It seems that mdtext is just an abbreviation of mediaWiki, would life be easy if the gurus of all these different forms could get together and decide on something common. Maybe for us (in the long term) we could simplify thing and e.g. say we use mediaWiki. This is the nature of programming, yes? The fame and glory comes form inventing something new, even if not needed. No one ever got promoted for reusing code ;-) -Rob jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. One thing I didn't mention in the video is we have two main kinds of pages on the website: HTML and mdtext. HTML is HTML, of course. mdtext == Markdown Text, a simplified format that is really easy for simple informational pages with text and headers, lists and hyperlinks. You can read about the syntax here: http://daringfireball.net/projects/markdown/ Or even better, look at a sample page in source: https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/native-lang.mdtext I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. You figured out the web CMS interface, which is a stumbling block for many people. So this is a great start, I think. How are the others doing it, do they have commit rights ? If I'm editing a page or two, I use the same web interface. So what you did was right, except in the syntax. A specific example. You added: +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. But what is really needed is HTML markup, like this: h2Tilgængelighed og Styring/h2 p Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra a href=http://openoffice.org;http://openoffice.org/a. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. /p Does this make sense? You want the diff's to be HTML format as well. The difference for a Committer is they can then check in directly from the web interface, preview how it looks on our staging server, and then publish. Once a page is checked in then the template is applied. Mdtext is converted to HTML, and the HTML is inserted into the skeleton of the template, with standard navigation, headers, footers and other page elements applied. So when you think of a page, concentrate on the content. The rest will come from the template. Regards, -Rob rgds jan I. 2012/10/19 Rob Weir robw...@apache.org This won't work. The existing page is HTML, so the additional text needs to be in HTML as well, including p for paragraphs and a href for hyperlinks, etc. One idea to simplify it would be to have only a tease of the story, maybe a sentence or two, and then link to this page for the full story: http://www.openoffice.org/da/graduation.html -Rob 2012/10/19 jan iversen anonym...@apache.org: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/da%2Findex.html jan iversen Index: trunk/content/da/index.html
Re: CMS diff: DA.OpenOffice - En komplet fri kontorpakke
just a comment on 2), I dont put anything in the patch as such, CMS does that ?? There is a field called header which I thought was for a message, but it obviously is not. So two changes to CMS would be nice: a) possibility to preview the page (making sure all html marking work as it should) b) possibility to add a note to the committer. The page is ok for now, and in a week or two, I would like to push this news into a news list. Thanks for your help. have a nice day Jan I. On 19 October 2012 15:21, Rob Weir robw...@apache.org wrote: 2012/10/19 jan iversen jancasacon...@gmail.com: You are right, even though I have lived a whole life, reusing code and tweaking it to fit my purpose. But honestly the real heroes (and gurus) are who work behind the scenes and get things working. Yes, I agree. I just had a CMS session, hope you like that better. Thanks. I committed your patch with two changes: 1) It was missing closing tags for the h2 headers. It needs to be: h2My header text here/h2 2) Only put page content in the patch. If you want to add a note to the committers, that should go in the email. I think there is a place for this in the form? I'm not sure. Take a look: http://www.openoffice.org/da/ Regards, -Rob Jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Got it, my failure (it was obvious a bit too late when I made it) I will do a new CMS session after lunch. It seems that mdtext is just an abbreviation of mediaWiki, would life be easy if the gurus of all these different forms could get together and decide on something common. Maybe for us (in the long term) we could simplify thing and e.g. say we use mediaWiki. This is the nature of programming, yes? The fame and glory comes form inventing something new, even if not needed. No one ever got promoted for reusing code ;-) -Rob jan. 2012/10/19 Rob Weir robw...@apache.org 2012/10/19 jan iversen jancasacon...@gmail.com: Hi Rob I just followed your youtube video :-) and CMS sent this off, more or less automatically. One thing I didn't mention in the video is we have two main kinds of pages on the website: HTML and mdtext. HTML is HTML, of course. mdtext == Markdown Text, a simplified format that is really easy for simple informational pages with text and headers, lists and hyperlinks. You can read about the syntax here: http://daringfireball.net/projects/markdown/ Or even better, look at a sample page in source: https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/native-lang.mdtext I think it is actually a diff to the existing page, and I thought your idea was quite brilliant since it would allow me and others to update the content easily. You figured out the web CMS interface, which is a stumbling block for many people. So this is a great start, I think. How are the others doing it, do they have commit rights ? If I'm editing a page or two, I use the same web interface. So what you did was right, except in the syntax. A specific example. You added: +Tilgængelighed og Styring +Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra http://openoffice.org. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. But what is really needed is HTML markup, like this: h2Tilgængelighed og Styring/h2 p Apache OpenOffice er tilgængelig gratis for enhver bruger og formål, og kan downloades fra a href=http://openoffice.org;http://openoffice.org/a. Productet downloades et ubegrænset antal gange på¨PC for et ubegrænset antal af brugere - HELT GRATIS fri for alle licens afgifter. Projektet har en stærk fokusering på at støtte open standards, fra ODF (der først implementerede ISO/IEC 26300) til fremtidige planer for CMIS, OpenSocial, og OData. /p Does this make sense? You want the diff's to be HTML format as well. The difference for a Committer is they can then check in directly from the web interface, preview how it looks on our staging server, and then publish. Once a page is checked in then the template is applied. Mdtext is converted to HTML, and the HTML is inserted into the skeleton of the template, with standard navigation, headers, footers and other page elements applied. So when you think of a page, concentrate on the content. The rest will come from the template. Regards, -Rob rgds jan I. 2012/10/19 Rob Weir
Re: OpenOffice graduation: translations of press release
Thank you for your review, we need a good reviewer on documentation too ;-). I've done the corrections and I've pubished it. Regards Juan Carlos El 19/10/2012 7:06, Fernando Cassia escribió: On Fri, Oct 19, 2012 at 2:04 AM, Fernando Cassia fcas...@gmail.com wrote: you need to first remove the underlined words... (I just did it to easily signal what I changed). Sorry, I mean remove the underlined formatting from the changed words. FC
Re: OpenOffice graduation: translations of press release
El 19/10/2012 7:48, Pedro Giffuni escribió: Hi Fernando; Both changes you propose are correct. Unfortunately there are also some other terms (escalada, germen) that just dont fit well and some even that I hadnt heard before (director de liberaciones). Yes, it didn't sound good to me too, but it's not easy to find some word which sound ok without change completely the sentence. You can propose better words or change it by yourself, it is ok for me. :-) Regards Its not Juan Carlos' fault though ... some terms can be OK on some countries and sound horrible in others and being neutral is not easy. Pedro. --- Gio 18/10/12, Fernando Cassia fcas...@gmail.com ha scritto: Da: Fernando Cassia fcas...@gmail.com Oggetto: Re: OpenOffice graduation: translations of press release A: ooo-dev@incubator.apache.org Data: Giovedì 18 ottobre 2012, 23:41 On Thu, Oct 18, 2012 at 8:16 PM, Juan C. Sanz juancsa...@hotmail.comwrote: It's finished and published: http://www.openoffice.org/es/** noticias/graduacion.htmlhttp://www.openoffice.org/es/noticias/graduacion.html Regards Juan Carlos I also don´t think I like suit ... I´d prefer suite de aplicaciones de oficina. As used elsewhere http://goo.gl/SFA8B Just my $0.02. I hope you don´t mind my suggestions... aka constructive criticism... FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto Revolucionario - George Orwell
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 8:55 AM, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 8:38 AM, Ariel Constenla-Haile arie...@apache.org wrote: On Fri, Oct 19, 2012 at 07:53:18AM -0400, Rob Weir wrote: Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? http://support.google.com/youtube/bin/answer.py?hl=enanswer=71673 Cool. That is good to know. Ideally we would go through Youtube's non-profit program, which has additional benefits: http://www.youtube.com/nonprofits It looks like the legal entity (the ASF) must apply, but once that is done we might have a separate account for the AOO project per this: We only allow one membership per organization. However, branches of umbrella organizations that share Employee Identification Numbers (EINs) with their parent organizations are eligible for individual memberships. Branches must indicate that they are applying as a related organization during the application process and go through additional screening. See lower right on this page: http://www.google.com/nonprofits/join/ Would it be worth doing this? If so, what part of Apache would need to be involved? Community development? Communications? I can certainly raise this in ConComm. It's a valid outlet for conference content, in my view at least. Everyone is concerned with the high cost of travel, this is worth exploring. -Rob Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 10:12 AM, Donald Harbison dpharbi...@gmail.com wrote: On Fri, Oct 19, 2012 at 8:55 AM, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 8:38 AM, Ariel Constenla-Haile arie...@apache.org wrote: On Fri, Oct 19, 2012 at 07:53:18AM -0400, Rob Weir wrote: Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? http://support.google.com/youtube/bin/answer.py?hl=enanswer=71673 Cool. That is good to know. Ideally we would go through Youtube's non-profit program, which has additional benefits: http://www.youtube.com/nonprofits It looks like the legal entity (the ASF) must apply, but once that is done we might have a separate account for the AOO project per this: We only allow one membership per organization. However, branches of umbrella organizations that share Employee Identification Numbers (EINs) with their parent organizations are eligible for individual memberships. Branches must indicate that they are applying as a related organization during the application process and go through additional screening. See lower right on this page: http://www.google.com/nonprofits/join/ Would it be worth doing this? If so, what part of Apache would need to be involved? Community development? Communications? I can certainly raise this in ConComm. It's a valid outlet for conference content, in my view at least. Everyone is concerned with the high cost of travel, this is worth exploring. Thanks. And it should be more useful than just conference material. Tutorials, promotional videos, etc., even where unrelated to conferences. -Rob -Rob Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: Documentation for writing addins
Hi Jürgen, Thanks for your answer. I am sure you have found the DevGuide and the samples in the wiki or the SDK. Yes. Nevertheless I would recommend that you subscribe to the ooo-...@incubator.apache.org (in the future a...@openoffice.apache.org) and ask concrete questions there. It's probably easier to answer concrete questions Thanks, I will. I am assuming that you develop an extension with some UI integration (menu, toolbar) that we call add-on. Yes, exactly. If yes you should maybe also try the NetBeans plugin that provides a wizard for basic add-ons. But the generated skeleton can be used to add more stuff later on manually. Sorry, I don't think, I will have the chance to use Netbeans. Even if I had to, I would like to not have to install a pretty huge IDE, that I'd only use to create some project skeletons. Where I completelly am lost is on the various XML FIles. Is there any document describing the contents of an XCU file and a description.xml? The latter is not that much of a problem, because I can at least get enough of it from some examples I found. The XCU fules are the bug issue. http://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Descriptio n_of_XML_Elements That is exactly wht I had not found. Thanks a lot. Christof signature.asc Description: This is a digitally signed message part.
Re: Submission to consultants directory
On Thu, Oct 18, 2012 at 10:06 AM, Russell Ossendryver russ...@worldlabel.com wrote: Name: World Label Inc Country: Global Practice: Other Description: WorldLabel specializes in developing templates for pre-press printing applications with an emphasis on labeling for address, shipping, CD and media, barcoding and mailmerge We create custom templates for all applications along with implementation and instructions for thier use. Website: http://www.worldlabel.com/Pages/openoffice-template.htm Email: cont...@worldlabel.com Phone: 1-914 930 1346 Thanks for the submission. For websites listed in the directory we need them to follow ASF branding/trademark policies. So based on a quick review of your site, I think we'd want three minor changes: 1) The OpenOffice.org logo should link to the www.openoffice.org website 2) The first use of OpenOffice.org should have a (R) indication (registered trademark) 3) At bottom of page where you put your other disclaimers, also put something along the lines of OpenOffice.org is a trademark of the Apache Software Foundation Thanks! -Rob
Re: Bitmap resampling in symphony? review for i121233)
Hello Clarence; Tomaz has acknowleged that the Symphony code is interesting and that it should be enabled by default. It would be great if someone from Symphony takes the initiative: its a good time to start merging those hidden jewels :). Pedro. - Original Message - From: Clarence GUO clarence.guo...@gmail.com To: ooo-dev@incubator.apache.org; Pedro Giffuni p...@apache.org Cc: Sent: Thursday, October 18, 2012 9:24 PM Subject: Re: Bitmap resampling in symphony? review for i121233) HI~ Pedro, The Symphony's code was there quite a long time ago. We need some time to pick up the background knowledge of the code. Then we will give you further information. Thanks BRs Clarence 2012/10/19 Pedro Giffuni p...@apache.org Hello; Thanks to Tomaž Vajngerl we now have lanczos and bicubic resampling for bitmaps. Looking at similar code in the symphony: symphony/trunk/main/vcl/inc/vcl/bitmap.hxx (line 54) ... #define BMP_SCALE_SUPER 0x0004UL ... Which would be in (minor) conflict with the change in BZ i121233. Perhaps someone from Symphony may want to take a look to see if there is something that we should bring from Symphony first and how to better adapt the new code? best regards, Pedro.
Estimating contributors by looking at wiki accounts?
I recently saw another open source project claim that they had over 3000 contributors. They derived this estimate by looking at the number of user accounts they had in their wiki. That is quite clever, I thought. Since we use the same wiki software, I thought I'd check this metric for us. Our wiki says we have over 58,000 user accounts. I know we're doing well, but would it really make sense to claim that we have over 58,000 contributors? I don't think so. I suppose we could look only at accounts where the person has actually contributed edits, or even recent edits. (MediaWiki is a well-known target of registration spam). Although the other project did not seem to filter out inactive or unused accounts, I think the metrics are meaningless unless we do that. What do you think? Or do we even care? -Rob
Re: Estimating contributors by looking at wiki accounts?
I think your idea of filtering out account that actually contributed is a wise thing, especially because our product has many end-users that want to be informed but do not contribute. As a developer I do not care, but thinking of some of the ongoing discussions in other forums (like: nearly nobody contributes to AOO anymore because Apache rules makes it far to difficult and restrictive), makes it worth while to publish a figure on our web, especially a figure saying e.g. during the last year we had xxx active contributors and xx active committers. jan. On 19 October 2012 17:28, Rob Weir robw...@apache.org wrote: I recently saw another open source project claim that they had over 3000 contributors. They derived this estimate by looking at the number of user accounts they had in their wiki. That is quite clever, I thought. Since we use the same wiki software, I thought I'd check this metric for us. Our wiki says we have over 58,000 user accounts. I know we're doing well, but would it really make sense to claim that we have over 58,000 contributors? I don't think so. I suppose we could look only at accounts where the person has actually contributed edits, or even recent edits. (MediaWiki is a well-known target of registration spam). Although the other project did not seem to filter out inactive or unused accounts, I think the metrics are meaningless unless we do that. What do you think? Or do we even care? -Rob
Re: OOoCon videos/material
Does ASF already has a channel? Also is there a way that we can get better quality of sources (i.e. Shotgun noise-cancellation microphone) or simple voice recorder attached to the conference tag that can have a closer, echo-free quality, and post processing to match to the video recording as we move forward. In the past, companies like kiberpippa officially support OOoCon media management. I am not sure if ASF has something like this, however we could plan some process to have a good quality recording. On 10/19/12, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 10:12 AM, Donald Harbison dpharbi...@gmail.com wrote: On Fri, Oct 19, 2012 at 8:55 AM, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 8:38 AM, Ariel Constenla-Haile arie...@apache.org wrote: On Fri, Oct 19, 2012 at 07:53:18AM -0400, Rob Weir wrote: Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? http://support.google.com/youtube/bin/answer.py?hl=enanswer=71673 Cool. That is good to know. Ideally we would go through Youtube's non-profit program, which has additional benefits: http://www.youtube.com/nonprofits It looks like the legal entity (the ASF) must apply, but once that is done we might have a separate account for the AOO project per this: We only allow one membership per organization. However, branches of umbrella organizations that share Employee Identification Numbers (EINs) with their parent organizations are eligible for individual memberships. Branches must indicate that they are applying as a related organization during the application process and go through additional screening. See lower right on this page: http://www.google.com/nonprofits/join/ Would it be worth doing this? If so, what part of Apache would need to be involved? Community development? Communications? I can certainly raise this in ConComm. It's a valid outlet for conference content, in my view at least. Everyone is concerned with the high cost of travel, this is worth exploring. Thanks. And it should be more useful than just conference material. Tutorials, promotional videos, etc., even where unrelated to conferences. -Rob -Rob Regards -- Ariel Constenla-Haile La Plata, Argentina -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 11:41 AM, Alexandro Colorado j...@oooes.org wrote: Does ASF already has a channel? It does: http://www.youtube.com/user/TheApacheFoundation But it not clear whether it is part of the Youtube non-profit program. If it is then we should be able apply for an AOO account as a related organization. -Rob Also is there a way that we can get better quality of sources (i.e. Shotgun noise-cancellation microphone) or simple voice recorder attached to the conference tag that can have a closer, echo-free quality, and post processing to match to the video recording as we move forward. In the past, companies like kiberpippa officially support OOoCon media management. I am not sure if ASF has something like this, however we could plan some process to have a good quality recording. On 10/19/12, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 10:12 AM, Donald Harbison dpharbi...@gmail.com wrote: On Fri, Oct 19, 2012 at 8:55 AM, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 8:38 AM, Ariel Constenla-Haile arie...@apache.org wrote: On Fri, Oct 19, 2012 at 07:53:18AM -0400, Rob Weir wrote: Can we get these all on Youtube? What special status does one need to do more than a short 5 minute video on Youtube? http://support.google.com/youtube/bin/answer.py?hl=enanswer=71673 Cool. That is good to know. Ideally we would go through Youtube's non-profit program, which has additional benefits: http://www.youtube.com/nonprofits It looks like the legal entity (the ASF) must apply, but once that is done we might have a separate account for the AOO project per this: We only allow one membership per organization. However, branches of umbrella organizations that share Employee Identification Numbers (EINs) with their parent organizations are eligible for individual memberships. Branches must indicate that they are applying as a related organization during the application process and go through additional screening. See lower right on this page: http://www.google.com/nonprofits/join/ Would it be worth doing this? If so, what part of Apache would need to be involved? Community development? Communications? I can certainly raise this in ConComm. It's a valid outlet for conference content, in my view at least. Everyone is concerned with the high cost of travel, this is worth exploring. Thanks. And it should be more useful than just conference material. Tutorials, promotional videos, etc., even where unrelated to conferences. -Rob -Rob Regards -- Ariel Constenla-Haile La Plata, Argentina -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Estimating contributors by looking at wiki accounts?
+1 all around. This sounds like it would be more interesting on the ooo-marketing@ list, since it's more about telling the story of who helps make AOO. With a project with as many different kinds of end users as AOO has, accurate stats like these would be good, if you want to go generate them. Plus, I like numbers. 8-) The most useful thing about generating them would be showing exactly how they're generated, with code (if any), and being very clear - as you suggest - at what the specific numbers mean. Openness in the way you generate the details is key to ensuring people know exactly what you're measuring. - Shane P.S. Is there already a chart of auto-upgrade downloads anywhere? Just curious. On 10/19/2012 11:38 AM, jan iversen wrote: I think your idea of filtering out account that actually contributed is a wise thing, especially because our product has many end-users that want to be informed but do not contribute. As a developer I do not care, but thinking of some of the ongoing discussions in other forums (like: nearly nobody contributes to AOO anymore because Apache rules makes it far to difficult and restrictive), makes it worth while to publish a figure on our web, especially a figure saying e.g. during the last year we had xxx active contributors and xx active committers. jan. On 19 October 2012 17:28, Rob Weir robw...@apache.org wrote: I recently saw another open source project claim that they had over 3000 contributors. They derived this estimate by looking at the number of user accounts they had in their wiki. That is quite clever, I thought. Since we use the same wiki software, I thought I'd check this metric for us. Our wiki says we have over 58,000 user accounts. I know we're doing well, but would it really make sense to claim that we have over 58,000 contributors? I don't think so. I suppose we could look only at accounts where the person has actually contributed edits, or even recent edits. (MediaWiki is a well-known target of registration spam). Although the other project did not seem to filter out inactive or unused accounts, I think the metrics are meaningless unless we do that. What do you think? Or do we even care? -Rob
AOO volunteers: essential skills and tasks
I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob
Re: AOO volunteers: essential skills and tasks
That is a BIG +++1 from me. Being a new contributors, I could have saved a lot of stupid questions, had I had a reading list. I have spent quite a number of hours (and that of others too) finding things, everybody knows. It would be good to have 1 wiki page with a suggested reading and items to do (get a wiki account etc.). That page can then later have specialized sub pages depending on the type of volunteer. What really bothers me, is that I waste time for many others, who are very polite in helping me get over the first startwith many new volunteers (assuming I am on average) that is a lot of time, that could have been spent on more fruitful things. I agree however that the wording of the page should be choose well, words like suggested reading are far better for those who take things personally. I will gladly review such a page :-) jan. On 19 October 2012 18:17, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob
Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx
Answering myself: On 19.10.2012 15:19, I wrote: Option (c) could be even better: removal of both the dangerous conversion BitmapColor::operator sal_uInt8() and the implicit construction of a BitmapColor from a sal_uInt8. But binfilter depends on their behind the scenes conversions and nobody should or would want to touch binfilter to make it compile again after such a change. FWIW I just committed revision 1400130 to allow cleanups in header files that are common to the general code base and binfilter without having to touch binfilter. To do this I added a define BINFILTER_COMPAT that is only active when compiling binfilter source files. Be careful when using the define because you need to make sure that the different code paths remain binary compatible. Yet another reason to get rid of binfilter... When we finally get rid of binfilter the macro BINFILTER_COMPAT can be grepped and easily be eliminated again. Herbert
Re: OpenOffice graduation: translations of press release
Hi Andrea, 2012/10/18 Andrea Pescetti pesce...@apache.org We welcome translations of today's press release about the OpenOffice graduation. The English source can be found at https://blogs.apache.org/**foundation/entry/the_apache_** software_foundation_**announces35https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces35 Translations are being listed by Rob at https://blogs.apache.org/OOo/**entry/openoffice_graduates_** from_the_apachehttps://blogs.apache.org/OOo/entry/openoffice_graduates_from_the_apache German and Italian are already available, Japanese is in progress. For other languages, feel free to put a basic HTML file in the localized subdirectories of www.openoffice.org (such as www.openoffice.org/de for German) or, if you don't have access, send the plain text here (not as attachment; in a normal e-mail message) and we will upload it. If you are starting to translate, please send a brief note (Reply All to ooo-dev and ooo-l10n) to avoid overlapping. Her is a french translation of the announce. --- Communiqué de presse Apache OpenOffice du 18.10.2012 L'Apache Software Foundation annonce que le projet Apache OpenOffice ™ est devenu projet Top-Level La principale suite bureautique Open Source est largement utilisée dans 228 pays; avec plus de 20 millions de téléchargements de sa dernière version sortie en mai 2012. Forest Hill, MD - 18 Octobre 2012 - L'Apache Software Foundation (ASF), constituée de développeurs et contributeurs volontaires de près de 150 projets Open Source et initiatives, a annoncé aujourd'hui la promotion du projet incubateur Apache Open Office en projet Top-Level (TLP), signifiant par là que la communauté et le projet ont bien été gérés en accord avec l'approche méritocratique et les principes de l'ASF. La promotion d'OpenOffice témoigne du succès de la méthode Apache pour faire migrer, par un processus d'incubation, des marques en produit utilisateur final de haut niveau a déclaré Ross Gardler, ASF Executive Vice President et mentor Apache OpenOffice. Le processus d'incubation a permis à des contributeurs expérimentés d'Apache de superviser le projet, aidant à la fois les nouveaux contributeurs du projet OpenOffice et les plus expérimentés à construire une communauté de type Apache, à la fois ouverte et diversifiée. La promotion d'OpenOffice constitue la reconnaissance officielle que le projet est maintenant en mesure de s'autogérer non seulement sur le plan technique, mais aussi dans son organisation communautaire, a déclaré Andrea Pescetti, Vice-Président d'Apache OpenOffice. Le ' Apache Way' et ses méthodes, comme la prise de toute décision en public, avec une totale transparence, ont permis au projet d'attirer et d'engager avec succès de nouveaux bénévoles, et d'élire un Project Management Committee, actif et diversifié, en mesure d'assurer un avenir stable à Apache OpenOffice. Initialement créé par la société Star Division dans les années 1990, le code source d'OpenOffice a été acquis par Sun Microsystems en 1999, puis plus tard par Oracle Corporation en 2010, avant d'être cédé en Juin 2011 à l'incubateur de l'Apache Software Foundation. Au cours de sa période de développement dans l'incubateur Apache, le projet Apache OpenOffice a migré près de 10 millions de lignes de code, ajouté de nombreuses améliorations et corrigé des dizaines de bugs signalés par les utilisateurs. En outre, le logiciel a reçu cinq prix, récompensant certaines de ses fonctionnalités ou le citant comme meilleure suite bureautique Open Source téléchargeable. En mai 2012 Apache OpenOffice v3.4 a été mis à disposition dans 20 langues et téléchargé plus de 20 millions de fois par des des utilisateurs privés ou actifs dans des entreprises, l'éducation, et dans des institutions gouvernementales de 228 pays. Depuis lors, le projet a travaillé sur de nouvelles fonctionnalités et innovations et de nouvelles versions sont planifiées pour les trimestres T1 et T4 en 2013. C'est vraiment agréable de voir maintenant OpenOffice promu projet Top-Level chez Apache, a déclaré Juergen Schmidt, Release Manager du projet Apache OpenOffice. Nous avons rencontré de nombreuses difficultés pour atteindre ce statut: notre première version Apache OpenOffice 3.4 ne s'est pas limitée à un simple déplacement de code des serveurs Oracle vers ceux d'Apache, mais a nécessité le remplacement de librairies aux licences incompatibles avec les exigences d'Apache en matière de licence. Maintenant, notre code source Apache OpenOffice est disponible pour d'autres projets et organisations. Nous sommes extrêmement fiers de cette étape importante et souhaitons la bienvenue à OpenOffice dans notre liste Apache de projets mondiaux de premier plan, a ajouté Gardler. Disponibilité et perspectives Apache OpenOffice est disponible gratuitement pour tout utilisateur et tout projet d'utilisation, et peut être téléchargé à partir http://openoffice.org. Le produit peut être téléchargé
Re: Estimating contributors by looking at wiki accounts?
On Fri, Oct 19, 2012 at 12:09 PM, Shane Curcuru a...@shanecurcuru.org wrote: +1 all around. This sounds like it would be more interesting on the ooo-marketing@ list, since it's more about telling the story of who helps make AOO. With a project with as many different kinds of end users as AOO has, accurate stats like these would be good, if you want to go generate them. Plus, I like numbers. 8-) The most useful thing about generating them would be showing exactly how they're generated, with code (if any), and being very clear - as you suggest - at what the specific numbers mean. Openness in the way you generate the details is key to ensuring people know exactly what you're measuring. I think Mwiki has REST API that gives XML out. But I'd need to check. - Shane P.S. Is there already a chart of auto-upgrade downloads anywhere? Just curious. Not yet. But it is something I've been trying to figure out. SourceForge numbers don't report it, but if you correlate the SF numbers with the website numbers from Google Analytics (we send users to a special update URL) I think we can estimate it. But getting charts means I need to figure how to automate it on both the GA and SF sides. But note that AOO 3.4.0 shipped with auto-update checking *disabled* by default (Doh!). So the AOO 3.4.0 -- 3.4.1 auto update numbers there are going to be modest compared to the numbers from OOo 3.3.0 users upgrading to AOO 3.4.x. Of course, many users will hear about the new releases via other means. We see that in the strong AOO 3.4.1 download numbers. -Rob On 10/19/2012 11:38 AM, jan iversen wrote: I think your idea of filtering out account that actually contributed is a wise thing, especially because our product has many end-users that want to be informed but do not contribute. As a developer I do not care, but thinking of some of the ongoing discussions in other forums (like: nearly nobody contributes to AOO anymore because Apache rules makes it far to difficult and restrictive), makes it worth while to publish a figure on our web, especially a figure saying e.g. during the last year we had xxx active contributors and xx active committers. jan. On 19 October 2012 17:28, Rob Weir robw...@apache.org wrote: I recently saw another open source project claim that they had over 3000 contributors. They derived this estimate by looking at the number of user accounts they had in their wiki. That is quite clever, I thought. Since we use the same wiki software, I thought I'd check this metric for us. Our wiki says we have over 58,000 user accounts. I know we're doing well, but would it really make sense to claim that we have over 58,000 contributors? I don't think so. I suppose we could look only at accounts where the person has actually contributed edits, or even recent edits. (MediaWiki is a well-known target of registration spam). Although the other project did not seem to filter out inactive or unused accounts, I think the metrics are meaningless unless we do that. What do you think? Or do we even care? -Rob
Re: [WWW]: shared ideas and looking for feedback
On Fri, Oct 19, 2012 at 1:22 AM, Jürgen Schmidt jogischm...@gmail.comwrote: Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. Definitely good ideas. A defined structure for all areas would be very useful. Do we need to start a wiki page to further elaborate, or should we just go ahead with the press area for now? Opinions? 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. Regards Juergen -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: Estimating contributors by looking at wiki accounts?
Sent from my iPhone On 19/ott/2012, at 18:37, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:09 PM, Shane Curcuru a...@shanecurcuru.org wrote: +1 all around. This sounds like it would be more interesting on the ooo-marketing@ list, since it's more about telling the story of who helps make AOO. With a project with as many different kinds of end users as AOO has, accurate stats like these would be good, if you want to go generate them. Plus, I like numbers. 8-) The most useful thing about generating them would be showing exactly how they're generated, with code (if any), and being very clear - as you suggest - at what the specific numbers mean. Openness in the way you generate the details is key to ensuring people know exactly what you're measuring. I think Mwiki has REST API that gives XML out. But I'd need to check. - Shane P.S. Is there already a chart of auto-upgrade downloads anywhere? Just curious. Not yet. But it is something I've been trying to figure out. SourceForge numbers don't report it, but if you correlate the SF numbers with the website numbers from Google Analytics (we send users to a special update URL) I think we can estimate it. But getting charts means I need to figure how to automate it on both the GA and SF sides. I'll be happy to help with that, early next week I ll have a look at that. Roberto But note that AOO 3.4.0 shipped with auto-update checking *disabled* by default (Doh!). So the AOO 3.4.0 -- 3.4.1 auto update numbers there are going to be modest compared to the numbers from OOo 3.3.0 users upgrading to AOO 3.4.x. Of course, many users will hear about the new releases via other means. We see that in the strong AOO 3.4.1 download numbers. -Rob On 10/19/2012 11:38 AM, jan iversen wrote: I think your idea of filtering out account that actually contributed is a wise thing, especially because our product has many end-users that want to be informed but do not contribute. As a developer I do not care, but thinking of some of the ongoing discussions in other forums (like: nearly nobody contributes to AOO anymore because Apache rules makes it far to difficult and restrictive), makes it worth while to publish a figure on our web, especially a figure saying e.g. during the last year we had xxx active contributors and xx active committers. jan. On 19 October 2012 17:28, Rob Weir robw...@apache.org wrote: I recently saw another open source project claim that they had over 3000 contributors. They derived this estimate by looking at the number of user accounts they had in their wiki. That is quite clever, I thought. Since we use the same wiki software, I thought I'd check this metric for us. Our wiki says we have over 58,000 user accounts. I know we're doing well, but would it really make sense to claim that we have over 58,000 contributors? I don't think so. I suppose we could look only at accounts where the person has actually contributed edits, or even recent edits. (MediaWiki is a well-known target of registration spam). Although the other project did not seem to filter out inactive or unused accounts, I think the metrics are meaningless unless we do that. What do you think? Or do we even care? -Rob -- This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: Marketing events: Brochure? Newsletter?
On Tue, Oct 9, 2012 at 6:19 PM, Nancy K nancythirt...@yahoo.com wrote: Hi! I have been keeping up with the discussions, but unable to participate much lately, unfortunately. In the marketing department, is there a newsletter or brochure that could be distributed at any event? I am thinking that a design could be approved, then placed on the website so that anyone representing Apache OpenOffice could print it out. This might be an example of a way to fund an event - using funds for the paper and ink or professional printing. The vote to offer funds for an event could be proposed for approval or disapproval. If approved the design posted could be in a file format that could be printed directly or sent to a printer. Nancy Nancy -- I think an downloadable brochure would be a super idea! Unfortunately, the marketing information via http://www.openoffice.org/marketing/ -- How to get Involved seems out of date. Please join the marketing mailing list (see info: http://incubator.apache.org/openofficeorg/mailing-lists.html#marketing-mailing-list), suggest some ideas, and see what others think! Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Albino B Neto bin...@apache.org To: ooo-dev@incubator.apache.org Sent: Tuesday, October 9, 2012 5:54 PM Subject: Re: Marketing events Hi I'm from Brazil and there various events: FISL, LatinoWare, Revista Espirito Livre and others spread throughout BR. You could have a fund for member official AOO, so you can attend the AOO speaking, lecturing, talking etc.. But this must be carefully discussed. This member can attend these events that have availability and time available. It'll be like us, being voluntary, but that talk of AOO events. Albino -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
How many countries has AOO been downloaded from?
I've seen some online traffic, on Twitter and elsewhere, questioning the claim in our graduation press release that AOO has been downloaded by users in 228 countries. The critics of this claim say that there are not that many countries in the world. Well, it depends on how you define things. There are UN countries. There are Olympic countries. There are postal countries. There are countries with telephone country codes. And so on. These don't all correspond with each other. (Look at the complexities with the status of Taiwan or Macedonia, for example). The definition used when looking at internet traffic is (not surprisingly) internet countries, e.g., countries with an assigned ccTLD (http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains). In this scheme, for example, Martinique (.mq) and France (.fr) are two different countries, although politically Martinique is an overseas region, or région d'outre-mer, of France. You can see the complete list of internet countries from which AOO has been downloaded here: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2012-06-01+to+2012-10-19 As you can see, the number is now 232, indicating that the press release understated the number. Anyone who is interested can take this publicly available data and map it to whatever other country-counting convention they wish, whether based on UN membership, US diplomatic recognition, Universal Postal Union, or whatever. Regards, -Rob
Re: How many countries has AOO been downloaded from?
This is really a lot more convincing than just a number, and something to be proud of !! Would it be an idea, to put a link in the on openoffice.org to this page, e.g. in the news area with the name (download statistics) ? Jan. On 19 October 2012 19:44, Rob Weir robw...@apache.org wrote: I've seen some online traffic, on Twitter and elsewhere, questioning the claim in our graduation press release that AOO has been downloaded by users in 228 countries. The critics of this claim say that there are not that many countries in the world. Well, it depends on how you define things. There are UN countries. There are Olympic countries. There are postal countries. There are countries with telephone country codes. And so on. These don't all correspond with each other. (Look at the complexities with the status of Taiwan or Macedonia, for example). The definition used when looking at internet traffic is (not surprisingly) internet countries, e.g., countries with an assigned ccTLD ( http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains ). In this scheme, for example, Martinique (.mq) and France (.fr) are two different countries, although politically Martinique is an overseas region, or région d'outre-mer, of France. You can see the complete list of internet countries from which AOO has been downloaded here: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2012-06-01+to+2012-10-19 As you can see, the number is now 232, indicating that the press release understated the number. Anyone who is interested can take this publicly available data and map it to whatever other country-counting convention they wish, whether based on UN membership, US diplomatic recognition, Universal Postal Union, or whatever. Regards, -Rob
Re: How many countries has AOO been downloaded from?
On Fri, Oct 19, 2012 at 1:55 PM, jan iversen jancasacon...@gmail.com wrote: This is really a lot more convincing than just a number, and something to be proud of !! And intriguing. It shows 62 downloads from the Vatican City. So Pope Benedict, of course. But who are the other 61 ;-) Would it be an idea, to put a link in the on openoffice.org to this page, e.g. in the news area with the name (download statistics) ? It might need some scripting, since the URL includes a date range as parameters. And in general I hesitate to put a home page link to some else's database query, due to the load it could generate for them. We get 250K+ home page visits/day. That could generate a lot of queries. So maybe we could take that info periodically (it doesn't change too quickly) and put a static version up on the website. That is what we do currently for the download counts: http://www.openoffice.org/stats/ -rob Jan. On 19 October 2012 19:44, Rob Weir robw...@apache.org wrote: I've seen some online traffic, on Twitter and elsewhere, questioning the claim in our graduation press release that AOO has been downloaded by users in 228 countries. The critics of this claim say that there are not that many countries in the world. Well, it depends on how you define things. There are UN countries. There are Olympic countries. There are postal countries. There are countries with telephone country codes. And so on. These don't all correspond with each other. (Look at the complexities with the status of Taiwan or Macedonia, for example). The definition used when looking at internet traffic is (not surprisingly) internet countries, e.g., countries with an assigned ccTLD ( http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains ). In this scheme, for example, Martinique (.mq) and France (.fr) are two different countries, although politically Martinique is an overseas region, or région d'outre-mer, of France. You can see the complete list of internet countries from which AOO has been downloaded here: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2012-06-01+to+2012-10-19 As you can see, the number is now 232, indicating that the press release understated the number. Anyone who is interested can take this publicly available data and map it to whatever other country-counting convention they wish, whether based on UN membership, US diplomatic recognition, Universal Postal Union, or whatever. Regards, -Rob
Re: AOO volunteers: essential skills and tasks
On Fri, Oct 19, 2012 at 12:27 PM, jan iversen jancasacon...@gmail.com wrote: That is a BIG +++1 from me. Being a new contributors, I could have saved a lot of stupid questions, had I had a reading list. I have spent quite a number of hours (and that of others too) finding things, everybody knows. It would be good to have 1 wiki page with a suggested reading and items to do (get a wiki account etc.). That page can then later have specialized sub pages depending on the type of volunteer. Right. This is the idea. What really bothers me, is that I waste time for many others, who are very polite in helping me get over the first startwith many new volunteers (assuming I am on average) that is a lot of time, that could have been spent on more fruitful things. Well, I must admit that your recent contributions, enthusiasm and questions have prompted these thoughts. Please don't be bothered that you have questions. This is getting us in the right direction and pointing out where we need to improve. This is good. We all need to keep a good attitude about this. And I think so far we're doing this well. I agree however that the wording of the page should be choose well, words like suggested reading are far better for those who take things personally. Good point. I will gladly review such a page :-) Great. Maybe we can start a thread on L10N list about what the essential skills a new volunteer would need in that area? -Rob jan. On 19 October 2012 18:17, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob
Re: Marketing events: Brochure? Newsletter?
On 10/19/12, Kay Schenk kay.sch...@gmail.com wrote: On Tue, Oct 9, 2012 at 6:19 PM, Nancy K nancythirt...@yahoo.com wrote: Hi! I have been keeping up with the discussions, but unable to participate much lately, unfortunately. In the marketing department, is there a newsletter or brochure that could be distributed at any event? I am thinking that a design could be approved, then placed on the website so that anyone representing Apache OpenOffice could print it out. This might be an example of a way to fund an event - using funds for the paper and ink or professional printing. The vote to offer funds for an event could be proposed for approval or disapproval. If approved the design posted could be in a file format that could be printed directly or sent to a printer. Nancy Nancy -- I think an downloadable brochure would be a super idea! Unfortunately, the marketing information via http://www.openoffice.org/marketing/ -- How to get Involved seems out of date. Please join the marketing mailing list (see info: http://incubator.apache.org/openofficeorg/mailing-lists.html#marketing-mailing-list), suggest some ideas, and see what others think! This can be easily updated, what is more dificult is trying to get back some of these marketing jobs, specially sources files. These source files makes editing and generating marketing kits more easily. Other communities like Software freedom day has been pretty good on launching new marketing kits, or images. OOo days, there was also some marketing efforts on presenting a similar design for things. Like the wireframe gull or the waves. unfortunately oracle's brand refresh of just using 'white' left us with only the orb as a design element. Apache hasn't really produce much, even with the logo there are some missing pieces. So I think is important at least to have something like brochure sources, newsletters, and such to be able to pull together some marketing efforts. Nancy Web Design Free 24 hour pass to lynda.com. Video courses on SEO, CMS, Design and Software Courses From: Albino B Neto bin...@apache.org To: ooo-dev@incubator.apache.org Sent: Tuesday, October 9, 2012 5:54 PM Subject: Re: Marketing events Hi I'm from Brazil and there various events: FISL, LatinoWare, Revista Espirito Livre and others spread throughout BR. You could have a fund for member official AOO, so you can attend the AOO speaking, lecturing, talking etc.. But this must be carefully discussed. This member can attend these events that have availability and time available. It'll be like us, being voluntary, but that talk of AOO events. Albino -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: How many countries has AOO been downloaded from?
I think the fact that it is not our data is important, but I agree that putting the link there could be a problem. Could we not simply write that our data comes from or are verified by, and then a general link ? Jan. On 19 October 2012 20:00, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 1:55 PM, jan iversen jancasacon...@gmail.com wrote: This is really a lot more convincing than just a number, and something to be proud of !! And intriguing. It shows 62 downloads from the Vatican City. So Pope Benedict, of course. But who are the other 61 ;-) Would it be an idea, to put a link in the on openoffice.org to this page, e.g. in the news area with the name (download statistics) ? It might need some scripting, since the URL includes a date range as parameters. And in general I hesitate to put a home page link to some else's database query, due to the load it could generate for them. We get 250K+ home page visits/day. That could generate a lot of queries. So maybe we could take that info periodically (it doesn't change too quickly) and put a static version up on the website. That is what we do currently for the download counts: http://www.openoffice.org/stats/ -rob Jan. On 19 October 2012 19:44, Rob Weir robw...@apache.org wrote: I've seen some online traffic, on Twitter and elsewhere, questioning the claim in our graduation press release that AOO has been downloaded by users in 228 countries. The critics of this claim say that there are not that many countries in the world. Well, it depends on how you define things. There are UN countries. There are Olympic countries. There are postal countries. There are countries with telephone country codes. And so on. These don't all correspond with each other. (Look at the complexities with the status of Taiwan or Macedonia, for example). The definition used when looking at internet traffic is (not surprisingly) internet countries, e.g., countries with an assigned ccTLD ( http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains ). In this scheme, for example, Martinique (.mq) and France (.fr) are two different countries, although politically Martinique is an overseas region, or région d'outre-mer, of France. You can see the complete list of internet countries from which AOO has been downloaded here: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2012-06-01+to+2012-10-19 As you can see, the number is now 232, indicating that the press release understated the number. Anyone who is interested can take this publicly available data and map it to whatever other country-counting convention they wish, whether based on UN membership, US diplomatic recognition, Universal Postal Union, or whatever. Regards, -Rob
Re: How many countries has AOO been downloaded from?
Should a form of this appear on the AOO blog? Don On Fri, Oct 19, 2012 at 2:12 PM, jan iversen jancasacon...@gmail.com wrote: I think the fact that it is not our data is important, but I agree that putting the link there could be a problem. Could we not simply write that our data comes from or are verified by, and then a general link ? Jan. On 19 October 2012 20:00, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 1:55 PM, jan iversen jancasacon...@gmail.com wrote: This is really a lot more convincing than just a number, and something to be proud of !! And intriguing. It shows 62 downloads from the Vatican City. So Pope Benedict, of course. But who are the other 61 ;-) Would it be an idea, to put a link in the on openoffice.org to this page, e.g. in the news area with the name (download statistics) ? It might need some scripting, since the URL includes a date range as parameters. And in general I hesitate to put a home page link to some else's database query, due to the load it could generate for them. We get 250K+ home page visits/day. That could generate a lot of queries. So maybe we could take that info periodically (it doesn't change too quickly) and put a static version up on the website. That is what we do currently for the download counts: http://www.openoffice.org/stats/ -rob Jan. On 19 October 2012 19:44, Rob Weir robw...@apache.org wrote: I've seen some online traffic, on Twitter and elsewhere, questioning the claim in our graduation press release that AOO has been downloaded by users in 228 countries. The critics of this claim say that there are not that many countries in the world. Well, it depends on how you define things. There are UN countries. There are Olympic countries. There are postal countries. There are countries with telephone country codes. And so on. These don't all correspond with each other. (Look at the complexities with the status of Taiwan or Macedonia, for example). The definition used when looking at internet traffic is (not surprisingly) internet countries, e.g., countries with an assigned ccTLD ( http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains ). In this scheme, for example, Martinique (.mq) and France (.fr) are two different countries, although politically Martinique is an overseas region, or région d'outre-mer, of France. You can see the complete list of internet countries from which AOO has been downloaded here: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2012-06-01+to+2012-10-19 As you can see, the number is now 232, indicating that the press release understated the number. Anyone who is interested can take this publicly available data and map it to whatever other country-counting convention they wish, whether based on UN membership, US diplomatic recognition, Universal Postal Union, or whatever. Regards, -Rob
Re: OpenOffice graduates from the Apache Incubator
Hello all, congratulations and all the best for the future! Not sure what else to say except good bye and that I hope to get in touch with you folks at ApacheCon someday. Cheers Christian On Thu, Oct 18, 2012 at 2:01 PM, Andrea Pescetti pesce...@apache.org wrote: The Apache Software Foundation today announced that Apache OpenOffice has graduated from the Apache Incubator to become a Top-Level Project, signifying that the Project's community and products have been well-governed under the ASF's meritocratic process and principles. In the near future there will be some changes to the website and mailing lists, as we move out of the Incubator. Details of changes will be posted on our wiki at http://s.apache.org/openoffice-graduation-changes But aside from these small administrative and infrastructure changes, work on the next release of Apache OpenOffice continues. More details in the blog post here: https://blogs.apache.org/OOo/entry/openoffice_graduates_from_the_apache Regards, Andrea. -- http://www.grobmeier.de https://www.timeandbill.de
Re: AOO volunteers: essential skills and tasks
I had a funny feeling, that I was the drop that made it flow over :-) I will make a lists of what I missed and post it on l10n and then we can take that as a starting point. jan. On 19 October 2012 20:04, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:27 PM, jan iversen jancasacon...@gmail.com wrote: That is a BIG +++1 from me. Being a new contributors, I could have saved a lot of stupid questions, had I had a reading list. I have spent quite a number of hours (and that of others too) finding things, everybody knows. It would be good to have 1 wiki page with a suggested reading and items to do (get a wiki account etc.). That page can then later have specialized sub pages depending on the type of volunteer. Right. This is the idea. What really bothers me, is that I waste time for many others, who are very polite in helping me get over the first startwith many new volunteers (assuming I am on average) that is a lot of time, that could have been spent on more fruitful things. Well, I must admit that your recent contributions, enthusiasm and questions have prompted these thoughts. Please don't be bothered that you have questions. This is getting us in the right direction and pointing out where we need to improve. This is good. We all need to keep a good attitude about this. And I think so far we're doing this well. I agree however that the wording of the page should be choose well, words like suggested reading are far better for those who take things personally. Good point. I will gladly review such a page :-) Great. Maybe we can start a thread on L10N list about what the essential skills a new volunteer would need in that area? -Rob jan. On 19 October 2012 18:17, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob
Re: Estimating contributors by looking at wiki accounts?
Am 10/19/2012 05:28 PM, schrieb Rob Weir: I recently saw another open source project claim that they had over 3000 contributors. They derived this estimate by looking at the number of user accounts they had in their wiki. That is quite clever, I thought. Since we use the same wiki software, I thought I'd check this metric for us. Our wiki says we have over 58,000 user accounts. I know we're doing well, but would it really make sense to claim that we have over 58,000 contributors? I don't think so. I suppose we could look only at accounts where the person has actually contributed edits, or even recent edits. (MediaWiki is a well-known target of registration spam). Although the other project did not seem to filter out inactive or unused accounts, I think the metrics are meaningless unless we do that. What do you think? Or do we even care? Yes, maybe a good chance to tell others some numbers from our project. However, the wording of the number is (for some people) the more important part. So, this should be double-checked. That means it doesn't make sense to say hey, we have 58,000+ contributors but more like ... in the last 12 months we got contributions from ~3,000 active people (incl. accounts from SVN, BZ, Wiki, MLs, etc.). Marcus
Re: [WWW]: shared ideas and looking for feedback
Am 10/19/2012 10:26 AM, schrieb jan iversen: It would be a good idea to have the same structure and then one directory with country special parts...as you say it makes it easier to maintain, and with the extra directory nobody is limited. I support this idea. When we extent this also for the translated release notes like: .../rn/release_notea_aoo341.html .../de//rn/release_notea_aoo341.html .../it//rn/release_notea_aoo341.html then we can change the already existing link on the download website, from the now English only release notes to the language-related notes. Would be a nice additonal service for our users. On 19 October 2012 10:22, Jürgen Schmidtjogischm...@gmail.com wrote: Hi, yesterday I had problems to find a good place for the German translation of the graduation press release. And I thought that it is probably a good idea to cleanup the whole page with a clear and well defined structure. I know that there is work ongoing and that we move already in this direction. But nevertheless I would like to share the things I have in mind to check if it is aligned with the already ongoing work or if it makes sense at all. 1. a clear structure for the English content as well as the translated pages. .../index.hmtl .../de/index.html .../it/index.html ... .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html ... Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This makes it easy to find the related translation for any files. We can also use Pootle to do the translation of the web content in the future. 2. we have special news areas where local communities can spread further news relevant to their local activities, e.g. local conferences, events. But in general we have the same content on all pages. Other local community relevant content should be moved in the wiki. The main idea is to have a smaller but cleaner and well structured and organized user portal www.openoffice.org. Community internal things should be move on openoffice.apache.org or the wiki. I know it is not really new and it is probably more to remind myself but I am interested to hear others opinion. Simply +1, with the addition from above. Marcus
Re: discussion on new l10n workflow
On 17/10/2012 jan iversen wrote: Would it be an idea to have 1 UI file pr directory in main (that would be so easy to implement) and 1 Help file pr directory in helpContent2 ? Yes, this might work. Sure the current 276 files are too many, while consolidating too much on the other hand is very inconvenient for sharing work. What we should preserve is that is someone is the, say, Calc guy in the, say, Polish team, then he can be given PO (or other format, this is irrelevant) files for the Calc UI and the Calc Help. This enables easy and safe division of work. also check the letter accellerators (Ca~ncel) I have a very strong suspicion that they are not always identical. This is not important. Actually, if I recall correctly we even deprecated them at a point. We are not talking about keyboard shortcuts here (e.g., CTRL-S to open a file); we are talking about the, much less common, accelerators, i.e., saving with ALT-F then S. OpenOffice will assign these accelerators automatically when they are not set using the ~ in the strings, and it makes sense to let OpenOffice assign them, since they are not listed in the documentation. Moreover, assigning them manually is very error-prone since it often results in conflicts, while automatic attribution doesn't. Regards, Andrea.
Re: AOO volunteers: essential skills and tasks
On 10/19/2012 01:07 PM, Rob Weir wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: To make it more concrete, this is what Level 1 might look like: http://incubator.apache.org/openofficeorg/orientation/level-1.html -Rob This is very good! I esp like the last part about providing a way for volunteers to sign up if you will. This will be a nice touch. I'm also wondering if there's some way to tie this in to our current Help Wanted page: https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted Maybe someone has some ideas? Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: AOO volunteers: essential skills and tasks
On Oct 19, 2012, at 4:45 PM, Kay Schenk kay.sch...@gmail.com wrote: On 10/19/2012 01:07 PM, Rob Weir wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: To make it more concrete, this is what Level 1 might look like: http://incubator.apache.org/openofficeorg/orientation/level-1.html -Rob This is very good! I esp like the last part about providing a way for volunteers to sign up if you will. This will be a nice touch. I'm also wondering if there's some way to tie this in to our current Help Wanted page: https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted Yes, It is worth looking at the new volunteer view of things, from end to end. My current thinking is this: as we scale the number of volunteers we'll soon want a better way to track items like these. Maybe putting them into BZ would work? Introduce a new field to record difficulty in BZ and filters to list unassigned easy issues? Maybe someone has some ideas? Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: discussion on new l10n workflow
Thanks for your reply. On 19 October 2012 22:33, Andrea Pescetti pesce...@apache.org wrote: On 17/10/2012 jan iversen wrote: Would it be an idea to have 1 UI file pr directory in main (that would be so easy to implement) and 1 Help file pr directory in helpContent2 ? Yes, this might work. Sure the current 276 files are too many, while consolidating too much on the other hand is very inconvenient for sharing work. What we should preserve is that is someone is the, say, Calc guy in the, say, Polish team, then he can be given PO (or other format, this is irrelevant) files for the Calc UI and the Calc Help. This enables easy and safe division of work. I agree...but I am not sure we can make the files for like calc, if I am correct the directories in main does not directly relate to a product part, many of the directories seems to be generic, but I might be wrong ? My intentions right now is to propose that each directory is a single translation file and helpcontent2 is split at that level, but there will be a new file combine.lst, where we can combine several directories into one. That way we are flexible but it is still easy to develop. also check the letter accellerators (Ca~ncel) I have a very strong suspicion that they are not always identical. This is not important. Actually, if I recall correctly we even deprecated them at a point. We are not talking about keyboard shortcuts here (e.g., CTRL-S to open a file); we are talking about the, much less common, accelerators, i.e., saving with ALT-F then S. OpenOffice will assign these accelerators automatically when they are not set using the ~ in the strings, and it makes sense to let OpenOffice assign them, since they are not listed in the documentation. Moreover, assigning them manually is very error-prone since it often results in conflicts, while automatic attribution doesn't. Should we the consistency checker than make a warning when they are used (which happens approx. 500 times in the danish files) ?? Regards, Andrea. For your information I have found a way of splitting the discussion of a new l10n workflow from the discussion of file formats. That is I have succeed (I think) in making a workflow that does not rely on the fileformat. Jan.
Re: AOO volunteers: essential skills and tasks
I think it is a good starting point, however I dont like the notation level 1, is looks like a graduation process, and I have to ask myself where am I on that latter. 1) Introduce yourself (by the way I think I have forgotten that). why do it on the mailling list, when Wiki ask you for more or less the exact same type of information. 2) I like that. 3) +1, but I will never understand why it is a mailing list and not a forum, where it is so much easier to look at history 4+5) yes, but that has not much to do specifically with AOO. 7) the project planning part seems a bit of a contradiction, look at localization planning as an example. Sorry for being frank, I do not want to be non-polite, but a lot of these items just highlight my difficulties. All aside, I think we are making huge steps in the right direction and that is what matters jan. On 19 October 2012 22:07, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: To make it more concrete, this is what Level 1 might look like: http://incubator.apache.org/openofficeorg/orientation/level-1.html -Rob Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob
Re: OpenOffice graduates from the Apache Incubator
Hi, Today apache.org announced: The Apache Software Foundation Announces Apache OpenOffice™ as a Top-Level Project Award-winning leading Open Source productivity suite widely used in 228 countries; over 20 million downloads of latest version since its release in May 2012 http://en.wikipedia.org/wiki/List_of_sovereign_states list 206 countries on this planet.
Re: AOO volunteers: essential skills and tasks
I think it is important to remember, that a volunteer is not signing up for anything. A volunteer, in my view, is a person who wants to help with his/hers skillset...so if we start saying you have to pass level x before continuing we have already lost (At least I can relate that to myself) I have been in this business since 1975, and I have never made it through any of all these master classes and other exams. I am just one of the guys who get things done, like in the early days before tcp/ip. What I am trying to say is, let´s help people work with usthat´s what it´s all about, if we can help people to easier help us, then we have a win-win situation. And in respect of introducing myself, which I forgot please read this resume: http://wiki.openoffice.org/wiki/User:JanIversen jan. Jan. On 19 October 2012 23:08, Rob Weir rabas...@gmail.com wrote: On Oct 19, 2012, at 4:45 PM, Kay Schenk kay.sch...@gmail.com wrote: On 10/19/2012 01:07 PM, Rob Weir wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: To make it more concrete, this is what Level 1 might look like: http://incubator.apache.org/openofficeorg/orientation/level-1.html -Rob This is very good! I esp like the last part about providing a way for volunteers to sign up if you will. This will be a nice touch. I'm also wondering if there's some way to tie this in to our current Help Wanted page: https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted Yes, It is worth looking at the new volunteer view of things, from end to end. My current thinking is this: as we scale the number of volunteers we'll soon want a better way to track items like these. Maybe putting them into BZ would work? Introduce a new field to record difficulty in BZ and filters to list unassigned easy issues? Maybe someone has some ideas? Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? -Rob -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: AOO volunteers: essential skills and tasks
On Fri, Oct 19, 2012 at 5:47 PM, jan iversen jancasacon...@gmail.com wrote: I think it is a good starting point, however I dont like the notation level 1, is looks like a graduation process, and I have to ask myself where am I on that latter. I don't want suggest that everyone must go through these steps. An experienced open source volunteer probably would just skim this material. Someone who is a Committer on another Apache project would probably skip over it altogether. The name Level 1 doesn't matter. We can call it Stage 1, or even Introduction. But there is an explicit ordering, and giving numbers is the natural way to express an ordering. But I am sensitive to having these stages give the feeling of accomplishment without becoming unwelcome status markers. 1) Introduce yourself (by the way I think I have forgotten that). why do it on the mailling list, when Wiki ask you for more or less the exact same type of information. This is more for the benefit of existing project volunteers already subscribed to ooo-dev. This gives them the opportunity to see who is getting involved. They might recognize some names. If so they can reach out to offer additional help and encouragement. 2) I like that. 3) +1, but I will never understand why it is a mailing list and not a forum, where it is so much easier to look at history Mailing lists are the lowest common denominator technologies. You can access email from nearly any device, online or offline, using plain text. It is important to note that as a project we don't directly control mailing lists, websites, Bugzilla, etc., except at the level of the content and application admin functions. The sysadmin functions are done ASF-wide by a group of volunteers that we call the Apache Infrastructure team. Since they are maintaining services for over 100 projects, there are limits to how much customization each project can have. This is a consideration for maintenance as well as server resources and security. So there is a something like a menu of tools we have access to, and which are supported by the Infra team. But changing the menu is more difficult. 4+5) yes, but that has not much to do specifically with AOO. Right. But these are practical issues that have come up with past volunteers. For any such document we need to assume some initial skill/knowledge level. This means those who have these skills already will find some items unnecessary. This is hard to avoid. 7) the project planning part seems a bit of a contradiction, look at localization planning as an example. Maybe calling it Project Coordination would be more accurate. CWiki is what we've been using to coordinate the various efforts of a major project-wide initiative, like a specific release. For example, we're using a page now to coordinate graduation-related infrastructure changes: https://cwiki.apache.org/confluence/display/OOOUSERS/Graduation+Infrastructure+Changes Sorry for being frank, I do not want to be non-polite, but a lot of these items just highlight my difficulties. Nothing on this page is going to help with the current localization process. I'm hoping that, with your help, we resolve that in parallel. -Rob All aside, I think we are making huge steps in the right direction and that is what matters jan. On 19 October 2012 22:07, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: To make it more concrete, this is what Level 1 might look like: http://incubator.apache.org/openofficeorg/orientation/level-1.html -Rob Level 1 tasks: 1) Read the
Re: AOO volunteers: essential skills and tasks
On Fri, Oct 19, 2012 at 6:16 PM, jan iversen jancasacon...@gmail.com wrote: I think it is important to remember, that a volunteer is not signing up for anything. A volunteer, in my view, is a person who wants to help with his/hers skillset...so if we start saying you have to pass level x before continuing we have already lost (At least I can relate that to myself) That might be true for you. But I can tell you from experience that we've had volunteer after volunteer who have posted a note to this list, said they wanted to help, stuck around for a few days, and then were never heard of again. They never found a hook that they could attach themselves to. They never figured out how to get started. The couldn't find where to get started. The lack of accomplishment and progress leads to frustration, and then they are gone. Maybe we can find some way of expressing this without offering too much offense ? -Rob I have been in this business since 1975, and I have never made it through any of all these master classes and other exams. I am just one of the guys who get things done, like in the early days before tcp/ip. What I am trying to say is, let´s help people work with usthat´s what it´s all about, if we can help people to easier help us, then we have a win-win situation. And in respect of introducing myself, which I forgot please read this resume: http://wiki.openoffice.org/wiki/User:JanIversen jan. Jan. On 19 October 2012 23:08, Rob Weir rabas...@gmail.com wrote: On Oct 19, 2012, at 4:45 PM, Kay Schenk kay.sch...@gmail.com wrote: On 10/19/2012 01:07 PM, Rob Weir wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: To make it more concrete, this is what Level 1 might look like: http://incubator.apache.org/openofficeorg/orientation/level-1.html -Rob This is very good! I esp like the last part about providing a way for volunteers to sign up if you will. This will be a nice touch. I'm also wondering if there's some way to tie this in to our current Help Wanted page: https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted Yes, It is worth looking at the new volunteer view of things, from end to end. My current thinking is this: as we scale the number of volunteers we'll soon want a better way to track items like these. Maybe putting them into BZ would work? Introduce a new field to record difficulty in BZ and filters to list unassigned easy issues? Maybe someone has some ideas? Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off
Re: OpenOffice graduates from the Apache Incubator
On Fri, Oct 19, 2012 at 6:14 PM, Andreas Säger ville...@t-online.de wrote: Hi, Today apache.org announced: The Apache Software Foundation Announces Apache OpenOffice™ as a Top-Level Project Award-winning leading Open Source productivity suite widely used in 228 countries; over 20 million downloads of latest version since its release in May 2012 http://en.wikipedia.org/wiki/List_of_sovereign_states list 206 countries on this planet. IANA recognizes over 250 country codes: http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains -Rob
Re: OOoCon videos/material
On 19/10/2012 Peter Junge wrote: - OOoCon 2009 (Orvieto/Italy) and OOoCon 2010 (Budapest) were hosted at http://www.ooocon.org. To my knowledge that site was running on a VM at one of Sun's data centers. I recall there was an incompatible update of the site between both conference, so the materials might be distributed over different database dumps. Correct (I actually don't know where the server was located, but it answered both www.ooocon.org and conference.services.openoffice.org or something like that, as of 2009). For Orvieto 2009, videos are still available at http://media.lscube.org/oooconf (someone download them please!). Presentations from Orvieto and Budapest should be available as files in backups of the system Peter mentioned. But I couldn't find it online any longer the last time I tried, so contacting the people Peter listed is a good idea, thanks Peter. Regards, Andrea.
Re: OOoCon videos/material
On 10/19/12, Peter Junge peter.ju...@gmx.org wrote: On 10/19/2012 1:01 PM, Alexandro Colorado wrote: On 10/18/12, Alexandro Colorado j...@oooes.org wrote: On 10/18/12, Christoph Jopp j...@gmx.de wrote: ... The videos of the OOoCon 2007 were shot and hosted by a video team (cannot remember the name) from Slovenia that also did the same job at OOoCon 2005 (Koper). Barcelona Kiberpipa had really bad problems with the Audio of the conference and they didnt release the videos. Koper in 06 the videos were in better shape, and they host it. AFAIR ... As far as I can remember their name was kiberpipa (https://www.kiberpipa.org/sl/) Found them: :) http://ooocon.kiberpipa.org/media/index-2007.html Super-cool and many more than I remember. :-) Just a note, I tried to upload to youtube a couple of the videos, Youtube seems to take them except for the audio. Anyone know if OGG audio is supported by youtube. This is the output specs I get from the videos: == Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family [theora @ 0x88e32c0]7 bits left in packet 82 Selected video codec: [fftheora] vfm: ffmpeg (FFmpeg Theora) == == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000-192000) Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis) == -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: OpenOffice graduates from the Apache Incubator
On Oct 19, 2012, at 3:34 PM, Rob Weir wrote: On Fri, Oct 19, 2012 at 6:14 PM, Andreas Säger ville...@t-online.de wrote: Hi, Today apache.org announced: The Apache Software Foundation Announces Apache OpenOffice™ as a Top-Level Project Award-winning leading Open Source productivity suite widely used in 228 countries; over 20 million downloads of latest version since its release in May 2012 http://en.wikipedia.org/wiki/List_of_sovereign_states list 206 countries on this planet. IANA recognizes over 250 country codes: http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains This is a silly argument. Basically here are very few countries from wikipedia that do not show downloads of Apache OpenOffice: Democratic People's Republic of Korea →Korea, North The rest are tiny and some are probably not IANA supported or are unusual like Tuvalu (.tv (?)) Nagorno-Karabakh (Azerbaijan) Nauru – Republic of Nauru (smallest republic on Earth) Sahrawi Arab Democratic Republic (Morocco) Somaliland (Somalia) South Ossetia (Georgia) South Sudan (just independent of Sudan) Transnistria (Moldova) Tuvalu (.tv) Downloads from just about all countries in the world! would suffice. Regards, Dave
Re: OpenOffice graduates from the Apache Incubator
On Fri, Oct 19, 2012 at 8:06 PM, Dave Fisher dave2w...@comcast.net wrote: On Oct 19, 2012, at 3:34 PM, Rob Weir wrote: On Fri, Oct 19, 2012 at 6:14 PM, Andreas Säger ville...@t-online.de wrote: Hi, Today apache.org announced: The Apache Software Foundation Announces Apache OpenOffice™ as a Top-Level Project Award-winning leading Open Source productivity suite widely used in 228 countries; over 20 million downloads of latest version since its release in May 2012 http://en.wikipedia.org/wiki/List_of_sovereign_states list 206 countries on this planet. IANA recognizes over 250 country codes: http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains This is a silly argument. Basically here are very few countries from wikipedia that do not show downloads of Apache OpenOffice: Democratic People's Republic of Korea →Korea, North And we know that North Korea uses OpenOffice on their Red Star distribution, according to screen shots taken by a Russian blogger: http://ashen-rus.livejournal.com/4300.html The rest are tiny and some are probably not IANA supported or are unusual like Tuvalu (.tv (?)) Nagorno-Karabakh (Azerbaijan) Nauru – Republic of Nauru (smallest republic on Earth) Sahrawi Arab Democratic Republic (Morocco) Somaliland (Somalia) South Ossetia (Georgia) South Sudan (just independent of Sudan) Transnistria (Moldova) Tuvalu (.tv) Downloads from just about all countries in the world! would suffice. Regards, Dave
Re: Documentation for writing addins
What language will you use? On 10/19/2012 09:00 AM, Christof Donat wrote: Hi, I am trying to write an addin for AOO writer. Thank google I found a fiew examples for additional calc functions and a bit of interface documentations so I was able to more or less guess how the code for my writer addin should look like. Where I completelly am lost is on the various XML FIles. Is there any document describing the contents of an XCU file and a description.xml? The latter is not that much of a problem, because I can at least get enough of it from some examples I found. The XCU fules are the bug issue. Christof -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt Info: http://www.pitonyak.org/oo.php
Re: OOoCon videos/material
On 12-10-19, at 19:47 , Alexandro Colorado j...@oooes.org wrote: On 10/19/12, Peter Junge peter.ju...@gmx.org wrote: On 10/19/2012 1:01 PM, Alexandro Colorado wrote: On 10/18/12, Alexandro Colorado j...@oooes.org wrote: On 10/18/12, Christoph Jopp j...@gmx.de wrote: ... The videos of the OOoCon 2007 were shot and hosted by a video team (cannot remember the name) from Slovenia that also did the same job at OOoCon 2005 (Koper). Barcelona Kiberpipa had really bad problems with the Audio of the conference and they didnt release the videos. Koper in 06 the videos were in better shape, and they host it. AFAIR ... As far as I can remember their name was kiberpipa (https://www.kiberpipa.org/sl/) Found them: :) http://ooocon.kiberpipa.org/media/index-2007.html Super-cool and many more than I remember. :-) Just a note, I tried to upload to youtube a couple of the videos, Youtube seems to take them except for the audio. Anyone know if OGG audio is supported by youtube. Alexandro, I assume you did the simple search, in Google, of OGG YouTube? There is a video explaining things and claiming it's possible. The second entry however complicates things by showing how to convert the formats. Of course, there are numerous converters that are open source. -louis
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 11:25 PM, Louis Suárez-Potts lui...@gmail.comwrote: On 12-10-19, at 19:47 , Alexandro Colorado j...@oooes.org wrote: On 10/19/12, Peter Junge peter.ju...@gmx.org wrote: On 10/19/2012 1:01 PM, Alexandro Colorado wrote: On 10/18/12, Alexandro Colorado j...@oooes.org wrote: On 10/18/12, Christoph Jopp j...@gmx.de wrote: ... The videos of the OOoCon 2007 were shot and hosted by a video team (cannot remember the name) from Slovenia that also did the same job at OOoCon 2005 (Koper). Barcelona Kiberpipa had really bad problems with the Audio of the conference and they didnt release the videos. Koper in 06 the videos were in better shape, and they host it. AFAIR ... As far as I can remember their name was kiberpipa (https://www.kiberpipa.org/sl/) Found them: :) http://ooocon.kiberpipa.org/media/index-2007.html Super-cool and many more than I remember. :-) Just a note, I tried to upload to youtube a couple of the videos, Youtube seems to take them except for the audio. Anyone know if OGG audio is supported by youtube. Alexandro, I assume you did the simple search, in Google, of OGG YouTube? There is a video explaining things and claiming it's possible. The second entry however complicates things by showing how to convert the formats. Of course, there are numerous converters that are open source. -louis In theory Youtube support both Theora and Vorbis, in practice however, vorbis does have issues with the sound of the OOoCon06 videos. There are different parameters which might have conflict with youtube internal converter like the Hz, Samplerate and kbit quality. So some vorbis (this also apply to other fileformats) will play nicer than otherones. My Meego phone does display some ogg but others will cause trouble. Of course transcoding is possible, but it will greatly delay the migration to youtube. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: OOoCon videos/material
On Fri, Oct 19, 2012 at 11:57 PM, Alexandro Colorado j...@oooes.org wrote: On Fri, Oct 19, 2012 at 11:25 PM, Louis Suárez-Potts lui...@gmail.comwrote: On 12-10-19, at 19:47 , Alexandro Colorado j...@oooes.org wrote: On 10/19/12, Peter Junge peter.ju...@gmx.org wrote: On 10/19/2012 1:01 PM, Alexandro Colorado wrote: On 10/18/12, Alexandro Colorado j...@oooes.org wrote: On 10/18/12, Christoph Jopp j...@gmx.de wrote: ... The videos of the OOoCon 2007 were shot and hosted by a video team (cannot remember the name) from Slovenia that also did the same job at OOoCon 2005 (Koper). Barcelona Kiberpipa had really bad problems with the Audio of the conference and they didnt release the videos. Koper in 06 the videos were in better shape, and they host it. AFAIR ... As far as I can remember their name was kiberpipa (https://www.kiberpipa.org/sl/) Found them: :) http://ooocon.kiberpipa.org/media/index-2007.html Super-cool and many more than I remember. :-) Just a note, I tried to upload to youtube a couple of the videos, Youtube seems to take them except for the audio. Anyone know if OGG audio is supported by youtube. Alexandro, I assume you did the simple search, in Google, of OGG YouTube? There is a video explaining things and claiming it's possible. The second entry however complicates things by showing how to convert the formats. Of course, there are numerous converters that are open source. -louis In theory Youtube support both Theora and Vorbis, in practice however, vorbis does have issues with the sound of the OOoCon06 videos. There are different parameters which might have conflict with youtube internal converter like the Hz, Samplerate and kbit quality. So some vorbis (this also apply to other fileformats) will play nicer than otherones. My Meego phone does display some ogg but others will cause trouble. ok I think I found the problem, the audio is at 48kHz as opposed to 44kHz and this might be the cause of the youtube failure to transcode internally. Of course transcoding is possible, but it will greatly delay the migration to youtube. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org