Apache OpenOffice Wiki - User contributions [en]

OOoCon2010Stay

2010-08-29T08:03:23Z

Andreasma: /* Silver Hotel Budapest City Center, VI., Hunyadi tér 11. */

{{Marketing}} [[Category:OOoCon]] [[Category:OOoCon2010]]
__TOC__
{{DISPLAYTITLE:Where do you stay at OOoCon 2010?}} [[Category:OOoCon2010]] [[Category:OOoCon]]

= Introduction =

In order to plan meetings and have common places to gather together, we'll try to collect all the hotels where OOoCon participants will stay. If it doesn't exist in the list already, please add your hotel and name to the list, if you want to share the information with the public. You can also add your e-mail address and mobile number, if you want people to reach you - the more the merrier ;-)

The OOoCon organizers would like to encourage everyone to add their details to this wiki page. Please note that all information on this wiki is public, and once published, '''cannot''' be removed anymore, not even by the administrators, so be '''careful''' with what you add.

= Stays =

The format of the entries is name, role, e-mail address, mobile phone number, arrival and departure

==Hotel Opera Garden, H-1065 Budapest, Hajós u. 24.==
[http://maps.google.co.uk/maps?client=safari&rls=en&oe=UTF-8&redir_esc=&um=1&ie=UTF-8&q=opera+garden+hotel+budapest&fb=1&gl=uk&hq=opera+garden+hotel&hnear=Budapest,+Hungary&cid=0,0,18347281351441338242&ei=yXR1TPnmHseQswbK-bXuBQ&sa=X&oi=local_result&ct=image&resnum=2&ved=0CCMQnwIwAQ Google mapping of Opera Garden Hotel]

'''How to get to the Conference Venue:''' On foot

*Louis Suarez-Potts, Community Development Manager, [mailto:louis.suarez-potts@oracle.com louis.suarez-potts@oracle.com], 30 August-6 September.

== Hotel Boutique Bristol, Kenyérmező u. 4. ==

[http://maps.google.de/maps?f=d&source=s_d&saddr=1081+Budapest,+VIII.+ker%C3%BClet,+Keny%C3%A9rmez%C5%91+utca+4,+Ungarn&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fd7E1AIdsBgjASkxSDqiYdxBRzHBjYYUAyHm4Q%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=ls&sll=47.498068,19.064498&sspn=0.020963,0.038581&ie=UTF8&ll=47.498648,19.063296&spn=0.020963,0.038581&z=15 Google Map Route to Hotel Boutique Bristol]

'''How to get to the Conference Venue:''' Get on metro line 2 in the direction of Déli pályaudvar. Get off at Deák Ferenc tér then [[OOoCon2010/Venues#Directions_to_the_Conference_Venue | go to the Conference Venue]].

*Florian Effenberger, Marketing Project Lead, [mailto:floeff@openoffice.org floeff@openoffice.org], +49 151 14424108, 29-Aug, 4-Sep
*Peter Junge, Marketing Project co-Lead, [mailto:pj@openoffice.org pj@openoffice.org], +49 160 5550044, 29-Aug, 6-Sep

== Camping Haller, Haller utca 27. ==

[http://maps.google.de/maps?f=d&source=s_d&saddr=Haller+utca&daddr=1051+Budapest,+N%C3%A1dor+utca+9,+Ungarn&hl=de&geocode=Fa9w1AIdKi8jAQ%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=dme&mrcr=0&mrsp=0&sz=16&sll=47.476593,19.0816&sspn=0.010486,0.01929&ie=UTF8&ll=47.489021,19.066257&spn=0.041933,0.077162&z=14 Google Map Route to Camping Haller]

'''How to get to the Conference Venue:''' Get on tho metro line 3 in the direction of Újpest városközpont. Get off at Deák Ferenc tér then [[OOoCon2010/Venues#Directions_to_the_Conference_Venue | go to the Conference Venue]]

*Stefan Weigel, no rank - not title, [[Special:EmailUser/Stefanw|StefanW]], 31-Aug, 4-Sep

== Hotel Eurostars Center, Kossuth Lajos u. 7-9. ==

[http://maps.google.es/maps?f=d&source=s_d&saddr=1051+Budapest,+N%C3%A1dor+utca+9,+Magyarorsz%C3%A1g+(CEU)&daddr=1053+Budapest,+V.+ker%C3%BClet,+Kossuth+Lajos+utca+7,+Hungr%C3%ADa&hl=es&geocode=FbXM1AIdoasiASFviAnhB6gN3Ckn0F0LFdxBRzEgEaZnEyeKJQ%3BFXmy1AIdd8wiASkvQb2ZQ9xBRzGC63PU5eFNQg&mra=pe&mrcr=0&sll=47.507092,19.066579&sspn=0.246292,0.441513&ie=UTF8&t=h&z=16 Google Map Route to Hotel Eurostars Center]

'''How to get to the Conference Venue:''' On foot or Get on tho metro line 2 at Astória in the direction of Déli pályaudvar. Get off at Deák Ferenc tér then [[OOoCon2010/Venues#Directions_to_the_Conference_Venue | go to the Conference Venue]]. (You can use Short Section Metro Ticket)

*Manu Arjó, VicePresident Business Development at [http://www.sironta.com Sironta], [mailto:manuel.arjo@sironta.com manuel.arjo@sironta.com], +34 933 535 627, 2-Sep, 3-Sep
*Arthur Buijs, NL.OpenOffice.org Co-Lead, [mailto:arthur@artietee.nl arthur@artietee.nl], +31 (0)654668131, 28-Aug, 3-Sep

== CEU Residence Center ==

[http://maps.google.com/maps?f=d&source=s_d&saddr=1106+Budapest,+Kerepesi+%FAt+87,+Magyarorsz%E1g&daddr=1051+Budapest,+N%E1dor+utca+9,+Magyarorsz%E1g+(CEU)&geocode=Fd_f1AIdMEokASndS7kXqcRBRzEDYtkELVo0bw%3BFbXM1AIdoasiASkn0F0LFdxBRzEgEaZnEyeKJQ&mra=prev&sll=47.499835,19.10243&sspn=0.051608,0.154324&ie=UTF8&z=13 Google Map Route to CEU]

'''How to get to the Conference Venue:''' Take any bus that stops opposite the Residence Center and go to the final station ("Örs Vezér tér") - 3 stops if you take the No. 44 and 4 stops if you take the No. 45. Look for the underpass that leads you to the Metro and take it to "Deák tér" then [[OOoCon2010/Venues#Directions_to_the_Conference_Venue | go to the Conference Venue]].

*Andrea Pescetti, Italian N-L Project Lead, pescetti@ooo, - , 31 Aug, 3 Sep
*Olivier Hallot, BrOffice.org/OpenOffice.org Brazil, [mailto:ohallot@openoffice.org ohallot@openoffice.org], +552188228812, 29-Aug, 4-Sep
*Gustavo Buzzatti Pacheco, BrOffice.org/OpenOffice.org Brazil, [mailto:gbpacheco@openoffice.org gbpacheco@openoffice.org], +555184029927, 29-Aug, 5-Sep
*Leo Moons, Translator/member nl.openoffice.org, Belgian, [mailto:vpanter@openoffice.org vpanter@openoffice.org], +32 475 241646, 30 Aug - 4 Sep
*Cor Nouws, community representative Community Council, marketing nl-OpenOffice.org, owner Nou&Off, Netherlands,[mailto:oolst@nouenoff.nl oolst@nouenoff.nl], + 31 625 207001, 29/30 Aug - 5 Sep
*Samphan Raruenrom, Thai N-L Project Lead, samphan at openoffice.org, 29 Aug - 4 Sep
*Tatat Thanakanok, Thai N-L Project member, tatat at openoffice.org, 29 Aug - 4 Sep
*Jan de Jong, Translator/member nl.openoffice.org, Netherlands, [mailto:pcs-ooo@live.nl pcs-ooo@live.nl] +31623798086, 30 aug - 4 sep
*Javier Sola, KhmerOS Project. Cambodia - 31st Aug - 3 Sep
*Alexandro Colorado OpenOffice.org Español / OOoES, Mexico [mailto:jza@openoffice.org jza@openoffice.org], +529931733362, 31-Aug - 6-Sep
*Marco Fioretti http://mfioretti.com, Italy - 31 Aug - 4 Sep [mailto:jza@openoffice.org mfioretti@nexaima.net]

== Alta Moda Fashion Hotel, 13 Nádor Utca 1051. ==

[http://www.splendia.com/en/alta-moda-fashion-hotel-budapest.html#map Map]

'''How to get to the Conference Venue:''' On foot

*[http://www4.plala.or.jp/k21/ Katsuya Kobayashi], Marketing Project member, [[Special:EmailUser/kynh|kynh]], , 30-Aug, 4-Sep
*Rony G. Flatscher, WU Wien, 31 Aug - 4 Sep

== Mercure Budapest Duna, Soroksari ut 12 ==

[http://maps.google.com/maps?q=Mercure+Budapest+Duna&hl=en&cd=1&ei=_bliTLXII5DyObH1mBk&vps=2&jsv=264c&sll=47.4793,19.0684&sspn=1.258326,3.140552&ie=UTF8&lr=lang_pt|lang_en&view=map&cid=15417917116959416148&iwloc=A&ved=0CIkBEKUG&sa=X Map]

'''How to get to the Conference Venue:''' Get on tram number 2 in the direction of Jászai Mari tér. Get off at Roosevelt tér (Roosevelt square) then [[OOoCon2010/Venues#Directions_to_the_Conference_Venue | go to the Conference Venue]].

*Leif Lodahl, Danish language coord, lodahl@openoffice.org
*Paulo Vilela, Marketing OOo Portugal, [mailto:pvilela@openoffice.org pvilela@openoffice.org], +351912591908, 30-Aug to 3- Sep
*Clayton Cornell, Documentation Project co-lead, [mailto:ccornell@openoffice.org ccornell@openoffice.org], 31 Aug to 03 Sept
*Chao Sun, Architect of Redflag2000, [mailto:sunchao@redoffice.com], 30Aug to 03Sept
*Heng Li, Proformance project co-lead, [mailto:liheng@redoffice.com], 30Aug to 03Sept
*Yu Liu, ODF project developer, [mailto:liuyu@redoffice.com], 30Aug to 03Sept
*Jesús Corrius, Catalan Native Lang Project Leader, [mailto:jesus@softcatala.org], 31Aug to 04Sept
*Joost Andrae, QA Project co-lead and release manager, [mailto:ja@openoffice.org ja@openoffice.org], August 31 to September 03
*Oliver-Rainer Wittmann, Writer Project co-lead, [mailto:od@openoffice.org], August 30 to September 04

== Mercure Budapest Buda, Krisztina Korut 41-43 ==

[http://maps.google.com/maps/place?cid=15227343547741076547&q=Mercure+Budapest+Buda+Krisztina+Korut+41-43+Hungary&hl=en&cd=1&ei=-BtjTI7XGYz8Oajx0dUC&sig2=NO51ehG49IYr2_G81o43Hw&dtab=0&sll=47.4987,19.0272&sspn=0.071946,0.1348&ie=UTF8&ll=47.51523,19.000769&spn=0,0&z=14&iwloc=A Map]

'''How to get to the Conference Venue:''' Get on metro line 2 at Déli pályaudvar in the direction of Örs vezér tere. Get off at Deák Ferenc tér then [[OOoCon2010/Venues#Directions_to_the_Conference_Venue | go to the Conference Venue]]. (You can use Short Section Metro Ticket)

*Dmitri Popov, Freelance contributor, [mailto:dmpop@openoffice.org dmpop@openoffice.org], August 30 - September 3

== Hotel Ambra, Kis Diofa 13 ==

[http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=kis+diofa+13,+budapest&sll=47.508853,19.067116&sspn=0.053107,0.168743&ie=UTF8&hq=&hnear=Budapest,+7+ker%C3%BClet,+Kis+Di%C3%B3fa+utca+13,+Ungheria&z=16 Google Map of Location]

'''How to get to the Conference Venue:''' On foot

*Italo Vignoli, President Associazione PLIO (Italian NLP), [mailto:italo@italovignoli.com italo@italovignoli.com], +39 348 5653829, August 31 - September 4

== InterContinental Budapest Hotel, Apáczai Csere János utca 12-14 ==

*Rob Weir, [mailto:rob@robweir.com rob@robweir.com], +1 978 467 5445, Aug 30th-Sept 4th
*Don Harbison

== Silver Hotel Budapest City Center, VI., Hunyadi tér 11. ==

[http://maps.google.de/maps?f=q&source=s_q&hl=de&geocode=&q=Silver+Hotel+Budapest+City+Center+***,+1067+Budapest,+Hunyadi+t%C3%A9r+11.,+Hungary&sll=51.151786,10.415039&sspn=18.620805,52.163086&ie=UTF8&hq=Silver+Hotel+Budapest+City+Center+***,&hnear=1067+Budapest,+VI.+ker%C3%BClet,+Hunyadi+t%C3%A9r+11,+Ungarn&t=h&z=16 Map]

*Christoph Noack, User Experience Project Co-Lead 
*Jacqueline Rahemipour, Co-Lead de.openoffice.org 
*Andreas Mantke, Content Developer, OOo Portable, OOoPDFConverter 

==Castle Garden, Lovas út 41, 1012 Budapest==

* mechtilde@openoffice.org

[[Category:Marketing]]

OOoCon2010/Around the conference venue

2010-08-25T07:37:55Z

Andreasma: /* Food & Drink in the Vicinity */

{{Marketing}} [[Category:OOoCon]] [[Category:OOoCon2010]]
__TOC__
== Around the conference venue - CEU & its Surroundings ==

=== Wireless Internet Coverage ===

'''FACULTY TOWER - '''Nádor u. 9

'''Network name: LAPTOP_AREA with no password'''

'''NÁDOR 11 BUILDING'''

'''Network name: ’LAPTOP_AREA_N11’'''

'''Password: ’nador11access’'''

'''OTHER WIRELESS INTERNET COVERED AREAS'''

OCTOGON LOBBY Nádor u. 9’s main entrance

LIBRARY

JAPANESE GARDEN: 2nd floor Monument Building

CAFE BAR MONUMENT BUILDING – 1st floor

'''Network name: LAPTOP_AREA with no password'''

=== Food & Drink within CEU ===

Faculty Tower Restaurant Faculty Tower building, 8th floor

Cafeteria''' '''Nádor u. 9 building, Ground floor

Snackbar and Lounge AreaNádor 9

=== Food & Drink in the Vicinity ===

==== CAFÉS ====

Sir Morik Café Nádor u. 5

Sundance Oktober 6 u. 9

Brunch Sandwich Bar Arany János u. 16

California Coffee CompanySzent István tér

==== LUNCH VENUES ====

'''Roosevelt Self-Service Restaurant'''Roosevelt tér 7-8

Buffet with a wide choice of soups, international

and vegetarian dishes and desserts, take-away

'''Sir Morik Café '''Nádor utca 5

Excellent coffee. Sandwiches, ice cream, cookies

'''Budapest Anno Café '''Nádor u. 5

Set meals and salads at reasonable prices

'''Feinkost '''Nádor utca 17

Cheap lunch menus, home-style cooking and Gyros

'''Terv Eszpressz'''Nádor u. 19

Drinks, sandwiches and salads

'''Coffee-to-go '''Október 6 u. 6

Coffee, tea, sandwiches, quiches and pies

'''Strudel House'''Október 6 u. 22

Home-made strudel, breakfast or a hot meal

'''Sundance Sandwiches '''Október 6 u. 9

Sandwiches and salads, tea and coffee

'''Duran Sandwich Bar '''Október 6 u. 15

Sandwiches, no sit-downs, only takeaway

'''Kisharang '''Október 6 u.17

Hungarian-style cooking at reasonable prices

'''István Cukrászda '''Október 6 u. 17

Home-style cakes and cookies, ice cream

'''Cicero Kávézó'''Október 6 u. 17

Salads, hot chocolate, coffee, sandwiches

'''Kheiron Café and Restaurant '''Október 6 u. 22

Hungarian and international dishes, snacks

and salads

'''Gyros '''Zrinyi u. 16

Snacks and soft drinks

'''Café Montmartre '''Zrinyi u. 16

Salads, sandwiches, coffee, tea

'''Veltins '''Sas u. 12

Salads and hot dishes at reasonable prices

'''Brunch and sandwich bar '''Arany János u. 16

Pastries, dairy products and sandwiches

'''Emporio Bar & Restaurant '''Arany János u. (Bank Center)

Lunches and drinks

'''Fruccola '''Arany János u. 32

Excellent soups, hot and cold baguettes,

coffee, salads, croissants, healthy joghurt

and bio drinks, freshly squeezed juices

'''Café Zaccos '''Corner of Arany János & Hercegprimás u.

Sandwiches and salads, cookies and cakes.

'''Petit Café Vian '''Hercegprímás u. 21

Breakfasts, snacks, lunches and tea

'''Salaam Bombay '''Mérleg u. 6. (Starlight Hotel building)

Indian restaurant and take-away

'''Kis Kukta '''Mérleg u.10

Inexpensive lunches.

'''Chinese Fast Food Restaurants'''

Several, e.g. Október 6 u. 6

Nádor u. 20

Hercegprímás u. 4

'''Görög Ételek '''Corner of Akadémia and Széchenyi u.

Gyros and other Greek dishes, falafel

and salad bar

'''SLIGHTLY MORE UPSCALE DINING ESTABLISHMENTS CLOSE TO CEU:'''

'''Govinda '''Vigyázó Ferenc u. 4

A real feast for vegetarians; exotic salads,

herb teas

'''Kama Sutra '''Október 6 u.17

Indian food, business lunches

'''Dió Restaurant & Bar '''Sas u. 2

Traditional Hungarian flavours and

modern fusion cooking

'''Mokka Restaurant '''Sas u. 4

French cuisine with Moroccan touch

'''Cafe Kör '''Sas u.17

Excellent food, trendy design, polite service.

Reserve a table in advance

'''La Fontaine '''Mérleg u.10

French-style cuisine in authentic surroundings,

romantic live music in the evenings

'''Trattoria Pomo D’Oro '''Arany János u. 9

Italian food

'''La Romana '''Arany János u.18

Italian food

'''Club Pirro '''Hercegprímás u.18

Quality food. Set meals

'''Leroy Kávéház '''Corner of Sas u. and Szt. István tér

Big salads, soups and other dishes.

'''Tom George Restaurant and Café '''Október 6 u. 8

Specialties of contemporary Hungarian

and international cuisine

'''Gresham Coffeehouse '''Roosevelt tér 5 (Four Seasons Hotel)

'''Páva Restaurant '''Roosevelt tér 5 (Four Seasons Hotel)

'''Via Luna '''Nagysándor József u.1

Italian and international cuisine

'''Iguana '''Zoltán u.16

Mexican and American food

'''Chinese Restaurant '''Corner of Széchenyi and Nádor u.

Authentic Chinese, quality food, not

the fast food-type

DE/LinuxTag2010

2010-05-18T19:53:05Z

Andreasma: /* Personalplan */

[[Category:De.openoffice.org]]
{{DISPLAYTITLE:OpenOffice.org auf dem LinuxTag 2010}}
= Allgemeines =

Auf dieser Seite wird der Messeauftritt von OpenOffice.org auf dem LinuxTag 2010 koordiniert. Ansprechpartner für die Organisation ist [mailto:jrahemipour@openoffice.org Jacqueline Rahemipour] 

Der LinuxTag findet vom 09. - 12.06.2010 in Berlin statt. OpenOffice.org stellt in '''Halle 7.2b, Standnummer 213''' aus.

Zusammen mit uns werden auf unserem Stand ausstellen:

* Stadt München
* Moneypenny
* Teamdrive

= Informationen für Besucher =

Als freies Projekt haben wir ein Kontingent an E-Freitickets für unsere Besucher erhalten. Bitte kurze Nachricht an [mailto:jrahemipour@openoffice.org Jacqueline] mit der Anzahl der gewünschten Karten.

= Personalplan =

{| cellspacing="1" cellpadding="1" border="1"
|-
| width="250" | '''Name'''
| width="100" | '''Di. 08.06.''' (Aufbautag)
| width="100" | '''Mi. 09.06.'''
| width="100" | '''Do. 10.06.'''
| width="100" | '''Fr. 11.06.''' (Vortragstag)
| width="100" | '''Sa. 12.06.''' (Abbau)
|-
| Jacqueline Rahemipour
| X
| X
| X
| X
| X
|-
| Jörg Schmidt
| X
|
|
|
|
|-
| Florian Effenberger
| X
| X
| X
| X
| bis Mittag
|-
| [[User:Mbayer|Martin Bayer]]
| ✔
| ✔
| ✔
| ✔
| (am Abend zum Abbau, falls dringend Hilfe benötigt)
|-
| Andreas Mantke
| X
| X
| X
| X
| X
|-
| nn
|
|
|
|
|
|}

DE/QA-Wochenende2010

2010-04-23T16:37:05Z

Andreasma: /* Angemeldete Teilnehmer */

[[Category:DE|QA-Wochenende2010]]
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}}
=QA-Wochenende 2010 Linux-Hotel Essen=

== Adresse ==

Linux-Hotel / Villa Vogelsang 
Antonienallee 1 
45279 Essen-Horst 
Tel.: 0201 8536-600 
Fax: 0201 8536-605 
E-Mail: rezeption@villa-vogelsang.de

== Ansprechpartner / Organisation ==

Jacqueline Rahemipour 
jrahemipour@openoffice.org 
Tel.: auf Anfrage

== Termin ==

30.4.-02.05.10

Die Anreise kann schon am Freitag erfolgen oder auch am Samstag früh. Das Programm beginnt am Samstag, 1.5.2010 ab ca. 10 Uhr und endet am Sonntag, 2.5.2010 um ca. 14 Uhr, damit genug Zeit für die Heimreise bleibt. Falls gewünscht können wir den großen Seminarraum bereits am Freitag nutzen.

== Worum geht es? ==

* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen
* Erfahrungsaustausch mit erfahrenen QA'lern
* Konkret anstehende Aufgaben gemeinsam bearbeiten
* die "schönsten" Bugs finden
* Die anderen netten Leute aus dem Projekt kennenlernen
* In geselliger Runde über OOo und die Welt quatschen
* und vieles mehr

In erster Linie soll das Wochenende denjenigen dienen, die im de-Projekt bereits erste Erfahrungen mit der QA-Arbeit gemacht haben. Es geht nicht darum, dass man für die Teilnahme viel wissen muss. Im Grunde muss nur das entsprechende Interesse für QA / Lokalisierung da sein und die Bereitschaft, auch mal an einer konkreten Aufgabe in diesem Bereich mitzuarbeiten.

== Angemeldete Teilnehmer ==

{| cellpadding="2" border="1"
|-
! Nr.
! Name
! Vorname
! Anreise am
! ggfs. Uhrzeit
! mit Übernachtung?
! Bemerkungen
|-
! 1
| Rahemipour
| Jacqueline
| Freitag
| ca. 14 Uhr
| ja
|
|-
! 2
| Wilper
| Simon
| Freitag
| ca. 14 Uhr
| ja
|
|-
! 3
| Pechlaner
| Wolfgang
| Freitag
| ca. 13 Uhr
| ja
| Vegetarier
|-
! 4
| Schnabel
| André
| Freitag
| gegen 19:30
| ja
|
|-
! 5
| Effenberger
| Florian
| Freitag
| ca. 18/19 Uhr
| ja
|
|-
! 6
| Stehmann
| Mechtilde
| vorauss. Freitag
|
| ja
|
|-
! 7
| Hackert
| Thomas
| Samstag
| ca. 10:00
| ja
| Vegetarier (steht aber leider erst kurz vorher wirklich fest, sorry ... :( )
|-
! 8
| Stehmann
| Michael
| vorauss. Freitag
|
| ja
|
|-
! 9
| Brekenfelder
| Ulf
| Freitag
|
| ja
|
|-
! 10
| Geib
| Gerald
| Freitag
|
| ja
|
|-
! 11
|
| 
| 
|
| 
|
|-
! 12
| Strohmaier
| Friedrich
| Freitag
| abend
| ja
|
|-
! 13
| Andrae
| Joost
| Freitag (noch unklar)
| Abend
| ja
|
|-
! 14
| Altmann
| Uwe
| Samstag
| nachmittag gegen 16:00
| ja
| suche für So MfG nach Köln
|-
! 15
| Behrens
| Thorsten
| Samstag
| mittags (voraussichtlich)
| ja
|
|-
! 16
| Lohmaier
| Christian
| Freitag
| nachmittag
| ja
| ist gerne scharf, wünscht sich deshalb ein Chili-Ketchup :-))
|-
! 17
| Bircher
| Raphael
| Freitag
| Abend
| ja
|
|-
! 18
| Mantke
| Andreas
| Samstag
| vormittag
| nicht erforderlich
|
|}

== Geplantes Programm ==

Das ganze ist als grobe Hülle gedacht, in den einzelnen Blöcken sollte immer Zeit für Diskussion bzw. direktes Arbeiten enthalten sein. In der Regel dürften die Themen für fast alle interessant sein. Es sollte aber immer die Möglichkeit gegeben sein, dass einzelne etwas Abseits an anderen Themen arbeiten.

===Themenvorschläge===

[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]

[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]

* '''OpenOffice.org unter Linux x86 selber bauen -- RELOADED''' (Simon Wilper)
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?
** Mercurial bedienen
** ./configure-Optionen
** Build-Tools
** Fehlerbehebung anhand eines Beispiels

* '''Wie geht es weiter? - QA und Release-Prozess in der Community''' (Mechtilde - Unterpunkte von Uwe Altmann)
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?
** Das zielt
**# auf neue Interessenten
**# auf welche wie mich, die das nur sporadisch verfolgen (es haben sich aber einer Menge Strukturen in der letzten Zeit geändert) - es würde mich selbst interessieren, wie das Projekt inzwischen kommuniziert.
**# auf "...haben wir dazu eine Präsi??" ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.

* '''QA von Extensionen''' (Michael)

===Samstag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:15
|| '''Begrüßung'''
* kurze Absprache des Arbeitsplanes
* Fragen zu Technik
* Organisatorisches
|| Jacqueline Rahemipour
|-

! 10:15-11:15
|| ''''''
*
||
|-

! 11:30-12:30
|| ''''''
*
||
|-

! 12:30-14:00
|| '''Pause''' Mittagessen
|| alle
|-

! 14:00-15:30
|| ''''''
*
||
|-

! 15:30-16:00
|| '''Pause''' Kaffee und Kuchen
|| alle
|-

! 16:00-17:00
|| ''''''
*
||
|-

! 17:00-Open End
|| '''Bughunting'''
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen
* neue Issues aufgeben
* Fehlersuche
|| alle
|-

|}

===Sonntag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:45
|| ''''''
*
||
|-

! 11:00-11:45
|| ''''''
*
||
|-

! 12:00-13:00
|| ''''''
*
||
|-

|}

== Anreise ==

=== S-Bahn ===
Die S-Bahn-Haltestelle "Essen-Horst (S)" (Linie S3) ist nur 8 Minuten Fußweg vom Hotel entfernt. Am S-Bahnhof Horst ankommen aus Richtung Essen-Hbf, dann bitte unter den Gleisen durchgehen, den Fußweg den Berg hinauf, geht über in kleine Straße, am Ende rechts Lindkenshofer Weg) und nach 200m wieder rechts (Eberhardstr) und dann gerade auf ein braunes Holztor zugehen.

=== Bus ===
Die Haltestelle "Geschwister-Scholl-Str." der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.

=== PKW ===
Den groben Weg aus Richtung A 40 entnehmt bitte der Skizze auf den Seiten des [http://www.linuxhotel.de/anreise.html Linux-Hotels] bzw. befragt einen Routenplaner. Folgt den Schildern „Route Industriekultur“ in Richtung "Eisenbahnmuseum". Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder "Villa-Vogelsang".

== Übernachtung ==

Die Übernachtung erfolgt in Doppelzimmern im Linux-Hotel, die Kosten dafür übernimmt der Verein OpenOffice.org Deutschland e.V.. Die genaue Raumverteilung machen wir vorort. Sonderwünsche bitte frühzeitig Jacqueline mitteilen!

== Verpflegung ==

Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel.

Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.
'''Gerne werden Salatspenden angenommen!'''
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.

'''Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.'''

Auch für Getränke wird gesorgt. Ihr könnt euch im Linux-Hotel bei den Getränken selbst bedienen (alkoholfreie Getränke, Bier, Kaffee, Tee). Besondere Getränke (Wein, Spirituosen) sind in der mit dem Linux-Hotel vereinbarten Getränkepauschale nicht enthalten. Diese müssen dann selbst vorort bezahlt werden.

== Seminarraum ==

Es steht uns ein großer Seminarraum zur Verfügung. Auch ein Beamer wird vorort sein. Bitte bringt wenn möglich euer eigenes Notebook bzw. einen eigenen Rechner mit.

Falls jemand keinen eigenen Rechner mitbringen kann, bitte vorab Bescheid sagen, damit wir gegebenenfalls noch etwas organisieren können (mehrere Vereinsrechner stehen zur Verfügung, 3 weitere Laptops kann ich mitbringen).

== Internet ==

Im Hotel und im Seminarraum ist WLAN verfügbar, jedoch sollten wir uns aufgrund der Erfahrungen in den letzten beiden Jahren nicht darauf verlassen und wenn möglich noch Netzwerkkabel mitbringen.

== Freizeit ==

Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Badetücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.

== Sonstiges ==

Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochenende auf uns allein gestellt, das heißt:

* Es herrscht an dem Wochenende Selbstbedienung, an den Getränkekühlbüffets / Weinkühlschrank / Kaffee/Teeautomat usw., Geschirr muss hinterher in die Spülmaschine geräumt werden.

* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen

* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug & Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.

'''Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräumarbeiten behilflich sein?'''

User Experience/Improving OOo Default Settings

2010-04-21T20:43:39Z

Andreasma: /* Renaissance Subproject to Achieve Better Default Settings */

{{User Experience}}

 

== Renaissance Subproject to Achieve Better Default Settings ==

''' '''

'''Executive summary:''' Please locate your favorite low hanging fruits by _'''end of April'''_ to improve default settings in Impress (or all apps for later, but the lmpress focus is till end of April)

 

"Better Defaults", as this effort is called for short, aims to collect suggestions for better default settings in OOo. First in Impress (in accordance with the present focus of project Renaissance) and later in the other OOo applications. This is a subproject of [http://wiki.services.openoffice.org/wiki/Renaissance Project Renaissance], so it is listed on the [http://wiki.services.openoffice.org/wiki/Renaissance:Impress#Current_Work "Current Work" wiki page] .

 

What does "better defaults" mean? Well, I KNOW there are default settings that you change first thing when you install a new version of OOo. So please share what they are and why the change(s) make(s) your life much easier. 

For example, two issues Frank found are:

Make objects same size {{bug|54281}}

Text area selection is not very accurate and covers other objects. {{bug|96548}}

One default setting changed recently was {{bug|2446}} Boy did that feel good! Let's find more of those.

 

'''Low Hanging Fruit Clause'''

No new features. The developer should only have to flip a switch on something that is already alive and kicking in the office suite, but just not set as the default. We want results, so the low hanging fruits are the ones we want to grab.

 '''How to Get Started'''

Find existing default setting issues or write new RFEs in IssueTracker (use "default" in the title and keyword) and add them to list in the table on this wiki page. Or, if RFE writing is not your kind of thing, just write your desires to achieve default utopia ;-) in the table below. Be sure to make it clear where the feature is located (write down where to click to get there) and why it is better to set the default the way you want it as compared to the old setting. 

If you have a complex issue or several defaults in the same area, it would be best if you create an individual wiki page (put link to it in the table below) for all the related defaults like Chris did (see [http://wiki.services.openoffice.org/wiki/GoodDefaults_GridHandling Grid Handling].) Each individual default setting being suggested can then be discussed on the respective wiki pages, just like the discussion in the table at the bottom of the Grind Handling wiki page. That information will serve as the basis for decision making when it comes to evaluation time, because the iTeam will have the discussion and details all in one place (wiki page) and not jumbled all over the mailing lists.

 '''Time Frame'''

Please get your 2cents in by the END of APRIL for OOo Impress. Then the iTeam can evaluate the suggestions and decide what to implement with the resources they have. The other applications will follow within the scope of the [http://wiki.services.openoffice.org/wiki/Renaissance Renaissance project]. 

'''List of Better Default Setting Suggestions'''

{| width="100%" class="prettytable"
|-
! scope="col" | Idea 
! scope="col" | Application 
! scope="col" | Description 
! scope="col" | Name 
|-
| Rotation Mode, Guides when Moving on
| Impress
| 'Rotation Mode after Clicking Object' & 'Guides When Moving' are two feature options which are switched off by default => they should be switched on by default (more info: [http://wiki.services.openoffice.org/wiki/GoodDefaults_GridHandling Grid Handling]).
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Change Handle Size
| Draw/Impress
| The current handle size was defined years ago - with displays offering less density than today. I propose to change the default handle size to "large". This option can be found in the toolbar "Options" (more info: [http://wiki.services.openoffice.org/wiki/GoodDefaults_GridHandling Grid Handling]).
| [[User:ChristophNoack|ChristophNoack]] 
|-
| bullet point lists
| Impress
| Bad standard defaults of bullet point lists. If one creates a text frame in Impress and clicks on the button "numbering and bullet points" (Nummerierung und Aufzählungszeichen), the newly created bullet point list has terrible standard defaults:
*(1) Almost no space between the bullet point and the text.
*(2) No ident for the second line of text under a bullet point. The second line appears left-justified directly under the bullet point. Instead, there should be a ident of the second line. It should begin exactly there where the first letter in the first line starts.

| [[User:Gerald|Gerald]]
|-
| default colour of drawing objects
| Draw/Impress
| The default color of drawing object is ugly and has not changed since the 1990ies. For more details, see {{issue|93507}}
| [[User:Gerald|Gerald]]
|-
| 'Right page' should be next style to 'Left page'
| Writer
| {{Bug|15498}}
| Name
|-
| Ugly style sheets for headings in Writer
| Writer
| I used Writer for several articles, publications, flyers and in all of them the standard headings look ugly and outdated. Any designer would not choose these style sheets for Heading 1-10. Furthermore, in this regard the competition has made large steps forward during the last release cycles.
| [[User:Gerald|Gerald]]
|-
| Make manual page break in Writer better visiable
| Writer
| for example use 'light blue' and a thicker line. {{bug|33518}} and duplicates {{bug|65150}}, {{bug|82353}}, {{bug|96963}}, {{bug|22646}}
| Name
|-
| Default line too thick
| Chart
| especially XY-Charts need hairline lines.{{bug|98803}}
| Name
|-
| Idea
| Draw
| Include toolboxes circles, rectangles, text instead of single symbol in drawing toolbar. Reasoning: (1) The 'circles and ovals' and the 'text' toolbox is not accessible via View - Toolbars in Draw. So currently the only way to access arcs and legends is to customize the drawing toolbar. (2) Draw is used for technical constructions and there those objects are often used, in contrast to Writer or Impress, where drawing objects are used for illustrations in most cases. (3) Using the toolboxes needs no more space than single objects and give you a quick access too, because the last used object remains above for single click.
| [[User:Regina|Regina]]
|-
| Add Math formula icon to standard bar
| All
| Math objects are often used in technical documents. You need the way Insert - Object - Formula to insert one. That is too long. For example consider writing a math text for school, which has about twenty formulas per page usually.
| [[User:Regina|Regina]]
|-
| Distance in numbering styles larger
| Writer
| Make the distance from number to text in numbering styles larger, so that 10. text is still in line.
| [[User:Regina|Regina]]
|-
| Add a gap in table of contents
| Writer
| Add a gap (tab or space) between number and text in table of contents in Writer. The picture shows the ugly default settings. Notice the missing space between number and heading text. [[Image:UglyDefaultSpaceInTOC.png]]
| [[User:Regina|Regina]]
|-
| Use parallel perspective for 3D-scene
| Draw
| 3D-scenes in Draw are to illustrate constructions. Often several 3D-objects are combined in one scene. Working with several objects is faulty if ''perspective'' is on. So the first step when working with 3D-objects is to switch to parallel projection. It is "faulty" because it is unhandy to arrange or rotate objects inside a scene when in central perspective and because of {{bug|67847}}.
| [[User:Regina|Regina]]
|-
| Set margins in style of Math formula objects to 0cm
| Writer
| Set margins in style of Math formula objects in Writer to 0cm. {{bug|22136}}
| [[User:Regina|Regina]]
|-
| Add a spacing below for tables
| Writer
| Add a spacing below for tables in Writer. In normal text flow the style ''text body'' is used, which gives good distance between two paragraphs. It has a spacing above of 0cm and a spacing below of 0.21cm. But after a table the text nearly touches the border of the table, because the table has spacing 0cm. And if you do not use borders the spacing is to small too, because the style ''Table contents'' has below spacing 0cm too.
| [[User:Regina|Regina]]
|-
| Uncheck transparency warning
| All
| Uncheck transparency warning in Tools > Options. Modern PCs are fast enough to calculate transparency. So most oft the users no longer need this warning.
| [[User:Regina|Regina]]
|-
| change default color in form wizard
| Database
| the default background color of an default form document, created by the form wizard, is anything like orang -> this is a bad default and looks unprofessional => change it in anything common like 'light gray'
| [http://wiki.services.openoffice.org/wiki/User:Msc MSC]
|-
| switch off impress wizard
| Impress
| looks old fashioned, is redundant and annoying
| [http://wiki.services.openoffice.org/wiki/User:Wg WG]
|-
| Default Clipboard Format for vector graphics
| All except Draw
| If someone paste a vector graphic into a document, he normally doesn't intend to edit it there, but most probably he needs to resize it. Unfortunately scaling of embedded Draw graphics doesn't work, because text will not scaled proper. Until this work, the user must use Paste Special->As GDI-Metafile. I think GDI-Metafile should be the default here.
| Jörg
|-
| Changing default font
| Impress & Draw
| {{bug|70585}} It should be possible to change the overall default font for text (not the GUI)
in Impress permanently, using one centralized setting, for example Options -> Openoffice.org -> fonts -> Change default font or somewhere similar. This is especially a problem when working with asian languages. I know you can work around the problem using templates, but it is neither quick, nor is it likely to appear obvious to the average user.

| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Change default pen color from neon green
| Impress
| {{bug|47990}} As described in BUG 10922 the neon green color of the pen used to draw on a
presentation is very difficult to see for students in a classroom, and the color is hard coded into OOo. I would like to see the default changed to perhaps black or red, as they are much easier colors to see. BUG 10922 is still a very good idea, but I filed this report to request a simple change of the default color, which should be much easier than what BUG 10922 is requesting. A slightly more ambitious, but still not difficult, would be to read the color value from a file or some such, instead of hard coding it in the OOo source. p.s. available after .. menue: slide show / slide show settings & check 'mouse pointer as pen' & starting a presentation 

| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]

|-
| Options for line width of the pen (in slideshow mode)
| Impress
| The pen in the slideshow mode has a very small line width. Therefor it is not visible for all partipants of a presentation. If something should be market the pen had to be much wider. The pen is available after you set in menue: slide show / slide show settings & check 'mouse pointer as pen' & starting a presentation.
There is already a patch for the pen integrated into the go-oo-build, that gives the posibility to change the configuration of the pen (color, line width etc.).Please integrate this patch into vanilla-ooo.
| [http://wiki.services.openoffice.org/wiki/User:andreasma andreasma]

|-
| change configuration of the pen during slideshow mode
| Impress
| It should be posible to change the configuration of the cursor (from arrow to pen) during the presentation mode (via context menu). There is already a patch for the pen available, that is integrated into the go-oo-build. It gives the posibility to change the configuration of the pen. I don't know yet, if it makes the options dialog also available during the presentation mode. Please integrate this patch into vanilla-ooo.
| [http://wiki.services.openoffice.org/wiki/User:andreasma andreasma]
|-
| Don't emulate MS Office's annoying "clippy"
| All
| Options | OpenOffice | General and then Turn off Help Agent and Turn on Extended Tips
| Safway
|-
| Please set all checkboxes in Change Tools --> Options --> Load/Save --> Microsoft Office by default
| All
| It is very annoying that these checkboxes are not checked by default because users which own Microsoft Office and open a document with an Excel OLE-object see a document in a different way than a user who does not have Microsoft Office installed. This is because (by default) an installed Excel is used to render the xls-diagrams while (when Excel is not installed) OpenOffice.org is used to render it. When a user sends such a document to a different user it seems as if OpenOffice.org does not display the document in the same way as on the other computer. But the problem is in the OLE-object. When the boxes are checked it would be a better default.
| parity
|-
| Tab Stops with reasonable settings
| All
| Tools > Options > Writer or Writer/Web or Calc or Impress or Draw > General > Settings > Tab stops = 0.50 instead of 0.49
| Safway
|-
| Grid Settings much more manageable and understandable
| All
| Tools > Options > Writer or Writer/Web or Calc or Impress or Draw > Grid
Snap to Grid should be off. Visible Grid should be off. Resolution > Horizontal = 0.10 instead of 0.39. Resolution > Vertical = 0.10 instead of 0.39. Synchronize axes should be on.

| Safway
|-
| Table keyboard handling consistent
| Calc
| Tools > Options > Calc > Table > Keyboard handling > Insert cell > Column = 0.20 like the others instead of 0.98.
| Safway
|-
| Anchor context sensitive toolbars by default
| All
| Context sensitive toolbars (like table, image toolbars) is a great feature
when you get used to it, but new users just see a toolbar popping in front of their work. I always dock those toolbars to the bottom edge of the window. I think this could be a good default for new (and old) users.

| RGB
|-
| Change "Show as tip" for word completion
| Writer
| The word completion is a useful feature, but the way it is shown by default is quite "disturbing": if a
long suggestion pops when you are near the page edge the word you are writing will jump to next line. "Show as tooltip is a better alternative, IMO. The option is on Tools -> AutoCorrect Options -> Word Completion tab

| RGB
|-
| Space Markers Off
| Writer
| Turn off markers for spaces (small dots between words).
| [[User:Mr smyle|mr_smyle]]
|-
| Shortcut For Insert Comment
| Calc, Writer
| Like Ctrl+Ins or Shift+Ins
| [[User:Mr smyle|mr_smyle]]
|-
| Text Paragraph Indents
| Writer(RU)
| For style 'Text Body' in RU Locale. Off top margin. Add first line indent 1cm. On justify.
| [[User:Mr smyle|mr_smyle]]
|-
| Many Issues From helen_russian
| All
| Look at this page, please: http://translate.google.com/translate?js=y&prev=_t&hl=en&ie=UTF-8&layout=1&eotf=1&u=http%3A%2F%2Fmyooo.ru%2Fcontent%2Fview%2F58%2F1%2F&sl=ru&tl=en -- [[Renaissance:Status Meetings:2010-02-22|Discussion was here]] at 5:05:35 PM
| [[User:Mr smyle|mr_smyle]]
|-
| Show Color Panel
| Impress
| View -> Toolbars -> Color Bar
| [[User:Mr smyle|mr_smyle]]
|-
| Please include presenter screen in default install set of OOo.
| Impress
| Only this integration in the default install set would make the presenter console usable for many use cases: See more detailed description in {{issue|90415}}.
| [[User:Gerald|Gerald]]
|-
| Remove the limits on multi-level undo!
| All
| I assume that this limit is just an out-dated, but hard coded default setting. Please see: {{issue|98009}}
| [[User:Gerald|Gerald]]
|-
| Styles and formatting panel docked right
| Writer
| Styles and formatting panel is floating and that's annoying, partialy because it obstructs sight from file in edition.It should be in right side (or left) docked so it's always in the same place, and doesn't obstruct the documents.
| [[User:Xihh|xihh]]
|-
| Find & Replace after selecting a range should have "current selection only" checked by default
| Calc
| If you select a range of cells before a Find & Replace, it means in 90% cases that you want to act inside this selection. So the option "current selection only" (two clicks more today) should be:
- pre-checked if there is an active cells range selection
- unchecked if there is no active cells range selection

| [[User:Gibi|Gilles Bignebat (gibi)]]
|-
| All OpenOffice.org programmes should use the same default keyboard short-cut for inserting comments
| Impress,Calc,Writer
| Inserting comments in OOo programmes is inconsistent. 1st: since the name has changed from "notes" to "comments", the keyboard short-cut in Writer is still Ctrl-Alt-N, but should be Ctrl-Alt-C now. 2nd: None of these short-cuts works in Impress or Calc. Why?
| [[User:Gerald|Gerald]]
|-
| Default Impress formula font should be much larger
| Impress
| The default font size for formula in Impress (after Insert->Objects->Formula) is 12pt which is too small to read on the screen. It should be 16pt or 18pt. Please see: {{issue|21118}}.
| [[User:Gerald|Gerald]]
|-
| Add default keyboard short-cut for inserting new slide
| Impress
| Please see: {{issue|100650}}.
| [[User:Gerald|Gerald]]
|-
| Remove old word versions from Save As dialog
| Writer
| Take a look at {{issue|21118}}, Word 95 and 6.0 formats aren't being used much anymore, I have had several users accidentally click on them and lose data from the format change. Since they are at least 15 years old and the number of people using Word 95 and 6.0 are likely a very small number I suggest we disable it by default. (It might be possible to move it over to Export?)
| [[User:Gquigs|gquigs]]
|-
| Remove old staroffice files from Save As dialog
| Impress, Writer, Calc
| Similar to above, but I haven't had users do it accidentally yet. It would also go a long way to make the save as-> file format dropdown less overwhelming to users. (It might be possible to move it over to Export?)
| [[User:Gquigs|gquigs]]
|-
| Enable Vertical Text Button for all
| Impress, Draw
| It was disabled apparently on purpose but it makes the interface inconsistent. Also, in many presentations people try to use vertical text and can't find it (I have been asked by my users about this on many occasions). Alternative solution (which seems odd to get this functionality) is to enable "enhanced support for asian languages" by default. Read more {{issue|54423}}
| [[User:Gquigs|gquigs]]
|-
| Enable Vertical Align Buttons
| Calc
| I always enable toolbar buttons for vertical align text in the cells. MT: +1
| [[User:Mr smyle|mr_smyle]]
|-
| Enable Add Comment Button
| Writer
| I always enable toolbar button for adding comment in writer
| [[User:Mr smyle|mr_smyle]]
|-
| Attach Numeric Styles to same Paragraph Styles
| Writer
| At now default paragraph styles 'Numeric paragraph N' 'Marked paragraph N' have not same numeric styles. So, activation of NUMERIC style did not activate numeration of paragraph! It`s very unexpected for trivial user.
| [[User:Dvc|dvc]]
|-
| Use ??/?? as default for fractions instead of ?/?
| Calc
| See {{issue|67862}}
| fst
|-
| New Document Property : PrintIntention
| ALL
| All users who wish to create documents who has to been "printed" by a professional Printer (high resolution) struggles with the same problem: The size/resolution off the graphics inside a OOdocument. I propose to store a "Printer Intention" in the Document see also http://api.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=22239
| Fernand
|-
| Default user annimation
| Impress
| {{issue|62838}} I want to create a user animation with default behaviour: The object just pops up with no tricky animation. Therefore I have to search for this "animation" type (called in german: "erscheinen") every time within the large list of possible animations. This costs me a lot of time. It would be better, when this were the default, and only if I really want fancy animation, then I have to choose from the list. clu: idea .. usage tracking can show if one setting is significantly more often shown than other .. and this one can became the new default
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Duration of pause to 0
| Impress
| {{issue|49762}} In Slide Show settings (Slide Show - Slide Show Settings), Impress features a setting for the "duration of pause before the slide show is repeated". It defaults to 10 seconds. I would suggest to have the default set to 0 seconds in order to improve compatibility with MS Powerpoint users, and secondly to leave the decision to insert a pause to the user.
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Slide Titles editable in navigator
| Impress
| {{issue|21888}} The Navigator is a very handy tool to move through a presentation and it also can act as a mini outline of the presentation. However, now the only way to change the slide title shown is to display the Modify Layout dialog from the Format menu. It would be a very nice addition to allow the user to directly edit the title of the slide shown in the Navigator directly in the Navigator.
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Real Slide Titles in Navigator
| Impress
| {{issue|21888}} It would also be very useful to display the title actually shown on the slide itself as the title unless the user deliberately changed it. The current "Slide 1", "Slide 2", etc. defaults are not very useful for identifying the slide.
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Change default table color
| Impress
| {{issue|102922}} After inserting a table I change the color of my table. I added the data. Now if I want to add a new row, then despite the color of my whole table it inserts the row with default color (blue combination). So I need to select that row again & then change the color. Steps to reproduce the bug:
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Shortcut for adding a new slide
| Impress
| {{issue|100650}}
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Open pps files in show mode
| Impress
| {{issue|52755}} If, during installation, a user choses to associate Microsoft PowerPoint
documents with Open Office, the default behavior for a .pps (PowerPoint Show) file is changed to this:

"C:\Program Files\OpenOffice.org 1.9.109\program\soffice.exe" -o "%1"

This causes the presentation to be opened in edit mode when double clicked. However, when using Microsoft PowerPoint as the default handler, double clicking a .pps file causes it to immediately start the show. To achieve the same behavior, and hence ease the migration from MSO to OOo, I believe the default behavior for .pps files should be as follow durring installation:

"C:\Program Files\OpenOffice.org 1.9.109\program\soffice.exe" -show "%1"

| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Disable "Allow quick editing" mode as default
| Draw/Impress
| The so called quick editing mode at /tools/options/draw/general or /tools/options/impress/general should be disabled by default because people will be able to detect and to move text objects more easily
| [http://wiki.services.openoffice.org/wiki/User:JoostAndrae ja]
|-
| "Number recognition" (in tables) should be turned of by default,
| Writer
| It's usefull for advanced user, but disorientating / annoying for new users. Advanced user can easily switch it on.
| [http://wiki.services.openoffice.org/wiki/User:Camillem CamilleM]
|-
| Default shadow should be transparent and smaller
| Impress
| A better shadow effect can be achieved with Distance : 0,1 cm (instead of 0,3) ; Color : Black (instead of Grey) ; Transparency : 60 % (instead of 0%)
| [http://wiki.services.openoffice.org/wiki/User:Camillem CamilleM]
|-
| "tagged PDF" as default
| All
| PDF-Export: set "tagged PDF" as default (30% bigger files, but accessible by default) .. from letter of MT
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| "don't register" as default
| All
| First-Start-Wizard: "don't register" as default .. from letter of MT
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Improvement Program in startup wizard
| All
| Move the question about participating in the improvement wizard to the first run wizard. (Alternatively put them both as part of the install)
| [[User:Gquigs|gquigs]]
|-
| Don't put OO install files on Desktop
| All
| It makes OO look messy when it has to extract the files to the desktop first. Removing the extra extraction step would be the best, but if not, extracting to a temporary location, and then deleting when done.
| [[User:Gquigs|gquigs]]
|-
| Keyboard shortcut to make fine position adjustments
| Draw, Impress
| I often use the alt+arrow keys to make fine adjustments to the position of drawing objects in Draw and Impress. In Mac OS X, that shortcut is assigned to switch 'Spaces' (the multiple desktops in Mac OS X). Please see {{issue|107125}}
| [[User:Vamsi Kodali|vkkodali]]
|-
| Double-click to bring up 'Position and Size' dialog box
| All
| Currently, the easiest way (AFAIK) to reach the 'Position and Size' dialog box for a drawing or text box object is from the right-click context menu. It would be nice to activate it upon double-clicking on the object ala MS Office. Currently, double-clicking the object brings up a cursor to allow text entry.
| [[User:Vamsi Kodali|vkkodali]]
|-
| Increase default size of graphics cache
| All
| Many users know nothing about the size of the pictures they insert in their documents and they encounter performance problems often due to the too small size of graphics cache. Please see {{issue|63253}}
| [[User:Jbfaure|jbfaure]]
|-
| Change print default to 'All Sheets'
| Calc
| In the file/print dialog the default setting is 'Selected sheets', but should be 'All sheets' and this can confuse normal user because 1. the user await that the whole doc is printed if he push the print button; not from selected sheet on (that can give a lot of confusion) 2. the preview can show a different numbering and amount of pages than the print outcome 3. the user do not await this behavior if he does not made further settings and this is an inconsistent behavior to f.e. writer which print all pages by default (from cj).
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Make the "record changes" feature more attractive
| Writer
| The "record changes" feature is not easy to find. Two suggestions: 1. Rename the toolbar from "Changes" to "Record changes". 2. Add icons to the toolbar buttons to make them more visually appealing.
| [[User:Paperjam|paperjam]]
|-
| Adapt the "update extensions" dialog to make it look like the "extensions manager" dialog.
| All
| The "update extensions" dialog should use the same layout that the "extensions manager" dialog uses.
| [[User:Paperjam|paperjam]]
|-
| No Splash Screen
| All
| Disable the splash screen by default, 3.2 is fast enough starting. it just feels like it is getting in the way.
| [[User:Gquigs|gquigs]]
|-
| Disable OpenOffice's Open/Save Dialogs
| All
| At least on Ubuntu Linux the non OpenOffice dialogs are much much easier to use and more consistent with the platform. You can try for yourself in options -> General -> Open/Save
| [[User:Gquigs|gquigs]]
|-
| Autotext default preview window too small
| Writer
| The default preview window of the Autotext dialogue is too small. It is almost impossible to read the available autotexts in that window.
| [[User:Gerald|Gerald]]
|-
| Do not close Toolbar dialog automatically
| All
| In View-Toolbar we can see a dialog to select the toolbars we want to be visible. Many times we are looking for a set of functions we do not know exactly in which toolbar they are implemented. So we select on toolbar and the dialog closes. We check the functions are not there, select View-Toolbar again, deselect the previous toolbar - and the dialog closes. Select again View-Toolbar, select another toolbar, and the dialog closes. You can now see what I mean. If the default is to keep the dialog open until we are satisfied that all the needed toolbars are selected we could save time and avoid frustration
| [[User:Pvilela|pvilela]]
|-
| remove 'Display Grid' icon from 'Standard' toolbar
| Impress
| delete 'Display Grid' icon from 'Standard' toolbar -> it is only 0.02% clicked (one of the fewest) and also available over menue
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|}

 

----

''Autors: [mailto:Christoph.Lukasiak@Sun.com?subject:OOoWiki Christoph Lukasiak] ([http://wiki.services.openoffice.org/wiki/User:Clu Clu]), [mailto:Elizabeth.Matthis@Sun.com?subject:OOoWiki Elizabeth Matthis] 30 March 2010''

User Experience/Improving OOo Default Settings

2010-04-08T19:03:48Z

Andreasma: /* Renaissance Subproject to Achieve Better Default Settings */

{{User Experience}}

== Renaissance Subproject to Achieve Better Default Settings ==

''' '''

'''Executive summary:''' Please locate your favorite low hanging fruits by _'''end of April'''_ to improve default settings in Impress (or all apps for later, but the lmpress focus is till end of April)

 

"Better Defaults", as this effort is called for short, aims to collect suggestions for better default settings in OOo. First in Impress (in accordance with the present focus of project Renaissance) and later in the other OOo applications. This is a subproject of [http://wiki.services.openoffice.org/wiki/Renaissance Project Renaissance], so it is listed on the [http://wiki.services.openoffice.org/wiki/Renaissance:Impress#Current_Work "Current Work" wiki page] .

 

What does "better defaults" mean? Well, I KNOW there are default settings that you change first thing when you install a new version of OOo. So please share what they are and why the change(s) make(s) your life much easier. 

For example, two issues Frank found are:

Make objects same size {{bug|54281}}

Text area selection is not very accurate and covers other objects. {{bug|96548}}

One default setting changed recently was {{bug|2446}} Boy did that feel good! Let's find more of those.

 

'''Low Hanging Fruit Clause'''

No new features. The developer should only have to flip a switch on something that is already alive and kicking in the office suite, but just not set as the default. We want results, so the low hanging fruits are the ones we want to grab.

 '''How to Get Started'''

Find existing default setting issues or write new RFEs in IssueTracker (use "default" in the title and keyword) and add them to list in the table on this wiki page. Or, if RFE writing is not your kind of thing, just write your desires to achieve default utopia ;-) in the table below. Be sure to make it clear where the feature is located (write down where to click to get there) and why it is better to set the default the way you want it as compared to the old setting. 

If you have a complex issue or several defaults in the same area, it would be best if you create an individual wiki page (put link to it in the table below) for all the related defaults like Chris did (see [http://wiki.services.openoffice.org/wiki/GoodDefaults_GridHandling Grid Handling].) Each individual default setting being suggested can then be discussed on the respective wiki pages, just like the discussion in the table at the bottom of the Grind Handling wiki page. That information will serve as the basis for decision making when it comes to evaluation time, because the iTeam will have the discussion and details all in one place (wiki page) and not jumbled all over the mailing lists.

 '''Time Frame'''

Please get your 2cents in by the END of APRIL (for Impress). Then the iTeam can evaluate the suggestions and decide what to implement with the resources they have. The other application will follow within the scop of the [http://wiki.services.openoffice.org/wiki/Renaissance Renaissance project]. 

'''List of Better Default Setting Suggestions'''

{| width="100%" class="prettytable"
|-
! scope="col" | Idea 
! scope="col" | Application 
! scope="col" | Description 
! scope="col" | Name 
|-
| Rotation Mode, Guides when Moving on
| Impress
| 'Rotation Mode after Clicking Object' & 'Guides When Moving' are two feature options which are switched off by default => they should be switched on by default (more info: [http://wiki.services.openoffice.org/wiki/GoodDefaults_GridHandling Grid Handling]).
| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Change Handle Size
| Draw/Impress
| The current handle size was defined years ago - with displays offering less density than today. I propose to change the default handle size to "large". This option can be found in the toolbar "Options" (more info: [http://wiki.services.openoffice.org/wiki/GoodDefaults_GridHandling Grid Handling]).
| [[User:ChristophNoack|ChristophNoack]] 
|-
| bullet point lists
| Impress
| Bad standard defaults of bullet point lists. If one creates a text frame in Impress and clicks on the button "numbering and bullet points" (Nummerierung und Aufzählungszeichen), the newly created bullet point list has terrible standard defaults:
*(1) Almost no space between the bullet point and the text.
*(2) No ident for the second line of text under a bullet point. The second line appears left-justified directly under the bullet point. Instead, there should be a ident of the second line. It should begin exactly there where the first letter in the first line starts.

| [[User:Gerald|Gerald]]
|-
| default colour of drawing objects
| Draw/Impress
| {{issue|93507}}
| [[User:Gerald|Gerald]]
|-
| 'Right page' should be next style to 'Left page'
| Writer
| {{Bug|15498}}
| Name
|-
| Ugly style sheets for headings in Writer
| Writer
| I used Writer for several articles, publications, flyers and in all of them the standard headings look ugly and outdated. Any designer would not choose these style sheets for Heading 1-10. Furthermore, in this regard the competition has made large steps forward during the last release cycles.
| [[User:Gerald|Gerald]]
|-
| 'Right page' should be next style to 'Left page'
| Writer
| {{Bug|15498}}
| Name
|-
| Make manual page break in Writer better visiable
| Writer
| for example use 'light blue' and a thicker line. {{bug|33518}} and duplicates {{bug|65150}}, {{bug|82353}}, {{bug|96963}}, {{bug|22646}}
| Name
|-
| Default line too thick
| Chart
| especially XY-Charts need hairline lines.{{bug|98803}}
| Name
|-
| Idea
| Draw
| Include toolboxes circles, rectangles, text instead of single symbol in drawing toolbar. Reasoning: (1) The 'circles and ovals' and the 'text' toolbox is not accessible via View - Toolbars in Draw. So currently the only way to access arcs and legends is to customize the drawing toolbar. (2) Draw is used for technical constructions and there those objects are often used, in contrast to Writer or Impress, where drawing objects are used for illustrations in most cases. (3) Using the toolboxes needs no more space than single objects and give you a quick access too, because the last used object remains above for single click.
| [[User:Regina|Regina]]
|-
| Add Math formula icon to standard bar
| All
| Math objects are often used in technical documents. You need the way Insert - Object - Formula to insert one. That is too long. For example consider writing a math text for school, which has about twenty formulas per page usually.
| [[User:Regina|Regina]]
|-
| Distance in numbering styles larger
| Writer
| Make the distance from number to text in numbering styles larger, so that 10. text is still in line.
| [[User:Regina|Regina]]
|-
| Add a gap in table of contents
| Writer
| Add a gap (tab or space) between number and text in table of contents in Writer. The picture shows the ugly default settings. Notice the missing space between number and heading text. [[Image:UglyDefaultSpaceInTOC.png]]
| [[User:Regina|Regina]]
|-
| Use parallel perspective for 3D-scene
| Draw
| 3D-scenes in Draw are to illustrate constructions. Often several 3D-objects are combined in one scene. Working with several objects is faulty if ''perspective'' is on. So the first step when working with 3D-objects is to switch to parallel projection. It is "faulty" because it is unhandy to arrange or rotate objects inside a scene when in central perspective and because of {{bug|67847}}.
| [[User:Regina|Regina]]
|-
| Set margins in style of Math formula objects to 0cm
| Writer
| Set margins in style of Math formula objects in Writer to 0cm. {{bug|22136}}
| [[User:Regina|Regina]]
|-
| Add a spacing below for tables
| Writer
| Add a spacing below for tables in Writer. In normal text flow the style ''text body'' is used, which gives good distance between two paragraphs. It has a spacing above of 0cm and a spacing below of 0.21cm. But after a table the text nearly touches the border of the table, because the table has spacing 0cm. And if you do not use borders the spacing is to small too, because the style ''Table contents'' has below spacing 0cm too.
| [[User:Regina|Regina]]
|-
| Uncheck transparency warning
| All
| Uncheck transparency warning in Tools > Options. Modern PCs are fast enough to calculate transparency. So most oft the users no longer need this warning.
| [[User:Regina|Regina]]
|-
| change default color in form wizard
| Database
| the default background color of an default form document, created by the form wizard, is anything like orang -> this is a bad default and looks unprofessional => change it in anything common like 'light gray'
| [http://wiki.services.openoffice.org/wiki/User:Msc MSC]
|-
| switch off impress wizard
| Impress
| looks old fashioned, is redundant and annoying
| [http://wiki.services.openoffice.org/wiki/User:Wg WG]
|-
| Default Clipboard Format for vector graphics
| All except Draw
| If someone paste a vector graphic into a document, he normally doesn't intend to edit it there, but most probably he needs to resize it. Unfortunately scaling of embedded Draw graphics doesn't work, because text will not scaled proper. Until this work, the user must use Paste Special->As GDI-Metafile. I think GDI-Metafile should be the default here.
| Jörg
|-
| Changing default font
| Impress & Draw
| {{bug|70585}} It should be possible to change the overall default font for text (not the GUI)
in Impress permanently, using one centralized setting, for example Options -> Openoffice.org -> fonts -> Change default font or somewhere similar. This is especially a problem when working with asian languages. I know you can work around the problem using templates, but it is neither quick, nor is it likely to appear obvious to the average user.

| [http://wiki.services.openoffice.org/wiki/User:Clu Clu]
|-
| Change default pen color from neon green
| Impress
| {{bug|47990}} As described in BUG 10922 the neon green color of the pen used to draw on a
presentation is very difficult to see for students in a classroom, and the color is hard coded into OOo. I would like to see the default changed to perhaps black or red, as they are much easier colors to see. BUG 10922 is still a very good idea, but I filed this report to request a simple change of the default color, which should be much easier than what BUG 10922 is requesting. A slightly more ambitious, but still not difficult, would be to read the color value from a file or some such, instead of hard coding it in the OOo source. p.s. available after .. menue: slide show / slide show settings & check 'mouse pointer as pen' & starting a presentation 
Please integrate the patch for the pen, that's already available in the go-oo-build, into vanilla-ooo. This patch allows to change the configuration of the pen (color, line width etc.). It should be posible to change the configuration of the cursor (from arrow to pen) during the presentation mode (via context menu).

| [http://wiki.services.openoffice.org/wiki/User:Clu Clu] andreasma
|-
| Don't emulate MS Office's annoying "clippy"
| All
| Tools | Options | OpenOffice | General and then Turn off Help Agent and Turn on Extended Tips
| Safway
|-
| Please set all checkboxes in Change Tools --> Options --> Load/Save --> Microsoft Office by default
| All
| It is very annoying that these checkboxes are not checked by default because users which own Microsoft Office and open a document with an Excel OLE-object see a document in a different way than a user who does not have Microsoft Office installed. This is because (by default) an installed Excel is used to render the xls-diagrams while (when Excel is not installed) OpenOffice.org is used to render it. When a user sends such a document to a different user it seems as if OpenOffice.org does not display the document in the same way as on the other computer. But the problem is in the OLE-object. When the boxes are checked it would be a better default.
| parity
|-
| Tab Stops with reasonable settings
| All
| Tools > Options > Writer or Writer/Web or Calc or Impress or Draw > General > Settings > Tab stops = 0.50 instead of 0.49
| Safway
|-
| Grid Settings much more manageable and understandable
| All
| Tools > Options > Writer or Writer/Web or Calc or Impress or Draw > Grid
Snap to Grid should be off. Visible Grid should be off.
Resolution > Horizontal = 0.10 instead of 0.39.
Resolution > Vertical = 0.10 instead of 0.39.
Synchronize axes should be on.
| Safway
|-
| Table keyboard handling consistent
| Calc
| Tools > Options > Calc > Table > Keyboard handling > Insert cell > Column = 0.20 like the others instead of 0.98.
| Safway
|-
| Anchor context sensitive toolbars by default
| All
| Context sensitive toolbars (like table, image toolbars) is a great feature
when you get used to it, but new users just see a toolbar popping in front of
their work. I always dock those toolbars to the bottom edge of the window.
I think this could be a good default for new (and old) users.
| RGB
|-
| Change "Show as tip" for word completion
| Writer
| The word completion is a useful feature, but the way it is shown by default is quite "disturbing": if a
long suggestion pops when you are near the page edge the word you are writing will jump to next line.
"Show as tooltip is a better alternative, IMO.
The option is on Tools -> AutoCorrect Options -> Word Completion tab
| RGB
|-
| <Idea>
| <Application>
| <Description>
| <Name>
 

|}

DE/CeBIT2010

2010-02-18T18:42:52Z

Andreasma: /* Personalplan */

{{DISPLAYTITLE:OpenOffice.org-Gemeinschaftsstand auf der CeBIT 2010}}

= Einführung =

Auf dieser Seite wird der OpenOffice.org-Gemeinschaftsstand auf der CeBIT 2010 koordiniert. Ansprechpartner für die Organisation ist [mailto:thomaskrumbein@openoffice.org Thomas Krumbein].

Die CeBIT findet statt vom 2. bis 6. März 2010 in Hannover. Der Aufbau ist am 1. März. Organisiert wird der Gemeinschaftsstand wie bereits die Jahre zuvor vom [http://www.ooodev.org gemeinnützigen Verein OpenOffice.org Deutschland e.V.] Ihr findet uns in '''Halle 2, Stand D38-137'''.

= Personalplan''' ''' =

{| align="center" width="100%" class="prettytable"
|-
| '''Name''' (Ticket)
| '''Montag, 1. März''' '''(Aufbautag)'''
| '''Dienstag, 2. März'''
| '''Mittwoch, 3. März'''
| '''Donnerstag, 4. März'''
| '''Freitag, 5. März'''
| '''Samstag, 6. März''' '''(Abbau am Abend)'''
|-
| [mailto:floeff@openoffice.org Effenberger, Florian] (Presseticket)
|
|
|
|
|
|
|-
| [mailto:thomaskrumbein@openoffice.org Krumbein, Thomas] (Presseticket)
| X
| X
| X
| X
| X
| X
|-
| [mailto:jrahemipour@openoffice.org Rahemipour, Jacqueline]
|
|
|
|
|
|
|-
| [mailto:simonaw@openoffice.org Wilper, Simon]
|
|
|
|
| X
| X
|-
| [mailto:andreschnabel@openoffice.org Schnabel,André]
|
|
|
|
| (evtl.)
| X
|-
| [mailto:uwealtmann@openoffice.org Altmann, Uwe]
| (bei Bedarf)
| X
| X
| X (nur vorm.)
|
|
|-
| [mailto:lothar.becker@riess.de Becker, Lothar]
|
|
|
|
| X
| X (nur vorm.)
|-
| [mailto:christoph@dogmatux.com Noack, Christoph]
|
|
|
|
| X
| X (ggf. nur vorm.)
|-
| Wolfgang Uhlig
|
|
|
|
| X
| X (Vormittag)
|-
| Andreas Mantke
|
|
|
| X (im Laufe des Vormittags)
| X
| X
|-
|
|
|
|
|
|
|
|-
|
|
|
|
|
|
|
|-
|
|
|
|
|
|
|
|-
|
|
|
|
|
|
|
|-
|
|
|
|
|
|
|
|}

[[Category:De.openoffice.org]]

Conferences/FOSDEM/2010

2010-01-16T11:32:41Z

Andreasma: /* Team */

{{DISPLAYTITLE:FOSDEM 2010}}

[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium

This page will collect ideas, todos and everything else that is related to the OpenOffice.org project activities @FOSDEM 2010. Planned activities are so far a stand to represent the OpenOffice.org project and to be the central info point for all OpenOffice.org related questions. And we want again organize a DevRoom to inform about our ongoing development work and projects. For more details please check the sections below.

==Communication Channel==
For all FOSDEM relevant communication the mailing list [http://marketing.openoffice.org/servlets/SummarizeList?listName=fosdem fosdem@marketing.openffcie.org] is used. If you are interested in any activities around FOSDEM please [http://marketing.openoffice.org/servlets/ProjectMailingListList subscribe] yourself. For special message or requests (like CFP) we will use some further mailing lists as well.

==DevRoom==
OpenOffice.org is accepted and we have a DevRoom for 1 day, on Saturday 6th February from 13:00 to 19:00. We will share our DevRoom with the ODF group which have no additional own DevRoom.

===Call for Papers===
The schedule for our DevRoom is organized by us and we can use the time as we want. We should plan with 45, 90 or 120 minutes sessions.

Some things that should be taken into account
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
** the speaker's real name,
** a short overview of her bio in a couple of lines,
** optionally also a longer bio,
** optionally a picture (please send it to Juergen as 128x128 PNG),
** optionally links to her website, blog, ...

We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.

====Proposals====
Papers, talks, workshop proposals or something else that fits into the DevRoom should be proposed on the following wiki page [[Conferences/FOSDEM/2010/CFP|CFP]] until Friday 12/18/2009.

===Schedule===

Changes are still possible

{| border=1
|+ DevRoom Overview
|- bgcolor=#CDDBF6
! Time !! Title !! Session type !! Slides !!Speaker
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''OpenOffice.org'''
|-
| 13:00 - 13:45 || [[Conferences/FOSDEM/2010/CFP#Tips_and_Tricks_for_Extension_Developer|Welcome + Tips and Tricks for Extension Developer]] || talk || ? || [[User:Jsc|Juergen Schmidt]]
|-
| 13:45 - 14:30 || [[Conferences/FOSDEM/2010/CFP#New_docking_windows_for_a_better_UI_.26_extension_integration|New docking windows for a better UI & extension integration]] || talk || ? || Carsten Driesner
|-
| 14:30 - 15:15 || [[Conferences/FOSDEM/2010/CFP#Improving_the_OpenOffice.org_Build_System|Improving the OpenOffice.org Build System]] || talk || ? || Bjoern Michaelsen
|-
| 15:15 - 16:00 || [[Conferences/FOSDEM/2010/CFP#Just_Testing|Just Testing]] || talk || ? || Stephan Bergmann
|-
| 16:00 - 16:45 || [[Conferences/FOSDEM/2010/CFP#Show_me_YOUR_code|Show me YOUR code]] || workshop || ? || [[User:ErAck|Eike Rathke]]
|-
| 16:45 - 17:30 || [[Conferences/FOSDEM/2010/CFP#Hidden_Pearls_-_What.27s_There_to_ReUse_for_Other_Projects|Hidden Pearls - What's There to ReUse for Other Projects]] || talk || ? || Thorsten Behrens
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''ODF'''
|-
| 17:30 - 18:00 || [[Conferences/FOSDEM/2010/CFP#ODF_Tools_and_Resources|ODF Tools and Resources]] || talk || ? || [http://be.linkedin.com/in/barthanssens Bart Hanssens]
|-
| 18:00 - 18:30 || [[Conferences/FOSDEM/2010/CFP#ODF_on_the_server_-_ODFDOM_architecture|ODF on the server - ODFDOM architecture]] || talk || ? || Svante Schubert
|-
| 18:30 - 19:00 || [[Conferences/FOSDEM/2010/CFP#lpOD_.E2.80.93_languages_.26_platforms_OpenDocument|lpOD – languages & platforms OpenDocument]] || talk || ? || Luis Belmar Letelier
|}

== Stand/Booth ==

Our stand will be most probably in building AW

{| border="1"
|+ Stand Overview
|- bgcolor="#cddbf6"
! Time
! Stand staff
|- bgcolor="#7c9acd"
| align="center" colspan="2" | '''Saturday 6th'''
|-
| 10:00 - 12:00
| floeff, jsc, lmo, sb, sophi, b_michaelsen 
|-
| 12:00 - 14:00
| floeff, lmo, er, sophi, thb 
|-
| 14:00 - 16:00
| floeff, cno, lmo, sophi, cd 
|-
| 16:00 - 18:00
| floeff, jsc, cno, lmo, sophi, b_michaelsen 
|- bgcolor="#7c9acd"
| align="center" colspan="4" | '''Sunday 7th'''
|-
| 10:00 - 12:00
| probably floeff, jsc, sophi, b_michaelsen, thb 
|-
| 12:00 - 14:00
| jsc, cno, sb, sophi, cd
|-
| 14:00 - 16:00
| cno, er, sophi
|-
| 16:00 - 17:00
| cno, sophi 
|}

=== Stand material ===
* sophi: I'll bring a coffee machine, tea and coffee, water, biscuits and cakes. Plugs, scissors, etc... A blue table coth. What else?
* jsc: i will bring 3 posters, stickers and t-shirts. All with the same design!

{| border=1 cellpadding="5" cellspacing="0"
|-
| [[Image:fosdem_design.png|thumb|left|150px|FOSDEM design]] || valign="top" | [[File:fosdem_design.pdf]] || valign="top" | design background: - the squirl stands for a moving, rotating, active, vital community - the cubes stand for the many, many individuals - and the different colors stand for different countries, continents.
|}

==Saturday Evening OOo Community Event==
...details will coming soon

== Team ==

...details will coming soon

{| border="1"
|- bgcolor="#cddbf6"
! Name
! Stay
! Function
! Funding request
|-
| Juergen Schmidt
| Friday - Sunday
| Stand/DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Florian Effenberger 
| Friday-Sunday
| Stand/Marketing
| yes (approx. 250-300 EUR) 
|-
| Cor Nouws [cno] 
| both days
| Stand/Marketing
| 70 Euro Hotel, 90 Euro train
|-
| Andrea Pescetti
| one day only (unsure)
|  ?
| no
|-
| Jacqueline Rahemipour
| both days
|
| 120 Eur hotel, 90 Eur train
|-
| Eike Rathke
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Thorsten Behrens
| both days
| Stand / DevRoom
| 124 Euro hotel, 140 Euro airfare
|-
| Bjoern Michaelsen
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Stephan Bergmann
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Carsten Driesner
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Leo Moons
| Saturday
| Stand
| no
|-
| Sophie Gautier
| both days
| Stand
| no
|-
|}

==Hotel Recommendation==
Brussels is a big city and especially during work days crowded with EU people. Here you can find three hotels that are all in the city directly and a perfect start point for the conference as well as night life activities. The prices are all for a single room.

* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&Sleep 59 Euro
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&Sleep 65 Euro
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&Sleep 65 Euro

Feel free to insert some more recommendations.

[[Category:Conferences]]
[[Category:FOSDEM]]

Conferences/FOSDEM/2010

2010-01-16T11:31:58Z

Andreasma: /* Stand/Booth */

{{DISPLAYTITLE:FOSDEM 2010}}

[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium

This page will collect ideas, todos and everything else that is related to the OpenOffice.org project activities @FOSDEM 2010. Planned activities are so far a stand to represent the OpenOffice.org project and to be the central info point for all OpenOffice.org related questions. And we want again organize a DevRoom to inform about our ongoing development work and projects. For more details please check the sections below.

==Communication Channel==
For all FOSDEM relevant communication the mailing list [http://marketing.openoffice.org/servlets/SummarizeList?listName=fosdem fosdem@marketing.openffcie.org] is used. If you are interested in any activities around FOSDEM please [http://marketing.openoffice.org/servlets/ProjectMailingListList subscribe] yourself. For special message or requests (like CFP) we will use some further mailing lists as well.

==DevRoom==
OpenOffice.org is accepted and we have a DevRoom for 1 day, on Saturday 6th February from 13:00 to 19:00. We will share our DevRoom with the ODF group which have no additional own DevRoom.

===Call for Papers===
The schedule for our DevRoom is organized by us and we can use the time as we want. We should plan with 45, 90 or 120 minutes sessions.

Some things that should be taken into account
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
** the speaker's real name,
** a short overview of her bio in a couple of lines,
** optionally also a longer bio,
** optionally a picture (please send it to Juergen as 128x128 PNG),
** optionally links to her website, blog, ...

We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.

====Proposals====
Papers, talks, workshop proposals or something else that fits into the DevRoom should be proposed on the following wiki page [[Conferences/FOSDEM/2010/CFP|CFP]] until Friday 12/18/2009.

===Schedule===

Changes are still possible

{| border=1
|+ DevRoom Overview
|- bgcolor=#CDDBF6
! Time !! Title !! Session type !! Slides !!Speaker
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''OpenOffice.org'''
|-
| 13:00 - 13:45 || [[Conferences/FOSDEM/2010/CFP#Tips_and_Tricks_for_Extension_Developer|Welcome + Tips and Tricks for Extension Developer]] || talk || ? || [[User:Jsc|Juergen Schmidt]]
|-
| 13:45 - 14:30 || [[Conferences/FOSDEM/2010/CFP#New_docking_windows_for_a_better_UI_.26_extension_integration|New docking windows for a better UI & extension integration]] || talk || ? || Carsten Driesner
|-
| 14:30 - 15:15 || [[Conferences/FOSDEM/2010/CFP#Improving_the_OpenOffice.org_Build_System|Improving the OpenOffice.org Build System]] || talk || ? || Bjoern Michaelsen
|-
| 15:15 - 16:00 || [[Conferences/FOSDEM/2010/CFP#Just_Testing|Just Testing]] || talk || ? || Stephan Bergmann
|-
| 16:00 - 16:45 || [[Conferences/FOSDEM/2010/CFP#Show_me_YOUR_code|Show me YOUR code]] || workshop || ? || [[User:ErAck|Eike Rathke]]
|-
| 16:45 - 17:30 || [[Conferences/FOSDEM/2010/CFP#Hidden_Pearls_-_What.27s_There_to_ReUse_for_Other_Projects|Hidden Pearls - What's There to ReUse for Other Projects]] || talk || ? || Thorsten Behrens
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''ODF'''
|-
| 17:30 - 18:00 || [[Conferences/FOSDEM/2010/CFP#ODF_Tools_and_Resources|ODF Tools and Resources]] || talk || ? || [http://be.linkedin.com/in/barthanssens Bart Hanssens]
|-
| 18:00 - 18:30 || [[Conferences/FOSDEM/2010/CFP#ODF_on_the_server_-_ODFDOM_architecture|ODF on the server - ODFDOM architecture]] || talk || ? || Svante Schubert
|-
| 18:30 - 19:00 || [[Conferences/FOSDEM/2010/CFP#lpOD_.E2.80.93_languages_.26_platforms_OpenDocument|lpOD – languages & platforms OpenDocument]] || talk || ? || Luis Belmar Letelier
|}

== Stand/Booth ==

Our stand will be most probably in building AW

{| border="1"
|+ Stand Overview
|- bgcolor="#cddbf6"
! Time
! Stand staff
|- bgcolor="#7c9acd"
| align="center" colspan="2" | '''Saturday 6th'''
|-
| 10:00 - 12:00
| floeff, jsc, lmo, sb, sophi, b_michaelsen 
|-
| 12:00 - 14:00
| floeff, lmo, er, sophi, thb 
|-
| 14:00 - 16:00
| floeff, cno, lmo, sophi, cd 
|-
| 16:00 - 18:00
| floeff, jsc, cno, lmo, sophi, b_michaelsen 
|- bgcolor="#7c9acd"
| align="center" colspan="4" | '''Sunday 7th'''
|-
| 10:00 - 12:00
| probably floeff, jsc, sophi, b_michaelsen, thb 
|-
| 12:00 - 14:00
| jsc, cno, sb, sophi, cd
|-
| 14:00 - 16:00
| cno, er, sophi
|-
| 16:00 - 17:00
| cno, sophi 
|}

=== Stand material ===
* sophi: I'll bring a coffee machine, tea and coffee, water, biscuits and cakes. Plugs, scissors, etc... A blue table coth. What else?
* jsc: i will bring 3 posters, stickers and t-shirts. All with the same design!

{| border=1 cellpadding="5" cellspacing="0"
|-
| [[Image:fosdem_design.png|thumb|left|150px|FOSDEM design]] || valign="top" | [[File:fosdem_design.pdf]] || valign="top" | design background: - the squirl stands for a moving, rotating, active, vital community - the cubes stand for the many, many individuals - and the different colors stand for different countries, continents.
|}

==Saturday Evening OOo Community Event==
...details will coming soon

== Team ==

...details will coming soon

{| border="1"
|- bgcolor="#cddbf6"
! Name
! Stay
! Function
! Funding request
|-
| Juergen Schmidt
| Friday - Sunday
| Stand/DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Florian Effenberger 
| Friday-Sunday
| Stand/Marketing
| yes (approx. 250-300 EUR) 
|-
| Cor Nouws [cno] 
| both days
| Stand/Marketing
| 70 Euro Hotel, 90 Euro train
|-
| Andrea Pescetti
| one day only (unsure)
|  ?
| no
|-
| Jacqueline Rahemipour
| both days
|
| 120 Eur hotel, 90 Eur train
|-
| Eike Rathke
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Thorsten Behrens
| both days
| Stand / DevRoom
| 124 Euro hotel, 140 Euro airfare
|-
| Bjoern Michaelsen
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Stephan Bergmann
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Carsten Driesner
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Leo Moons
| Saturday
| Stand
| no
|-
| Andreas Mantke
| Saturday
| Stand
| yes (approx. 60 EUR fuel)
|-
| Sophie Gautier
| both days
| Stand
| no
|-
|}

==Hotel Recommendation==
Brussels is a big city and especially during work days crowded with EU people. Here you can find three hotels that are all in the city directly and a perfect start point for the conference as well as night life activities. The prices are all for a single room.

* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&Sleep 59 Euro
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&Sleep 65 Euro
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&Sleep 65 Euro

Feel free to insert some more recommendations.

[[Category:Conferences]]
[[Category:FOSDEM]]

Conferences/FOSDEM/2010

2010-01-13T20:59:53Z

Andreasma: /* Stand/Booth */

{{DISPLAYTITLE:FOSDEM 2010}}

[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium

This page will collect ideas, todos and everything else that is related to the OpenOffice.org project activities @FOSDEM 2010. Planned activities are so far a stand to represent the OpenOffice.org project and to be the central info point for all OpenOffice.org related questions. And we want again organize a DevRoom to inform about our ongoing development work and projects. For more details please check the sections below.

==Communication Channel==
For all FOSDEM relevant communication the mailing list [http://marketing.openoffice.org/servlets/SummarizeList?listName=fosdem fosdem@marketing.openffcie.org] is used. If you are interested in any activities around FOSDEM please [http://marketing.openoffice.org/servlets/ProjectMailingListList subscribe] yourself. For special message or requests (like CFP) we will use some further mailing lists as well.

==DevRoom==
OpenOffice.org is accepted and we have a DevRoom for 1 day, on Saturday 6th February from 13:00 to 19:00. We will share our DevRoom with the ODF group which have no additional own DevRoom.

===Call for Papers===
The schedule for our DevRoom is organized by us and we can use the time as we want. We should plan with 45, 90 or 120 minutes sessions.

Some things that should be taken into account
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
** the speaker's real name,
** a short overview of her bio in a couple of lines,
** optionally also a longer bio,
** optionally a picture (please send it to Juergen as 128x128 PNG),
** optionally links to her website, blog, ...

We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.

====Proposals====
Papers, talks, workshop proposals or something else that fits into the DevRoom should be proposed on the following wiki page [[Conferences/FOSDEM/2010/CFP|CFP]] until Friday 12/18/2009.

===Schedule===

Changes are still possible

{| border=1
|+ DevRoom Overview
|- bgcolor=#CDDBF6
! Time !! Title !! Session type !! Slides !!Speaker
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''OpenOffice.org'''
|-
| 13:00 - 13:45 || [[Conferences/FOSDEM/2010/CFP#Tips_and_Tricks_for_Extension_Developer|Welcome + Tips and Tricks for Extension Developer]] || talk || ? || [[User:Jsc|Juergen Schmidt]]
|-
| 13:45 - 14:30 || [[Conferences/FOSDEM/2010/CFP#New_docking_windows_for_a_better_UI_.26_extension_integration|New docking windows for a better UI & extension integration]] || talk || ? || Carsten Driesner
|-
| 14:30 - 15:15 || [[Conferences/FOSDEM/2010/CFP#Improving_the_OpenOffice.org_Build_System|Improving the OpenOffice.org Build System]] || talk || ? || Bjoern Michaelsen
|-
| 15:15 - 16:00 || [[Conferences/FOSDEM/2010/CFP#Just_Testing|Just Testing]] || talk || ? || Stephan Bergmann
|-
| 16:00 - 16:45 || [[Conferences/FOSDEM/2010/CFP#Show_me_YOUR_code|Show me YOUR code]] || workshop || ? || [[User:ErAck|Eike Rathke]]
|-
| 16:45 - 17:30 || [[Conferences/FOSDEM/2010/CFP#Hidden_Pearls_-_What.27s_There_to_ReUse_for_Other_Projects|Hidden Pearls - What's There to ReUse for Other Projects]] || talk || ? || Thorsten Behrens
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''ODF'''
|-
| 17:30 - 18:00 || [[Conferences/FOSDEM/2010/CFP#ODF_Tools_and_Resources|ODF Tools and Resources]] || talk || ? || [http://be.linkedin.com/in/barthanssens Bart Hanssens]
|-
| 18:00 - 18:30 || [[Conferences/FOSDEM/2010/CFP#ODF_on_the_server_-_ODFDOM_architecture|ODF on the server - ODFDOM architecture]] || talk || ? || Svante Schubert
|-
| 18:30 - 19:00 || [[Conferences/FOSDEM/2010/CFP#lpOD_.E2.80.93_languages_.26_platforms_OpenDocument|lpOD – languages & platforms OpenDocument]] || talk || ? || ?
|}

== Stand/Booth ==

Our stand will be most probably in building AW

{| border="1"
|+ Stand Overview
|- bgcolor="#cddbf6"
! Time
! Stand staff
|- bgcolor="#7c9acd"
| align="center" colspan="2" | '''Saturday 6th'''
|-
| 10:00 - 12:00
| floeff, jsc, lmo, sb, sophi 
|-
| 12:00 - 14:00
| floeff, lmo, er, sophi, andreasma 
|-
| 14:00 - 16:00
| floeff, cno, lmo, sophi, andreasma 
|-
| 16:00 - 18:00
| floeff, jsc, cno, lmo, sophi, andreasma 
|- bgcolor="#7c9acd"
| align="center" colspan="4" | '''Sunday 7th'''
|-
| 10:00 - 12:00
| probably floeff, jsc, sophi 
|-
| 12:00 - 14:00
| jsc, cno, sb, sophi
|-
| 14:00 - 16:00
| cno, er, sophi
|-
| 16:00 - 17:00
| cno, sophi 
|}

sophi: I'll bring a coffee machine, tea and coffee, water, biscuits and cakes. Plugs, scissors, etc... A blue table coth. What else?

==Saturday Evening OOo Community Event==
...details will coming soon

== Team ==

...details will coming soon

{| border="1"
|- bgcolor="#cddbf6"
! Name
! Stay
! Function
! Funding request
|-
| Juergen Schmidt
| Friday - Sunday
| Stand/DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Florian Effenberger 
| Friday-Sunday
| Stand/Marketing
| yes (approx. 250-300 EUR) 
|-
| Cor Nouws [cno] 
| both days
| Stand/Marketing
| 70 Euro Hotel, 90 Euro train
|-
| Andrea Pescetti
| one day only (unsure)
|  ?
| no
|-
| Jacqueline Rahemipour
| both days
|
| 120 Eur hotel, 90 Eur train
|-
| Eike Rathke
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Thorsten Behrens
| both days
| Stand / DevRoom
| 124 Euro hotel, 140 Euro airfare
|-
| Bjoern Michaelsen
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Stephan Bergmann
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Carsten Driesner
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Leo Moons
| Saturday
| Stand
| no
|-
| Andreas Mantke
| Saturday
| Stand
| yes (approx. 60 EUR fuel)
|-
| Sophie Gautier
| both days
| Stand
| no
|-
|}

==Hotel Recommendation==
Brussels is a big city and especially during work days crowded with EU people. Here you can find three hotels that are all in the city directly and a perfect start point for the conference as well as night life activities. The prices are all for a single room.

* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&Sleep 59 Euro
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&Sleep 65 Euro
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&Sleep 65 Euro

Feel free to insert some more recommendations.

[[Category:Conferences]]
[[Category:FOSDEM]]

Conferences/FOSDEM/2010

2010-01-08T17:46:31Z

Andreasma: /* Team */

{{DISPLAYTITLE:FOSDEM 2010}}

[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium

This page will collect ideas, todos and everything else that is related to the OpenOffice.org project activities @FOSDEM 2010. Planned activities are so far a stand to represent the OpenOffice.org project and to be the central info point for all OpenOffice.org related questions. And we want again organize a DevRoom to inform about our ongoing development work and projects. For more details please check the sections below.

==Communication Channel==
For all FOSDEM relevant communication the mailing list [http://marketing.openoffice.org/servlets/SummarizeList?listName=fosdem fosdem@marketing.openffcie.org] is used. If you are interested in any activities around FOSDEM please [http://marketing.openoffice.org/servlets/ProjectMailingListList subscribe] yourself. For special message or requests (like CFP) we will use some further mailing lists as well.

==DevRoom==
OpenOffice.org is accepted and we have a DevRoom for 1 day, on Saturday 6th February from 13:00 to 19:00. We will share our DevRoom with the ODF group which have no additional own DevRoom.

===Call for Papers===
The schedule for our DevRoom is organized by us and we can use the time as we want. We should plan with 45, 90 or 120 minutes sessions.

Some things that should be taken into account
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
** the speaker's real name,
** a short overview of her bio in a couple of lines,
** optionally also a longer bio,
** optionally a picture (please send it to Juergen as 128x128 PNG),
** optionally links to her website, blog, ...

We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.

====Proposals====
Papers, talks, workshop proposals or something else that fits into the DevRoom should be proposed on the following wiki page [[Conferences/FOSDEM/2010/CFP|CFP]] until Friday 12/18/2009.

===Schedule===

Changes are still possible

{| border=1
|+ DevRoom Overview
|- bgcolor=#CDDBF6
! Time !! Title !! Session type !! Slides !!Speaker
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''OpenOffice.org'''
|-
| 13:00 - 13:45 || Welcome + Tips and Tricks for Extension Developer || talk || ? || [[User:Jsc|Juergen Schmidt]]
|-
| 13:45 - 14:30 || New docking windows for a better UI & extension integration || talk || ? || Carsten Driesner
|-
| 14:30 - 15:15 || Improving the OpenOffice.org Build System || talk || ? || Bjoern Michaelsen
|-
| 15:15 - 16:00 || Just Testing || talk || ? || Stephan Bergmann
|-
| 16:00 - 16:45 || Show me YOUR code || workshop || ? || [[User:ErAck|Eike Rathke]]
|-
| 16:45 - 17:30 || Hidden Pearls - What's There to ReUse for Other Projects || talk || ? || Thorsten Behrens
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''ODF'''
|-
| 17:30 - 18:00 || ODF Tools and Resources || talk || ? || [http://be.linkedin.com/in/barthanssens Bart Hanssens]
|-
| 18:00 - 18:30 || ODF on the server - ODFDOM architecture || talk || ? || Svante Schubert
|-
| 18:30 - 19:00 || lpOD – languages & platforms OpenDocument || talk || ? || ?
|}

== Stand/Booth ==

Our stand will be most probably in building AW

{| border="1"
|+ Stand Overview
|- bgcolor="#cddbf6"
! Time
! Stand staff
|- bgcolor="#7c9acd"
| align="center" colspan="2" | '''Saturday 6th'''
|-
| 10:00 - 12:00
| floeff, jsc, lmo, sb 
|-
| 12:00 - 14:00
| floeff, lmo 
|-
| 14:00 - 16:00
| floeff, cno, lmo 
|-
| 16:00 - 18:00
| floeff, jsc, cno, lmo 
|- bgcolor="#7c9acd"
| align="center" colspan="4" | '''Sunday 7th'''
|-
| 10:00 - 12:00
| probably floeff, jsc 
|-
| 12:00 - 14:00
| jsc, cno, sb
|-
| 14:00 - 16:00
| cno
|-
| 16:00 - 17:00
| cno 
|}

More info ...

==Saturday Evening OOo Community Event==
...details will coming soon

== Team ==

...details will coming soon

{| border="1"
|- bgcolor="#cddbf6"
! Name
! Stay
! Function
! Funding request
|-
| Juergen Schmidt
| Friday - Sunday
| Stand/DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Florian Effenberger 
| Friday-Sunday
| Stand/Marketing
| yes (approx. 250-300 EUR) 
|-
| Cor Nouws [cno] 
| both days
| Stand/Marketing
| 70 Euro Hotel, 90 Euro train
|-
| Andrea Pescetti
| one day only (unsure)
|  ?
| no
|-
| Jacqueline Rahemipour
| both days
|
| 120 Eur hotel, 90 Eur train
|-
| Eike Rathke
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Thorsten Behrens
| both days
| Stand / DevRoom
| 124 Euro hotel, 140 Euro airfare
|-
| Bjoern Michaelsen
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Stephan Bergmann
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Carsten Driesner
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Leo Moons
| Saturday
| Stand
| no
|-
| Andreas Mantke
| Saturday
| Stand
| yes (approx. 60 EUR fuel)
|-
|}

==Hotel Recommendation==
Brussels is a big city and especially during work days crowded with EU people. Here you can find three hotels that are all in the city directly and a perfect start point for the conference as well as night life activities. The prices are all for a single room.

* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&Sleep 59 Euro
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&Sleep 65 Euro
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&Sleep 65 Euro

Feel free to insert some more recommendations.

[[Category:Conferences]]
[[Category:FOSDEM]]

Conferences/FOSDEM/2010

2010-01-08T17:45:44Z

Andreasma: /* Team */

{{DISPLAYTITLE:FOSDEM 2010}}

[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium

This page will collect ideas, todos and everything else that is related to the OpenOffice.org project activities @FOSDEM 2010. Planned activities are so far a stand to represent the OpenOffice.org project and to be the central info point for all OpenOffice.org related questions. And we want again organize a DevRoom to inform about our ongoing development work and projects. For more details please check the sections below.

==Communication Channel==
For all FOSDEM relevant communication the mailing list [http://marketing.openoffice.org/servlets/SummarizeList?listName=fosdem fosdem@marketing.openffcie.org] is used. If you are interested in any activities around FOSDEM please [http://marketing.openoffice.org/servlets/ProjectMailingListList subscribe] yourself. For special message or requests (like CFP) we will use some further mailing lists as well.

==DevRoom==
OpenOffice.org is accepted and we have a DevRoom for 1 day, on Saturday 6th February from 13:00 to 19:00. We will share our DevRoom with the ODF group which have no additional own DevRoom.

===Call for Papers===
The schedule for our DevRoom is organized by us and we can use the time as we want. We should plan with 45, 90 or 120 minutes sessions.

Some things that should be taken into account
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
** the speaker's real name,
** a short overview of her bio in a couple of lines,
** optionally also a longer bio,
** optionally a picture (please send it to Juergen as 128x128 PNG),
** optionally links to her website, blog, ...

We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.

====Proposals====
Papers, talks, workshop proposals or something else that fits into the DevRoom should be proposed on the following wiki page [[Conferences/FOSDEM/2010/CFP|CFP]] until Friday 12/18/2009.

===Schedule===

Changes are still possible

{| border=1
|+ DevRoom Overview
|- bgcolor=#CDDBF6
! Time !! Title !! Session type !! Slides !!Speaker
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''OpenOffice.org'''
|-
| 13:00 - 13:45 || Welcome + Tips and Tricks for Extension Developer || talk || ? || [[User:Jsc|Juergen Schmidt]]
|-
| 13:45 - 14:30 || New docking windows for a better UI & extension integration || talk || ? || Carsten Driesner
|-
| 14:30 - 15:15 || Improving the OpenOffice.org Build System || talk || ? || Bjoern Michaelsen
|-
| 15:15 - 16:00 || Just Testing || talk || ? || Stephan Bergmann
|-
| 16:00 - 16:45 || Show me YOUR code || workshop || ? || [[User:ErAck|Eike Rathke]]
|-
| 16:45 - 17:30 || Hidden Pearls - What's There to ReUse for Other Projects || talk || ? || Thorsten Behrens
|- bgcolor=#7c9acd
| colspan="5" align="center" | '''ODF'''
|-
| 17:30 - 18:00 || ODF Tools and Resources || talk || ? || [http://be.linkedin.com/in/barthanssens Bart Hanssens]
|-
| 18:00 - 18:30 || ODF on the server - ODFDOM architecture || talk || ? || Svante Schubert
|-
| 18:30 - 19:00 || lpOD – languages & platforms OpenDocument || talk || ? || ?
|}

== Stand/Booth ==

Our stand will be most probably in building AW

{| border="1"
|+ Stand Overview
|- bgcolor="#cddbf6"
! Time
! Stand staff
|- bgcolor="#7c9acd"
| align="center" colspan="2" | '''Saturday 6th'''
|-
| 10:00 - 12:00
| floeff, jsc, lmo, sb 
|-
| 12:00 - 14:00
| floeff, lmo 
|-
| 14:00 - 16:00
| floeff, cno, lmo 
|-
| 16:00 - 18:00
| floeff, jsc, cno, lmo 
|- bgcolor="#7c9acd"
| align="center" colspan="4" | '''Sunday 7th'''
|-
| 10:00 - 12:00
| probably floeff, jsc 
|-
| 12:00 - 14:00
| jsc, cno, sb
|-
| 14:00 - 16:00
| cno
|-
| 16:00 - 17:00
| cno 
|}

More info ...

==Saturday Evening OOo Community Event==
...details will coming soon

== Team ==

...details will coming soon

{| border="1"
|- bgcolor="#cddbf6"
! Name
! Stay
! Function
! Funding request
|-
| Juergen Schmidt
| Friday - Sunday
| Stand/DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Florian Effenberger 
| Friday-Sunday
| Stand/Marketing
| yes (approx. 250-300 EUR) 
|-
| Cor Nouws [cno] 
| both days
| Stand/Marketing
| 70 Euro Hotel, 90 Euro train
|-
| Andrea Pescetti
| one day only (unsure)
|  ?
| no
|-
| Jacqueline Rahemipour
| both days
|
| 120 Eur hotel, 90 Eur train
|-
| Eike Rathke
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Thorsten Behrens
| both days
| Stand / DevRoom
| 124 Euro hotel, 140 Euro airfare
|-
| Bjoern Michaelsen
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Stephan Bergmann
| both days
| Stand / DevRoom
| 140 Euro hotel
|-
| Carsten Driesner
| both days
| Stand / DevRoom
| 140 Euro hotel, ~150 Euro fuel
|-
| Leo Moons
| Saturday
| Stand
| no
|-
| Andreas Mantke
| Saturday
| Stand
| yes (approx. 60 EUR)
|-
|}

==Hotel Recommendation==
Brussels is a big city and especially during work days crowded with EU people. Here you can find three hotels that are all in the city directly and a perfect start point for the conference as well as night life activities. The prices are all for a single room.

* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&Sleep 59 Euro
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&Sleep 65 Euro
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&Sleep 65 Euro

Feel free to insert some more recommendations.

[[Category:Conferences]]
[[Category:FOSDEM]]

Documentation/Dashboard/Ideastorm

2009-11-24T15:31:25Z

Andreasma: /* Questions */

[[Documentation/Dashboard/Ideastorm/Complete]]

== Infrastructure ==
Ideas for improving the documentation infrastructure. This can be new toolset proposals, reusing existing tools that are not being used effectively, wiki extensions and so on.

=== One Purpose - One Wiki ===
I think mixing Project organisation with End User documentation as actually done '''is bad'''. We (i.e. the doc project) should have "our own" wiki. And it should be clearly target group oriented and not project oriented (as the actual). This would lift quality and usability and hopefully usage (and therefore motivation for contribution). And I don't believe that administrating two separated wikis will double admin time as there will be less need/effort to harmonize the two target groups (developers vs. doc people).
: I dont think this is a good idea for the following reasons:
:* There are not just two groups of content. There is are at least the following groups: User Documentation. Advanced User Documentation (API), Internal Development Documentation, Project/Effort Progress Documentation, Marketing
:* Those are not easily separated: There are huge overlaps between:
:** User Documentation. Advanced User Documentation (API)
:** Advanced User Documentation (API), Internal Development Documentation
:** Internal Development Documentation, Project/Effort Progress Documentation
:** Project/Effort Progress Documentation, Marketing
:''Even if'' current pages could be separated in different groups (which would be a huge effort) there would be a lot of duplicate content, contradicting content and outdated content.
:Also namespacing is easy in Wikis: Everything in [[:Category:Documentation]] and subcategories is yours. The problem is that there are currently ~2400 pages that are in no category. That needs to be fixed otherwise the wiki quality will degrade. There needs to be an coordinated effort to move this stuff into categories.
:--[[User:B michaelsen|B michaelsen]] 09:51, 11 November 2009 (UTC)
:: Björn, what is your suggestion to make the wiki doc usable for the "lowest" intended target group (which is presumably "User" in your nomenclature)? The present mess is simply unusable (I don't talk about techies and project members but of Jo Average).
::: IMHO the simple and uncomfortable truth is that '''the present mess needs to be cleaned up'''. The mess will not magically disappear by splitting in two wikis. Also most docs evolve in a [[WikiPedia:Waterfall model|waterfall model]]-like fashion:
:::# They get spec'ed (by UX and Devs)
:::# Then project progress gets tracked (by devs) and while doing that devs document the implementation details. They do this mostly in the same docs, which is Bad(tm). But to believe splitting wikis would solve that is an illusion, because as Edwards's Law states: '''You cannot apply a technological solution to a sociological problem.'''
:::# Pieces of the rough dev-docs get picked up by the documentation project and get distilled in usable end user documentation.
:::This waterfall would drain, if there are barriers like different wikis inbetween. Also some topics are sitting between all chairs: for example, even the non-techie Users might want to use a bit of Basic, but that is tightly coupled with the API. Where you you put the [[Documentation/BASIC Guide|BASIC Guide]]? the [[Documentation/Administration Guide|Administration Guide]]?
:::I guess a separated end user documentation would end up just like http://user-faq.openoffice.org/ did.
:::How does one clean up the mess? Well, the answer is simple and uncomfortable again:
:::* Everything needs to be in a category belonging to a project, which is responsible to clean up "their house" (their categories)
:::* Everything not in a category belonging to a project get viciously deleted in two months. Sounds scary? Good. It should.
:::see also [[User Experience/SOP]]
:::--[[User:B michaelsen|B michaelsen]] 00:00, 12 November 2009 (UTC)
:::: One of the problems we face in the Wiki in general is a strong resistance to the cleanup - although, simply doing it vs asking if we can do it seems to be working so far :-) There are also historical decisions made that make wiki cleanup kind of messy... for example language namespaces. It would be nice if we could implement this... we could turn namespaces on... but then we'd have to manually move all the pages for different languages into their own namespace.. not impossible. Or.. another example, I'd love to enable FlaggedRevs to allow for change control, but the problem is configuring it so that it does not disrupt the status quo on the dev side. All issues that can be resolved of course.
:::: It's interesting to see both sides of this argument, and can I see the point being made for cleanup vs split. --[[User:Ccornell|ccornell]] 08:07, 12 November 2009 (UTC)
::::: Clayton, '''Wiki ''is'' doing''' (with or w/o asking does not matter, in most cases w/o works fine as people in general tend to be constructive) :-) (BTW - do you see, why I suggested to "externalize" discussion?) [[User:Nnino|-nino]] 18:08, 12 November 2009 (UTC)
::: '''Reply to B_michaelsen:''' The issue I try to address is not to clean up the wiki. For me, the wiki works as is. (If you continue your category cleanup, it will even work better.) The issue I'm trying to address is usability for "low level" documentation consumers, the primary target group of the User Guides. Hopfully you understand what I mean - I'm not a developer ;-) [[User:Nnino|-nino]] 18:08, 12 November 2009 (UTC)

===MindMap===
During the OOoCon20009 Doc presentation, Sophie requested a MindMap extension for the MediaWiki.
* Which MindMap is this? Sophie mentioned one that WikiPedia uses, but I've not been able to find out which one it is. --[[User:Ccornell|ccornell]] 12:00, 8 November 2009 (UTC)
* The one I had in mind (map ;) was wikimindmap [http://www.wikimindmap.org/about.htm] --[[User:sgauti|sophie]]

===Next/Prev Page at Bottom===
Pet peeve, here: reaching the bottom of a long page in one of the Guides, and having to navigate back to the top, in order to get to the next page.--[[User:TJFrazier|TJ]] 09:38, 5 November 2009 (UTC)
* This was experimented with, but... for some reason, I cannot remember exactly why, it wasn't implemented. We could definitely look at it again. --[[User:Ccornell|ccornell]] 12:01, 8 November 2009 (UTC)

===Move Material from Docs Website to Wiki===
Many (most?) legacy pages on Docs website would be much easier to keep up to date if on the wiki: things like the list of PDFs of user guides (and the PDFs themselves). Get as much out of CVS as possible. --[[User:jeanweber|jeanweber]] 11 November 2009

=== Mail Notification containing diffs ===
Clicking on the diff links in Wiki change notifications is more or less time consuming as the page needs to be loaded in the browser first. I'd like to see the diffs directly in the Mail Notifications below the text (like e.g. in MoinMoin). The first 100 diff lines would give enough information. Any chance to get this implemented?
:Sure, this can be implemented... if I know what needs to be done to do this... I don't think it's an option that can be enabled.. maybe an Extension is needed to do this? If anyone knows how this can be done, let me know. --[[User:Ccornell|ccornell]] 11:50, 17 November 2009 (UTC)

== Usage / Usability ==
# Generally, the wiki (or any docuentation CMS) needs clear '''entry points''' and from there a clear and '''consistent navigation''' and search
# several special issue are discussed below

=== Document Versioning ===
* FAQs, HowTos, tutorials and the like should clearly indicate for which OpenOffice.org versions(s) they are valid. Older help pages should go into an archive.

=== L10N ===
* end users should by default only see documents from their desired language(s) (defaulting to english if a document is not translated)
** I'm not sure how this could be done unless we rolled out a new DocWiki with full support for language namespaces. This is something we will need to research a bit. --[[User:Ccornell|ccornell]] 11:57, 8 November 2009 (UTC)

* Searches, indexes, categories and so on (may be called '''user space''') '''should reflect constraints''' mentioned above

=== Targeting / User Roles ===
End Users
* should by default only see published material
** See FlaggedRevs extension --[[User:Ccornell|ccornell]] 11:57, 8 November 2009 (UTC)

* Searches, indexes, categories and so on (may be called '''user space''') '''should reflect constraints''' mentioned above

=== Common Terminology List ===
Need to work toward a single style guide to improve consistency in terminology, writing style, etc. between user guides, help, other docs, building on what's already available. This page on [http://specs.openoffice.org/collaterals/guides/text-style-guide.html| text for the user interface] may have all or most of what we need. I have not yet read it in detail to see if everything in it fits the user guides. --[[User:jeanweber|jeanweber]] 11 November 2009

: I already started with a [[Documentation/Dashboard/Help_Style_Guide| style guide]] in the wiki, mainly intended for the How Tos. Unfortunately, it's not so visible as I would like it to be. I think it's a good idea to look into the two guides and find out what is still missing in the wiki style guide.--[[User:Mwaller|Mwaller]] 11:18, 17 November 2009 (UTC)

=== Tagging ===
Just thought of free tagging like in social bookmarking sites (very preliminary thoughts, nothing particular - just the question if it might be of help for doc purposes)

== Process ==
Ideas for improving the documentation process.
=== Category:Documentation/Incoming ===
Maybe we should have a category "Documentation/Incoming" or "Documentation/Handover" for pages containing "rough" user documentation by the development projects (e.g. Writer). Those could be polished, cleared of duplicate info and integrated in the "Guides" by the Documentation project.
The page [[Writer/page styles]] is an example of such a page. I guess most of its content is already in the "Guides", but it should be checked if there is any additional info in it. If not or if all content has been merged into the pages handled by the Documentation project, those pages should be deleted.
On a second thought it might be a good idea in general to have "${PROJECT}/Incoming" categories for all projects. Everyone would be able to put stuff in these categories saying "I think this belongs to you". Project members then can either:
* Integrate the content into their current structure
* Move the content to another, more fitting "${PROJECT}/Incoming"
:Note: Actually there is [[:Category:Documentation/Candidate]] meeting the description above. Still, we might find having such a category (with a common naming scheme) for each project useful. --[[User:B michaelsen|B michaelsen]] 11:24, 12 November 2009 (UTC)

=== User-friendly and Prioritized "Task List" ===
(Need a better term, as I do NOT mean the task list generated from IssueTracker.) Especially for the user guides, we need an easy-to-access, easy-to-edit list of which chapters need what type of work: update for version X, check for accuracy, edit for English usage, fill in missing info or screenshots, etc., and WHO is currently working on what. All with an indication of priority: what's most urgent and important. --[[User:jeanweber|jeanweber]] 11 November 2009
: Jean, could [[User:Nnino/Drafts/Oooauthors TodoList|this Wiki prototype]] be helpful? [[User:Nnino|-nino]] 16:12, 12 November 2009 (UTC)

=== Consolidate Wiki Rules ===
Merge:
* [[Marketing#Marketing_wiki_usage]]
* [[User_Experience/SOP]]
* [[Documentation/Dashboard/Wiki_Editing_Policy]]
* [[Wiki/Guidelines]]
* [[Art/Wiki_Instructions]]
* [[Documentation/Dashboard/Styles]]
* [[OOoArt_Art_Contributions]]
* [[OOoArt--Art_Contributions]]
* [[User_Experience/Wiki_Instructions]]
* [[Wiki_Improvement_Effort]]
* (... add more wiki use documentation here)
into one global set of rules.

== Documentation Ownership on the Wiki ==
Use Categories to attribute documentation ownership/maintainers. Non-english content should always be attributed to a [[NLC]] Project by Categories.

== The Licencing Problem ==
The Licencing problem should be solved generically.
* When editing a wiki page, there should be an explicit licence aggreement (ATM there you are pointed to [[OpenOffice.org Wiki:Copyrights]] and from there to other pages.)
* What licence shall we use for which purpose?
* just FYI: When starting to wikify German OOoAuthors stuff (up to now only the [[DE/Dokumentation/OOo 2.x/Handbücher|wg2]]) we had a licencing discussion in the dev@de mailing list, which led to the current solution (triple licenced wiki pages to make back porting to OOoAuthors' ODT going smooth)

== Other ==

Other ideas? Questions? Comments? (but no critics, please :-) )
=== Category cleanup ===
Categories need to be renamed systematically. This is especially true for the [[:Category:NLC|NLC subcategories]] which are a totally unsystematic mess. Proposal: Native Language Categories should follow the following scheme:
:'''NLC/${ISO 639-1:2002 language code}'''
The job should be easy to perform with a bot. --[[User:B michaelsen|B michaelsen]] 09:59, 11 November 2009 (UTC)
: This also points to one of the other issues... the inconsistent subpage naming with the various language groups. It turned out this way because no one at the time really knew where their language specific content should be... so they made a best guess. I'd like to see the content in various languages consolidated under a master parent page that is the ISO language code for that language (for example how the [[DE]], [[JA]], [[FR]] etc communities are now set up). This can be done using a bot... but the NLC people from each community need to be involved. --[[User:Ccornell|ccornell]] 13:20, 23 November 2009 (UTC)

=== Review internal documents? ===
Some OO.o internal documents, especially specifications, are available, and even sent out, to users. Might some of the authors be interested in our help, with reviewing and polishing (I'm thinking of proof-reading and light copy-editing, mostly)? --[[User:TJFrazier|TJ]] 12:46, 5 November 2009 (UTC)

=== Image naming convention in the wiki? ===
I wonder if it would be a good idea to give images (resp. screenshots) "speaking" names - e.g. "InsertImageFromFile-icon.png" (or IconInsertImageFromFile.png") as this could reduce redundancy + number of uploaded files and could be also of use if an icon changes. [[User:Nnino|-nino]] 22:33, 10 November 2009 (UTC)
* That's a good idea, and one that has been attempted in a few places. There has been no clear statement on this, so people (myself included) picked image names that made sense at the time (or just used the legacy name from the source docs). --[[User:Ccornell|ccornell]] 07:18, 11 November 2009 (UTC)
* Another related question, regardless of naming convention, how do we find out what image have been uploaded? MediaWiki has an image gallery, but it's a generic one showing all images uploaded, not just the ones we want/need. Maybe there is an extension that allows us to view images by Category? --[[User:Ccornell|ccornell]] 07:25, 11 November 2009 (UTC)

=== Just some additional thoughts ===
# What do we know about our users (in case of documentation - are they called readers?)? Who does need what kind of documentation? Who is satisfied who is not? How could we monitor this 'customer satisfaction'?
#* We have access to some visitor stats (although there is a gap of a couple months in the stats due to an error on my part). This might give us some ideas... --[[User:Ccornell|ccornell]] 07:24, 11 November 2009 (UTC)
# Would it help to define a (small) set of "top ten" or "most needed documents" on which (updating/translating) efforts should focussed to keep them up to date first (and only later writing all the other stuff) - i.e. the question if priorization would help?
#* How do we identify the top 10/most needed docs? By access stats on the websites? This is a question I've been struggling with... We can def prioritize based on our own perception of what is needed, and then fine tune it later based on what data we can collect... mailing list questions and forum posts are a good indicator or where the weak points are (although a huge percentage of the new user questions are answered by them simply pressing F1 and looking in the Application Help). --[[User:Ccornell|ccornell]] 07:24, 11 November 2009 (UTC)
# How could we organize users/customers to cooperate creating good documentation? By expressing their needs?
#* Maybe a new/different feedback channel? There is a sense of disconnect between the end user and the Doc Project (at least to me). End users/readers don't know what channels they can use to communicate back to the writers... yes there is Issue Tracker, but try explaining that tool to someone who has trouble installing OOo in Windows. The mailing lists seem to confuse a significant number of users as well. --[[User:Ccornell|ccornell]] 07:24, 11 November 2009 (UTC)

== Questions ==
* '''Wiki/OOoAuthors:''' Do we need to aggree (now) on a single common tool/approach? Couldn't we continue with two (or more) (equal?) tools for a while? And let "the community" decide? For doc localization efforts, it appears many language communities have already made the decision in favour of the wiki, and some (like the German) in favor of the ODT/OOoAuthors.
The Dutch speaking community is also in favour of ODT/OOoAuthors as a workspace.
But can anything be done to have OOoAuthors site more quickly accesible? --[[vpanter]] 11:35 11 Nov 2009 (UTC)

Did you ask for a better performance of the OOoAuthors site? --[[User:Andreasma|Andreasma]] 15:31, 24 November 2009 (UTC)

* I don't think there needs to be a single tool, but what would be nice is a more unified approach to docs, or at the very least a better defined approach (this is especially important for new contributors... a group that we need to build up). --[[User:Ccornell|ccornell]] 07:14, 11 November 2009 (UTC)
[[Category: Documentation/Dashboard]]

Documentation/Dashboard/Project Plan

2009-10-04T09:49:36Z

Andreasma: /* Identifying the gaps and problem areas */

{{DISPLAYTITLE:Documentation Project 2009/10}}

The OOo Documentation Project needs some planning and guidance. There is a lot of work that can be done, but exactly what is unclear.

This is a first draft of ideas (initial input is based on an email conversation with Valden L.).

{{Documentation/Note|This only covers the User Documentation. Application Help is a separate component and not included in this brainstorm.}}

== Identifying the gaps and problem areas ==

#Identify the duplication of effort. Exactly how many different Doc projects exist? How many are active? How many are producing docs that are duplicates of existing docs? Are any working with or in parallel with the main OOo Doc Project?
#*[http://ooodocs.sourceforge.net/index.php http://ooodocs.sourceforge.net/index.php]
#*[http://oooauthors.org/ http://oooauthors.org/]
#*[http://wiki.services.openoffice.org http://wiki.services.openoffice.org]
#*[http://en.flossmanuals.net/OpenOffice http://en.flossmanuals.net/OpenOffice]
#*Others
#Licenses that each of the many docs are released under. (PDL, CC-BY and GPL)
#*Are they compatible? or do they conflict with each other?
#*Other?
#What manuals are currently available?
#What manuals are missing? For example, is there an OOo Math Guide?
#What communication channels are we using?
#*The dev@documentation mailing list?
#*The authors@user-faq.openoffice.org mailing list?
#*Comments inside an odt-file?
#*The OOoForum?
#*The Wiki discussion pages?
#*Other?
#Doc process? Is there any definition of what to do, and how to do it? All on the Wiki? Offline in another process?
#Where can new authors or community members get started?
#*This is one of the biggest gaps in my opinion... new Doc Project members don't know where to go, or what to start with.
#*There is a Wiki Category of documents that need attention, but it's not really clear what actually needs to be done or what the priorities are.
#Languages? The OOoDocs are being translated into multiple languages. Are the needs of the translators being met? Link to the translation process?
#Publication?
#*On the Wiki only? Is the Wiki meeting the needs of the users?
#*Provide "Wiki Books" ( eg [[Documentation/Wiki Books]])
#*Other?
#Identify the possible Doc Project roles, with descriptions:
#*Writing
#*Reviewing
#*Editing or proofreading existing documents
#*Research (what user questions are not covered, or hard to find)
#*Maintenance (keep pages up to date with changes in OOo, and clearly identify which ooo version is documented in How Tos and FAQs)
#*Screen captures and other artwork
#*Others? For example more technical roles, Wiki maintenance/admin, website maintenance etc. Important to identify where new members can contribute.. make it easy for them to find things they can do for the Doc Project (bite sized chunks).
#Explain were different documentation is written/developed (simple and concise description... with links?)

== Proposed Plan to fill the known gaps and focus on some of the problem areas ==

TBD

Documentation/Dashboard/CMS Evaluation

2009-10-04T09:42:19Z

Andreasma: /* Tools to Evaluate */

{{Documentation/Banner}}
{{DISPLAYTITLE:CMS Evaluation for Multilingual Documentation Maintenance}}

== Purpose of this page ==

This page is intended to collect and discuss requirements, processes, and tools to
implement a '''content management framework''' that allows '''maintenance of multilingual
documentation'''.

The goal is to find a way to intelligently create, update, localize, and
publish documentation in multiple languages. We are in agreement, that the current
Mediawiki-based solution, while having unbeatably low barrier to contribution, lacks
basic content management functions required to maintain documentation in multiple
languages, and publish documentation that went through review and quality
assurance cycles.

== Open Questions ==

# Will the CMS also be used as publication platform for users?

==Scenarios==

...

{{Spacer|20}}

==Requirements==

Enter requirements that a content management framework should meet. Think problem, not solution.

{|class="prettytable sortable"
|-
!Requirement !!Description !!Examples
|-valign=top
|Access Control
|Availability of customizable user group access levels, document based, document-type based, or document-status based
|
|-valign=top
|Multi-Language Access
|GUI must be available in multiple languages, switching between document languages
|
|-valign=top
|Localization
|Allow for localization of documents, availability of glossary, terminology, translation memory, or interface to external localization tools and formats
|
|-valign=top
|Document Workflow
|Document creation and maintenance must take place inside a customizable work flow including steps to create, edit, review, publish, and archive documents in multiple languages
|
|-valign=top
|Document Publication
|Ability to publish documents internally and to different sites in different formats (ODF, PDF, HTML)
|
|-valign=top
|Extensability
|Framework to add extensions that provide special services, availability of vibrant extension development community
|
|-valign=top
|API for programmatic access
|Ability to automate tasks like mass-changes to documents using API access
|
|-valign=top
|Metrics
|Ability to measure access and usage metrics
|
|-valign=top
|ODF support
|Support of ODF documents, metadata evaluation, search in ODF, ODF diffs, plugging of OOo instances
|
|-valign=top
|WYSIWYG support
|Support of WYSIWYG editor for non-ODF content
|
|-valign=top
|Document Versioning
|Version control of documents, ability to recover/rollback old versions, milestones, creating release tags across different documents/languages
|
|-valign=top
|Document Rating
|Rating of documents by readers (only required if CMS will also be the publication framework)
|
|-valign=top
|Comments
|Add comments to documents by readers (only required if CMS will also be the publication framework)
|
|-valign=top
|Ease of Use
|
|
|-valign=top
|Registration with click-through agreement
|New users of the framework may need to agree to Terms of Use
|
|-valign=top
|License maintenance
|Ability to attach different licenses to different content pieces. Ability to track license usage and mixing of licenses in aggregated content.
|
|-valign=top
|Content aggregation
|Ability to aggregate content modules to different documentation types.
|
|}


{{Spacer|20}}

==Tools to Evaluate==

See also the [http://en.wikipedia.org/wiki/List_of_content_management_systems#Free_and_open_source_software Wikipedia list of CMSs]

{|class="prettytable sortable"
|-valign=top
! Tool !! Description !! Pros !! Cons
|-valign=top
|[http://plone.org/ Plone]
|CMS built on top of Zope, e.g. [http://www.oooauthors.org http://www.oooauthors.org], [http://www.plone.org http://www.plone.org]
|
* very low entry threshold
* dynamic navigation
* tools for editing like wordprocessor
* multilingual support right out of the box
* external editor posible
* many extensions (products) available
* ODF files support (also preview inside the cms)
* customizable workflow for every folder / subproject / nat-lang-group
* finetuning of rights for every function
|
|-valign=top
|[http://www.mediawiki.org Mediawiki with Extensions]
|
|
* supposed lowest entry threshold
* best suited for setting up a "quick and dirty pilot environment" (e.g. for trying out workflows)
* very large estension base
* existing implementation
|
* not well suited to implement specific behavior (e.g. automatized workflows)
|-valign=top
|[http://drupal.org/ Drupal]
|Very popular CMS
|
* Rich in multilingual and translation support
* Very widely used, so familiar to users
|
|-valign=top
|[http://www.alfresco.com/ Alfresco]
|Alfresco is the Open Source Alternative for Enterprise Content Management (ECM), providing Document Management, Collaboration, Records Management, Knowledge Management, Web Content Management and Imaging.
|
* sophisticated, enterprise-level CMS
* ODF integration
|Learning curve?
|-valign=top
|Joomla
|
|
|
|-valign=top
|Mambo
|
|
|
|-valign=top
|OpenCMS
|
|
|
|-valign=top
|O3Spaces
|
|
|
|-valign=top
|[http://cocoondev.org/daisy/index.html Daisy]
|Daisy is a content management system that offers rich out-of-the-box functionality combined with solid foundations for extensibility and integration. Daisy consists of two main components:
* a stand-alone repository server accessible through HTTP/XML (using the ReST style of WebServices) and/or a high-level (remote) Java API, and
* an extensive editing and publishing front-end web application running inside Apache Cocoon.
(copied from the Daisy website)
|
* WYSIWYG editing
* Document inclusions
* PDF publishing of single pages or collections of pages as a book
|
|}

Documentation/Dashboard/CMS Evaluation

2009-10-04T09:38:48Z

Andreasma: /* Tools to Evaluate */

{{Documentation/Banner}}
{{DISPLAYTITLE:CMS Evaluation for Multilingual Documentation Maintenance}}

== Purpose of this page ==

This page is intended to collect and discuss requirements, processes, and tools to
implement a '''content management framework''' that allows '''maintenance of multilingual
documentation'''.

The goal is to find a way to intelligently create, update, localize, and
publish documentation in multiple languages. We are in agreement, that the current
Mediawiki-based solution, while having unbeatably low barrier to contribution, lacks
basic content management functions required to maintain documentation in multiple
languages, and publish documentation that went through review and quality
assurance cycles.

== Open Questions ==

# Will the CMS also be used as publication platform for users?

==Scenarios==

...

{{Spacer|20}}

==Requirements==

Enter requirements that a content management framework should meet. Think problem, not solution.

{|class="prettytable sortable"
|-
!Requirement !!Description !!Examples
|-valign=top
|Access Control
|Availability of customizable user group access levels, document based, document-type based, or document-status based
|
|-valign=top
|Multi-Language Access
|GUI must be available in multiple languages, switching between document languages
|
|-valign=top
|Localization
|Allow for localization of documents, availability of glossary, terminology, translation memory, or interface to external localization tools and formats
|
|-valign=top
|Document Workflow
|Document creation and maintenance must take place inside a customizable work flow including steps to create, edit, review, publish, and archive documents in multiple languages
|
|-valign=top
|Document Publication
|Ability to publish documents internally and to different sites in different formats (ODF, PDF, HTML)
|
|-valign=top
|Extensability
|Framework to add extensions that provide special services, availability of vibrant extension development community
|
|-valign=top
|API for programmatic access
|Ability to automate tasks like mass-changes to documents using API access
|
|-valign=top
|Metrics
|Ability to measure access and usage metrics
|
|-valign=top
|ODF support
|Support of ODF documents, metadata evaluation, search in ODF, ODF diffs, plugging of OOo instances
|
|-valign=top
|WYSIWYG support
|Support of WYSIWYG editor for non-ODF content
|
|-valign=top
|Document Versioning
|Version control of documents, ability to recover/rollback old versions, milestones, creating release tags across different documents/languages
|
|-valign=top
|Document Rating
|Rating of documents by readers (only required if CMS will also be the publication framework)
|
|-valign=top
|Comments
|Add comments to documents by readers (only required if CMS will also be the publication framework)
|
|-valign=top
|Ease of Use
|
|
|-valign=top
|Registration with click-through agreement
|New users of the framework may need to agree to Terms of Use
|
|-valign=top
|License maintenance
|Ability to attach different licenses to different content pieces. Ability to track license usage and mixing of licenses in aggregated content.
|
|-valign=top
|Content aggregation
|Ability to aggregate content modules to different documentation types.
|
|}


{{Spacer|20}}

==Tools to Evaluate==

See also the [http://en.wikipedia.org/wiki/List_of_content_management_systems#Free_and_open_source_software Wikipedia list of CMSs]

{|class="prettytable sortable"
|-valign=top
! Tool !! Description !! Pros !! Cons
|-valign=top
|[http://plone.org/ Plone]
|CMS built on top of Zope, e.g. [http://www.oooauthors.org http://www.oooauthors.org], [http://www.plone.org http://www.plone.org]
|
* very low entry threshold
* dynamic navigation
* tools for editing like wordprocessor
* multilingual support right out of the box
* external editor posible
* many extensions (products) available
* ODF files support (also preview inside the cms)
* customizable workflow for every folder / subproject / nat-lang-group
|
|-valign=top
|[http://www.mediawiki.org Mediawiki with Extensions]
|
|
* supposed lowest entry threshold
* best suited for setting up a "quick and dirty pilot environment" (e.g. for trying out workflows)
* very large estension base
* existing implementation
|
* not well suited to implement specific behavior (e.g. automatized workflows)
|-valign=top
|[http://drupal.org/ Drupal]
|Very popular CMS
|
* Rich in multilingual and translation support
* Very widely used, so familiar to users
|
|-valign=top
|[http://www.alfresco.com/ Alfresco]
|Alfresco is the Open Source Alternative for Enterprise Content Management (ECM), providing Document Management, Collaboration, Records Management, Knowledge Management, Web Content Management and Imaging.
|
* sophisticated, enterprise-level CMS
* ODF integration
|Learning curve?
|-valign=top
|Joomla
|
|
|
|-valign=top
|Mambo
|
|
|
|-valign=top
|OpenCMS
|
|
|
|-valign=top
|O3Spaces
|
|
|
|-valign=top
|[http://cocoondev.org/daisy/index.html Daisy]
|Daisy is a content management system that offers rich out-of-the-box functionality combined with solid foundations for extensibility and integration. Daisy consists of two main components:
* a stand-alone repository server accessible through HTTP/XML (using the ReST style of WebServices) and/or a high-level (remote) Java API, and
* an extensive editing and publishing front-end web application running inside Apache Cocoon.
(copied from the Daisy website)
|
* WYSIWYG editing
* Document inclusions
* PDF publishing of single pages or collections of pages as a book
|
|}

DE/QA-Wochenende2009

2009-06-08T17:16:25Z

Andreasma: /* Angemeldete Teilnehmer */

[[Category:de.openoffice.org|QA-Wochenende2009]]
{{DISPLAYTITLE:QA-Wochenende 2009 im LinuxHotel in Essen}}
=QA-Wochenende 2009 Linux-Hotel Essen=

== Adresse ==

Linux-Hotel / Villa Vogelsang 
Antonienallee 1 
45279 Essen-Horst 
Tel.: 0201 8536-600 
Fax: 0201 8536-605 
E-Mail: rezeption@villa-vogelsang.de

== Ansprechpartner / Organisation ==

Jacqueline Rahemipour 
jrahemipour@openoffice.org 
Tel.: auf Anfrage

== Termin ==

12.-14.06.09

Die Anreise kann schon am Freitag erfolgen oder auch am Samstag früh. Das Programm beginnt am Samstag, 13.06.09 ab ca. 10 Uhr und endet am Sonntag, 14.06.09 um ca. 14 Uhr, damit genug Zeit für die Heimreise bleibt. Falls gewünscht können wir den großen Seminarraum bereits am Freitag nutzen.

== Worum geht es? ==

* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen
* Erfahrungsaustausch mit erfahrenen QA'lern
* Konkret anstehende Aufgaben gemeinsam bearbeiten
* die "schönsten" Bugs finden
* Die anderen netten Leute aus dem Projekt kennenlernen
* In geselliger Runde über OOo und die Welt quatschen
* und vieles mehr

In erster Linie soll das Wochenende denjenigen dienen, die im de-Projekt bereits erste Erfahrungen mit der QA-Arbeit gemacht haben. Es geht nicht darum, dass man für die Teilnahme viel wissen muss. Im Grunde muss nur das entsprechende Interesse für QA / Lokalisierung da sein und die Bereitschaft, auch mal an einer konkreten Aufgabe in diesem Bereich mitzuarbeiten.

== Angemeldete Teilnehmer ==

{| border="1" cellpadding="2"
|-
! Nr.
! Name
! Vorname
! Anreise am
! ggfs. Uhrzeit
! mit Übernachtung?
! Bemerkungen
|-

! 1
|| Rahemipour || Jacqueline || Freitag || ca. 10 Uhr || ja ||
|-

! 2
|| Geib || Gerald || Freitag || ca. 18:30 Uhr || ja ||
|-.

! 3
|| Brekenfelder || Ulf || Freitag || ca. 18:30 Uhr || ja ||
|-

! 4
|| Pechlaner || Wolfgang || Freitag || ca. 12 Uhr || ja || Vegetarier
|-

! 5
|| Effenberger || Florian || Freitag || nachmittags || ja ||
|-

! 6
|| Mantke || Andreas || Freitag || (versuche ca. 15.00 Uhr da zu sein) || ja (Samstag/Sonntag) ||
|-

! 7
|| Wilper || Simon || Freitag || ca. 16 Uhr || ja || Bringe zur Sicherheit mit: 3-fach-Steckdose, ausreichend langes Netzwerkkabel
|-

! 8
|| Delfs || Helge || Freitag || ca. 18:30 Uhr || ja ||
|-

! 9
|| Stehmann || Mechtilde || Freitag || || ja ||Benötige 1 TFT-Monitor
|-

! 10
|| Schnabel || André || Freitag || || ja ||
|-

! 11
|| Hoch || Eric || Freitag/Samstag || || ja || Zimmer erst voraussichtlich erst ab Samstag
|-

! 12
|| Hagmann || Martin || Freitag || || ja || aus der Schweiz
|-

! 13
|| Werner || Alexander || Freitag || nachmittags || ja ||
|-

! 14
|| Habermann || Jens || Samstag || || nein ||
|-

! 15
|| Bircher || Raphael || Freitag || Abend || ja || aus der Schweiz
|-

! 16
|| evtl. Dormann || Markus || Freitag || || nein || steht noch nicht fest, Zimmer kann nicht garantiert werden
|-

! 17
|| Baltzer || Stefan || Freitag || ca. 18:30 Uhr || ja ||
|-

! 18
|| Andrae || Joost || Freitag || ca. 18:30 Uhr || ja ||
|-

! 19
|| Rückgauer || Bernhard || Freitag || || ja || nur 1 Übernachtung
|-

! 20
|| Groß || Stephanie || Freitag || || ja || nur 1 Übernachtung, 2 Personen
|-

! 21
|| Altmann || Uwe || Freitag o. Sa. || || nein || Teilname noch offen
|-

! 22
|| Hackert || Thomas || Samstag || || ja ||
|-

|}

== Geplantes Programm ==

Das ganze ist als grobe Hülle gedacht, in den einzelnen Blöcken sollte immer Zeit für Diskussion bzw. direktes Arbeiten enthalten sein. In der Regel dürften die Themen für fast alle interessant sein. Es sollte aber immer die Möglichkeit gegeben sein, dass einzelne etwas Abseits an anderen Themen arbeiten.

===Themenvorschläge===

[Programm für 2009 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]

* '''Einführung für Neulinge''' - Erklärung von CWS/MWS, Arbeiten mit dem Issuetracker, EIS und Buildbot (Raphael Bircher)
* '''Support - Marketing''' - Wie können wir besser Probleme kommunizieren? (Mechtilde Stehmann)
* '''Automatisches Testen in der Community''' - TT zum laufen prügeln, Serientests mit Scripts, Idee Testbot (Raphael Bircher)
* '''Offline Übersetzungswerkzeuge effizient benutzen''' - Kontrastprogramm zum letztjährigen Pootle (André Schnabel)
* '''Quo Vadis, QS?''' - Aufzucht und Hege von Qualität :-) (Stefan Baltzer) (3 Stunden Samstag nachmittag)
* '''Was muss für ein Release organisiert werden?''' - organisatorischer Hintergrund zum Release-Prozess (Mechtilde Stehmann)

===Samstag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:15
|| '''Begrüßung'''
* kurze Absprache des Arbeitsplanes
* Fragen zu Technik
* Organisatorisches
|| Jacqueline Rahemipour
|-

! 10:15-11:15
|| '''Einführung für Neulinge'''
* Erklärung von CWS/MWS, Arbeiten mit dem Issuetracker, EIS und Buildbot
|| Raphael Bircher
|-

! 11:30-12:30
|| '''Was muss für ein Release organisiert werden?'''
* organisatorischer Hintergrund zum Release-Prozess
|| Mechtilde Stehmann
|-

! 12:30-14:00
|| '''Pause''' Mittagessen
|| alle
|-

! 14:00-15:30
|| '''Quo Vadis, QS?'''
* Aufzucht und Hege von Qualität
|| Stefan Baltzer
|-

! 15:30-16:00
|| '''Pause''' Kaffee und Kuchen
|| alle
|-

! 16:00-17:00
|| '''Fortsetzung: Quo Vadis, QS?'''
* Aufzucht und Hege von Qualität
|| Stefan Baltzer
|-

! 17:00-Open End
|| '''Bughunting'''
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen
* neue Issues aufgeben
* Fehlersuche
|| alle
|-

|}

===Sonntag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:45
|| '''Support - Marketing'''
* Wie können wir besser Probleme kommunizieren?
|| Mechtilde Stehmann
|-

! 11:00-11:45
|| '''Automatisches Testen in der Community'''
* Testtool, Serientests mit Scripts, Idee Testbot
|| Raphael Bircher
|-

! 12:00-13:00
|| '''Offline Übersetzungswerkzeuge effizient benutzen'''
* Kontrastprogramm zum letztjährigen Pootle
|| André Schnabel
|-

|}

== Anreise ==

=== S-Bahn ===
Die S-Bahn-Haltestelle "Essen-Horst (S)" (Linie S3) ist nur 8 Minuten Fußweg vom Hotel entfernt. Am S-Bahnhof Horst ankommen aus Richtung Essen-Hbf, dann bitte unter den Gleisen durchgehen, den Fußweg den Berg hinauf, geht über in kleine Straße, am Ende rechts Lindkenshofer Weg) und nach 200m wieder rechts (Eberhardstr) und dann gerade auf ein braunes Holztor zugehen.

=== Bus ===
Die Haltestelle "Geschwister-Scholl-Str." der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.

=== PKW ===
Den groben Weg aus Richtung A 40 entnehmt bitte der Skizze auf den Seiten des [http://www.linuxhotel.de/anreise.html Linux-Hotels] bzw. befragt einen Routenplaner. Folgt den Schildern „Route Industriekultur“ in Richtung "Eisenbahnmuseum". Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder "Villa-Vogelsang".

== Übernachtung ==

Die Übernachtung erfolgt in Doppelzimmern im Linux-Hotel, die Kosten dafür übernimmt der Verein OpenOffice.org Deutschland e.V.. Die genaue Raumverteilung machen wir vorort. Sonderwünsche bitte frühzeitig Jacqueline mitteilen!

== Verpflegung ==

Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel.

Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.
'''Gerne werden Salatspenden angenommen!'''
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.

'''Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.'''

Auch für Getränke wird gesorgt. Ihr könnt euch im Linux-Hotel bei den Getränken selbst bedienen (alkoholfreie Getränke, Bier, Kaffee, Tee). Besondere Getränke (Wein, Spirituosen) sind in der mit dem Linux-Hotel vereinbarten Getränkepauschale nicht enthalten. Diese müssen dann selbst vorort bezahlt werden.

== Seminarraum ==

Es steht uns ein großer Seminarraum zur Verfügung. Auch ein Beamer wird vorort sein. Bitte bringt wenn möglich euer eigenes Notebook bzw. einen eigenen Rechner mit.

Falls jemand keinen eigenen Rechner mitbringen kann, bitte vorab Bescheid sagen, damit wir gegebenenfalls noch etwas organisieren können (mehrere Vereinsrechner stehen zur Verfügung, 3 weitere Laptops kann ich mitbringen).

== Internet ==

Im Hotel und im Seminarraum ist WLAN verfügbar, jedoch sollten wir uns aufgrund der Erfahrungen in den letzten beiden Jahren nicht darauf verlassen und wenn möglich noch Netzwerkkabel mitbringen.

== Freizeit ==

Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Badetücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.

== Sonstiges ==

Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochenende auf uns allein gestellt, das heißt:

* Es herrscht an dem Wochenende Selbstbedienung, an den Getränkekühlbüffets / Weinkühlschrank / Kaffee/Teeautomat usw., Geschirr muss hinterher in die Spülmaschine geräumt werden.

* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen

* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug & Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.

'''Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräumarbeiten behilflich sein?'''

* Nachdem mein Flieger erst um 21 Uhr von DUE abfliegt, hab ich natürlich noch etwas Zeit (wope)

DE/QA-Wochenende2009

2009-06-08T17:14:35Z

Andreasma: /* Angemeldete Teilnehmer */

[[Category:de.openoffice.org|QA-Wochenende2009]]
{{DISPLAYTITLE:QA-Wochenende 2009 im LinuxHotel in Essen}}
=QA-Wochenende 2009 Linux-Hotel Essen=

== Adresse ==

Linux-Hotel / Villa Vogelsang 
Antonienallee 1 
45279 Essen-Horst 
Tel.: 0201 8536-600 
Fax: 0201 8536-605 
E-Mail: rezeption@villa-vogelsang.de

== Ansprechpartner / Organisation ==

Jacqueline Rahemipour 
jrahemipour@openoffice.org 
Tel.: auf Anfrage

== Termin ==

12.-14.06.09

Die Anreise kann schon am Freitag erfolgen oder auch am Samstag früh. Das Programm beginnt am Samstag, 13.06.09 ab ca. 10 Uhr und endet am Sonntag, 14.06.09 um ca. 14 Uhr, damit genug Zeit für die Heimreise bleibt. Falls gewünscht können wir den großen Seminarraum bereits am Freitag nutzen.

== Worum geht es? ==

* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen
* Erfahrungsaustausch mit erfahrenen QA'lern
* Konkret anstehende Aufgaben gemeinsam bearbeiten
* die "schönsten" Bugs finden
* Die anderen netten Leute aus dem Projekt kennenlernen
* In geselliger Runde über OOo und die Welt quatschen
* und vieles mehr

In erster Linie soll das Wochenende denjenigen dienen, die im de-Projekt bereits erste Erfahrungen mit der QA-Arbeit gemacht haben. Es geht nicht darum, dass man für die Teilnahme viel wissen muss. Im Grunde muss nur das entsprechende Interesse für QA / Lokalisierung da sein und die Bereitschaft, auch mal an einer konkreten Aufgabe in diesem Bereich mitzuarbeiten.

== Angemeldete Teilnehmer ==

{| border="1" cellpadding="2"
|-
! Nr.
! Name
! Vorname
! Anreise am
! ggfs. Uhrzeit
! mit Übernachtung?
! Bemerkungen
|-

! 1
|| Rahemipour || Jacqueline || Freitag || ca. 10 Uhr || ja ||
|-

! 2
|| Geib || Gerald || Freitag || ca. 18:30 Uhr || ja ||
|-.

! 3
|| Brekenfelder || Ulf || Freitag || ca. 18:30 Uhr || ja ||
|-

! 4
|| Pechlaner || Wolfgang || Freitag || ca. 12 Uhr || ja || Vegetarier
|-

! 5
|| Effenberger || Florian || Freitag || nachmittags || ja ||
|-

! 6
|| Mantke || Andreas || Freitag (versuche ca. 15.00 Uhr da zu sein || || ja (Samstag/Sonntag) ||
|-

! 7
|| Wilper || Simon || Freitag || ca. 16 Uhr || ja || Bringe zur Sicherheit mit: 3-fach-Steckdose, ausreichend langes Netzwerkkabel
|-

! 8
|| Delfs || Helge || Freitag || ca. 18:30 Uhr || ja ||
|-

! 9
|| Stehmann || Mechtilde || Freitag || || ja ||Benötige 1 TFT-Monitor
|-

! 10
|| Schnabel || André || Freitag || || ja ||
|-

! 11
|| Hoch || Eric || Freitag/Samstag || || ja || Zimmer erst voraussichtlich erst ab Samstag
|-

! 12
|| Hagmann || Martin || Freitag || || ja || aus der Schweiz
|-

! 13
|| Werner || Alexander || Freitag || nachmittags || ja ||
|-

! 14
|| Habermann || Jens || Samstag || || nein ||
|-

! 15
|| Bircher || Raphael || Freitag || Abend || ja || aus der Schweiz
|-

! 16
|| evtl. Dormann || Markus || Freitag || || nein || steht noch nicht fest, Zimmer kann nicht garantiert werden
|-

! 17
|| Baltzer || Stefan || Freitag || ca. 18:30 Uhr || ja ||
|-

! 18
|| Andrae || Joost || Freitag || ca. 18:30 Uhr || ja ||
|-

! 19
|| Rückgauer || Bernhard || Freitag || || ja || nur 1 Übernachtung
|-

! 20
|| Groß || Stephanie || Freitag || || ja || nur 1 Übernachtung, 2 Personen
|-

! 21
|| Altmann || Uwe || Freitag o. Sa. || || nein || Teilname noch offen
|-

! 22
|| Hackert || Thomas || Samstag || || ja ||
|-

|}

== Geplantes Programm ==

Das ganze ist als grobe Hülle gedacht, in den einzelnen Blöcken sollte immer Zeit für Diskussion bzw. direktes Arbeiten enthalten sein. In der Regel dürften die Themen für fast alle interessant sein. Es sollte aber immer die Möglichkeit gegeben sein, dass einzelne etwas Abseits an anderen Themen arbeiten.

===Themenvorschläge===

[Programm für 2009 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]

* '''Einführung für Neulinge''' - Erklärung von CWS/MWS, Arbeiten mit dem Issuetracker, EIS und Buildbot (Raphael Bircher)
* '''Support - Marketing''' - Wie können wir besser Probleme kommunizieren? (Mechtilde Stehmann)
* '''Automatisches Testen in der Community''' - TT zum laufen prügeln, Serientests mit Scripts, Idee Testbot (Raphael Bircher)
* '''Offline Übersetzungswerkzeuge effizient benutzen''' - Kontrastprogramm zum letztjährigen Pootle (André Schnabel)
* '''Quo Vadis, QS?''' - Aufzucht und Hege von Qualität :-) (Stefan Baltzer) (3 Stunden Samstag nachmittag)
* '''Was muss für ein Release organisiert werden?''' - organisatorischer Hintergrund zum Release-Prozess (Mechtilde Stehmann)

===Samstag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:15
|| '''Begrüßung'''
* kurze Absprache des Arbeitsplanes
* Fragen zu Technik
* Organisatorisches
|| Jacqueline Rahemipour
|-

! 10:15-11:15
|| '''Einführung für Neulinge'''
* Erklärung von CWS/MWS, Arbeiten mit dem Issuetracker, EIS und Buildbot
|| Raphael Bircher
|-

! 11:30-12:30
|| '''Was muss für ein Release organisiert werden?'''
* organisatorischer Hintergrund zum Release-Prozess
|| Mechtilde Stehmann
|-

! 12:30-14:00
|| '''Pause''' Mittagessen
|| alle
|-

! 14:00-15:30
|| '''Quo Vadis, QS?'''
* Aufzucht und Hege von Qualität
|| Stefan Baltzer
|-

! 15:30-16:00
|| '''Pause''' Kaffee und Kuchen
|| alle
|-

! 16:00-17:00
|| '''Fortsetzung: Quo Vadis, QS?'''
* Aufzucht und Hege von Qualität
|| Stefan Baltzer
|-

! 17:00-Open End
|| '''Bughunting'''
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen
* neue Issues aufgeben
* Fehlersuche
|| alle
|-

|}

===Sonntag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:45
|| '''Support - Marketing'''
* Wie können wir besser Probleme kommunizieren?
|| Mechtilde Stehmann
|-

! 11:00-11:45
|| '''Automatisches Testen in der Community'''
* Testtool, Serientests mit Scripts, Idee Testbot
|| Raphael Bircher
|-

! 12:00-13:00
|| '''Offline Übersetzungswerkzeuge effizient benutzen'''
* Kontrastprogramm zum letztjährigen Pootle
|| André Schnabel
|-

|}

== Anreise ==

=== S-Bahn ===
Die S-Bahn-Haltestelle "Essen-Horst (S)" (Linie S3) ist nur 8 Minuten Fußweg vom Hotel entfernt. Am S-Bahnhof Horst ankommen aus Richtung Essen-Hbf, dann bitte unter den Gleisen durchgehen, den Fußweg den Berg hinauf, geht über in kleine Straße, am Ende rechts Lindkenshofer Weg) und nach 200m wieder rechts (Eberhardstr) und dann gerade auf ein braunes Holztor zugehen.

=== Bus ===
Die Haltestelle "Geschwister-Scholl-Str." der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.

=== PKW ===
Den groben Weg aus Richtung A 40 entnehmt bitte der Skizze auf den Seiten des [http://www.linuxhotel.de/anreise.html Linux-Hotels] bzw. befragt einen Routenplaner. Folgt den Schildern „Route Industriekultur“ in Richtung "Eisenbahnmuseum". Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder "Villa-Vogelsang".

== Übernachtung ==

Die Übernachtung erfolgt in Doppelzimmern im Linux-Hotel, die Kosten dafür übernimmt der Verein OpenOffice.org Deutschland e.V.. Die genaue Raumverteilung machen wir vorort. Sonderwünsche bitte frühzeitig Jacqueline mitteilen!

== Verpflegung ==

Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel.

Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.
'''Gerne werden Salatspenden angenommen!'''
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.

'''Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.'''

Auch für Getränke wird gesorgt. Ihr könnt euch im Linux-Hotel bei den Getränken selbst bedienen (alkoholfreie Getränke, Bier, Kaffee, Tee). Besondere Getränke (Wein, Spirituosen) sind in der mit dem Linux-Hotel vereinbarten Getränkepauschale nicht enthalten. Diese müssen dann selbst vorort bezahlt werden.

== Seminarraum ==

Es steht uns ein großer Seminarraum zur Verfügung. Auch ein Beamer wird vorort sein. Bitte bringt wenn möglich euer eigenes Notebook bzw. einen eigenen Rechner mit.

Falls jemand keinen eigenen Rechner mitbringen kann, bitte vorab Bescheid sagen, damit wir gegebenenfalls noch etwas organisieren können (mehrere Vereinsrechner stehen zur Verfügung, 3 weitere Laptops kann ich mitbringen).

== Internet ==

Im Hotel und im Seminarraum ist WLAN verfügbar, jedoch sollten wir uns aufgrund der Erfahrungen in den letzten beiden Jahren nicht darauf verlassen und wenn möglich noch Netzwerkkabel mitbringen.

== Freizeit ==

Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Badetücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.

== Sonstiges ==

Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochenende auf uns allein gestellt, das heißt:

* Es herrscht an dem Wochenende Selbstbedienung, an den Getränkekühlbüffets / Weinkühlschrank / Kaffee/Teeautomat usw., Geschirr muss hinterher in die Spülmaschine geräumt werden.

* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen

* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug & Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.

'''Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräumarbeiten behilflich sein?'''

* Nachdem mein Flieger erst um 21 Uhr von DUE abfliegt, hab ich natürlich noch etwas Zeit (wope)

Building OpenOffice.org

2009-03-11T20:59:43Z

Andreasma: /* Running configure */

[[Category:Development]]
[[Category:Build_System]]

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]]. Be sure that the [[Build_Requirements | Build Requirements]] have been fulfilled.

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

Up to DEV300m39 you have to go to a subdirectory, in which the configure script lives:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

'''Now''' (>= DEV300m40) this subdirectory doesn't exist anymore and you are able to '''run configure in the root folder''' of your checkout.

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell. If you run ./configure in the root of your SRC_ROOT (>=DEV300m40) you mustn't change the directory. You can run the source directly.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.

Since DEV300m40 you are able to use make on Linux instead:
<pre>
make
</pre>
in <SRC_ROOT>.

==== Hints ====
dmake first checks for depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m2 swext 
(for DEV300_m22) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is too old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the one that is in OOo's sources just is too
old. 
Actually, there is an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

If you got an error like this
<pre>
ERROR: Error 65280 occurred while making /work/ooovanillabuild/ucb/source/ucp/gvfs
</pre>
look inside the output in your shell if there are something wrong with your glib-devel version. If you see inside the messages in the shell something like this:
<pre>

/usr/include/glib-1.2/glib.h:2725:1: warning: this is the location of the previous definition
(...)
/usr/include/glib-2.0/glib/gthread.h:352:1: warning: "G_LOCK_NAME" redefined
</pre>
you have to unistall one of the glib-devel version; mostly glib-devel version 1.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

== alternative build system ==
The instructions above describes on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at Building_with_ooobuild instead.

DE/QA-Wochenende2009

2009-02-22T19:45:35Z

Andreasma: /* Angemeldete Teilnehmer */

[[Category:de.openoffice.org|QA-Wochenende2009]]
{{DISPLAYTITLE:QA-Wochenende 2009 im LinuxHotel in Essen}}
=QA-Wochenende 2009 Linux-Hotel Essen=

== Adresse ==

Linux-Hotel / Villa Vogelsang 
Antonienallee 1 
45279 Essen-Horst 
Tel.: 0201 8536-600 
Fax: 0201 8536-605 
E-Mail: rezeption@villa-vogelsang.de

== Ansprechpartner / Organisation ==

Jacqueline Rahemipour 
jrahemipour@openoffice.org 
Tel.: auf Anfrage

== Termin ==

12.-14.06.09

Die Anreise kann schon am Freitag erfolgen oder auch am Samstag früh. Das Programm beginnt am Samstag, 13.06.09 ab ca. 10 Uhr und endet am Sonntag, 14.06.09 um ca. 14 Uhr, damit genug Zeit für die Heimreise bleibt. Falls gewünscht können wir den großen Seminarraum bereits am Freitag nutzen.

== Worum geht es? ==

* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen
* Erfahrungsaustausch mit erfahrenen QA'lern
* Konkret anstehende Aufgaben gemeinsam bearbeiten
* die "schönsten" Bugs finden
* Die anderen netten Leute aus dem Projekt kennenlernen
* In geselliger Runde über OOo und die Welt quatschen
* und vieles mehr

In erster Linie soll das Wochenende denjenigen dienen, die im de-Projekt bereits erste Erfahrungen mit der QA-Arbeit gemacht haben. Es geht nicht darum, dass man für die Teilnahme viel wissen muss. Im Grunde muss nur das entsprechende Interesse für QA / Lokalisierung da sein und die Bereitschaft, auch mal an einer konkreten Aufgabe in diesem Bereich mitzuarbeiten.

== Angemeldete Teilnehmer ==

{| border="1" cellpadding="2"
|-
! Nr.
! Name
! Vorname
! Anreise am
! ggfs. Uhrzeit
! mit Übernachtung?
! Bemerkungen
|-

! 1
|| Rahemipour || Jacqueline || Freitag || ca. 10 Uhr || ja ||
|-

! 2
|| Geib || Gerald || Freitag || || ja ||
|-

! 3
|| Brekenfelder || Ulf || Freitag || || ja ||
|-

! 4
||Pechlaner ||Wolfgang || Freitag || || ja ||
|-

! 5
|| Effenberger || Florian || Freitag || nachmittags || ja ||
|-

! 6
||Mantke ||Andreas || Samstag || || ja ||
|-

! 7
|| || || Freitag/Samstag || || ja/nein ||
|-

! 8
|| || || Freitag/Samstag || || ja/nein ||
|-

! 9
|| || || Freitag/Samstag || || ja/nein ||
|-

! 10
|| || || Freitag/Samstag || || ja/nein ||
|-

! 11
|| || || Freitag/Samstag || || ja/nein ||
|-

! 12
|| || || Freitag/Samstag || || ja/nein ||
|-

! 13
|| || || Freitag/Samstag || || ja/nein ||
|-

! 14
|| || || Freitag/Samstag || || ja/nein ||
|-

! 15
|| || || Freitag/Samstag || || ja/nein ||
|-

! 16
|| || || Freitag/Samstag || || ja/nein ||
|-

! 17
|| || || Freitag/Samstag || || ja/nein ||
|-

! 18
|| || || Freitag/Samstag || || ja/nein ||
|-

|}

== Geplantes Programm ==

Das ganze ist als grobe Hülle gedacht, in den einzelnen Blöcken sollte immer Zeit für Diskussion bzw. direktes Arbeiten enthalten sein. In der Regel dürften die Themen für fast alle interessant sein. Es sollte aber immer die Möglichkeit gegeben sein, dass einzelne etwas Abseits an anderen Themen arbeiten.

[Programm für 2009 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]

===Samstag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:15
|| '''Begrüßung'''
* kurze Absprache des Arbeitsplanes
* Fragen zu Technik
* Organisatorisches
|| Jacqueline Rahemipour
|-

! 10:15-11:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 11:00-11:45
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 11:45-12:30
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 12:30-13:30
|| '''Pause''' Mittagessen || alle
|-

! 13:30-14:15
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 14:15-15:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 15:00-15:45
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 15:45-16:15
|| '''Pause''' Kaffee und Kuchen || alle
|-

! 16:15-17:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 17:00-Open End
|| '''Bughunting'''
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen
* neue Issues aufgeben
* Fehlersuche
|| alle
|-

|}

===Sonntag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:45
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 10:45-11:30
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 11:30-12:15
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 12:15-13:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-
|}

== Anreise ==

=== S-Bahn ===
Die S-Bahn-Haltestelle "Essen-Horst (S)" (Linie S3) ist nur 8 Minuten Fußweg vom Hotel entfernt. Am S-Bahnhof Horst ankommen aus Richtung Essen-Hbf, dann bitte unter den Gleisen durchgehen, den Fußweg den Berg hinauf, geht über in kleine Straße, am Ende rechts Lindkenshofer Weg) und nach 200m wieder rechts (Eberhardstr) und dann gerade auf ein braunes Holztor zugehen.

=== Bus ===
Die Haltestelle "Geschwister-Scholl-Str." der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.

=== PKW ===
Den groben Weg aus Richtung A 40 entnehmt bitte der Skizze auf den Seiten des [http://www.linuxhotel.de/anreise.html Linux-Hotels] bzw. befragt einen Routenplaner. Folgt den Schildern „Route Industriekultur“ in Richtung "Eisenbahnmuseum". Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder "Villa-Vogelsang".

== Übernachtung ==

Die Übernachtung erfolgt in Doppelzimmern im Linux-Hotel, die Kosten dafür übernimmt der Verein OpenOffice.org Deutschland e.V.. Die genaue Raumverteilung machen wir vorort. Sonderwünsche bitte frühzeitig Jacqueline mitteilen!

== Verpflegung ==

Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel.

Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.
'''Gerne werden Salatspenden angenommen!'''
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.

'''Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.'''

Auch für Getränke wird gesorgt. Ihr könnt euch im Linux-Hotel bei den Getränken selbst bedienen (alkoholfreie Getränke, Bier, Kaffee, Tee). Besondere Getränke (Wein, Spirituosen) sind in der mit dem Linux-Hotel vereinbarten Getränkepauschale nicht enthalten. Diese müssen dann selbst vorort bezahlt werden.

== Seminarraum ==

Es steht uns ein großer Seminarraum zur Verfügung. Auch ein Beamer wird vorort sein. Bitte bringt wenn möglich euer eigenes Notebook bzw. einen eigenen Rechner mit.

Falls jemand keinen eigenen Rechner mitbringen kann, bitte vorab Bescheid sagen, damit wir gegebenenfalls noch etwas organisieren können (mehrere Vereinsrechner stehen zur Verfügung, 3 weitere Laptops kann ich mitbringen).

== Internet ==

Im Hotel und im Seminarraum ist WLAN verfügbar, jedoch sollten wir uns aufgrund der Erfahrungen in den letzten beiden Jahren nicht darauf verlassen und wenn möglich noch Netzwerkkabel mitbringen.

== Freizeit ==

Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Badetücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.

== Sonstiges ==

Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochenende auf uns allein gestellt, das heißt:

* Es herrscht an dem Wochenende Selbstbedienung, an den Getränkekühlbüffets / Weinkühlschrank / Kaffee/Teeautomat usw., Geschirr muss hinterher in die Spülmaschine geräumt werden.

* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen

* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug & Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.

'''Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräumarbeiten behilflich sein?'''

DE/QA-Wochenende2009

2009-02-22T19:42:11Z

Andreasma: /* Termin */

[[Category:de.openoffice.org|QA-Wochenende2009]]
{{DISPLAYTITLE:QA-Wochenende 2009 im LinuxHotel in Essen}}
=QA-Wochenende 2009 Linux-Hotel Essen=

== Adresse ==

Linux-Hotel / Villa Vogelsang 
Antonienallee 1 
45279 Essen-Horst 
Tel.: 0201 8536-600 
Fax: 0201 8536-605 
E-Mail: rezeption@villa-vogelsang.de

== Ansprechpartner / Organisation ==

Jacqueline Rahemipour 
jrahemipour@openoffice.org 
Tel.: auf Anfrage

== Termin ==

12.-14.06.09

Die Anreise kann schon am Freitag erfolgen oder auch am Samstag früh. Das Programm beginnt am Samstag, 13.06.09 ab ca. 10 Uhr und endet am Sonntag, 14.06.09 um ca. 14 Uhr, damit genug Zeit für die Heimreise bleibt. Falls gewünscht können wir den großen Seminarraum bereits am Freitag nutzen.

== Worum geht es? ==

* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen
* Erfahrungsaustausch mit erfahrenen QA'lern
* Konkret anstehende Aufgaben gemeinsam bearbeiten
* die "schönsten" Bugs finden
* Die anderen netten Leute aus dem Projekt kennenlernen
* In geselliger Runde über OOo und die Welt quatschen
* und vieles mehr

In erster Linie soll das Wochenende denjenigen dienen, die im de-Projekt bereits erste Erfahrungen mit der QA-Arbeit gemacht haben. Es geht nicht darum, dass man für die Teilnahme viel wissen muss. Im Grunde muss nur das entsprechende Interesse für QA / Lokalisierung da sein und die Bereitschaft, auch mal an einer konkreten Aufgabe in diesem Bereich mitzuarbeiten.

== Angemeldete Teilnehmer ==

{| border="1" cellpadding="2"
|-
! Nr.
! Name
! Vorname
! Anreise am
! ggfs. Uhrzeit
! mit Übernachtung?
! Bemerkungen
|-

! 1
|| Rahemipour || Jacqueline || Freitag || ca. 10 Uhr || ja ||
|-

! 2
|| Geib || Gerald || Freitag || || ja ||
|-

! 3
|| Brekenfelder || Ulf || Freitag || || ja ||
|-

! 4
||Pechlaner ||Wolfgang || Freitag || || ja ||
|-

! 5
|| Effenberger || Florian || Freitag || nachmittags || ja ||
|-

! 6
|| || || Freitag/Samstag || || ja/nein ||
|-

! 7
|| || || Freitag/Samstag || || ja/nein ||
|-

! 8
|| || || Freitag/Samstag || || ja/nein ||
|-

! 9
|| || || Freitag/Samstag || || ja/nein ||
|-

! 10
|| || || Freitag/Samstag || || ja/nein ||
|-

! 11
|| || || Freitag/Samstag || || ja/nein ||
|-

! 12
|| || || Freitag/Samstag || || ja/nein ||
|-

! 13
|| || || Freitag/Samstag || || ja/nein ||
|-

! 14
|| || || Freitag/Samstag || || ja/nein ||
|-

! 15
|| || || Freitag/Samstag || || ja/nein ||
|-

! 16
|| || || Freitag/Samstag || || ja/nein ||
|-

! 17
|| || || Freitag/Samstag || || ja/nein ||
|-

! 18
|| || || Freitag/Samstag || || ja/nein ||
|-

|}

== Geplantes Programm ==

Das ganze ist als grobe Hülle gedacht, in den einzelnen Blöcken sollte immer Zeit für Diskussion bzw. direktes Arbeiten enthalten sein. In der Regel dürften die Themen für fast alle interessant sein. Es sollte aber immer die Möglichkeit gegeben sein, dass einzelne etwas Abseits an anderen Themen arbeiten.

[Programm für 2009 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]

===Samstag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:15
|| '''Begrüßung'''
* kurze Absprache des Arbeitsplanes
* Fragen zu Technik
* Organisatorisches
|| Jacqueline Rahemipour
|-

! 10:15-11:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 11:00-11:45
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 11:45-12:30
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 12:30-13:30
|| '''Pause''' Mittagessen || alle
|-

! 13:30-14:15
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 14:15-15:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 15:00-15:45
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 15:45-16:15
|| '''Pause''' Kaffee und Kuchen || alle
|-

! 16:15-17:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 17:00-Open End
|| '''Bughunting'''
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen
* neue Issues aufgeben
* Fehlersuche
|| alle
|-

|}

===Sonntag===

{| border="1" cellpadding="2"
|-
! width="120" |Wann?
! width="480" | Was?
! width="180" | Wer?
|-

! 10:00-10:45
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 10:45-11:30
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 11:30-12:15
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-

! 12:15-13:00
|| '''Titel'''
* Themenbeschreibung
|| Referent
|-
|}

== Anreise ==

=== S-Bahn ===
Die S-Bahn-Haltestelle "Essen-Horst (S)" (Linie S3) ist nur 8 Minuten Fußweg vom Hotel entfernt. Am S-Bahnhof Horst ankommen aus Richtung Essen-Hbf, dann bitte unter den Gleisen durchgehen, den Fußweg den Berg hinauf, geht über in kleine Straße, am Ende rechts Lindkenshofer Weg) und nach 200m wieder rechts (Eberhardstr) und dann gerade auf ein braunes Holztor zugehen.

=== Bus ===
Die Haltestelle "Geschwister-Scholl-Str." der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.

=== PKW ===
Den groben Weg aus Richtung A 40 entnehmt bitte der Skizze auf den Seiten des [http://www.linuxhotel.de/anreise.html Linux-Hotels] bzw. befragt einen Routenplaner. Folgt den Schildern „Route Industriekultur“ in Richtung "Eisenbahnmuseum". Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder "Villa-Vogelsang".

== Übernachtung ==

Die Übernachtung erfolgt in Doppelzimmern im Linux-Hotel, die Kosten dafür übernimmt der Verein OpenOffice.org Deutschland e.V.. Die genaue Raumverteilung machen wir vorort. Sonderwünsche bitte frühzeitig Jacqueline mitteilen!

== Verpflegung ==

Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel.

Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.
'''Gerne werden Salatspenden angenommen!'''
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.

'''Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.'''

Auch für Getränke wird gesorgt. Ihr könnt euch im Linux-Hotel bei den Getränken selbst bedienen (alkoholfreie Getränke, Bier, Kaffee, Tee). Besondere Getränke (Wein, Spirituosen) sind in der mit dem Linux-Hotel vereinbarten Getränkepauschale nicht enthalten. Diese müssen dann selbst vorort bezahlt werden.

== Seminarraum ==

Es steht uns ein großer Seminarraum zur Verfügung. Auch ein Beamer wird vorort sein. Bitte bringt wenn möglich euer eigenes Notebook bzw. einen eigenen Rechner mit.

Falls jemand keinen eigenen Rechner mitbringen kann, bitte vorab Bescheid sagen, damit wir gegebenenfalls noch etwas organisieren können (mehrere Vereinsrechner stehen zur Verfügung, 3 weitere Laptops kann ich mitbringen).

== Internet ==

Im Hotel und im Seminarraum ist WLAN verfügbar, jedoch sollten wir uns aufgrund der Erfahrungen in den letzten beiden Jahren nicht darauf verlassen und wenn möglich noch Netzwerkkabel mitbringen.

== Freizeit ==

Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Badetücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.

== Sonstiges ==

Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochenende auf uns allein gestellt, das heißt:

* Es herrscht an dem Wochenende Selbstbedienung, an den Getränkekühlbüffets / Weinkühlschrank / Kaffee/Teeautomat usw., Geschirr muss hinterher in die Spülmaschine geräumt werden.

* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen

* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug & Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.

'''Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräumarbeiten behilflich sein?'''

Building OpenOffice.org

2009-02-01T19:56:34Z

Andreasma: /* Starting the real build */

[[Category:Development]]
[[Category:Build_System]]

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]]. Be sure that the [[Build_Requirements | Build Requirements]] have been fulfilled.

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

Up to DEV300m39 you have to go to a subdirectory, in which the configure script lives:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

'''Now''' (>= DEV300m40) this subdirectory doesn't exist anymore and you are able '''run configure in the root folder''' of your checkout.

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell. If you run ./configure in the root of your SRC_ROOT (>=DEV300m40) you mustn't change the directory. You can run the source directly.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.

Since DEV300m40 you are able to use make on Linux instead:
<pre>
make
</pre>
in <SRC_ROOT>.

==== Hints ====
dmake first checks for depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m2 swext 
(for DEV300_m22) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is too old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the one that is in OOo's sources just is too
old. 
Actually, there is an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

If you got an error like this
<pre>
ERROR: Error 65280 occurred while making /work/ooovanillabuild/ucb/source/ucp/gvfs
</pre>
look inside the output in your shell if there are something wrong with your glib-devel version. If you see inside the messages in the shell something like this:
<pre>

/usr/include/glib-1.2/glib.h:2725:1: warning: this is the location of the previous definition
(...)
/usr/include/glib-2.0/glib/gthread.h:352:1: warning: "G_LOCK_NAME" redefined
</pre>
you have to unistall one of the glib-devel version; mostly glib-devel version 1.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

== alternative build system ==
The instructions above describes on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at Building_with_ooobuild instead.

Building OpenOffice.org

2009-02-01T19:53:20Z

Andreasma: /* Bootstrapping */

[[Category:Development]]
[[Category:Build_System]]

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]]. Be sure that the [[Build_Requirements | Build Requirements]] have been fulfilled.

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

Up to DEV300m39 you have to go to a subdirectory, in which the configure script lives:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

'''Now''' (>= DEV300m40) this subdirectory doesn't exist anymore and you are able '''run configure in the root folder''' of your checkout.

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell. If you run ./configure in the root of your SRC_ROOT (>=DEV300m40) you mustn't change the directory. You can run the source directly.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first checks for depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m2 swext 
(for DEV300_m22) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is too old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the one that is in OOo's sources just is too
old. 
Actually, there is an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

If you got an error like this
<pre>
ERROR: Error 65280 occurred while making /work/ooovanillabuild/ucb/source/ucp/gvfs
</pre>
look inside the output in your shell if there are something wrong with your glib-devel version. If you see inside the messages in the shell something like this:
<pre>

/usr/include/glib-1.2/glib.h:2725:1: warning: this is the location of the previous definition
(...)
/usr/include/glib-2.0/glib/gthread.h:352:1: warning: "G_LOCK_NAME" redefined
</pre>
you have to unistall one of the glib-devel version; mostly glib-devel version 1.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

== alternative build system ==
The instructions above describes on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at Building_with_ooobuild instead.

Building OpenOffice.org

2009-02-01T19:47:34Z

Andreasma: /* Running configure */

[[Category:Development]]
[[Category:Build_System]]

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]]. Be sure that the [[Build_Requirements | Build Requirements]] have been fulfilled.

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

Up to DEV300m39 you have to go to a subdirectory, in which the configure script lives:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

'''Now''' (>= DEV300m40) this subdirectory doesn't exist anymore and you are able '''run configure in the root folder''' of your checkout.

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first checks for depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m2 swext 
(for DEV300_m22) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is too old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the one that is in OOo's sources just is too
old. 
Actually, there is an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

If you got an error like this
<pre>
ERROR: Error 65280 occurred while making /work/ooovanillabuild/ucb/source/ucp/gvfs
</pre>
look inside the output in your shell if there are something wrong with your glib-devel version. If you see inside the messages in the shell something like this:
<pre>

/usr/include/glib-1.2/glib.h:2725:1: warning: this is the location of the previous definition
(...)
/usr/include/glib-2.0/glib/gthread.h:352:1: warning: "G_LOCK_NAME" redefined
</pre>
you have to unistall one of the glib-devel version; mostly glib-devel version 1.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

== alternative build system ==
The instructions above describes on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at Building_with_ooobuild instead.

DE/Uebersetzung 3.1

2009-01-12T20:06:16Z

Andreasma: /* Runde 2 */

{{De.OOo}}
[[Category:de.openoffice.org|Übersetzung 3.1]]

= Allgemeine Hinweise =
Diese Seite dient zur Koordination der Übersetzung für OpenOffice.org
3.1

== Etappen ==
=== Runde 1 ===
* Inhalt: Hilfe / UI
* Start (Pootle): 13.12.2008
* Start (Verteilung Übersetzung): 23.12.2008
* Abgabetermin (für Review): 02.01.2009
* Abgabetermin (Pootle): 05.01.2009

=== Runde 2 ===
* Inhalt: Hilfe / UI (?)
* Start (Pootle): 08.01.2009
* Start (Verteilung Übersetzung): 11.01.2009 (?)
* Abgabetermin (für Review): 29.01.2009
* Abgabetermin (Pootle): 02.02.2009

= Dateidownload =

Die zu übersetzenden Dateien können als komplettes zip Archiv heruntergeladen werden.

Ladet das Paket herunter, wählt eine Datei zur Übersetzung und tragt sie hier im Wiki in der unten stehende Tabelle ein. Überprüft jeweils vorher, ob die Datei nicht bereits in Bearbeitung ist. Bitte nur für Aufgaben melden, die auch bis zum Termin erledigt werden können!

Sendet die fertigen Übersetzungen an Jacqueline (jrahemipour@openoffice.org) und André (andreschnabel@openoffice.org) zum Review. Bitte sendet die Dateien, sobald sie übersetzt sind, spätestens aber bis zum angegebenen Abgabetermin für den Review.

=== Runde 1 ===
* [http://l10n.projects.ooodev.org/3.1/HC2/round1/work_xlf.zip work_xlf.zip (93 kb)]

=== Runde 2 ===
* [http://l10n.projects.ooodev.org/3.1/HC2/round2/work_xlf.zip work_xlf.zip (13 kb)]

= Aktueller Bearbeitungsstand =

Bitte hier immer den aktuellen Bearbeitungsstand eintragen! (Für die Aufwandsabschätzung: Die Segmente haben im Schnitt 15 Wörter. Ist man bereits geübt, sind etwa 1500 Wörter oder 100 Segmente in 3-4h zu schaffen.)

== Runde 1 ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! width="200" | Ordner / Datei
! Anzahl Segmente (Wörter)
! width="100" | Übersetzer
! width="100" | Reviewer
! width="100" | Status
! Bemerkungen

|-
| work_xlf/sbasic/shared.xlf
| 4 (172)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/sbasic/shared/01.xlf
| 1 (15)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/scalc/00.xlf
| 3 (3)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/scalc/01.xlf
| 68 (1468)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/scalc/04.xlf
| 50 (240)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/scalc/05.xlf
| 1 (17)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/scalc/guide.xlf
| 50 (839)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/schart/01.xlf
| 16 (290)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/schart/04.xlf
| 1 (1)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/sdraw/04.xlf
| 23 (106)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/sdraw/guide.xlf
| 9 (93)
| thackert
| andreschnabel
| ok
|

|-
| work_xlf/shared/00.xlf
| 48 (355)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/shared/01.xlf
| 165 (1795)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/shared/02.xlf
| 65 (997)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/shared/04.xlf
| 64 (401)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/shared/05.xlf
| 7 (126)
| thackert
| andreschnabel
| ok
|

|-
| work_xlf/shared/autopi.xlf
| 3 (72)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/shared/explorer/database.xlf
| 6 (128)
| wope
| andreschnabel
| ok
|

|-
| work_xlf/shared/guide.xlf
| 119 (2493)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/shared/optionen.xlf
| 20 (580)
|
|
| offen
|

|-
| work_xlf/simpress.xlf
| 1 (48)
| thackert
| andreschnabel
| ok
|

|-
| work_xlf/simpress/01.xlf
| 46 (513)
| thackert
| andreschnabel
| ok
|

|-
| work_xlf/simpress/02.xlf
| 88 (1634)
|
|
| offen
|

|-
| work_xlf/simpress/04.xlf
| 7 (27)
| thackert
| andreschnabel
| ok
|

|-
| work_xlf/simpress/guide.xlf
| 40 (786)
|
|
| offen
|

|-
| work_xlf/swriter.xlf
| 7 (101)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/swriter/00.xlf
| 10 (46)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/swriter/01.xlf
| 42 (739)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/swriter/04.xlf
| 21 (97)
| gghh
| andreschnabel
| ok
|

|-
| work_xlf/swriter/guide.xlf
| 48 (1020)
| gghh
| andreschnabel
| ok
|

|}

== Runde 2 ==

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! width="200" | Ordner / Datei
! Anzahl Segmente (Wörter)
! width="100" | Übersetzer
! width="100" | Reviewer
! width="100" | Status
! Bemerkungen

|-
| work_xlf/schart/00.xlf
| 2 (16)
|
|
| offen
|

|-
| work_xlf/schart/01.xlf
| 20 (104)
|
|
| offen
|

|-
| work_xlf/shared/optionen.xlf
| 22 (613)
| wope
|
| in Arbeit
|

|-
| work_xlf/simpress/02.xlf
| 88 (1634)
|
|
| offen
|

|-
| work_xlf/simpress/guide.xlf
| 40 (786)
| andreasma
|
| in Arbeit
|

|-
| work_xlf/swriter/00.xlf
| 16 (70)
|
|
| offen
|

|-
| work_xlf/swriter/01.xlf
| 7 (87)
|
|
| offen
|

|}

= Hilfsmittel und wichtige Links zur Übersetzung =

== Open Translation Editor ==
Für die Übersetzung der Dateien ist ein modifizierter Open Translation Editor erforderlich. Download, Installationshinweise und Benutzerhandbuch gibt es hier:
* [ftp://ftp.ooodev.org/pub/l10n/tools/ote-light-1.2.7.1.zip Modifizierter OTE (light)] 3,3MB - ohne integrierte Rechtschreibprüfung - unter Linux wird aspell des Systems verwendet
* [ftp://ftp.ooodev.org/pub/l10n/tools/ote-heavy-1.2.7.1.zip Modifizierter OTE (full)] 26MB mit integrierter Rechtschreibprüfung und Wörterbüchern

* [ftp://ftp.ooodev.org/pub/l10n/tools/ote-README.txt ReadMe] Kurzinfo zum OTE

* [ftp://ftp.ooodev.org/pub/l10n/tools/TransEditor-1.2.7.4.jar TransEditor-1.2.7.4.jar] Update 3 für den OTE ([ftp://ftp.ooodev.org/pub/l10n/tools/OTE-README-1.2.7.4 Readme])

== Translation Memory ==

Ein aktuelles Translation Memory kann man [http://l10n.projects.ooodev.org/tools/ooo_de_glossary.tmx hier] herunterladen:
* http://l10n.projects.ooodev.org/tools/ooo_de_glossary.tmx
Das gleiche als ods-Datei (zum schnellen durchsuchen außerhalb OTE):
* http://l10n.projects.ooodev.org/tools/ooo_de_glossary.ods

Zur Verwendung im Open Translation Editor:
* Die Datei herunterladen und entpacken.
* Danach den Editor starten und zunächst keine Datei öffnen.
* Extras - Mini-TM pflegen wählen
* Aus TXM importieren... wählen und die entpackte Datei importieren (vorhandene Daten werden überschrieben)

Werden anschließend Texte übersetzt, versucht der Editor Übereinstimmungen im TM zu finden und bietet diese im unteren Fensterbereich an.

== Pootle ==

In Pootle können die jeweils aktuellen Übersetzungen der Hilfe und der UI eingesehen / gesucht werden.
* [http://pootle.sunvirtuallab.com/ Pootle]
* [http://pootle.sunvirtuallab.com/de/xliff_ui/ Deutsche UI in Pootle]
* [http://pootle.sunvirtuallab.com/de/xliff_help/ Deutsche Hilfe in Pootle]

== Modifikation der Hilfe ==
Viele der Absätze sind ohne den Gesamtzusammenhang in der Online-Hilfe schwer zu übersetzen. Unter Ansicht - Quellkontext kann man sich im Open Translation Editor die Help-ID des markierten Segments anzeigen lassen, sofern sie vorhanden ist. Ist für das Segment kein Quellkontext hinterlegt, so gibt es jetzt die Möglichkeit in einer Textbox oberhalb der Statusleiste sich zumindest die Seite, wo der Text erscheint als auch die dazugehörende hd_id anzusehen.
Die betreffende Stelle in der Online-Hilfe findet man, wenn man die Hilfe wie in Issue 56321 modifiziert:
* Modifikation der Hilfe zum einfachen Auffinden der relevanten Passagen [http://qa.openoffice.org/issues/show_bug.cgi?id=56321 Issue 56321]

== Style-Guide ==
Der Style-Guide für die deutsche Lokalisierung ist nun verfügbar. Dort sind sprachliche Gestaltungsrichtlinien beschrieben.
* [http://de.openoffice.org/files/documents/66/3982/file_3982.dat/Style%20Guide%20German.pdf Style Guide (218 kb)]

== Localisation Guide ==
Zum allgemeinen Aufbau der Online-Hilfe und den einzelnen Bestandteilen der Hilfe-Segmente gibt es eine Dokumentation, die einiges an Hintergrundinformationen liefert. Hier erhält man unter anderem Beschreibungen über die verschiedenen XML-Elemente und Attribute wie ''bookmark_value'' oder ''caseinline'':
* [http://documentation.openoffice.org/online_help/localization/LocalisationguideOOo2.pdf Localisation Guide (302 kb)]

= Allgemeine Anmerkungen zu den Übersetzungen =

* '''Englischer Text in der Zielspache für ein Segment:''' Neu zu übersetzende Segmente enthalten zunächst den (englischen) Originaltext als "Übersetzung".
* '''Deutscher Text in der Zielspache für ein Segment:''' Diese Segmente waren bereits übersetzt, der (englische) Originaltext wurde aber geändert. Hier ist sehr genau zu prüfen, ob es Abweichungen in Tags (Links) gibt, oder ob Teilsätze hinzugefügt bzw.entfernt wurden.
* '''Nie mehr übersetzen als in der source language angegeben ist:''' Die Schwierigkeit bei dieser Art von Übersetzungen ist sicherlich nicht die Übersetzung selbst. Durch die besonderen Umstände, dass OpenOffice.org in vielen Sprachen gepflegt werden muss und für den Übersetzer oftmals der Zusammenhang zwischen den einzelnen Text-Segmenten nicht ersichtlich ist, machen es notwendig, möglichst genau am Original zu bleiben. Das heißt, auch wenn eine andere Formulierung oder ein zusätzlicher Satz klarer erscheint: Es darf wirklich nur das übersetzt werden, was auch in der source language angegeben ist.
* '''Tags unverändert lassen:''' In vielen Segmenten sind sogenannte Tags enthalten, die für die Verlinkung innerhalb der Hilfe, für das Einfügen von Bildern oder für das Hervorheben einzelner Textstellen notwendig sind. Lasst diese Tags einfach unverändert. Im OTE gibt es eine "Tag protection", die ohnehin dafür sorgen soll, dass hier nichts schief geht.
*'''Dateinamen unverändert lassen:''' Um die Dateien später wieder korrekt zusammenfügen zu können, dürfen die Dateinamen nicht geändert werden. Gebt bei der Rücksendung bitte den gesamten Pfad (zum Beispiel scalc\01.xlf) an, da viele der Dateien gleich benannt sind und sonst eine spätere Zuordnung sehr aufwändig ist.
* '''Nicht zu übersetzende Segmente:''' Bei Text-Segmenten, die nicht übersetzt werden müssen, weil englisch und deutsch identisch sind (zum Beispiel "Format"), bitte trotzdem das "übersetzt"-Kennzeichen setzen (Rechtsklick in der target language auf das entsprechende Segment und dann "Mark segment as translated").
* '''Kommentar-Funktion:''' Wenn ihr euch bei einer Übersetzung unsicher seid oder eine Bemerkung dazu loswerden wollt, dann nutzt die Kommentar-Funktion des OTE: Edit - Comment on Segment - Add comment. Dieser Kommentar kann in deutsch eingegeben werden, da er nur von den Reviewern des de-Projekts gelesen wird (Kommentare entfallen bei der Rückkonvertierung).
* '''Rechtschreibprüfung:''' Der OTE hat eine integrierte Rechtschreibprüfung. Bitte nutzt diese, um eventuelle Tippfehler oder Buchstabendreher aufzuspüren. Das erleichtert dem Reviewer die Arbeit ungemein.
*'''Zugehörige Hilfe-Seite aufrufen:''' Oft ist es hilfreich, ein Text-Segment im Gesamt-Zusammenhang zu betrachten. Wenn ihr die Online-Hilfe (wie oben beschrieben) modifiziert habt, sind die Textstellen recht einfach auffindbar: Markiert das betreffende Text-Segment und schaut unter View - Source Text, wie die Hilfe-Datei heißt und welche ID das Segment hat, z.B. source\text\scalc\main0202.xhp, par_id192266. Öffnet nun die modifizierte Hilfe. Unter "Inhalte" gibt es einen Eintrag "All files for testing". Darunter findet man im Grunde die gleiche Ordnerstruktur wie bei den zu übersetzenden Hilfe-Dateien (nur ist in der Regel viel weniger zu übersetzen, als es tatsächlich gibt). Dort geht man zum Beispiel in den Unterordner source\text\scalc\ und ruft die Datei main0202.xhp auf. Manche Dateien befinden sich in den Unterordnern 01 etc, das sind die aus der Hilfe-Datei 01.po.xlz usw. Rechts wird dann die entsprechende Hilfeseite angezeigt. Über die Suchen-Funktion kann man schnell die entsprechende Help-ID finden.
* '''Style-Guide berücksichtigen:''' Bitte nehmt euch die Zeit und schaut euch den [http://de.openoffice.org/files/documents/66/3982/file_3982.dat/Style%20Guide%20German.pdf Style Guide] an. Damit bekommt ihr ein ganz gutes Gefühl für den Stil, der in der Online-Hilfe verwendet wird. Die Übersetzungen sollen später wie "aus einem Guss" wirken, also sollte man möglichst einheitliche Formulierungen verwenden.
* '''Die richtigen Fachbegriffe verwenden:''' Nicht immer ist eine exakte Übersetzung richtig, nämlich immer dann, wenn in der deutschen Lokalisierung ein anderer Fachbegriff verwendet wird (zum Beispiel ist das englische "Orphan control" keine "Waisen Kontrolle", sondern die "Schusterjungenregelung". Sollte Begriffe könnt ihr im Glossar nachschlagen. Wenn ihr euch nicht sicher seid oder der betreffende Begriff im Glossar fehlt, versucht die Stelle im Programm zu finden und verwendet den Begriff, den ihr in der Oberfläche seht. Auch hier wieder: Im Zweifelsfalle die Stelle kommentieren oder einfach auf der Mailingliste nachfragen.
* '''Fehler in der source language:''' Solltet ihr einen Fehler in der source language finden, dann genügt es nicht, dieses Text-Segment richtig zu übersetzen. Für solche Fälle sollte ein Issue aufgegeben werden. Im Zweifelsfalle wieder auf der Liste melden.

DE/3.0.1 Release Test

2009-01-02T12:57:58Z

Andreasma: /* Testmatrix */

[[Category:de.openoffice.org|Release Test 3.0.1]]
Diese Seite dient der Koordination der Release-Tests der deutschsprachigen Version 3.0.1.
Die Tests sollen der Freigabe der deutschsprachigen Pakete von OpenOffice.org 3.0.1 dienen.

Der Freigabetest wird anhand des Release-Sanity Scenarios im TCM durchgeführt.
Zum Test werden die regulären RC's für die jeweilige Plattform verwendet. Dies ist diesmal die Version 3.0.1 RC 1 (OOO300_m14).

==Liste der Plattformen: ==

[http://qatrack.services.openoffice.org/ QaTrack] (alle Plattformen)

* SUN-Builds
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86 deb]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86_64 deb]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Windows ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Windows mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86 RPM ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86 RPM mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86_64 RPM ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Linux x86_64 RPM mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ SolarisSparc ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Solaris Sparc mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Solaris X86 ohne JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ Solaris X86 mit JRE]
** [http://ftp-1.gwdg.de/pub/openoffice/extended/ MacOSX/Intel]

* Pavels Build
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/OOO300/OOO300_m14/ Linux x86 deb]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/OOO300/OOO300_m14/ Linux x86 rpm]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/OOO300/OOO300_m14/ Linux x86_64 deb]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/OOO300/OOO300_m14/ Linux x86_64 rpm]
** [http://ftp.linux.cz/pub/localization/OpenOffice.org/devel/OOO300/OOO300_m14/ Windows]

* Mahos builds
** [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ Mac OS X x86 (Intel)]
** [ftp://ooopackages.good-day.net/pub/OpenOffice.org/MacOSX/ Mac OS X PPC]

* [ftp://ooopackages.good-day.net/pub/OpenOffice.org/FreeBSD/ Jacks builds] FreeBSD 5 und 6 - Verzeichnisse .

Werden Fehler oder Probleme aufgedeckt, sollten unbedingt entsprechende Issues gesucht und ggf. neu erfasst werden. Diese sollten dann im TCM bei dem Testfall hinterlegt werden, bei dem das Problem entdeckt wurde.
Bei Problemen unbedingt auf der QA Liste melden. Gefundene Fehler sollten im Zweifelsfall auch dort diskutiert werden.
Bei Problemen mit Issuezilla (z.B. ungenügende Kenntnisse beim Aufgeben von Issues) ebenfalls auf der QA-Liste melden. Dort erhaltet Ihr Hilfe zur Erstellung und Bearbeitung der Issues.

Um bei den Tests mithelfen zu können, wird ein TCM-Account benötigt. Bei Interesse wendet euch bitte an qa@de.openoffice.org

= Informationen und Links =

* [http://de.openoffice.org/about-ooo/about_tcm.html Über TCM]
* [http://www.sunvirtuallab.com/tcm2/opensource/tcm_login.cgi?tcm_config=newooo TCM Login]

= Testmatrix =
wer macht welche Tests - es werden folgende Markierungen verwendet:

'''Bitte gebt an, ob ihr die Version mit oder ohne JRE installiert'''

* grau - Test noch nicht zugeteilt
* normal - zum Testen eingeteilt / Test in Arbeit
* ''kursiv'' - Test mit unkritischen Fehlern bestanden
* '''fett''' - Test ohne Fehler bestanden
* '''''fett-kursiv''''' - Test mit kritischen Fehlern fehlgeschlagen

{| border="1" cellpadding="2"
|-
! Plattform
! Tester !! Ergebnis
|-
! Mac( PPC)
|| ||
|-
! Mac( x86)
||torwart||
|-
! PowerPC(Linux)
|| ||
|-
! Sparc(Solaris10)
|| ||
|-
! Sparc(Solaris8)
|| ||
|-
! Sparc(Solaris9)
|| ||
|-
! x86(FreeBSD5.3)
|| ||
|-
! x86(Linux/deb mit/ohne KDE)
|| ||
|-
! x86(Linux/RPM mit/ohne JRE)
|| andreasma ||
|-
! x86_64 (Linux/deb mit/ohne KDE)
|| ||
|-
! x86_64(Linux rpm mit/ohne JRE)
||wope ||'''''1 Fehler, werd das noch analysieren'''''
|-
! x86(Solaris10)
|| ||
|-
! x86(Solaris10jre)
|| ||
|-
! X86(Solaris9)
|| ||
|-
! x86(Win2003 mit/ohne JRE)
|| ||
|-
! x86(Win2K mit/ohne JRE)
|| ||
|-
! x86(WinXP mit/ohne JRE)
|| wope || '''ok mit JRE'''
|-
! x86(WinVista mit/ohne JRE)
|| ||
|}

= Zusatzaufgaben =

== Issues verifizieren ==

Folgende Issues sind für OOo 3.0.1 geplant, aber noch nicht geschlossen. Diese sollten aufgearbeitet werden:

* [http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&target_milestone=OOo+3.0.1&Submit+query=Submit+query zu verifizierende Issues]

Vorgehen:
* einen Issue hernehmen (am besten, einen, mit dem man bereits zu tun hatte)
* prüfen, ob er tatsächlich gefixt ist ('''nur Issues bearbeiten, bei denen man sicher ist, das Problem zu verstehen''')
* wenn ja -> Status auf "Closed" wechseln (Mark Issue as Closed)
* wenn nein -> Issue wieder öffnen (reopen issue) und target auf 3.x ändern
* jeweils einen Kommentar hinterlassen, mit welcher Version (RC x) geprüft wurde und welche Probleme evtl. noch beobachtet wurden

Sonst keine Änderungen vornehmen .. auch keine Diskussionen, dass man den Fehler lieber anders gefixt haben möchte, oder dass es im Umfeld noch weitere Probleme gibt. Sollte das der Fall sein, einen neuen Issue aufgeben.

Module Build Order

2008-12-01T18:42:37Z

Andreasma:

OpenOffice.org consists of several module directories. They need to be built in a certain order in order to satisfy dependencies.

solenv
boost
stlport
soltools
external
expat
zlib
libxml2
libxslt
xml2cmp
sal
salhelper
vos
icu
moz
openssl
sandbox
berkeleydb
cosv
hyphen
python
redland
MathMLDTD
afms
agg
apple_remote
beanshell
cppunit
testshl2
curl
epm
extras
fondu
hsqldb
hunspell
icc
jpeg
libtextcat
libwpd
libxmlsec
lpsolve
lucene
msfontextract
neon
np_sdk
o3tl
psprint_config
rhino
sane
stax
saxon
store
registry
idlc
udkapi
offapi
codemaker
offuh
cppu
cppuhelper
rdbmaker
ucbhelper
comphelper
basegfx
ridljar
jvmaccess
jurt
bridges
cpputools
jvmfwk
stoc
i18nutil
io
remotebridges
sax
ucb
animations
unodevtools
embedserv
eventattacher
hwpfilter
oovbaapi
package
regexp
i18npool
tools
unotools
transex3
cli_ure
unoil
javaunohelper
sot
configmgr
fileaccess
officecfg
setup_native
rsc
xmlscript
oox
psprint
pyuno
qadevOOo
readlicense_oo
sysui
UnoControls
bean
dtrans
idl
sccomp
scp2
testtools
udm
autodoc
odk
unixODBC
unoxml
ure
vigra
basebmp
vcl
toolkit
svtools
goodies
uui
xmloff
canvas
connectivity
cppcanvas
fpicker
framework
xmlhelp
accessibility
embeddedobj
helpcontent2
padmin
scaddins
shell
sj2
basic
sfx2
avmedia
linguistic
lingucomponent
slideshow
automation
binfilter
dictionaries
drawinglayer
svx
basctl
chart2
dbaccess
desktop
extensions
filter
forms
sc
scripting
sd
sdext
starmath
wizards
writerfilter
writerperfect
sw
xmerge
xmlsecurity
postprocess
packimages
instsetoo_native

Module Build Order

2008-12-01T18:41:39Z

Andreasma:

OpenOffice.org consists of several module directories. They need to be built in a certain order in order to satisfy dependencies.

solenv
boost
stlport
soltools
external
expat
zlib
libxml2
libxslt
xml2cmp
sal
salhelper
vos
icu
moz
openssl
sandbox
berkeleydb
cosv
hyphen
python
redland
MathMLDTD
afms
agg
apple_remote
beanshell
cppunit
testshl2
curl
epm
extras
fondu
hsqldb
hunspell
icc
jpeg
libtextcat
libwpd
libxmlsec
lpsolve
lucene
msfontextract
neon
np_sdk
o3tl
psprint_config
rhino
sane
stax
saxon
store
registry
idlc
udkapi
offapi
codemaker
offuh
cppu
cppuhelper
rdbmaker
ucbhelper
comphelper
basegfx
ridljar
jvmaccess
jurt
bridges
cpputools
jvmfwk
stoc
i18nutil
io
remotebridges
sax
ucb
animations
unodevtools
embedserv
eventattacher
hwpfilter
oovbaapi
package
regexp
i18npool
tools
unotools
transex3
cli_ure
unoil
javaunohelper
sot
configmgr
fileaccess
officecfg
setup_native
rsc
xmlscript
oox
psprint
pyuno
qadevOOo
readlicense_oo
sysui
UnoControls
bean
dtrans
idl
sccomp
scp2
testtools
udm
autodoc
odk
unixODBC
unoxml
ure
vigra
basebmp
vcl
toolkit
svtools
goodies
uui
xmloff
canvas
connectivity
cppcanvas
fpicker
framework
xmlhelp
accessibility
embeddedobj
helpcontent2
padmin
scaddins
shell
sj2
basic
sfx2
avmedia
linguistic
lingucomponent
slideshow
automation
(binfilter)
dictionaries
drawinglayer
svx
basctl
chart2
dbaccess
desktop
extensions
filter
forms
sc
scripting
sd
sdext
starmath
wizards
writerfilter
writerperfect
sw
xmerge
xmlsecurity
postprocess
packimages
instsetoo_native

OOoCon 2008 Who Where When

2008-10-27T21:39:09Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight. Low flying duration possible (9-10 hours).

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Korea, Republic of ==
'''Incheon - Beijing''':[http://www.easternair.co.kr/eastern/index.jsp Chine Eastern Airlines], '''400 EUR'''

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || dep SN8107 12:20 || arr SN8107 05:10 + BF hotel || BF hotel || BF hotel || BF hotel || BF hotel || BF hotel || BF hotel || BF hotel || dep SN8108 02:35
|-
| Cor Nouws || Amsterdam, NL || || || Dept. || KL 0897 Arr. 9:55 || hotel || hotel || hotel || hotel || hotel || KL 3810 Dept. 14:20 ||
|-
| Nakata Maho || Tokyo NRT || || || NW 029 arrive 21:40 || hotel || hotel || hotel || hotel || NW 030 08:45 || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, D || || dep KL 1874 2:55pm || arr KL 0897 9:55am + hotel || hotel || hotel || hotel || hotel || hotel || hotel|| dep AF 0125 1:45pm
|-
| Andreas || Düsseldorf, D || || || AY 051 9:55am hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40am
|-
| Kazunari Hirano || Tokyo/Narita || || || || NW0029 arr:21:40 hotel || hotel || hotel || hotel || hotel | hotel || NW0030 dep:08:45 ||
|-
| ccornell || Hamburg, DE || || || || AF 126 arr 11:50 - hotel || hotel || hotel || hotel || hotel || || ||
|-
| Andreas S. || Frankfurt, D || || || || arriving 11:50 CA932 [PEK] - hotel || hotel || hotel || hotel || hotel | hotel || hotel || departing 14:05 CA931 [PEK] ||
|-
| Carsten Driesner || Vienna, AUT || || || OS 63 arr 12:55 || hotel || hotel || hotel || hotel || hotel | hotel || hotel || OS 64 dep 14:35 ||
|-
| JiHui Choi || Incheon || || || || MU 5088, arriving 09:55 || hotel || hotel || MU 5087, departing 18:00 || || || ||
|-
|}

OOoCon 2008 Who Where When

2008-08-31T18:41:05Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, D || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm
|-
| Andreas || Düsseldorf, D || || || AY 051 9:55am || hotel || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40am
|-
|}

OOoCon 2008 Who Where When

2008-08-31T18:39:49Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, Germany || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm
|-
| Andreas || Düsseldorf, Germany || || || AY 051 9:55am || hotel || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40am
|-
|}

OOoCon 2008 Who Where When

2008-08-31T18:39:05Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, Germany || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm|
|-
| Andreas || Düsseldorf, Germany || || || AY 051 9:55am || hotel || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40am|
|-
|}

OOoCon 2008 Who Where When

2008-08-31T18:36:52Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, Germany || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm|
|-
| Andreas || Düsseldorf, Germany || || AY 051 9:55 am || hotel || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40 am|
|-
|}

OOoCon 2008 Who Where When

2008-08-31T18:36:09Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, Germany || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm|
|-
| Andreas || Düsseldorf, Germany || || || AY 051 9:55 am || hotel || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40 am|
|}

OOoCon 2008 Who Where When

2008-08-31T18:35:17Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, Germany || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm|
|-
| Andreas || Düsseldorf, Germany || || || || AY 051 9:55 am || hotel || hotel || hotel || hotel || hotel || hotel || AY 052 11:40 am|
|}

OOoCon 2008 Who Where When

2008-08-31T18:34:43Z

Andreasma: /* Overview */

[[Category:Marketing]]
[[Category:OOoCon]]
[[Category:Conferences]]

Information on who's flying when and staying where.

= Flights =

Prices are economy class, two-way, tax inclusive. Please note that this is merely an indication, no guarantee whatsoever !

== Belgium ==
'''Brussels''' National Airport (Zaventem): [http://www.snbrussels.be SNBrussels] codesharing [http://www.hnair.com HNAir], direct flight, B747, '''+/- 650 EUR'''

== Finland ==
'''Helsinki''': [http://www.finnair.com FinnAir], '''499 EUR'''

== France ==
'''Paris''': [http://www.airfrance.fr Air France], '''555 EUR'''

== Germany ==
'''Frankfurt''': [http://www.lufthansa.de Lufthansa]

'''Frankfurt''': [http://de.fly-airchina.com/de/index.html Air China] from '''554€''' Direct flight, price depends on day of flight

'''Munich, Dusseldorf, Hamburg, Frankfurt''': [http://www.emirates.com/de/german/destinations_offers/special_offers/special_fares/special_fares.aspx Emirates] '''499€''' ''(Booking until 31. August)'' stop-over Dubai 
''If you have trouble selecting the right date for booking try this link:'' [http://fly.emirates.com/IBE/SearchAvailability.aspx Emirates]

'''Munich''': also [http://www.lufthansa.de Lufthansa] nonstop, 740 €

'''Hamburg - Amsterdam - Beijing''': Via Amsterdam on KLM from '''€465.22'''. Advantage is no overnight stopover like Emirates has with travel via Dubai.

'''Hannover - Amsterdam - Beijing''': Via Amsterdam on KLM at about '''€570'''. starting 03.11.2008, returning 11.11.2008

'''Stuttgart - Amsterdam - Beijing''': KLM/AirFrance for '''580€''' for stay 02.11.2008-10.11.2008 (checked 2008-08-26). Advantage is the rather low flying time (outward: 12 hours, return: 13.5 hours). Only available at [http://www.bravofly.de BravoFly], otherwise it costs 746€ if booked directly at KLM.

== India ==

== Japan ==

== Netherlands ==
'''Schiphol''': [http://www.klm.com KLM], '''580 EUR'''

== UK ==
'''London''': [http://www.britishairways.com British Airways], '''575 EUR'''

= Overview =
{| class="wikitable sortable" border="1"
! Who !! Airport !! Nov 1 || Nov 2 !! Nov 3 !! Nov 4 !! Nov 5 !! Nov 6 !! Nov 7 !! Nov 8 !! Nov 9 !! Nov 10 !! Nov 11
|-
| S G || Brussels, BE || SN || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN || ||
|-
| Bart Hanssens || Brussels, BE || || SN8107 12:00 || hotel || hotel || hotel || hotel || hotel || hotel || hotel || hotel || SN8108 02:20
|-
| N M || Tokyo ? || || || || X || hotel || hotel || hotel || X || || ||
|-
| Jesús Corrius || Barcelona, ES || || || || || || || || || || ||
|-
| Christoph || Stuttgart, Germany || || KL 1874 2:55pm || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AF 0125 1:45pm|
|-
| Andreas || Düsseldorf, Germany || || || || AY 051 9:55 am || hotel || hotel || hotel || hotel || hotel || hotel || hotel|| AY 052 11:40 am|
|}

Education Project/Willkommen de

2008-07-03T19:22:37Z

Andreasma: /* IRC */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind und uns unterstützen wollen, tragen Sie sich bitte in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun, um uns zu helfen? ==

HABEN SIE EINEN VORSCHLAG ? WOLLEN SIE ETWAS TUN ODER ETWAS EINBRINGEN ?

Tun Sie es einfach !! ...und schauen Sie unten, was am besten zu Ihren Anforderungen passt !

== BEITRAGEN ==

Student, Professor, Entwickler ( C++ , Objective-C , C, Python, alles in Bezug auf Webseiten) ,
Sponsor oder Freiwilliger, Sie können uns sicherlich helfen. Und fühlen Sie sich willkommen im Education-Project !!

Mit uns können Sie lernen:

- wie der Quelltext für OpenOffice.org organisiert ist, so dass Sie effektiv entwickeln können

- welche Werkzeuge bei OpenOffice.org benutzt werden

- wie Sie OpenOffice.org für Ihr Betriebssystem erstellen

- wie eine neue Funktionsimplemtierung akzeptiert und eingeplant wird

- wie die QA gemanaged wird

- how the component or module you want to understand and possibly contribute to functions

- was zu tun ist, falls Sie etwas hinzufügen wollen

- was zu tun ist, wenn Sie eine Extension (Erweiterung) erstellen wollen

- how to define applications for your students adapted to OpenOffice.org

- wie man ein Haupt-Entwickler für ein OpenOffice.org-Projekt wird

Zum Schluß: wir sind daran interessiert, Kurse über OpenOffice.org zur Verfügung zu stellen. Alle Vorschläge sind willkommen!

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Diskutieren Sie mit uns!

Wir haben einen IRC-Kanal und Sie können uns dort wirklich treffen:

Server ist irc.freenode.net
Channel (Kanal) ist #education.openoffice.org

Wir sehen Sie :-)

=== REGULÄRE IRC-MEETINGS ===

Wir halten regelmäßige IRC-Meetings ab. Alle Logs sind öffentlich.

Sie können Sie hier finden : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Falls Sie teilnehmen wollen, schauen Sie bitte auf: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (kurz gefaßt ) ===

Die Haupt-Webseite : http://education.openoffice.org [1]

Das Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailinglisten : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs von früheren Education-IRC-Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education-IRC-Meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator-Projecte : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T19:20:17Z

Andreasma: /* REGULAR IRC MEETINGS */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind und uns unterstützen wollen, tragen Sie sich bitte in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun, um uns zu helfen? ==

HABEN SIE EINEN VORSCHLAG ? WOLLEN SIE ETWAS TUN ODER ETWAS EINBRINGEN ?

Tun Sie es einfach !! ...und schauen Sie unten, was am besten zu Ihren Anforderungen passt !

== BEITRAGEN ==

Student, Professor, Entwickler ( C++ , Objective-C , C, Python, alles in Bezug auf Webseiten) ,
Sponsor oder Freiwilliger, Sie können uns sicherlich helfen. Und fühlen Sie sich willkommen im Education-Project !!

Mit uns können Sie lernen:

- wie der Quelltext für OpenOffice.org organisiert ist, so dass Sie effektiv entwickeln können

- welche Werkzeuge bei OpenOffice.org benutzt werden

- wie Sie OpenOffice.org für Ihr Betriebssystem erstellen

- wie eine neue Funktionsimplemtierung akzeptiert und eingeplant wird

- wie die QA gemanaged wird

- how the component or module you want to understand and possibly contribute to functions

- was zu tun ist, falls Sie etwas hinzufügen wollen

- was zu tun ist, wenn Sie eine Extension (Erweiterung) erstellen wollen

- how to define applications for your students adapted to OpenOffice.org

- wie man ein Haupt-Entwickler für ein OpenOffice.org-Projekt wird

Zum Schluß: wir sind daran interessiert, Kurse über OpenOffice.org zur Verfügung zu stellen. Alle Vorschläge sind willkommen!

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULÄRE IRC-MEETINGS ===

Wir halten regelmäßige IRC-Meetings ab. Alle Logs sind öffentlich.

Sie können Sie hier finden : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Falls Sie teilnehmen wollen, schauen Sie bitte auf: http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (kurz gefaßt ) ===

Die Haupt-Webseite : http://education.openoffice.org [1]

Das Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailinglisten : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs von früheren Education-IRC-Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education-IRC-Meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator-Projecte : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T19:17:02Z

Andreasma: /* LINKS (summary ) */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind und uns unterstützen wollen, tragen Sie sich bitte in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun, um uns zu helfen? ==

HABEN SIE EINEN VORSCHLAG ? WOLLEN SIE ETWAS TUN ODER ETWAS EINBRINGEN ?

Tun Sie es einfach !! ...und schauen Sie unten, was am besten zu Ihren Anforderungen passt !

== BEITRAGEN ==

Student, Professor, Entwickler ( C++ , Objective-C , C, Python, alles in Bezug auf Webseiten) ,
Sponsor oder Freiwilliger, Sie können uns sicherlich helfen. Und fühlen Sie sich willkommen im Education-Project !!

Mit uns können Sie lernen:

- wie der Quelltext für OpenOffice.org organisiert ist, so dass Sie effektiv entwickeln können

- welche Werkzeuge bei OpenOffice.org benutzt werden

- wie Sie OpenOffice.org für Ihr Betriebssystem erstellen

- wie eine neue Funktionsimplemtierung akzeptiert und eingeplant wird

- wie die QA gemanaged wird

- how the component or module you want to understand and possibly contribute to functions

- was zu tun ist, falls Sie etwas hinzufügen wollen

- was zu tun ist, wenn Sie eine Extension (Erweiterung) erstellen wollen

- how to define applications for your students adapted to OpenOffice.org

- wie man ein Haupt-Entwickler für ein OpenOffice.org-Projekt wird

Zum Schluß: wir sind daran interessiert, Kurse über OpenOffice.org zur Verfügung zu stellen. Alle Vorschläge sind willkommen!

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULAR IRC MEETINGS ===

We hold regular IRC meetings, and all logs are public.

You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (kurz gefaßt ) ===

Die Haupt-Webseite : http://education.openoffice.org [1]

Das Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailinglisten : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs von früheren Education-IRC-Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education-IRC-Meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator-Projecte : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T19:11:19Z

Andreasma: /* CONTRIBUTE */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind und uns unterstützen wollen, tragen Sie sich bitte in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun, um uns zu helfen? ==

HABEN SIE EINEN VORSCHLAG ? WOLLEN SIE ETWAS TUN ODER ETWAS EINBRINGEN ?

Tun Sie es einfach !! ...und schauen Sie unten, was am besten zu Ihren Anforderungen passt !

== BEITRAGEN ==

Student, Professor, Entwickler ( C++ , Objective-C , C, Python, alles in Bezug auf Webseiten) ,
Sponsor oder Freiwilliger, Sie können uns sicherlich helfen. Und fühlen Sie sich willkommen im Education-Project !!

Mit uns können Sie lernen:

- wie der Quelltext für OpenOffice.org organisiert ist, so dass Sie effektiv entwickeln können

- welche Werkzeuge bei OpenOffice.org benutzt werden

- wie Sie OpenOffice.org für Ihr Betriebssystem erstellen

- wie eine neue Funktionsimplemtierung akzeptiert und eingeplant wird

- wie die QA gemanaged wird

- how the component or module you want to understand and possibly contribute to functions

- was zu tun ist, falls Sie etwas hinzufügen wollen

- was zu tun ist, wenn Sie eine Extension (Erweiterung) erstellen wollen

- how to define applications for your students adapted to OpenOffice.org

- wie man ein Haupt-Entwickler für ein OpenOffice.org-Projekt wird

Zum Schluß: wir sind daran interessiert, Kurse über OpenOffice.org zur Verfügung zu stellen. Alle Vorschläge sind willkommen!

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULAR IRC MEETINGS ===

We hold regular IRC meetings, and all logs are public.

You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (summary ) ===

The main website : http://education.openoffice.org [1]

The Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailing list list : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs of previous Education IRC Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education IRC meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator projects : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T18:58:09Z

Andreasma: /* Was können Sie tun um uns zu helfen? */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind und uns unterstützen wollen, tragen Sie sich bitte in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun, um uns zu helfen? ==

HABEN SIE EINEN VORSCHLAG ? WOLLEN SIE ETWAS TUN ODER ETWAS EINBRINGEN ?

Tun Sie es einfach !! ...und schauen Sie unten, was am besten zu Ihren Anforderungen passt !

== CONTRIBUTE ==

Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) ,
sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!

With us, you can learn :

- how the source code for OpenOffice.org is organized so that you can develop effectively

- which tools are used in OpenOffice.org

- how to build OpenOffice.org for your Operating System

- how a new feature implementation is accepted and scheduled

- how the QA is managed

- how the component or module you want to understand and possibly contribute to functions

- what to do if you want to add something

- what to do if you want to create an extension

- how to define applications for your students adapted to OpenOffice.org

- how to become a Domain Developer for OpenOffice.org project

Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULAR IRC MEETINGS ===

We hold regular IRC meetings, and all logs are public.

You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (summary ) ===

The main website : http://education.openoffice.org [1]

The Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailing list list : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs of previous Education IRC Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education IRC meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator projects : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T18:51:02Z

Andreasma: /* PARTNER sind non profit Organisationen */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind und uns unterstützen wollen, tragen Sie sich bitte in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun um uns zu helfen? ==

DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?

Just do it !! ...and see below what fits at the best to your needs !

== CONTRIBUTE ==

Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) ,
sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!

With us, you can learn :

- how the source code for OpenOffice.org is organized so that you can develop effectively

- which tools are used in OpenOffice.org

- how to build OpenOffice.org for your Operating System

- how a new feature implementation is accepted and scheduled

- how the QA is managed

- how the component or module you want to understand and possibly contribute to functions

- what to do if you want to add something

- what to do if you want to create an extension

- how to define applications for your students adapted to OpenOffice.org

- how to become a Domain Developer for OpenOffice.org project

Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULAR IRC MEETINGS ===

We hold regular IRC meetings, and all logs are public.

You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (summary ) ===

The main website : http://education.openoffice.org [1]

The Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailing list list : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs of previous Education IRC Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education IRC meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator projects : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T18:50:02Z

Andreasma: /* Unsere Ziele */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren. wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles, was mit Bildung zu tun hat, gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Programmcode gemeinsam schreiben : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind uns uns unterstützen wollen, bitte tragen Sie sich in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun um uns zu helfen? ==

DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?

Just do it !! ...and see below what fits at the best to your needs !

== CONTRIBUTE ==

Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) ,
sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!

With us, you can learn :

- how the source code for OpenOffice.org is organized so that you can develop effectively

- which tools are used in OpenOffice.org

- how to build OpenOffice.org for your Operating System

- how a new feature implementation is accepted and scheduled

- how the QA is managed

- how the component or module you want to understand and possibly contribute to functions

- what to do if you want to add something

- what to do if you want to create an extension

- how to define applications for your students adapted to OpenOffice.org

- how to become a Domain Developer for OpenOffice.org project

Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULAR IRC MEETINGS ===

We hold regular IRC meetings, and all logs are public.

You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (summary ) ===

The main website : http://education.openoffice.org [1]

The Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailing list list : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs of previous Education IRC Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education IRC meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator projects : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Education Project/Willkommen de

2008-07-03T18:46:38Z

Andreasma: /* Was ist das Education project ? */

Dies ist das logo für das Education Projekt:

[[Image:LaMouette-Degree_mini.jpg]]

Education (englisch) bedeutet: Unterricht, Ausbildung, Bildungswesen.

Author : Ben Bois ( ben at hooboo dot com )

== Was ist das Education project ? ==

Innerhalb von OpenOffice.org ist alles ein Projekt. Alle Projekt-Websites haben folgende URL:
http://$(project).OpenOffice.org

z.B.: http://education.openoffice.org

Momentan ist OpenOffice.Education noch kein ausgewachsenens Projekt, bis dahin bleibt noch sehr viel zu tun.

'''... wir brauchen Ihre Mithilfe !'''

== Unsere Ziele ==

'''In 3 Punkten''':

*Einen Platz für OpenOffice.org Benutzer zu schaffen, die mit Education (Ausbildung) zu tun haben: diskutieren wie man OpenOffice.org für Pädagogen einsetzten kann, wie man es anpasst etc. (alles was mit Bildung zu tun hat gehört hierher)

*Anbieten und Vorstellen von tools für den pädagogigschen Einsatz rund um OpenOffice.org

*Write code together : Wir können Ihnen alles beibringen zum Thema OpenOffice code (programmieren) und wie Sie Ihren Code einbringen.

== SPONSOREN ==

(gibt's da wen ? :-) )

== PARTNER sind non profit Organisationen ==

Wenn Sie (in einer) Schule sind uns uns unterstützen wollen, bitte tragen Sie sich in diese Liste ein:

University of Technology of Belfort Montebeliard : http://www.utbm.fr [6]

== Was können Sie tun um uns zu helfen? ==

DO YOU HAVE A SUGGESTION ? WANT TO DO OR PROPOSE SOMETHING ?

Just do it !! ...and see below what fits at the best to your needs !

== CONTRIBUTE ==

Student, Professor, Developer ( C++ , Objective-C , C, Python, everything website) ,
sponsor or volunteer, you certainly can help us, and feel welcome in Education project !!

With us, you can learn :

- how the source code for OpenOffice.org is organized so that you can develop effectively

- which tools are used in OpenOffice.org

- how to build OpenOffice.org for your Operating System

- how a new feature implementation is accepted and scheduled

- how the QA is managed

- how the component or module you want to understand and possibly contribute to functions

- what to do if you want to add something

- what to do if you want to create an extension

- how to define applications for your students adapted to OpenOffice.org

- how to become a Domain Developer for OpenOffice.org project

Last: we are interested to provide courses about OpenOffice.org. All suggestions are welcome !

== DONATE ==

FIXME ( work in progress )

== SEARCH TOOLS about EDUCATION and OpenOffice.org ==

We do provide tools using OpenOffice.org and adapted to your pedagogy.
Every time we can, we try to provide

== PROVIDE US EXPERTISE ==

Are you using OpenOffice.org in your courses/studies ? Please :

- let us know which School you represent
- what you did
- provide us pedagogical methods adapted to teaching

== Where start ? ==
=== JOIN THE PROJECT ===

Thanks to respect the steps below :

Go at http://education.openoffice.org <= exactly this site ...

If you don't have a login, create one is mandatory ( on top right)

Validate all the steps allowing to connnect yourself to the Education Project ( confirm the subscription mail and so on )

Log you in with the password you have choosen,

Click on Membership, then on Request project membership / role

Finaly, click on "Submit Request" and wait for a project Lead accpect your pending request

That's it :-)

=== MAILING LISTS ===

Just subscribe to dev@education.openoffice.org (highly advised) at : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Archives are extremely important, and are usefull to retrieve something being discussed long time ago.

=== WEB ===

Fixed informations are on Education project website : [1] http://education.openoffice.org

You'll find : links for tools, links for exchange area FIXME ( add some of them )

=== WIKI ===

Alive informations stand in our wiki : [2] http://wiki.services.openoffice.org/wiki/Education_Project

Localized wiki pages :

French page :

Switzerland ( german at this time) : [3] http://wiki.services.openoffice.org/wiki/Project_EDUCATION-ch

(other ) : TODO

=== IRC ===

Discuss with us !

We have an IRC channel and you can meet us for true:

Server is irc.freenode.net
Channel is #education.openoffice.org

See you :-)

=== REGULAR IRC MEETINGS ===

We hold regular IRC meetings, and all logs are public.

You'll find them here : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

If you want to join, please have a look at : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

=== LINKS (summary ) ===

The main website : http://education.openoffice.org [1]

The Wiki : http://wiki.services.openoffice.org/wiki/Education_Project [2]

Mailing list list : http://education.openoffice.org/servlets/ProjectMailingListList [3]

Logs of previous Education IRC Meetings : http://wiki.services.openoffice.org/wiki/Previous_Education_Meetings_logs [4]

Education IRC meetings : http://wiki.services.openoffice.org/wiki/Education_IRC_meetings [5]

University of Technology of Belfort Montbeliard : http://www.utbm.fr [6]

Incubator projects : http://projects.openoffice.org/incubator.html [7]

=== EDUCATION Team ===

'''[[Education_Project/Team | Click Here to know who we are, and more]]'''

[[Category:Education]]

Building OpenOffice.org

2008-07-02T19:00:41Z

Andreasma: /* Hints */

[[Category:Development]]
[[Category:Build_System]]

These are the instructions on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first proofs the depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m2 swext 
(for DEV300_m22) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is to old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the that is in OOo's sources just is too
old. 
There are actual an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

If you got an error like this
<pre>
ERROR: Error 65280 occurred while making /work/ooovanillabuild/ucb/source/ucp/gvfs
</pre>
look inside the output in your shell if there are something wrong with your glib-devel version. If you see inside the messages in the shell something like this:
<pre>

/usr/include/glib-1.2/glib.h:2725:1: warning: this is the location of the previous definition
(...)
/usr/include/glib-2.0/glib/gthread.h:352:1: warning: "G_LOCK_NAME" redefined
</pre>
you have to unistall one of the glib-devel version; mostly glib-devel version 1.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

Building OpenOffice.org

2008-07-02T18:52:15Z

Andreasma: /* Hints */

[[Category:Development]]
[[Category:Build_System]]

These are the instructions on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first proofs the depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m2 swext 
(for DEV300_m22) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is to old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the that is in OOo's sources just is too
old. 
There are actual an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

Building OpenOffice.org

2008-06-05T21:04:39Z

Andreasma: /* Hints */

[[Category:Development]]
[[Category:Build_System]]

These are the instructions on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first proofs the depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m16 swext 
(for DEV300_m16) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is to old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the that is in OOo's sources just is too
old. 
There are actual an error about ant, if you build swext/mediawiki:
<pre>
BUILD FAILED
swext/mediawiki/build.xml:126: No supported regular expression matcher found: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpMatcher
</pre>
This error could be solved on Linux by installing a package called ant-optional or similar. There are some additional files for ant missing.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

Building OpenOffice.org

2008-06-05T19:54:59Z

Andreasma: /* Hints */

[[Category:Development]]
[[Category:Build_System]]

These are the instructions on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first proofs the depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m16 swext 
(for DEV300_m16) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter 
dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is to old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the that is in OOo's sources just is too
old.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

Building OpenOffice.org

2008-06-05T19:53:31Z

Andreasma: /* Hints */

[[Category:Development]]
[[Category:Build_System]]

These are the instructions on how to build "vanilla" (or "up-stream") OpenOffice.org. Vanilla means: without tools like ooo-build that wrap the build-process. If you're using ooo-build, have a look at [[Building_with_ooobuild]] instead.

= Compiling OpenOffice.org : the practice =
== Getting the sources ==
To not make these instructions longer than necessary, there is a dedicated page on [[Getting_It | how to get the source]].

== Dependencies ==
Of course you need to have some development libraries installed to build OpenOffice.org.
The configure script will complain if something is missing.
Until this guide lists the prerequisites, please have a look at http://tools.openoffice.org/

==Different Platforms==
Some information for specific platforms is provided at [http://tools.openoffice.org#Build tools].

Also for Mac OS X see [[AquaBuild]] ( experimental Aqua version of OpenOffice.org) or [[MacOSXBuildInstructions]] ( X11 version ), for GNU/Linux Sparc see [[GNULinuxSparcPorting]] and for Windows see [[Windows]].

= Building a Milestone =
== Running configure ==
The first step after getting the sources (and hopefully all prerequisites) is to run configure:

<pre>
cd <SRC_ROOT>
cd config_office
./configure
</pre>

You will most likely have to tell configure where it finds some packages such as ant or tell it what java to use. Use
<pre>
./configure --help
</pre>
to get a list of valid options that you can use.

If you forgot to install some dependencies, the configure will remind you
which one are lacking.

Special hint related to ant: Make sure to use an absolute path.

== Bootstrapping ==
When configure ran fine (i.e. it did finish without any error or warnings), you can continue the build.
Configure creates an environment file that you need to read into your shell.
If you run bash, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set.sh
</pre>
If you run a tcsh or similar, use
<pre>
cd <SRC_ROOT>
source LinuxX86Env.Set
rehash
</pre>

Note: the environment script filename might be different on a different architecture. Replace 'X86' by what is appropriate. Also note that on older version it is 'Intel' and not 'X86'.

The last step before the real build is to build the buildtools that OOo uses. To do so, simply run
<pre>
./bootstrap
</pre>
in <SRC_ROOT>

== Starting the real build ==
Now it is time for the real build
Just type
<pre>
dmake
</pre>
in <SRC_ROOT> and then relax.
Building OOo takes some time (approx 10-12 hours on standard desktop PC) so you can do other things in the meantime.
==== Hints ====
dmake first proofs the depencies of the modules. If you have a fresh checkout you could get some errors:
<pre>
Fetching dependencies for module swext from solver... failed...
Fetching from CVS... failed

WARNING! Project(s):
swext

not found and couldn't be built. Dependencies on that module(s)
ignored. Maybe you should correct build
dmake: Error code 1, while making 'check_modules'
</pre>
You have to checkout the module swext by i.e.: 
cvs co -r DEV300_m16 swext 
(for DEV300_m16) 
There are also failing depencies for modules apache-commons and tomcat. Check them out in the same way as swext above. 
If you get the following error or something similar:
<pre>
Checking DLL ../unxlngi6.pro/lib/check_libeggtrayli.so ...: ERROR: /usr/lib/libcairo.so.2: undefined symbol: FT_Library_SetLcdFilter dmake: Error code 1, while making '../unxlngi6.pro/lib/libeggtrayli.so'
</pre>
your version of libcairo is to old. To solve this error install a newer version (i.e. libcairo.so.2.11.7).
When building with cairo, you almost certainly need to specify
--with-sytem-freetype, since the that is in OOo's sources just is too
old.

= Building a [[CWS]] =
In order to build a child workspace (CWS), you need to first checkout the milestone that the cws is based upon (see Getting the source above). After that, you have to update the modules included in the cws with the cvs tag of the CWS.

You can either use [[EIS]] to get information about what milestone is the base for the CWS (see the field "Milestone (current)") and what modules it includes (see the table "Modules & Files") - or you can use [http://go-oo.org/tinderbox/tags/tag-list Tinderbox's tag-list] to get this information.

Once you have collected the necessary information, you can run:

<pre>
cd <SRC_ROOT>
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs [optional cvs flags such as -z #] update -dP -r <cwstag> <module1> <module2> <moduleN>
</pre>

Where
* SRC_ROOT is the top-level directory of your milestone-checkout
* cwstag is the cvs tag of the CWS. The tag is in the form cws_<main codeline>_<name of cws>, for example cws_src680_chart2mst3

Note: If you're using cvs using the ssh-tunnel, use ssh's compression rather than cvs compression - that gives better results

For example, you can issue :

<pre>
cd src680-m172
setenv CVSROOT ":pserver:anoncvs@anoncvs.services.openoffice.org:/cvs"
cvs -z3 update -dP -r cws_src680_chart2mst3 chart2/ offuh/
</pre>

= Tips and Tricks =

Here are some tips that make your life easier or can accelerate the build

== ccache ==
If possible, it is strongly recommended to install (and configure) [http://ccache.samba.org/ ccache] - this will greatly reduce build time on subsequent builds. Allow for a big cache and lots of files for the entire OOo build tree. If you're working on several [[CWS]]s simultaneously it pays to have separate caches, and also separate caches for non-/product builds within one CWS, e.g. after having sourced the environment execute the commands

export CCACHE_DIR="${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
export CC="ccache gcc"
export CXX="ccache g++"

in bash, respectively in tcsh

setenv CCACHE_DIR "${YOUR_SOURCES}/$CWS_WORK_STAMP/.ccache_$INPATH"
ccache -M 2G -F 100000
setenv CC "ccache gcc"
setenv CXX "ccache g++"

For Windows: download from [http://artax.karlin.mff.cuni.cz/~kendy/ccache/ here], do the following:

export CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
export CCACHE_CPP2=TRUE
export CXX="guw.pl ccache cl"
# export USE_PCH= if you experience trouble with precompiled headers

in bash, respectively in 4NT:

set CCACHE_DIR="some/place/with/space"
ccache -M 2G -F 10000
set CXX=ccache cl
unset USE_PCH
# if you want to experient with precompiled headers (not recommended):
set CCACHE_CPP2=TRUE and keep USE_PCH=TRUE

See also this [http://www.nabble.com/ccache-for-MSVC-t4013218.html thread] for background info on Windows ccache specifics.

== set nodep=TRUE ==
If you set the environment variable nodep to TRUE, then dependendy information files are not created - the build finishes faster.

But only enable that on a clean build. Once you have built OOo and then made modifications, unset the variable again to be on the safe side.

== set NO_HIDS=TRUE ==
Similar to the nodep variable, this one prevents the generation of HIDs (Help IDs) that are mainly used for automated testing - if you only want to build OOo, you don't need those.

== use parallel builds ==
If you have a multiprocessor machine or similar, you can run a parallel build. There are two levels of parallelism - one operating on makefile level, the other one on module level

=== set MAXPROCESS=<numer or processes> ===
This is the makefile-parallelism. This tells dmake how many targets it is allowed to build in parallel

=== running parallel build.pl ===
For parallelism on the module level, you have to run build from <SRC_ROOT>/instsetoo_native with the -P<number> switch, for example:
<pre>
build -P2
</pre>

== create prebuilt mozilla and use that instead of recompiling everytime ==
For the mozilla-components you have the choice to either build from mozilla sources, to use precompiled packages ([http://tools.openoffice.org/moz_prebuild/680/ the "official" ones can be obtained from tools.openoffice.org]) or to use system-mozilla (the one installed on your buildsystem, not everything might work, depending on the version you got installed)
You can easily create your own version of the prepacked binaries if you wish to do so (either because you cannot use the official ones because of mismatch of compiler version used to build them/other technical reasons or because you want to use stuff you didn't build yourself).
To do so:

* build the <code>moz</code> module from the mozilla sources (use <code>--enable-build-mozilla</code> when running configure and put the mozilla-source tarball to <code>moz/download</code>)
* in <code>moz</code> run <code>dmake zip</code> to create the zip files
* you'll find the zips in <code>{unxlngi#,wntmsci#}.pro/zipped</code>

Copy them to a location of your liking.
Now instead of using <code>--enable-build-mozilla</code>, use <code>--disable-build-mozilla</code> and copy the zips you created or downloaded to <code>moz/zipped</code> and these will be used when compiling.
This will greatly reduce build-time (you save the time that would otherwise be spent on compiling mozilla)

== saving disk space by linking to the solver only ==
Use "--dlv_switch -link" when running build to tell deliver to only link the files instead of copying them:
<pre>
build --dlv_switch -link
</pre>

== fixing epm 4 product name error ==
If you get "epm: Product names can only contain letters and numbers!" error, you must patch epm and comment out name check:
<pre>
/*
* for (i = 0; prodname[i]; i ++)
* if (!isalnum(prodname[i] & 255))
* {
* puts("epm: Product names can only contain letters and numbers!");
* usage();
* }
*/
</pre>

Apache OpenOffice Wiki - User contributions [en]

OOoCon2010Stay

OOoCon2010/Around the conference venue

DE/LinuxTag2010

DE/QA-Wochenende2010

User Experience/Improving OOo Default Settings

User Experience/Improving OOo Default Settings

DE/CeBIT2010

Conferences/FOSDEM/2010

Conferences/FOSDEM/2010

Conferences/FOSDEM/2010

Conferences/FOSDEM/2010

Conferences/FOSDEM/2010

Documentation/Dashboard/Ideastorm

Documentation/Dashboard/Project Plan

Documentation/Dashboard/CMS Evaluation

Documentation/Dashboard/CMS Evaluation

DE/QA-Wochenende2009

DE/QA-Wochenende2009

Building OpenOffice.org

DE/QA-Wochenende2009

DE/QA-Wochenende2009

Building OpenOffice.org

Building OpenOffice.org

Building OpenOffice.org

Recommended Reading

DE/Uebersetzung 3.1

DE/3.0.1 Release Test

Module Build Order

Module Build Order

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

OOoCon 2008 Who Where When

Education Project/Willkommen de

Education Project/Willkommen de

Education Project/Willkommen de

Education Project/Willkommen de

Education Project/Willkommen de

Education Project/Willkommen de

Education Project/Willkommen de

Education Project/Willkommen de

Building OpenOffice.org

Building OpenOffice.org

Building OpenOffice.org

Building OpenOffice.org

Building OpenOffice.org