content/marketing/ooocon2005/schedule/friday_community.html - openoffice-org - Git at Google

 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <head>
   <meta content="text/html; charset=ISO-8859-1"
  http-equiv="content-type">
   <title>OOoCon 2005 Community</title>
   <style type="text/css">
 h3 { background-color: rgb(255, 192, 90) ! important;
 color: rgb(255, 255, 255);
 }
   </style>
 </head>
 <body>
 <div id="startpage" class="app">
 <div class="h3" id="myprojects">
 <h2>Abstracts
 of
 Conference Papers
 - Community Stream</h2>
 <h3><a name="c5"></a>FOSS
 Participation in the Developing World</h3>
 </div>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Danese Cooper - Open
 Source Diva, Intel Corporation<br>
       </td>
     </tr>
     <tr class="b">
       <td>OpenOffice.org has been
 a huge boon to the so-called &ldquo;Developing
 World&rdquo;, places where technology penetration (even just
 electricity
 penetration) is relatively shallow and the hard-currency GDP is
 relatively low.&nbsp; Yet much of the Developing World has not yet
 understood that in the FOSS software commons, &ldquo;Participation
 =
 Ownership&rdquo;.&nbsp; Listen to a report on the current state
 of global
 participation in the FOSS ecosystem, garnered from first-hand
 observations by Danese Cooper, former Chief Open Source Evangelist for
 Sun Microsystems and now Sr. Director of Open Source Strategy for Intel&rsquo;s
 CSO Group.<br>
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biography: Danese Cooper
 has a 15-year history in the software industry
 and has long been an advocate for transparent development
 methodologies. Danese worked for six years at Sun Microsystems, Inc. on
 the inception and growth of the various open source projects sponsored
 by Sun (including OpenOffice.org, java.net and blogs.sun.com). She was
 Sun's Chief Open Source Evangelist and founded Sun's Open Source
 Programs Office. She has unique experience implementing open source
 projects from within a large proprietary company. She joined the OSI
 Board in December 2001 and currently serves as Secretary &amp;
 Treasurer. As of March 2005 Danese has joined Intel to advise on open
 source projects, investment and support. She speaks internationally on
 Open Source and Licensing issues. <br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="friday.html">Back</a><br>
 <h3><a name="c6"></a>Developing
 for OpenOffice.org</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Martin Hollmichel -
 OpenOffice.org Project Lead of Tools, Porting and External Project, Sun
 Microsystems<br>
       </td>
     </tr>
     <tr class="b">
       <td>The session will
 introduce on how to contribute to OpenOffice.org. <br>
 There are many different way on how to contribute to the project, we
 will look on different aspects: <br>
       <ul>
         <li>code contributions, </li>
         <li>macros, examples and
 other contributions</li>
         <li>legal aspects </li>
         <li>access to resources of
 the Projects (Website, Issue Tracker, etc) </li>
         <li>CVS access and
 branches </li>
         <li>channels of
 communication </li>
       </ul>
 The new OpenOffice.org development process differs in several aspects
 from usual OpenSource habits of other projects. The session will
 explain reasons for this differences and also discuss chances and
 difficulties of having an own development style. In detail we will have
 a look onto different roles of contributors, especially at the impact
 of the new development process to core-developer, QA folks and
 add-on-developers.<br>
 Target: New Developers<br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="friday.html">Back</a><br>
 <h3><a name="c7"></a>Doing
 QA at OpenOffice.org</h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Joost Andrae -
 StarOffice program manager, Sun Microsystems</td>
     </tr>
     <tr class="b">
       <td>Overview<br>
       <ul>
         <li>How can you help?</li>
         <li>confirming issues</li>
         <li>submitting issues</li>
         <li>gather feedback from
 various sources (Users mailing list, discussion forums, etc.)</li>
         <li>...</li>
         <li>Child workspaces from
 QA perspective</li>
         <li>Information about
 OpenOffice.org automation</li>
         <li>About crash reporting
 and how it helps OpenOffice.org development</li>
         <li>QA project statistics</li>
         <li>Localization (l10n)
 team collaboration with QA</li>
       </ul>
 Target audience: Developers, Testers, Translators and People interested
 into OpenOffice.org QA<br>
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biography: Born in 1965.
 In the late 80's I had my first experiences
 with RDBMS, SQL, software distribution, marketing and support on
 products running on DOS, OS/2 and Windows. Later I did Informix 4GL
 programming (at different companies) on SINIX and BSD UNIX. Since 1995
 I'm working on the StarOffice product which later open sourced as
 OpenOffice.org. I started as a QA engineer doing QA &amp; testing
 in
 Calc, Chart, Math and on Sun ONE Webtop. Later I've been doing QA
 &amp;
 Coordination within StarOffice development at Sun Microsystems in
 Hamburg, Germany. My current position is StarOffice Program Manager as
 part of the StarOffice Operations team within StarOffice.<br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="friday.html">Back</a><br>
 <h3><a name="c8"></a>Addons
 : From production to end-users </h3>
 <table border="1" cellpadding="3" cellspacing="2" width="100%">
   <tbody>
     <tr style="font-style: italic;" class="a">
       <td>Laurent Godard -
 Directeur Technique, Nuxeo - Indesko<br>
       </td>
     </tr>
     <tr class="b">
       <td>OOo scripting and addon
 production is just an other way to bring value to OOo by attracting new
 developpers.<br>
       <br>
 OpenOffice.org brings a lot of possibilities regarding scripting.<br>
 With the 2.0 release, a lot of new languages are available and the
 addon installation is now available at end users level<br>
       <br>
 It is now time to take benefits of this capabilities and organize
 ourselves to make addon production and use more and more easy. Building
 the scripting project through 3 main branches is a way to
 attract new developers in OOo world's and bring value to end users.<br>
 These 3 branches are :<br>
       <ul>
         <li>Provide basic
 knowledge and help new commers start quickly</li>
         <li>Collect the addons and
 check/verify/valid them</li>
         <li>Provide a user
 friendly tool allowing end users to install these addons</li>
       </ul>
 I'll begin by a description of the scripting incubator project, the
 needs regarding contributors and the benefits that end-users can attend
 from. Then the attendees will discuss the following points:<br>
       <ul>
         <li>How to build a
 development team covering the languages supported by OOo
 scripting (basic, java, python, javascript). Define the tools in each
 of them to make life easier to newcomers (pre-built wizards,
 introspection tools...)</li>
         <li>The translation
 mechanism we should adopt and the relation with the native-lang
 communities</li>
         <li>The validation of the
 submitted addons and the repository</li>
         <li>The end-user tool to
 browse the repository </li>
         <li>The other
 possibilities of such a deployment tools (templates, galleries ...)</li>
         <li>...</li>
       </ul>
 Target audience: Addon developers (basic, python, java ...),
 translators &ndash; native-lang representative, End-users who want
 to deploy
 addons ...<br>
       </td>
     </tr>
     <tr style="font-style: italic;" class="a">
       <td>Biography: The speaker
 is technical director of Indesko, building
 solutions for workflows and document management with OpenOffice.org for
 large companies. Involved in the OOo community for many years and
 author of various well know tools such as DicOOo, FontOOo, OOoWikipedia
 ..., the speaker is dedicated to macros writing in various language and
 known as a reference regarding OOo API use. He is also the co-author of
 the only french book dealing with OOo macros and API. He is now deeply
 involved in the scripting project.<br>
       </td>
     </tr>
   </tbody>
 </table>
 <a href="friday.html">Back</a><br>
 </div>
 </body>
 </html>
	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
	<html>
	<head>
	<meta content="text/html; charset=ISO-8859-1"
	http-equiv="content-type">
	<title>OOoCon 2005 Community</title>
	<style type="text/css">
	h3 { background-color: rgb(255, 192, 90) ! important;
	color: rgb(255, 255, 255);
	}
	</style>
	</head>
	<body>
	<div id="startpage" class="app">
	<div class="h3" id="myprojects">
	<h2>Abstracts
	of
	Conference Papers
	- Community Stream</h2>
	<h3><a name="c5"></a>FOSS
	Participation in the Developing World</h3>
	</div>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Danese Cooper - Open
	Source Diva, Intel Corporation<br>
	</td>
	</tr>
	<tr class="b">
	<td>OpenOffice.org has been
	a huge boon to the so-called “Developing
	World”, places where technology penetration (even just
	electricity
	penetration) is relatively shallow and the hard-currency GDP is
	relatively low.  Yet much of the Developing World has not yet
	understood that in the FOSS software commons, “Participation
	=
	Ownership”.  Listen to a report on the current state
	of global
	participation in the FOSS ecosystem, garnered from first-hand
	observations by Danese Cooper, former Chief Open Source Evangelist for
	Sun Microsystems and now Sr. Director of Open Source Strategy for Intel’s
	CSO Group.<br>
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biography: Danese Cooper
	has a 15-year history in the software industry
	and has long been an advocate for transparent development
	methodologies. Danese worked for six years at Sun Microsystems, Inc. on
	the inception and growth of the various open source projects sponsored
	by Sun (including OpenOffice.org, java.net and blogs.sun.com). She was
	Sun's Chief Open Source Evangelist and founded Sun's Open Source
	Programs Office. She has unique experience implementing open source
	projects from within a large proprietary company. She joined the OSI
	Board in December 2001 and currently serves as Secretary &
	Treasurer. As of March 2005 Danese has joined Intel to advise on open
	source projects, investment and support. She speaks internationally on
	Open Source and Licensing issues. <br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="friday.html">Back</a><br>
	<h3><a name="c6"></a>Developing
	for OpenOffice.org</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Martin Hollmichel -
	OpenOffice.org Project Lead of Tools, Porting and External Project, Sun
	Microsystems<br>
	</td>
	</tr>
	<tr class="b">
	<td>The session will
	introduce on how to contribute to OpenOffice.org. <br>
	There are many different way on how to contribute to the project, we
	will look on different aspects: <br>
	<ul>
	<li>code contributions, </li>
	<li>macros, examples and
	other contributions</li>
	<li>legal aspects </li>
	<li>access to resources of
	the Projects (Website, Issue Tracker, etc) </li>
	<li>CVS access and
	branches </li>
	<li>channels of
	communication </li>
	</ul>
	The new OpenOffice.org development process differs in several aspects
	from usual OpenSource habits of other projects. The session will
	explain reasons for this differences and also discuss chances and
	difficulties of having an own development style. In detail we will have
	a look onto different roles of contributors, especially at the impact
	of the new development process to core-developer, QA folks and
	add-on-developers.<br>
	Target: New Developers<br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="friday.html">Back</a><br>
	<h3><a name="c7"></a>Doing
	QA at OpenOffice.org</h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Joost Andrae -
	StarOffice program manager, Sun Microsystems</td>
	</tr>
	<tr class="b">
	<td>Overview<br>
	<ul>
	<li>How can you help?</li>
	<li>confirming issues</li>
	<li>submitting issues</li>
	<li>gather feedback from
	various sources (Users mailing list, discussion forums, etc.)</li>
	<li>...</li>
	<li>Child workspaces from
	QA perspective</li>
	<li>Information about
	OpenOffice.org automation</li>
	<li>About crash reporting
	and how it helps OpenOffice.org development</li>
	<li>QA project statistics</li>
	<li>Localization (l10n)
	team collaboration with QA</li>
	</ul>
	Target audience: Developers, Testers, Translators and People interested
	into OpenOffice.org QA<br>
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biography: Born in 1965.
	In the late 80's I had my first experiences
	with RDBMS, SQL, software distribution, marketing and support on
	products running on DOS, OS/2 and Windows. Later I did Informix 4GL
	programming (at different companies) on SINIX and BSD UNIX. Since 1995
	I'm working on the StarOffice product which later open sourced as
	OpenOffice.org. I started as a QA engineer doing QA & testing
	in
	Calc, Chart, Math and on Sun ONE Webtop. Later I've been doing QA
	&
	Coordination within StarOffice development at Sun Microsystems in
	Hamburg, Germany. My current position is StarOffice Program Manager as
	part of the StarOffice Operations team within StarOffice.<br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="friday.html">Back</a><br>
	<h3><a name="c8"></a>Addons
	: From production to end-users </h3>
	<table border="1" cellpadding="3" cellspacing="2" width="100%">
	<tbody>
	<tr style="font-style: italic;" class="a">
	<td>Laurent Godard -
	Directeur Technique, Nuxeo - Indesko<br>
	</td>
	</tr>
	<tr class="b">
	<td>OOo scripting and addon
	production is just an other way to bring value to OOo by attracting new
	developpers.<br>
	<br>
	OpenOffice.org brings a lot of possibilities regarding scripting.<br>
	With the 2.0 release, a lot of new languages are available and the
	addon installation is now available at end users level<br>
	<br>
	It is now time to take benefits of this capabilities and organize
	ourselves to make addon production and use more and more easy. Building
	the scripting project through 3 main branches is a way to
	attract new developers in OOo world's and bring value to end users.<br>
	These 3 branches are :<br>
	<ul>
	<li>Provide basic
	knowledge and help new commers start quickly</li>
	<li>Collect the addons and
	check/verify/valid them</li>
	<li>Provide a user
	friendly tool allowing end users to install these addons</li>
	</ul>
	I'll begin by a description of the scripting incubator project, the
	needs regarding contributors and the benefits that end-users can attend
	from. Then the attendees will discuss the following points:<br>
	<ul>
	<li>How to build a
	development team covering the languages supported by OOo
	scripting (basic, java, python, javascript). Define the tools in each
	of them to make life easier to newcomers (pre-built wizards,
	introspection tools...)</li>
	<li>The translation
	mechanism we should adopt and the relation with the native-lang
	communities</li>
	<li>The validation of the
	submitted addons and the repository</li>
	<li>The end-user tool to
	browse the repository </li>
	<li>The other
	possibilities of such a deployment tools (templates, galleries ...)</li>
	<li>...</li>
	</ul>
	Target audience: Addon developers (basic, python, java ...),
	translators – native-lang representative, End-users who want
	to deploy
	addons ...<br>
	</td>
	</tr>
	<tr style="font-style: italic;" class="a">
	<td>Biography: The speaker
	is technical director of Indesko, building
	solutions for workflows and document management with OpenOffice.org for
	large companies. Involved in the OOo community for many years and
	author of various well know tools such as DicOOo, FontOOo, OOoWikipedia
	..., the speaker is dedicated to macros writing in various language and
	known as a reference regarding OOo API use. He is also the co-author of
	the only french book dealing with OOo macros and API. He is now deeply
	involved in the scripting project.<br>
	</td>
	</tr>
	</tbody>
	</table>
	<a href="friday.html">Back</a><br>
	</div>
	</body>
	</html>