<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.openoffice.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thorsten</id>
	<title>Apache OpenOffice Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.openoffice.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thorsten"/>
	<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/wiki/Special:Contributions/Thorsten"/>
	<updated>2026-11-21T04:48:41Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.14</generator>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Hackfest2010/Topics&amp;diff=186514</id>
		<title>Hackfest2010/Topics</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Hackfest2010/Topics&amp;diff=186514"/>
		<updated>2010-10-11T14:46:39Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:OpenOffice.org HackFest 2010 Topics}} &lt;br /&gt;
&lt;br /&gt;
==Concrete Hacks==&lt;br /&gt;
&lt;br /&gt;
Please add your ideas and topics you&amp;#039;d like to work on or mentor during the hackfest. Issues and/or features to be worked on should either be doable within two days, or at least could be given enough spin to be completed within a reasonable time and amount of effort after the hackfest. If available add links to the corresponding issue and possibly UX or other feature specifications.&lt;br /&gt;
&lt;br /&gt;
Note that this is not an agenda and does not involve any schedule, we&amp;#039;re &amp;quot;planning&amp;quot; more in an [http://www.unconference.net/ unConference] style, so about anything may go once the hackfest started. However, getting prepared for some tasks isn&amp;#039;t bad either..&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Module || Topic || Remarks || Issue # || Mentor || Participants&amp;lt;br&amp;gt;Interested&lt;br /&gt;
|-&lt;br /&gt;
| Calc || Fill operations should not touch filtered rows || A long outstanding issue that if solved would ease many people&amp;#039;s itches..&amp;lt;br&amp;gt; A sketch of possible behavior is available at [[Calc/Drafts/Issue_33851#Fill_cells]] and [[Calc/Drafts/Issue_33851#Fill_series]] || {{Bug|89232}} || Eike Rathke [er] || {you}&amp;lt;br&amp;gt;{and you}&amp;lt;br&amp;gt;{and you} ;-)&lt;br /&gt;
|-&lt;br /&gt;
|  ||  ||  ||  ||  || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Mentors around==&lt;br /&gt;
&lt;br /&gt;
This is a list of hackers around, that are able to cover/mentor certain subject areas in the code base - if you have specific ideas/plans, poke them if they can help you with that.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Modules || Mentor(OOo user name) || Participants&amp;lt;br&amp;gt;Interested&lt;br /&gt;
|-&lt;br /&gt;
| Calc/I18N ||  Eike Rathke [er] || {you}&amp;lt;br&amp;gt;{and you}&amp;lt;br&amp;gt;{and you} ;-)&lt;br /&gt;
|-&lt;br /&gt;
| Draw/Impress/VCL ||  Thorsten Behrens [thb] || {you}&amp;lt;br&amp;gt;{and you}&amp;lt;br&amp;gt;{and you} ;-)&lt;br /&gt;
|-&lt;br /&gt;
|  ||  ||  ||  ||  || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186375</id>
		<title>A Brief History Of OpenOffice.org</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186375"/>
		<updated>2010-10-08T08:12:15Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* 2000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[file:OOo10.png]]&lt;br /&gt;
&lt;br /&gt;
=History, Milestones and Earth Shaking Events=&lt;br /&gt;
&lt;br /&gt;
==The early years==&lt;br /&gt;
&lt;br /&gt;
1986            Marco Börries founds StarDivision, first StarWriter is developed&amp;lt;br&amp;gt;&lt;br /&gt;
1990            Development site moves to Hamburg, a crossplatform office suite is developed, and marketed as &amp;quot;StarOffice&amp;quot; - this is the oldest code that&amp;#039;s still inside OpenOffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
1999    	Sun Microsystems, Inc., buys StarDivision&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==OpenOffice.org 1.0 - Let Freedom Ring==&lt;br /&gt;
===2000===&lt;br /&gt;
2000-07-19 	OpenOffice.org announced; StarOffice 5.2 code open-sourced under LGPL/SISSL&amp;lt;br&amp;gt;&lt;br /&gt;
2000-10-13 	OpenOffice.org goes live, with the source available for download&amp;lt;br&amp;gt;&lt;br /&gt;
2000-11-24 	First port complete: PPC Linux&amp;lt;br&amp;gt;&lt;br /&gt;
2000-12 	An XML-based file-format specification is published, and used by &amp;#039;&amp;#039;default&amp;#039;&amp;#039; - the *.sxw / *.sxc / *.sxi type of files&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2001===&lt;br /&gt;
2001-02 	Integration of the new, psprint-based printing system&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Whiteboard (now Incubator) projects grow; these are community-initiated development projects&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Source code to Mac OS X port released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	First Lang (now Native-Lang) project - Francophone&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Thesaurus announced (en_US )&amp;lt;br&amp;gt;&lt;br /&gt;
2001-05 	Spell Checking integrated (MySpell)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-06 	ODK released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	First community localization - Finnish&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	Marketing (Whiteboard) project created&amp;lt;br&amp;gt;&lt;br /&gt;
2001-09 	Help system and content integrated&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	Build 638c is released (638c was a milestone release)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	One Million Downloads!&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	First anniversary&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2002===&lt;br /&gt;
2002-04 	10,000 members registered; 4.5 Million downloads&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May - Version 1.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	OpenOffice.org 1.0 announced&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	6 Million downloads, 2,000 messages posted per week&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05-07 	Mac OS X (developer) build released, adding to the list that includes all other flavors of Unix, such as FreeBSD&amp;lt;br&amp;gt;&lt;br /&gt;
2002-06-30 	OpenOffice.org grows to 55,000, adding five thousand new members per week&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July - Version 1.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-07 	Native Lang projects: Deutsch, Español, Italiano, Nederlands, Português do Brasil&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Community-sponsored development projects include: Documentation, QA, WP, Groupware, Lingucomponent&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Best Office Productivity Award (Linux Journal)&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Evolutionary Enterprise Award (Linux World Expo) (picture coming soon)&amp;lt;br&amp;gt;&lt;br /&gt;
2000-09 	SDK released, superseding the ODK&amp;lt;br&amp;gt;&lt;br /&gt;
2002-09 	XML Journal Finalist Award&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10 	New developer builds and ports: 643, Mac OS X11 Public Beta&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 8.5 Million downloads&lt;br /&gt;
* Over 70,000 registered members&lt;br /&gt;
* More than 30 projects and sub-projects, two of which, Marketing and Documentation are led by volunteer community members; the Porting Project is co-lead by a volunteer member&lt;br /&gt;
* Over one hundred developers and contributors working in all the active projects&lt;br /&gt;
&lt;br /&gt;
===2003===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;January - Version 1.0.2 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-02 	OpenOffice.org Software Development Kit released (Beta; now final)&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
March 20th - March 21st &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - University of Hamburg, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SDK 1.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-04 	OpenOffice.org 1.1 RC1 released&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039; April - Version 1.0.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-07 	OpenOffice.org Mac OS X (X11) port finalized (GM)&amp;lt;br&amp;gt;&lt;br /&gt;
2003-08 	Numerous new Native-Lang and Incubator projects&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	The OpenOffice.org Community Council Formed&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	OpenOffice.org 1.1 released&amp;lt;br&amp;gt;2004-02 	&lt;br /&gt;
2003-10 	Awards: Numerous user and editor awards&amp;lt;br&amp;gt;&lt;br /&gt;
2003-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 20 million downloads&lt;br /&gt;
* Over 107,000 registered members&lt;br /&gt;
* More than 50 projects, many led by volunteer members&lt;br /&gt;
* Sixty localizations achieved or in progress&lt;br /&gt;
* Over 270 developers and contributors&lt;br /&gt;
* More statistics&lt;br /&gt;
&lt;br /&gt;
===2004===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;April Version 1.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 1.1.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 1.1.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 22nd - 24th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Humboldt University Berlin, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 1.1.4 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2005===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 1.1.5&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 28th - 30th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Koper - Capodistria, Slovenia&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Evolution - Version 2.0 Arrives==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2006===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July  Version 2.0.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 11 - 13 2006 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Lyon, France&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adaptation - Extensions, ODF Tools==&lt;br /&gt;
===2007===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 2.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 14 the first entry at extensions.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;Auto Starter for Presentation documents&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
18th to 21st of September &amp;#039;&amp;#039;&amp;#039;OOoCon Barcelona (Catalonia, Spain)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2008===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.4.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.4.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th to 7th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Bejing China&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th The first template is made available at templates.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;1/4&amp;quot; Cartesian Graph Paper&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Maturity and Grace - &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Version 3.0 Takes the World by Storm&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October (2008) Version 3.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2009===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;August Version 3.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 3, 2009 - November 6 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Orvieto, Italy&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2010===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;February Version 3.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
August 31st - September 3rd &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Budapest Hungary&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Category:Marketing]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186374</id>
		<title>A Brief History Of OpenOffice.org</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186374"/>
		<updated>2010-10-08T08:11:53Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* 2000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[file:OOo10.png]]&lt;br /&gt;
&lt;br /&gt;
=History, Milestones and Earth Shaking Events=&lt;br /&gt;
&lt;br /&gt;
==The early years==&lt;br /&gt;
&lt;br /&gt;
1986            Marco Börries founds StarDivision, first StarWriter is developed&amp;lt;br&amp;gt;&lt;br /&gt;
1990            Development site moves to Hamburg, a crossplatform office suite is developed, and marketed as &amp;quot;StarOffice&amp;quot; - this is the oldest code that&amp;#039;s still inside OpenOffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
1999    	Sun Microsystems, Inc., buys StarDivision&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==OpenOffice.org 1.0 - Let Freedom Ring==&lt;br /&gt;
===2000===&lt;br /&gt;
2000-07-19 	OpenOffice.org announced; StarOffice 5.2 code open-sourced under LGPL/SISSL&amp;lt;br&amp;gt;&lt;br /&gt;
2000-10-13 	OpenOffice.org goes live, with the source available for download&amp;lt;br&amp;gt;&lt;br /&gt;
2000-11-24 	First port complete: PPC Linux&amp;lt;br&amp;gt;&lt;br /&gt;
2000-12 	An XML-based file-format specification is published, and used by &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;default&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; - the *.sxw / *.sxc / *.sxi type of files&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2001===&lt;br /&gt;
2001-02 	Integration of the new, psprint-based printing system&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Whiteboard (now Incubator) projects grow; these are community-initiated development projects&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Source code to Mac OS X port released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	First Lang (now Native-Lang) project - Francophone&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Thesaurus announced (en_US )&amp;lt;br&amp;gt;&lt;br /&gt;
2001-05 	Spell Checking integrated (MySpell)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-06 	ODK released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	First community localization - Finnish&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	Marketing (Whiteboard) project created&amp;lt;br&amp;gt;&lt;br /&gt;
2001-09 	Help system and content integrated&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	Build 638c is released (638c was a milestone release)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	One Million Downloads!&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	First anniversary&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2002===&lt;br /&gt;
2002-04 	10,000 members registered; 4.5 Million downloads&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May - Version 1.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	OpenOffice.org 1.0 announced&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	6 Million downloads, 2,000 messages posted per week&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05-07 	Mac OS X (developer) build released, adding to the list that includes all other flavors of Unix, such as FreeBSD&amp;lt;br&amp;gt;&lt;br /&gt;
2002-06-30 	OpenOffice.org grows to 55,000, adding five thousand new members per week&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July - Version 1.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-07 	Native Lang projects: Deutsch, Español, Italiano, Nederlands, Português do Brasil&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Community-sponsored development projects include: Documentation, QA, WP, Groupware, Lingucomponent&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Best Office Productivity Award (Linux Journal)&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Evolutionary Enterprise Award (Linux World Expo) (picture coming soon)&amp;lt;br&amp;gt;&lt;br /&gt;
2000-09 	SDK released, superseding the ODK&amp;lt;br&amp;gt;&lt;br /&gt;
2002-09 	XML Journal Finalist Award&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10 	New developer builds and ports: 643, Mac OS X11 Public Beta&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 8.5 Million downloads&lt;br /&gt;
* Over 70,000 registered members&lt;br /&gt;
* More than 30 projects and sub-projects, two of which, Marketing and Documentation are led by volunteer community members; the Porting Project is co-lead by a volunteer member&lt;br /&gt;
* Over one hundred developers and contributors working in all the active projects&lt;br /&gt;
&lt;br /&gt;
===2003===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;January - Version 1.0.2 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-02 	OpenOffice.org Software Development Kit released (Beta; now final)&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
March 20th - March 21st &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - University of Hamburg, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SDK 1.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-04 	OpenOffice.org 1.1 RC1 released&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039; April - Version 1.0.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-07 	OpenOffice.org Mac OS X (X11) port finalized (GM)&amp;lt;br&amp;gt;&lt;br /&gt;
2003-08 	Numerous new Native-Lang and Incubator projects&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	The OpenOffice.org Community Council Formed&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	OpenOffice.org 1.1 released&amp;lt;br&amp;gt;2004-02 	&lt;br /&gt;
2003-10 	Awards: Numerous user and editor awards&amp;lt;br&amp;gt;&lt;br /&gt;
2003-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 20 million downloads&lt;br /&gt;
* Over 107,000 registered members&lt;br /&gt;
* More than 50 projects, many led by volunteer members&lt;br /&gt;
* Sixty localizations achieved or in progress&lt;br /&gt;
* Over 270 developers and contributors&lt;br /&gt;
* More statistics&lt;br /&gt;
&lt;br /&gt;
===2004===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;April Version 1.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 1.1.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 1.1.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 22nd - 24th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Humboldt University Berlin, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 1.1.4 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2005===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 1.1.5&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 28th - 30th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Koper - Capodistria, Slovenia&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Evolution - Version 2.0 Arrives==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2006===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July  Version 2.0.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 11 - 13 2006 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Lyon, France&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adaptation - Extensions, ODF Tools==&lt;br /&gt;
===2007===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 2.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 14 the first entry at extensions.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;Auto Starter for Presentation documents&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
18th to 21st of September &amp;#039;&amp;#039;&amp;#039;OOoCon Barcelona (Catalonia, Spain)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2008===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.4.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.4.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th to 7th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Bejing China&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th The first template is made available at templates.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;1/4&amp;quot; Cartesian Graph Paper&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Maturity and Grace - &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Version 3.0 Takes the World by Storm&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October (2008) Version 3.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2009===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;August Version 3.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 3, 2009 - November 6 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Orvieto, Italy&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2010===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;February Version 3.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
August 31st - September 3rd &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Budapest Hungary&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Category:Marketing]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186373</id>
		<title>A Brief History Of OpenOffice.org</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186373"/>
		<updated>2010-10-08T08:10:48Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* 2000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[file:OOo10.png]]&lt;br /&gt;
&lt;br /&gt;
=History, Milestones and Earth Shaking Events=&lt;br /&gt;
&lt;br /&gt;
==The early years==&lt;br /&gt;
&lt;br /&gt;
1986            Marco Börries founds StarDivision, first StarWriter is developed&amp;lt;br&amp;gt;&lt;br /&gt;
1990            Development site moves to Hamburg, a crossplatform office suite is developed, and marketed as &amp;quot;StarOffice&amp;quot; - this is the oldest code that&amp;#039;s still inside OpenOffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
1999    	Sun Microsystems, Inc., buys StarDivision&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==OpenOffice.org 1.0 - Let Freedom Ring==&lt;br /&gt;
===2000===&lt;br /&gt;
2000-07-19 	OpenOffice.org announced; StarOffice 5.2 code open-sourced under LGPL/SISSL&amp;lt;br&amp;gt;&lt;br /&gt;
2000-10-13 	OpenOffice.org goes live, with the source available for download&amp;lt;br&amp;gt;&lt;br /&gt;
2000-11-24 	First port complete: PPC Linux&amp;lt;br&amp;gt;&lt;br /&gt;
2000-12 	XML file-format specification is published - the *.sxw / *.sxc / *.sxi type of files&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2001===&lt;br /&gt;
2001-02 	Integration of the new, psprint-based printing system&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Whiteboard (now Incubator) projects grow; these are community-initiated development projects&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Source code to Mac OS X port released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	First Lang (now Native-Lang) project - Francophone&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Thesaurus announced (en_US )&amp;lt;br&amp;gt;&lt;br /&gt;
2001-05 	Spell Checking integrated (MySpell)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-06 	ODK released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	First community localization - Finnish&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	Marketing (Whiteboard) project created&amp;lt;br&amp;gt;&lt;br /&gt;
2001-09 	Help system and content integrated&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	Build 638c is released (638c was a milestone release)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	One Million Downloads!&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	First anniversary&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2002===&lt;br /&gt;
2002-04 	10,000 members registered; 4.5 Million downloads&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May - Version 1.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	OpenOffice.org 1.0 announced&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	6 Million downloads, 2,000 messages posted per week&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05-07 	Mac OS X (developer) build released, adding to the list that includes all other flavors of Unix, such as FreeBSD&amp;lt;br&amp;gt;&lt;br /&gt;
2002-06-30 	OpenOffice.org grows to 55,000, adding five thousand new members per week&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July - Version 1.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-07 	Native Lang projects: Deutsch, Español, Italiano, Nederlands, Português do Brasil&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Community-sponsored development projects include: Documentation, QA, WP, Groupware, Lingucomponent&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Best Office Productivity Award (Linux Journal)&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Evolutionary Enterprise Award (Linux World Expo) (picture coming soon)&amp;lt;br&amp;gt;&lt;br /&gt;
2000-09 	SDK released, superseding the ODK&amp;lt;br&amp;gt;&lt;br /&gt;
2002-09 	XML Journal Finalist Award&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10 	New developer builds and ports: 643, Mac OS X11 Public Beta&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 8.5 Million downloads&lt;br /&gt;
* Over 70,000 registered members&lt;br /&gt;
* More than 30 projects and sub-projects, two of which, Marketing and Documentation are led by volunteer community members; the Porting Project is co-lead by a volunteer member&lt;br /&gt;
* Over one hundred developers and contributors working in all the active projects&lt;br /&gt;
&lt;br /&gt;
===2003===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;January - Version 1.0.2 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-02 	OpenOffice.org Software Development Kit released (Beta; now final)&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
March 20th - March 21st &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - University of Hamburg, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SDK 1.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-04 	OpenOffice.org 1.1 RC1 released&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039; April - Version 1.0.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-07 	OpenOffice.org Mac OS X (X11) port finalized (GM)&amp;lt;br&amp;gt;&lt;br /&gt;
2003-08 	Numerous new Native-Lang and Incubator projects&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	The OpenOffice.org Community Council Formed&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	OpenOffice.org 1.1 released&amp;lt;br&amp;gt;2004-02 	&lt;br /&gt;
2003-10 	Awards: Numerous user and editor awards&amp;lt;br&amp;gt;&lt;br /&gt;
2003-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 20 million downloads&lt;br /&gt;
* Over 107,000 registered members&lt;br /&gt;
* More than 50 projects, many led by volunteer members&lt;br /&gt;
* Sixty localizations achieved or in progress&lt;br /&gt;
* Over 270 developers and contributors&lt;br /&gt;
* More statistics&lt;br /&gt;
&lt;br /&gt;
===2004===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;April Version 1.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 1.1.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 1.1.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 22nd - 24th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Humboldt University Berlin, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 1.1.4 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2005===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 1.1.5&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 28th - 30th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Koper - Capodistria, Slovenia&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Evolution - Version 2.0 Arrives==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2006===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July  Version 2.0.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 11 - 13 2006 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Lyon, France&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adaptation - Extensions, ODF Tools==&lt;br /&gt;
===2007===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 2.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 14 the first entry at extensions.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;Auto Starter for Presentation documents&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
18th to 21st of September &amp;#039;&amp;#039;&amp;#039;OOoCon Barcelona (Catalonia, Spain)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2008===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.4.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.4.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th to 7th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Bejing China&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th The first template is made available at templates.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;1/4&amp;quot; Cartesian Graph Paper&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Maturity and Grace - &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Version 3.0 Takes the World by Storm&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October (2008) Version 3.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2009===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;August Version 3.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 3, 2009 - November 6 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Orvieto, Italy&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2010===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;February Version 3.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
August 31st - September 3rd &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Budapest Hungary&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Category:Marketing]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186372</id>
		<title>A Brief History Of OpenOffice.org</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186372"/>
		<updated>2010-10-08T08:09:09Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* The early years */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[file:OOo10.png]]&lt;br /&gt;
&lt;br /&gt;
=History, Milestones and Earth Shaking Events=&lt;br /&gt;
&lt;br /&gt;
==The early years==&lt;br /&gt;
&lt;br /&gt;
1986            Marco Börries founds StarDivision, first StarWriter is developed&amp;lt;br&amp;gt;&lt;br /&gt;
1990            Development site moves to Hamburg, a crossplatform office suite is developed, and marketed as &amp;quot;StarOffice&amp;quot; - this is the oldest code that&amp;#039;s still inside OpenOffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
1999    	Sun Microsystems, Inc., buys StarDivision&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==OpenOffice.org 1.0 - Let Freedom Ring==&lt;br /&gt;
===2000===&lt;br /&gt;
2000-07-19 	OpenOffice.org announced; StarOffice 5.2 code open-sourced under LGPL/SISSL&amp;lt;br&amp;gt;&lt;br /&gt;
2000-10-13 	OpenOffice.org goes live, with the source available for download&amp;lt;br&amp;gt;&lt;br /&gt;
2000-11-24 	First port complete: PPC Linux&amp;lt;br&amp;gt;&lt;br /&gt;
2000-12 	XML file-format specification&amp;lt;br&amp;gt;&lt;br /&gt;
===2001===&lt;br /&gt;
2001-02 	Integration of the new, psprint-based printing system&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Whiteboard (now Incubator) projects grow; these are community-initiated development projects&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Source code to Mac OS X port released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	First Lang (now Native-Lang) project - Francophone&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Thesaurus announced (en_US )&amp;lt;br&amp;gt;&lt;br /&gt;
2001-05 	Spell Checking integrated (MySpell)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-06 	ODK released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	First community localization - Finnish&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	Marketing (Whiteboard) project created&amp;lt;br&amp;gt;&lt;br /&gt;
2001-09 	Help system and content integrated&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	Build 638c is released (638c was a milestone release)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	One Million Downloads!&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	First anniversary&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2002===&lt;br /&gt;
2002-04 	10,000 members registered; 4.5 Million downloads&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May - Version 1.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	OpenOffice.org 1.0 announced&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	6 Million downloads, 2,000 messages posted per week&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05-07 	Mac OS X (developer) build released, adding to the list that includes all other flavors of Unix, such as FreeBSD&amp;lt;br&amp;gt;&lt;br /&gt;
2002-06-30 	OpenOffice.org grows to 55,000, adding five thousand new members per week&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July - Version 1.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-07 	Native Lang projects: Deutsch, Español, Italiano, Nederlands, Português do Brasil&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Community-sponsored development projects include: Documentation, QA, WP, Groupware, Lingucomponent&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Best Office Productivity Award (Linux Journal)&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Evolutionary Enterprise Award (Linux World Expo) (picture coming soon)&amp;lt;br&amp;gt;&lt;br /&gt;
2000-09 	SDK released, superseding the ODK&amp;lt;br&amp;gt;&lt;br /&gt;
2002-09 	XML Journal Finalist Award&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10 	New developer builds and ports: 643, Mac OS X11 Public Beta&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 8.5 Million downloads&lt;br /&gt;
* Over 70,000 registered members&lt;br /&gt;
* More than 30 projects and sub-projects, two of which, Marketing and Documentation are led by volunteer community members; the Porting Project is co-lead by a volunteer member&lt;br /&gt;
* Over one hundred developers and contributors working in all the active projects&lt;br /&gt;
&lt;br /&gt;
===2003===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;January - Version 1.0.2 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-02 	OpenOffice.org Software Development Kit released (Beta; now final)&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
March 20th - March 21st &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - University of Hamburg, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SDK 1.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-04 	OpenOffice.org 1.1 RC1 released&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039; April - Version 1.0.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-07 	OpenOffice.org Mac OS X (X11) port finalized (GM)&amp;lt;br&amp;gt;&lt;br /&gt;
2003-08 	Numerous new Native-Lang and Incubator projects&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	The OpenOffice.org Community Council Formed&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	OpenOffice.org 1.1 released&amp;lt;br&amp;gt;2004-02 	&lt;br /&gt;
2003-10 	Awards: Numerous user and editor awards&amp;lt;br&amp;gt;&lt;br /&gt;
2003-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 20 million downloads&lt;br /&gt;
* Over 107,000 registered members&lt;br /&gt;
* More than 50 projects, many led by volunteer members&lt;br /&gt;
* Sixty localizations achieved or in progress&lt;br /&gt;
* Over 270 developers and contributors&lt;br /&gt;
* More statistics&lt;br /&gt;
&lt;br /&gt;
===2004===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;April Version 1.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 1.1.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 1.1.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 22nd - 24th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Humboldt University Berlin, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 1.1.4 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2005===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 1.1.5&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 28th - 30th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Koper - Capodistria, Slovenia&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Evolution - Version 2.0 Arrives==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2006===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July  Version 2.0.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 11 - 13 2006 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Lyon, France&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adaptation - Extensions, ODF Tools==&lt;br /&gt;
===2007===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 2.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 14 the first entry at extensions.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;Auto Starter for Presentation documents&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
18th to 21st of September &amp;#039;&amp;#039;&amp;#039;OOoCon Barcelona (Catalonia, Spain)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2008===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.4.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.4.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th to 7th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Bejing China&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th The first template is made available at templates.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;1/4&amp;quot; Cartesian Graph Paper&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Maturity and Grace - &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Version 3.0 Takes the World by Storm&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October (2008) Version 3.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2009===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;August Version 3.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 3, 2009 - November 6 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Orvieto, Italy&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2010===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;February Version 3.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
August 31st - September 3rd &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Budapest Hungary&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Category:Marketing]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186371</id>
		<title>A Brief History Of OpenOffice.org</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=A_Brief_History_Of_OpenOffice.org&amp;diff=186371"/>
		<updated>2010-10-08T08:07:43Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* The early years */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[file:OOo10.png]]&lt;br /&gt;
&lt;br /&gt;
=History, Milestones and Earth Shaking Events=&lt;br /&gt;
&lt;br /&gt;
==The early years==&lt;br /&gt;
&lt;br /&gt;
1986            Marco Börries founds StarDivision, first StarWriter is developed&amp;lt;br&amp;gt;&lt;br /&gt;
1990            Development site moves to Hamburg, a crossplatform office suite is developed, and marketed as &amp;quot;StarOffice&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
1999    	Sun Microsystems, Inc., buys StarDivision&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==OpenOffice.org 1.0 - Let Freedom Ring==&lt;br /&gt;
===2000===&lt;br /&gt;
2000-07-19 	OpenOffice.org announced; StarOffice 5.2 code open-sourced under LGPL/SISSL&amp;lt;br&amp;gt;&lt;br /&gt;
2000-10-13 	OpenOffice.org goes live, with the source available for download&amp;lt;br&amp;gt;&lt;br /&gt;
2000-11-24 	First port complete: PPC Linux&amp;lt;br&amp;gt;&lt;br /&gt;
2000-12 	XML file-format specification&amp;lt;br&amp;gt;&lt;br /&gt;
===2001===&lt;br /&gt;
2001-02 	Integration of the new, psprint-based printing system&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Whiteboard (now Incubator) projects grow; these are community-initiated development projects&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Source code to Mac OS X port released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	First Lang (now Native-Lang) project - Francophone&amp;lt;br&amp;gt;&lt;br /&gt;
2001-04 	Thesaurus announced (en_US )&amp;lt;br&amp;gt;&lt;br /&gt;
2001-05 	Spell Checking integrated (MySpell)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-06 	ODK released&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	First community localization - Finnish&amp;lt;br&amp;gt;&lt;br /&gt;
2001-07 	Marketing (Whiteboard) project created&amp;lt;br&amp;gt;&lt;br /&gt;
2001-09 	Help system and content integrated&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	Build 638c is released (638c was a milestone release)&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	One Million Downloads!&amp;lt;br&amp;gt;&lt;br /&gt;
2001-10 	First anniversary&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2002===&lt;br /&gt;
2002-04 	10,000 members registered; 4.5 Million downloads&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May - Version 1.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	OpenOffice.org 1.0 announced&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05 	6 Million downloads, 2,000 messages posted per week&amp;lt;br&amp;gt;&lt;br /&gt;
2002-05-07 	Mac OS X (developer) build released, adding to the list that includes all other flavors of Unix, such as FreeBSD&amp;lt;br&amp;gt;&lt;br /&gt;
2002-06-30 	OpenOffice.org grows to 55,000, adding five thousand new members per week&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July - Version 1.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2002-07 	Native Lang projects: Deutsch, Español, Italiano, Nederlands, Português do Brasil&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Community-sponsored development projects include: Documentation, QA, WP, Groupware, Lingucomponent&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Best Office Productivity Award (Linux Journal)&amp;lt;br&amp;gt;&lt;br /&gt;
2002-08 	Evolutionary Enterprise Award (Linux World Expo) (picture coming soon)&amp;lt;br&amp;gt;&lt;br /&gt;
2000-09 	SDK released, superseding the ODK&amp;lt;br&amp;gt;&lt;br /&gt;
2002-09 	XML Journal Finalist Award&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10 	New developer builds and ports: 643, Mac OS X11 Public Beta&amp;lt;br&amp;gt;&lt;br /&gt;
2002-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 8.5 Million downloads&lt;br /&gt;
* Over 70,000 registered members&lt;br /&gt;
* More than 30 projects and sub-projects, two of which, Marketing and Documentation are led by volunteer community members; the Porting Project is co-lead by a volunteer member&lt;br /&gt;
* Over one hundred developers and contributors working in all the active projects&lt;br /&gt;
&lt;br /&gt;
===2003===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;January - Version 1.0.2 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-02 	OpenOffice.org Software Development Kit released (Beta; now final)&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
March 20th - March 21st &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - University of Hamburg, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SDK 1.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-04 	OpenOffice.org 1.1 RC1 released&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039; April - Version 1.0.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
2003-07 	OpenOffice.org Mac OS X (X11) port finalized (GM)&amp;lt;br&amp;gt;&lt;br /&gt;
2003-08 	Numerous new Native-Lang and Incubator projects&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	The OpenOffice.org Community Council Formed&amp;lt;br&amp;gt;&lt;br /&gt;
2003-09 	OpenOffice.org 1.1 released&amp;lt;br&amp;gt;2004-02 	&lt;br /&gt;
2003-10 	Awards: Numerous user and editor awards&amp;lt;br&amp;gt;&lt;br /&gt;
2003-10-13 	Facts:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* More than 20 million downloads&lt;br /&gt;
* Over 107,000 registered members&lt;br /&gt;
* More than 50 projects, many led by volunteer members&lt;br /&gt;
* Sixty localizations achieved or in progress&lt;br /&gt;
* Over 270 developers and contributors&lt;br /&gt;
* More statistics&lt;br /&gt;
&lt;br /&gt;
===2004===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;April Version 1.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 1.1.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 1.1.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 22nd - 24th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Humboldt University Berlin, Germany&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 1.1.4 &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2005===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 1.1.5&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 28th - 30th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference - Koper - Capodistria, Slovenia&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Evolution - Version 2.0 Arrives==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.0.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2006===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.0.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;July  Version 2.0.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.0.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 11 - 13 2006 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Lyon, France&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Adaptation - Extensions, ODF Tools==&lt;br /&gt;
===2007===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;September Version 2.3&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
September 14 the first entry at extensions.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;Auto Starter for Presentation documents&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
18th to 21st of September &amp;#039;&amp;#039;&amp;#039;OOoCon Barcelona (Catalonia, Spain)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;December Version 2.3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2008===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;March Version 2.4&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;June Version 2.4.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October Version 2.4.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th to 7th &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Bejing China&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 5th The first template is made available at templates.services.openoffice.org &amp;#039;&amp;#039;&amp;#039;1/4&amp;quot; Cartesian Graph Paper&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Maturity and Grace - &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;Version 3.0 Takes the World by Storm&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;==&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;October (2008) Version 3.0&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2009===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;August Version 3.1.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
November 3, 2009 - November 6 &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Orvieto, Italy&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===2010===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;February Version 3.2&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;May Version 3.2.1&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
August 31st - September 3rd &amp;#039;&amp;#039;&amp;#039;OpenOffice.org Conference Budapest Hungary&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Category:Marketing]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Hackfest2010/de&amp;diff=182198</id>
		<title>Hackfest2010/de</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Hackfest2010/de&amp;diff=182198"/>
		<updated>2010-09-07T06:21:38Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:OpenOffice.org Hackfest 2010}} &lt;br /&gt;
&lt;br /&gt;
[[Hackfest2010|For the English version of this page, please click here.]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Geschätzte OOo-Hacker, &lt;br /&gt;
&lt;br /&gt;
die OOoCon ist nun zuende, und wir stellen mal wieder fest, wie wichtig &amp;amp;amp; effektiv persönliche Treffen sind - leider haben wir davon im Jahr viel zu wenige. Um das Problem mal grundlegend zu fixen, kündigen wir hiermit das OOo HackFest Hamburg an, ein Event speziell für und mit Entwicklern, bei dem wir gemeinschaftlich am Code arbeiten wollen. &lt;br /&gt;
&lt;br /&gt;
Das OOo HackFest wird an einem Wochenende in Hamburg stattfinden (Beginn Freitagabend, mit Gelegenheit zum Kennenlernen &amp;amp;amp; Bierchen trinken, und endet am Sonntagmittag), das Programm wird in etwa folgendermaßen aussehen: &lt;br /&gt;
&lt;br /&gt;
*Freitag abend - Bierchen &amp;amp;amp; Kennenlernen &lt;br /&gt;
*Samstag morgen - Einführungsvorträge, Hands-on sessions &lt;br /&gt;
*Samstag nachmittag/nacht - gemeinschaftliches Hacken &amp;amp;amp; Bugfixen &lt;br /&gt;
*Sonntag morgen - wrap-up, review, dokumentieren&lt;br /&gt;
&lt;br /&gt;
Es wird ein limitiertes Budget für Reisekosten geben, für Übernachtungen steht ein großer (leider unbeheizter) Raum zur Verfügung, also an Isomatte &amp;amp;amp; Schlafsack denken. Für etwas komfortablere &amp;amp;amp; dennoch preiswerte Übernachtungsmöglichkeiten siehe die [[Sleeping in Hamburg|entsprechende Wikiseite]]. &lt;br /&gt;
&lt;br /&gt;
Um möglichst vielen die Teilnahme zu ermöglichen, bieten wir zwei Termine zur Auswahl an. Falls Du Interesse hast, bitte binnen einer Woche an der folgenden (unverbindlichen) Umfrage teilnehmen, damit wir den Raum entsprechend buchen können: &lt;br /&gt;
&lt;br /&gt;
http://www.doodle.com/6agr35kkqyxtnakd &lt;br /&gt;
&lt;br /&gt;
Viele Grüße, Eure HackFest-Organisierer &lt;br /&gt;
&lt;br /&gt;
[mailto:erack@openoffice.org Eike], [mailto:floeff@openoffice.org Florian] &amp;amp;amp; [mailto:thb@openoffice.org Thorsten] &lt;br /&gt;
&lt;br /&gt;
{{CCBY}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Hackfest2010&amp;diff=182197</id>
		<title>Hackfest2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Hackfest2010&amp;diff=182197"/>
		<updated>2010-09-07T06:19:48Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: added license&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:OpenOffice.org Hackfest 2010}} &lt;br /&gt;
&lt;br /&gt;
[[Hackfest2010/de|Für die deutsche Version dieser Seite klickt bitte hier.]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Dear OOo hackers, &lt;br /&gt;
&lt;br /&gt;
the OOoCon just ended, and we realize how little time we can spend together face2face each year. To properly fix that problem, we hereby announce the next event around OpenOffice.org - a hackfest in Hamburg, specifically targeted to developers, to give all of us more face time &amp;amp;amp; collectively work on the code. &lt;br /&gt;
&lt;br /&gt;
The OOo Hackfest will take place over a weekend (starting Friday night with some opportunity to socialize, and ending Sunday noon), and a tentative program could look like this: &lt;br /&gt;
&lt;br /&gt;
*Friday night - beer &amp;amp;amp; fun, warming up &lt;br /&gt;
*Saturday morning - Intro talks, Hands-on sessions &lt;br /&gt;
*Saturday afternoon/night - collective hacking, bug fixing &lt;br /&gt;
*Sunday morning - wrap-up, review, document&lt;br /&gt;
&lt;br /&gt;
For those who are in need for a bursary, we have a limited travel funding budget available. For sleeping, couchsurfing at the organizers is available. Be aware that would be in an unheated loft, so bringing a sleeping mat and a good sleeping bag would be essential. For more comfortable reasonably priced acommodations see [[Sleeping in Hamburg|the wiki page]].&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
To give as many people as possible the opportunity to participate, we&amp;#039;re offering two dates to select from. If you&amp;#039;re interested, we ask you to log your preferred date(s) within one week here: &lt;br /&gt;
&lt;br /&gt;
http://www.doodle.com/6agr35kkqyxtnakd &lt;br /&gt;
&lt;br /&gt;
Putting your name &amp;amp;amp; dates there is no obligation for coming, this is just a poll. &lt;br /&gt;
&lt;br /&gt;
Faithfully, your hackfest organizers &lt;br /&gt;
&lt;br /&gt;
[mailto:erack@openoffice.org Eike], [mailto:floeff@openoffice.org Florian] &amp;amp;amp; [mailto:thb@openoffice.org Thorsten] &lt;br /&gt;
&lt;br /&gt;
{{CCBY}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Authors_licensing_declaration&amp;diff=176626</id>
		<title>Authors licensing declaration</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Authors_licensing_declaration&amp;diff=176626"/>
		<updated>2010-07-24T10:40:41Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This site is intended to clear things regarding licensing issues using the results of this wiki on other places in OpenOffice.org project.&lt;br /&gt;
&lt;br /&gt;
Authors listed in the following section release all work ever posted in this wiki under the terms of any (single or combination) of the following licenses as long as there is no different statement on a given wiki page.&lt;br /&gt;
&lt;br /&gt;
* Public Documentation License 1.0 or later ([http://www.openoffice.org/licenses/PDL.html PDL])&lt;br /&gt;
* Creative Common Attribution-Share Alike 3.0 license ([http://creativecommons.org/licenses/by-sa/3.0/ CC-BY-SA])&lt;br /&gt;
* GNU Free Documentation License 1.2 or later ([http://www.gnu.org/licenses/fdl-1.2.html GNU FDL]) &lt;br /&gt;
* GNU Lesser General Public License 3 or later ([http://www.gnu.org/licenses/lgpl.html GNU LGPL])&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
** Friedrich Strohmaier [[User:FriedrichStrohmaier|FriedrichStrohmaier]]&amp;lt;BR&amp;gt;&lt;br /&gt;
** Edgar Kuchelmeister [[User:Ede|Edgar Kuchelmeister]]&amp;lt;br&amp;gt;&lt;br /&gt;
** Thomas Hackert [[User:Thackert|Thomas Hackert]]&amp;lt;br&amp;gt;&lt;br /&gt;
** Erich Christian [[User:Epix|Erich Christian]]&amp;lt;br&amp;gt;&lt;br /&gt;
** Sigrid Kronenberger [[User:eskroni|Sigrid Kronenberger]]&amp;lt;br&amp;gt;&lt;br /&gt;
** Stefan Weigel [[User:Stefanw|Stefan Weigel]] 08:15, 10 March 2009 (UTC)&lt;br /&gt;
** Carsten Klein [[User:CarstenKlein|Carsten Klein]] (Releasing under the GNU Free Documentation License 1.2 or later, and the Creative Common Attribution-Share Alike 3.0 license)&lt;br /&gt;
** NAKATA Maho (中田真秀) [[User:Maho|NAKATA Maho]] 16:50, 18 April 2009 (JST)&lt;br /&gt;
** PARET Matthieu [[User:Matt1|Matt1]]&lt;br /&gt;
** Thorsten Behrens [[User:Thorsten|Thorsten Behrens]]&lt;br /&gt;
&lt;br /&gt;
[[Category:License]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=User:Thorsten&amp;diff=176625</id>
		<title>User:Thorsten</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=User:Thorsten&amp;diff=176625"/>
		<updated>2010-07-24T10:39:34Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Full Name: Thorsten Behrens&lt;br /&gt;
&lt;br /&gt;
Occupation: OOo hacker&lt;br /&gt;
&lt;br /&gt;
GSL project co-lead&lt;br /&gt;
&lt;br /&gt;
[mailto:thb@openoffice.org thb@openoffice.org]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=User:Thorsten&amp;diff=176624</id>
		<title>User:Thorsten</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=User:Thorsten&amp;diff=176624"/>
		<updated>2010-07-24T10:38:59Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: Created page with &amp;#039;Full Name: Thorsten Behrens Occupation: OOo hacker GSL project co-lead&amp;#039;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Full Name: Thorsten Behrens&lt;br /&gt;
Occupation: OOo hacker&lt;br /&gt;
GSL project co-lead&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/Projektwochenende2010&amp;diff=176619</id>
		<title>DE/Projektwochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/Projektwochenende2010&amp;diff=176619"/>
		<updated>2010-07-24T08:42:59Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Teilnehmer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:OpenOffice.org Projektwochenende 2010}} &lt;br /&gt;
&lt;br /&gt;
= Kurzüberblick  =&lt;br /&gt;
&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wann?&amp;#039;&amp;#039;&amp;#039; Freitagabend, &amp;#039;&amp;#039;&amp;#039;23. Juli&amp;#039;&amp;#039;&amp;#039; bis Sonntagmittag, &amp;#039;&amp;#039;&amp;#039;25. Juli&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
*&amp;lt;u&amp;gt;&amp;#039;&amp;#039;&amp;#039;Der Anmeldeschluss ist bereits vorüber!&amp;amp;nbsp;Wer sich jetzt noch anmelden möchte, bitte nur per E-Mail an [mailto:floeff@openoffice.org Florian Effenberger] - freie Plätze können nicht mehr garantiert werden!&amp;#039;&amp;#039;&amp;#039;&amp;lt;/u&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wo?&amp;#039;&amp;#039;&amp;#039; In der [http://www.fhvr-aiv.de Fachhochschule für öffentliche Verwaltung und Rechtspflege] &amp;#039;&amp;#039;&amp;#039;in Hof&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wieviel?&amp;#039;&amp;#039;&amp;#039; Die Übernachtungskosten werden voraussichtlich vom Verein [http://www.ooodev.org OpenOffice.org Deutschland e.V.] übernommen. Für Anfahrt und Verpflegung muss jeder selbst aufkommen. &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wieviele?&amp;#039;&amp;#039;&amp;#039; Insgesamt können wir &amp;#039;&amp;#039;&amp;#039;25-30&amp;#039;&amp;#039;&amp;#039; Personen in &amp;#039;&amp;#039;&amp;#039;Einzelzimmern mit Dusche und WC&amp;#039;&amp;#039;&amp;#039; direkt auf dem Campus unterbringen &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wer?&amp;#039;&amp;#039;&amp;#039; Teilnehmen können sowohl &amp;#039;&amp;#039;&amp;#039;&amp;quot;alte Hasen&amp;quot;&amp;#039;&amp;#039;&amp;#039; im Projekt, die ihr Wissen weitergeben wollen, als auch im Besonderen &amp;#039;&amp;#039;&amp;#039;Neulinge, die gerne ein bisschen mehr über das Projekt erfahren würden&amp;#039;&amp;#039;&amp;#039;, um sich selbst dort einzubringen. Wir möchten insbesondere diejenigen zur Anmeldung ermuntern, die noch nicht so aktiv im Projekt sind, uns aber gerne kennenlernen würden! &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Was?&amp;#039;&amp;#039;&amp;#039; Das Wochenende dient zum einen zum &amp;#039;&amp;#039;&amp;#039;gegenseitigen Kennenlernen&amp;#039;&amp;#039;&amp;#039; der Projektmitglieder, zum anderen wollen wir durch Vorträge und Diskussionsrunden &amp;#039;&amp;#039;&amp;#039;künftige Vorhaben und Aktivitäten des deutschsprachigen Projektes planen&amp;#039;&amp;#039;&amp;#039;. 2007 ging es beispielsweise unter anderem um die rechtliche Stellung und Haftungsfragen von Projektmitgliedern, um geplante Marketing-Aktivitäten und Wettbewerbe, die Stellung des DE-Projektes innerhalb der internationalen OpenOffice.org-Community sowie über die Virtualisierung als Möglichkeit, OpenOffice.org, für viele Betriebssysteme zu testen. &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Veranstalter:&amp;#039;&amp;#039;&amp;#039; [http://www.ooodev.org OpenOffice.org Deutschland e.V.] &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Organisation und Ansprechpartner:&amp;#039;&amp;#039;&amp;#039; [mailto:floeff@openoffice.org Florian Effenberger] &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Internet&amp;#039;&amp;#039;&amp;#039; steht uns vor Ort nicht zur Verfügung. &amp;#039;&amp;#039;&amp;#039;Bitte ggf. UMTS-Karten fürs Notebook mitnehmen!&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Transfer vom Bahnhof&amp;#039;&amp;#039;&amp;#039; ist nach Rücksprache möglich&lt;br /&gt;
&lt;br /&gt;
= Teilnehmer  =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;&amp;#039;&amp;#039;&amp;#039;Der Anmeldeschluss ist bereits vorüber!&amp;amp;nbsp;Wer sich jetzt noch anmelden möchte, bitte nur per E-Mail an [mailto:floeff@openoffice.org Florian Effenberger] - freie Plätze können nicht mehr garantiert werden!&amp;#039;&amp;#039;&amp;#039;&amp;lt;/u&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#Geib, Gerald - [mailto:gghh@openoffice.org gghh@openoffice.org] - Freitag bis Sonntag - bitte holt uns vom Bahnhof ab, Plan 17:35 Uhr - Doppelzimmer&amp;lt;br&amp;gt; &lt;br /&gt;
#Brekenfelder, Ulf - [mailto:ubhh@openoffice.org ubhh@openoffice.org] - Freitag bis Sonntag - bitte holt uns vom Bahnhof ab, Plan 17:35 Uhr - Doppelzimmer&amp;lt;br&amp;gt; &lt;br /&gt;
#Hermann, Rene - [mailto:goherm76@googlemail.com goherm76@googlemail.com] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Henschel, Regina - [mailto:regina@openoffice.org regina@openoffice.org] - Freitag bis Sonntag - Bitte holt uns (Jacqueline und ich) vom Bahnhof ab, Ankunft 19:26 Uhr&amp;lt;br&amp;gt;&lt;br /&gt;
#Rahemipour, Jacqueline - [mailto:jrahemipour@openoffice.org jrahemipour@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Strohmaier, Friedrich - [mailto:bitsfritz@openoffice.org Friedrich Strohmaier] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Pechlaner, Wolfgang - [mailto:wope@openoffice.org Wolfgang Pechlaner] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Wilper, Simon - [mailto:simonaw@openoffice.org simonaw@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Stehmann, Mechtilde - [mailto:mechtilde@openoffice.org mechtilde@openoffice.org] - Samstag bis Sonntag - Bitte holt uns vom Bahnhof ab (Samstag. 10:24) - Doppelzimmer&amp;lt;br&amp;gt; &lt;br /&gt;
#Stehmann, Michael - [mailto:mikeadvo@openoffice.org mikeadvo@openoffice.org] - Samstag bis Sonntag - Bitte holt uns vom Bahnhof ab - Doppelzimmer&amp;lt;br&amp;gt; &lt;br /&gt;
#Weigel, Stefan - [[Special:EmailUser/Stefanw|StefanW]] - Freitag bis Sonntag - &amp;lt;span style=&amp;quot;color: red;&amp;quot;&amp;gt;Ankunft voraussichtlich 24:00 Uhr&amp;lt;/span&amp;gt;&amp;amp;nbsp;:-( geht das? &lt;br /&gt;
#Schnabel, André - [mailto:andreschnabel@openoffice.org andreschnabel@openoffice.org] - Freitag bis Sonntag &lt;br /&gt;
#Krumbein, Thomas (und Ayko) - [mailto:thomaskrumbein@openoffice.org thomaskrumbein@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Hillen, Andreas - [mailto:andreas.hillen@online.de andreas.hillen@online.de] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Brunjes, Holger - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Jakob, Franz - Freitag bis Sonntag - ohne&amp;amp;nbsp;Übernachtung &lt;br /&gt;
#Behrens, Thorsten - [mailto:thb@openoffice.org thb@openoffice.org] - Freitag bis Sonntag&lt;br /&gt;
&lt;br /&gt;
= Programm - wird noch bekanntgegeben -  =&lt;br /&gt;
&lt;br /&gt;
=== Freitag, 23. Juli  ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; | Zeit &lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Thema &lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Referent&lt;br /&gt;
|-&lt;br /&gt;
! ab 18:00 &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;geselliges Beisammensitzen und Grillen; bei schlechtem Wetter &amp;lt;u&amp;gt;KEIN&amp;lt;/u&amp;gt; Grillen möglich; Einkauf der Grillsachen erst vor Ort&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;kein offizieller Programmpunkt mehr am Freitag, da einige Leute später oder erst am Samstag anreisen &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Samstag, 24. Juli  ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; | Zeit &lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Thema &lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Referent&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Sonntag, 25. Juli  ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; | Zeit &lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Thema &lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Referent&lt;br /&gt;
|-&lt;br /&gt;
! 09:00-10:00 &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Frühstück (an der Fachhochschule)&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! 12:30-13:30 &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Zimmer räumen und Mittagessen (Pizzaservice)&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Themenvorschläge  ==&lt;br /&gt;
&lt;br /&gt;
=== Übersetzungsworkshop  ===&lt;br /&gt;
&lt;br /&gt;
Kurze Info zum Übersetzungsprozess bei de.OpenOffice.org, dann anschließend Arbeit an den Übersetzungen für OOo 3.3 (Abgabetermin ist 12.08.) Sollte idealrweise am Samstag nachmittag stattfinden, so dass man eine &amp;quot;OpenEnd&amp;quot;-Session für Leute, die es interessiert daraus machen kann. &lt;br /&gt;
&lt;br /&gt;
=== Basic Macros Workshop  ===&lt;br /&gt;
&lt;br /&gt;
Als Ergebnis stelle ich mir einige kommentierte Makros und zugehörige Anleitungen vor. Dabei sollten auch Hilfmittel und Informationsquellen gesammelt werden. &lt;br /&gt;
&lt;br /&gt;
Macros beispielweise für: &lt;br /&gt;
&lt;br /&gt;
*Ein Math-Objekt erhält seine Schriftgröße und Text-Schriftart von dem Zeichenformat des Ankerzeichens bzw. von dem zugewiesenen Graphik-Style. &lt;br /&gt;
*Eine Calc-Funktion, die die Reihenfolge der Zellinhalte eines Bereichs umkehrt &lt;br /&gt;
*Einen Dialog, in dem man die Eigenschaften von Bögen und Sektoren wie etwa Anfangs- und Endwinkel und Mittelpunkt genau setzen kann. &lt;br /&gt;
*Zu einem Diagramm eine polynominale Regressionsline hinzufügen&lt;br /&gt;
&lt;br /&gt;
=== Serienbriefassistent  ===&lt;br /&gt;
&lt;br /&gt;
Welche Probleme haben die aktuellen Lösungen, wie müsste ein neuer, besserer Assistent funktionieren. Ideensammlung für eine Spec. &lt;br /&gt;
&lt;br /&gt;
=== Issuetracker  ===&lt;br /&gt;
&lt;br /&gt;
Praxistipps zum Umgang mit Issuetracker und EIS. Darüber hinaus eine Ideensammlung für die Frage, wie die Community in den Prozess, welche Issues gefixed und welche Features implementiert werden, eingebunden werden kann. &lt;br /&gt;
&lt;br /&gt;
=== Kapitel- und Listennummerierung  ===&lt;br /&gt;
&lt;br /&gt;
Was ist möglich, was ist nicht möglich? Lösungen und Workarounds für spezielle Probleme. Was sind wünschenswerte Verbesserungen? Welche könnten ohne Änderungen des Standards realisiert werden? &lt;br /&gt;
&lt;br /&gt;
=== Calc zur Verwaltung von Listen  ===&lt;br /&gt;
&lt;br /&gt;
Es ist bekannt, dass viele das Benutzen einer &amp;quot;richtigen&amp;quot; Datenbank scheuen (aus welchen Gründen auch immer) und lieber Calc benutzen. Dazu sollte eine Anleitung erfolgen, was möglich ist, worauf man achten muss und was man vermeiden sollte. Es sollte eine Gliederung und eine Stoffsammlung im Wiki entstehen, vielleicht auch einzelne ausformulierte Texte.&lt;br /&gt;
* &amp;#039;&amp;#039;Vielleicht hilft [[User:Stefanw/www.datenpilot.org/Vortrag_Graz_2010|das]] zur Stoffsammlung [[User:Stefanw|Stefan Weigel]] 17:24, 12 July 2010 (UTC)&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
=== Kennenlernrunde ===&lt;br /&gt;
Diejenigen, die schon länger im Projekt sind, stellen ihr Arbeitsgebiet vor. Das sollte jeweils bis zu 10 Minuten dauern.&lt;br /&gt;
&lt;br /&gt;
=== Projektspezifische Themen ===&lt;br /&gt;
&lt;br /&gt;
==== PrOOo-Box ====&lt;br /&gt;
&lt;br /&gt;
Kurzer Insiderbericht zu Stand und Status des Projekts  (ca. 10 min, Friedrich)&lt;br /&gt;
&lt;br /&gt;
==== Nachwuchspflege ====&lt;br /&gt;
&lt;br /&gt;
Neue Interessenten werden nur zu einem Bruchteil im Projekt aktiv. Ist da noch&lt;br /&gt;
Spielraum für Verbesserungen? (ca. 5min Darstellung + 20 min &amp;quot;andiskutieren&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
= Fahrgemeinschaften  =&lt;br /&gt;
&lt;br /&gt;
*Biete &lt;br /&gt;
**Rene: - von und nach Leipzig &lt;br /&gt;
**[[Special:EmailUser/Stefanw|StefanW]] - Passau, Vilshofen, Deggendorf, Regensburg, ... und zurück. &lt;br /&gt;
**Bernhard: Ravensburg, Memmingen, Ulm, Nürnberg - Florian, ich hole dich ab (wie letztes Mal).&lt;br /&gt;
&lt;br /&gt;
*Suche &lt;br /&gt;
**Regina Henschel - von Dortmund und zurück&lt;br /&gt;
&lt;br /&gt;
= Dank  =&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Herzlichen Dank an Franz Jakob, der es uns auch in diesem Jahr wieder ermöglicht, ein solches Wochenende zu organisieren!&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
&lt;br /&gt;
[[Category:De.openoffice.org|Projektwochenende]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/Projektwochenende2010&amp;diff=173017</id>
		<title>DE/Projektwochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/Projektwochenende2010&amp;diff=173017"/>
		<updated>2010-06-24T07:52:47Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Will teilnehmen, weiß aber noch nicht, ob sie/er kann */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:OpenOffice.org Projektwochenende 2010}} &lt;br /&gt;
&lt;br /&gt;
= Kurzüberblick  =&lt;br /&gt;
&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wann?&amp;#039;&amp;#039;&amp;#039; Freitagabend, &amp;#039;&amp;#039;&amp;#039;23. Juli&amp;#039;&amp;#039;&amp;#039; bis Sonntagmittag, &amp;#039;&amp;#039;&amp;#039;25. Juli&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wo?&amp;#039;&amp;#039;&amp;#039; In der [http://www.fhvr-aiv.de Fachhochschule für öffentliche Verwaltung und Rechtspflege] &amp;#039;&amp;#039;&amp;#039;in Hof&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wieviel?&amp;#039;&amp;#039;&amp;#039; Die Übernachtungskosten werden voraussichtlich vom Verein [http://www.ooodev.org OpenOffice.org Deutschland e.V.] übernommen. Für Anfahrt und Verpflegung muss jeder selbst aufkommen. &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wieviele?&amp;#039;&amp;#039;&amp;#039; Insgesamt können wir &amp;#039;&amp;#039;&amp;#039;25-30&amp;#039;&amp;#039;&amp;#039; Personen in &amp;#039;&amp;#039;&amp;#039;Einzelzimmern mit Dusche und WC&amp;#039;&amp;#039;&amp;#039; direkt auf dem Campus unterbringen &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Wer?&amp;#039;&amp;#039;&amp;#039; Teilnehmen können sowohl &amp;#039;&amp;#039;&amp;#039;&amp;quot;alte Hasen&amp;quot;&amp;#039;&amp;#039;&amp;#039; im Projekt, die ihr Wissen weitergeben wollen, als auch im Besonderen &amp;#039;&amp;#039;&amp;#039;Neulinge, die gerne ein bisschen mehr über das Projekt erfahren würden&amp;#039;&amp;#039;&amp;#039;, um sich selbst dort einzubringen. Wir möchten insbesondere diejenigen zur Anmeldung ermuntern, die noch nicht so aktiv im Projekt sind, uns aber gerne kennenlernen würden! &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Was?&amp;#039;&amp;#039;&amp;#039; Das Wochenende dient zum einen zum &amp;#039;&amp;#039;&amp;#039;gegenseitigen Kennenlernen&amp;#039;&amp;#039;&amp;#039; der Projektmitglieder, zum anderen wollen wir durch Vorträge und Diskussionsrunden &amp;#039;&amp;#039;&amp;#039;künftige Vorhaben und Aktivitäten des deutschsprachigen Projektes planen&amp;#039;&amp;#039;&amp;#039;. 2007 ging es beispielsweise unter anderem um die rechtliche Stellung und Haftungsfragen von Projektmitgliedern, um geplante Marketing-Aktivitäten und Wettbewerbe, die Stellung des DE-Projektes innerhalb der internationalen OpenOffice.org-Community sowie über die Virtualisierung als Möglichkeit, OpenOffice.org, für viele Betriebssysteme zu testen. &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Veranstalter:&amp;#039;&amp;#039;&amp;#039; [http://www.ooodev.org OpenOffice.org Deutschland e.V.] &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Organisation und Ansprechpartner:&amp;#039;&amp;#039;&amp;#039; [mailto:floeff@openoffice.org Florian Effenberger] &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Internet&amp;#039;&amp;#039;&amp;#039; steht uns vor Ort nicht zur Verfügung. &amp;#039;&amp;#039;&amp;#039;Bitte ggf. UMTS-Karten fürs Notebook mitnehmen!&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;Transfer vom Bahnhof&amp;#039;&amp;#039;&amp;#039; ist nach Rücksprache möglich&lt;br /&gt;
&lt;br /&gt;
= Teilnehmer  =&lt;br /&gt;
&lt;br /&gt;
Bitte tragt euch in diese Liste mit Name, E-Mail-Adresse und An- sowie Abfahrtstag ein, um am Projektwochenende teilzunehmen. Wer keine Übernachtung benötigt, vermerkt dies bitte separat.&amp;amp;nbsp;Wer mit dem Wiki Probleme hat, kann sich auch per&amp;amp;nbsp;E-Mail bei [mailto:floeff@openoffice.org Florian Effenberger] anmelden. &amp;#039;&amp;#039;&amp;#039;Die Anmeldung ist zwar noch bis Anfang Juli möglich, aber wer zuerst kommt, der bekommt auch einen&amp;amp;nbsp;Schlafplatz.&amp;amp;nbsp;;-)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#Effenberger, Florian - [mailto:floeff@openoffice.org floeff@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Geib, Gerald - [mailto:gghh@openoffice.org gghh@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Brekenfelder, Ulf - [mailto:ubhh@openoffice.org ubhh@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Hermann, Rene - [mailto:goherm76@googlemail.com goherm76@googlemail.com] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Henschel, Regina - [mailto:regina@openoffice.org regina@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Rahemipour, Jacqueline - [mailto:jrahemipour@openoffice.org jrahemipour@openoffice.org] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Strohmaier, Friedrich - [mailto:bitsfritz@openoffice.org Friedrich Strohmaier] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Richter, Uwe - [mailto:richteruwe@openoffice.org Uwe Richter] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Rückgauer, Bernhard - [mailto:berni_rueck@openoffice.org Bernhard Rückgauer] - Freitag bis Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Pechlaner, Wolfgang - [mailto:wope@openoffice.org Wolfgang Pechlaner] - Freitag - Sonntag &amp;lt;br&amp;gt; &lt;br /&gt;
#Wilper, Simon - [mailto:simonaw@openoffice.org simonaw@openoffice.org] - Freitag - Sonntag &amp;lt;br&amp;gt; &lt;br /&gt;
#Stehmann, Mechtilde - [mailto:mechtilde@openoffice.org mechtilde@openoffice.org] - Samstag - Sonntag &amp;lt;br&amp;gt; &lt;br /&gt;
#Stehmann, Michael - [mailto:mikeadvo@openoffice.org mikeadvo@openoffice.org] - Samstag - Sonntag &amp;lt;br&amp;gt; &lt;br /&gt;
#Siebert,&amp;amp;nbsp;Frank - [mailto:fsiebert@trinuts.de fsiebert@trinuts.de] - Freitag - Sonntag &lt;br /&gt;
#Weigel, Stefan - [[Special:EmailUser/Stefanw|StefanW]] - Freitag bis Sonntag &lt;br /&gt;
#Schnabel, André - [mailto:andreschnabel@openoffice.org andreschnabel@openoffice.org] - Freitag bis Sonntag &lt;br /&gt;
#Krumbein, Thomas (und Ayko) - [mailto:thomaskrumbein@openoffice.org thomaskrumbein@openoffice.org] - Freitag - Sonntag &lt;br /&gt;
#Rahemipour, Jacqueline - [mailto:jrahemipour@openoffice.org jrahemipour@openoffice.org] - Freitag - Sonntag &lt;br /&gt;
#Hillen, Andreas - [mailto:andreas.hillen@online.de andreas.hillen@online.de] - Freitag - Sonntag&amp;lt;br&amp;gt; &lt;br /&gt;
#Schießl, Florian - [[Special:EmailUser/FloSchi|FloSchi]]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Will teilnehmen, weiß aber noch nicht, ob sie/er kann  ====&lt;br /&gt;
&lt;br /&gt;
#G., M. - [[Special:EmailUser/mgommel|mgommel]] - Freitag bis Sonntag &lt;br /&gt;
#Lohmaier, Christian - [[Special:EmailUser/cloph|cloph]] - Freitag bis Sonntag&lt;br /&gt;
#Brunjes, Holger - Freitag bis Sonntag&lt;br /&gt;
#Behrens, Thorsten - Freitag bis Sonntag - oder nur einen Tag, dann mit Kindern&lt;br /&gt;
&lt;br /&gt;
= Programm - wird noch bekanntgegeben -  =&lt;br /&gt;
&lt;br /&gt;
=== Freitag, 23. Juli  ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; | Zeit &lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Thema &lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Referent&lt;br /&gt;
|-&lt;br /&gt;
! ab 18:00 &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;geselliges Beisammensitzen und Grillen; bei schlechtem Wetter &amp;lt;u&amp;gt;KEIN&amp;lt;/u&amp;gt; Grillen möglich; Einkauf der Grillsachen erst vor Ort&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;kein offizieller Programmpunkt mehr am Freitag, da einige Leute später oder erst am Samstag anreisen &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! parallel dazu &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Vorstandssitzung OpenOffice.org Deutschland e.V.&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Samstag, 24. Juli  ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; | Zeit &lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Thema &lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Referent&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Sonntag, 25. Juli  ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; | Zeit &lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Thema &lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Referent&lt;br /&gt;
|-&lt;br /&gt;
! 09:00-10:00 &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Frühstück (an der Fachhochschule)&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
! 12:30-13:30 &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Zimmer räumen und Mittagessen (Pizzaservice)&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Themenvorschläge  ==&lt;br /&gt;
&lt;br /&gt;
=== Übersetzungsworkshop ===&lt;br /&gt;
Kurze Info zum Übersetzungsprozess bei de.OpenOffice.org, dann anschließend Arbeit an den Übersetzungen für OOo 3.3 (Abgabetermin ist 12.08.)&lt;br /&gt;
Sollte idealrweise am Samstag nachmittag stattfinden, so dass man eine &amp;quot;OpenEnd&amp;quot;-Session für Leute, die es interessiert daraus machen kann.&lt;br /&gt;
&lt;br /&gt;
= Fahrgemeinschaften  =&lt;br /&gt;
&lt;br /&gt;
*Biete &lt;br /&gt;
**Rene: - von und nach Leipzig &lt;br /&gt;
**[[Special:EmailUser/Stefanw|StefanW]] - Passau, Vilshofen, Deggendorf, Regensburg, ... und zurück. &lt;br /&gt;
**Bernhard: Ravensburg, Memmingen, Ulm, Nürnberg - Florian, ich hole dich ab (wie letztes Mal).&lt;br /&gt;
&lt;br /&gt;
*Suche &lt;br /&gt;
**Florian Effenberger - von Kaufbeuren/München/Augsburg/Kempten &lt;br /&gt;
**Christian Lohmaier - von München. Suche Mitfahrgelegenheit (bevorzugt) bzw. suche Mitfahrer (da Teilnahme nicht sicher, die unsichere Alternative) &lt;br /&gt;
**Regina Henschel - von Dortmund und zurück&lt;br /&gt;
&lt;br /&gt;
= Dank  =&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Herzlichen Dank an Franz Jakob, der es uns auch in diesem Jahr wieder ermöglicht, ein solches Wochenende zu organisieren!&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
&lt;br /&gt;
[[Category:De.openoffice.org|Projektwochenende]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165873</id>
		<title>DE/QA-Wochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165873"/>
		<updated>2010-05-02T10:23:28Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Sonntag */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:DE|QA-Wochenende2010]]&lt;br /&gt;
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}} &lt;br /&gt;
=QA-Wochenende 2010 Linux-Hotel Essen=&lt;br /&gt;
&lt;br /&gt;
== Adresse ==&lt;br /&gt;
&lt;br /&gt;
Linux-Hotel / Villa Vogelsang&amp;lt;br&amp;gt;&lt;br /&gt;
Antonienallee 1&amp;lt;br&amp;gt;&lt;br /&gt;
45279 Essen-Horst&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: 0201 8536-600&amp;lt;br&amp;gt;&lt;br /&gt;
Fax: 0201 8536-605&amp;lt;br&amp;gt;&lt;br /&gt;
E-Mail: rezeption@villa-vogelsang.de&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ansprechpartner / Organisation ==&lt;br /&gt;
&lt;br /&gt;
Jacqueline Rahemipour&amp;lt;br&amp;gt;&lt;br /&gt;
jrahemipour@openoffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: auf Anfrage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Termin ==&lt;br /&gt;
&lt;br /&gt;
30.4.-02.05.10&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Worum geht es? ==&lt;br /&gt;
&lt;br /&gt;
* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren&lt;br /&gt;
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen&lt;br /&gt;
* Erfahrungsaustausch mit erfahrenen QA&amp;#039;lern&lt;br /&gt;
* Konkret anstehende Aufgaben gemeinsam bearbeiten&lt;br /&gt;
* die &amp;quot;schönsten&amp;quot; Bugs finden&lt;br /&gt;
* Die anderen netten Leute aus dem Projekt kennenlernen&lt;br /&gt;
* In geselliger Runde über OOo und die Welt quatschen&lt;br /&gt;
* und vieles mehr&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Angemeldete Teilnehmer  ==&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Nr. &lt;br /&gt;
! Name &lt;br /&gt;
! Vorname &lt;br /&gt;
! Anreise am &lt;br /&gt;
! ggfs. Uhrzeit &lt;br /&gt;
! mit Übernachtung? &lt;br /&gt;
! Bemerkungen&lt;br /&gt;
|-&lt;br /&gt;
! 1 &lt;br /&gt;
| Rahemipour &lt;br /&gt;
| Jacqueline &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 2 &lt;br /&gt;
| Wilper &lt;br /&gt;
| Simon &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 3 &lt;br /&gt;
| Pechlaner &lt;br /&gt;
| Wolfgang &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 13 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier&lt;br /&gt;
|-&lt;br /&gt;
! 4 &lt;br /&gt;
| Schnabel &lt;br /&gt;
| André &lt;br /&gt;
| Freitag &lt;br /&gt;
| gegen 19:30 &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 5 &lt;br /&gt;
| Effenberger &lt;br /&gt;
| Florian &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 18/19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 6 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Mechtilde &lt;br /&gt;
| Freitag &lt;br /&gt;
| Nach Mittag&lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 7 &lt;br /&gt;
| Heggemann&lt;br /&gt;
| Volker&lt;br /&gt;
| Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 8 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Michael &lt;br /&gt;
| Freitag &lt;br /&gt;
| Nach Mittag&lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 9 &lt;br /&gt;
| Brekenfelder &lt;br /&gt;
| Ulf &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 10 &lt;br /&gt;
| Geib &lt;br /&gt;
| Gerald &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 11 &lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 12 &lt;br /&gt;
| Strohmaier &lt;br /&gt;
| Friedrich &lt;br /&gt;
| Freitag &lt;br /&gt;
| abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 13 &lt;br /&gt;
| Andrae &lt;br /&gt;
| Joost &lt;br /&gt;
| Freitag&lt;br /&gt;
| Abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 14 &lt;br /&gt;
| Altmann &lt;br /&gt;
| Uwe &lt;br /&gt;
| Samstag &lt;br /&gt;
| nachmittag gegen 16:00 &lt;br /&gt;
| ja &lt;br /&gt;
| suche für So MfG nach Köln&lt;br /&gt;
|-&lt;br /&gt;
! 15 &lt;br /&gt;
| Behrens &lt;br /&gt;
| Thorsten &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachts&lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 16 &lt;br /&gt;
| Lohmaier &lt;br /&gt;
| Christian &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachmittag &lt;br /&gt;
| ja &lt;br /&gt;
| ist gerne scharf, wünscht sich deshalb ein Chili-Ketchup&amp;amp;nbsp;:-))&lt;br /&gt;
|-&lt;br /&gt;
! 17 &lt;br /&gt;
| Hollmichel&lt;br /&gt;
| 2 Pers.&lt;br /&gt;
| Freitag &lt;br /&gt;
| speat&lt;br /&gt;
| ja&lt;br /&gt;
| ist Samstag fruehen nachmittag wieder weg&lt;br /&gt;
|-&lt;br /&gt;
! 18 &lt;br /&gt;
| Mantke&lt;br /&gt;
| Andreas&lt;br /&gt;
| Samstag&lt;br /&gt;
| vormittag&lt;br /&gt;
| nicht erforderlich&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geplantes Programm ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Themenvorschläge===&lt;br /&gt;
&lt;br /&gt;
[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]&lt;br /&gt;
&lt;br /&gt;
[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039; (Simon Wilper)&lt;br /&gt;
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
** Mercurial bedienen&lt;br /&gt;
** ./configure-Optionen&lt;br /&gt;
** Build-Tools&lt;br /&gt;
** Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Wie geht es weiter? - QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039; (Mechtilde - Unterpunkte von Uwe Altmann)&lt;br /&gt;
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?&lt;br /&gt;
** Das zielt&lt;br /&gt;
**# auf neue Interessenten&lt;br /&gt;
**# 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.&lt;br /&gt;
**# auf &amp;quot;...haben wir dazu eine Präsi??&amp;quot; ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;QA von Extensionen&amp;#039;&amp;#039;&amp;#039; (Michael)&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Lokalisierungsprozess bei OOo&amp;#039;&amp;#039;&amp;#039; (André)&lt;br /&gt;
** Infos über den Lokalisierungsprozesse bei OOo, verwendete Dateiformate, Tools und Prozesse in der DE-Community&lt;br /&gt;
** eigentlich meine Präsentation von der OOoCon, die aber sicher auch für uns interessant ist&lt;br /&gt;
** original-Abstract:&lt;br /&gt;
::OpenOffice.org supports localization for about 100 languages. 96k words in UI and 433k words for the help making it one of the largest and most complex software localization projects.Although most translation teams share a common process, the tools, used file formats and intra project coordination differ. Within the session we will give a short overview of the recommended translation process. In a second step we will present the way how the German teams works - what tools we use, why we have chosen those tools and why we use the XLIFF file format.&lt;br /&gt;
&lt;br /&gt;
===Samstag===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Begrüßung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* kurze Absprache des Arbeitsplanes&lt;br /&gt;
* Fragen zu Technik&lt;br /&gt;
* Organisatorisches  &lt;br /&gt;
|| Jacqueline Rahemipour&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
* Mercurial bedienen&lt;br /&gt;
* ./configure-Optionen&lt;br /&gt;
* Build-Tools&lt;br /&gt;
* Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
|| Simon Wilper&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Wie sieht der aktuelle Release-Prozess aus?&lt;br /&gt;
* ...&lt;br /&gt;
|| Mechtilde Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:30-14:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Mittagessen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 14:00-15:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Aktuelle Situation im de-Projekt&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Personelle Situation - wo sind derzeit die größten Engpässe?&lt;br /&gt;
* Vakante Position des Ansprechpartners QA&lt;br /&gt;
* Welche Auswirkungen hat die Oracle-Übernahme auf die Motivation der Mithelfer im de-Projekt?&lt;br /&gt;
* Welche Möglichkeiten gibt es, neue aktive Helfer für das de-Projekt zu gewinnen?&lt;br /&gt;
|| Jacqueline Rahemipour, alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 15:30-16:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee und Kuchen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 16:00-Open End&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Bughunting / Diskussion&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen&lt;br /&gt;
* neue Issues aufgeben&lt;br /&gt;
* Fehlersuche&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Sonntag===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-11:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA für Extensions&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Bisher gibt es keinen definierten Prozess für die QA von Extensions. Welche Möglichkeiten gibt es für die Zukunft?&lt;br /&gt;
* ...&lt;br /&gt;
|| Michael Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Kurze Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Dateiformat-QA: ODF Validierung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was ist Validierung?&lt;br /&gt;
* Standard-konform vs. Interoperabel&lt;br /&gt;
* Vortragsfolien [[File:Qa-weekend-2010.odp]]&lt;br /&gt;
|| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Anreise ==&lt;br /&gt;
&lt;br /&gt;
=== S-Bahn ===&lt;br /&gt;
Die S-Bahn-Haltestelle &amp;quot;Essen-Horst (S)&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
=== Bus ===&lt;br /&gt;
Die Haltestelle &amp;quot;Geschwister-Scholl-Str.&amp;quot; der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.&lt;br /&gt;
&lt;br /&gt;
=== PKW ===&lt;br /&gt;
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 &amp;quot;Eisenbahnmuseum&amp;quot;. Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder &amp;quot;Villa-Vogelsang&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Übernachtung ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Verpflegung ==&lt;br /&gt;
&lt;br /&gt;
Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel. &lt;br /&gt;
&lt;br /&gt;
Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Gerne werden Salatspenden angenommen!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Seminarraum ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internet ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Freizeit ==&lt;br /&gt;
&lt;br /&gt;
Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Bade­tücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sonstiges ==&lt;br /&gt;
&lt;br /&gt;
Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochen­ende auf uns allein gestellt, das heißt:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen&lt;br /&gt;
&lt;br /&gt;
* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug &amp;amp; Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräum­arbeiten behilflich sein?&amp;#039;&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=File:Qa-weekend-2010.odp&amp;diff=165872</id>
		<title>File:Qa-weekend-2010.odp</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=File:Qa-weekend-2010.odp&amp;diff=165872"/>
		<updated>2010-05-02T10:19:01Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: Talk QA Weekend&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Talk QA Weekend&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165665</id>
		<title>DE/QA-Wochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165665"/>
		<updated>2010-04-30T16:48:51Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Angemeldete Teilnehmer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:DE|QA-Wochenende2010]]&lt;br /&gt;
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}} &lt;br /&gt;
=QA-Wochenende 2010 Linux-Hotel Essen=&lt;br /&gt;
&lt;br /&gt;
== Adresse ==&lt;br /&gt;
&lt;br /&gt;
Linux-Hotel / Villa Vogelsang&amp;lt;br&amp;gt;&lt;br /&gt;
Antonienallee 1&amp;lt;br&amp;gt;&lt;br /&gt;
45279 Essen-Horst&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: 0201 8536-600&amp;lt;br&amp;gt;&lt;br /&gt;
Fax: 0201 8536-605&amp;lt;br&amp;gt;&lt;br /&gt;
E-Mail: rezeption@villa-vogelsang.de&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ansprechpartner / Organisation ==&lt;br /&gt;
&lt;br /&gt;
Jacqueline Rahemipour&amp;lt;br&amp;gt;&lt;br /&gt;
jrahemipour@openoffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: auf Anfrage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Termin ==&lt;br /&gt;
&lt;br /&gt;
30.4.-02.05.10&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Worum geht es? ==&lt;br /&gt;
&lt;br /&gt;
* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren&lt;br /&gt;
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen&lt;br /&gt;
* Erfahrungsaustausch mit erfahrenen QA&amp;#039;lern&lt;br /&gt;
* Konkret anstehende Aufgaben gemeinsam bearbeiten&lt;br /&gt;
* die &amp;quot;schönsten&amp;quot; Bugs finden&lt;br /&gt;
* Die anderen netten Leute aus dem Projekt kennenlernen&lt;br /&gt;
* In geselliger Runde über OOo und die Welt quatschen&lt;br /&gt;
* und vieles mehr&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Angemeldete Teilnehmer  ==&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Nr. &lt;br /&gt;
! Name &lt;br /&gt;
! Vorname &lt;br /&gt;
! Anreise am &lt;br /&gt;
! ggfs. Uhrzeit &lt;br /&gt;
! mit Übernachtung? &lt;br /&gt;
! Bemerkungen&lt;br /&gt;
|-&lt;br /&gt;
! 1 &lt;br /&gt;
| Rahemipour &lt;br /&gt;
| Jacqueline &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 2 &lt;br /&gt;
| Wilper &lt;br /&gt;
| Simon &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 3 &lt;br /&gt;
| Pechlaner &lt;br /&gt;
| Wolfgang &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 13 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier&lt;br /&gt;
|-&lt;br /&gt;
! 4 &lt;br /&gt;
| Schnabel &lt;br /&gt;
| André &lt;br /&gt;
| Freitag &lt;br /&gt;
| gegen 19:30 &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 5 &lt;br /&gt;
| Effenberger &lt;br /&gt;
| Florian &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 18/19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 6 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Mechtilde &lt;br /&gt;
| Freitag &lt;br /&gt;
| Nach Mittag&lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 7 &lt;br /&gt;
| Heggemann&lt;br /&gt;
| Volker&lt;br /&gt;
| Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 8 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Michael &lt;br /&gt;
| Freitag &lt;br /&gt;
| Nach Mittag&lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 9 &lt;br /&gt;
| Brekenfelder &lt;br /&gt;
| Ulf &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 10 &lt;br /&gt;
| Geib &lt;br /&gt;
| Gerald &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 11 &lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 12 &lt;br /&gt;
| Strohmaier &lt;br /&gt;
| Friedrich &lt;br /&gt;
| Freitag &lt;br /&gt;
| abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 13 &lt;br /&gt;
| Andrae &lt;br /&gt;
| Joost &lt;br /&gt;
| Freitag&lt;br /&gt;
| Abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 14 &lt;br /&gt;
| Altmann &lt;br /&gt;
| Uwe &lt;br /&gt;
| Samstag &lt;br /&gt;
| nachmittag gegen 16:00 &lt;br /&gt;
| ja &lt;br /&gt;
| suche für So MfG nach Köln&lt;br /&gt;
|-&lt;br /&gt;
! 15 &lt;br /&gt;
| Behrens &lt;br /&gt;
| Thorsten &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachts&lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 16 &lt;br /&gt;
| Lohmaier &lt;br /&gt;
| Christian &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachmittag &lt;br /&gt;
| ja &lt;br /&gt;
| ist gerne scharf, wünscht sich deshalb ein Chili-Ketchup&amp;amp;nbsp;:-))&lt;br /&gt;
|-&lt;br /&gt;
! 17 &lt;br /&gt;
| Hollmichel&lt;br /&gt;
| 2 Pers.&lt;br /&gt;
| Freitag &lt;br /&gt;
| speat&lt;br /&gt;
| ja&lt;br /&gt;
| ist Samstag fruehen nachmittag wieder weg&lt;br /&gt;
|-&lt;br /&gt;
! 18 &lt;br /&gt;
| Mantke&lt;br /&gt;
| Andreas&lt;br /&gt;
| Samstag&lt;br /&gt;
| vormittag&lt;br /&gt;
| nicht erforderlich&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geplantes Programm ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Themenvorschläge===&lt;br /&gt;
&lt;br /&gt;
[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]&lt;br /&gt;
&lt;br /&gt;
[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039; (Simon Wilper)&lt;br /&gt;
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
** Mercurial bedienen&lt;br /&gt;
** ./configure-Optionen&lt;br /&gt;
** Build-Tools&lt;br /&gt;
** Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Wie geht es weiter? - QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039; (Mechtilde - Unterpunkte von Uwe Altmann)&lt;br /&gt;
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?&lt;br /&gt;
** Das zielt&lt;br /&gt;
**# auf neue Interessenten&lt;br /&gt;
**# 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.&lt;br /&gt;
**# auf &amp;quot;...haben wir dazu eine Präsi??&amp;quot; ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;QA von Extensionen&amp;#039;&amp;#039;&amp;#039; (Michael)&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Lokalisierungsprozess bei OOo&amp;#039;&amp;#039;&amp;#039; (André)&lt;br /&gt;
** Infos über den Lokalisierungsprozesse bei OOo, verwendete Dateiformate, Tools und Prozesse in der DE-Community&lt;br /&gt;
** eigentlich meine Präsentation von der OOoCon, die aber sicher auch für uns interessant ist&lt;br /&gt;
** original-Abstract:&lt;br /&gt;
::OpenOffice.org supports localization for about 100 languages. 96k words in UI and 433k words for the help making it one of the largest and most complex software localization projects.Although most translation teams share a common process, the tools, used file formats and intra project coordination differ. Within the session we will give a short overview of the recommended translation process. In a second step we will present the way how the German teams works - what tools we use, why we have chosen those tools and why we use the XLIFF file format.&lt;br /&gt;
&lt;br /&gt;
===Samstag===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Begrüßung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* kurze Absprache des Arbeitsplanes&lt;br /&gt;
* Fragen zu Technik&lt;br /&gt;
* Organisatorisches  &lt;br /&gt;
|| Jacqueline Rahemipour&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
* Mercurial bedienen&lt;br /&gt;
* ./configure-Optionen&lt;br /&gt;
* Build-Tools&lt;br /&gt;
* Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
|| Simon Wilper&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Wie sieht der aktuelle Release-Prozess aus?&lt;br /&gt;
* ...&lt;br /&gt;
|| Mechtilde Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:30-14:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Mittagessen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 14:00-15:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Aktuelle Situation im de-Projekt&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Personelle Situation - wo sind derzeit die größten Engpässe?&lt;br /&gt;
* Vakante Position des Ansprechpartners QA&lt;br /&gt;
* Welche Auswirkungen hat die Oracle-Übernahme auf die Motivation der Mithelfer im de-Projekt?&lt;br /&gt;
* Welche Möglichkeiten gibt es, neue aktive Helfer für das de-Projekt zu gewinnen?&lt;br /&gt;
|| Jacqueline Rahemipour, alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 15:30-16:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee und Kuchen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 16:00-Open End&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Bughunting / Diskussion&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen&lt;br /&gt;
* neue Issues aufgeben&lt;br /&gt;
* Fehlersuche&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Sonntag===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-11:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA für Extensions&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Bisher gibt es keinen definierten Prozess für die QA von Extensions. Welche Möglichkeiten gibt es für die Zukunft?&lt;br /&gt;
* ...&lt;br /&gt;
|| Michael Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Kurze Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Dateiformat-QA: ODF Validierung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was ist Validierung?&lt;br /&gt;
* Standard-konform vs. Interoperabel&lt;br /&gt;
* ...&lt;br /&gt;
|| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Anreise ==&lt;br /&gt;
&lt;br /&gt;
=== S-Bahn ===&lt;br /&gt;
Die S-Bahn-Haltestelle &amp;quot;Essen-Horst (S)&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
=== Bus ===&lt;br /&gt;
Die Haltestelle &amp;quot;Geschwister-Scholl-Str.&amp;quot; der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.&lt;br /&gt;
&lt;br /&gt;
=== PKW ===&lt;br /&gt;
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 &amp;quot;Eisenbahnmuseum&amp;quot;. Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder &amp;quot;Villa-Vogelsang&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Übernachtung ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Verpflegung ==&lt;br /&gt;
&lt;br /&gt;
Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel. &lt;br /&gt;
&lt;br /&gt;
Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Gerne werden Salatspenden angenommen!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Seminarraum ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internet ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Freizeit ==&lt;br /&gt;
&lt;br /&gt;
Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Bade­tücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sonstiges ==&lt;br /&gt;
&lt;br /&gt;
Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochen­ende auf uns allein gestellt, das heißt:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen&lt;br /&gt;
&lt;br /&gt;
* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug &amp;amp; Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräum­arbeiten behilflich sein?&amp;#039;&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165181</id>
		<title>DE/QA-Wochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165181"/>
		<updated>2010-04-26T14:10:03Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Sonntag */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:DE|QA-Wochenende2010]]&lt;br /&gt;
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}} &lt;br /&gt;
=QA-Wochenende 2010 Linux-Hotel Essen=&lt;br /&gt;
&lt;br /&gt;
== Adresse ==&lt;br /&gt;
&lt;br /&gt;
Linux-Hotel / Villa Vogelsang&amp;lt;br&amp;gt;&lt;br /&gt;
Antonienallee 1&amp;lt;br&amp;gt;&lt;br /&gt;
45279 Essen-Horst&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: 0201 8536-600&amp;lt;br&amp;gt;&lt;br /&gt;
Fax: 0201 8536-605&amp;lt;br&amp;gt;&lt;br /&gt;
E-Mail: rezeption@villa-vogelsang.de&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ansprechpartner / Organisation ==&lt;br /&gt;
&lt;br /&gt;
Jacqueline Rahemipour&amp;lt;br&amp;gt;&lt;br /&gt;
jrahemipour@openoffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: auf Anfrage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Termin ==&lt;br /&gt;
&lt;br /&gt;
30.4.-02.05.10&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Worum geht es? ==&lt;br /&gt;
&lt;br /&gt;
* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren&lt;br /&gt;
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen&lt;br /&gt;
* Erfahrungsaustausch mit erfahrenen QA&amp;#039;lern&lt;br /&gt;
* Konkret anstehende Aufgaben gemeinsam bearbeiten&lt;br /&gt;
* die &amp;quot;schönsten&amp;quot; Bugs finden&lt;br /&gt;
* Die anderen netten Leute aus dem Projekt kennenlernen&lt;br /&gt;
* In geselliger Runde über OOo und die Welt quatschen&lt;br /&gt;
* und vieles mehr&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Angemeldete Teilnehmer  ==&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Nr. &lt;br /&gt;
! Name &lt;br /&gt;
! Vorname &lt;br /&gt;
! Anreise am &lt;br /&gt;
! ggfs. Uhrzeit &lt;br /&gt;
! mit Übernachtung? &lt;br /&gt;
! Bemerkungen&lt;br /&gt;
|-&lt;br /&gt;
! 1 &lt;br /&gt;
| Rahemipour &lt;br /&gt;
| Jacqueline &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 2 &lt;br /&gt;
| Wilper &lt;br /&gt;
| Simon &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 3 &lt;br /&gt;
| Pechlaner &lt;br /&gt;
| Wolfgang &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 13 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier&lt;br /&gt;
|-&lt;br /&gt;
! 4 &lt;br /&gt;
| Schnabel &lt;br /&gt;
| André &lt;br /&gt;
| Freitag &lt;br /&gt;
| gegen 19:30 &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 5 &lt;br /&gt;
| Effenberger &lt;br /&gt;
| Florian &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 18/19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 6 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Mechtilde &lt;br /&gt;
| vorauss. Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 7 &lt;br /&gt;
| Hackert &lt;br /&gt;
| Thomas &lt;br /&gt;
| Samstag &lt;br /&gt;
| ca. 10:00 &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier (steht aber leider erst kurz vorher wirklich fest, sorry ...&amp;amp;nbsp;:( ) &lt;br /&gt;
|-&lt;br /&gt;
! 8 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Michael &lt;br /&gt;
| vorauss. Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 9 &lt;br /&gt;
| Brekenfelder &lt;br /&gt;
| Ulf &lt;br /&gt;
| Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 10 &lt;br /&gt;
| Geib &lt;br /&gt;
| Gerald &lt;br /&gt;
| Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 11 &lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 12 &lt;br /&gt;
| Strohmaier &lt;br /&gt;
| Friedrich &lt;br /&gt;
| Freitag &lt;br /&gt;
| abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 13 &lt;br /&gt;
| Andrae &lt;br /&gt;
| Joost &lt;br /&gt;
| Freitag (noch unklar) &lt;br /&gt;
| Abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 14 &lt;br /&gt;
| Altmann &lt;br /&gt;
| Uwe &lt;br /&gt;
| Samstag &lt;br /&gt;
| nachmittag gegen 16:00 &lt;br /&gt;
| ja &lt;br /&gt;
| suche für So MfG nach Köln&lt;br /&gt;
|-&lt;br /&gt;
! 15 &lt;br /&gt;
| Behrens &lt;br /&gt;
| Thorsten &lt;br /&gt;
| Samstag &lt;br /&gt;
| mittags (voraussichtlich) &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 16 &lt;br /&gt;
| Lohmaier &lt;br /&gt;
| Christian &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachmittag &lt;br /&gt;
| ja &lt;br /&gt;
| ist gerne scharf, wünscht sich deshalb ein Chili-Ketchup&amp;amp;nbsp;:-))&lt;br /&gt;
|-&lt;br /&gt;
! 17 &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 18 &lt;br /&gt;
| Mantke&lt;br /&gt;
| Andreas&lt;br /&gt;
| Samstag&lt;br /&gt;
| vormittag&lt;br /&gt;
| nicht erforderlich&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geplantes Programm ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Themenvorschläge===&lt;br /&gt;
&lt;br /&gt;
[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]&lt;br /&gt;
&lt;br /&gt;
[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039; (Simon Wilper)&lt;br /&gt;
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
** Mercurial bedienen&lt;br /&gt;
** ./configure-Optionen&lt;br /&gt;
** Build-Tools&lt;br /&gt;
** Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Wie geht es weiter? - QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039; (Mechtilde - Unterpunkte von Uwe Altmann)&lt;br /&gt;
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?&lt;br /&gt;
** Das zielt&lt;br /&gt;
**# auf neue Interessenten&lt;br /&gt;
**# 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.&lt;br /&gt;
**# auf &amp;quot;...haben wir dazu eine Präsi??&amp;quot; ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;QA von Extensionen&amp;#039;&amp;#039;&amp;#039; (Michael)&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Lokalisierungsprozess bei OOo&amp;#039;&amp;#039;&amp;#039; (André)&lt;br /&gt;
** Infos über den Lokalisierungsprozesse bei OOo, verwendete Dateiformate, Tools und Prozesse in der DE-Community&lt;br /&gt;
** eigentlich meine Präsentation von der OOoCon, die aber sicher auch für uns interessant ist&lt;br /&gt;
** original-Abstract:&lt;br /&gt;
::OpenOffice.org supports localization for about 100 languages. 96k words in UI and 433k words for the help making it one of the largest and most complex software localization projects.Although most translation teams share a common process, the tools, used file formats and intra project coordination differ. Within the session we will give a short overview of the recommended translation process. In a second step we will present the way how the German teams works - what tools we use, why we have chosen those tools and why we use the XLIFF file format.&lt;br /&gt;
&lt;br /&gt;
===Samstag===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Begrüßung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* kurze Absprache des Arbeitsplanes&lt;br /&gt;
* Fragen zu Technik&lt;br /&gt;
* Organisatorisches  &lt;br /&gt;
|| Jacqueline Rahemipour&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
* Mercurial bedienen&lt;br /&gt;
* ./configure-Optionen&lt;br /&gt;
* Build-Tools&lt;br /&gt;
* Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
|| Simon Wilper&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Wie sieht der aktuelle Release-Prozess aus?&lt;br /&gt;
* ...&lt;br /&gt;
|| Mechtilde Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:30-14:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Mittagessen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 14:00-15:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Aktuelle Situation im de-Projekt&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Personelle Situation - wo sind derzeit die größten Engpässe?&lt;br /&gt;
* Vakante Position des Ansprechpartners QA&lt;br /&gt;
* Welche Auswirkungen hat die Oracle-Übernahme auf die Motivation der Mithelfer im de-Projekt?&lt;br /&gt;
* Welche Möglichkeiten gibt es, neue aktive Helfer für das de-Projekt zu gewinnen?&lt;br /&gt;
|| Jacqueline Rahemipour, alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 15:30-16:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee und Kuchen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 16:00-Open End&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Bughunting / Diskussion&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen&lt;br /&gt;
* neue Issues aufgeben&lt;br /&gt;
* Fehlersuche&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Sonntag===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-11:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA für Extensions&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Bisher gibt es keinen definierten Prozess für die QA von Extensions. Welche Möglichkeiten gibt es für die Zukunft?&lt;br /&gt;
* ...&lt;br /&gt;
|| Michael Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Kurze Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Dateiformat-QA: ODF Validierung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was ist Validierung?&lt;br /&gt;
* Standard-konform vs. Interoperabel&lt;br /&gt;
* ...&lt;br /&gt;
|| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Anreise ==&lt;br /&gt;
&lt;br /&gt;
=== S-Bahn ===&lt;br /&gt;
Die S-Bahn-Haltestelle &amp;quot;Essen-Horst (S)&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
=== Bus ===&lt;br /&gt;
Die Haltestelle &amp;quot;Geschwister-Scholl-Str.&amp;quot; der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.&lt;br /&gt;
&lt;br /&gt;
=== PKW ===&lt;br /&gt;
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 &amp;quot;Eisenbahnmuseum&amp;quot;. Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder &amp;quot;Villa-Vogelsang&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Übernachtung ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Verpflegung ==&lt;br /&gt;
&lt;br /&gt;
Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel. &lt;br /&gt;
&lt;br /&gt;
Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Gerne werden Salatspenden angenommen!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Seminarraum ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internet ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Freizeit ==&lt;br /&gt;
&lt;br /&gt;
Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Bade­tücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sonstiges ==&lt;br /&gt;
&lt;br /&gt;
Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochen­ende auf uns allein gestellt, das heißt:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen&lt;br /&gt;
&lt;br /&gt;
* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug &amp;amp; Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräum­arbeiten behilflich sein?&amp;#039;&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165168</id>
		<title>DE/QA-Wochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165168"/>
		<updated>2010-04-26T14:00:41Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Sonntag */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:DE|QA-Wochenende2010]]&lt;br /&gt;
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}} &lt;br /&gt;
=QA-Wochenende 2010 Linux-Hotel Essen=&lt;br /&gt;
&lt;br /&gt;
== Adresse ==&lt;br /&gt;
&lt;br /&gt;
Linux-Hotel / Villa Vogelsang&amp;lt;br&amp;gt;&lt;br /&gt;
Antonienallee 1&amp;lt;br&amp;gt;&lt;br /&gt;
45279 Essen-Horst&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: 0201 8536-600&amp;lt;br&amp;gt;&lt;br /&gt;
Fax: 0201 8536-605&amp;lt;br&amp;gt;&lt;br /&gt;
E-Mail: rezeption@villa-vogelsang.de&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ansprechpartner / Organisation ==&lt;br /&gt;
&lt;br /&gt;
Jacqueline Rahemipour&amp;lt;br&amp;gt;&lt;br /&gt;
jrahemipour@openoffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: auf Anfrage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Termin ==&lt;br /&gt;
&lt;br /&gt;
30.4.-02.05.10&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Worum geht es? ==&lt;br /&gt;
&lt;br /&gt;
* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren&lt;br /&gt;
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen&lt;br /&gt;
* Erfahrungsaustausch mit erfahrenen QA&amp;#039;lern&lt;br /&gt;
* Konkret anstehende Aufgaben gemeinsam bearbeiten&lt;br /&gt;
* die &amp;quot;schönsten&amp;quot; Bugs finden&lt;br /&gt;
* Die anderen netten Leute aus dem Projekt kennenlernen&lt;br /&gt;
* In geselliger Runde über OOo und die Welt quatschen&lt;br /&gt;
* und vieles mehr&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Angemeldete Teilnehmer  ==&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Nr. &lt;br /&gt;
! Name &lt;br /&gt;
! Vorname &lt;br /&gt;
! Anreise am &lt;br /&gt;
! ggfs. Uhrzeit &lt;br /&gt;
! mit Übernachtung? &lt;br /&gt;
! Bemerkungen&lt;br /&gt;
|-&lt;br /&gt;
! 1 &lt;br /&gt;
| Rahemipour &lt;br /&gt;
| Jacqueline &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 2 &lt;br /&gt;
| Wilper &lt;br /&gt;
| Simon &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 3 &lt;br /&gt;
| Pechlaner &lt;br /&gt;
| Wolfgang &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 13 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier&lt;br /&gt;
|-&lt;br /&gt;
! 4 &lt;br /&gt;
| Schnabel &lt;br /&gt;
| André &lt;br /&gt;
| Freitag &lt;br /&gt;
| gegen 19:30 &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 5 &lt;br /&gt;
| Effenberger &lt;br /&gt;
| Florian &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 18/19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 6 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Mechtilde &lt;br /&gt;
| vorauss. Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 7 &lt;br /&gt;
| Hackert &lt;br /&gt;
| Thomas &lt;br /&gt;
| Samstag &lt;br /&gt;
| ca. 10:00 &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier (steht aber leider erst kurz vorher wirklich fest, sorry ...&amp;amp;nbsp;:( ) &lt;br /&gt;
|-&lt;br /&gt;
! 8 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Michael &lt;br /&gt;
| vorauss. Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 9 &lt;br /&gt;
| Brekenfelder &lt;br /&gt;
| Ulf &lt;br /&gt;
| Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 10 &lt;br /&gt;
| Geib &lt;br /&gt;
| Gerald &lt;br /&gt;
| Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 11 &lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 12 &lt;br /&gt;
| Strohmaier &lt;br /&gt;
| Friedrich &lt;br /&gt;
| Freitag &lt;br /&gt;
| abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 13 &lt;br /&gt;
| Andrae &lt;br /&gt;
| Joost &lt;br /&gt;
| Freitag (noch unklar) &lt;br /&gt;
| Abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 14 &lt;br /&gt;
| Altmann &lt;br /&gt;
| Uwe &lt;br /&gt;
| Samstag &lt;br /&gt;
| nachmittag gegen 16:00 &lt;br /&gt;
| ja &lt;br /&gt;
| suche für So MfG nach Köln&lt;br /&gt;
|-&lt;br /&gt;
! 15 &lt;br /&gt;
| Behrens &lt;br /&gt;
| Thorsten &lt;br /&gt;
| Samstag &lt;br /&gt;
| mittags (voraussichtlich) &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 16 &lt;br /&gt;
| Lohmaier &lt;br /&gt;
| Christian &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachmittag &lt;br /&gt;
| ja &lt;br /&gt;
| ist gerne scharf, wünscht sich deshalb ein Chili-Ketchup&amp;amp;nbsp;:-))&lt;br /&gt;
|-&lt;br /&gt;
! 17 &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 18 &lt;br /&gt;
| Mantke&lt;br /&gt;
| Andreas&lt;br /&gt;
| Samstag&lt;br /&gt;
| vormittag&lt;br /&gt;
| nicht erforderlich&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geplantes Programm ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Themenvorschläge===&lt;br /&gt;
&lt;br /&gt;
[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]&lt;br /&gt;
&lt;br /&gt;
[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039; (Simon Wilper)&lt;br /&gt;
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
** Mercurial bedienen&lt;br /&gt;
** ./configure-Optionen&lt;br /&gt;
** Build-Tools&lt;br /&gt;
** Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Wie geht es weiter? - QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039; (Mechtilde - Unterpunkte von Uwe Altmann)&lt;br /&gt;
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?&lt;br /&gt;
** Das zielt&lt;br /&gt;
**# auf neue Interessenten&lt;br /&gt;
**# 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.&lt;br /&gt;
**# auf &amp;quot;...haben wir dazu eine Präsi??&amp;quot; ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;QA von Extensionen&amp;#039;&amp;#039;&amp;#039; (Michael)&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Lokalisierungsprozess bei OOo&amp;#039;&amp;#039;&amp;#039; (André)&lt;br /&gt;
** Infos über den Lokalisierungsprozesse bei OOo, verwendete Dateiformate, Tools und Prozesse in der DE-Community&lt;br /&gt;
** eigentlich meine Präsentation von der OOoCon, die aber sicher auch für uns interessant ist&lt;br /&gt;
** original-Abstract:&lt;br /&gt;
::OpenOffice.org supports localization for about 100 languages. 96k words in UI and 433k words for the help making it one of the largest and most complex software localization projects.Although most translation teams share a common process, the tools, used file formats and intra project coordination differ. Within the session we will give a short overview of the recommended translation process. In a second step we will present the way how the German teams works - what tools we use, why we have chosen those tools and why we use the XLIFF file format.&lt;br /&gt;
&lt;br /&gt;
===Samstag===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Begrüßung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* kurze Absprache des Arbeitsplanes&lt;br /&gt;
* Fragen zu Technik&lt;br /&gt;
* Organisatorisches  &lt;br /&gt;
|| Jacqueline Rahemipour&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
* Mercurial bedienen&lt;br /&gt;
* ./configure-Optionen&lt;br /&gt;
* Build-Tools&lt;br /&gt;
* Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
|| Simon Wilper&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Wie sieht der aktuelle Release-Prozess aus?&lt;br /&gt;
* ...&lt;br /&gt;
|| Mechtilde Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:30-14:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Mittagessen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 14:00-15:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Aktuelle Situation im de-Projekt&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Personelle Situation - wo sind derzeit die größten Engpässe?&lt;br /&gt;
* Vakante Position des Ansprechpartners QA&lt;br /&gt;
* Welche Auswirkungen hat die Oracle-Übernahme auf die Motivation der Mithelfer im de-Projekt?&lt;br /&gt;
* Welche Möglichkeiten gibt es, neue aktive Helfer für das de-Projekt zu gewinnen?&lt;br /&gt;
|| Jacqueline Rahemipour, alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 15:30-16:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee und Kuchen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 16:00-Open End&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Bughunting / Diskussion&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen&lt;br /&gt;
* neue Issues aufgeben&lt;br /&gt;
* Fehlersuche&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Sonntag===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-11:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA für Extensions&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Bisher gibt es keinen definierten Prozess für die QA von Extensions. Welche Möglichkeiten gibt es für die Zukunft?&lt;br /&gt;
* ...&lt;br /&gt;
|| Michael Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Kurze Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-13:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Dateiformat-QA: ODF Validierung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was ist Validierung?&lt;br /&gt;
* Standard-konform vs. Interoperabel&lt;br /&gt;
* ...&lt;br /&gt;
|| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Anreise ==&lt;br /&gt;
&lt;br /&gt;
=== S-Bahn ===&lt;br /&gt;
Die S-Bahn-Haltestelle &amp;quot;Essen-Horst (S)&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
=== Bus ===&lt;br /&gt;
Die Haltestelle &amp;quot;Geschwister-Scholl-Str.&amp;quot; der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.&lt;br /&gt;
&lt;br /&gt;
=== PKW ===&lt;br /&gt;
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 &amp;quot;Eisenbahnmuseum&amp;quot;. Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder &amp;quot;Villa-Vogelsang&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Übernachtung ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Verpflegung ==&lt;br /&gt;
&lt;br /&gt;
Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel. &lt;br /&gt;
&lt;br /&gt;
Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Gerne werden Salatspenden angenommen!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Seminarraum ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internet ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Freizeit ==&lt;br /&gt;
&lt;br /&gt;
Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Bade­tücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sonstiges ==&lt;br /&gt;
&lt;br /&gt;
Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochen­ende auf uns allein gestellt, das heißt:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen&lt;br /&gt;
&lt;br /&gt;
* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug &amp;amp; Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräum­arbeiten behilflich sein?&amp;#039;&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165165</id>
		<title>DE/QA-Wochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=165165"/>
		<updated>2010-04-26T13:59:24Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Sonntag */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:DE|QA-Wochenende2010]]&lt;br /&gt;
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}} &lt;br /&gt;
=QA-Wochenende 2010 Linux-Hotel Essen=&lt;br /&gt;
&lt;br /&gt;
== Adresse ==&lt;br /&gt;
&lt;br /&gt;
Linux-Hotel / Villa Vogelsang&amp;lt;br&amp;gt;&lt;br /&gt;
Antonienallee 1&amp;lt;br&amp;gt;&lt;br /&gt;
45279 Essen-Horst&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: 0201 8536-600&amp;lt;br&amp;gt;&lt;br /&gt;
Fax: 0201 8536-605&amp;lt;br&amp;gt;&lt;br /&gt;
E-Mail: rezeption@villa-vogelsang.de&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ansprechpartner / Organisation ==&lt;br /&gt;
&lt;br /&gt;
Jacqueline Rahemipour&amp;lt;br&amp;gt;&lt;br /&gt;
jrahemipour@openoffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: auf Anfrage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Termin ==&lt;br /&gt;
&lt;br /&gt;
30.4.-02.05.10&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Worum geht es? ==&lt;br /&gt;
&lt;br /&gt;
* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren&lt;br /&gt;
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen&lt;br /&gt;
* Erfahrungsaustausch mit erfahrenen QA&amp;#039;lern&lt;br /&gt;
* Konkret anstehende Aufgaben gemeinsam bearbeiten&lt;br /&gt;
* die &amp;quot;schönsten&amp;quot; Bugs finden&lt;br /&gt;
* Die anderen netten Leute aus dem Projekt kennenlernen&lt;br /&gt;
* In geselliger Runde über OOo und die Welt quatschen&lt;br /&gt;
* und vieles mehr&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Angemeldete Teilnehmer  ==&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Nr. &lt;br /&gt;
! Name &lt;br /&gt;
! Vorname &lt;br /&gt;
! Anreise am &lt;br /&gt;
! ggfs. Uhrzeit &lt;br /&gt;
! mit Übernachtung? &lt;br /&gt;
! Bemerkungen&lt;br /&gt;
|-&lt;br /&gt;
! 1 &lt;br /&gt;
| Rahemipour &lt;br /&gt;
| Jacqueline &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 2 &lt;br /&gt;
| Wilper &lt;br /&gt;
| Simon &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 3 &lt;br /&gt;
| Pechlaner &lt;br /&gt;
| Wolfgang &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 13 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier&lt;br /&gt;
|-&lt;br /&gt;
! 4 &lt;br /&gt;
| Schnabel &lt;br /&gt;
| André &lt;br /&gt;
| Freitag &lt;br /&gt;
| gegen 19:30 &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 5 &lt;br /&gt;
| Effenberger &lt;br /&gt;
| Florian &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 18/19 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 6 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Mechtilde &lt;br /&gt;
| vorauss. Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 7 &lt;br /&gt;
| Hackert &lt;br /&gt;
| Thomas &lt;br /&gt;
| Samstag &lt;br /&gt;
| ca. 10:00 &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier (steht aber leider erst kurz vorher wirklich fest, sorry ...&amp;amp;nbsp;:( ) &lt;br /&gt;
|-&lt;br /&gt;
! 8 &lt;br /&gt;
| Stehmann &lt;br /&gt;
| Michael &lt;br /&gt;
| vorauss. Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 9 &lt;br /&gt;
| Brekenfelder &lt;br /&gt;
| Ulf &lt;br /&gt;
| Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 10 &lt;br /&gt;
| Geib &lt;br /&gt;
| Gerald &lt;br /&gt;
| Freitag &lt;br /&gt;
| &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 11 &lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 12 &lt;br /&gt;
| Strohmaier &lt;br /&gt;
| Friedrich &lt;br /&gt;
| Freitag &lt;br /&gt;
| abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 13 &lt;br /&gt;
| Andrae &lt;br /&gt;
| Joost &lt;br /&gt;
| Freitag (noch unklar) &lt;br /&gt;
| Abend &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 14 &lt;br /&gt;
| Altmann &lt;br /&gt;
| Uwe &lt;br /&gt;
| Samstag &lt;br /&gt;
| nachmittag gegen 16:00 &lt;br /&gt;
| ja &lt;br /&gt;
| suche für So MfG nach Köln&lt;br /&gt;
|-&lt;br /&gt;
! 15 &lt;br /&gt;
| Behrens &lt;br /&gt;
| Thorsten &lt;br /&gt;
| Samstag &lt;br /&gt;
| mittags (voraussichtlich) &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 16 &lt;br /&gt;
| Lohmaier &lt;br /&gt;
| Christian &lt;br /&gt;
| Freitag &lt;br /&gt;
| nachmittag &lt;br /&gt;
| ja &lt;br /&gt;
| ist gerne scharf, wünscht sich deshalb ein Chili-Ketchup&amp;amp;nbsp;:-))&lt;br /&gt;
|-&lt;br /&gt;
! 17 &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 18 &lt;br /&gt;
| Mantke&lt;br /&gt;
| Andreas&lt;br /&gt;
| Samstag&lt;br /&gt;
| vormittag&lt;br /&gt;
| nicht erforderlich&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geplantes Programm ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Themenvorschläge===&lt;br /&gt;
&lt;br /&gt;
[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]&lt;br /&gt;
&lt;br /&gt;
[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039; (Simon Wilper)&lt;br /&gt;
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
** Mercurial bedienen&lt;br /&gt;
** ./configure-Optionen&lt;br /&gt;
** Build-Tools&lt;br /&gt;
** Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Wie geht es weiter? - QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039; (Mechtilde - Unterpunkte von Uwe Altmann)&lt;br /&gt;
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?&lt;br /&gt;
** Das zielt&lt;br /&gt;
**# auf neue Interessenten&lt;br /&gt;
**# 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.&lt;br /&gt;
**# auf &amp;quot;...haben wir dazu eine Präsi??&amp;quot; ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;QA von Extensionen&amp;#039;&amp;#039;&amp;#039; (Michael)&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Lokalisierungsprozess bei OOo&amp;#039;&amp;#039;&amp;#039; (André)&lt;br /&gt;
** Infos über den Lokalisierungsprozesse bei OOo, verwendete Dateiformate, Tools und Prozesse in der DE-Community&lt;br /&gt;
** eigentlich meine Präsentation von der OOoCon, die aber sicher auch für uns interessant ist&lt;br /&gt;
** original-Abstract:&lt;br /&gt;
::OpenOffice.org supports localization for about 100 languages. 96k words in UI and 433k words for the help making it one of the largest and most complex software localization projects.Although most translation teams share a common process, the tools, used file formats and intra project coordination differ. Within the session we will give a short overview of the recommended translation process. In a second step we will present the way how the German teams works - what tools we use, why we have chosen those tools and why we use the XLIFF file format.&lt;br /&gt;
&lt;br /&gt;
===Samstag===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Begrüßung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* kurze Absprache des Arbeitsplanes&lt;br /&gt;
* Fragen zu Technik&lt;br /&gt;
* Organisatorisches  &lt;br /&gt;
|| Jacqueline Rahemipour&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
* Mercurial bedienen&lt;br /&gt;
* ./configure-Optionen&lt;br /&gt;
* Build-Tools&lt;br /&gt;
* Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
|| Simon Wilper&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Wie sieht der aktuelle Release-Prozess aus?&lt;br /&gt;
* ...&lt;br /&gt;
|| Mechtilde Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:30-14:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Mittagessen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 14:00-15:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Aktuelle Situation im de-Projekt&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Personelle Situation - wo sind derzeit die größten Engpässe?&lt;br /&gt;
* Vakante Position des Ansprechpartners QA&lt;br /&gt;
* Welche Auswirkungen hat die Oracle-Übernahme auf die Motivation der Mithelfer im de-Projekt?&lt;br /&gt;
* Welche Möglichkeiten gibt es, neue aktive Helfer für das de-Projekt zu gewinnen?&lt;br /&gt;
|| Jacqueline Rahemipour, alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 15:30-16:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee und Kuchen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 16:00-Open End&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Bughunting / Diskussion&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen&lt;br /&gt;
* neue Issues aufgeben&lt;br /&gt;
* Fehlersuche&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Sonntag===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-11:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;QA für Extensions&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Bisher gibt es keinen definierten Prozess für die QA von Extensions. Welche Möglichkeiten gibt es für die Zukunft?&lt;br /&gt;
* ...&lt;br /&gt;
|| Michael Stehmann&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:15-11:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Kurze Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-13:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;Dateiformat-QA: ODF Validierung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* ...&lt;br /&gt;
|| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Anreise ==&lt;br /&gt;
&lt;br /&gt;
=== S-Bahn ===&lt;br /&gt;
Die S-Bahn-Haltestelle &amp;quot;Essen-Horst (S)&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
=== Bus ===&lt;br /&gt;
Die Haltestelle &amp;quot;Geschwister-Scholl-Str.&amp;quot; der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.&lt;br /&gt;
&lt;br /&gt;
=== PKW ===&lt;br /&gt;
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 &amp;quot;Eisenbahnmuseum&amp;quot;. Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder &amp;quot;Villa-Vogelsang&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Übernachtung ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Verpflegung ==&lt;br /&gt;
&lt;br /&gt;
Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel. &lt;br /&gt;
&lt;br /&gt;
Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Gerne werden Salatspenden angenommen!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Seminarraum ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internet ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Freizeit ==&lt;br /&gt;
&lt;br /&gt;
Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Bade­tücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sonstiges ==&lt;br /&gt;
&lt;br /&gt;
Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochen­ende auf uns allein gestellt, das heißt:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen&lt;br /&gt;
&lt;br /&gt;
* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug &amp;amp; Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräum­arbeiten behilflich sein?&amp;#039;&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=164784</id>
		<title>DE/QA-Wochenende2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/QA-Wochenende2010&amp;diff=164784"/>
		<updated>2010-04-21T16:36:53Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Angemeldete Teilnehmer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:DE|QA-Wochenende2010]]&lt;br /&gt;
{{DISPLAYTITLE:QA-Wochenende 2010 im LinuxHotel in Essen}} &lt;br /&gt;
=QA-Wochenende 2010 Linux-Hotel Essen=&lt;br /&gt;
&lt;br /&gt;
== Adresse ==&lt;br /&gt;
&lt;br /&gt;
Linux-Hotel / Villa Vogelsang&amp;lt;br&amp;gt;&lt;br /&gt;
Antonienallee 1&amp;lt;br&amp;gt;&lt;br /&gt;
45279 Essen-Horst&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: 0201 8536-600&amp;lt;br&amp;gt;&lt;br /&gt;
Fax: 0201 8536-605&amp;lt;br&amp;gt;&lt;br /&gt;
E-Mail: rezeption@villa-vogelsang.de&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ansprechpartner / Organisation ==&lt;br /&gt;
&lt;br /&gt;
Jacqueline Rahemipour&amp;lt;br&amp;gt;&lt;br /&gt;
jrahemipour@openoffice.org&amp;lt;br&amp;gt;&lt;br /&gt;
Tel.: auf Anfrage&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Termin ==&lt;br /&gt;
&lt;br /&gt;
30.4.-02.05.10&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Worum geht es? ==&lt;br /&gt;
&lt;br /&gt;
* Hintergründe der Qualitätssicherung und der Lokalisierungsarbeit bei OpenOffice.org erfahren&lt;br /&gt;
* Wichtige Arbeitstechniken und Werkzeuge kennenlernen&lt;br /&gt;
* Erfahrungsaustausch mit erfahrenen QA&amp;#039;lern&lt;br /&gt;
* Konkret anstehende Aufgaben gemeinsam bearbeiten&lt;br /&gt;
* die &amp;quot;schönsten&amp;quot; Bugs finden&lt;br /&gt;
* Die anderen netten Leute aus dem Projekt kennenlernen&lt;br /&gt;
* In geselliger Runde über OOo und die Welt quatschen&lt;br /&gt;
* und vieles mehr&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Angemeldete Teilnehmer  ==&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Nr. &lt;br /&gt;
! Name &lt;br /&gt;
! Vorname &lt;br /&gt;
! Anreise am &lt;br /&gt;
! ggfs. Uhrzeit &lt;br /&gt;
! mit Übernachtung? &lt;br /&gt;
! Bemerkungen&lt;br /&gt;
|-&lt;br /&gt;
! 1 &lt;br /&gt;
| Rahemipour &lt;br /&gt;
| Jacqueline &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 2 &lt;br /&gt;
| Wilper &lt;br /&gt;
| Simon &lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 14 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 3 &lt;br /&gt;
| Pechlaner &lt;br /&gt;
| Wolfgang&lt;br /&gt;
| Freitag &lt;br /&gt;
| ca. 13 Uhr &lt;br /&gt;
| ja &lt;br /&gt;
| Vegetarier&lt;br /&gt;
|-&lt;br /&gt;
! 4 &lt;br /&gt;
| Schnabel &lt;br /&gt;
| André &lt;br /&gt;
| Freitag &lt;br /&gt;
| gegen 19:30 &lt;br /&gt;
| ja &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 5 &lt;br /&gt;
| Effenberger&lt;br /&gt;
| Florian&lt;br /&gt;
| Freitag&lt;br /&gt;
| ca. 15/16 Uhr&lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 6 &lt;br /&gt;
| Stehmann&lt;br /&gt;
| Mechtilde&lt;br /&gt;
| vorauss. Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 7 &lt;br /&gt;
| Hackert&lt;br /&gt;
| Thomas&lt;br /&gt;
| Samstag&lt;br /&gt;
| ca. 10:00&lt;br /&gt;
| ja&lt;br /&gt;
| Vegetarier (steht aber leider erst kurz vorher wirklich fest, sorry ... :( )&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
! 8 &lt;br /&gt;
| Stehmann&lt;br /&gt;
| Michael&lt;br /&gt;
| vorauss. Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 9 &lt;br /&gt;
| Brekenfelder&lt;br /&gt;
| Ulf&lt;br /&gt;
| Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 10 &lt;br /&gt;
| Geib&lt;br /&gt;
| Gerald&lt;br /&gt;
| Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 11 &lt;br /&gt;
| Werner&lt;br /&gt;
| Alexander&lt;br /&gt;
| Freitag&lt;br /&gt;
| &lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 12 &lt;br /&gt;
| Strohmaier&lt;br /&gt;
| Friedrich&lt;br /&gt;
| Freitag&lt;br /&gt;
| abend&lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 13 &lt;br /&gt;
| Andrae&lt;br /&gt;
| Joost&lt;br /&gt;
| Freitag (noch unklar)&lt;br /&gt;
| Abend&lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 14 &lt;br /&gt;
| Altmann&lt;br /&gt;
| Uwe&lt;br /&gt;
| Samstag&lt;br /&gt;
| nachmittag gegen 16:00&lt;br /&gt;
| ja&lt;br /&gt;
| suche für So MfG nach Köln &lt;br /&gt;
|-&lt;br /&gt;
! 15 &lt;br /&gt;
| Behrens&lt;br /&gt;
| Thorsten&lt;br /&gt;
| Samstag&lt;br /&gt;
| mittags (voraussichtlich)&lt;br /&gt;
| ja&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 16 &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 17 &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
! 18 &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Geplantes Programm ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Themenvorschläge===&lt;br /&gt;
&lt;br /&gt;
[Programm für 2010 ist noch im Entwurfsstatus - Weitere Vorschläge bitte an dev@de.openoffice.org oder direkt an Jacqueline senden]&lt;br /&gt;
&lt;br /&gt;
[http://wiki.services.openoffice.org/wiki/Talk:DE/QA-Wochenende2010 Diskussion]&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;OpenOffice.org unter Linux x86 selber bauen -- RELOADED&amp;#039;&amp;#039;&amp;#039; (Simon Wilper)&lt;br /&gt;
** Was hat sich im Build-Prozess seit dem letzten Mal (3 Jahre) getan?&lt;br /&gt;
** Mercurial bedienen&lt;br /&gt;
** ./configure-Optionen&lt;br /&gt;
** Build-Tools&lt;br /&gt;
** Fehlerbehebung anhand eines Beispiels&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Wie geht es weiter? - QA und Release-Prozess in der Community&amp;#039;&amp;#039;&amp;#039; (Mechtilde - Unterpunkte von Uwe Altmann)&lt;br /&gt;
** Nehmen wir mal an, ich wüsste nix von QA - was muss ich wissen und was müsste ich tun um mitzuwirken?&lt;br /&gt;
** Das zielt&lt;br /&gt;
**# auf neue Interessenten&lt;br /&gt;
**# 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.&lt;br /&gt;
**# auf &amp;quot;...haben wir dazu eine Präsi??&amp;quot; ein klare Antwort oder zumindest eine link zu haben, wäre schon komfortabel.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;QA von Extensionen&amp;#039;&amp;#039;&amp;#039; (Michael)&lt;br /&gt;
&lt;br /&gt;
===Samstag===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Begrüßung&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* kurze Absprache des Arbeitsplanes&lt;br /&gt;
* Fragen zu Technik&lt;br /&gt;
* Organisatorisches  &lt;br /&gt;
|| Jacqueline Rahemipour&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:15-11:15&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:30-12:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:30-14:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Mittagessen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 14:00-15:30&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 15:30-16:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Pause&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;Kaffee und Kuchen&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 16:00-17:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
! 17:00-Open End&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;Bughunting&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* gemeldete Fehler nachvollziehen u. im Issue-Tracker bestätigen&lt;br /&gt;
* neue Issues aufgeben&lt;br /&gt;
* Fehlersuche&lt;br /&gt;
|| alle&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===Sonntag===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;120&amp;quot; |Wann?&lt;br /&gt;
! width=&amp;quot;480&amp;quot; | Was?&lt;br /&gt;
! width=&amp;quot;180&amp;quot; | Wer?&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 10:00-10:45&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 11:00-11:45&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
! 12:00-13:00&lt;br /&gt;
|| &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* &lt;br /&gt;
|| &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Anreise ==&lt;br /&gt;
&lt;br /&gt;
=== S-Bahn ===&lt;br /&gt;
Die S-Bahn-Haltestelle &amp;quot;Essen-Horst (S)&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
=== Bus ===&lt;br /&gt;
Die Haltestelle &amp;quot;Geschwister-Scholl-Str.&amp;quot; der Buslinien 184 und NE5 sind weniger als 5 Minuten entfernt.&lt;br /&gt;
&lt;br /&gt;
=== PKW ===&lt;br /&gt;
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 &amp;quot;Eisenbahnmuseum&amp;quot;. Ab Dahlhauser Str. ist das Linux-Hotel direkt ausgeschildert, achtet dort auf die Schilder &amp;quot;Villa-Vogelsang&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Übernachtung ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Verpflegung ==&lt;br /&gt;
&lt;br /&gt;
Auch Verpflegung am Wochenende wird vom Verein OOo Deutschland e.V. finanziert. Das Frühstück erhalten wir direkt im Linux-Hotel. &lt;br /&gt;
&lt;br /&gt;
Je nach Wetterlage wollen wir Freitag abend bzw. Samstag abend den Grill anmachen. Fleisch und Würstchen werden organisiert.&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Gerne werden Salatspenden angenommen!&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
Bei schlechtem Wetter weichen wir auf den örtlichen Pizza-Service aus. Für Samstag mittag ist ein kalter Snack vorgesehen.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wichtig: Vegetarier möchten sich bitte vorher melden, dann können wir für den Grillabend Alternativen anbieten.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Seminarraum ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internet ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Freizeit ==&lt;br /&gt;
&lt;br /&gt;
Es gibt eine Sauna und einen Fitnessraum, die wir nach Absprache benutzen können. Bade­tücher und Bademäntel sind vorhanden, alles weitere bitte mitbringen.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Sonstiges ==&lt;br /&gt;
&lt;br /&gt;
Da das Linux-Hotel keine Personalkosten bezahlen möchte, sind wir an dem Wochen­ende auf uns allein gestellt, das heißt:&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Wir müssen den Seminarraum sauber hinterlassen (Sonntag einmal durchwischen) und gegebenenfalls die Tische und Stühle wieder zusammenräumen&lt;br /&gt;
&lt;br /&gt;
* Die Zimmer werden an uns sauber übergeben und dann aber nicht vom Hotel aus gemacht (= 2 Nächte gleiches Bettzeug &amp;amp; Handtücher). Bei Abreise bitte die Betten abziehen, den Rest übernimmt das Linux-Hotel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wer hat am Sonntag ab ca. 14 Uhr noch ein wenig Zeit und kann bei den Aufräum­arbeiten behilflich sein?&amp;#039;&amp;#039;&amp;#039;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=File:Thorsten.jpg&amp;diff=161423</id>
		<title>File:Thorsten.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=File:Thorsten.jpg&amp;diff=161423"/>
		<updated>2010-03-29T11:56:52Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=DE/CeBIT2010&amp;diff=157798</id>
		<title>DE/CeBIT2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=DE/CeBIT2010&amp;diff=157798"/>
		<updated>2010-02-23T09:52:33Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Personalplan */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:OpenOffice.org-Gemeinschaftsstand auf der CeBIT 2010}} &lt;br /&gt;
&lt;br /&gt;
= Einführung  =&lt;br /&gt;
&lt;br /&gt;
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]. &lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;&amp;#039;&amp;#039;&amp;#039;Halle 2, Stand D38-137&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
[http://files.messe.de/cmsdb/D/007/1978.pdf Hallenplan]&lt;br /&gt;
&lt;br /&gt;
[http://files.messe.de/cmsdb/D/007/10985.pdf Geländeplan]&lt;br /&gt;
&lt;br /&gt;
[http://files.messe.de/cmsdb/D/007/17554.pdf Übersichtsplan mit Parkplätzen]&lt;br /&gt;
&lt;br /&gt;
Der Stand ist in der Nähe des Eingangs Nord (Stadtbahnhaltestelle). &lt;br /&gt;
Für Pkw-Anreisende ist Parkplatz Ost zu empfehlen, auf den man in der Regel geleitet wird wenn man auf dem Messeschnellweg die linken Fahrstreifen benutzt.&lt;br /&gt;
&lt;br /&gt;
= Personalplan&amp;#039;&amp;#039;&amp;#039;&amp;lt;u&amp;gt;&amp;lt;br&amp;gt;&amp;lt;/u&amp;gt;&amp;#039;&amp;#039;&amp;#039;  =&lt;br /&gt;
&lt;br /&gt;
{| align=&amp;quot;center&amp;quot; width=&amp;quot;100%&amp;quot; class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Name&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;(Ticket) &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Montag, 1. März&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&amp;#039;&amp;#039;&amp;#039;(Aufbautag)&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Dienstag, 2. März&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Mittwoch, 3. März&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Donnerstag, 4. März&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Freitag, 5. März&amp;#039;&amp;#039;&amp;#039; &lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Samstag, 6. März&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&amp;#039;&amp;#039;&amp;#039;(Abbau am Abend)&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:floeff@openoffice.org Effenberger, Florian]&amp;lt;br&amp;gt;(Presseticket) &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:thomaskrumbein@openoffice.org Krumbein, Thomas]&amp;lt;br&amp;gt;(Presseticket)&lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:jrahemipour@openoffice.org Rahemipour, Jacqueline] &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:simonaw@openoffice.org Wilper, Simon] &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:andreschnabel@openoffice.org Schnabel,André] &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| (evtl.) &lt;br /&gt;
| X&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:uwealtmann@openoffice.org Altmann, Uwe] &lt;br /&gt;
| (bei Bedarf) &lt;br /&gt;
| X &lt;br /&gt;
| X &lt;br /&gt;
| X (nur vorm.) &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| [mailto:lothar.becker@riess.de Becker, Lothar] &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| X &lt;br /&gt;
| X&amp;amp;nbsp;(nur vorm.)&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:christoph@dogmatux.com Noack, Christoph]&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| X&lt;br /&gt;
| X (ggf. nur vorm.)&lt;br /&gt;
|-&lt;br /&gt;
| Wolfgang Uhlig&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| X&lt;br /&gt;
| X (Vormittag)&lt;br /&gt;
|-&lt;br /&gt;
| Andreas Mantke&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| X (im Laufe des Vormittags)&lt;br /&gt;
| X&lt;br /&gt;
| X&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:volkerme@openoffice.org Merschmann,Volker] &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| (x)&lt;br /&gt;
| x (einschl. Abbau)&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:thb@openoffice.org Thorsten Behrens] &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| x (abends)&lt;br /&gt;
| x (einschl. Abbau) &lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:De.openoffice.org]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Build_Environment_Effort/New_Build_System_Requirements&amp;diff=156099</id>
		<title>Build Environment Effort/New Build System Requirements</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Build_Environment_Effort/New_Build_System_Requirements&amp;diff=156099"/>
		<updated>2010-02-01T17:43:45Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Build Environment Effort}}&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
This page lists the requirements for a new build system for OpenOffice.org. In addition, it discusses how easy or hard these aims are archiveable with different alternatives.&lt;br /&gt;
&lt;br /&gt;
== Build Configuration ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (autoconf)&amp;#039;&amp;#039;&amp;#039;: Autoconf is a huge old mess, but it has lean deps (POSIX sh) as long as there are no needs to change the configuration. A huge part of the configuration is custom code and not standard autoconf macros.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: GNU make does not provide a configuration tool itself. So one would continue to use autoconf or another configuration system.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: CMake provides tools to check the configuration of the build system, but since OOo uses only a few standard checks, a lot of code would need to be rewritten.&lt;br /&gt;
&lt;br /&gt;
== Lean dependencies ==&lt;br /&gt;
To ensure a long life and maximum portability (even to platforms that might not even be available yet) for the new build system it should depend on as little as possible.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (build.pl and dmake)&amp;#039;&amp;#039;&amp;#039;: The current build system has fat dependencies. It depends directly on Perl and dmake (which has to be maintained by OOo development). In addition a wide range of tools are being used: zip, awk, GNU coreutils, GNU findutils, ant (please add more ...)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: GNU make is lean in its direct dependencies -- it is part of the GNU toolchain and thus available on all platforms where gcc is available.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: CMake aims to be highly portable, but it is not usually available on the default install of  many platforms. Also it does not build itself, but requires another native build system to be available on the platform for that task (GNU make on unix).&lt;br /&gt;
&lt;br /&gt;
== Debugging ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (build.pl and dmake)&amp;#039;&amp;#039;&amp;#039;: The current build system is not easy to debug because its code is old and the used tools are too adding needless complexity (Perl, dmake).&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: The new implementation is very clean. It should be a lot easier to debug and use for common developers.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: CMakes BuildLists are clean and well documentented. CMake generates native build system files. Failures in the generated makefiles might be a lot harder to track down to their source.&lt;br /&gt;
&lt;br /&gt;
== &amp;quot;Native&amp;quot; Builds on Windows (msbuild) ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (build.pl and dmake)&amp;#039;&amp;#039;&amp;#039;: The current build system does not provide a native Windows build using msbuild.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: It is not very hard to generate msbuild files from GNU make for common build tasks. However, there are many cases where the current build process depends on a large set of external tools like bash, awk, findutils, coreutils. Doing a &amp;quot;native&amp;quot; build that requires cygwin and a wide range of other tools does make little sense.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: CMake provides native builds for common tasks. However, there are many cases where the current build process depends on a large set of external tools like bash, awk, findutils, coreutils. Doing a &amp;quot;native&amp;quot; build that requires cygwin and a wide range of other tools does make little sense. cmakes ability to generate msbuild files for common build tasks only solves a part of the problem as a &amp;quot;native build&amp;quot; that requires a lot of external tools has little to no added value.&lt;br /&gt;
{{Documentation/Note|One might consider using Python as a tool for _all_ non-standard build tasks. Python is easy to distribute and install on all platforms. However, it is also a very fat dependency and thus it is questionable, if it would be worth the effort just to get rid of cygwin (or another Unix environment on windows).}}&lt;br /&gt;
&lt;br /&gt;
== Dependency generation ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (build.pl and dmake)&amp;#039;&amp;#039;&amp;#039;: The current build system uses a set of mostly redundant dependency generators: a selfmaintained mkdepend, a selfmaintained rscdep ...&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: The GNU make prototype uses the dependency generator of the compiler where possible. On platforms, where these are not available, a externally maintained generator is considered for use (mcpp was the first choice, but might be to slow as it does very thorough syntax checks)&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: CMake has its own dependency generation. It has to be checked, if that generator can be used for all deps needed in OOo build (resource files etc.)&lt;br /&gt;
&lt;br /&gt;
== Parallelization ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (build.pl and dmake)&amp;#039;&amp;#039;&amp;#039;: The current build system uses a two-step approach (build.pl starts one dmake process per directory). Its a bit like a recursive make system limited to depth two. However, build.pl and dmake do not even communicate the number of running processes (like a GNU make would do with its jobserver).&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: The common approach with CMake is also to use recursive makefiles (one per library). This hinders paralellization in that object files of a library are not compiled (although compilable) unless all libs that are linked against are completely linked (although those are only required at linktime). &lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: The GNU make prototype handles all deps in one process and thus can compile all object files ASAP.&lt;br /&gt;
&lt;br /&gt;
== Code Quality ==&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Current build system (build.pl and dmake)&amp;#039;&amp;#039;&amp;#039;: very low - quite often ad-hoc, procedural coding of tasks.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;: The GNU make prototype employs a declarative way of specifying tasks, but commonly violates the DRY principle.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;cmake&amp;#039;&amp;#039;&amp;#039;: CMake has a reasonably brief and declarative syntax.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;GNU make + custom generator&amp;#039;&amp;#039;&amp;#039;: see &amp;#039;&amp;#039;&amp;#039;GNU make&amp;#039;&amp;#039;&amp;#039;, enforces declarativeness, eliminates the boilerplate. Also, additional constraints can be expressed.&lt;br /&gt;
&lt;br /&gt;
*&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=155736</id>
		<title>Conferences/FOSDEM/2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=155736"/>
		<updated>2010-01-26T16:41:15Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Team */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium&lt;br /&gt;
 &lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
==Communication Channel==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==DevRoom==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Call for Papers===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Some things that should be taken into account &lt;br /&gt;
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),&lt;br /&gt;
* a short abstract (1-2 paragraphs),&lt;br /&gt;
* a longer description if appropriate,&lt;br /&gt;
* optionally a list of links to the project website or similar&lt;br /&gt;
* for each speaker:&lt;br /&gt;
** the speaker&amp;#039;s real name,&lt;br /&gt;
** a short overview of her bio in a couple of lines,&lt;br /&gt;
** optionally also a longer bio,&lt;br /&gt;
** optionally a picture (please send it to Juergen as 128x128 PNG),&lt;br /&gt;
** optionally links to her website, blog, ... &lt;br /&gt;
&lt;br /&gt;
We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.&lt;br /&gt;
&lt;br /&gt;
====Proposals====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Schedule===&lt;br /&gt;
&lt;br /&gt;
Changes are still possible&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ DevRoom Overview&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;[http://www.fosdem.org/2010/schedule/devrooms/openofficeorg OpenOffice.org DevRoom]&amp;#039;&amp;#039;&amp;#039;, Building AW, Room AW1.120&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Time !! Title !! Session type !! Slides !!Speaker&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;OpenOffice.org&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 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]]&lt;br /&gt;
|-&lt;br /&gt;
| 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 &amp;amp; extension integration]] || talk || ? || Carsten Driesner&lt;br /&gt;
|- &lt;br /&gt;
| 14:30 - 15:15 || [[Conferences/FOSDEM/2010/CFP#Improving_the_OpenOffice.org_Build_System|Improving the OpenOffice.org Build System]] || talk || ? || Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| 15:15 - 16:00 || [[Conferences/FOSDEM/2010/CFP#Just_Testing|Just Testing]] || talk || ? || Stephan Bergmann &lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 16:45 || [[Conferences/FOSDEM/2010/CFP#Show_me_YOUR_code|Show me YOUR code]] || workshop || ? || [[User:ErAck|Eike Rathke]]&lt;br /&gt;
|-&lt;br /&gt;
| 16:45 - 17:30 || [[Conferences/FOSDEM/2010/CFP#Hidden_Pearls_-_What.27s_There_to_ReUse_for_Other_Projects|Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects]]  || talk || ? || Thorsten Behrens&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 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]&lt;br /&gt;
|-&lt;br /&gt;
| 18:00 - 18:30 || [[Conferences/FOSDEM/2010/CFP#ODF_on_the_server_-_ODFDOM_architecture|ODF on the server - ODFDOM architecture]] || talk || ? || Svante Schubert&lt;br /&gt;
|-&lt;br /&gt;
| 18:30 - 19:00 || [[Conferences/FOSDEM/2010/CFP#lpOD_.E2.80.93_languages_.26_platforms_OpenDocument|lpOD – languages &amp;amp; platforms OpenDocument]] || talk || ? || Luis Belmar Letelier&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Stand/Booth ==&lt;br /&gt;
&lt;br /&gt;
Our stand will be most probably in building AW &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Stand Overview &lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Time &lt;br /&gt;
! Stand staff&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Saturday 6th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 &lt;br /&gt;
| floeff, jsc, lmo, sb, sophi, b_michaelsen&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 &lt;br /&gt;
| floeff, lmo, er, sophi, thb&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 &lt;br /&gt;
| floeff, cno, lmo, sophi, cd&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 18:00 &lt;br /&gt;
| floeff, jsc, cno, lmo, sophi, b_michaelsen&amp;lt;br&amp;gt;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;4&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sunday 7th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 &lt;br /&gt;
| probably floeff, jsc, sophi, b_michaelsen, thb&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 &lt;br /&gt;
| jsc, cno, sb, sophi, cd&lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 &lt;br /&gt;
| cno, er, sophi&lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 17:00 &lt;br /&gt;
| cno, sophi&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Stand material ===&lt;br /&gt;
* sophi: I&amp;#039;ll bring a coffee machine, tea and coffee, water, biscuits and cakes. Plugs, scissors, etc... A blue table coth. What else?&lt;br /&gt;
* jsc: i will bring 3 posters, stickers and t-shirts. All with the same design!&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:fosdem_design.png|thumb|left|150px|FOSDEM design]] || valign=&amp;quot;top&amp;quot; | [[File:fosdem_design.pdf]] || valign=&amp;quot;top&amp;quot; | design background:&amp;lt;br&amp;gt;- the squirl stands for a moving, rotating, active, vital community&amp;lt;br&amp;gt;- the cubes stand for the many, many individuals&amp;lt;br&amp;gt;- and the different colors stand for different countries, continents.  &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Saturday Evening OOo Community Event==&lt;br /&gt;
===Where===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;[http://www.sensum.be/en/resto/show/l-achepot?Brussels L&amp;#039;Achepot]&amp;#039;&amp;#039;&amp;#039; (Gourmet Bistro)&lt;br /&gt;
&lt;br /&gt;
Place Sainte-Catherine, 1 - 1000 Brussels - Tel : +32 (0)2 511 62 21&lt;br /&gt;
&lt;br /&gt;
Open from 12h to 14h30 and from 19h to 22h45.&lt;br /&gt;
&lt;br /&gt;
===When===&lt;br /&gt;
8:00pm?&lt;br /&gt;
&lt;br /&gt;
== Team  ==&lt;br /&gt;
&lt;br /&gt;
...details will coming soon &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Name &lt;br /&gt;
! Stay &lt;br /&gt;
! Function &lt;br /&gt;
! Funding request &lt;br /&gt;
! Dinner on Saturday&lt;br /&gt;
|-&lt;br /&gt;
| Juergen Schmidt &lt;br /&gt;
| Friday - Sunday &lt;br /&gt;
| Stand/DevRoom &lt;br /&gt;
| 140 Euro hotel, ~150 Euro fuel &lt;br /&gt;
| yes&lt;br /&gt;
|-&lt;br /&gt;
| Florian Effenberger&amp;lt;br&amp;gt; &lt;br /&gt;
| Friday-Sunday &lt;br /&gt;
| Stand/Marketing &lt;br /&gt;
| yes (approx. 250-300 EUR)&amp;lt;br&amp;gt; &lt;br /&gt;
| yes&lt;br /&gt;
|-&lt;br /&gt;
| Cor Nouws [cno]&amp;lt;br&amp;gt; &lt;br /&gt;
| both days &lt;br /&gt;
| Stand/Marketing &lt;br /&gt;
| 70 Euro Hotel, 90 Euro train &lt;br /&gt;
| &amp;amp;nbsp;?&lt;br /&gt;
|-&lt;br /&gt;
| Jacqueline Rahemipour &lt;br /&gt;
| both days &lt;br /&gt;
| &lt;br /&gt;
| 120 Eur hotel, 90 Eur train &lt;br /&gt;
| &amp;amp;nbsp;?&lt;br /&gt;
|-&lt;br /&gt;
| Eike Rathke &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel, ~150 Euro fuel &lt;br /&gt;
| yes, 2 persons&lt;br /&gt;
|-&lt;br /&gt;
| Thorsten Behrens &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 124 Euro hotel, 140 Euro airfare &lt;br /&gt;
| yes&lt;br /&gt;
|-&lt;br /&gt;
| Bjoern Michaelsen &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel &lt;br /&gt;
| &amp;amp;nbsp;?&lt;br /&gt;
|-&lt;br /&gt;
| Stephan Bergmann &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel &lt;br /&gt;
| yes&lt;br /&gt;
|-&lt;br /&gt;
| Carsten Driesner &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel, ~150 Euro fuel &lt;br /&gt;
| &amp;amp;nbsp;?&lt;br /&gt;
|-&lt;br /&gt;
| Leo Moons &lt;br /&gt;
| Saturday &lt;br /&gt;
| Stand &lt;br /&gt;
| no &lt;br /&gt;
| yes&lt;br /&gt;
|-&lt;br /&gt;
| Sophie Gautier &lt;br /&gt;
| both days &lt;br /&gt;
| Stand &lt;br /&gt;
| no &lt;br /&gt;
| yes, 2 persons&lt;br /&gt;
|-&lt;br /&gt;
| Louis Suarez-Potts &lt;br /&gt;
| Friday-Sunday &lt;br /&gt;
| Stand &lt;br /&gt;
| &amp;amp;nbsp;? &lt;br /&gt;
| &amp;amp;nbsp;?&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Hotel Recommendation==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&amp;amp;Sleep 59 Euro &lt;br /&gt;
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
&lt;br /&gt;
Feel free to insert some more recommendations.&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Mercurial/Tips_And_Tricks&amp;diff=155362</id>
		<title>Mercurial/Tips And Tricks</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Mercurial/Tips_And_Tricks&amp;diff=155362"/>
		<updated>2010-01-21T09:51:19Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Strip an unwanted branch */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Mercurial}}&lt;br /&gt;
This is the page to add your favorite Mercurial tip.&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= Tips and Tricks =&lt;br /&gt;
&lt;br /&gt;
== Preparing a local repo for a cws ==&lt;br /&gt;
* If you want to create a local repo for an existing cws, take care to clone &amp;#039;&amp;#039;to the milestone of the cws&amp;#039;&amp;#039;.&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
hg clone -r &amp;lt;CWS_milestone&amp;gt; &amp;lt;local_prestine copy&amp;gt; &amp;lt;local_cws_repo&amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
{{Documentation/Caution|If the cws is on &amp;lt;code&amp;gt;DEV300_m60&amp;lt;/code&amp;gt; and you pull it into a local repo that is on &amp;lt;code&amp;gt;DEV300_m61&amp;lt;/code&amp;gt;, you will create new heads in the local repo. If you not comfortable in handling multiple heads, then &amp;#039;&amp;#039;&amp;#039;dont do that!&amp;#039;&amp;#039;&amp;#039;}}&lt;br /&gt;
&lt;br /&gt;
== After pulling/merging ==&lt;br /&gt;
* &amp;lt;code&amp;gt;hg log --follow-first&amp;lt;/code&amp;gt; is a convenient way to display your CWS changes at the top of the log.&lt;br /&gt;
* &amp;lt;code&amp;gt;hg log --follow-first -P &amp;lt;original_clone_milestone&amp;gt;&amp;lt;/code&amp;gt; will show only the CWS changesets.&lt;br /&gt;
* &amp;lt;code&amp;gt;hg outgoing&amp;lt;/code&amp;gt; works as well, of course.&lt;br /&gt;
== Combined diff which contains exactly the changes of your CWS without anything pulled from master ==&lt;br /&gt;
If your current milestone tag is locally available:&lt;br /&gt;
  hg diff -r &amp;lt;current_milestone_tag&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If your current milestone tag is *not* locally available (might happen, see above):&lt;br /&gt;
* search for your last pull/merge from the master with &lt;br /&gt;
  hg log -m&lt;br /&gt;
* then&lt;br /&gt;
  hg diff -r &amp;lt;second_parent_of_last_master_merge&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, if you just did a pull/merge from master:&lt;br /&gt;
  hg export --switch-parent tip&lt;br /&gt;
&lt;br /&gt;
Yet alternatively, just do&lt;br /&gt;
  hg outgoing &amp;lt;master_repository&amp;gt; -p --template &amp;#039;\n&amp;#039;&lt;br /&gt;
&lt;br /&gt;
== obtain a list of all modules which contain changes ==&lt;br /&gt;
&lt;br /&gt;
Sometimes, it is interesting to know which modules in your CWS actually contain changes. That&amp;#039;s quite easy to find out with&lt;br /&gt;
  hg out -q -M --template &amp;#039;{files}\n&amp;#039; &amp;lt;master_repository&amp;gt; | tr &amp;#039; &amp;#039; \\n | sed &amp;quot;s#/.*##&amp;quot; | sort | uniq&lt;br /&gt;
&lt;br /&gt;
== Styles ==&lt;br /&gt;
The default output format of some commands does not suit you? Use styles:&lt;br /&gt;
*&amp;lt;code&amp;gt;hg log --style=compact&amp;lt;/code&amp;gt;&lt;br /&gt;
*&amp;lt;code&amp;gt;hg outgoing --style=changelog&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
* Or create your own format with the template engine:&lt;br /&gt;
** &amp;lt;code&amp;gt;hg outgoing --template &amp;#039;{date|shortdate} {author|person} {desc}\n&amp;#039; --newest-first&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== On Windows/cygwin ==&lt;br /&gt;
=== TortoiseHg ===&lt;br /&gt;
Depending on the cygwin version, using cygwins hg (and other tools) sometimes fails. TortoiseHg (http://bitbucket.org/tortoisehg/stable/wiki/Home) can be used as alternative.&lt;br /&gt;
&lt;br /&gt;
To get rid of cygwin&amp;#039;s hg rename &amp;lt;code&amp;gt;/usr/bin/hg&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
You can decide which ssl support you use in the cygwin shell. &lt;br /&gt;
If you want to use the ssh-agent then you have to specify the following line in the &amp;lt;code&amp;gt;[ui]&amp;lt;/code&amp;gt; section of &amp;lt;code&amp;gt;~/.hgrc&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
ssh = &amp;lt;Windows path to cygwin&amp;gt;\bin\ssh.exe -C&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the graphical interface of TortoiseHg Putty&amp;#039;s pageant is the default ssh key provider. TortoiseHg allows easy graphical access to hg repositories within the Windows Explorer.&lt;br /&gt;
&lt;br /&gt;
==== Accessing repository over ssh ==== &lt;br /&gt;
* If you want to use the ssh client of your Cygwin shell (and also ssh-agent), add the following to the &amp;lt;code&amp;gt;[ui]&amp;lt;/code&amp;gt; section of your &amp;lt;code&amp;gt;mercurial.ini&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
ssh = ssh -C&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
== Handling multiple heads ==&lt;br /&gt;
=== Getting rid of multiple heads ===&lt;br /&gt;
When you accidentally created a repo with multiple heads, these are the possibilities to get rid of them:&lt;br /&gt;
==== Merge heads ====&lt;br /&gt;
* &amp;lt;code&amp;gt;hg merge&amp;lt;/code&amp;gt; This is the easiest possibility.&lt;br /&gt;
{{Documentation/Note|However, keep in mind, that everything you merged will end up in the master if the merged head gets integrated.}}&lt;br /&gt;
&lt;br /&gt;
==== Strip an unwanted branch ====&lt;br /&gt;
* [[hg:Strip|hg strip]] can be used to get rid of the unwanted branch. It is provided by the Mq Extension.&lt;br /&gt;
{{Documentation/Caution|Be very careful when using it as it deletes history from your repository! Use rev hashes instead of rev numbers, as the latter are changing under strip!}}&lt;br /&gt;
&lt;br /&gt;
=== Updating with multiple heads ===&lt;br /&gt;
Updating your working copy is a bit more complex when there are multiple heads in the repo. Quoth &amp;lt;code&amp;gt;hg up --help&amp;lt;/code&amp;gt;:&lt;br /&gt;
&amp;lt;cite&amp;gt;&lt;br /&gt;
    Update the repository&amp;#039;s working directory to the specified&lt;br /&gt;
    revision, or the tip &amp;#039;&amp;#039;&amp;#039;of the current branch&amp;#039;&amp;#039;&amp;#039; if none is specified.&lt;br /&gt;
    Use null as the revision to remove the working copy (like &amp;#039;hg&lt;br /&gt;
    clone -U&amp;#039;).&lt;br /&gt;
&amp;lt;/cite&amp;gt;&lt;br /&gt;
So, if you clone a repo up to &amp;lt;code&amp;gt;DEV300_m62&amp;lt;/code&amp;gt; creating a working copy of its tip, and then pull a &amp;lt;code&amp;gt;DEV300_m60&amp;lt;/code&amp;gt;-based cws and do a &amp;lt;code&amp;gt;hg up&amp;lt;/code&amp;gt; you will not be on the tip of the cws, because Mercurial will not switch branches. If you want that, you would need a &amp;lt;code&amp;gt;hg up -C -r tip&amp;lt;/code&amp;gt;.&lt;br /&gt;
{{Documentation/Caution|Be careful, as this destroys any uncommited changes on the working copy. See &amp;lt;code&amp;gt;hg up --help&amp;lt;/code&amp;gt; for details.}}&lt;br /&gt;
&lt;br /&gt;
=== Containing multiple heads locally ===&lt;br /&gt;
If you (for whatever reason) have multiple heads in a local repo, pushing to outgoing will fail because it would create new heads. In this case you can specify one head and push only that one and if no new heads will be created this way, everything will work fine. Use &amp;lt;code&amp;gt;hg heads&amp;lt;/code&amp;gt; to find the head you want to push and then use&lt;br /&gt;
&lt;br /&gt;
 hg push -r &amp;lt;changeset_id_of _selected_head&amp;gt;&lt;br /&gt;
&lt;br /&gt;
to push this head.&lt;br /&gt;
&lt;br /&gt;
{{Documentation/Caution|You should never create multiple heads on an outgoing repo unless you really know what you are doing, because &amp;#039;&amp;#039;&amp;#039;you will need to merge the heads anyway if you want your cws to be integrated someday&amp;#039;&amp;#039;&amp;#039;, and thus you can do the merge before pushing just as well.}}&lt;br /&gt;
&lt;br /&gt;
== Using interwiki links to hg-wiki ==&lt;br /&gt;
You can use interwiki links to Mercurial wiki e.g. [[hg:OtherTools]]. This is may be helpful for documentation links direct to hg-wiki. Try it!&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=154847</id>
		<title>Conferences/FOSDEM/2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=154847"/>
		<updated>2010-01-13T22:21:40Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Stand/Booth */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium&lt;br /&gt;
 &lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
==Communication Channel==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==DevRoom==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Call for Papers===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Some things that should be taken into account &lt;br /&gt;
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),&lt;br /&gt;
* a short abstract (1-2 paragraphs),&lt;br /&gt;
* a longer description if appropriate,&lt;br /&gt;
* optionally a list of links to the project website or similar&lt;br /&gt;
* for each speaker:&lt;br /&gt;
** the speaker&amp;#039;s real name,&lt;br /&gt;
** a short overview of her bio in a couple of lines,&lt;br /&gt;
** optionally also a longer bio,&lt;br /&gt;
** optionally a picture (please send it to Juergen as 128x128 PNG),&lt;br /&gt;
** optionally links to her website, blog, ... &lt;br /&gt;
&lt;br /&gt;
We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.&lt;br /&gt;
&lt;br /&gt;
====Proposals====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Schedule===&lt;br /&gt;
&lt;br /&gt;
Changes are still possible&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ DevRoom Overview&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Time !! Title !! Session type !! Slides !!Speaker&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;OpenOffice.org&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 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]]&lt;br /&gt;
|-&lt;br /&gt;
| 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 &amp;amp; extension integration]] || talk || ? || Carsten Driesner&lt;br /&gt;
|- &lt;br /&gt;
| 14:30 - 15:15 || [[Conferences/FOSDEM/2010/CFP#Improving_the_OpenOffice.org_Build_System|Improving the OpenOffice.org Build System]] || talk || ? || Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| 15:15 - 16:00 || [[Conferences/FOSDEM/2010/CFP#Just_Testing|Just Testing]] || talk || ? || Stephan Bergmann &lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 16:45 || [[Conferences/FOSDEM/2010/CFP#Show_me_YOUR_code|Show me YOUR code]] || workshop || ? || [[User:ErAck|Eike Rathke]]&lt;br /&gt;
|-&lt;br /&gt;
| 16:45 - 17:30 || [[Conferences/FOSDEM/2010/CFP#Hidden_Pearls_-_What.27s_There_to_ReUse_for_Other_Projects|Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects]]  || talk || ? || Thorsten Behrens&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 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]&lt;br /&gt;
|-&lt;br /&gt;
| 18:00 - 18:30 || [[Conferences/FOSDEM/2010/CFP#ODF_on_the_server_-_ODFDOM_architecture|ODF on the server - ODFDOM architecture]] || talk || ? || Svante Schubert&lt;br /&gt;
|-&lt;br /&gt;
| 18:30 - 19:00 || [[Conferences/FOSDEM/2010/CFP#lpOD_.E2.80.93_languages_.26_platforms_OpenDocument|lpOD – languages &amp;amp; platforms OpenDocument]] || talk || ? || ?&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Stand/Booth ==&lt;br /&gt;
&lt;br /&gt;
Our stand will be most probably in building AW &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Stand Overview &lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Time &lt;br /&gt;
! Stand staff&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Saturday 6th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 &lt;br /&gt;
| floeff, jsc, lmo, sb, sophi, b_michaelsen&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 &lt;br /&gt;
| floeff, lmo, er, sophi, andreasma, thb&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 &lt;br /&gt;
| floeff, cno, lmo, sophi, andreasma&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 18:00 &lt;br /&gt;
| floeff, jsc, cno, lmo, sophi, andreasma, b_michaelsen&amp;lt;br&amp;gt;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;4&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sunday 7th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 &lt;br /&gt;
| probably floeff, jsc, sophi, b_michaelsen, thb&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 &lt;br /&gt;
| jsc, cno, sb, sophi&lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 &lt;br /&gt;
| cno, er, sophi&lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 17:00 &lt;br /&gt;
| cno, sophi&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
sophi: I&amp;#039;ll bring a coffee machine, tea and coffee, water, biscuits and cakes. Plugs, scissors, etc... A blue table coth. What else?&lt;br /&gt;
&lt;br /&gt;
==Saturday Evening OOo Community Event==&lt;br /&gt;
...details will coming soon&lt;br /&gt;
&lt;br /&gt;
== Team  ==&lt;br /&gt;
&lt;br /&gt;
...details will coming soon &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Name &lt;br /&gt;
! Stay &lt;br /&gt;
! Function &lt;br /&gt;
! Funding request&lt;br /&gt;
|-&lt;br /&gt;
| Juergen Schmidt &lt;br /&gt;
| Friday - Sunday &lt;br /&gt;
| Stand/DevRoom &lt;br /&gt;
| 140 Euro hotel, ~150 Euro fuel&lt;br /&gt;
|-&lt;br /&gt;
| Florian Effenberger&amp;lt;br&amp;gt; &lt;br /&gt;
| Friday-Sunday &lt;br /&gt;
| Stand/Marketing &lt;br /&gt;
| yes (approx. 250-300 EUR)&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Cor Nouws [cno]&amp;lt;br&amp;gt; &lt;br /&gt;
| both days &lt;br /&gt;
| Stand/Marketing &lt;br /&gt;
| 70 Euro Hotel, 90 Euro train&lt;br /&gt;
|-&lt;br /&gt;
| Andrea Pescetti &lt;br /&gt;
| one day only (unsure) &lt;br /&gt;
| &amp;amp;nbsp;? &lt;br /&gt;
| no&lt;br /&gt;
|-&lt;br /&gt;
| Jacqueline Rahemipour &lt;br /&gt;
| both days &lt;br /&gt;
| &lt;br /&gt;
| 120 Eur hotel, 90 Eur train&lt;br /&gt;
|-&lt;br /&gt;
| Eike Rathke &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel, ~150 Euro fuel&lt;br /&gt;
|-&lt;br /&gt;
| Thorsten Behrens &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 124 Euro hotel, 140 Euro airfare&lt;br /&gt;
|-&lt;br /&gt;
| Bjoern Michaelsen &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel&lt;br /&gt;
|-&lt;br /&gt;
| Stephan Bergmann &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel&lt;br /&gt;
|-&lt;br /&gt;
| Carsten Driesner &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel, ~150 Euro fuel&lt;br /&gt;
|-&lt;br /&gt;
| Leo Moons &lt;br /&gt;
| Saturday &lt;br /&gt;
| Stand &lt;br /&gt;
| no&lt;br /&gt;
|-&lt;br /&gt;
| Andreas Mantke &lt;br /&gt;
| Saturday &lt;br /&gt;
| Stand &lt;br /&gt;
| yes (approx. 60 EUR fuel)&lt;br /&gt;
|-&lt;br /&gt;
| Sophie Gautier &lt;br /&gt;
| both days&lt;br /&gt;
| Stand &lt;br /&gt;
| no&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Hotel Recommendation==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&amp;amp;Sleep 59 Euro &lt;br /&gt;
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
&lt;br /&gt;
Feel free to insert some more recommendations.&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=154623</id>
		<title>Conferences/FOSDEM/2010/CFP</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=154623"/>
		<updated>2010-01-11T08:49:06Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Call for Papers for the OpenOffice.org and ODF DevRoom@FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=&amp;quot;6&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;Deadline: Friday, December 18th&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Proposals==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Local community building - Open-Source-Treffen===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Local community building - Open-Source-Treffen&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| Local community building - Open-Source-Treffen&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Florian Effenberger, OpenOffice.org&amp;lt;br&amp;gt;Carsten&amp;amp;nbsp;Book, Mozilla&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Florian Effenberger has been an open source evangelist for many years. He is co-lead of the international OpenOffice.org marketing project as well as a member of the management board of the non-profit OpenOffice.org Deutschland e.V. He is also a frequent contributor to a variety of professional magazines worldwide.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Mozilla and OpenOffice.org jointly organize so called open source meetings (&amp;quot;Open-Source-Treffen&amp;quot;) in&amp;amp;nbsp;Germany to foster the idea of community building and to support exchange amongst projects and communities. This talk gives an overview of the idea, on what we achieved so far, what our plans for the future are - and how you can help!&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| Most people use open source software day by day. A fact that most of them do not know: Often, this free software is being developed, documented, marketed and improved by volunteers in their free time. Many open source projects work on fostering the idea of free software and open content, and a lot of users benefit from their efforts. Other than with proprietary software, users can get in direct touch with the communites via blogs, IRC channels, mailing lists or forums.&lt;br /&gt;
Despite the modern way of communicating, personal contact still is the best way to get to know each other. Meeting the people behind the names in reality is a great experience, and helps users of finding their way into open source communites to engage themselves. Therefore, Mozilla and OpenOffice.org jointly organize the so-called &amp;quot;Open-Source-Treffen&amp;quot; (&amp;quot;Open Source Meetings&amp;quot;) to help open source projects in meeting their end-users and vice versa. Members of the community can get in touch with their users to gather valueable feedback, and open source adopters meet other supporters from their area.&lt;br /&gt;
&lt;br /&gt;
In the German city of Munich, the &amp;quot;Open-Source-Treffen&amp;quot; have been taking place regularly, and the idea is to spread the word for other areas, engaging community members to set up more meetings. Carsten Book of Mozilla and Florian Effenberger of OpenOffice.org, founders of the &amp;quot;Open-Source-Treffen&amp;quot;, introduce their vision and tell about the previous experiences. Audience for this talk are open source communities wishing to set up their own meetings as well as interested users who love to learn more about the idea.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://www.opensourcetreffen.de http://www.opensourcetreffen.de]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:Floeff.jpg]] See [[User:Floeff]]&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== ODF Tools and Resources ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF Tools and Resources&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenDocument format (ODF)&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Talk / 30 mins&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bart Hanssens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bart Hanssens is chairing the OASIS ODF Interop and Conformance TC, co-organizer of the ODF plugfests and has been testing various ODF applications for the Belgian Federal government in his role as Interoperability Expert at Fedict &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session lists the various ODF tools and libraries that are &amp;quot;out there&amp;quot;, and where one can find additional info about ODF itself.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| ODF has become a popular document format, but for new developers it isn&amp;#039;t always clear what open source tools exist and where to find them. This presentations aims to list the most interesting tools, libraries, projects and other resources available. &lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://be.linkedin.com/in/barthanssens&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| (See LinkedIn profile)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===lpOD – languages &amp;amp; platforms OpenDocument=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;lpOD – languages &amp;amp; platforms OpenDocument&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenDocument format (ODF)&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| TALK / 30min&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Luis Belmar-Letelier and Jérôme Dumonteil&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Luis Belmar-Letelier PhD in Physics, CEO of Itaapy a Python agil shop since 2003, work with the ODF Toolkit Union, and is the coordinator of the lpOD project http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Presentation of the lpOD -- languages &amp;amp; platforms OpenDocument &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| lpOD, is a Free Software project that offers, for high level use cases, an application programming interface dedicated to document processing with the Python, Perl and Ruby languages. It’s complying with the Open Document Format (ODF).&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://fr.linkedin.com/in/luisbelmarletelier&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===ODF on the server - ODFDOM architecture === &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF on the server - ODFDOM architecture&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenDocument format (ODF)&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 30min&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Svante Schubert&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
|Svante	Schubert (Sun Microsystems Inc.) has been a full-time developer for OpenOffice.org since its foundation. On OpenOffice.org he is the co-lead of the &amp;#039;XML project&amp;#039;, with emphasis on XML based filters and the new RDF metadata model of the OpenDocument Format 1.2. On the &amp;#039;ODF Toolkit project&amp;#039; he is responsible for the new ODFDOM library. He works on the ODF standardization in the OASIS ODF TC, the German DIN and ISO SC34.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| ODFDOM is the name of the free OpenDocument framework, which was recently published in version 0.75 to support ODF 1.2. Its overall purpose is to provide the ODF developer community a lightweight programming API in order to easily access and manipulate ODF documents. With its version 0.75, ODFDOM supports all ODF 1.2 elements and attributes, generated from the OpenDocument RelaxNG schema directly into the Java source code. The upcoming presentation will give an overview over the architecture, design ideas and in addition deliver insights about the roadmap and upcoming features.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| See [http://odftoolkit.org/projects/odfdom/pages/Home http://odftoolkit.org/projects/odfdom/pages/Home] for details...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:SvanteSmiling.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Tips and Tricks for Extension Developer=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Tips and Tricks for Extension Developer&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Juergen Schmidt&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Juergen Schmidt is working for Sun Microsystems in the StarOffice group for more then 12 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API and the Extensions project and he is a member of the OpenOffice.org Community Council. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. He speaks frequently about the programmability features of OpenOffice.org on international conferences. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension. Extensions provide often the necessary connector from OpenOffice.org to other software systems and the better they are integrated the better is the overall user experience and the interoperability.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| OpenOffice.org Extensions provide a very good mechanism to extend OpenOffice.org with new and often specialized new functions. The extension infra structure gets better and better and an extension developer should make use of all the available feature to integrate best in the office. The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension.&amp;lt;br&amp;gt;&lt;br /&gt;
Often extensions are the beginning of more advanced development tasks that will go deeper in the core code of OpenOffice.org whereas extensions use API&amp;#039;s only. The advantage of extensions is that you can work on a standalone mini project that uses official API&amp;#039;s only and that you can learn the basics and secrets of OpenOffice.org step by step. But extensions can not solve all problems and often additional changes in the core or even new API&amp;#039;s are necessary to solve a specific task. But as mentioned before extensions provide a smooth way to get started and to dive deeper and deeper into the large project code base over time. OpenOffice.org is a very huge project and the start to develop with and for OpenOffice.org is not easy and the hype factor is also not the highest one. But it must be something behind this project that big companies hire special people to work on campaigns against OpenOffice.org and open source in general. Is it still David versus Goliath or has the situation changed a little bit? Who knows but you can be part of the huge and worldwide community and can start to develop with and for OpenOffice.org.&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:jsc.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== New docking windows for a better UI &amp;amp; extension integration ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;New docking windows for a better UI &amp;amp; extension integration&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Carsten Driesner&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Carsten Driesner works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2000. He is the project lead of the framework project since 2006. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The main goal of the framework project is to provide low-level functions (like loading/storing documents, generic UI, OLE, filter management) to the application modules. As the generic OpenOffice.org UI is mainly based on framework code many aspects of the Project Renaissance must be implement there. This presentation wants to provide an overview about our latest plans to provide new and powerful docking window functions.&lt;br /&gt;
The presentation is split up into four different parts:&lt;br /&gt;
1. The current state of docking window design&lt;br /&gt;
2. The new docking window design&lt;br /&gt;
3. How can extensions profit from the new design&lt;br /&gt;
4. Future outlook&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/Framework&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Improving the OpenOffice.org Build System ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Improving the OpenOffice.org Build System&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk, 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bjoern Michaelsen works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2008. He is the a member of the ongoing [[Build Environment Effort]] and a member of the Writer/Framework team at Sun.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The [[Build Environment Effort]] is an ongoing effort to update various aspects of the OpenOffice.org build environment. Some of the aims of this effort require to rethink the basic architecture of how OpenOffice.org is build.&lt;br /&gt;
This talk with present the results so far and how we are planning to go on.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| see http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu for details&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| &lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/build_scalability1&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/a_split_build_for_openoffice (by Mathias Bauer)&lt;br /&gt;
* http://wiki.services.openoffice.org/wiki/Build_Environment_Effort&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:bmichaelsen.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Show me YOUR code ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Show me YOUR code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Workshop, 90-120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Eike Rathke&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Eike Rathke is a core developer and co-lead of the OpenOffice.org Calc spreadsheet application. &amp;lt;br&amp;gt; Working on the spreadsheet core engine, formula compiler and interpreter since 1994. Also working on the number parser/formatter and doing related i18n work. He works for Sun Microsystems.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Show me the code YOU have written and want to be integrated. Talk about, identify and hopefully clear obstacles. Let&amp;#039;s solve remaining problems together.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| The last two FOSDEMs I gave an overview of the Calc spreadsheet interpreter core, and showed how to debug and profile the beast. This year it is time YOU show me YOUR code. Go into details. Discuss your solution. Ask questions. &amp;lt;br&amp;gt; If you would like to dive into your code at the workshop I&amp;#039;d appreciate if you made it available in advance so I can take a look. Send a mail to mailto:erack@sun.com?subject=FOSDEM%20code&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/User:ErAck&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo&lt;br /&gt;
| [[Image:ErAck_128x128.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Just Testing ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Just Testing&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration&lt;br /&gt;
| talk/45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker&lt;br /&gt;
| Stephan Bergmann&lt;br /&gt;
|-&lt;br /&gt;
| Biography&lt;br /&gt;
| Stephan has been working on all kinds of aspects of OpenOffice.org for well over a decade now, as a member of the StarOffice/OpenOffice.org development team at Sun Hamburg.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| OpenOffice.org is too fat and too weird to let you simply apply your standard unit-testing-approach to writing correct code.  Over the years, this has lead to the creation of a number of mechanisms within the OOo code base with which OOo developers can test the code they write and compile.  Some of the mechanisms are, erm, creative, some are trivial.  But what all the mechanisms have in common is that they all are brittle and all start to fail, in one way or another, sooner or later.  Time to clean up. &amp;lt;br/&amp;gt; This talk will discuss where we intend to go, and probably tell a couple of anecdotes about where we came from.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Hidden Pearls&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Thorsten has been hacking on OpenOffice.org for many years.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session presents a few examples of uniquely useful code inside OOo, plus a way for other projects to mine those pearls.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| This [http://blog.thebehrens.net/2008/09/29/ooo-non-vision/ rant] (except for the ranting) pretty much conveys the ideas I want to present here&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blog.thebehrens.net]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-271-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-271-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=154417</id>
		<title>Conferences/FOSDEM/2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=154417"/>
		<updated>2010-01-05T22:34:34Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Team */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium&lt;br /&gt;
 &lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
==Communication Channel==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==DevRoom==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Call for Papers===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Some things that should be taken into account &lt;br /&gt;
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),&lt;br /&gt;
* a short abstract (1-2 paragraphs),&lt;br /&gt;
* a longer description if appropriate,&lt;br /&gt;
* optionally a list of links to the project website or similar&lt;br /&gt;
* for each speaker:&lt;br /&gt;
** the speaker&amp;#039;s real name,&lt;br /&gt;
** a short overview of her bio in a couple of lines,&lt;br /&gt;
** optionally also a longer bio,&lt;br /&gt;
** optionally a picture (please send it to Juergen as 128x128 PNG),&lt;br /&gt;
** optionally links to her website, blog, ... &lt;br /&gt;
&lt;br /&gt;
We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.&lt;br /&gt;
&lt;br /&gt;
====Proposals====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Schedule===&lt;br /&gt;
&lt;br /&gt;
Changes are still possible&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ DevRoom Overview&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Time !! Title !! Session type !! Slides !!Speaker&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;OpenOffice.org&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 13:00 - 13:45 || Welcome + Tips and Tricks for Extension Developer || talk || ? || [[User:Jsc|Juergen Schmidt]]&lt;br /&gt;
|-&lt;br /&gt;
| 13:45 - 14:30 || New docking windows for a better UI &amp;amp; extension integration || talk || ? || Carsten Driesner&lt;br /&gt;
|- &lt;br /&gt;
| 14:30 - 15:15 || Improving the OpenOffice.org Build System || talk || ? || Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| 15:15 - 16:00 || Just Testing || talk || ? || Stephan Bergmann &lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 16:45 || Show me YOUR code || workshop || ? || [[User:ErAck|Eike Rathke]]&lt;br /&gt;
|-&lt;br /&gt;
| 16:45 - 17:30 || Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  || talk || ? || Thorsten Behrens&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 17:30 - 18:00 || ODF Tools and Resources || talk || ? || [http://be.linkedin.com/in/barthanssens Bart Hanssens]&lt;br /&gt;
|-&lt;br /&gt;
| 18:00 - 18:30 || ODF on the server - ODFDOM architecture || talk || ? || Svante Schubert&lt;br /&gt;
|-&lt;br /&gt;
| 18:30 - 19:00 || lpOD – languages &amp;amp; platforms OpenDocument || talk || ? || ?&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Stand/Booth ==&lt;br /&gt;
&lt;br /&gt;
Our stand will be most probably in building AW &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Stand Overview &lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Time &lt;br /&gt;
! Stand staff&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Saturday 6th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 &lt;br /&gt;
| floeff, jsc&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 &lt;br /&gt;
| floeff&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 &lt;br /&gt;
| floeff&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 18:00 &lt;br /&gt;
| floeff, jsc&amp;lt;br&amp;gt;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;4&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sunday 7th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 &lt;br /&gt;
| probably floeff, jsc&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 &lt;br /&gt;
| jsc&lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 17:00 &lt;br /&gt;
| &amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
More info ...&lt;br /&gt;
&lt;br /&gt;
==Saturday Evening OOo Community Event==&lt;br /&gt;
...details will coming soon&lt;br /&gt;
&lt;br /&gt;
== Team  ==&lt;br /&gt;
&lt;br /&gt;
...details will coming soon &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Name &lt;br /&gt;
! Stay &lt;br /&gt;
! Function &lt;br /&gt;
! Funding request&lt;br /&gt;
|-&lt;br /&gt;
| Juergen Schmidt &lt;br /&gt;
| Friday - Sunday &lt;br /&gt;
| Stand/DevRoom &lt;br /&gt;
| 140 Euro hotel, 120 Euro fuel&lt;br /&gt;
|-&lt;br /&gt;
| Florian Effenberger&amp;lt;br&amp;gt; &lt;br /&gt;
| Friday-Sunday &lt;br /&gt;
| Stand/Marketing &lt;br /&gt;
| yes (approx. 250-300 EUR)&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Cor Nouws&amp;lt;br&amp;gt; &lt;br /&gt;
| probably both days &lt;br /&gt;
| - &lt;br /&gt;
| partly&lt;br /&gt;
|-&lt;br /&gt;
| Andrea Pescetti &lt;br /&gt;
| one day only (unsure) &lt;br /&gt;
| &amp;amp;nbsp;? &lt;br /&gt;
| no&lt;br /&gt;
|-&lt;br /&gt;
| Jacqueline Rahemipour &lt;br /&gt;
| both days &lt;br /&gt;
| &lt;br /&gt;
| partly&lt;br /&gt;
|-&lt;br /&gt;
| Eike Rathke &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel, 120 Euro fuel&lt;br /&gt;
|-&lt;br /&gt;
| Thorsten Behrens &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 124 Euro hotel, 140 Euro airfare&lt;br /&gt;
|-&lt;br /&gt;
| Bjoern Michaelsen &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel&lt;br /&gt;
|-&lt;br /&gt;
| Stephan Bergmann &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel&lt;br /&gt;
|-&lt;br /&gt;
| Carsten Driesner &lt;br /&gt;
| both days &lt;br /&gt;
| Stand / DevRoom &lt;br /&gt;
| 140 Euro hotel, 120 Euro fuel&lt;br /&gt;
|-&lt;br /&gt;
| Leo Moons &lt;br /&gt;
| probably both days &lt;br /&gt;
| Stand &lt;br /&gt;
| no&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Hotel Recommendation==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&amp;amp;Sleep 59 Euro &lt;br /&gt;
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
&lt;br /&gt;
Feel free to insert some more recommendations.&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153438</id>
		<title>Conferences/FOSDEM/2010/CFP</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153438"/>
		<updated>2009-12-18T19:33:50Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Call for Papers for the OpenOffice.org and ODF DevRoom@FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=&amp;quot;6&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;Deadline: Friday, December 18th&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Proposals==&lt;br /&gt;
&lt;br /&gt;
=== Sample  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sample&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org or ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk or workshop / 45, 90 or 120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Max Mustermann&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Max Mustermann is working on the OpenOffice.org project since ...&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session gives an overview of ...&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| longer description of the session content if appropriate&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| links to projects, web pages etc.&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Local community building - Open-Source-Treffen===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Local community building - Open-Source-Treffen&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| Local community building - Open-Source-Treffen&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Florian Effenberger, OpenOffice.org&amp;lt;br&amp;gt;Carsten&amp;amp;nbsp;Book, Mozilla&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Florian Effenberger has been an open source evangelist for many years. He is co-lead of the international OpenOffice.org marketing project as well as a member of the management board of the non-profit OpenOffice.org Deutschland e.V. He is also a frequent contributor to a variety of professional magazines worldwide.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Mozilla and OpenOffice.org jointly organize so called open source meetings (&amp;quot;Open-Source-Treffen&amp;quot;) in&amp;amp;nbsp;Germany to foster the idea of community building and to support exchange amongst projects and communities. This talk gives an overview of the idea, on what we achieved so far, what our plans for the future are - and how you can help!&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| Most people use open source software day by day. A fact that most of them do not know: Often, this free software is being developed, documented, marketed and improved by volunteers in their free time. Many open source projects work on fostering the idea of free software and open content, and a lot of users benefit from their efforts. Other than with proprietary software, users can get in direct touch with the communites via blogs, IRC channels, mailing lists or forums.&lt;br /&gt;
Despite the modern way of communicating, personal contact still is the best way to get to know each other. Meeting the people behind the names in reality is a great experience, and helps users of finding their way into open source communites to engage themselves. Therefore, Mozilla and OpenOffice.org jointly organize the so-called &amp;quot;Open-Source-Treffen&amp;quot; (&amp;quot;Open Source Meetings&amp;quot;) to help open source projects in meeting their end-users and vice versa. Members of the community can get in touch with their users to gather valueable feedback, and open source adopters meet other supporters from their area.&lt;br /&gt;
&lt;br /&gt;
In the German city of Munich, the &amp;quot;Open-Source-Treffen&amp;quot; have been taking place regularly, and the idea is to spread the word for other areas, engaging community members to set up more meetings. Carsten Book of Mozilla and Florian Effenberger of OpenOffice.org, founders of the &amp;quot;Open-Source-Treffen&amp;quot;, introduce their vision and tell about the previous experiences. Audience for this talk are open source communities wishing to set up their own meetings as well as interested users who love to learn more about the idea.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://www.opensourcetreffen.de http://www.opensourcetreffen.de]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:Floeff.jpg]] See [[User:Floeff]]&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== ODF Tools and Resources ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF Tools and Resources&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Talk / 45 mins&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bart Hanssens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bart Hanssens is chairing the OASIS ODF Interop and Conformance TC, co-organizer of the ODF plugfests and has been testing various ODF applications for the Belgian Federal government in his role as Interoperability Expert at Fedict &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session lists the various ODF tools and libraries that are &amp;quot;out there&amp;quot;, and where one can find additional info about ODF itself.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| ODF has become a popular document format, but for new developers it isn&amp;#039;t always clear what open source tools exist and where to find them. This presentations aims to list the most interesting tools, libraries, projects and other resources available. &lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://be.linkedin.com/in/barthanssens&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| (See LinkedIn profile)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===lpOD – languages &amp;amp; platforms OpenDocument=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;lpOD – languages &amp;amp; platforms OpenDocument&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Luis Belmar-Letelier, Charles, JMG and/or Jérôme ? &lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Luis Belmar-Letelier PhD in Physics, CEO of Itaapy a Python agil shop since 2003, work with the ODF Toolkit Union, and is the coordinator of the lpOD project http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Presentation of the lpOD -- languages &amp;amp; platforms OpenDocument &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| lpOD, is a Free Software project that offers, for high level use cases, an application programming interface dedicated to document processing with the Python, Perl and Ruby languages. It’s complying with the Open Document Format (ODF).&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tips and Tricks for Extension Developer=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Tips and Tricks for Extension Developer&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Juergen Schmidt&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Juergen Schmidt is working for Sun Microsystems in the StarOffice group for more then 12 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API and the Extensions project and he is a member of the OpenOffice.org Community Council. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. He speaks frequently about the programmability features of OpenOffice.org on international conferences. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension. Extensions provide often the necessary connector from OpenOffice.org to other software systems and the better they are integrated the better is the overall user experience and the interoperability.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| is coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:jsc.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== New docking windows for a better UI &amp;amp; extension integration ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;New docking windows for a better UI &amp;amp; extension integration&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Carsten Driesner&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Carsten Driesner works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2000. He is the project lead of the framework project since 2006. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The main goal of the framework project is to provide low-level functions (like loading/storing documents, generic UI, OLE, filter management) to the application modules. As the generic OpenOffice.org UI is mainly based on framework code many aspects of the Project Renaissance must be implement there. This presentation wants to provide an overview about our latest plans to provide new and powerful docking window functions.&lt;br /&gt;
The presentation is split up into four different parts:&lt;br /&gt;
1. The current state of docking window design&lt;br /&gt;
2. The new docking window design&lt;br /&gt;
3. How can extensions profit from the new design&lt;br /&gt;
4. Future outlook&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/Framework&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Improving the OpenOffice.org Build System ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Improving the OpenOffice.org Build System&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk, 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bjoern Michaelsen works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2008. He is the a member of the ongoing [[Build Environment Effort]] and a member of the Writer/Framework team at Sun.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The [[Build Environment Effort]] is an ongoing effort to update various aspects of the OpenOffice.org build environment. Some of the aims of this effort require to rethink the basic architecture of how OpenOffice.org is build.&lt;br /&gt;
This talk with present the results so far and how we are planning to go on.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| see http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu for details&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| &lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/build_scalability1&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/a_split_build_for_openoffice (by Mathias Bauer)&lt;br /&gt;
* http://wiki.services.openoffice.org/wiki/Build_Environment_Effort&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:bmichaelsen.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Show me YOUR code ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Show me YOUR code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Workshop, 90-120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Eike Rathke&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Eike Rathke is a core developer and co-lead of the OpenOffice.org Calc spreadsheet application. &amp;lt;br&amp;gt; Working on the spreadsheet core engine, formula compiler and interpreter since 1994. Also working on the number parser/formatter and doing related i18n work. He works for Sun Microsystems.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Show me the code YOU have written and want to be integrated. Talk about, identify and hopefully clear obstacles. Let&amp;#039;s solve remaining problems together.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| The last two FOSDEMs I gave an overview of the Calc spreadsheet interpreter core, and showed how to debug and profile the beast. This year it is time YOU show me YOUR code. Go into details. Discuss your solution. Ask questions. &amp;lt;br&amp;gt; If you would like to dive into your code at the workshop I&amp;#039;d appreciate if you made it available in advance so I can take a look. Send a mail to mailto:erack@sun.com?subject=FOSDEM%20code&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/User:ErAck&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo&lt;br /&gt;
| [[Image:ErAck_128x128.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Just Testing ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Just Testing&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration&lt;br /&gt;
| talk/45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker&lt;br /&gt;
| Stephan Bergmann&lt;br /&gt;
|-&lt;br /&gt;
| Biography&lt;br /&gt;
| Stephan has been working on all kinds of aspects of OpenOffice.org for well over a decade now, as a member of the StarOffice/OpenOffice.org development team at Sun Hamburg.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| OpenOffice.org is too fat and too weird to let you simply apply your standard unit-testing-approach to writing correct code.  Over the years, this has lead to the creation of a number of mechanisms within the OOo code base with which OOo developers can test the code they write and compile.  Some of the mechanisms are, erm, creative, some are trivial.  But what all the mechanisms have in common is that they all are brittle and all start to fail, in one way or another, sooner or later.  Time to clean up. &amp;lt;br/&amp;gt; This talk will discuss where we intend to go, and probably tell a couple of anecdotes about where we came from.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Hidden Pearls&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Thorsten has been hacking on OpenOffice.org for many years.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session presents a few examples of uniquely useful code inside OOo, plus a way for other projects to mine those pearls.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| This [http://blog.thebehrens.net/2008/09/29/ooo-non-vision/ rant] (except for the ranting) pretty much conveys the ideas I want to present here&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blog.thebehrens.net]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://blog.thebehrens.net http://netsroth.110mb.com/wtf2.png]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153437</id>
		<title>Conferences/FOSDEM/2010/CFP</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153437"/>
		<updated>2009-12-18T19:32:21Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Proposals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Call for Papers for the OpenOffice.org and ODF DevRoom@FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=&amp;quot;6&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;Deadline: Friday, December 18th&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Proposals==&lt;br /&gt;
&lt;br /&gt;
=== Sample  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sample&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org or ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk or workshop / 45, 90 or 120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Max Mustermann&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Max Mustermann is working on the OpenOffice.org project since ...&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session gives an overview of ...&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| longer description of the session content if appropriate&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| links to projects, web pages etc.&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Local community building - Open-Source-Treffen===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Local community building - Open-Source-Treffen&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| Local community building - Open-Source-Treffen&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Florian Effenberger, OpenOffice.org&amp;lt;br&amp;gt;Carsten&amp;amp;nbsp;Book, Mozilla&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Florian Effenberger has been an open source evangelist for many years. He is co-lead of the international OpenOffice.org marketing project as well as a member of the management board of the non-profit OpenOffice.org Deutschland e.V. He is also a frequent contributor to a variety of professional magazines worldwide.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Mozilla and OpenOffice.org jointly organize so called open source meetings (&amp;quot;Open-Source-Treffen&amp;quot;) in&amp;amp;nbsp;Germany to foster the idea of community building and to support exchange amongst projects and communities. This talk gives an overview of the idea, on what we achieved so far, what our plans for the future are - and how you can help!&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| Most people use open source software day by day. A fact that most of them do not know: Often, this free software is being developed, documented, marketed and improved by volunteers in their free time. Many open source projects work on fostering the idea of free software and open content, and a lot of users benefit from their efforts. Other than with proprietary software, users can get in direct touch with the communites via blogs, IRC channels, mailing lists or forums.&lt;br /&gt;
Despite the modern way of communicating, personal contact still is the best way to get to know each other. Meeting the people behind the names in reality is a great experience, and helps users of finding their way into open source communites to engage themselves. Therefore, Mozilla and OpenOffice.org jointly organize the so-called &amp;quot;Open-Source-Treffen&amp;quot; (&amp;quot;Open Source Meetings&amp;quot;) to help open source projects in meeting their end-users and vice versa. Members of the community can get in touch with their users to gather valueable feedback, and open source adopters meet other supporters from their area.&lt;br /&gt;
&lt;br /&gt;
In the German city of Munich, the &amp;quot;Open-Source-Treffen&amp;quot; have been taking place regularly, and the idea is to spread the word for other areas, engaging community members to set up more meetings. Carsten Book of Mozilla and Florian Effenberger of OpenOffice.org, founders of the &amp;quot;Open-Source-Treffen&amp;quot;, introduce their vision and tell about the previous experiences. Audience for this talk are open source communities wishing to set up their own meetings as well as interested users who love to learn more about the idea.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://www.opensourcetreffen.de http://www.opensourcetreffen.de]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:Floeff.jpg]] See [[User:Floeff]]&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== ODF Tools and Resources ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF Tools and Resources&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Talk / 45 mins&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bart Hanssens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bart Hanssens is chairing the OASIS ODF Interop and Conformance TC, co-organizer of the ODF plugfests and has been testing various ODF applications for the Belgian Federal government in his role as Interoperability Expert at Fedict &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session lists the various ODF tools and libraries that are &amp;quot;out there&amp;quot;, and where one can find additional info about ODF itself.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| ODF has become a popular document format, but for new developers it isn&amp;#039;t always clear what open source tools exist and where to find them. This presentations aims to list the most interesting tools, libraries, projects and other resources available. &lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://be.linkedin.com/in/barthanssens&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| (See LinkedIn profile)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===lpOD – languages &amp;amp; platforms OpenDocument=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;lpOD – languages &amp;amp; platforms OpenDocument&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Luis Belmar-Letelier, Charles, JMG and/or Jérôme ? &lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Luis Belmar-Letelier PhD in Physics, CEO of Itaapy a Python agil shop since 2003, work with the ODF Toolkit Union, and is the coordinator of the lpOD project http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Presentation of the lpOD -- languages &amp;amp; platforms OpenDocument &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| lpOD, is a Free Software project that offers, for high level use cases, an application programming interface dedicated to document processing with the Python, Perl and Ruby languages. It’s complying with the Open Document Format (ODF).&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tips and Tricks for Extension Developer=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Tips and Tricks for Extension Developer&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Juergen Schmidt&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Juergen Schmidt is working for Sun Microsystems in the StarOffice group for more then 12 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API and the Extensions project and he is a member of the OpenOffice.org Community Council. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. He speaks frequently about the programmability features of OpenOffice.org on international conferences. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension. Extensions provide often the necessary connector from OpenOffice.org to other software systems and the better they are integrated the better is the overall user experience and the interoperability.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| is coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:jsc.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== New docking windows for a better UI &amp;amp; extension integration ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;New docking windows for a better UI &amp;amp; extension integration&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Carsten Driesner&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Carsten Driesner works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2000. He is the project lead of the framework project since 2006. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The main goal of the framework project is to provide low-level functions (like loading/storing documents, generic UI, OLE, filter management) to the application modules. As the generic OpenOffice.org UI is mainly based on framework code many aspects of the Project Renaissance must be implement there. This presentation wants to provide an overview about our latest plans to provide new and powerful docking window functions.&lt;br /&gt;
The presentation is split up into four different parts:&lt;br /&gt;
1. The current state of docking window design&lt;br /&gt;
2. The new docking window design&lt;br /&gt;
3. How can extensions profit from the new design&lt;br /&gt;
4. Future outlook&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/Framework&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Improving the OpenOffice.org Build System ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Improving the OpenOffice.org Build System&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk, 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bjoern Michaelsen works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2008. He is the a member of the ongoing [[Build Environment Effort]] and a member of the Writer/Framework team at Sun.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The [[Build Environment Effort]] is an ongoing effort to update various aspects of the OpenOffice.org build environment. Some of the aims of this effort require to rethink the basic architecture of how OpenOffice.org is build.&lt;br /&gt;
This talk with present the results so far and how we are planning to go on.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| see http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu for details&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| &lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/build_scalability1&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/a_split_build_for_openoffice (by Mathias Bauer)&lt;br /&gt;
* http://wiki.services.openoffice.org/wiki/Build_Environment_Effort&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:bmichaelsen.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Show me YOUR code ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Show me YOUR code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Workshop, 90-120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Eike Rathke&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Eike Rathke is a core developer and co-lead of the OpenOffice.org Calc spreadsheet application. &amp;lt;br&amp;gt; Working on the spreadsheet core engine, formula compiler and interpreter since 1994. Also working on the number parser/formatter and doing related i18n work. He works for Sun Microsystems.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Show me the code YOU have written and want to be integrated. Talk about, identify and hopefully clear obstacles. Let&amp;#039;s solve remaining problems together.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| The last two FOSDEMs I gave an overview of the Calc spreadsheet interpreter core, and showed how to debug and profile the beast. This year it is time YOU show me YOUR code. Go into details. Discuss your solution. Ask questions. &amp;lt;br&amp;gt; If you would like to dive into your code at the workshop I&amp;#039;d appreciate if you made it available in advance so I can take a look. Send a mail to mailto:erack@sun.com?subject=FOSDEM%20code&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/User:ErAck&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo&lt;br /&gt;
| [[Image:ErAck_128x128.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Just Testing ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Just Testing&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration&lt;br /&gt;
| talk/45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker&lt;br /&gt;
| Stephan Bergmann&lt;br /&gt;
|-&lt;br /&gt;
| Biography&lt;br /&gt;
| Stephan has been working on all kinds of aspects of OpenOffice.org for well over a decade now, as a member of the StarOffice/OpenOffice.org development team at Sun Hamburg.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| OpenOffice.org is too fat and too weird to let you simply apply your standard unit-testing-approach to writing correct code.  Over the years, this has lead to the creation of a number of mechanisms within the OOo code base with which OOo developers can test the code they write and compile.  Some of the mechanisms are, erm, creative, some are trivial.  But what all the mechanisms have in common is that they all are brittle and all start to fail, in one way or another, sooner or later.  Time to clean up. &amp;lt;br/&amp;gt; This talk will discuss where we intend to go, and probably tell a couple of anecdotes about where we came from.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Hidden Pearls&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Thorsten has been hacking on OpenOffice.org for many years.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session presents a few examples of uniquely useful code inside OOo, plus a way for other projects to mine those pearls.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -todo-&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blog.thebehrens.net]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://blog.thebehrens.net http://netsroth.110mb.com/wtf2.png]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153436</id>
		<title>Conferences/FOSDEM/2010/CFP</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153436"/>
		<updated>2009-12-18T19:31:17Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Proposals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Call for Papers for the OpenOffice.org and ODF DevRoom@FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=&amp;quot;6&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;Deadline: Friday, December 18th&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Proposals==&lt;br /&gt;
&lt;br /&gt;
=== Sample  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sample&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org or ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk or workshop / 45, 90 or 120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Max Mustermann&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Max Mustermann is working on the OpenOffice.org project since ...&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session gives an overview of ...&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| longer description of the session content if appropriate&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| links to projects, web pages etc.&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Local community building - Open-Source-Treffen===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Local community building - Open-Source-Treffen&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| Local community building - Open-Source-Treffen&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Florian Effenberger, OpenOffice.org&amp;lt;br&amp;gt;Carsten&amp;amp;nbsp;Book, Mozilla&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Florian Effenberger has been an open source evangelist for many years. He is co-lead of the international OpenOffice.org marketing project as well as a member of the management board of the non-profit OpenOffice.org Deutschland e.V. He is also a frequent contributor to a variety of professional magazines worldwide.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Mozilla and OpenOffice.org jointly organize so called open source meetings (&amp;quot;Open-Source-Treffen&amp;quot;) in&amp;amp;nbsp;Germany to foster the idea of community building and to support exchange amongst projects and communities. This talk gives an overview of the idea, on what we achieved so far, what our plans for the future are - and how you can help!&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| Most people use open source software day by day. A fact that most of them do not know: Often, this free software is being developed, documented, marketed and improved by volunteers in their free time. Many open source projects work on fostering the idea of free software and open content, and a lot of users benefit from their efforts. Other than with proprietary software, users can get in direct touch with the communites via blogs, IRC channels, mailing lists or forums.&lt;br /&gt;
Despite the modern way of communicating, personal contact still is the best way to get to know each other. Meeting the people behind the names in reality is a great experience, and helps users of finding their way into open source communites to engage themselves. Therefore, Mozilla and OpenOffice.org jointly organize the so-called &amp;quot;Open-Source-Treffen&amp;quot; (&amp;quot;Open Source Meetings&amp;quot;) to help open source projects in meeting their end-users and vice versa. Members of the community can get in touch with their users to gather valueable feedback, and open source adopters meet other supporters from their area.&lt;br /&gt;
&lt;br /&gt;
In the German city of Munich, the &amp;quot;Open-Source-Treffen&amp;quot; have been taking place regularly, and the idea is to spread the word for other areas, engaging community members to set up more meetings. Carsten Book of Mozilla and Florian Effenberger of OpenOffice.org, founders of the &amp;quot;Open-Source-Treffen&amp;quot;, introduce their vision and tell about the previous experiences. Audience for this talk are open source communities wishing to set up their own meetings as well as interested users who love to learn more about the idea.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://www.opensourcetreffen.de http://www.opensourcetreffen.de]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:Floeff.jpg]] See [[User:Floeff]]&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== ODF Tools and Resources ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF Tools and Resources&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Talk / 45 mins&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bart Hanssens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bart Hanssens is chairing the OASIS ODF Interop and Conformance TC, co-organizer of the ODF plugfests and has been testing various ODF applications for the Belgian Federal government in his role as Interoperability Expert at Fedict &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session lists the various ODF tools and libraries that are &amp;quot;out there&amp;quot;, and where one can find additional info about ODF itself.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| ODF has become a popular document format, but for new developers it isn&amp;#039;t always clear what open source tools exist and where to find them. This presentations aims to list the most interesting tools, libraries, projects and other resources available. &lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://be.linkedin.com/in/barthanssens&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| (See LinkedIn profile)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===lpOD – languages &amp;amp; platforms OpenDocument=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;lpOD – languages &amp;amp; platforms OpenDocument&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Luis Belmar-Letelier, Charles, JMG and/or Jérôme ? &lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Luis Belmar-Letelier PhD in Physics, CEO of Itaapy a Python agil shop since 2003, work with the ODF Toolkit Union, and is the coordinator of the lpOD project http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Presentation of the lpOD -- languages &amp;amp; platforms OpenDocument &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| lpOD, is a Free Software project that offers, for high level use cases, an application programming interface dedicated to document processing with the Python, Perl and Ruby languages. It’s complying with the Open Document Format (ODF).&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tips and Tricks for Extension Developer=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Tips and Tricks for Extension Developer&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Juergen Schmidt&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Juergen Schmidt is working for Sun Microsystems in the StarOffice group for more then 12 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API and the Extensions project and he is a member of the OpenOffice.org Community Council. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. He speaks frequently about the programmability features of OpenOffice.org on international conferences. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension. Extensions provide often the necessary connector from OpenOffice.org to other software systems and the better they are integrated the better is the overall user experience and the interoperability.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| is coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:jsc.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== New docking windows for a better UI &amp;amp; extension integration ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;New docking windows for a better UI &amp;amp; extension integration&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Carsten Driesner&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Carsten Driesner works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2000. He is the project lead of the framework project since 2006. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The main goal of the framework project is to provide low-level functions (like loading/storing documents, generic UI, OLE, filter management) to the application modules. As the generic OpenOffice.org UI is mainly based on framework code many aspects of the Project Renaissance must be implement there. This presentation wants to provide an overview about our latest plans to provide new and powerful docking window functions.&lt;br /&gt;
The presentation is split up into four different parts:&lt;br /&gt;
1. The current state of docking window design&lt;br /&gt;
2. The new docking window design&lt;br /&gt;
3. How can extensions profit from the new design&lt;br /&gt;
4. Future outlook&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/Framework&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Improving the OpenOffice.org Build System ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Improving the OpenOffice.org Build System&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk, 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bjoern Michaelsen works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2008. He is the a member of the ongoing [[Build Environment Effort]] and a member of the Writer/Framework team at Sun.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The [[Build Environment Effort]] is an ongoing effort to update various aspects of the OpenOffice.org build environment. Some of the aims of this effort require to rethink the basic architecture of how OpenOffice.org is build.&lt;br /&gt;
This talk with present the results so far and how we are planning to go on.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| see http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu for details&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| &lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/build_scalability1&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/a_split_build_for_openoffice (by Mathias Bauer)&lt;br /&gt;
* http://wiki.services.openoffice.org/wiki/Build_Environment_Effort&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:bmichaelsen.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Show me YOUR code ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Show me YOUR code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Workshop, 90-120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Eike Rathke&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Eike Rathke is a core developer and co-lead of the OpenOffice.org Calc spreadsheet application. &amp;lt;br&amp;gt; Working on the spreadsheet core engine, formula compiler and interpreter since 1994. Also working on the number parser/formatter and doing related i18n work. He works for Sun Microsystems.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Show me the code YOU have written and want to be integrated. Talk about, identify and hopefully clear obstacles. Let&amp;#039;s solve remaining problems together.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| The last two FOSDEMs I gave an overview of the Calc spreadsheet interpreter core, and showed how to debug and profile the beast. This year it is time YOU show me YOUR code. Go into details. Discuss your solution. Ask questions. &amp;lt;br&amp;gt; If you would like to dive into your code at the workshop I&amp;#039;d appreciate if you made it available in advance so I can take a look. Send a mail to mailto:erack@sun.com?subject=FOSDEM%20code&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/User:ErAck&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo&lt;br /&gt;
| [[Image:ErAck_128x128.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Just Testing ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Just Testing&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration&lt;br /&gt;
| talk/45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker&lt;br /&gt;
| Stephan Bergmann&lt;br /&gt;
|-&lt;br /&gt;
| Biography&lt;br /&gt;
| Stephan has been working on all kinds of aspects of OpenOffice.org for well over a decade now, as a member of the StarOffice/OpenOffice.org development team at Sun Hamburg.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| OpenOffice.org is too fat and too weird to let you simply apply your standard unit-testing-approach to writing correct code.  Over the years, this has lead to the creation of a number of mechanisms within the OOo code base with which OOo developers can test the code they write and compile.  Some of the mechanisms are, erm, creative, some are trivial.  But what all the mechanisms have in common is that they all are brittle and all start to fail, in one way or another, sooner or later.  Time to clean up. &amp;lt;br/&amp;gt; This talk will discuss where we intend to go, and probably tell a couple of anecdotes about where we came from.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Hidden Pearls&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Thorsten has been hacking on OpenOffice.org for many years.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session presents a few examples of uniquely useful code inside OOo, plus a way for other projects to mine those pearls.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -todo-&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blog.thebehrens.net]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://netsroth.110mb.com/wtf2.png]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153435</id>
		<title>Conferences/FOSDEM/2010/CFP</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153435"/>
		<updated>2009-12-18T19:29:48Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Proposals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Call for Papers for the OpenOffice.org and ODF DevRoom@FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=&amp;quot;6&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;Deadline: Friday, December 18th&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Proposals==&lt;br /&gt;
&lt;br /&gt;
=== Sample  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sample&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org or ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk or workshop / 45, 90 or 120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Max Mustermann&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Max Mustermann is working on the OpenOffice.org project since ...&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session gives an overview of ...&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| longer description of the session content if appropriate&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| links to projects, web pages etc.&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Local community building - Open-Source-Treffen===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Local community building - Open-Source-Treffen&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| Local community building - Open-Source-Treffen&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Florian Effenberger, OpenOffice.org&amp;lt;br&amp;gt;Carsten&amp;amp;nbsp;Book, Mozilla&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Florian Effenberger has been an open source evangelist for many years. He is co-lead of the international OpenOffice.org marketing project as well as a member of the management board of the non-profit OpenOffice.org Deutschland e.V. He is also a frequent contributor to a variety of professional magazines worldwide.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Mozilla and OpenOffice.org jointly organize so called open source meetings (&amp;quot;Open-Source-Treffen&amp;quot;) in&amp;amp;nbsp;Germany to foster the idea of community building and to support exchange amongst projects and communities. This talk gives an overview of the idea, on what we achieved so far, what our plans for the future are - and how you can help!&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| Most people use open source software day by day. A fact that most of them do not know: Often, this free software is being developed, documented, marketed and improved by volunteers in their free time. Many open source projects work on fostering the idea of free software and open content, and a lot of users benefit from their efforts. Other than with proprietary software, users can get in direct touch with the communites via blogs, IRC channels, mailing lists or forums.&lt;br /&gt;
Despite the modern way of communicating, personal contact still is the best way to get to know each other. Meeting the people behind the names in reality is a great experience, and helps users of finding their way into open source communites to engage themselves. Therefore, Mozilla and OpenOffice.org jointly organize the so-called &amp;quot;Open-Source-Treffen&amp;quot; (&amp;quot;Open Source Meetings&amp;quot;) to help open source projects in meeting their end-users and vice versa. Members of the community can get in touch with their users to gather valueable feedback, and open source adopters meet other supporters from their area.&lt;br /&gt;
&lt;br /&gt;
In the German city of Munich, the &amp;quot;Open-Source-Treffen&amp;quot; have been taking place regularly, and the idea is to spread the word for other areas, engaging community members to set up more meetings. Carsten Book of Mozilla and Florian Effenberger of OpenOffice.org, founders of the &amp;quot;Open-Source-Treffen&amp;quot;, introduce their vision and tell about the previous experiences. Audience for this talk are open source communities wishing to set up their own meetings as well as interested users who love to learn more about the idea.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://www.opensourcetreffen.de http://www.opensourcetreffen.de]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:Floeff.jpg]] See [[User:Floeff]]&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== ODF Tools and Resources ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF Tools and Resources&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Talk / 45 mins&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bart Hanssens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bart Hanssens is chairing the OASIS ODF Interop and Conformance TC, co-organizer of the ODF plugfests and has been testing various ODF applications for the Belgian Federal government in his role as Interoperability Expert at Fedict &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session lists the various ODF tools and libraries that are &amp;quot;out there&amp;quot;, and where one can find additional info about ODF itself.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| ODF has become a popular document format, but for new developers it isn&amp;#039;t always clear what open source tools exist and where to find them. This presentations aims to list the most interesting tools, libraries, projects and other resources available. &lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://be.linkedin.com/in/barthanssens&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| (See LinkedIn profile)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===lpOD – languages &amp;amp; platforms OpenDocument=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;lpOD – languages &amp;amp; platforms OpenDocument&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Luis Belmar-Letelier, Charles, JMG and/or Jérôme ? &lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Luis Belmar-Letelier PhD in Physics, CEO of Itaapy a Python agil shop since 2003, work with the ODF Toolkit Union, and is the coordinator of the lpOD project http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Presentation of the lpOD -- languages &amp;amp; platforms OpenDocument &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| lpOD, is a Free Software project that offers, for high level use cases, an application programming interface dedicated to document processing with the Python, Perl and Ruby languages. It’s complying with the Open Document Format (ODF).&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tips and Tricks for Extension Developer=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Tips and Tricks for Extension Developer&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Juergen Schmidt&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Juergen Schmidt is working for Sun Microsystems in the StarOffice group for more then 12 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API and the Extensions project and he is a member of the OpenOffice.org Community Council. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. He speaks frequently about the programmability features of OpenOffice.org on international conferences. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension. Extensions provide often the necessary connector from OpenOffice.org to other software systems and the better they are integrated the better is the overall user experience and the interoperability.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| is coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:jsc.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== New docking windows for a better UI &amp;amp; extension integration ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;New docking windows for a better UI &amp;amp; extension integration&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Carsten Driesner&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Carsten Driesner works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2000. He is the project lead of the framework project since 2006. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The main goal of the framework project is to provide low-level functions (like loading/storing documents, generic UI, OLE, filter management) to the application modules. As the generic OpenOffice.org UI is mainly based on framework code many aspects of the Project Renaissance must be implement there. This presentation wants to provide an overview about our latest plans to provide new and powerful docking window functions.&lt;br /&gt;
The presentation is split up into four different parts:&lt;br /&gt;
1. The current state of docking window design&lt;br /&gt;
2. The new docking window design&lt;br /&gt;
3. How can extensions profit from the new design&lt;br /&gt;
4. Future outlook&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/Framework&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Improving the OpenOffice.org Build System ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Improving the OpenOffice.org Build System&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk, 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bjoern Michaelsen works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2008. He is the a member of the ongoing [[Build Environment Effort]] and a member of the Writer/Framework team at Sun.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The [[Build Environment Effort]] is an ongoing effort to update various aspects of the OpenOffice.org build environment. Some of the aims of this effort require to rethink the basic architecture of how OpenOffice.org is build.&lt;br /&gt;
This talk with present the results so far and how we are planning to go on.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| see http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu for details&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| &lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/build_scalability1&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/a_split_build_for_openoffice (by Mathias Bauer)&lt;br /&gt;
* http://wiki.services.openoffice.org/wiki/Build_Environment_Effort&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:bmichaelsen.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Show me YOUR code ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Show me YOUR code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Workshop, 90-120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Eike Rathke&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Eike Rathke is a core developer and co-lead of the OpenOffice.org Calc spreadsheet application. &amp;lt;br&amp;gt; Working on the spreadsheet core engine, formula compiler and interpreter since 1994. Also working on the number parser/formatter and doing related i18n work. He works for Sun Microsystems.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Show me the code YOU have written and want to be integrated. Talk about, identify and hopefully clear obstacles. Let&amp;#039;s solve remaining problems together.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| The last two FOSDEMs I gave an overview of the Calc spreadsheet interpreter core, and showed how to debug and profile the beast. This year it is time YOU show me YOUR code. Go into details. Discuss your solution. Ask questions. &amp;lt;br&amp;gt; If you would like to dive into your code at the workshop I&amp;#039;d appreciate if you made it available in advance so I can take a look. Send a mail to mailto:erack@sun.com?subject=FOSDEM%20code&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/User:ErAck&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo&lt;br /&gt;
| [[Image:ErAck_128x128.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Just Testing ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Just Testing&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration&lt;br /&gt;
| talk/45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker&lt;br /&gt;
| Stephan Bergmann&lt;br /&gt;
|-&lt;br /&gt;
| Biography&lt;br /&gt;
| Stephan has been working on all kinds of aspects of OpenOffice.org for well over a decade now, as a member of the StarOffice/OpenOffice.org development team at Sun Hamburg.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| OpenOffice.org is too fat and too weird to let you simply apply your standard unit-testing-approach to writing correct code.  Over the years, this has lead to the creation of a number of mechanisms within the OOo code base with which OOo developers can test the code they write and compile.  Some of the mechanisms are, erm, creative, some are trivial.  But what all the mechanisms have in common is that they all are brittle and all start to fail, in one way or another, sooner or later.  Time to clean up. &amp;lt;br/&amp;gt; This talk will discuss where we intend to go, and probably tell a couple of anecdotes about where we came from.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Hidden Pearls&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Thorsten has been hacking on OpenOffice.org for many years.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session presents a few examples of uniquely useful code inside OOo, plus a way for other projects to mine those pearls.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -todo-&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blog.thebehrens.net]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153434</id>
		<title>Conferences/FOSDEM/2010/CFP</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010/CFP&amp;diff=153434"/>
		<updated>2009-12-18T19:28:32Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Proposals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:Call for Papers for the OpenOffice.org and ODF DevRoom@FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=&amp;quot;6&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;Deadline: Friday, December 18th&amp;lt;/font&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==Proposals==&lt;br /&gt;
&lt;br /&gt;
=== Sample  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sample&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org or ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk or workshop / 45, 90 or 120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Max Mustermann&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Max Mustermann is working on the OpenOffice.org project since ...&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session gives an overview of ...&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| longer description of the session content if appropriate&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| links to projects, web pages etc.&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Local community building - Open-Source-Treffen===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Local community building - Open-Source-Treffen&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| Local community building - Open-Source-Treffen&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Florian Effenberger, OpenOffice.org&amp;lt;br&amp;gt;Carsten&amp;amp;nbsp;Book, Mozilla&amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Florian Effenberger has been an open source evangelist for many years. He is co-lead of the international OpenOffice.org marketing project as well as a member of the management board of the non-profit OpenOffice.org Deutschland e.V. He is also a frequent contributor to a variety of professional magazines worldwide.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Mozilla and OpenOffice.org jointly organize so called open source meetings (&amp;quot;Open-Source-Treffen&amp;quot;) in&amp;amp;nbsp;Germany to foster the idea of community building and to support exchange amongst projects and communities. This talk gives an overview of the idea, on what we achieved so far, what our plans for the future are - and how you can help!&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| Most people use open source software day by day. A fact that most of them do not know: Often, this free software is being developed, documented, marketed and improved by volunteers in their free time. Many open source projects work on fostering the idea of free software and open content, and a lot of users benefit from their efforts. Other than with proprietary software, users can get in direct touch with the communites via blogs, IRC channels, mailing lists or forums.&lt;br /&gt;
Despite the modern way of communicating, personal contact still is the best way to get to know each other. Meeting the people behind the names in reality is a great experience, and helps users of finding their way into open source communites to engage themselves. Therefore, Mozilla and OpenOffice.org jointly organize the so-called &amp;quot;Open-Source-Treffen&amp;quot; (&amp;quot;Open Source Meetings&amp;quot;) to help open source projects in meeting their end-users and vice versa. Members of the community can get in touch with their users to gather valueable feedback, and open source adopters meet other supporters from their area.&lt;br /&gt;
&lt;br /&gt;
In the German city of Munich, the &amp;quot;Open-Source-Treffen&amp;quot; have been taking place regularly, and the idea is to spread the word for other areas, engaging community members to set up more meetings. Carsten Book of Mozilla and Florian Effenberger of OpenOffice.org, founders of the &amp;quot;Open-Source-Treffen&amp;quot;, introduce their vision and tell about the previous experiences. Audience for this talk are open source communities wishing to set up their own meetings as well as interested users who love to learn more about the idea.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://www.opensourcetreffen.de http://www.opensourcetreffen.de]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:Floeff.jpg]] See [[User:Floeff]]&amp;lt;br&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== ODF Tools and Resources ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;ODF Tools and Resources&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Talk / 45 mins&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bart Hanssens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bart Hanssens is chairing the OASIS ODF Interop and Conformance TC, co-organizer of the ODF plugfests and has been testing various ODF applications for the Belgian Federal government in his role as Interoperability Expert at Fedict &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session lists the various ODF tools and libraries that are &amp;quot;out there&amp;quot;, and where one can find additional info about ODF itself.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| ODF has become a popular document format, but for new developers it isn&amp;#039;t always clear what open source tools exist and where to find them. This presentations aims to list the most interesting tools, libraries, projects and other resources available. &lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://be.linkedin.com/in/barthanssens&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| (See LinkedIn profile)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===lpOD – languages &amp;amp; platforms OpenDocument=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;lpOD – languages &amp;amp; platforms OpenDocument&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| ODF&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| ?? / ??&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Luis Belmar-Letelier, Charles, JMG and/or Jérôme ? &lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Luis Belmar-Letelier PhD in Physics, CEO of Itaapy a Python agil shop since 2003, work with the ODF Toolkit Union, and is the coordinator of the lpOD project http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Presentation of the lpOD -- languages &amp;amp; platforms OpenDocument &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| lpOD, is a Free Software project that offers, for high level use cases, an application programming interface dedicated to document processing with the Python, Perl and Ruby languages. It’s complying with the Open Document Format (ODF).&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://lpod-project.org&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tips and Tricks for Extension Developer=== &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Tips and Tricks for Extension Developer&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Juergen Schmidt&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Juergen Schmidt is working for Sun Microsystems in the StarOffice group for more then 12 years. He was deeply involved in the development of the UNO component model which is the foundation for the OpenOffice.org API. The OpenOffice.org community is one aspect of his daily work. He is involved in the OpenOffice.org project since the beginning, he is the project lead of the OpenOffice.org API and the Extensions project and he is a member of the OpenOffice.org Community Council. His main goal is to spread the knowledge around the programmability features of OpenOffice.org around the world and to show that it is more than only an office productivity suite. He speaks frequently about the programmability features of OpenOffice.org on international conferences. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The session will give an overview about the Extension infrastructure and will give tips and hints what&amp;#039;s most important to integrate well in OpenOffice.org and to provide a more professional extension. Extensions provide often the necessary connector from OpenOffice.org to other software systems and the better they are integrated the better is the overall user experience and the interoperability.    &lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| is coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:jsc.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== New docking windows for a better UI &amp;amp; extension integration ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;New docking windows for a better UI &amp;amp; extension integration&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Carsten Driesner&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Carsten Driesner works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2000. He is the project lead of the framework project since 2006. &lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The main goal of the framework project is to provide low-level functions (like loading/storing documents, generic UI, OLE, filter management) to the application modules. As the generic OpenOffice.org UI is mainly based on framework code many aspects of the Project Renaissance must be implement there. This presentation wants to provide an overview about our latest plans to provide new and powerful docking window functions.&lt;br /&gt;
The presentation is split up into four different parts:&lt;br /&gt;
1. The current state of docking window design&lt;br /&gt;
2. The new docking window design&lt;br /&gt;
3. How can extensions profit from the new design&lt;br /&gt;
4. Future outlook&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| coming soon...&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/Framework&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Improving the OpenOffice.org Build System ===&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Improving the OpenOffice.org Build System&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk, 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Bjoern Michaelsen&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Bjoern Michaelsen works for Sun Microsystems, Inc. and StarOffice/OpenOffice.org since 2008. He is the a member of the ongoing [[Build Environment Effort]] and a member of the Writer/Framework team at Sun.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| The [[Build Environment Effort]] is an ongoing effort to update various aspects of the OpenOffice.org build environment. Some of the aims of this effort require to rethink the basic architecture of how OpenOffice.org is build.&lt;br /&gt;
This talk with present the results so far and how we are planning to go on.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| see http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu for details&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| &lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/building_openoffice_org_with_gnu&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/build_scalability1&lt;br /&gt;
* http://blogs.sun.com/GullFOSS/entry/a_split_build_for_openoffice (by Mathias Bauer)&lt;br /&gt;
* http://wiki.services.openoffice.org/wiki/Build_Environment_Effort&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [[Image:bmichaelsen.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Show me YOUR code ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Show me YOUR code&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| Workshop, 90-120 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Eike Rathke&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Eike Rathke is a core developer and co-lead of the OpenOffice.org Calc spreadsheet application. &amp;lt;br&amp;gt; Working on the spreadsheet core engine, formula compiler and interpreter since 1994. Also working on the number parser/formatter and doing related i18n work. He works for Sun Microsystems.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| Show me the code YOU have written and want to be integrated. Talk about, identify and hopefully clear obstacles. Let&amp;#039;s solve remaining problems together.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| The last two FOSDEMs I gave an overview of the Calc spreadsheet interpreter core, and showed how to debug and profile the beast. This year it is time YOU show me YOUR code. Go into details. Discuss your solution. Ask questions. &amp;lt;br&amp;gt; If you would like to dive into your code at the workshop I&amp;#039;d appreciate if you made it available in advance so I can take a look. Send a mail to mailto:erack@sun.com?subject=FOSDEM%20code&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| http://wiki.services.openoffice.org/wiki/User:ErAck&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo&lt;br /&gt;
| [[Image:ErAck_128x128.png]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Just Testing ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Just Testing&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic&lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration&lt;br /&gt;
| talk/45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker&lt;br /&gt;
| Stephan Bergmann&lt;br /&gt;
|-&lt;br /&gt;
| Biography&lt;br /&gt;
| Stephan has been working on all kinds of aspects of OpenOffice.org for well over a decade now, as a member of the StarOffice/OpenOffice.org development team at Sun Hamburg.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| OpenOffice.org is too fat and too weird to let you simply apply your standard unit-testing-approach to writing correct code.  Over the years, this has lead to the creation of a number of mechanisms within the OOo code base with which OOo developers can test the code they write and compile.  Some of the mechanisms are, erm, creative, some are trivial.  But what all the mechanisms have in common is that they all are brittle and all start to fail, in one way or another, sooner or later.  Time to clean up. &amp;lt;br/&amp;gt; This talk will discuss where we intend to go, and probably tell a couple of anecdotes about where we came from.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blogs.sun.com/gullfoss http://blogs.sun.com/gullfoss]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| [http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg http://archive.fosdem.org/2009/schedule/images/speaker-270-128x128.jpg]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hidden Pearls - What&amp;#039;s There to ReUse for Other Projects  ===&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#7c9acd&amp;quot;&lt;br /&gt;
| align=&amp;quot;center&amp;quot; colspan=&amp;quot;2&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sample&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| Topic &lt;br /&gt;
| OpenOffice.org&lt;br /&gt;
|-&lt;br /&gt;
| Session/duration &lt;br /&gt;
| talk / 45 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Speaker &lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
|-&lt;br /&gt;
| Biography &lt;br /&gt;
| Thorsten has been hacking on OpenOffice.org for many years.&lt;br /&gt;
|-&lt;br /&gt;
| Abstract (1-2 paragraphs) &lt;br /&gt;
| This session presents a few examples of uniquely useful code inside OOo, plus a way for other projects to mine those pearls.&lt;br /&gt;
|-&lt;br /&gt;
| Description &lt;br /&gt;
| -todo-&lt;br /&gt;
|-&lt;br /&gt;
| Additional speaker info &lt;br /&gt;
| [http://blog.thebehrens.net]&lt;br /&gt;
|-&lt;br /&gt;
| Speaker Photo (128x128 PNG) &lt;br /&gt;
| ....&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=153206</id>
		<title>Conferences/FOSDEM/2010</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2010&amp;diff=153206"/>
		<updated>2009-12-16T22:43:56Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Team */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:FOSDEM 2010}}&lt;br /&gt;
&lt;br /&gt;
[http://www.fosdem.org/2010/ FOSDEM] 6-7 February 2010 in Brussels, Belgium&lt;br /&gt;
 &lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
==Communication Channel==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==DevRoom==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Call for Papers===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Some things that should be taken into account &lt;br /&gt;
* activity title (please try to be descriptive, there are ~250 talks at FOSDEM during the week-end ;)),&lt;br /&gt;
* a short abstract (1-2 paragraphs),&lt;br /&gt;
* a longer description if appropriate,&lt;br /&gt;
* optionally a list of links to the project website or similar&lt;br /&gt;
* for each speaker:&lt;br /&gt;
** the speaker&amp;#039;s real name,&lt;br /&gt;
** a short overview of her bio in a couple of lines,&lt;br /&gt;
** optionally also a longer bio,&lt;br /&gt;
** optionally a picture (please send it to Juergen as 128x128 PNG),&lt;br /&gt;
** optionally links to her website, blog, ... &lt;br /&gt;
&lt;br /&gt;
We have no guarantee so far but probably we can sponsor potential speakers with some funding to at least cover parts of the costs.&lt;br /&gt;
&lt;br /&gt;
====Proposals====&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===Final Schedule===&lt;br /&gt;
...&lt;br /&gt;
&lt;br /&gt;
==Stand/Booth==&lt;br /&gt;
&lt;br /&gt;
Our stand will be most probably in building AW&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Stand Overview&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Time !! Stand staff &lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Saturday 6th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 || &lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 || &lt;br /&gt;
|- &lt;br /&gt;
| 14:00 - 16:00 || &lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 18:00 || &lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sunday 7th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 || &lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 || &lt;br /&gt;
|-&lt;br /&gt;
| 14:00 - 16:00 || &lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 17:00 || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
More info ...&lt;br /&gt;
&lt;br /&gt;
==Saturday Evening OOo Community Event==&lt;br /&gt;
...details will coming soon&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
&lt;br /&gt;
...details will coming soon &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|- bgcolor=&amp;quot;#cddbf6&amp;quot;&lt;br /&gt;
! Name &lt;br /&gt;
! Stay &lt;br /&gt;
! Function &lt;br /&gt;
! Funding request&lt;br /&gt;
|-&lt;br /&gt;
| Juergen Schmidt &lt;br /&gt;
| Friday - Sunday&lt;br /&gt;
| Stand/DevRoom&lt;br /&gt;
| ?&lt;br /&gt;
|-&lt;br /&gt;
| Florian Effenberger&amp;lt;br&amp;gt;&lt;br /&gt;
| probably both days &lt;br /&gt;
| - &lt;br /&gt;
| probably yes ;)&lt;br /&gt;
|-&lt;br /&gt;
| Cor Nouws&amp;lt;br&amp;gt;&lt;br /&gt;
| probably both days &lt;br /&gt;
| - &lt;br /&gt;
| partly&lt;br /&gt;
|-&lt;br /&gt;
| Andrea Pescetti&lt;br /&gt;
| probably one day only&lt;br /&gt;
| ?&lt;br /&gt;
| don&amp;#039;t know&lt;br /&gt;
|-&lt;br /&gt;
| Jacqueline Rahemipour&lt;br /&gt;
| both days&lt;br /&gt;
| &lt;br /&gt;
| partly&lt;br /&gt;
|-&lt;br /&gt;
| Eike Rathke&lt;br /&gt;
| both days&lt;br /&gt;
| Stand / DevRoom&lt;br /&gt;
| maybe&lt;br /&gt;
|-&lt;br /&gt;
| Thorsten Behrens&lt;br /&gt;
| both days&lt;br /&gt;
| Stand / DevRoom&lt;br /&gt;
| likely&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Hotel Recommendation==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [http://www.astridhotel.be/ Hotel Astrid], price at the weekend 69 Euro or Cash&amp;amp;Sleep 59 Euro &lt;br /&gt;
* [http://www.arishotel.be/ Hotel Aris], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
* [http://www.almahotel.be/ Hotel Alma], price at the weekend 75 Euro or Cash&amp;amp;Sleep 65 Euro &lt;br /&gt;
&lt;br /&gt;
Feel free to insert some more recommendations.&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Marketing/Conferences&amp;diff=145726</id>
		<title>Marketing/Conferences</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Marketing/Conferences&amp;diff=145726"/>
		<updated>2009-11-02T16:52:14Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* OpenOffice.org Annual Conference 2009 (Orvieto,ITALY) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Marketing}} &lt;br /&gt;
&lt;br /&gt;
= OpenOffice.org Conferences =&lt;br /&gt;
&lt;br /&gt;
[[Category:Marketing|Conferences]]&lt;br /&gt;
[[Category:OOoCon]]&lt;br /&gt;
[[Category:Conferences|Conferences]]&lt;br /&gt;
&lt;br /&gt;
The OOoCon page on the main website is http://marketing.openoffice.org/conference/&lt;br /&gt;
&lt;br /&gt;
== Future Conferences ==&lt;br /&gt;
&lt;br /&gt;
=== OpenOffice.org Annual Conference 2010 (Budapest,HUNGARY) ===&lt;br /&gt;
The [[OOoCon_2010|OpenOffice.org Conference 2010]] will be held in Budapest, Hungary, in early September 2010. Other details can be found in the proposal: http://marketing.openoffice.org/ooocon2009/cfl/budapest.html&lt;br /&gt;
&lt;br /&gt;
=== OpenOffice.org Annual Conference 2009 (Orvieto,ITALY) ===&lt;br /&gt;
The [[OOoCon_2009|OpenOffice.org Conference 2009]] will be held in Orvieto, Italy, from November 3rd to November 6th 2009. Other details can be found on the following pages: http://marketing.openoffice.org/ooocon2009/&lt;br /&gt;
&lt;br /&gt;
* [[OOoCon_2009_CFP|Call for Papers]]&lt;br /&gt;
* [[OOoCon_2009_Keysigning|Keysigning event]]&lt;br /&gt;
&lt;br /&gt;
== Previous Conferences ==&lt;br /&gt;
&lt;br /&gt;
=== OpenOffice.org Annual Conference 2008 (Beijing,CHINA) ===&lt;br /&gt;
The [[OOoCon_2008|OpenOffice.org Conference 2008]] was held in Beijing, China, from Wednesday 5th November to Friday 7th November. Other details can be found on the following pages: http://marketing.openoffice.org/ooocon2008/&lt;br /&gt;
&lt;br /&gt;
* [[OOoCon_2008_Who_Where_When| OOoCon 2008 Who Where When]]&lt;br /&gt;
* [[OOoCon_2008_Visa_Procedures| OOoCon 2008 Visa Procedures]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=OOoCon_2009_Keysigning&amp;diff=145725</id>
		<title>OOoCon 2009 Keysigning</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=OOoCon_2009_Keysigning&amp;diff=145725"/>
		<updated>2009-11-02T16:51:10Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: Created page with &amp;#039;==Keysigning party at OOoCon 2009==  * after the town visit/diner on Wednesday, 2009-11-04 * see [http://cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html#traditi…&amp;#039;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Keysigning party at OOoCon 2009==&lt;br /&gt;
&lt;br /&gt;
* after the town visit/diner on Wednesday, 2009-11-04&lt;br /&gt;
* see [http://cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html#traditional] for background on the method we&amp;#039;ll use - the &amp;quot;informal party&amp;quot;&lt;br /&gt;
* ideally, bring little sheets of paper with your name, email address, and pgp/gpg fingerprint on it (though we&amp;#039;ll provide pens and paper for the spontaneous visitor)&lt;br /&gt;
** for gpg, this gives your fingerprint &amp;#039;&amp;#039;&amp;#039;gpg --fingerprint &amp;lt;your_email_here&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Build_Verbosity&amp;diff=143749</id>
		<title>Build Verbosity</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Build_Verbosity&amp;diff=143749"/>
		<updated>2009-10-21T15:17:34Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;In CWS [http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fbuildverbosity buildverbosity], probably to be integrated into DEV300.m63, the work [http://blogs.sun.com/GullFOSS/entry/shut_up_or_better_tell started by Rüdiger Timm] and [http://www.openoffice.org/issues/show_bug.cgi?id=84497 Michael Meeks] a while ago has been continued (though probably not finished): The OpenOffice.org build now has extensive support for different verbosity levels.&lt;br /&gt;
&lt;br /&gt;
You control those levels by un/setting an environment variable VERBOSE, or by giving a &amp;lt;code&amp;gt;verbose=...&amp;lt;/code&amp;gt; parameter to the &amp;lt;code&amp;gt;build&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;dmake&amp;lt;/code&amp;gt; call. Three different levels are implemented:&lt;br /&gt;
&amp;lt;dl&amp;gt;&lt;br /&gt;
&amp;lt;dt&amp;gt;&amp;lt;code&amp;gt;VERBOSE=TRUE&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;verbose=true&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;dd&amp;gt;produces the most detailed output. In this mode, the build output is slightly more verbose than what you know up to milestone m62, echoing compiler command lines, and quite some (not all, not by far) commands executed by &amp;lt;code&amp;gt;dmake&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;dt&amp;gt;&amp;lt;code&amp;gt;VERBOSE&amp;lt;/code&amp;gt; not set and &amp;lt;code&amp;gt;verbose&amp;lt;/code&amp;gt; not given&lt;br /&gt;
&amp;lt;dd&amp;gt;produces &amp;quot;normal&amp;quot; output. Nearly no command echos anymore, much less &amp;quot;fill&amp;quot; output, and a lot of tools is less gossipy, too.&lt;br /&gt;
&amp;lt;dt&amp;gt;&amp;lt;code&amp;gt;VERBOSE=FALSE&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;verbose=false&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;dd&amp;gt;Even less output. On Unix platforms, this is near to the &amp;quot;one line of output per file&amp;quot; goal, but not quite there.&lt;br /&gt;
&amp;lt;/dl&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There&amp;#039;s still room for improvement - for instance, some places still emit too much noise even in quiet mode. Also,, the quiet and the normal mode currently do not differ very much. So, one option might be to make the quiet mode &amp;#039;&amp;#039;really&amp;#039;&amp;#039; quiet ...&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=ESC_dashboard&amp;diff=143733</id>
		<title>ESC dashboard</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=ESC_dashboard&amp;diff=143733"/>
		<updated>2009-10-21T11:55:28Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:ESC Dashboard}}&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;4&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;&amp;quot; class=&amp;quot;prettytable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name || Owner || Prio || Due || Notes &lt;br /&gt;
|-&lt;br /&gt;
| CVS to bazaar/git/subversion transition     || Fuhrmann, Meeks, Klose    || 1  || July 2008 for step 1 and Q1 2009 for step2  || Weekly meeting Friday 2pm UTC #oooscm, set up prototypes for evaluation. Details on http://wiki.services.openoffice.org/wiki/OOoSCM_Minutes. SVN and git repository prototypes are available and public accessible (via SSH). There is still no Bazaar import, it is thought that a full bazaar import might be difficult to achieve. We will for now continue with SVN and git. Discover workflows wrt to SVN and git is in progress, templates can be found [[http://wiki.services.openoffice.org/wiki/SCM_Migration#Sun_Hamburg_RE here]]. Next: measure the candidates against the template. Open: Split of git repository just because of performance issues when dealing with big repositories. step 1 : move to subversion first, step 2: revisit bazaar, mercurial, git and come to a final decision in Q1 2009&lt;br /&gt;
|-&lt;br /&gt;
| Unified sign on/Federated Identity     || Fuhrmann    ||  1 || work in progress         || Requirement added to http://wiki.services.openoffice.org/wiki/Infrastructure_Requirements. Gerd Weiss has kicked of the discussion within the website project.  &lt;br /&gt;
|-&lt;br /&gt;
| Wiki/better search, structure     || Peters || 1  ||  work in progress   &lt;br /&gt;
|&lt;br /&gt;
* Wiki Engine Updated to MW 1.13 (Feb 15)&lt;br /&gt;
* Structural hierarchy implemented on wiki/Documentation (wip)&lt;br /&gt;
* Structure of localized wiki sections TBD &lt;br /&gt;
* Implemented crosslink functionality for localized pages&lt;br /&gt;
|-&lt;br /&gt;
| Buildbots     || Fuhrmann, Cheng    || 2  || work in progress   || Gregor Hartmann from Sun and Bao Honglin from Redflag CH2000 assigned to this task. Kick of on IRC has taken place on Dec 19, the agenda and log can be found [[http://wiki.services.openoffice.org/wiki/BuildBot_Meeting here]]. A buildbot has been brought online by the RedFlag team. Work on a Mac build bot kicked of in June.    &lt;br /&gt;
|-&lt;br /&gt;
| CWS Upload area  || Hollmichel    || 2  || done, April &amp;#039;08  ||      authentication work under way to get up-load with EIS, expected end of Feb 08.&lt;br /&gt;
|-&lt;br /&gt;
| reduce storage needed for l10n builds, related to modularization issues || Hütsch || 2 || not earlier than OOo 3.3  ||     &lt;br /&gt;
|-&lt;br /&gt;
| help content should be platform independent ||  Peters || 2 ||  After OOo 3.1     ||     &lt;br /&gt;
|-&lt;br /&gt;
| Language Packs/Dictionaries to be moved to extensions, modularization || Hütsch || 2  || OOo 3.2         || Configuration nailed down to make dictionaries as extensions. With OOo 3.0 dictionaries has come as extension. In 3.2 timeframe the language pack/dictionary issue will be adressed.&lt;br /&gt;
|-&lt;br /&gt;
| Language Fallback to en-US must be fixed (help img fallback doesn&amp;#039;t work) || Bauer || 2 || OOo 3.1         || Issue existent. Mathias to follow up on img fallback problem, Target is OOo 3.1&lt;br /&gt;
|-&lt;br /&gt;
| Access to translation data to be moved to Pootle || Braconi || 2 || completed          ||     25 languages have been uploaded. Here the [http://wiki.services.openoffice.org/wiki/Pootle_Integration_Roadmap Pootle_Roadmap]. Pootle server on arsaperta.org has been removed (announced by Charles Schultz). OOo and Sun Vendors are working with Pootle on sunvirtuallab: http://www.sunvirtuallab.com:32300/projects/openoffice_org/. Due to additional request, Sun/G11n will set up a second Pootle server to host additional languages. Machine has already been requested and approved. The second Pootle server has been set up in July/August &amp;#039;08.&lt;br /&gt;
|-&lt;br /&gt;
| Process and tools to allow localization of wiki content || Braconi || 2 || work in progress, OOo 3.0         ||Workflow at:http://wiki.services.openoffice.org/wiki/Image:OOo_Wiki_process.png The progress can be viewed at: http://wiki.services.openoffice.org/wiki/L10n_Wiki_Process_for_Documentation. A pilot to translate the MediWiki content will run in August/September &amp;#039;08 time frame.&lt;br /&gt;
|-&lt;br /&gt;
| email (offline) access to bugtracking || Fuhrmann || 2 || pending   || Requirement added to http://wiki.services.openoffice.org/wiki/Infrastructure_Requirements and handed over to Sun team which evaluates hosting efforts.&lt;br /&gt;
|-&lt;br /&gt;
| make cvs artwork authoritative  || Bauer || 3 || completed || Matthias talked to the owner of the image tool. The tool does corret updates, so people are able to deal with images within CVS directly without getting any conflicts.      &lt;br /&gt;
|-&lt;br /&gt;
| create checklist for full open source compliance for developers || Engelhard || 1 || waiting for feedback on documentation license status (Frank)         ||      &lt;br /&gt;
|-&lt;br /&gt;
| QA Unit tests || Meeks, Hütsch || 2 || incremental improvements, open ended tasks || get unit test infrastructure into environment, next step get unit test written by all, patch 87469 is pending&lt;br /&gt;
|-&lt;br /&gt;
| Make high impact bug reports visible || Hollmichel || 2 ||  work in progress, Q1 2008        || [[http://www.openoffice.org/issues/showdependencytree.cgi?id=81913 Ubuntu]], [[http://www.openoffice.org/issues/showdependencytree.cgi?id=84291 Redflag 2000]] [[http://www.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&amp;amp;issue_type=DEFECT&amp;amp;issue_type=ENHANCEMENT&amp;amp;issue_type=FEATURE&amp;amp;issue_type=TASK&amp;amp;issue_type=PATCH&amp;amp;issue_status=UNCONFIRMED&amp;amp;issue_status=NEW&amp;amp;issue_status=STARTED&amp;amp;issue_status=REOPENED&amp;amp;issue_status=RESOLVED&amp;amp;issue_status=VERIFIED&amp;amp;issue_status=CLOSED&amp;amp;email1=&amp;amp;emailtype1=exact&amp;amp;emailassigned_to1=1&amp;amp;email2=&amp;amp;emailtype2=exact&amp;amp;emailreporter2=1&amp;amp;issueidtype=include&amp;amp;issue_id=&amp;amp;changedin=&amp;amp;votes=&amp;amp;chfieldfrom=&amp;amp;chfieldto=&amp;amp;chfieldvalue=&amp;amp;short_desc=&amp;amp;short_desc_type=allwords&amp;amp;long_desc=&amp;amp;long_desc_type=allwords&amp;amp;issue_file_loc=&amp;amp;issue_file_loc_type=fulltext&amp;amp;status_whiteboard=&amp;amp;status_whiteboard_type=fulltext&amp;amp;keywords=&amp;amp;keywords_type=anytokens&amp;amp;field0-0-0=blocked&amp;amp;type0-0-0=equals&amp;amp;value0-0-0=90439&amp;amp;cmdtype=doit&amp;amp;namedcmd=micheal&amp;amp;newqueryname=&amp;amp;order=Reuse+same+sort+as+last+time Fedora]]&lt;br /&gt;
|-&lt;br /&gt;
| fast legal reviews for external modules || Hollmichel || 2 || completed         ||  [[http://www.openoffice.org/issues/showdependencytree.cgi?id=86166 Meta Issue 86166]]  &lt;br /&gt;
|-&lt;br /&gt;
| easy integration of small fixes || Bauer, Hollmichel, Meeks || 2 || work in progress   || aim to get developer process/time overhead for integrating suitably trivial fixes down to the 10minute range. Agreed on proposal: [[FixesOnMaster]], communication in Release Status meeting needs to be done&lt;br /&gt;
|-&lt;br /&gt;
| more ways of being diverse in the source code || Meeks || 3  ||          || get agreement on including distro-specific patches, artwork, per-distro configuration options etc. into the (D)RCS, and look at ways of making existing hard-to-configure things (eg. settings defaults) build-time configurable. It has been agreed that a patch process is desired, searching an owner for implementation&lt;br /&gt;
|-&lt;br /&gt;
| Modularization, independent Apps  || Cheng, Meeks, Hütsch || 3 ||  TBD   ||       &lt;br /&gt;
|-&lt;br /&gt;
| Modularization, build on installed OOo, small developer packages  || Meeks || 2 || pending         ||  Petr is going to work on that on go-oo, see issue [[http://qa.openoffice.org/issues/show_bug.cgi?id=100265]]&lt;br /&gt;
|-&lt;br /&gt;
| Modularization, smaller, independent packages  || Hütsch || 1  || in progress, target for step 1 OOo 3.0    || see three layered packaging by Ramme, Bergmann     &lt;br /&gt;
|-&lt;br /&gt;
|  ||  ||  ||          ||     &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:ESC]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Mercurial_Pilot&amp;diff=137963</id>
		<title>Mercurial Pilot</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Mercurial_Pilot&amp;diff=137963"/>
		<updated>2009-08-21T12:22:37Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Example */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Mercurial]][[Category:SCM]]&lt;br /&gt;
=Mercurial Pilot=&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
==Purpose==&lt;br /&gt;
To find out if our DSCM tool of choice can stand the harsh realities of the OOo development process. The OOo code base is pretty huge and we want to know if there are scalability and usability issues before we commit ourselves to a (hopefully) very long lasting SCM tool for OpenOffice.org. After all, SCM migrations are no fun, indeed.&lt;br /&gt;
&lt;br /&gt;
==Timeline==&lt;br /&gt;
&lt;br /&gt;
The OOo Mercurial pilot is expected to last at least 2 month. This is necessary to ensure that some &amp;quot;old enough&amp;quot; hg hosted child workspaces exist to check out how well the updating/re-sychronizing/re-basing works, something which is considerably painful with SVN. If we find that the pilot doesn&amp;#039;t expose some hidden Mercurial problems, we will switch over completely to Mercurial as soon as the necessary infrastructure for a full scale hg usage is in place. If substantial problems surfaces during the pilot we might extend the pilot time frame to see if the problem can be overcome, or, in an extreme case, even set up a new pilot with git or bazaar.&lt;br /&gt;
&lt;br /&gt;
==The details==&lt;br /&gt;
&lt;br /&gt;
* The pilot will only cover the main development code line (aka trunk in SVN).&lt;br /&gt;
* The master repository can be found here: http://hg.services.openoffice.org/hg/DEV300. This repository is hourly updated from the SVN trunk.&lt;br /&gt;
* After a CWS is finished and QAed, it is necessary to pull/merge/push one final time in case of expected conflicts to help the REs with clean patches. &lt;br /&gt;
* RE will pull from your hg hosted CWS, export your changes and apply it as patch to the SVN trunk.&lt;br /&gt;
&lt;br /&gt;
==What the pilot covers==&lt;br /&gt;
* The complete CWS life cycle from a developers point of view, this includes cloning, committing, pulling, merging, re-basing and transplanting changesets from other CWSs &lt;br /&gt;
* Parts of the CWS handling for RE: pulling from developers, merging.&lt;br /&gt;
&lt;br /&gt;
==What is not covered==&lt;br /&gt;
* Transplanting changesets from a release code line to the main development line. RE will set up separate tests for this. &lt;br /&gt;
* Integration is done via SVN, thus pushing to the master repository on the remote server by REs is not tested. No problem, this repository is only by convention different from developer repositories.&lt;br /&gt;
&lt;br /&gt;
==Caveats==&lt;br /&gt;
&lt;br /&gt;
Since every change will still have to be integrated via SVN there are a few caveats which you will need to consider if you plan to participate in the pilot:&lt;br /&gt;
&lt;br /&gt;
* Your changesets will loose their identity during integration. This might create problems if you cross merged changesets between several CWSs.&lt;br /&gt;
* Integration will lump all changeset of your CWS into one single changeset. &lt;br /&gt;
* The single changeset commit during integration will contain of course only a single commit log. If possible I&amp;#039;ll try to lump all commit logs of your changesets together via scripting. Alternatively REs will accept a detailed commit log supplied by you.&lt;br /&gt;
* The author of the hg changesets is lost as well because a RE engineer will do the integration commit to SVN. If scripting works we&amp;#039;ll include the original author info into the commit log.&lt;br /&gt;
* Be careful with renaming files. If you do a lot of renaming you&amp;#039;ll most probable cause a lot of stress on the integrator. Remember, the RE integrate your CWS via diff and patch. Also, all restrictions of SVN regarding the renaming of files/directories still apply. If you plan to do a lot of renaming please do it on a SVN based repository. Or better, if possible, wait for the final switch to hg.&lt;br /&gt;
* Tinderboxes, buildbots etc will have to be adapted to Mercurial, this will take some time.&lt;br /&gt;
&lt;br /&gt;
==I&amp;#039;m an OOo domain developer, what to do if I want to participate?==&lt;br /&gt;
&lt;br /&gt;
Please send me (hr@openoffice.org) a note that you plan to participate. I will setup your public ssh key so you can push your changesets to an outgoing repository on hg.services.openoffice.org. It&amp;#039;s not mandatory that you use this server to publish your changes, but at integration time latest the RE will naturally need to access your repository somewhere. It is planned to offer this server as central publishing point for OOo CWSs to ease the development coordination. An overview of active hg hosted CWSs can be found here: http://hg.services.openoffice.org/hg/cws.&lt;br /&gt;
&lt;br /&gt;
==Example==&lt;br /&gt;
&lt;br /&gt;
Let&amp;#039;s say you want to participate in the pilot with your new CWS &amp;#039;mycws&amp;#039;, based on DEV300 m47. The steps are:&lt;br /&gt;
(see [[OOo and Mercurial]] for general mercurial workflow info)&lt;br /&gt;
&lt;br /&gt;
* clone the repository the repository from the master server into a pristine local copy (best w/o tree)&lt;br /&gt;
 $ hg clone -U -r DEV300_m47 http://hg.services.openoffice.org/hg/DEV300 local_DEV300&lt;br /&gt;
&lt;br /&gt;
Why use &amp;#039;-r DEV300_m47&amp;#039; here? During the pilot the master repository will be hourly updated from /trunk of the SVN server. Since /trunk  may not be buildable all the time (for instance during integrations) as a consequence the tip of the master hg repository may not be buildable as well. The situation will change after the switch to Mercurial. RE will only push complete milestones to the repository so you can safely use the tip of the repository. Why use a pristine intermediate local repository? Well, the current repository size is ~1.1 GB, cloning from the server can take from about 50min up to several hours if you are unlucky. You want to do this only once.&lt;br /&gt;
* clone into your cws&lt;br /&gt;
 $ hg clone local_DEV300 mycws&lt;br /&gt;
Note: don&amp;#039;t use &amp;#039;-r DEV300_m47 here, if you followed the steps above you know that the tip of repository local_DEV300 is at milestone DEV300_m48. Without &amp;#039;-r&amp;#039; hg can use optimizations like hard linking the repository if both repository are on the same disk.[http://blogs.sun.com/GullFOSS/entry/mercurial_pilot_fast_local_clones] Besides you&amp;#039;ll encounter the one unintuitive &amp;lt;strike&amp;gt;bug&amp;lt;/strike&amp;gt;[http://www.selenic.com/mercurial/wiki/GitConcepts#head-944e6c0ababa25ffb900b7a5d4f6ee0391cb9092 feature] I have seen so far in Mercurial. If the clone is created with -r &amp;lt;tag&amp;gt;, the clone will contain everything up to the tag &amp;#039;&amp;#039;excluding&amp;#039;&amp;#039; the tag itself.&lt;br /&gt;
* configure, etc&lt;br /&gt;
* create a dummy entry for your CWS in the SVN repository, register your CWS with EIS&lt;br /&gt;
 $ cws create -m m47 DEV300 mycws&lt;br /&gt;
* send me (hr@openoffice.org) a note with name and the current milestone of your CWS if you plan to use hg.services.openoffice.org as outgoing server. I&amp;#039;ll then create a server side clone of the master repository to serve as your outgoing repository. This saves time (270000 changesets less to push over the line) and server diskspace (hard links). This operation will be the first candidate for automation, of course ... &lt;br /&gt;
* hack away in your CWS ...&lt;br /&gt;
* push your changes to the outgoing repository for publishing if you feel so&lt;br /&gt;
 $ hg push  ssh://hg@hg.services.openoffice.org/cws/mycws&lt;br /&gt;
* pull/merge from the repository to re-synchronize your CWS from a new milestone, say DEV300_m52&lt;br /&gt;
 $ hg pull -r DEV300_m52 http://hg.services.openoffice.org/hg/DEV300&lt;br /&gt;
 $ hg merge&lt;br /&gt;
Note: if you haven&amp;#039;t published your repository yet, &amp;#039;hg rebase&amp;#039; is an option to consider.&lt;br /&gt;
* QA,fixes, etc&lt;br /&gt;
* final pull/merge/push cycle to ease the integration into SVN trunk.&lt;br /&gt;
&lt;br /&gt;
==Mercurial documentation and other resources==&lt;br /&gt;
&lt;br /&gt;
* Main Mercurial web presence: http://www.selenic.com/mercurial/wiki/&lt;br /&gt;
* Mercurial book: [http://hgbook.red-bean.com/ Mercurial: The Definitive Guide]&lt;br /&gt;
&lt;br /&gt;
==Mercurial extensions you might want to have look at==&lt;br /&gt;
&lt;br /&gt;
* hg rebase: git style rebasing instead of pull/merge&lt;br /&gt;
* hg transplant: cherry picking of changsets from other CWSs&lt;br /&gt;
* hg win32text: if you work on windows&lt;br /&gt;
&lt;br /&gt;
==Things that may surprise former CVS or SVN users==&lt;br /&gt;
&lt;br /&gt;
* hg clone -r &amp;lt;tag&amp;gt; &amp;lt;from_rep&amp;gt; &amp;lt;to_rep&amp;gt; will clone everything up to the tagged revsion &amp;#039;&amp;#039;excluding&amp;#039;&amp;#039; the tag. See explanation above.&lt;br /&gt;
* hg resolve does a very different thing than svn resolve. Read the man page.&lt;br /&gt;
* Many hg commands work on the whole repository if no path is specified, no &amp;#039;&amp;#039;matter where your current working directory is inside the source tree&amp;#039;&amp;#039;. Example: &amp;quot;cd DEV300/sw/source; hg status&amp;quot; will compute the status of the whole source tree (which might take a minute depending on IO bandwidth). Use &amp;quot;cd DEV300/sw/source; hg status .&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Tips and Tricks==&lt;br /&gt;
&lt;br /&gt;
* After pulling/merging: &lt;br /&gt;
** &amp;quot;hg log --follow-first&amp;quot; is a convenient way to display your CWS changes at the top of the log.&lt;br /&gt;
** &amp;quot;hg log --follow-first -P &amp;lt;original_clone_milestone&amp;gt;&amp;quot; will show only the CWS changesets.&lt;br /&gt;
** &amp;quot;hg outgoing&amp;quot; works as well, of course.&lt;br /&gt;
* Combined diff which contains exactly the changes of your CWS without anything pulled from master&lt;br /&gt;
** If your current milestone tag is locally available: hg diff -r &amp;lt;current_milestone_tag&amp;gt;&lt;br /&gt;
** If your current milestone tag is *not* locally available (might happen, see above): &lt;br /&gt;
***search for your last pull/merge from the master with &amp;quot;hg log -m&amp;quot;&lt;br /&gt;
*** &amp;quot;hg diff -r &amp;lt;second_parent_of_last_master_merge&amp;gt;&amp;quot;&lt;br /&gt;
** Alternatively, if you just did a pull/merge from master: &amp;quot;hg export --switch-parent tip&amp;quot;&lt;br /&gt;
* The default output format of some commands does not suit you? Use styles:&lt;br /&gt;
**&amp;quot;hg log --style=compact&amp;quot;&lt;br /&gt;
**&amp;quot;hg outgoing --style=changelog&amp;quot;&lt;br /&gt;
* Or create your own format with the template engine:&lt;br /&gt;
**&amp;quot;hg outgoing --template &amp;#039;{date|shortdate} {author|person} {desc}\n&amp;#039; --newest-first&amp;quot;&lt;br /&gt;
* Accessing repository over ssh using Tortoise Hg on Windows&lt;br /&gt;
** If you want to use the ssh client of your Cygwin shell (and also ssh-agent), add the following to the [ui] section of your mercurial.ini: ssh = ssh&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Ooo-build&amp;diff=117802</id>
		<title>Ooo-build</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Ooo-build&amp;diff=117802"/>
		<updated>2009-03-31T08:49:37Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This collection of patches, artwork and build infrastructure exists solely as a reflection of the many problems encouraging reasonably responsive change up-stream. The process of change is painful for any organisation, the larger the more painful. However - the size of the problem is no excuse to not try; hence the evenutal aim is to remove the need for ooo-build by incrementally fixing the various problems.&lt;br /&gt;
&lt;br /&gt;
== About ooo-build ==&lt;br /&gt;
&lt;br /&gt;
ooo-build arose from acute frustration with the bad-old days of OOo process before the [[CWS|Child Workspace]] concept was introduced, it is&lt;br /&gt;
also fueled by a non-performant [[Infrastructure_Problems#CVS|CVS server]].&lt;br /&gt;
&lt;br /&gt;
* [[ooo-build/bin]] - A description of the tools in bin/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Checking out ==&lt;br /&gt;
To check out trunk ooo-build from the fd.o git repository, run one of the following in the command line:&lt;br /&gt;
&lt;br /&gt;
 git clone git://anongit.freedesktop.org/git/ooo-build/ooo-build&lt;br /&gt;
 git clone ssh://[username@]git.freedesktop.org/git/ooo-build/ooo-build (trunk via ssh tunnel)&lt;br /&gt;
&lt;br /&gt;
If you need to work on a branch:&lt;br /&gt;
&lt;br /&gt;
 git checkout -b ooo-build-3-0-1 origin/ooo-build-3-0-1&lt;br /&gt;
&lt;br /&gt;
(see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt fd.o wiki] for authoritative info)&lt;br /&gt;
&lt;br /&gt;
== Making a patch on a set of files ==&lt;br /&gt;
You can use git locally and it&amp;#039;s really great for larger tasks.&lt;br /&gt;
&lt;br /&gt;
 make patch.apply&lt;br /&gt;
 cd build/current&lt;br /&gt;
 git init&lt;br /&gt;
 ../../bin/create-gitignores.sh&lt;br /&gt;
 git add sc&lt;br /&gt;
 git commit -m &amp;quot;initial&amp;quot;&lt;br /&gt;
&lt;br /&gt;
And from now on you can locally commit to sc (git commit -a) until you are happy. &lt;br /&gt;
To generate the patch, just&lt;br /&gt;
 git diff --no-prefix&lt;br /&gt;
You can see the diff from your initial commit with this command&lt;br /&gt;
 git diff --no-prefix HEAD^&lt;br /&gt;
To remove the git tracking :&lt;br /&gt;
 rm -rf .git&lt;br /&gt;
&lt;br /&gt;
You can also think of more fancy use of git, like having a master branch for applying the patches, and other branches to track history of development you are doing, or use it to actually edit existing patches, to merge patches, etc.  In that case, it is useful to track history of the entire tree; to do that, use&lt;br /&gt;
 git add .&lt;br /&gt;
instead of the &amp;#039;git add sc&amp;#039; in the example above.&lt;br /&gt;
&lt;br /&gt;
Some people prefer stacked git (stg) over plain git when juggling with patches, after the initial &amp;quot;git init; git add .; git commit -a&amp;quot; do a &amp;quot;stg init&amp;quot; - and read the nice manual page.&lt;br /&gt;
&lt;br /&gt;
== Adding Patch ==&lt;br /&gt;
&lt;br /&gt;
One of the main ooo-build features is the ability to apply patches against the upstream sources. A patch can be added the following way:&lt;br /&gt;
&lt;br /&gt;
* propose a patch file name:&lt;br /&gt;
** the file suffix &amp;#039;&amp;#039;.diff&amp;#039;&amp;#039; is required&lt;br /&gt;
** the file name &amp;#039;&amp;#039;&amp;lt;theme&amp;gt;-short-fix-description.diff&amp;#039;&amp;#039; is suggested when there are more thematic patches, e.g. &amp;#039;&amp;#039;warnigns&amp;#039;&amp;#039;, &amp;#039;&amp;#039;unittesting&amp;#039;&amp;#039;, &amp;#039;&amp;#039;speed&amp;#039;&amp;#039; that are not put in any thematic directory&lt;br /&gt;
** the file name &amp;#039;&amp;#039;&amp;lt;module&amp;gt;-short-fix-description.diff&amp;#039;&amp;#039; is suggested when the patch modifies only one source &amp;#039;&amp;#039;module&amp;#039;&amp;#039;, e&amp;#039;g&amp;#039; &amp;#039;&amp;#039;vcl&amp;#039;&amp;#039;, &amp;#039;&amp;#039;svx&amp;#039;&amp;#039;, &amp;#039;&amp;#039;sd&amp;#039;&amp;#039;&lt;br /&gt;
** the file name cws-&amp;lt;name&amp;gt; should be used for CWS backports&lt;br /&gt;
** the file name &amp;#039;&amp;#039;short-fix-description.diff&amp;#039;&amp;#039; is enough otherwise&lt;br /&gt;
* create the patch in the format to be applied in the top source directory with &amp;#039;&amp;#039;-P0&amp;#039;&amp;#039;, see the sample content:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:--- jvmfwk/plugins/sunmajor/pluginlib/gnujre.cxx.old    2007-08-10 17:32:26.0000&lt;br /&gt;
*:+++ jvmfwk/plugins/sunmajor/pluginlib/gnujre.cxx        2007-08-16 22:40:42.0000&lt;br /&gt;
*:@@ -78,6 +78,7 @@ char const* const* GnuInfo::getJavaExePa &lt;br /&gt;
*:...&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
*put the patch below &amp;#039;&amp;#039;ooo-build/patches/&amp;lt;group&amp;gt;&amp;#039;&amp;#039;; most patches are located in the MWS specific directory. Some bigger groups of patches have their own thematic directory. For example:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:patches/src680/sc-save-split-view.diff&lt;br /&gt;
*:patches/src680/warning-return-values-filter.diff&lt;br /&gt;
*:&lt;br /&gt;
*:patches/scsolver/scsolver-source-inc-basedlg-hxx.diff&lt;br /&gt;
*:patches/scsolver/scsolver-source-inc-baselistener-hxx.diff&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
* mention the patch in the &amp;#039;&amp;#039;apply&amp;#039;&amp;#039; file:&lt;br /&gt;
**ooo-build allows to sort the patches into groups and apply them conditionaly &amp;#039;&amp;#039;&amp;#039;by distributions&amp;#039;&amp;#039;&amp;#039;. Therefore, each patch has to be mentioned in the &amp;#039;&amp;#039;&amp;#039;right section&amp;#039;&amp;#039;&amp;#039; in the &amp;#039;&amp;#039;apply&amp;#039;&amp;#039; file. This file is usually located in the MWS-specific directory, e.g. &amp;#039;&amp;#039;patches/src680/apply&amp;#039;&amp;#039;.&lt;br /&gt;
**the patch entry might look like:&lt;br /&gt;
**: &amp;lt;pre&amp;gt;&lt;br /&gt;
**: [ CalcFixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # Support Hungarian localized keywords for CELL and INFO functions.&lt;br /&gt;
**: sc-celltrans-hungarian-keywords.diff, i#80299, kohei&lt;br /&gt;
**: # Fix saving split-view information on 64-bit platforms.&lt;br /&gt;
**: sc-save-split-view.diff, n#235131, i#81936, jonp&amp;lt;/pre&amp;gt;&lt;br /&gt;
**please do not forget to mention the &amp;#039;&amp;#039;&amp;#039;issue numbers&amp;#039;&amp;#039;&amp;#039; and the responsible &amp;#039;&amp;#039;&amp;#039;developer name&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**note that the patches are applied in the order in which they are listed in the apply file. If there are some conflicts between the patches, it might be necessary to &amp;#039;&amp;#039;&amp;#039;split a section&amp;#039;&amp;#039;&amp;#039;, for example:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**: [ Fixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # make unzip command not ask when overwriting files&lt;br /&gt;
**: unzip-command.diff, i#81087, fridrich&lt;br /&gt;
**:&lt;br /&gt;
**: [ CalcFixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: #fix import filter for userforms with calc specific data ( rowsource ) &lt;br /&gt;
**: svx-filter-userform-rowsource.diff, i#73753&lt;br /&gt;
**:&lt;br /&gt;
**:[ Fixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # edit fields text displaying&lt;br /&gt;
**: svx-sdrobjeditview-update-edit-area.diff, n#305205, rodo&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Committing a Change ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The following process describes how to commit any change to the ooo-build:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
* do your changes&lt;br /&gt;
* create a changelog entry:&lt;br /&gt;
** list all the modified files; hint: use the command &amp;#039;&amp;#039;&amp;#039;svn stat&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** add a good description of the changes&lt;br /&gt;
** mention the related issue or bug numbers&lt;br /&gt;
** for example, it might look like:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**:2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
**:&lt;br /&gt;
**:        * patches/src680/xmlhelp-work-with-symlinks.diff, patches/src680/apply:&lt;br /&gt;
**:          display help correctly even when the files are symlinked, i#81138&lt;br /&gt;
**:&amp;lt;/pre&amp;gt;&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - if it took some more time to finish the changes, there is a high chance that anybody else committed another change and it might be necessary to resolve conflicts&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn stat&amp;#039;&amp;#039;&amp;#039; - it is a good practice to double check that only the expected files are modified&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn diff&amp;#039;&amp;#039;&amp;#039; - it is a good practice to double check all changes, especially after resolving some conflicts&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039; - use the same text for SVN changelog that was used for the &amp;#039;&amp;#039;Changelog&amp;#039;&amp;#039; file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Releasing ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
When there&amp;#039;s a particularly good reason for a release, such as a distro needs a stable base or we want to do something potentially&lt;br /&gt;
disruptive, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
&lt;br /&gt;
* Read back through the &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039; and update the &amp;#039;&amp;#039;NEWS&amp;#039;&amp;#039; file for the release, summarizing and attributing the changes.&lt;br /&gt;
&lt;br /&gt;
* edit &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;, bump the version in the &amp;#039;&amp;#039;&amp;#039;AC_INIT&amp;#039;&amp;#039;&amp;#039; line, incrementing the minor version eg. &amp;#039;&amp;#039;&amp;#039;AC_INIT(ooo-build, X.Y.Z)&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* Add a line to any handy &amp;#039;&amp;#039;ChangeLogs&amp;#039;&amp;#039;, so we can easily see where this happened in the flow:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
            * Version X.Y.Z&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039; - so what&amp;#039;s there is what&amp;#039;s there. If there was a collision you get to loop to the first stage here, but don&amp;#039;t re-increment the number.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn -r &amp;lt;id&amp;gt; copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/&amp;lt;tree&amp;gt;/ svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/tags/OOO_BUILD_X_Y_Z&amp;#039;&amp;#039;&amp;#039; - this creates a copy of the current state so we can reproduce the build at any time and easily diff between releases. The &amp;#039;&amp;#039;&amp;#039;id&amp;#039;&amp;#039;&amp;#039; is the revision number printed when the &amp;#039;&amp;#039;&amp;#039;commit&amp;#039;&amp;#039;&amp;#039; command finishes, e.g. &amp;#039;&amp;#039;10364&amp;#039;&amp;#039;. The &amp;#039;&amp;#039;&amp;#039;tree&amp;#039;&amp;#039;&amp;#039; is either &amp;#039;&amp;#039;trunk&amp;#039;&amp;#039; or &amp;#039;&amp;#039;branches/ooo-build-M-N&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;./autogen.sh&amp;#039;&amp;#039;&amp;#039; - this re-builds configure with the version in place; a distro must be specified eg. &amp;#039;&amp;#039;&amp;#039;./autogen.sh --with-distro=GoOoLinux&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;make dist&amp;#039;&amp;#039;&amp;#039; - this builds the archive containing everything.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;md5sum ooo-build-X.Y.Z.tar.gz &amp;gt; ooo-build-X.Y.Z.tar.gz.md5&amp;#039;&amp;#039;&amp;#039; - so that users can do at least the basic consistency check&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;scp ooo-build-X.Y.Z.tar.gz* ooweb@seagull.dreamhost.com:~/download.go-oo.org/&amp;lt;MWS_DIR&amp;gt;/&amp;#039;&amp;#039;&amp;#039; - uploads the tarball and the .md5 file for the right Master Work Space, eg. SRC680&lt;br /&gt;
&lt;br /&gt;
* It&amp;#039;s then customary to announce the release, see the template in &amp;#039;&amp;#039;doc/announce.txt&amp;#039;&amp;#039; - update all the ***s to the right versions, insert the contents of &amp;#039;&amp;#039;NEWS&amp;#039;&amp;#039;, fire and forget.&lt;br /&gt;
&lt;br /&gt;
== Branching ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
When there&amp;#039;s a particularly good reason for a branch, such as a MWS is moved to the maintenace mode and we want open TRUNK for further development, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* create the branch and anchor copies:&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/tags/OOO_BUILD_X_Y_Z svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/branches/ooo-build-M-N&amp;#039;&amp;#039;&amp;#039; - do the branch for OOo-M.N from a previous release of ooo-build-X.Y.Z&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/tags/branches/ooo-build-M-N svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/tags/OOO-BUILD-M-K-ANCHOR&amp;#039;&amp;#039;&amp;#039; - this creates a copy of the current state so we can diff against it and see the branch specific changes&lt;br /&gt;
* make changes specific for the original tree (TRUNK):&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn co svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/&amp;lt;tree&amp;gt;/ ooo-build&amp;#039;&amp;#039;&amp;#039; - get sources from the original tree, either from &amp;#039;&amp;#039;trunk&amp;#039;&amp;#039; or &amp;#039;&amp;#039;branches/ooo-build-M-N&amp;#039;&amp;#039;.&lt;br /&gt;
** if it is an important branch, such as for a minor OOo version, add a line to the message printed at the end of &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;. It might be something like: &lt;br /&gt;
**:&amp;lt;tt&amp;gt;ooo-build-X-Y-Z  branch for X.Y.Z&amp;lt;/tt&amp;gt;&lt;br /&gt;
** add a line to any handy &amp;#039;&amp;#039;ChangeLogs&amp;#039;&amp;#039;, so we can easily see where this happened in the flow. Of course, if you branched an older tag, you must put the comment into the right context. See below for a sample comment.&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* make changes specific for the branch:&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn co svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/branches/ooo-build-M-N ooo-build-M-N&amp;#039;&amp;#039;&amp;#039; - get sources from the branch&lt;br /&gt;
** modify the message printed at the end of &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;. It might be something like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;This is ooo-build-2-0-4 - the stable branch for the 2.0.4 release.&amp;lt;br&amp;gt;If you want to build something cool, unstable, and risky, use trunk.&amp;lt;/tt&amp;gt;&lt;br /&gt;
** add the same comment to the &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039; as in the original tree&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* it&amp;#039;s then customary to announce the release&lt;br /&gt;
&lt;br /&gt;
Sample comment:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    * Branched for X.Y.Z:                                                   &lt;br /&gt;
          OOO-BUILD-X-Y-Z-ANCHOR - the anchor tag,                              &lt;br /&gt;
          ooo-build-2-0-4 - the branch.                                         &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Support for new MWS ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
When the upstream branches new MWS and we want to support it in ooo-build, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* first, it is better to clean ooo-build and remove support for all old and obsolete milestones; FIXME: it will be described somewhere else&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
*edit &amp;#039;&amp;#039;download.in&amp;#039;&amp;#039;, mention the new tarball file name and URL in the array &amp;#039;&amp;#039;%SRC_URLS&amp;#039;&amp;#039;, something like:&lt;br /&gt;
*:&amp;lt;tt&amp;gt;               &amp;#039;oox680-m.*&amp;#039;                         =&amp;gt; &amp;#039;@MIRROR@/OOX680&amp;#039;,&amp;lt;/tt&amp;gt;&lt;br /&gt;
*edit &amp;#039;&amp;#039;patches/src680/apply&amp;#039;&amp;#039;&lt;br /&gt;
**fix the &amp;#039;&amp;#039;OLDEST_SUPPORTED&amp;#039;&amp;#039; option; note that more MWSs can be supported, it might be something like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;OLDEST_SUPPORTED=src680-m181,ooe680-m1&amp;lt;/tt&amp;gt;&lt;br /&gt;
**fix the conditions for the various sections; note that you must add condition for the new MWS everywhere where a condition for another MWS already exists; it might look like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;[ Fixes &amp;gt;= src680-m182 &amp;gt;= ooe680-m2 ]&amp;lt;/tt&amp;gt;&lt;br /&gt;
*might want to use the new milestone by default, then update &amp;#039;&amp;#039;DEFAULT_TAG&amp;#039;&amp;#039; in &amp;#039;&amp;#039;configure&amp;#039;&amp;#039; in, it looks like:&lt;br /&gt;
*:&amp;lt;tt&amp;gt;DEFAULT_TAG=oox680-mY&amp;lt;/tt&amp;gt;&lt;br /&gt;
*describe all changes in &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039;; it is usually enough to mention something like:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
*:  &lt;br /&gt;
*:        * configure.in, download.in, patches/src680/apply: support for oox680&lt;br /&gt;
*:        * configure.in: Default to oox680-mY&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
*it&amp;#039;s then customary to announce this kind of change&lt;br /&gt;
&lt;br /&gt;
== Support for final OOo version ==&lt;br /&gt;
&lt;br /&gt;
When the upstream releases final version of a MWS, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* must check whether the final sources differ from the latest milestone; if the sources are the same, only symlink is made at go-oo.org/packages; new sources are created otherwise; the new tarball name is something like &amp;#039;&amp;#039;OOO_X_Y_Z&amp;#039;&amp;#039;&lt;br /&gt;
* do all the steps as in case of [[ooo-build#Support for new MWS|support for new MWS]] with the following modifications:&lt;br /&gt;
** use the tarball name &amp;#039;&amp;#039;OOO_X_Y_Z&amp;#039;&amp;#039; instead of the MWS- and milestone-based name &amp;#039;&amp;#039;oox680-mY&amp;#039;&amp;#039;&lt;br /&gt;
** if the sources are only symlinks to the lates milestone, hack &amp;#039;&amp;#039;bin/unpack&amp;#039;&amp;#039;, so it creates the symlink to the unpacked sources; it might look like:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**:if test -d oox680-mY -a ! -d OOO_X_Y_Z ; then&lt;br /&gt;
**:    echo &amp;quot;Linking rcZ to X.Y.Z&amp;quot;&lt;br /&gt;
**:    ln -sf oox680-mY OOO_X_Y_Z&lt;br /&gt;
**:fi&lt;br /&gt;
**:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remaining unsolved issue summary ==&lt;br /&gt;
&lt;br /&gt;
A helpful summary of these is provided here in no particular order along with suggestions for improvement.&lt;br /&gt;
Many of these are mercifully easy to fix, and should be fixed soon.&lt;br /&gt;
&lt;br /&gt;
=== source handling ===&lt;br /&gt;
&lt;br /&gt;
ooo-build has a post-configure &amp;#039;download&amp;#039; mechanism, whereby the relevant source archives will be automatically downloaded to your system having configured it, in response to your various options.&lt;br /&gt;
&lt;br /&gt;
=== non-responsiveness / lack of leadership ===&lt;br /&gt;
&lt;br /&gt;
Many ooo-build patches are ready for up-streaming but there is no / little response from up-stream. Worse there is the perception that taking leadership and actually doing something about merging fixes would be firmly opposed. Finally - even when maintainers are active, responsive &amp;amp; friendly - there is no agreed mechanism for blanket&lt;br /&gt;
approving fixes - or sub-types of trivial fixes, which thus tend to fester in IssueZilla.&lt;br /&gt;
&lt;br /&gt;
At the time of writing ooo-build&amp;#039;s patches are available here: http://go-oo.org/ooo-build/patches/src680/apply.&lt;br /&gt;
&lt;br /&gt;
=== font substitution ===&lt;br /&gt;
&lt;br /&gt;
Many vendors ship AGFA&amp;#039;s propriatory metric-compatible fonts with OO.o - it is thus necessary to run several seds on the VCL.xcu [ further bloating this already gigantic messy beast ]. We also remove some of the more foolish &amp;amp;amp; enthusiastic font-usage of eg. the metrically-extremely-strange bitstream font eg. &amp;lt;code&amp;gt;bin/font-munge.pl&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    s/(Bitstream Vera Sans;.*)Albany;/Albany;$1/;&lt;br /&gt;
    # add AMT fonts&lt;br /&gt;
    s/Albany;/Albany AMT;Albany;/g;&lt;br /&gt;
    s/albany;/albanyamt;albany;/g;&lt;br /&gt;
&lt;br /&gt;
=== no &amp;#039;UI&amp;#039; team ===&lt;br /&gt;
&lt;br /&gt;
The up-stream UI team have come up with master-pieces of UI design such as the Yes/No dialog on&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Would you like to not continue saving in the original OpenOffice.org 2.0 format or perhaps switch to another format&amp;quot;&lt;br /&gt;
&lt;br /&gt;
that takes 10 seconds to parse each time ( presumably since it&amp;#039;s a recent feature - with a specification too ).&lt;br /&gt;
&lt;br /&gt;
The rest of us mere-mortals know that the UI in OO.o is &amp;lt;b&amp;gt;shockingly&amp;lt;/b&amp;gt; broken - and hence are eager to fix it&lt;br /&gt;
without being blocked &amp;amp; frustrated for weeks by those responsible for the current mess.&lt;br /&gt;
&lt;br /&gt;
A number of the changes / patches in apply/ are blocked on &amp;#039;user experience&amp;#039; feedback.&lt;br /&gt;
&lt;br /&gt;
=== different defaults ===&lt;br /&gt;
&lt;br /&gt;
It is self evident to ooo-build users that a slew of dialogs on 1st run is a painful mess; eg. if there are settings to migrate, don&amp;#039;t shout about it - do it silently. Furthermore - the registration dialog looks tacky,&lt;br /&gt;
we disable both. We also alter a number of other defaults. cf. the last point - I&amp;#039;m optimistic that these will&lt;br /&gt;
~never get up-stream agreement.&lt;br /&gt;
&lt;br /&gt;
=== bleeding-edgeness ===&lt;br /&gt;
&lt;br /&gt;
There is a &amp;#039;cool factor&amp;#039; to building the very latest things yourself; and helping solve problems with them.&lt;br /&gt;
It&amp;#039;s nice to be able to see your changes have an effect &amp;amp;amp; help others rapidly, eg. a fix being immediately&lt;br /&gt;
useful to other people. Of course - you can have too much of a good thing here but ...&lt;br /&gt;
&lt;br /&gt;
=== Philosophical differences ===&lt;br /&gt;
&lt;br /&gt;
==== compatibility ====&lt;br /&gt;
&lt;br /&gt;
Up-stream believe that the most important data set to be compatible with is existing [[StarOffice]] / OO.o users.&lt;br /&gt;
ooo-build users believe that nearly all the world&amp;#039;s data is stored in Microsoft Office format - hence we&lt;br /&gt;
sacrifice legacy support for better interop.&lt;br /&gt;
This is of course a continuum, up-stream are at the luny extreme of pushing back-compatibility regardless&lt;br /&gt;
of it&amp;#039;s impact on interoperability, even in cases deliberately excluding useful interoperability improvements&lt;br /&gt;
on that basis. ooo-build appreciates backwards comaptibility, but is in favour of viewing core differences&lt;br /&gt;
that are non-interoperable as bugs not features.&lt;br /&gt;
&lt;br /&gt;
==== process complexity ====&lt;br /&gt;
&lt;br /&gt;
ooo-build users believe in programmer lead development, with strong peer review and user QA.&lt;br /&gt;
up-stream believe in process based development, with teams, consensus building, specification writing, test-instead-of-detailed-code-review-or-unit-testing, and all these &amp;#039;Professional&amp;#039; pasttimes.&lt;br /&gt;
ooo-build users believe the OO.o we have today is broadly a product of these processes. Up-stream users&lt;br /&gt;
believe the previous sentence is a compliment.&lt;br /&gt;
&lt;br /&gt;
==== cross-platform ====&lt;br /&gt;
&lt;br /&gt;
ooo-build enables patch sub-setting, thus we include patches for features (eg. Mono integration) that are&lt;br /&gt;
most likely not well separated, and will break the Win32 build. Of course, for ooo-build these are not&lt;br /&gt;
enabled on Win32 thus causing no problem. This is an impediment to getting work up-stream. Hopefully&lt;br /&gt;
the &amp;#039;experimental&amp;#039; process may help encourage good behavior here.&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
&lt;br /&gt;
If you read all that don&amp;#039;t get depressed - these issues can all be fixed - many of them almost painlessly. We hope to shrink this page quickly.&lt;br /&gt;
&lt;br /&gt;
[[Category: Development]]&lt;br /&gt;
[[Category:Build_System]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Ooo-build&amp;diff=117801</id>
		<title>Ooo-build</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Ooo-build&amp;diff=117801"/>
		<updated>2009-03-31T08:47:31Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Checking out */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This collection of patches, artwork and build infrastructure exists solely as a reflection of the many problems encouraging reasonably responsive change up-stream. The process of change is painful for any organisation, the larger the more painful. However - the size of the problem is no excuse to not try; hence the evenutal aim is to remove the need for ooo-build by incrementally fixing the various problems.&lt;br /&gt;
&lt;br /&gt;
== About ooo-build ==&lt;br /&gt;
&lt;br /&gt;
ooo-build arose from acute frustration with the bad-old days of OOo process before the [[CWS|Child Workspace]] concept was introduced, it is&lt;br /&gt;
also fueled by a non-performant [[Infrastructure_Problems#CVS|CVS server]].&lt;br /&gt;
&lt;br /&gt;
* [[ooo-build/bin]] - A description of the tools in bin/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Checking out ==&lt;br /&gt;
To check out trunk ooo-build from the fd.o git repository, run one of the following in the command line:&lt;br /&gt;
&lt;br /&gt;
 git clone git://anongit.freedesktop.org/git/ooo-build/ooo-build&lt;br /&gt;
 git clone ssh://[username@]git.freedesktop.org/git/ooo-build/ooo-build (trunk via ssh tunnel)&lt;br /&gt;
&lt;br /&gt;
If you need to work on a branch:&lt;br /&gt;
&lt;br /&gt;
 git checkout -b ooo-build-3-0-1 origin/ooo-build-3-0-1&lt;br /&gt;
&lt;br /&gt;
(see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt fd.o wiki] for authoritative info)&lt;br /&gt;
&lt;br /&gt;
== Making a patch on a set of files ==&lt;br /&gt;
You can use git locally and it&amp;#039;s really great for larger tasks.&lt;br /&gt;
&lt;br /&gt;
 make patch.apply&lt;br /&gt;
 cd build/current&lt;br /&gt;
 git init&lt;br /&gt;
 ../../bin/create-gitignores.sh&lt;br /&gt;
 git add sc&lt;br /&gt;
 git commit -m &amp;quot;initial&amp;quot;&lt;br /&gt;
&lt;br /&gt;
And from now on you can locally commit to sc (git commit -a) until you are happy. &lt;br /&gt;
To generate the patch, just&lt;br /&gt;
 git diff --no-prefix&lt;br /&gt;
You can see the diff from your initial commit with this command&lt;br /&gt;
 git diff --no-prefix HEAD^&lt;br /&gt;
To remove the git tracking :&lt;br /&gt;
 rm -rf .git&lt;br /&gt;
&lt;br /&gt;
You can also think of more fancy use of git, like having a master branch for applying the patches, and other branches to track history of development you are doing, or use it to actually edit existing patches, to merge patches, etc.  In that case, it is useful to track history of the entire tree; to do that, use&lt;br /&gt;
 git add .&lt;br /&gt;
instead of the &amp;#039;git add sc&amp;#039; in the example above.&lt;br /&gt;
&lt;br /&gt;
Some people prefer stacked git (stg) over plain git when juggling with patches, after the initial &amp;quot;git init; git add .; git commit -a&amp;quot; do a &amp;quot;stg init&amp;quot; - and read the nice manual page.&lt;br /&gt;
&lt;br /&gt;
== Adding Patch ==&lt;br /&gt;
&lt;br /&gt;
One of the main ooo-build features is the ability to apply patches against the upstream sources. A patch can be added the following way:&lt;br /&gt;
&lt;br /&gt;
* propose a patch file name:&lt;br /&gt;
** the file suffix &amp;#039;&amp;#039;.diff&amp;#039;&amp;#039; is required&lt;br /&gt;
** the file name &amp;#039;&amp;#039;&amp;lt;theme&amp;gt;-short-fix-description.diff&amp;#039;&amp;#039; is suggested when there are more thematic patches, e.g. &amp;#039;&amp;#039;warnigns&amp;#039;&amp;#039;, &amp;#039;&amp;#039;unittesting&amp;#039;&amp;#039;, &amp;#039;&amp;#039;speed&amp;#039;&amp;#039; that are not put in any thematic directory&lt;br /&gt;
** the file name &amp;#039;&amp;#039;&amp;lt;module&amp;gt;-short-fix-description.diff&amp;#039;&amp;#039; is suggested when the patch modifies only one source &amp;#039;&amp;#039;module&amp;#039;&amp;#039;, e&amp;#039;g&amp;#039; &amp;#039;&amp;#039;vcl&amp;#039;&amp;#039;, &amp;#039;&amp;#039;svx&amp;#039;&amp;#039;, &amp;#039;&amp;#039;sd&amp;#039;&amp;#039;&lt;br /&gt;
** the file name cws-&amp;lt;name&amp;gt; should be used for CWS backports&lt;br /&gt;
** the file name &amp;#039;&amp;#039;short-fix-description.diff&amp;#039;&amp;#039; is enough otherwise&lt;br /&gt;
* create the patch in the format to be applied in the top source directory with &amp;#039;&amp;#039;-P0&amp;#039;&amp;#039;, see the sample content:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:--- jvmfwk/plugins/sunmajor/pluginlib/gnujre.cxx.old    2007-08-10 17:32:26.0000&lt;br /&gt;
*:+++ jvmfwk/plugins/sunmajor/pluginlib/gnujre.cxx        2007-08-16 22:40:42.0000&lt;br /&gt;
*:@@ -78,6 +78,7 @@ char const* const* GnuInfo::getJavaExePa &lt;br /&gt;
*:...&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
*put the patch below &amp;#039;&amp;#039;ooo-build/patches/&amp;lt;group&amp;gt;&amp;#039;&amp;#039;; most patches are located in the MWS specific directory. Some bigger groups of patches have their own thematic directory. For example:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:patches/src680/sc-save-split-view.diff&lt;br /&gt;
*:patches/src680/warning-return-values-filter.diff&lt;br /&gt;
*:&lt;br /&gt;
*:patches/scsolver/scsolver-source-inc-basedlg-hxx.diff&lt;br /&gt;
*:patches/scsolver/scsolver-source-inc-baselistener-hxx.diff&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
* mention the patch in the &amp;#039;&amp;#039;apply&amp;#039;&amp;#039; file:&lt;br /&gt;
**ooo-build allows to sort the patches into groups and apply them conditionaly &amp;#039;&amp;#039;&amp;#039;by distributions&amp;#039;&amp;#039;&amp;#039;. Therefore, each patch has to be mentioned in the &amp;#039;&amp;#039;&amp;#039;right section&amp;#039;&amp;#039;&amp;#039; in the &amp;#039;&amp;#039;apply&amp;#039;&amp;#039; file. This file is usually located in the MWS-specific directory, e.g. &amp;#039;&amp;#039;patches/src680/apply&amp;#039;&amp;#039;.&lt;br /&gt;
**the patch entry might look like:&lt;br /&gt;
**: &amp;lt;pre&amp;gt;&lt;br /&gt;
**: [ CalcFixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # Support Hungarian localized keywords for CELL and INFO functions.&lt;br /&gt;
**: sc-celltrans-hungarian-keywords.diff, i#80299, kohei&lt;br /&gt;
**: # Fix saving split-view information on 64-bit platforms.&lt;br /&gt;
**: sc-save-split-view.diff, n#235131, i#81936, jonp&amp;lt;/pre&amp;gt;&lt;br /&gt;
**please do not forget to mention the &amp;#039;&amp;#039;&amp;#039;issue numbers&amp;#039;&amp;#039;&amp;#039; and the responsible &amp;#039;&amp;#039;&amp;#039;developer name&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**note that the patches are applied in the order in which they are listed in the apply file. If there are some conflicts between the patches, it might be necessary to &amp;#039;&amp;#039;&amp;#039;split a section&amp;#039;&amp;#039;&amp;#039;, for example:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**: [ Fixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # make unzip command not ask when overwriting files&lt;br /&gt;
**: unzip-command.diff, i#81087, fridrich&lt;br /&gt;
**:&lt;br /&gt;
**: [ CalcFixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: #fix import filter for userforms with calc specific data ( rowsource ) &lt;br /&gt;
**: svx-filter-userform-rowsource.diff, i#73753&lt;br /&gt;
**:&lt;br /&gt;
**:[ Fixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # edit fields text displaying&lt;br /&gt;
**: svx-sdrobjeditview-update-edit-area.diff, n#305205, rodo&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Committing a Change ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
The following process describes how to commit any change to the ooo-build:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
* do your changes&lt;br /&gt;
* create a changelog entry:&lt;br /&gt;
** list all the modified files; hint: use the command &amp;#039;&amp;#039;&amp;#039;svn stat&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** add a good description of the changes&lt;br /&gt;
** mention the related issue or bug numbers&lt;br /&gt;
** for example, it might look like:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**:2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
**:&lt;br /&gt;
**:        * patches/src680/xmlhelp-work-with-symlinks.diff, patches/src680/apply:&lt;br /&gt;
**:          display help correctly even when the files are symlinked, i#81138&lt;br /&gt;
**:&amp;lt;/pre&amp;gt;&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - if it took some more time to finish the changes, there is a high chance that anybody else committed another change and it might be necessary to resolve conflicts&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn stat&amp;#039;&amp;#039;&amp;#039; - it is a good practice to double check that only the expected files are modified&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn diff&amp;#039;&amp;#039;&amp;#039; - it is a good practice to double check all changes, especially after resolving some conflicts&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039; - use the same text for SVN changelog that was used for the &amp;#039;&amp;#039;Changelog&amp;#039;&amp;#039; file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Releasing ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
When there&amp;#039;s a particularly good reason for a release, such as a distro needs a stable base or we want to do something potentially&lt;br /&gt;
disruptive, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
&lt;br /&gt;
* Read back through the &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039; and update the &amp;#039;&amp;#039;NEWS&amp;#039;&amp;#039; file for the release, summarizing and attributing the changes.&lt;br /&gt;
&lt;br /&gt;
* edit &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;, bump the version in the &amp;#039;&amp;#039;&amp;#039;AC_INIT&amp;#039;&amp;#039;&amp;#039; line, incrementing the minor version eg. &amp;#039;&amp;#039;&amp;#039;AC_INIT(ooo-build, X.Y.Z)&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* Add a line to any handy &amp;#039;&amp;#039;ChangeLogs&amp;#039;&amp;#039;, so we can easily see where this happened in the flow:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
            * Version X.Y.Z&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039; - so what&amp;#039;s there is what&amp;#039;s there. If there was a collision you get to loop to the first stage here, but don&amp;#039;t re-increment the number.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn -r &amp;lt;id&amp;gt; copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/&amp;lt;tree&amp;gt;/ svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/tags/OOO_BUILD_X_Y_Z&amp;#039;&amp;#039;&amp;#039; - this creates a copy of the current state so we can reproduce the build at any time and easily diff between releases. The &amp;#039;&amp;#039;&amp;#039;id&amp;#039;&amp;#039;&amp;#039; is the revision number printed when the &amp;#039;&amp;#039;&amp;#039;commit&amp;#039;&amp;#039;&amp;#039; command finishes, e.g. &amp;#039;&amp;#039;10364&amp;#039;&amp;#039;. The &amp;#039;&amp;#039;&amp;#039;tree&amp;#039;&amp;#039;&amp;#039; is either &amp;#039;&amp;#039;trunk&amp;#039;&amp;#039; or &amp;#039;&amp;#039;branches/ooo-build-M-N&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;./autogen.sh&amp;#039;&amp;#039;&amp;#039; - this re-builds configure with the version in place; a distro must be specified eg. &amp;#039;&amp;#039;&amp;#039;./autogen.sh --with-distro=GoOoLinux&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;make dist&amp;#039;&amp;#039;&amp;#039; - this builds the archive containing everything.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;md5sum ooo-build-X.Y.Z.tar.gz &amp;gt; ooo-build-X.Y.Z.tar.gz.md5&amp;#039;&amp;#039;&amp;#039; - so that users can do at least the basic consistency check&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;scp ooo-build-X.Y.Z.tar.gz* ooweb@seagull.dreamhost.com:~/download.go-oo.org/&amp;lt;MWS_DIR&amp;gt;/&amp;#039;&amp;#039;&amp;#039; - uploads the tarball and the .md5 file for the right Master Work Space, eg. SRC680&lt;br /&gt;
&lt;br /&gt;
* It&amp;#039;s then customary to announce the release, see the template in &amp;#039;&amp;#039;doc/announce.txt&amp;#039;&amp;#039; - update all the ***s to the right versions, insert the contents of &amp;#039;&amp;#039;NEWS&amp;#039;&amp;#039;, fire and forget.&lt;br /&gt;
&lt;br /&gt;
== Branching ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
When there&amp;#039;s a particularly good reason for a branch, such as a MWS is moved to the maintenace mode and we want open TRUNK for further development, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* create the branch and anchor copies:&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/tags/OOO_BUILD_X_Y_Z svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/branches/ooo-build-M-N&amp;#039;&amp;#039;&amp;#039; - do the branch for OOo-M.N from a previous release of ooo-build-X.Y.Z&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/tags/branches/ooo-build-M-N svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/tags/OOO-BUILD-M-K-ANCHOR&amp;#039;&amp;#039;&amp;#039; - this creates a copy of the current state so we can diff against it and see the branch specific changes&lt;br /&gt;
* make changes specific for the original tree (TRUNK):&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn co svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/&amp;lt;tree&amp;gt;/ ooo-build&amp;#039;&amp;#039;&amp;#039; - get sources from the original tree, either from &amp;#039;&amp;#039;trunk&amp;#039;&amp;#039; or &amp;#039;&amp;#039;branches/ooo-build-M-N&amp;#039;&amp;#039;.&lt;br /&gt;
** if it is an important branch, such as for a minor OOo version, add a line to the message printed at the end of &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;. It might be something like: &lt;br /&gt;
**:&amp;lt;tt&amp;gt;ooo-build-X-Y-Z  branch for X.Y.Z&amp;lt;/tt&amp;gt;&lt;br /&gt;
** add a line to any handy &amp;#039;&amp;#039;ChangeLogs&amp;#039;&amp;#039;, so we can easily see where this happened in the flow. Of course, if you branched an older tag, you must put the comment into the right context. See below for a sample comment.&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* make changes specific for the branch:&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn co svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/branches/ooo-build-M-N ooo-build-M-N&amp;#039;&amp;#039;&amp;#039; - get sources from the branch&lt;br /&gt;
** modify the message printed at the end of &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;. It might be something like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;This is ooo-build-2-0-4 - the stable branch for the 2.0.4 release.&amp;lt;br&amp;gt;If you want to build something cool, unstable, and risky, use trunk.&amp;lt;/tt&amp;gt;&lt;br /&gt;
** add the same comment to the &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039; as in the original tree&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* it&amp;#039;s then customary to announce the release&lt;br /&gt;
&lt;br /&gt;
Sample comment:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    * Branched for X.Y.Z:                                                   &lt;br /&gt;
          OOO-BUILD-X-Y-Z-ANCHOR - the anchor tag,                              &lt;br /&gt;
          ooo-build-2-0-4 - the branch.                                         &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Support for new MWS ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
When the upstream branches new MWS and we want to support it in ooo-build, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* first, it is better to clean ooo-build and remove support for all old and obsolete milestones; FIXME: it will be described somewhere else&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
*edit &amp;#039;&amp;#039;download.in&amp;#039;&amp;#039;, mention the new tarball file name and URL in the array &amp;#039;&amp;#039;%SRC_URLS&amp;#039;&amp;#039;, something like:&lt;br /&gt;
*:&amp;lt;tt&amp;gt;               &amp;#039;oox680-m.*&amp;#039;                         =&amp;gt; &amp;#039;@MIRROR@/OOX680&amp;#039;,&amp;lt;/tt&amp;gt;&lt;br /&gt;
*edit &amp;#039;&amp;#039;patches/src680/apply&amp;#039;&amp;#039;&lt;br /&gt;
**fix the &amp;#039;&amp;#039;OLDEST_SUPPORTED&amp;#039;&amp;#039; option; note that more MWSs can be supported, it might be something like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;OLDEST_SUPPORTED=src680-m181,ooe680-m1&amp;lt;/tt&amp;gt;&lt;br /&gt;
**fix the conditions for the various sections; note that you must add condition for the new MWS everywhere where a condition for another MWS already exists; it might look like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;[ Fixes &amp;gt;= src680-m182 &amp;gt;= ooe680-m2 ]&amp;lt;/tt&amp;gt;&lt;br /&gt;
*might want to use the new milestone by default, then update &amp;#039;&amp;#039;DEFAULT_TAG&amp;#039;&amp;#039; in &amp;#039;&amp;#039;configure&amp;#039;&amp;#039; in, it looks like:&lt;br /&gt;
*:&amp;lt;tt&amp;gt;DEFAULT_TAG=oox680-mY&amp;lt;/tt&amp;gt;&lt;br /&gt;
*describe all changes in &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039;; it is usually enough to mention something like:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
*:  &lt;br /&gt;
*:        * configure.in, download.in, patches/src680/apply: support for oox680&lt;br /&gt;
*:        * configure.in: Default to oox680-mY&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
*it&amp;#039;s then customary to announce this kind of change&lt;br /&gt;
&lt;br /&gt;
== Support for final OOo version ==&lt;br /&gt;
&lt;br /&gt;
When the upstream releases final version of a MWS, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* must check whether the final sources differ from the latest milestone; if the sources are the same, only symlink is made at go-oo.org/packages; new sources are created otherwise; the new tarball name is something like &amp;#039;&amp;#039;OOO_X_Y_Z&amp;#039;&amp;#039;&lt;br /&gt;
* do all the steps as in case of [[ooo-build#Support for new MWS|support for new MWS]] with the following modifications:&lt;br /&gt;
** use the tarball name &amp;#039;&amp;#039;OOO_X_Y_Z&amp;#039;&amp;#039; instead of the MWS- and milestone-based name &amp;#039;&amp;#039;oox680-mY&amp;#039;&amp;#039;&lt;br /&gt;
** if the sources are only symlinks to the lates milestone, hack &amp;#039;&amp;#039;bin/unpack&amp;#039;&amp;#039;, so it creates the symlink to the unpacked sources; it might look like:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**:if test -d oox680-mY -a ! -d OOO_X_Y_Z ; then&lt;br /&gt;
**:    echo &amp;quot;Linking rcZ to X.Y.Z&amp;quot;&lt;br /&gt;
**:    ln -sf oox680-mY OOO_X_Y_Z&lt;br /&gt;
**:fi&lt;br /&gt;
**:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remaining unsolved issue summary ==&lt;br /&gt;
&lt;br /&gt;
A helpful summary of these is provided here in no particular order along with suggestions for improvement.&lt;br /&gt;
Many of these are mercifully easy to fix, and should be fixed soon.&lt;br /&gt;
&lt;br /&gt;
=== source handling ===&lt;br /&gt;
&lt;br /&gt;
ooo-build has a post-configure &amp;#039;download&amp;#039; mechanism, whereby the relevant source archives will be automatically downloaded to your system having configured it, in response to your various options.&lt;br /&gt;
&lt;br /&gt;
=== non-responsiveness / lack of leadership ===&lt;br /&gt;
&lt;br /&gt;
Many ooo-build patches are ready for up-streaming but there is no / little response from up-stream. Worse there is the perception that taking leadership and actually doing something about merging fixes would be firmly opposed. Finally - even when maintainers are active, responsive &amp;amp; friendly - there is no agreed mechanism for blanket&lt;br /&gt;
approving fixes - or sub-types of trivial fixes, which thus tend to fester in IssueZilla.&lt;br /&gt;
&lt;br /&gt;
At the time of writing ooo-build&amp;#039;s patches are available here: http://go-oo.org/ooo-build/patches/src680/apply.&lt;br /&gt;
&lt;br /&gt;
=== font substitution ===&lt;br /&gt;
&lt;br /&gt;
Many vendors ship AGFA&amp;#039;s propriatory metric-compatible fonts with OO.o - it is thus necessary to run several seds on the VCL.xcu [ further bloating this already gigantic messy beast ]. We also remove some of the more foolish &amp;amp;amp; enthusiastic font-usage of eg. the metrically-extremely-strange bitstream font eg. &amp;lt;code&amp;gt;bin/font-munge.pl&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    s/(Bitstream Vera Sans;.*)Albany;/Albany;$1/;&lt;br /&gt;
    # add AMT fonts&lt;br /&gt;
    s/Albany;/Albany AMT;Albany;/g;&lt;br /&gt;
    s/albany;/albanyamt;albany;/g;&lt;br /&gt;
&lt;br /&gt;
=== no &amp;#039;UI&amp;#039; team ===&lt;br /&gt;
&lt;br /&gt;
The up-stream UI team have come up with master-pieces of UI design such as the Yes/No dialog on&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Would you like to not continue saving in the original OpenOffice.org 2.0 format or perhaps switch to another format&amp;quot;&lt;br /&gt;
&lt;br /&gt;
that takes 10 seconds to parse each time ( presumably since it&amp;#039;s a recent feature - with a specification too ).&lt;br /&gt;
&lt;br /&gt;
The rest of us mere-mortals know that the UI in OO.o is &amp;lt;b&amp;gt;shockingly&amp;lt;/b&amp;gt; broken - and hence are eager to fix it&lt;br /&gt;
without being blocked &amp;amp; frustrated for weeks by those responsible for the current mess.&lt;br /&gt;
&lt;br /&gt;
A number of the changes / patches in apply/ are blocked on &amp;#039;user experience&amp;#039; feedback.&lt;br /&gt;
&lt;br /&gt;
=== different defaults ===&lt;br /&gt;
&lt;br /&gt;
It is self evident to ooo-build users that a slew of dialogs on 1st run is a painful mess; eg. if there are settings to migrate, don&amp;#039;t shout about it - do it silently. Furthermore - the registration dialog looks tacky,&lt;br /&gt;
we disable both. We also alter a number of other defaults. cf. the last point - I&amp;#039;m optimistic that these will&lt;br /&gt;
~never get up-stream agreement.&lt;br /&gt;
&lt;br /&gt;
=== bleeding-edgeness ===&lt;br /&gt;
&lt;br /&gt;
There is a &amp;#039;cool factor&amp;#039; to building the very latest things yourself; and helping solve problems with them.&lt;br /&gt;
It&amp;#039;s nice to be able to see your changes have an effect &amp;amp;amp; help others rapidly, eg. a fix being immediately&lt;br /&gt;
useful to other people. Of course - you can have too much of a good thing here but ...&lt;br /&gt;
&lt;br /&gt;
=== Philosophical differences ===&lt;br /&gt;
&lt;br /&gt;
==== compatibility ====&lt;br /&gt;
&lt;br /&gt;
Up-stream believe that the most important data set to be compatible with is existing [[StarOffice]] / OO.o users.&lt;br /&gt;
ooo-build users believe that nearly all the world&amp;#039;s data is stored in Microsoft Office format - hence we&lt;br /&gt;
sacrifice legacy support for better interop.&lt;br /&gt;
This is of course a continuum, up-stream are at the luny extreme of pushing back-compatibility regardless&lt;br /&gt;
of it&amp;#039;s impact on interoperability, even in cases deliberately excluding useful interoperability improvements&lt;br /&gt;
on that basis. ooo-build appreciates backwards comaptibility, but is in favour of viewing core differences&lt;br /&gt;
that are non-interoperable as bugs not features.&lt;br /&gt;
&lt;br /&gt;
==== process complexity ====&lt;br /&gt;
&lt;br /&gt;
ooo-build users believe in programmer lead development, with strong peer review and user QA.&lt;br /&gt;
up-stream believe in process based development, with teams, consensus building, specification writing, test-instead-of-detailed-code-review-or-unit-testing, and all these &amp;#039;Professional&amp;#039; pasttimes.&lt;br /&gt;
ooo-build users believe the OO.o we have today is broadly a product of these processes. Up-stream users&lt;br /&gt;
believe the previous sentence is a compliment.&lt;br /&gt;
&lt;br /&gt;
==== cross-platform ====&lt;br /&gt;
&lt;br /&gt;
ooo-build enables patch sub-setting, thus we include patches for features (eg. Mono integration) that are&lt;br /&gt;
most likely not well separated, and will break the Win32 build. Of course, for ooo-build these are not&lt;br /&gt;
enabled on Win32 thus causing no problem. This is an impediment to getting work up-stream. Hopefully&lt;br /&gt;
the &amp;#039;experimental&amp;#039; process may help encourage good behavior here.&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
&lt;br /&gt;
If you read all that don&amp;#039;t get depressed - these issues can all be fixed - many of them almost painlessly. We hope to shrink this page quickly.&lt;br /&gt;
&lt;br /&gt;
[[Category: Development]]&lt;br /&gt;
[[Category:Build_System]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Ooo-build&amp;diff=117800</id>
		<title>Ooo-build</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Ooo-build&amp;diff=117800"/>
		<updated>2009-03-31T08:46:48Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: (partially) updated for git move&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This collection of patches, artwork and build infrastructure exists solely as a reflection of the many problems encouraging reasonably responsive change up-stream. The process of change is painful for any organisation, the larger the more painful. However - the size of the problem is no excuse to not try; hence the evenutal aim is to remove the need for ooo-build by incrementally fixing the various problems.&lt;br /&gt;
&lt;br /&gt;
== About ooo-build ==&lt;br /&gt;
&lt;br /&gt;
ooo-build arose from acute frustration with the bad-old days of OOo process before the [[CWS|Child Workspace]] concept was introduced, it is&lt;br /&gt;
also fueled by a non-performant [[Infrastructure_Problems#CVS|CVS server]].&lt;br /&gt;
&lt;br /&gt;
* [[ooo-build/bin]] - A description of the tools in bin/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Checking out ==&lt;br /&gt;
To check out trunk ooo-build from the fd.o git repository, run one of the following in the command line:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
git clone git://anongit.freedesktop.org/git/ooo-build/ooo-build&lt;br /&gt;
git clone ssh://[username@]git.freedesktop.org/git/ooo-build/ooo-build (trunk via ssh tunnel)&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need to work on a branch:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
git checkout -b ooo-build-3-0-1 origin/ooo-build-3-0-1&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt fd.o wiki] for authoritative info)&lt;br /&gt;
&lt;br /&gt;
== Making a patch on a set of files ==&lt;br /&gt;
You can use git locally and it&amp;#039;s really great for larger tasks.&lt;br /&gt;
&lt;br /&gt;
 make patch.apply&lt;br /&gt;
 cd build/current&lt;br /&gt;
 git init&lt;br /&gt;
 ../../bin/create-gitignores.sh&lt;br /&gt;
 git add sc&lt;br /&gt;
 git commit -m &amp;quot;initial&amp;quot;&lt;br /&gt;
&lt;br /&gt;
And from now on you can locally commit to sc (git commit -a) until you are happy. &lt;br /&gt;
To generate the patch, just&lt;br /&gt;
 git diff --no-prefix&lt;br /&gt;
You can see the diff from your initial commit with this command&lt;br /&gt;
 git diff --no-prefix HEAD^&lt;br /&gt;
To remove the git tracking :&lt;br /&gt;
 rm -rf .git&lt;br /&gt;
&lt;br /&gt;
You can also think of more fancy use of git, like having a master branch for applying the patches, and other branches to track history of development you are doing, or use it to actually edit existing patches, to merge patches, etc.  In that case, it is useful to track history of the entire tree; to do that, use&lt;br /&gt;
 git add .&lt;br /&gt;
instead of the &amp;#039;git add sc&amp;#039; in the example above.&lt;br /&gt;
&lt;br /&gt;
Some people prefer stacked git (stg) over plain git when juggling with patches, after the initial &amp;quot;git init; git add .; git commit -a&amp;quot; do a &amp;quot;stg init&amp;quot; - and read the nice manual page.&lt;br /&gt;
&lt;br /&gt;
== Adding Patch ==&lt;br /&gt;
&lt;br /&gt;
One of the main ooo-build features is the ability to apply patches against the upstream sources. A patch can be added the following way:&lt;br /&gt;
&lt;br /&gt;
* propose a patch file name:&lt;br /&gt;
** the file suffix &amp;#039;&amp;#039;.diff&amp;#039;&amp;#039; is required&lt;br /&gt;
** the file name &amp;#039;&amp;#039;&amp;lt;theme&amp;gt;-short-fix-description.diff&amp;#039;&amp;#039; is suggested when there are more thematic patches, e.g. &amp;#039;&amp;#039;warnigns&amp;#039;&amp;#039;, &amp;#039;&amp;#039;unittesting&amp;#039;&amp;#039;, &amp;#039;&amp;#039;speed&amp;#039;&amp;#039; that are not put in any thematic directory&lt;br /&gt;
** the file name &amp;#039;&amp;#039;&amp;lt;module&amp;gt;-short-fix-description.diff&amp;#039;&amp;#039; is suggested when the patch modifies only one source &amp;#039;&amp;#039;module&amp;#039;&amp;#039;, e&amp;#039;g&amp;#039; &amp;#039;&amp;#039;vcl&amp;#039;&amp;#039;, &amp;#039;&amp;#039;svx&amp;#039;&amp;#039;, &amp;#039;&amp;#039;sd&amp;#039;&amp;#039;&lt;br /&gt;
** the file name cws-&amp;lt;name&amp;gt; should be used for CWS backports&lt;br /&gt;
** the file name &amp;#039;&amp;#039;short-fix-description.diff&amp;#039;&amp;#039; is enough otherwise&lt;br /&gt;
* create the patch in the format to be applied in the top source directory with &amp;#039;&amp;#039;-P0&amp;#039;&amp;#039;, see the sample content:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:--- jvmfwk/plugins/sunmajor/pluginlib/gnujre.cxx.old    2007-08-10 17:32:26.0000&lt;br /&gt;
*:+++ jvmfwk/plugins/sunmajor/pluginlib/gnujre.cxx        2007-08-16 22:40:42.0000&lt;br /&gt;
*:@@ -78,6 +78,7 @@ char const* const* GnuInfo::getJavaExePa &lt;br /&gt;
*:...&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
*put the patch below &amp;#039;&amp;#039;ooo-build/patches/&amp;lt;group&amp;gt;&amp;#039;&amp;#039;; most patches are located in the MWS specific directory. Some bigger groups of patches have their own thematic directory. For example:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:patches/src680/sc-save-split-view.diff&lt;br /&gt;
*:patches/src680/warning-return-values-filter.diff&lt;br /&gt;
*:&lt;br /&gt;
*:patches/scsolver/scsolver-source-inc-basedlg-hxx.diff&lt;br /&gt;
*:patches/scsolver/scsolver-source-inc-baselistener-hxx.diff&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
* mention the patch in the &amp;#039;&amp;#039;apply&amp;#039;&amp;#039; file:&lt;br /&gt;
**ooo-build allows to sort the patches into groups and apply them conditionaly &amp;#039;&amp;#039;&amp;#039;by distributions&amp;#039;&amp;#039;&amp;#039;. Therefore, each patch has to be mentioned in the &amp;#039;&amp;#039;&amp;#039;right section&amp;#039;&amp;#039;&amp;#039; in the &amp;#039;&amp;#039;apply&amp;#039;&amp;#039; file. This file is usually located in the MWS-specific directory, e.g. &amp;#039;&amp;#039;patches/src680/apply&amp;#039;&amp;#039;.&lt;br /&gt;
**the patch entry might look like:&lt;br /&gt;
**: &amp;lt;pre&amp;gt;&lt;br /&gt;
**: [ CalcFixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # Support Hungarian localized keywords for CELL and INFO functions.&lt;br /&gt;
**: sc-celltrans-hungarian-keywords.diff, i#80299, kohei&lt;br /&gt;
**: # Fix saving split-view information on 64-bit platforms.&lt;br /&gt;
**: sc-save-split-view.diff, n#235131, i#81936, jonp&amp;lt;/pre&amp;gt;&lt;br /&gt;
**please do not forget to mention the &amp;#039;&amp;#039;&amp;#039;issue numbers&amp;#039;&amp;#039;&amp;#039; and the responsible &amp;#039;&amp;#039;&amp;#039;developer name&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
**note that the patches are applied in the order in which they are listed in the apply file. If there are some conflicts between the patches, it might be necessary to &amp;#039;&amp;#039;&amp;#039;split a section&amp;#039;&amp;#039;&amp;#039;, for example:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**: [ Fixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # make unzip command not ask when overwriting files&lt;br /&gt;
**: unzip-command.diff, i#81087, fridrich&lt;br /&gt;
**:&lt;br /&gt;
**: [ CalcFixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: #fix import filter for userforms with calc specific data ( rowsource ) &lt;br /&gt;
**: svx-filter-userform-rowsource.diff, i#73753&lt;br /&gt;
**:&lt;br /&gt;
**:[ Fixes ]&lt;br /&gt;
**:&lt;br /&gt;
**: # edit fields text displaying&lt;br /&gt;
**: svx-sdrobjeditview-update-edit-area.diff, n#305205, rodo&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Committing a Change ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
The following process describes how to commit any change to the ooo-build:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
* do your changes&lt;br /&gt;
* create a changelog entry:&lt;br /&gt;
** list all the modified files; hint: use the command &amp;#039;&amp;#039;&amp;#039;svn stat&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
** add a good description of the changes&lt;br /&gt;
** mention the related issue or bug numbers&lt;br /&gt;
** for example, it might look like:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**:2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
**:&lt;br /&gt;
**:        * patches/src680/xmlhelp-work-with-symlinks.diff, patches/src680/apply:&lt;br /&gt;
**:          display help correctly even when the files are symlinked, i#81138&lt;br /&gt;
**:&amp;lt;/pre&amp;gt;&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - if it took some more time to finish the changes, there is a high chance that anybody else committed another change and it might be necessary to resolve conflicts&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn stat&amp;#039;&amp;#039;&amp;#039; - it is a good practice to double check that only the expected files are modified&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn diff&amp;#039;&amp;#039;&amp;#039; - it is a good practice to double check all changes, especially after resolving some conflicts&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039; - use the same text for SVN changelog that was used for the &amp;#039;&amp;#039;Changelog&amp;#039;&amp;#039; file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Releasing ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
When there&amp;#039;s a particularly good reason for a release, such as a distro needs a stable base or we want to do something potentially&lt;br /&gt;
disruptive, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
&lt;br /&gt;
* Read back through the &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039; and update the &amp;#039;&amp;#039;NEWS&amp;#039;&amp;#039; file for the release, summarizing and attributing the changes.&lt;br /&gt;
&lt;br /&gt;
* edit &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;, bump the version in the &amp;#039;&amp;#039;&amp;#039;AC_INIT&amp;#039;&amp;#039;&amp;#039; line, incrementing the minor version eg. &amp;#039;&amp;#039;&amp;#039;AC_INIT(ooo-build, X.Y.Z)&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* Add a line to any handy &amp;#039;&amp;#039;ChangeLogs&amp;#039;&amp;#039;, so we can easily see where this happened in the flow:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
            * Version X.Y.Z&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039; - so what&amp;#039;s there is what&amp;#039;s there. If there was a collision you get to loop to the first stage here, but don&amp;#039;t re-increment the number.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;svn -r &amp;lt;id&amp;gt; copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/&amp;lt;tree&amp;gt;/ svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/tags/OOO_BUILD_X_Y_Z&amp;#039;&amp;#039;&amp;#039; - this creates a copy of the current state so we can reproduce the build at any time and easily diff between releases. The &amp;#039;&amp;#039;&amp;#039;id&amp;#039;&amp;#039;&amp;#039; is the revision number printed when the &amp;#039;&amp;#039;&amp;#039;commit&amp;#039;&amp;#039;&amp;#039; command finishes, e.g. &amp;#039;&amp;#039;10364&amp;#039;&amp;#039;. The &amp;#039;&amp;#039;&amp;#039;tree&amp;#039;&amp;#039;&amp;#039; is either &amp;#039;&amp;#039;trunk&amp;#039;&amp;#039; or &amp;#039;&amp;#039;branches/ooo-build-M-N&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;./autogen.sh&amp;#039;&amp;#039;&amp;#039; - this re-builds configure with the version in place; a distro must be specified eg. &amp;#039;&amp;#039;&amp;#039;./autogen.sh --with-distro=GoOoLinux&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;make dist&amp;#039;&amp;#039;&amp;#039; - this builds the archive containing everything.&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;md5sum ooo-build-X.Y.Z.tar.gz &amp;gt; ooo-build-X.Y.Z.tar.gz.md5&amp;#039;&amp;#039;&amp;#039; - so that users can do at least the basic consistency check&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;scp ooo-build-X.Y.Z.tar.gz* ooweb@seagull.dreamhost.com:~/download.go-oo.org/&amp;lt;MWS_DIR&amp;gt;/&amp;#039;&amp;#039;&amp;#039; - uploads the tarball and the .md5 file for the right Master Work Space, eg. SRC680&lt;br /&gt;
&lt;br /&gt;
* It&amp;#039;s then customary to announce the release, see the template in &amp;#039;&amp;#039;doc/announce.txt&amp;#039;&amp;#039; - update all the ***s to the right versions, insert the contents of &amp;#039;&amp;#039;NEWS&amp;#039;&amp;#039;, fire and forget.&lt;br /&gt;
&lt;br /&gt;
== Branching ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
When there&amp;#039;s a particularly good reason for a branch, such as a MWS is moved to the maintenace mode and we want open TRUNK for further development, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* create the branch and anchor copies:&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/tags/OOO_BUILD_X_Y_Z svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/branches/ooo-build-M-N&amp;#039;&amp;#039;&amp;#039; - do the branch for OOo-M.N from a previous release of ooo-build-X.Y.Z&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn copy svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/tags/branches/ooo-build-M-N svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/tags/OOO-BUILD-M-K-ANCHOR&amp;#039;&amp;#039;&amp;#039; - this creates a copy of the current state so we can diff against it and see the branch specific changes&lt;br /&gt;
* make changes specific for the original tree (TRUNK):&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn co svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/&amp;lt;tree&amp;gt;/ ooo-build&amp;#039;&amp;#039;&amp;#039; - get sources from the original tree, either from &amp;#039;&amp;#039;trunk&amp;#039;&amp;#039; or &amp;#039;&amp;#039;branches/ooo-build-M-N&amp;#039;&amp;#039;.&lt;br /&gt;
** if it is an important branch, such as for a minor OOo version, add a line to the message printed at the end of &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;. It might be something like: &lt;br /&gt;
**:&amp;lt;tt&amp;gt;ooo-build-X-Y-Z  branch for X.Y.Z&amp;lt;/tt&amp;gt;&lt;br /&gt;
** add a line to any handy &amp;#039;&amp;#039;ChangeLogs&amp;#039;&amp;#039;, so we can easily see where this happened in the flow. Of course, if you branched an older tag, you must put the comment into the right context. See below for a sample comment.&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* make changes specific for the branch:&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn co svn+ssh://&amp;lt;user&amp;gt;@svn.gnome.org/svn/ooo-build/branches/ooo-build-M-N ooo-build-M-N&amp;#039;&amp;#039;&amp;#039; - get sources from the branch&lt;br /&gt;
** modify the message printed at the end of &amp;#039;&amp;#039;configure.in&amp;#039;&amp;#039;. It might be something like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;This is ooo-build-2-0-4 - the stable branch for the 2.0.4 release.&amp;lt;br&amp;gt;If you want to build something cool, unstable, and risky, use trunk.&amp;lt;/tt&amp;gt;&lt;br /&gt;
** add the same comment to the &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039; as in the original tree&lt;br /&gt;
** &amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* it&amp;#039;s then customary to announce the release&lt;br /&gt;
&lt;br /&gt;
Sample comment:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    * Branched for X.Y.Z:                                                   &lt;br /&gt;
          OOO-BUILD-X-Y-Z-ANCHOR - the anchor tag,                              &lt;br /&gt;
          ooo-build-2-0-4 - the branch.                                         &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Support for new MWS ==&lt;br /&gt;
&lt;br /&gt;
Note: this section is obsolete because of the recent move to git, see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt#head-a1c714c3a215422d08997d59051b21f32dd28152 fd.o wiki] for more info.&lt;br /&gt;
&lt;br /&gt;
When the upstream branches new MWS and we want to support it in ooo-build, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* first, it is better to clean ooo-build and remove support for all old and obsolete milestones; FIXME: it will be described somewhere else&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;svn up&amp;#039;&amp;#039;&amp;#039; - get the latest everything&lt;br /&gt;
*edit &amp;#039;&amp;#039;download.in&amp;#039;&amp;#039;, mention the new tarball file name and URL in the array &amp;#039;&amp;#039;%SRC_URLS&amp;#039;&amp;#039;, something like:&lt;br /&gt;
*:&amp;lt;tt&amp;gt;               &amp;#039;oox680-m.*&amp;#039;                         =&amp;gt; &amp;#039;@MIRROR@/OOX680&amp;#039;,&amp;lt;/tt&amp;gt;&lt;br /&gt;
*edit &amp;#039;&amp;#039;patches/src680/apply&amp;#039;&amp;#039;&lt;br /&gt;
**fix the &amp;#039;&amp;#039;OLDEST_SUPPORTED&amp;#039;&amp;#039; option; note that more MWSs can be supported, it might be something like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;OLDEST_SUPPORTED=src680-m181,ooe680-m1&amp;lt;/tt&amp;gt;&lt;br /&gt;
**fix the conditions for the various sections; note that you must add condition for the new MWS everywhere where a condition for another MWS already exists; it might look like:&lt;br /&gt;
**:&amp;lt;tt&amp;gt;[ Fixes &amp;gt;= src680-m182 &amp;gt;= ooe680-m2 ]&amp;lt;/tt&amp;gt;&lt;br /&gt;
*might want to use the new milestone by default, then update &amp;#039;&amp;#039;DEFAULT_TAG&amp;#039;&amp;#039; in &amp;#039;&amp;#039;configure&amp;#039;&amp;#039; in, it looks like:&lt;br /&gt;
*:&amp;lt;tt&amp;gt;DEFAULT_TAG=oox680-mY&amp;lt;/tt&amp;gt;&lt;br /&gt;
*describe all changes in &amp;#039;&amp;#039;ChangeLog&amp;#039;&amp;#039;; it is usually enough to mention something like:&lt;br /&gt;
*:&amp;lt;pre&amp;gt;&lt;br /&gt;
*:2019-13-33  Ned Squeers  &amp;lt;ned@sqeers.com&amp;gt;&lt;br /&gt;
*:  &lt;br /&gt;
*:        * configure.in, download.in, patches/src680/apply: support for oox680&lt;br /&gt;
*:        * configure.in: Default to oox680-mY&lt;br /&gt;
*:&amp;lt;/pre&amp;gt;&lt;br /&gt;
*&amp;#039;&amp;#039;&amp;#039;svn commit&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
*it&amp;#039;s then customary to announce this kind of change&lt;br /&gt;
&lt;br /&gt;
== Support for final OOo version ==&lt;br /&gt;
&lt;br /&gt;
When the upstream releases final version of a MWS, one of the core ooo-build hackers will follow something like this process:&lt;br /&gt;
&lt;br /&gt;
* must check whether the final sources differ from the latest milestone; if the sources are the same, only symlink is made at go-oo.org/packages; new sources are created otherwise; the new tarball name is something like &amp;#039;&amp;#039;OOO_X_Y_Z&amp;#039;&amp;#039;&lt;br /&gt;
* do all the steps as in case of [[ooo-build#Support for new MWS|support for new MWS]] with the following modifications:&lt;br /&gt;
** use the tarball name &amp;#039;&amp;#039;OOO_X_Y_Z&amp;#039;&amp;#039; instead of the MWS- and milestone-based name &amp;#039;&amp;#039;oox680-mY&amp;#039;&amp;#039;&lt;br /&gt;
** if the sources are only symlinks to the lates milestone, hack &amp;#039;&amp;#039;bin/unpack&amp;#039;&amp;#039;, so it creates the symlink to the unpacked sources; it might look like:&lt;br /&gt;
**:&amp;lt;pre&amp;gt;&lt;br /&gt;
**:if test -d oox680-mY -a ! -d OOO_X_Y_Z ; then&lt;br /&gt;
**:    echo &amp;quot;Linking rcZ to X.Y.Z&amp;quot;&lt;br /&gt;
**:    ln -sf oox680-mY OOO_X_Y_Z&lt;br /&gt;
**:fi&lt;br /&gt;
**:&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Remaining unsolved issue summary ==&lt;br /&gt;
&lt;br /&gt;
A helpful summary of these is provided here in no particular order along with suggestions for improvement.&lt;br /&gt;
Many of these are mercifully easy to fix, and should be fixed soon.&lt;br /&gt;
&lt;br /&gt;
=== source handling ===&lt;br /&gt;
&lt;br /&gt;
ooo-build has a post-configure &amp;#039;download&amp;#039; mechanism, whereby the relevant source archives will be automatically downloaded to your system having configured it, in response to your various options.&lt;br /&gt;
&lt;br /&gt;
=== non-responsiveness / lack of leadership ===&lt;br /&gt;
&lt;br /&gt;
Many ooo-build patches are ready for up-streaming but there is no / little response from up-stream. Worse there is the perception that taking leadership and actually doing something about merging fixes would be firmly opposed. Finally - even when maintainers are active, responsive &amp;amp; friendly - there is no agreed mechanism for blanket&lt;br /&gt;
approving fixes - or sub-types of trivial fixes, which thus tend to fester in IssueZilla.&lt;br /&gt;
&lt;br /&gt;
At the time of writing ooo-build&amp;#039;s patches are available here: http://go-oo.org/ooo-build/patches/src680/apply.&lt;br /&gt;
&lt;br /&gt;
=== font substitution ===&lt;br /&gt;
&lt;br /&gt;
Many vendors ship AGFA&amp;#039;s propriatory metric-compatible fonts with OO.o - it is thus necessary to run several seds on the VCL.xcu [ further bloating this already gigantic messy beast ]. We also remove some of the more foolish &amp;amp;amp; enthusiastic font-usage of eg. the metrically-extremely-strange bitstream font eg. &amp;lt;code&amp;gt;bin/font-munge.pl&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    s/(Bitstream Vera Sans;.*)Albany;/Albany;$1/;&lt;br /&gt;
    # add AMT fonts&lt;br /&gt;
    s/Albany;/Albany AMT;Albany;/g;&lt;br /&gt;
    s/albany;/albanyamt;albany;/g;&lt;br /&gt;
&lt;br /&gt;
=== no &amp;#039;UI&amp;#039; team ===&lt;br /&gt;
&lt;br /&gt;
The up-stream UI team have come up with master-pieces of UI design such as the Yes/No dialog on&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Would you like to not continue saving in the original OpenOffice.org 2.0 format or perhaps switch to another format&amp;quot;&lt;br /&gt;
&lt;br /&gt;
that takes 10 seconds to parse each time ( presumably since it&amp;#039;s a recent feature - with a specification too ).&lt;br /&gt;
&lt;br /&gt;
The rest of us mere-mortals know that the UI in OO.o is &amp;lt;b&amp;gt;shockingly&amp;lt;/b&amp;gt; broken - and hence are eager to fix it&lt;br /&gt;
without being blocked &amp;amp; frustrated for weeks by those responsible for the current mess.&lt;br /&gt;
&lt;br /&gt;
A number of the changes / patches in apply/ are blocked on &amp;#039;user experience&amp;#039; feedback.&lt;br /&gt;
&lt;br /&gt;
=== different defaults ===&lt;br /&gt;
&lt;br /&gt;
It is self evident to ooo-build users that a slew of dialogs on 1st run is a painful mess; eg. if there are settings to migrate, don&amp;#039;t shout about it - do it silently. Furthermore - the registration dialog looks tacky,&lt;br /&gt;
we disable both. We also alter a number of other defaults. cf. the last point - I&amp;#039;m optimistic that these will&lt;br /&gt;
~never get up-stream agreement.&lt;br /&gt;
&lt;br /&gt;
=== bleeding-edgeness ===&lt;br /&gt;
&lt;br /&gt;
There is a &amp;#039;cool factor&amp;#039; to building the very latest things yourself; and helping solve problems with them.&lt;br /&gt;
It&amp;#039;s nice to be able to see your changes have an effect &amp;amp;amp; help others rapidly, eg. a fix being immediately&lt;br /&gt;
useful to other people. Of course - you can have too much of a good thing here but ...&lt;br /&gt;
&lt;br /&gt;
=== Philosophical differences ===&lt;br /&gt;
&lt;br /&gt;
==== compatibility ====&lt;br /&gt;
&lt;br /&gt;
Up-stream believe that the most important data set to be compatible with is existing [[StarOffice]] / OO.o users.&lt;br /&gt;
ooo-build users believe that nearly all the world&amp;#039;s data is stored in Microsoft Office format - hence we&lt;br /&gt;
sacrifice legacy support for better interop.&lt;br /&gt;
This is of course a continuum, up-stream are at the luny extreme of pushing back-compatibility regardless&lt;br /&gt;
of it&amp;#039;s impact on interoperability, even in cases deliberately excluding useful interoperability improvements&lt;br /&gt;
on that basis. ooo-build appreciates backwards comaptibility, but is in favour of viewing core differences&lt;br /&gt;
that are non-interoperable as bugs not features.&lt;br /&gt;
&lt;br /&gt;
==== process complexity ====&lt;br /&gt;
&lt;br /&gt;
ooo-build users believe in programmer lead development, with strong peer review and user QA.&lt;br /&gt;
up-stream believe in process based development, with teams, consensus building, specification writing, test-instead-of-detailed-code-review-or-unit-testing, and all these &amp;#039;Professional&amp;#039; pasttimes.&lt;br /&gt;
ooo-build users believe the OO.o we have today is broadly a product of these processes. Up-stream users&lt;br /&gt;
believe the previous sentence is a compliment.&lt;br /&gt;
&lt;br /&gt;
==== cross-platform ====&lt;br /&gt;
&lt;br /&gt;
ooo-build enables patch sub-setting, thus we include patches for features (eg. Mono integration) that are&lt;br /&gt;
most likely not well separated, and will break the Win32 build. Of course, for ooo-build these are not&lt;br /&gt;
enabled on Win32 thus causing no problem. This is an impediment to getting work up-stream. Hopefully&lt;br /&gt;
the &amp;#039;experimental&amp;#039; process may help encourage good behavior here.&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
&lt;br /&gt;
If you read all that don&amp;#039;t get depressed - these issues can all be fixed - many of them almost painlessly. We hope to shrink this page quickly.&lt;br /&gt;
&lt;br /&gt;
[[Category: Development]]&lt;br /&gt;
[[Category:Build_System]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&amp;diff=117796</id>
		<title>Building with ooobuild</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&amp;diff=117796"/>
		<updated>2009-03-31T08:26:54Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Vanilla Up-stream builds ==&lt;br /&gt;
&lt;br /&gt;
See the [http://tools.openoffice.org#Build tools] project for build guides for various platforms.&lt;br /&gt;
&lt;br /&gt;
Also for OS/X see [[MacOSXBuildInstructions]]&lt;br /&gt;
&lt;br /&gt;
For GNU/Linux Sparc, with gcc4.1 &amp;amp; gcj, see [[GNULinuxSparcPorting]]&lt;br /&gt;
&lt;br /&gt;
== ooo-build builds ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;If you are looking for additional building tips for Windows check [[Windows |this]] page first.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== get the source ===&lt;br /&gt;
&lt;br /&gt;
You need to checkout the source code using git:&lt;br /&gt;
&lt;br /&gt;
 git clone git://anongit.freedesktop.org/git/ooo-build/ooo-build&lt;br /&gt;
&lt;br /&gt;
(see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt fd.o wiki] for authoritative info)&lt;br /&gt;
&lt;br /&gt;
=== configure ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      The build process is pretty complicated; you have a choice&lt;br /&gt;
      of commands now; although running both won&amp;#039;t actually hurt:&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
      ./autogen.sh --with-distro=&amp;lt;b&amp;gt;HelloMum&amp;lt;/b&amp;gt;  # only for the git version&lt;br /&gt;
      ./configure  --with-distro=&amp;lt;b&amp;gt;HelloMum&amp;lt;/b&amp;gt; # the packaged version&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      This will guess which branch snapshot you want to build; if&lt;br /&gt;
      you have other ideas use the --with-tag option; eg.&lt;br /&gt;
      &amp;lt;code&amp;gt;--with-tag=src680-m65&amp;lt;/code&amp;gt; for a legacy branch.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      NB. getting your distro right is quite important; values like&lt;br /&gt;
      SUSE-10.1 (also SLED10), UbuntuDapper, DebianEtch64 may float&lt;br /&gt;
      your boat. Checkout &amp;lt;code&amp;gt;ls distro-configs&amp;lt;/code&amp;gt; to see more.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      If for some reason you have a 31337 multi-threaded computer,&lt;br /&gt;
      with great slabs of RAM; you&amp;#039;ll want to use --with-num-cpus=8&lt;br /&gt;
      etc. NB. it&amp;#039;s not clever to force the build to swap like a&lt;br /&gt;
      demented pawnbroker by using an artificially high number; C++&lt;br /&gt;
      compilation is seriously memory hungry.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      In particular, building DEV300 requires a recent jdk &amp;amp;amp; a&lt;br /&gt;
      version of apache-ant. If you use a Novell system, just do:&lt;br /&gt;
      &amp;lt;code&amp;gt;sudo rug in apache-ant&amp;lt;/code&amp;gt;, alternatively download&lt;br /&gt;
      a package from [http://www.rpmfind.net/linux/rpm2html/search.php?query=apache-ant&amp;amp;submit=Search+...&amp;quot; rpmfind.net] or failing that see [http://ant.apache.org/bindownload.cgi Ant download]&lt;br /&gt;
&amp;amp;amp; set the ANT environment variable&lt;br /&gt;
      appropriately before configuring.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;h4&amp;gt;Known ./configure parameters&amp;lt;/h4&amp;gt;&lt;br /&gt;
    &amp;lt;ul&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;up-stream options&amp;lt;/h5&amp;gt;&amp;lt;p&amp;gt; - all options are passed through directly&lt;br /&gt;
    to the internal configure, so they should work nicely here too.&amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--with-system-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt;where &amp;amp;lt;package name&amp;gt; is replaced by the package to use. I don&amp;#039;t&lt;br /&gt;
        have a particularly good understanding of its full effects beyond&lt;br /&gt;
        the fact that it (probably) doesn&amp;#039;t then build its own copy of the&lt;br /&gt;
        package.&amp;lt;/p&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-python&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-mozilla&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-gcc&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-neon&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-curl&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--without-system-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-system-mozilla&amp;lt;/code&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--with-&amp;lt;package or tag&amp;gt;[=value]&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-lang=en-US&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-build-version=&amp;quot;Build 2.0.1.3&amp;quot;&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-distro=Gentoo&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--without-&amp;lt;package or tag&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-myspell-dicts&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-java&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-nas&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--enable-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--enable-openldap&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--disable-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-openldap&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-qadevoo&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-mozilla&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-access&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-evolution2&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--mandir=&amp;lt;dir&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
On opensuse 11.1, this line should get you all prerequisites:&lt;br /&gt;
 zypper si -d OpenOffice_org-bootstrap&lt;br /&gt;
&lt;br /&gt;
Also see the distro-specific setup in the link section at the bottom, otherwise here&amp;#039;s the detailed list:&lt;br /&gt;
*A recent version of automake, such as the 1.9 series.&lt;br /&gt;
*If you don&amp;#039;t have a working Java VM (i.e. any runtime), you should pass &amp;lt;code&amp;gt;--with-java=no&amp;lt;/code&amp;gt; to either &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need the Archive/Zip module for Perl (perl-Archive-Zip on RPM-based distributions, libarchive-zip-perl on dpkg-based distributions). Alternatively, see instructions[http://ooo.ximian.com/cpan.html] for obtaining Perl modules through CPAN.&lt;br /&gt;
*You need the development package for Python (this would be python-devel on RPM-based distributions).&lt;br /&gt;
*You need curl and curl-devel.&lt;br /&gt;
*You need odbc_config to be present.  On SUSE systems, this is in the unixODBC-devel package.&lt;br /&gt;
*You need libsndfile and libsndfile-devel.&lt;br /&gt;
*If you don&amp;#039;t have a recent enough openldap, pass &amp;lt;code&amp;gt;--disable-openldap&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need neon and neon-devel.&lt;br /&gt;
*You need qt3 and qt3-devel, or if you don&amp;#039;t have the KDE development packages, pass &amp;lt;code&amp;gt;--disable-kde&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need mozilla-nss-devel.&lt;br /&gt;
*In SuSE, you need gecko-sdk, mono-devel and cups-devel&lt;br /&gt;
&lt;br /&gt;
=== download ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      By the time you&amp;#039;ve upgraded your system to the point that it&lt;br /&gt;
      has all the packages you need to start building OO.o (mozilla etc. etc.) you&amp;#039;re almost at the point that you&lt;br /&gt;
      can download the bulk of the source. To do this, after a&lt;br /&gt;
      successful configure simply type: &amp;lt;code&amp;gt;./download&amp;lt;/code&amp;gt; and wait.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      If for whatever reason this fails, you can verify your download&lt;br /&gt;
      by fetching the equivalent .md5 file &amp;amp;amp; comparing it to&lt;br /&gt;
      the result of &amp;lt;code&amp;gt;md5sum &amp;lt;archive&amp;gt;&amp;lt;/code&amp;gt;. The source&lt;br /&gt;
      archives are http://download.go-oo.org/SRC680&lt;br /&gt;
       - put the source in ooo-build/src.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== make ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      This is the taxing bit - type &amp;lt;code&amp;gt;make&amp;lt;/code&amp;gt; and don&amp;#039;t forget&lt;br /&gt;
      to press enter. Quite possibly you want to log the output, so&lt;br /&gt;
      why not &amp;lt;code&amp;gt;make 2&amp;gt;&amp;amp;1 | tee /tmp/log&amp;lt;/code&amp;gt;.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      Since ooo-build wraps the actual OO.o configuration &amp;amp;amp;&lt;br /&gt;
      build process, there are a number of internal config checks that&lt;br /&gt;
      also need to pass. For a first time build it&amp;#039;s well worth staying&lt;br /&gt;
      near the console while everything unpacks, and the internal&lt;br /&gt;
      configure runs; if that completes without incident - you&amp;#039;re&lt;br /&gt;
      usually into the heavy-duty thumb twiddling.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
*[[Installing]]&lt;br /&gt;
*[[Tinderbox Setup]]&lt;br /&gt;
*[[BuildSpeedup]]&lt;br /&gt;
*[[OpenSUSE Build Instructions]]&lt;br /&gt;
*[[SUSE9.3 Build Instructions]]&lt;br /&gt;
*[[Building ooo-build on Mac OS X]]&lt;br /&gt;
*[[Ubuntu Build Instructions]]&lt;br /&gt;
*OpenOffice.org &amp;quot;Tools&amp;quot; page [http://tools.openoffice.org/dev_docs/build_linux.html]&lt;br /&gt;
*[[Build Tool Requirements]]&lt;br /&gt;
*[[O3-build|O3 Build]], an ISO image containing all the required software to build OOo on Linux.&lt;br /&gt;
&lt;br /&gt;
[[Category: Development]]&lt;br /&gt;
[[Category:Build_System]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&amp;diff=117795</id>
		<title>Building with ooobuild</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&amp;diff=117795"/>
		<updated>2009-03-31T08:25:48Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Vanilla Up-stream builds ==&lt;br /&gt;
&lt;br /&gt;
See the [http://tools.openoffice.org#Build tools] project for build guides for various platforms.&lt;br /&gt;
&lt;br /&gt;
Also for OS/X see [[MacOSXBuildInstructions]]&lt;br /&gt;
&lt;br /&gt;
For GNU/Linux Sparc, with gcc4.1 &amp;amp; gcj, see [[GNULinuxSparcPorting]]&lt;br /&gt;
&lt;br /&gt;
== ooo-build builds ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;If you are looking for additional building tips for Windows check [[Windows |this]] page first.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== get the source ===&lt;br /&gt;
&lt;br /&gt;
You need to checkout the source code using git:&lt;br /&gt;
&lt;br /&gt;
 git clone git://anongit.freedesktop.org/git/ooo-build/ooo-build&lt;br /&gt;
&lt;br /&gt;
(see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt fd.o wiki] for authoritative info)&lt;br /&gt;
&lt;br /&gt;
=== configure ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      The build process is pretty complicated; you have a choice&lt;br /&gt;
      of commands now; although running both won&amp;#039;t actually hurt:&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
      ./autogen.sh --with-distro=&amp;lt;b&amp;gt;HelloMum&amp;lt;/b&amp;gt;  # only for the git version&lt;br /&gt;
      ./configure  --with-distro=&amp;lt;b&amp;gt;HelloMum&amp;lt;/b&amp;gt; # the packaged version&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      This will guess which branch snapshot you want to build; if&lt;br /&gt;
      you have other ideas use the --with-tag option; eg.&lt;br /&gt;
      &amp;lt;code&amp;gt;--with-tag=src680-m65&amp;lt;/code&amp;gt; for a legacy branch.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      NB. getting your distro right is quite important; values like&lt;br /&gt;
      SUSE-10.1 (also SLED10), UbuntuDapper, DebianEtch64 may float&lt;br /&gt;
      your boat. Checkout &amp;lt;code&amp;gt;ls distro-configs&amp;lt;/code&amp;gt; to see more.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      If for some reason you have a 31337 multi-threaded computer,&lt;br /&gt;
      with great slabs of RAM; you&amp;#039;ll want to use --with-num-cpus=8&lt;br /&gt;
      etc. NB. it&amp;#039;s not clever to force the build to swap like a&lt;br /&gt;
      demented pawnbroker by using an artificially high number; C++&lt;br /&gt;
      compilation is seriously memory hungry.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      In particular, building DEV300 requires a recent jdk &amp;amp;amp; a&lt;br /&gt;
      version of apache-ant. If you use a Novell system, just do:&lt;br /&gt;
      &amp;lt;code&amp;gt;sudo rug in apache-ant&amp;lt;/code&amp;gt;, alternatively download&lt;br /&gt;
      a package from [http://www.rpmfind.net/linux/rpm2html/search.php?query=apache-ant&amp;amp;submit=Search+...&amp;quot; rpmfind.net] or failing that see [http://ant.apache.org/bindownload.cgi Ant download]&lt;br /&gt;
&amp;amp;amp; set the ANT environment variable&lt;br /&gt;
      appropriately before configuring.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;h4&amp;gt;Known ./configure parameters&amp;lt;/h4&amp;gt;&lt;br /&gt;
    &amp;lt;ul&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;up-stream options&amp;lt;/h5&amp;gt;&amp;lt;p&amp;gt; - all options are passed through directly&lt;br /&gt;
    to the internal configure, so they should work nicely here too.&amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--with-system-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt;where &amp;amp;lt;package name&amp;gt; is replaced by the package to use. I don&amp;#039;t&lt;br /&gt;
        have a particularly good understanding of its full effects beyond&lt;br /&gt;
        the fact that it (probably) doesn&amp;#039;t then build its own copy of the&lt;br /&gt;
        package.&amp;lt;/p&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-python&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-mozilla&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-gcc&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-neon&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-curl&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--without-system-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-system-mozilla&amp;lt;/code&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--with-&amp;lt;package or tag&amp;gt;[=value]&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-lang=en-US&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-build-version=&amp;quot;Build 2.0.1.3&amp;quot;&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-distro=Gentoo&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--without-&amp;lt;package or tag&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-myspell-dicts&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-java&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-nas&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--enable-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--enable-openldap&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--disable-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-openldap&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-qadevoo&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-mozilla&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-access&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-evolution2&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--mandir=&amp;lt;dir&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
On opensuse 11.1, this should get you settled:&lt;br /&gt;
 zypper si -d OpenOffice_org-bootstrap&lt;br /&gt;
&lt;br /&gt;
See the distro-specific setup in the link section at the bottom, otherwise here&amp;#039;s the detailed list:&lt;br /&gt;
*A recent version of automake, such as the 1.9 series.&lt;br /&gt;
*If you don&amp;#039;t have a working Java VM (i.e. any runtime), you should pass &amp;lt;code&amp;gt;--with-java=no&amp;lt;/code&amp;gt; to either &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need the Archive/Zip module for Perl (perl-Archive-Zip on RPM-based distributions, libarchive-zip-perl on dpkg-based distributions). Alternatively, see instructions[http://ooo.ximian.com/cpan.html] for obtaining Perl modules through CPAN.&lt;br /&gt;
*You need the development package for Python (this would be python-devel on RPM-based distributions).&lt;br /&gt;
*You need curl and curl-devel.&lt;br /&gt;
*You need odbc_config to be present.  On SUSE systems, this is in the unixODBC-devel package.&lt;br /&gt;
*You need libsndfile and libsndfile-devel.&lt;br /&gt;
*If you don&amp;#039;t have a recent enough openldap, pass &amp;lt;code&amp;gt;--disable-openldap&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need neon and neon-devel.&lt;br /&gt;
*You need qt3 and qt3-devel, or if you don&amp;#039;t have the KDE development packages, pass &amp;lt;code&amp;gt;--disable-kde&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need mozilla-nss-devel.&lt;br /&gt;
*In SuSE, you need gecko-sdk, mono-devel and cups-devel&lt;br /&gt;
&lt;br /&gt;
=== download ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      By the time you&amp;#039;ve upgraded your system to the point that it&lt;br /&gt;
      has all the packages you need to start building OO.o (mozilla etc. etc.) you&amp;#039;re almost at the point that you&lt;br /&gt;
      can download the bulk of the source. To do this, after a&lt;br /&gt;
      successful configure simply type: &amp;lt;code&amp;gt;./download&amp;lt;/code&amp;gt; and wait.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      If for whatever reason this fails, you can verify your download&lt;br /&gt;
      by fetching the equivalent .md5 file &amp;amp;amp; comparing it to&lt;br /&gt;
      the result of &amp;lt;code&amp;gt;md5sum &amp;lt;archive&amp;gt;&amp;lt;/code&amp;gt;. The source&lt;br /&gt;
      archives are http://download.go-oo.org/SRC680&lt;br /&gt;
       - put the source in ooo-build/src.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== make ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      This is the taxing bit - type &amp;lt;code&amp;gt;make&amp;lt;/code&amp;gt; and don&amp;#039;t forget&lt;br /&gt;
      to press enter. Quite possibly you want to log the output, so&lt;br /&gt;
      why not &amp;lt;code&amp;gt;make 2&amp;gt;&amp;amp;1 | tee /tmp/log&amp;lt;/code&amp;gt;.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      Since ooo-build wraps the actual OO.o configuration &amp;amp;amp;&lt;br /&gt;
      build process, there are a number of internal config checks that&lt;br /&gt;
      also need to pass. For a first time build it&amp;#039;s well worth staying&lt;br /&gt;
      near the console while everything unpacks, and the internal&lt;br /&gt;
      configure runs; if that completes without incident - you&amp;#039;re&lt;br /&gt;
      usually into the heavy-duty thumb twiddling.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
*[[Installing]]&lt;br /&gt;
*[[Tinderbox Setup]]&lt;br /&gt;
*[[BuildSpeedup]]&lt;br /&gt;
*[[OpenSUSE Build Instructions]]&lt;br /&gt;
*[[SUSE9.3 Build Instructions]]&lt;br /&gt;
*[[Building ooo-build on Mac OS X]]&lt;br /&gt;
*[[Ubuntu Build Instructions]]&lt;br /&gt;
*OpenOffice.org &amp;quot;Tools&amp;quot; page [http://tools.openoffice.org/dev_docs/build_linux.html]&lt;br /&gt;
*[[Build Tool Requirements]]&lt;br /&gt;
*[[O3-build|O3 Build]], an ISO image containing all the required software to build OOo on Linux.&lt;br /&gt;
&lt;br /&gt;
[[Category: Development]]&lt;br /&gt;
[[Category:Build_System]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&amp;diff=117794</id>
		<title>Building with ooobuild</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Building_with_ooobuild&amp;diff=117794"/>
		<updated>2009-03-31T08:22:45Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: changed cvs/svn to git&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Vanilla Up-stream builds ==&lt;br /&gt;
&lt;br /&gt;
See the [http://tools.openoffice.org#Build tools] project for build guides for various platforms.&lt;br /&gt;
&lt;br /&gt;
Also for OS/X see [[MacOSXBuildInstructions]]&lt;br /&gt;
&lt;br /&gt;
For GNU/Linux Sparc, with gcc4.1 &amp;amp; gcj, see [[GNULinuxSparcPorting]]&lt;br /&gt;
&lt;br /&gt;
== ooo-build builds ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;If you are looking for additional building tips for Windows check [[Windows |this]] page first.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== get the source ===&lt;br /&gt;
&lt;br /&gt;
You need to checkout the source code using git:&lt;br /&gt;
&lt;br /&gt;
 git clone git://anongit.freedesktop.org/git/ooo-build/ooo-build&lt;br /&gt;
&lt;br /&gt;
(see [http://freedesktop.org/wiki/Software/ooo-build/GettingIt fd.o wiki] for authoritative info)&lt;br /&gt;
&lt;br /&gt;
=== configure ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      The build process is pretty complicated; you have a choice&lt;br /&gt;
      of commands now; although running both won&amp;#039;t actually hurt:&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
      ./autogen.sh --with-distro=&amp;lt;b&amp;gt;HelloMum&amp;lt;/b&amp;gt;  # only for the git version&lt;br /&gt;
      ./configure  --with-distro=&amp;lt;b&amp;gt;HelloMum&amp;lt;/b&amp;gt; # the packaged version&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      This will guess which branch snapshot you want to build; if&lt;br /&gt;
      you have other ideas use the --with-tag option; eg.&lt;br /&gt;
      &amp;lt;code&amp;gt;--with-tag=src680-m65&amp;lt;/code&amp;gt; for a legacy branch.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      NB. getting your distro right is quite important; values like&lt;br /&gt;
      SUSE-10.1 (also SLED10), UbuntuDapper, DebianEtch64 may float&lt;br /&gt;
      your boat. Checkout &amp;lt;code&amp;gt;ls distro-configs&amp;lt;/code&amp;gt; to see more.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      If for some reason you have a 31337 multi-threaded computer,&lt;br /&gt;
      with great slabs of RAM; you&amp;#039;ll want to use --with-num-cpus=8&lt;br /&gt;
      etc. NB. it&amp;#039;s not clever to force the build to swap like a&lt;br /&gt;
      demented pawnbroker by using an artificially high number; C++&lt;br /&gt;
      compilation is seriously memory hungry.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      In particular, building DEV300 requires a recent jdk &amp;amp;amp; a&lt;br /&gt;
      version of apache-ant. If you use a Novell system, just do:&lt;br /&gt;
      &amp;lt;code&amp;gt;sudo rug in apache-ant&amp;lt;/code&amp;gt;, alternatively download&lt;br /&gt;
      a package from [http://www.rpmfind.net/linux/rpm2html/search.php?query=apache-ant&amp;amp;submit=Search+...&amp;quot; rpmfind.net] or failing that see [http://ant.apache.org/bindownload.cgi Ant download]&lt;br /&gt;
&amp;amp;amp; set the ANT environment variable&lt;br /&gt;
      appropriately before configuring.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;h4&amp;gt;Known ./configure parameters&amp;lt;/h4&amp;gt;&lt;br /&gt;
    &amp;lt;ul&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;up-stream options&amp;lt;/h5&amp;gt;&amp;lt;p&amp;gt; - all options are passed through directly&lt;br /&gt;
    to the internal configure, so they should work nicely here too.&amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;/li&amp;gt;&lt;br /&gt;
    &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--with-system-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt;where &amp;amp;lt;package name&amp;gt; is replaced by the package to use. I don&amp;#039;t&lt;br /&gt;
        have a particularly good understanding of its full effects beyond&lt;br /&gt;
        the fact that it (probably) doesn&amp;#039;t then build its own copy of the&lt;br /&gt;
        package.&amp;lt;/p&amp;gt;&lt;br /&gt;
        &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-python&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-mozilla&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-gcc&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-neon&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
           &amp;lt;code&amp;gt;--with-system-curl&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
        &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--without-system-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-system-mozilla&amp;lt;/code&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--with-&amp;lt;package or tag&amp;gt;[=value]&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-lang=en-US&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-build-version=&amp;quot;Build 2.0.1.3&amp;quot;&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--with-distro=Gentoo&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--without-&amp;lt;package or tag&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-myspell-dicts&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-java&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--without-nas&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--enable-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--enable-openldap&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--disable-&amp;lt;package name&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&lt;br /&gt;
         &amp;lt;p&amp;gt;&amp;lt;b&amp;gt;Examples:&amp;lt;/b&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-openldap&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-qadevoo&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-mozilla&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-access&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
            &amp;lt;code&amp;gt;--disable-evolution2&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
         &amp;lt;/p&amp;gt;&lt;br /&gt;
     &amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;li&amp;gt;&amp;lt;h5&amp;gt;&amp;lt;code&amp;gt;--mandir=&amp;lt;dir&amp;gt;&amp;lt;/code&amp;gt;&amp;lt;/h5&amp;gt;&amp;lt;/li&amp;gt;&lt;br /&gt;
     &amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
&lt;br /&gt;
*A recent version of automake, such as the 1.9 series.&lt;br /&gt;
*If you don&amp;#039;t have a working Java VM (i.e. any runtime), you should pass &amp;lt;code&amp;gt;--with-java=no&amp;lt;/code&amp;gt; to either &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need the Archive/Zip module for Perl (perl-Archive-Zip on RPM-based distributions, libarchive-zip-perl on dpkg-based distributions). Alternatively, see instructions[http://ooo.ximian.com/cpan.html] for obtaining Perl modules through CPAN.&lt;br /&gt;
*You need the development package for Python (this would be python-devel on RPM-based distributions).&lt;br /&gt;
*You need curl and curl-devel.&lt;br /&gt;
*You need odbc_config to be present.  On SUSE systems, this is in the unixODBC-devel package.&lt;br /&gt;
*You need libsndfile and libsndfile-devel.&lt;br /&gt;
*If you don&amp;#039;t have a recent enough openldap, pass &amp;lt;code&amp;gt;--disable-openldap&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need neon and neon-devel.&lt;br /&gt;
*You need qt3 and qt3-devel, or if you don&amp;#039;t have the KDE development packages, pass &amp;lt;code&amp;gt;--disable-kde&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;autogen.sh&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;configure&amp;lt;/code&amp;gt;.&lt;br /&gt;
*You need mozilla-nss-devel.&lt;br /&gt;
*In SuSE, you need gecko-sdk, mono-devel and cups-devel&lt;br /&gt;
&lt;br /&gt;
=== download ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      By the time you&amp;#039;ve upgraded your system to the point that it&lt;br /&gt;
      has all the packages you need to start building OO.o (mozilla etc. etc.) you&amp;#039;re almost at the point that you&lt;br /&gt;
      can download the bulk of the source. To do this, after a&lt;br /&gt;
      successful configure simply type: &amp;lt;code&amp;gt;./download&amp;lt;/code&amp;gt; and wait.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      If for whatever reason this fails, you can verify your download&lt;br /&gt;
      by fetching the equivalent .md5 file &amp;amp;amp; comparing it to&lt;br /&gt;
      the result of &amp;lt;code&amp;gt;md5sum &amp;lt;archive&amp;gt;&amp;lt;/code&amp;gt;. The source&lt;br /&gt;
      archives are http://download.go-oo.org/SRC680&lt;br /&gt;
       - put the source in ooo-build/src.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== make ===&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      This is the taxing bit - type &amp;lt;code&amp;gt;make&amp;lt;/code&amp;gt; and don&amp;#039;t forget&lt;br /&gt;
      to press enter. Quite possibly you want to log the output, so&lt;br /&gt;
      why not &amp;lt;code&amp;gt;make 2&amp;gt;&amp;amp;1 | tee /tmp/log&amp;lt;/code&amp;gt;.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
    &amp;lt;p&amp;gt;&lt;br /&gt;
      Since ooo-build wraps the actual OO.o configuration &amp;amp;amp;&lt;br /&gt;
      build process, there are a number of internal config checks that&lt;br /&gt;
      also need to pass. For a first time build it&amp;#039;s well worth staying&lt;br /&gt;
      near the console while everything unpacks, and the internal&lt;br /&gt;
      configure runs; if that completes without incident - you&amp;#039;re&lt;br /&gt;
      usually into the heavy-duty thumb twiddling.&lt;br /&gt;
    &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
*[[Installing]]&lt;br /&gt;
*[[Tinderbox Setup]]&lt;br /&gt;
*[[BuildSpeedup]]&lt;br /&gt;
*[[OpenSUSE Build Instructions]]&lt;br /&gt;
*[[SUSE9.3 Build Instructions]]&lt;br /&gt;
*[[Building ooo-build on Mac OS X]]&lt;br /&gt;
*[[Ubuntu Build Instructions]]&lt;br /&gt;
*OpenOffice.org &amp;quot;Tools&amp;quot; page [http://tools.openoffice.org/dev_docs/build_linux.html]&lt;br /&gt;
*[[Build Tool Requirements]]&lt;br /&gt;
*[[O3-build|O3 Build]], an ISO image containing all the required software to build OOo on Linux.&lt;br /&gt;
&lt;br /&gt;
[[Category: Development]]&lt;br /&gt;
[[Category:Build_System]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=ESC_meeting_minutes_20090309&amp;diff=115457</id>
		<title>ESC meeting minutes 20090309</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=ESC_meeting_minutes_20090309&amp;diff=115457"/>
		<updated>2009-03-10T21:21:01Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Action Items */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;ESC meeting minutes March 9/10&amp;lt;sup&amp;gt;th&amp;lt;/sup&amp;gt; – Hamburg&lt;br /&gt;
&lt;br /&gt;
Attendees&lt;br /&gt;
** Matthias Huetsch (Sun)&lt;br /&gt;
** Xiuzhi Cheng (Redflag CH2000, via phone)&lt;br /&gt;
** Dieter Loeschky (Sun, Monday only)&lt;br /&gt;
** Stefan Taxhet (Sun)&lt;br /&gt;
** Mathias Bauer (Sun)&lt;br /&gt;
** Martin Hollmichel (Sun)&lt;br /&gt;
** Eric (Yong Lin) Ma (IBM, Tuesday, via phone)&lt;br /&gt;
** Frank Peters (Sun, Monday)&lt;br /&gt;
** Matthias Klose (Canonical) &lt;br /&gt;
** Nils Fuhrmann (Sun)&lt;br /&gt;
** Thosten Behrens (Novell)&lt;br /&gt;
** Rene Engelhard (Debian)&lt;br /&gt;
** kendy (Novell, during DSCM discussion)&lt;br /&gt;
** Heiner Rechtien (Sun, during DSCM discussion)&lt;br /&gt;
** Kay Ramme (Sun, during API discussion)&lt;br /&gt;
&lt;br /&gt;
== Monday ==&lt;br /&gt;
&lt;br /&gt;
=== DSCM discussion ===&lt;br /&gt;
&lt;br /&gt;
Heiner presented a evaluation of the DSCM [http://wiki.services.openoffice.org/w/images/c/c0/Esc_dscm_evaluation.odp], [http://wiki.services.openoffice.org/w/images/a/a8/DSCM_evaluation_2009_03.odt]&lt;br /&gt;
&lt;br /&gt;
 Thorsten Behrens: - git is used broadest, large community, - git learning curve might a little bit steeper, but daily usage is easy, flexibility is great.&lt;br /&gt;
 Matthias H/Thorsten B. big projects (e.g. mozilla, linux kernel, etc) are on both systems: hg and git&lt;br /&gt;
 Jan: - no addtional tooling for cws with git is required. Heiner: but for milestone information. Jan: prefers git&lt;br /&gt;
 Matthias K.: unfortunately the import of bzr did not finished yet, would like to see the prototype for all three systems&lt;br /&gt;
 Stefan: has no preference, is interested in how the backend infrastructure can be managed, practical experience appreciated so running the pilots is interesting&lt;br /&gt;
 Rene: preference is git&lt;br /&gt;
 Mathias B.: - majority of Developers are Windows and Mac Users, so it is important to use best system available on these platforms and also including non-code developers in a prototype.&lt;br /&gt;
 Dieter: let the experts decide, ease of rolling out is important to the project&lt;br /&gt;
 Frank: offers one member of the documentation team for the pilot&lt;br /&gt;
 Nils: agrees to Mathias B., what is our target group, mozilla is already desktop oriented application, and they use hg&lt;br /&gt;
 Matthias H.: this is like a vi vs. emacs discussion, this can last endless&lt;br /&gt;
 Martin: would like to see a pilot for the candidates before doing a decision&lt;br /&gt;
 Nils: does it make sense to start the pilot with a reduced set of candidates? This is a matter of resources.&lt;br /&gt;
 Mathias K.: will look if Canonical can also support hardware if needed.&lt;br /&gt;
 Mathias H.: do we have success criteria ?&lt;br /&gt;
 all: a pilot should last a least two months, we should have a pilot for at least both: git and mercurial.&lt;br /&gt;
 Frank: we need to have a larger set of people doing the pilot to have satisfying data&lt;br /&gt;
 Nils: mercurial pilot will be sponsored by Hamburg RE&lt;br /&gt;
 Thorsten/kendy: will sponsor a git pilot&lt;br /&gt;
 Matthias K. bzr pilot to be sponsored by bzr team&lt;br /&gt;
 Heiner: incremental updated repositories are a prerequisite for a prototype, patches from the pilots will be applied via patchset into subversion&lt;br /&gt;
 Martin: also integration back needs to be done natively on the DSCM within the pilot&lt;br /&gt;
 all: negative success criteria: in case of failure the system is out&lt;br /&gt;
 martin/kendy: it may be useful to ask contributors for their favorites. these should be educated votes, meaning only opinions based on practical experience should be taken into account&lt;br /&gt;
 kendy: suggested educated vote of the member of the ESC (educated vote means: every voter need to do a cws in each pilot before give a vote)&lt;br /&gt;
 nils: is supporting _one_ pilot by RE&lt;br /&gt;
 majority (5 vs. 2) we will conduct a survey within 3 weeks (Stefan is driving this survey) to consult committers.  we will do an irc meeting on March 30th to decide on which DSCM to start the pilot.&lt;br /&gt;
&lt;br /&gt;
=== proposal for unified ODF Document icons ===&lt;br /&gt;
&lt;br /&gt;
Dieter proposed that for ODF unified Document icons should be used, meaning the various application using ODF should use the icons [http://wiki.services.openoffice.org/w/images/a/a7/ODF_document_icons.odp]. All agreed that this proposal is good, although some distributors may want to make slight modification to adopt them to their desktop theme.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== vanilla OOO Environment set up vs. Hamburg set up (aka configure vs. setsolar) Hamburg needs to take care about autotools  ===&lt;br /&gt;
&lt;br /&gt;
after consultation with ause it was agreed that the configure script should be adopted to serve also the needs of the Hamburg envrionment. Ause and Rene will work on this adoption with the objective to use one set of settings for both setup so that the problem raised by Rene should vanish.&lt;br /&gt;
&lt;br /&gt;
== Tuesday ==&lt;br /&gt;
&lt;br /&gt;
=== [[ESC/Criteria_for_bundling_extensions | Define Criteria ]] on when to bundle extensions ===&lt;br /&gt;
&lt;br /&gt;
After short discussion all agreed the engineering is not the main stakeholder for making a proposal for bundling an extension with the product. It is common sense, the the default bundling should be done on exceptional basis and that there should be good compelling reasons to do such bundling. Martin to extract technical criteria/prerequisites from the proposal, so that marketing / User Experience groups can define own rules upon that. The release status meeting should finally the meeting where proposal for bundling should be raised and decided upon.&lt;br /&gt;
&lt;br /&gt;
=== review of the ESC dashboard  ===&lt;br /&gt;
&amp;lt;nowiki&amp;gt;(see updates within &amp;lt;&amp;lt;/nowiki&amp;gt;[http://wiki.services.openoffice.oorg/wiki/ESC_dashboard http://wiki.services.openoffice.oorg/wiki/ESC_dashboard]&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== kick off discussion about changes to published UNO API ===&lt;br /&gt;
&lt;br /&gt;
see [http://wiki.services.openoffice.org/w/images/2/2a/Esc-mar-2009-api-deprecation.odp], it was agreed that this discussion is wanted and needed, Thorsten and Kay to work out some more details.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
* Stefan: to set up and drive DSCM survey&lt;br /&gt;
* Martin: work with marketing and User Experience group to define process on how to decide on bundling of extensions&lt;br /&gt;
* Martin: make [[FixesOnMaster]] from the ESC Dashboard happen&lt;br /&gt;
* Thorsten: finalize proposal for deprecating APIs&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=ESC_meeting_minutes_20090309&amp;diff=115456</id>
		<title>ESC meeting minutes 20090309</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=ESC_meeting_minutes_20090309&amp;diff=115456"/>
		<updated>2009-03-10T21:19:45Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* DSCM discussion */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;ESC meeting minutes March 9/10&amp;lt;sup&amp;gt;th&amp;lt;/sup&amp;gt; – Hamburg&lt;br /&gt;
&lt;br /&gt;
Attendees&lt;br /&gt;
** Matthias Huetsch (Sun)&lt;br /&gt;
** Xiuzhi Cheng (Redflag CH2000, via phone)&lt;br /&gt;
** Dieter Loeschky (Sun, Monday only)&lt;br /&gt;
** Stefan Taxhet (Sun)&lt;br /&gt;
** Mathias Bauer (Sun)&lt;br /&gt;
** Martin Hollmichel (Sun)&lt;br /&gt;
** Eric (Yong Lin) Ma (IBM, Tuesday, via phone)&lt;br /&gt;
** Frank Peters (Sun, Monday)&lt;br /&gt;
** Matthias Klose (Canonical) &lt;br /&gt;
** Nils Fuhrmann (Sun)&lt;br /&gt;
** Thosten Behrens (Novell)&lt;br /&gt;
** Rene Engelhard (Debian)&lt;br /&gt;
** kendy (Novell, during DSCM discussion)&lt;br /&gt;
** Heiner Rechtien (Sun, during DSCM discussion)&lt;br /&gt;
** Kay Ramme (Sun, during API discussion)&lt;br /&gt;
&lt;br /&gt;
== Monday ==&lt;br /&gt;
&lt;br /&gt;
=== DSCM discussion ===&lt;br /&gt;
&lt;br /&gt;
Heiner presented a evaluation of the DSCM [http://wiki.services.openoffice.org/w/images/c/c0/Esc_dscm_evaluation.odp], [http://wiki.services.openoffice.org/w/images/a/a8/DSCM_evaluation_2009_03.odt]&lt;br /&gt;
&lt;br /&gt;
 Thorsten Behrens: - git is used broadest, large community, - git learning curve might a little bit steeper, but daily usage is easy, flexibility is great.&lt;br /&gt;
 Matthias H/Thorsten B. big projects (e.g. mozilla, linux kernel, etc) are on both systems: hg and git&lt;br /&gt;
 Jan: - no addtional tooling for cws with git is required. Heiner: but for milestone information. Jan: prefers git&lt;br /&gt;
 Matthias K.: unfortunately the import of bzr did not finished yet, would like to see the prototype for all three systems&lt;br /&gt;
 Stefan: has no preference, is interested in how the backend infrastructure can be managed, practical experience appreciated so running the pilots is interesting&lt;br /&gt;
 Rene: preference is git&lt;br /&gt;
 Mathias B.: - majority of Developers are Windows and Mac Users, so it is important to use best system available on these platforms and also including non-code developers in a prototype.&lt;br /&gt;
 Dieter: let the experts decide, ease of rolling out is important to the project&lt;br /&gt;
 Frank: offers one member of the documentation team for the pilot&lt;br /&gt;
 Nils: agrees to Mathias B., what is our target group, mozilla is already desktop oriented application, and they use hg&lt;br /&gt;
 Matthias H.: this is like a vi vs. emacs discussion, this can last endless&lt;br /&gt;
 Martin: would like to see a pilot for the candidates before doing a decision&lt;br /&gt;
 Nils: does it make sense to start the pilot with a reduced set of candidates? This is a matter of resources.&lt;br /&gt;
 Mathias K.: will look if Canonical can also support hardware if needed.&lt;br /&gt;
 Mathias H.: do we have success criteria ?&lt;br /&gt;
 all: a pilot should last a least two months, we should have a pilot for at least both: git and mercurial.&lt;br /&gt;
 Frank: we need to have a larger set of people doing the pilot to have satisfying data&lt;br /&gt;
 Nils: mercurial pilot will be sponsored by Hamburg RE&lt;br /&gt;
 Thorsten/kendy: will sponsor a git pilot&lt;br /&gt;
 Matthias K. bzr pilot to be sponsored by bzr team&lt;br /&gt;
 Heiner: incremental updated repositories are a prerequisite for a prototype, patches from the pilots will be applied via patchset into subversion&lt;br /&gt;
 Martin: also integration back needs to be done natively on the DSCM within the pilot&lt;br /&gt;
 all: negative success criteria: in case of failure the system is out&lt;br /&gt;
 martin/kendy: it may be useful to ask contributors for their favorites. these should be educated votes, meaning only opinions based on practical experience should be taken into account&lt;br /&gt;
 kendy: suggested educated vote of the member of the ESC (educated vote means: every voter need to do a cws in each pilot before give a vote)&lt;br /&gt;
 nils: is supporting _one_ pilot by RE&lt;br /&gt;
 majority (5 vs. 2) we will conduct a survey within 3 weeks (Stefan is driving this survey) to consult committers.  we will do an irc meeting on March 30th to decide on which DSCM to start the pilot.&lt;br /&gt;
&lt;br /&gt;
=== proposal for unified ODF Document icons ===&lt;br /&gt;
&lt;br /&gt;
Dieter proposed that for ODF unified Document icons should be used, meaning the various application using ODF should use the icons [http://wiki.services.openoffice.org/w/images/a/a7/ODF_document_icons.odp]. All agreed that this proposal is good, although some distributors may want to make slight modification to adopt them to their desktop theme.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== vanilla OOO Environment set up vs. Hamburg set up (aka configure vs. setsolar) Hamburg needs to take care about autotools  ===&lt;br /&gt;
&lt;br /&gt;
after consultation with ause it was agreed that the configure script should be adopted to serve also the needs of the Hamburg envrionment. Ause and Rene will work on this adoption with the objective to use one set of settings for both setup so that the problem raised by Rene should vanish.&lt;br /&gt;
&lt;br /&gt;
== Tuesday ==&lt;br /&gt;
&lt;br /&gt;
=== [[ESC/Criteria_for_bundling_extensions | Define Criteria ]] on when to bundle extensions ===&lt;br /&gt;
&lt;br /&gt;
After short discussion all agreed the engineering is not the main stakeholder for making a proposal for bundling an extension with the product. It is common sense, the the default bundling should be done on exceptional basis and that there should be good compelling reasons to do such bundling. Martin to extract technical criteria/prerequisites from the proposal, so that marketing / User Experience groups can define own rules upon that. The release status meeting should finally the meeting where proposal for bundling should be raised and decided upon.&lt;br /&gt;
&lt;br /&gt;
=== review of the ESC dashboard  ===&lt;br /&gt;
&amp;lt;nowiki&amp;gt;(see updates within &amp;lt;&amp;lt;/nowiki&amp;gt;[http://wiki.services.openoffice.oorg/wiki/ESC_dashboard http://wiki.services.openoffice.oorg/wiki/ESC_dashboard]&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== kick off discussion about changes to published UNO API ===&lt;br /&gt;
&lt;br /&gt;
see [http://wiki.services.openoffice.org/w/images/2/2a/Esc-mar-2009-api-deprecation.odp], it was agreed that this discussion is wanted and needed, Thorsten and Kay to work out some more details.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Action Items ==&lt;br /&gt;
&lt;br /&gt;
* Stefan: to set up and drive DSCM survey&lt;br /&gt;
* Martin: work with marketing and User Experience group to define process on how to decide on bundling of extensions&lt;br /&gt;
* Martin: make [[FixesOnMaster]] from the ESC Dashboard happen&lt;br /&gt;
* Thorsten: finalize proposal for deprecating UNO APIs&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Impress/Performance&amp;diff=111250</id>
		<title>Impress/Performance</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Impress/Performance&amp;diff=111250"/>
		<updated>2009-02-10T13:14:35Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* Slideshow */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Ongoing work =&lt;br /&gt;
&lt;br /&gt;
== OpenDocument ==&lt;br /&gt;
&lt;br /&gt;
We currently evaluate possible bottlenecks and performance opportunities in the implementation of loading and saving the native OpenDocument xml formats in impress.&lt;br /&gt;
&lt;br /&gt;
== Slideshow ==&lt;br /&gt;
&lt;br /&gt;
We currently work on the visual performance of the slideshow in impress.&lt;br /&gt;
&lt;br /&gt;
Already detected problems we will try to address:&lt;br /&gt;
&lt;br /&gt;
* Timing problems in current implementation cause visual lag while during animations&lt;br /&gt;
* Rendering speed during slideshow is too slow for complex content&lt;br /&gt;
** Hardware acceleration of rendering during slideshow is desirable&lt;br /&gt;
*** Rework of the directx canvas for windows to use native directx calls to render geometry instead of using the slow GDI+&lt;br /&gt;
*** New XCanvas implementation based on pure OpenGL. A prototype is available in ooo-build [http://svn.gnome.org/viewvc/ooo-build/trunk/patches/test/opengl-canvas.diff?view=log]&lt;br /&gt;
** avoid intermediate representations and conversions, by using the drawing layer primitives in slideshow as well&lt;br /&gt;
*** use more high-level canvas primitives, gradients are a lot faster when not decomposed into polygon strips&lt;br /&gt;
&lt;br /&gt;
= Previews =&lt;br /&gt;
&lt;br /&gt;
PNG images can be saved in interlaced mode. This increases the file size a little but it allows to load preview image up to 64 times faster. Without it you can for example end with loading few megabytes image - only to compute a small preview containing 64x64 pixels. (see [http://www.libpng.org/pub/png/pngintro.html http://www.libpng.org/pub/png/pngintro.html] for interlaced example)&lt;br /&gt;
&lt;br /&gt;
The JPEG image format contains data stored hierarchically and thus can even provide higher quality preview images than a naive downsampling of the original size image. For JPEGs that have been saved in &amp;quot;progressive mode&amp;quot; only a small part of the image file has to be read for previews.&lt;br /&gt;
&lt;br /&gt;
The pngperf cws adds necessary API for loading images in preview mode.&lt;br /&gt;
&lt;br /&gt;
= Preview API =&lt;br /&gt;
&lt;br /&gt;
So far there is API for previews, but OOo doesn&amp;#039;t use it yet.&lt;br /&gt;
&lt;br /&gt;
There exist slidesorter-demo-* patches in ooo-build [http://svn.gnome.org/viewcvs/ooo-build/trunk/patches/src680/ http://svn.gnome.org/viewcvs/ooo-build/trunk/patches/src680/] to use pngperf API, but they have still some problems (such as impress sometimes showing preview quality images in slideshow presentation). There is problem with using that API, as Sun needs to keep API/ABI compatability, and thus it is now only possible to set parameters to png/jpeg loaders by static functions.&lt;br /&gt;
&lt;br /&gt;
== TODO: ==&lt;br /&gt;
&lt;br /&gt;
* provide hints for more situations where big images are previewed&lt;br /&gt;
* many more optimizations are possible...&lt;br /&gt;
* make an extension to downsample large images (5megapixels is common from digital camera) to screen resolutions such as 1024x768 or 800x600&lt;br /&gt;
* add image downsampling to support to [[http://www.ooomacros.org/user.php#95976 Impress Photo Album Creator extension]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Impress issues]]&lt;br /&gt;
[[Category:Performance]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2009&amp;diff=111137</id>
		<title>Conferences/FOSDEM/2009</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=Conferences/FOSDEM/2009&amp;diff=111137"/>
		<updated>2009-02-09T16:34:38Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: /* DevRoom */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{DISPLAYTITLE:FOSDEM 2009}}&lt;br /&gt;
This page will collect ideas, todos and everything else that is related to the OpenOffice.org project activities @FOSDEM 2009&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
|[[image:fosdem2009.gif|left]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Team ==&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Name !! Stay !! Function !! Funding request&lt;br /&gt;
|-&lt;br /&gt;
| Cor Nouws || about one and a half / two days || stand || 75 Euro&lt;br /&gt;
|-&lt;br /&gt;
| Sophie Gautier || 6th, 7th, 8th || stand || no funding request&lt;br /&gt;
|-&lt;br /&gt;
| Jean-François Terret || 6th, 7th, 8th || stand || no funding requested&lt;br /&gt;
|-&lt;br /&gt;
| [[User:Jsc|Jürgen Schmidt]] || 6th, 7th, 8th || stand, devroom || 326 Euro (hotel, flight)&lt;br /&gt;
|-&lt;br /&gt;
| Stephan Bergmann || 6th, 7th, 8th || stand, devroom || 326 Euro (hotel, flight)&lt;br /&gt;
|-&lt;br /&gt;
| Leo Moons || 6th, 7th || stand || no funding requested&lt;br /&gt;
|-&lt;br /&gt;
| [[User:ErAck|Eike Rathke]] || 6th, 7th, 8th || stand, devroom || 278 Euro (hotel, fuel)&lt;br /&gt;
|-&lt;br /&gt;
| Florian Effenberger || from 7th in the afternoon until 8th noon || stand || ~250 Euro (hotel, traveling)&lt;br /&gt;
|-&lt;br /&gt;
| Jacqueline Rahemipour || 6th, 7th, 8th || stand || no funding requested&lt;br /&gt;
|-&lt;br /&gt;
| Mechtilde Stehmann || 7th, 8th || stand || ~250 Euro (hotel, traveling)&lt;br /&gt;
|-&lt;br /&gt;
| Michael Stehmann || 7th, 8th || stand || ~250 Euro (hotel, traveling)&lt;br /&gt;
|-&lt;br /&gt;
| [[User:ericb |Eric Bachard]] || 6th, 7th, 8th || stand, devroom || 390 Euro (hotel, flight)&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;strike&amp;gt;Robert Vojta&amp;lt;/strike&amp;gt; (sick) || &amp;lt;strike&amp;gt;6th, 7th, 8th&amp;lt;/strike&amp;gt; || &amp;lt;strike&amp;gt;stand, devroom&amp;lt;/strike&amp;gt; || &amp;lt;strike&amp;gt;323 Euro (hotel, flight)&amp;lt;/strike&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Thorsten Behrens || 7th, 8th || stand, devroom || 160 Euro (hotel, flight)&lt;br /&gt;
|-&lt;br /&gt;
| Louis Suarez Potts || ?? || stand || ??&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== DevRoom ==&lt;br /&gt;
We will have our DevRoom on Saturday 7th from 13:00 to 19:00 in building AW room [http://fosdem.org/2009/schedule/rooms/aw1.126 AW1.126] and on Sunday 8th from 9:00 - 13:00 in building AW room [http://fosdem.org/2009/schedule/rooms/aw1.105 AW1.105].&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ DevRoom Overview&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Time !! Title !! Session type !! Slides !!Speaker&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Saturday 7th - Room AW1.126&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 13:00 - 13:15 || [http://fosdem.org/2009/schedule/events/ooo_welcome Welcome] || informal || ||&lt;br /&gt;
|-&lt;br /&gt;
| 13:15 - 14:15 || [http://fosdem.org/2009/schedule/events/ooo_uno UNO: Anecdotal Evidence] || Presentation || || [http://fosdem.org/2009/schedule/speakers/stephan+bergmann Stephan Bergmann]&lt;br /&gt;
|- &lt;br /&gt;
| 14:15 - 15:15 || [http://fosdem.org/2009/schedule/events/ooo_java Introduction to Java development with OpenOffice.org] || Presentation || || [http://fosdem.org/2009/schedule/speakers/robert+vojta &amp;lt;strike&amp;gt;Robert  Vojta&amp;lt;/strike&amp;gt; (sick) -&amp;gt; Juergen Schmidt] &lt;br /&gt;
|-&lt;br /&gt;
| 15:15 - 17:15 || [http://fosdem.org/2009/schedule/events/ooo_extensions_in_java OpenOffice.org Extensions in Java – do it yourself] || Workshop || || [http://fosdem.org/2009/schedule/speakers/juergen+schmidt Jürgen Schmidt]  &lt;br /&gt;
|-&lt;br /&gt;
| 17:15 - 18:15 || [http://fosdem.org/2009/schedule/events/ooo_gfx_hackers Layout &amp;amp; Canvas &amp;amp; Slideshow - selected topics for the graphics hackers] || Presentation || [[Media:Fosdem_2009.pdf|pdf]] || [http://fosdem.org/2009/schedule/speakers/thorsten+behrens Thorsten Behrens]&lt;br /&gt;
|-&lt;br /&gt;
| 18:15 - 18:45 || [http://fosdem.org/2009/schedule/events/ooo_bug_hunting Bug hunting and fixing] || Workshop || || all speaker&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sunday 8th - Room AW1.1.05 &amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 9:00 - 11:00 || [http://fosdem.org/2009/schedule/events/ooo_code_mac_port Traveling in OOo code and having Fun with the Mac port] || Workshop || || [http://fosdem.org/2009/schedule/speakers/eric+bachard Eric Bachard]&lt;br /&gt;
|-&lt;br /&gt;
| 11:00 - 13:00 || [http://fosdem.org/2009/schedule/events/ooo_calc_profiling OOoCalc Bug Hunting and Performance Profiling Workshop] || Workshop || || [http://fosdem.org/2009/schedule/speakers/eike+rathke Eike Rathke]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Stand ==&lt;br /&gt;
Our stand will be in building H and we can get in the building at 9:00am (on Saturday definitely not earlier).&lt;br /&gt;
&lt;br /&gt;
{| border=1&lt;br /&gt;
|+ Stand Overview&lt;br /&gt;
|- bgcolor=#CDDBF6&lt;br /&gt;
! Time !! Stand staff &lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Saturday 7th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 10:00 - 12:00 || Sophie / Juergen&lt;br /&gt;
|-&lt;br /&gt;
| 12:00 - 14:00 || Sophie / Jacqueline / Leo&lt;br /&gt;
|- &lt;br /&gt;
| 14:00 - 16:00 || Sophie / Jacqueline / Leo&lt;br /&gt;
|-&lt;br /&gt;
| 16:00 - 18:30 || Cor Nouws / Sophie / Leo till 18:00&lt;br /&gt;
|- bgcolor=#7c9acd&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; align=&amp;quot;center&amp;quot; | &amp;#039;&amp;#039;&amp;#039;Sunday 8th&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
| 9:00 - 11:00 || Juergen / Thorsten&lt;br /&gt;
|-&lt;br /&gt;
| 11:00 - 13:00 || Cor Nouws / Sophie / Stephan / Eric&lt;br /&gt;
|-&lt;br /&gt;
| 13:00 - 15:00 || Cor Nouws / Sophie&lt;br /&gt;
|-&lt;br /&gt;
| 15:00 - 18:00 || Juergen / Sophie / Eike&lt;br /&gt;
|}&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
The main idea behind the stand/booth for FOSDEM 2009 is to present the project, demo it, promote it, .... The booth should be a meeting point for all who work on the project and for all who are interested in the project. Interested to learn more, to meet the developers, the volunteers behind the project, to become a developer, ... &lt;br /&gt;
&lt;br /&gt;
* Coffee&amp;lt;br&amp;gt;Sophie volunteered to organize a coffee machine and everything else that is necessary to serve some good coffee for all the breaks ;-)&lt;br /&gt;
* T-Shirts (available for a small donation)&lt;br /&gt;
* other merchandising material (TBD)&lt;br /&gt;
&lt;br /&gt;
== Saturday evening dinner in Brussels around 20:00 hrs ==&lt;br /&gt;
&lt;br /&gt;
Who will attend?&lt;br /&gt;
&lt;br /&gt;
Leo, Juergen, Florian, Eric, Jacqueline, Eike, Anne, Stephan&lt;br /&gt;
&lt;br /&gt;
Robert had canceled his attendance, he has a virus influenza.&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Design ==&lt;br /&gt;
Two different designs (by Jacek) for possible T-Shirts, coffee mugs, lanyard keychains.&lt;br /&gt;
The first is for keychains, the second for the T-Shirt (royal) and the third for coffee mugs (white).&lt;br /&gt;
The third image is a draft for a possible roll-up banner. It&amp;#039;s for discussion and we need ~10 tags/terms/words that are specific or typical for OpenOffice. If somebody has a better idea, everything is welcome.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:oo3_preview_all.png|thumb|left|400px|Design 1]] || [[Image:oo3_ver_5_keychains_a_preview.png|thumb|left|400px|Design 1a for keychains]] || [[Image:oo3_ver_5_keychains_b_preview.png|thumb|left|400px|Design 1b for keychains]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:oo3_preview_all_a.png|thumb|left|400px|Design 2]] || ||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Banner Design ==&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
| [[Image:banner2b.png|thumb|left|400px|Draft for roll-up banner]] || [[Image:255px-Banner2c.png|thumb|left|400px|Draft 2 for roll-up banner]] || [[Image:oo3_banner_draft3.png|thumb|left|400px|Draft 3 for roll-up banner]] &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:Conferences]]&lt;br /&gt;
[[Category:FOSDEM]]&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
	<entry>
		<id>https://wiki.openoffice.org/w/index.php?title=File:Fosdem_2009.pdf&amp;diff=111127</id>
		<title>File:Fosdem 2009.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.openoffice.org/w/index.php?title=File:Fosdem_2009.pdf&amp;diff=111127"/>
		<updated>2009-02-09T16:28:04Z</updated>

		<summary type="html">&lt;p&gt;Thorsten: fosdem 2009 &amp;quot;selected topics for graphics hackers&amp;quot; talk slides&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;fosdem 2009 &amp;quot;selected topics for graphics hackers&amp;quot; talk slides&lt;/div&gt;</summary>
		<author><name>Thorsten</name></author>
	</entry>
</feed>