https://wiki.cdot.senecacollege.ca/w/api.php?action=feedcontributions&user=Dmoon4&feedformat=atomCDOT Wiki - User contributions [en]2024-03-28T18:57:18ZUser contributionsMediaWiki 1.30.0https://wiki.cdot.senecacollege.ca/w/index.php?title=User:Dmoon4&diff=24887User:Dmoon42009-04-02T19:25:09Z<p>Dmoon4: </p>
<hr />
<div>== About Me ==<br />
<ul><br />
<li>'''Name : '''Daeseon Moon</li><br />
<li>'''Program : '''Computer Programming and Analysis</li><br />
</ul><br />
<br />
== Contacts ==<br />
<ul><br />
<li>'''Email : '''dmoon4@learn.senecac.on.ca</li><br />
<li>'''Blog : '''http://daeseonmoon.wordpress.com</li><br />
<li>'''IRC Nick: '''daeseon</li><br />
</ul><br />
<br />
== Project ==<br />
<ul><br />
<li>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles Improve Impress Style]</li><br />
</ul><br />
<br />
== Links ==<br />
<ul><br />
<li>[http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide OO Developer's Guide]</li><br />
</ul></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=User:Dmoon4&diff=24886User:Dmoon42009-04-02T19:23:25Z<p>Dmoon4: </p>
<hr />
<div>== About Me ==<br />
<ul><br />
<li>'''Name : '''Daeseon Moon</li><br />
<li>'''Program : '''Computer Programming and Analysis</li><br />
</ul><br />
<br />
== Contacts ==<br />
<ul><br />
<li>'''Email : '''dmoon4@learn.senecac.on.ca</li><br />
<li>'''Blog : '''http://daeseonmoon.wordpress.com</li><br />
<li>'''IRC Nick: '''daeseon</li><br />
</ul><br />
<br />
== Project ==<br />
<ul><br />
<li>'''[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles Improve Impress Style]'''</li><br />
</ul></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24544DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:15:27Z<p>Dmoon4: /* Week 10 (Mar 16) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Daeseon Moon, Improve impress style, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Fred Wang, Issue, Issue Link.<br />
**Tiago, Building OpenOffice on OpenSolaris<br />
* Thu: <br />
**Ladan Zahir, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Jerry Pau, Issue, Issue Link.<br />
**Name1, Issue, Issue Link.<br />
* Thu: <br />
**Daeseon Moon, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==<br />
* Tue: <br />
**Ladan Zahir, Issue, Issue Link.<br />
**Fred Wang, Issue, Issue Link.<br />
* Thu: <br />
**Bartosz Barcicki, Issue, Issue Link.<br />
**Jerry Pau, Issue, Issue Link.</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24540DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:13:18Z<p>Dmoon4: /* Week 12 (Mar 30) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Tiago, Building OpenOffice on OpenSolaris<br />
* Thu: <br />
**Ladan, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Jerry Pau, Issue, Issue Link.<br />
**Name1, Issue, Issue Link.<br />
* Thu: <br />
**Daeseon Moon, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==<br />
* Tue: <br />
**Ladan, Issue, Issue Link.<br />
**Fred Wang, Issue, Issue Link.<br />
* Thu: <br />
**Bartosz Barcicki, Issue, Issue Link.<br />
**Jerry Pau, Issue, Issue Link.</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24530DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:08:10Z<p>Dmoon4: /* Week 10 (Mar 16) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Name4, Issue, Issue Link.<br />
* Thu: <br />
**Daeseon Moon, Issue, Issue Link.<br />
**Name6, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name7, Issue, Issue Link.<br />
**Name1, Issue, Issue Link.<br />
* Thu: <br />
**Daeseon Moon, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Name4, Issue, Issue Link.<br />
**Jerry Pau, Issue, Issue Link.<br />
* Thu: <br />
**Fred Wang, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24528DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:07:36Z<p>Dmoon4: /* Week 11 (Mar 23) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Name4, Issue, Issue Link.<br />
* Thu: <br />
**Name5, Issue, Issue Link.<br />
**Name6, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name7, Issue, Issue Link.<br />
**Name1, Issue, Issue Link.<br />
* Thu: <br />
**Daeseon Moon, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Name4, Issue, Issue Link.<br />
**Name5, Issue, Issue Link.<br />
* Thu: <br />
**Fred Wang, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24527DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:06:55Z<p>Dmoon4: /* Week 11 (Mar 23) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Name4, Issue, Issue Link.<br />
* Thu: <br />
**Name5, Issue, Issue Link.<br />
**Name6, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name7, Issue, Issue Link.<br />
**Name1, Issue, Issue Link.<br />
* Thu: <br />
**Name2, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Name4, Issue, Issue Link.<br />
**Name5, Issue, Issue Link.<br />
* Thu: <br />
**Fred Wang, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24526DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:06:31Z<p>Dmoon4: /* Week 12 (Mar 30) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Name4, Issue, Issue Link.<br />
* Thu: <br />
**Name5, Issue, Issue Link.<br />
**Name6, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name7, Issue, Issue Link.<br />
**Daeseon Moon, Issue, Issue Link.<br />
* Thu: <br />
**Name2, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Name4, Issue, Issue Link.<br />
**Name5, Issue, Issue Link.<br />
* Thu: <br />
**Fred Wang, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24525DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:05:58Z<p>Dmoon4: /* Week 12 (Mar 30) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Name4, Issue, Issue Link.<br />
* Thu: <br />
**Name5, Issue, Issue Link.<br />
**Name6, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name7, Issue, Issue Link.<br />
**Daeseon Moon, Issue, Issue Link.<br />
* Thu: <br />
**Name2, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Daeseon Moon, Issue, Issue Link.<br />
**Name5, Issue, Issue Link.<br />
* Thu: <br />
**Fred Wang, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=24524DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-03-17T16:05:39Z<p>Dmoon4: /* Week 11 (Mar 23) - Presenting Issues */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) - Course Introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
<br />
<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common editing tasks, history, and reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ distcc]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc Installation]], Managing and Building Large Source Trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local working copy<br />
*** Typical read-only activities: ''checkout, update''<br />
* Using ''make'' to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) ''make'']<br />
* Building large open source projects from source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control with Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install distcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to compile locally and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
== Week 4 (Feb 2) - Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or submitting [http://qa.openoffice.org/issue_handling/basic_rules.html rules]<br />
*** Only one problem per issue<br />
*** Summary (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaborative-ly create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) - Navigating The Source Code ==<br />
* Learning to be "lost productively"<br />
** Adding to OpenOffice is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org source code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers guide]<br />
** OOo directory structure<br />
* Searching for code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to make changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** Complete week 4 TODO<br />
** Run, make a change, build, and then run again<br />
<br />
== Week 6 (Feb 16) - Patches, Build, GDB ==<br />
* Guest lecturer Eric Bachard, lead of OOo [http://education.openoffice.org/ Education Project]<br />
** Patches <br />
** Build<br />
** [http://www.gnu.org/software/gdb/ GDB]<br />
* '''Resources'''<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090217&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Tuesday's lecture]<br />
** [http://fardad.com/irclogs/Default.aspx?co=1&log=%23lecture.education.openoffice.org.freenode.20090219&u1=All+Users&u2=No+One+Else&u3=No+One+Else&u4=No+One+Else Thursday's lecture]<br />
** [http://linux.about.com/od/commands/l/blcmdl1_patch.htm patch command]<br />
* '''TODO'''<br />
** Complete week 5 TODO<br />
** Test and experiment with patches ie. create, dry run, apply... (blog, wiki)<br />
** Use GDB and run OpenOffice in debug mode (blog, wiki)<br />
<br />
== Week 7 (Feb 23) - Selecting a Project (Issue) ==<br />
* '''[http://education.openoffice.org Education project]'''<br />
** Become a member: [http://education.openoffice.org/servlets/ProjectMemberList Membership]<br />
** Select a project: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort Available Projects] (search for those with Seneca tag)<br />
** [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress Additional projects]<br />
** Update Seneca page: [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Seneca Seneca Page On Education Project]<br />
* '''Resources'''<br />
** [[OOo Project List]]<br />
** [http://wiki.services.openoffice.org/wiki/Source_code_directories OOo Directories description]<br />
** [http://wiki.services.openoffice.org/wiki/ChildWorkSpace ChildWorkSpace(CWS)]<br />
* '''TO DO'''<br />
== Week 8 (Mar 02) - ==<br />
== Week 9 (Mar 09) - ==<br />
* Tue: filling spots<br />
* Thu: <br />
**Name1, Issue, Issue Link.<br />
**Name2, Issue, Issue Link.<br />
<br />
== Week 10 (Mar 16) - Presenting Issues ==<br />
* Tue: <br />
**Name3, Issue, Issue Link.<br />
**Name4, Issue, Issue Link.<br />
* Thu: <br />
**Name5, Issue, Issue Link.<br />
**Name6, Issue, Issue Link.<br />
<br />
== Week 11 (Mar 23) - Presenting Issues ==<br />
* Tue: <br />
**Name7, Issue, Issue Link.<br />
**Daeseon Moon, Issue, Issue Link.<br />
* Thu: <br />
**Name2, Issue, Issue Link.<br />
**Name3, Issue, Issue Link.<br />
<br />
== Week 12 (Mar 30) - Presenting Issues ==<br />
* Tue: <br />
**Name4, Issue, Issue Link.<br />
**Name5, Issue, Issue Link.<br />
* Thu: <br />
**Fred Wang, Issue, Issue Link.<br />
**Bartosz Barcicki, Issue, Issue Link.<br />
<br />
== Week 13 (Apr 06) - Presenting Issues ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Project_List&diff=24461Project List2009-03-13T02:24:34Z<p>Dmoon4: /* Active Projects */</p>
<hr />
<div>[http://www.senecac.on.ca Seneca College] is working on many joint research and development projects with [http://www.mozilla.com Mozilla] and [http://fedoraproject.org Fedora]. These projects are listed below. Many of the projects below are part of the [[DPS909]] or [[OSD600]] courses or the [[LUX Program]].<br />
<br />
For more information about what [http://www.senecac.on.ca Seneca] is doing with [http://www.mozilla.com Mozilla], [http://fedoraproject.org Fedora], and other open source projects, see the [[Main Page]].<br />
<br />
= Introduction =<br />
<br />
This page lists many of the research and coursework projects that are being done between Seneca faculty, students, and various Open Source communities, including Mozilla, Fedora, and OpenOffice.org. All of these projects are open source, and you can get involved with any of the current ones, or look at the list of [[Potential Projects]]. To claim a project, move it from the [[Potential Projects]] page to Active Project table below and create a link to a new project page based on the [[Sample Project]] page.<br />
<br />
= Active Projects =<br />
<br />
{| class="mediawiki sortable" border="1"<br />
<br />
|-<br />
!Project Name<br />
!Description<br />
!Leader(s)<br />
!Community or Communities<br />
<br />
|-<br />
|[[Migrate aNd Manage]]<br />
|Anaconda supports partition resizing (including NTFS) in Rawhide now. It would be great to combine this with a data migration tool for Windows or dual booting users.<br />
|Nestor Chan<br />
|Fedora<br />
<br />
|-<br />
|[[Add IPv6 Support to Condor]]<br />
|Sooner or later we're going to have to live with IPv6. Many applications are very tied to IPv4 and that includes Condor. Understand what IP addresses really mean to Condor, like many existing systems, and what the implications of an IPv6 conversion means and how it can be done. There are many resources about IPv6 interfaces, but not many good transition guides, and fewer that address what the change can really mean to an application - Condor takes addresses and passes them as ascii text between components. <br />
|Kezhong Liang<br />
|Fedora<br />
<br />
|-<br />
|[[Corresponding Source Web App]]<br />
|Finish design and implement web application that provides downloadable SRPMS for any package+tag in the Fedora Package Source Code Control system. While we provide SRPMS for all packages at release, the updates and rawhide trees churn their packages more rapidly, and will remove the koji-built SRPMS when the binary packages are removed. This would allow people to request source corresponding to the packages they have on ISO media or otherwise.<br />
|Patricia Constantino<br />
|Fedora<br />
<br />
|-<br />
|[[Thunderbird Draft Scheduler Extension ]]<br />
|Write an extension for Thunderbird so that the user has the ability to mark a draft email for sending later. This is not the same as having to save emails in your DRAFT box because users would have to remember to go back in and click Send later. What is different here is that users could set the date and time for each email to be sent. <br />
|[[User:jevangel|James Evangelista]]<br />
|Thunderbird<br />
<br />
|-<br />
|[[Creating an MDRK spin]]<br />
|The [[Mozilla Developer Resource Kit]] is a set of tools, code, and documentation intended to make it easy for new Mozilla developers to get up to speed. Package the MDRK components (including the software tools, a Moz source tree, and documentation) as RPM packages and then create a Fedora "spin" (Live + Installable DVD) of these packages.<br />
<br />
Edit the spin image (from Revisor/Live CD Tools) so that, in addition to being a bootable/installable disc, the image can be run in a VM under Windows/Mac OSX. The disc image must be edited to include Windows/Mac OSX versions of the tools, so that if the disc is inserted into a running Windows or Mac OSX system, the appropriate version can be installed.<br />
|[[User:vyas|Mohak vyas]]<br />
|Fedora/Mozilla<br />
<br />
|-<br />
|[[Canvas3D XUL Runner App]]<br />
|Installing a test version of Canvas3D has been a logistical nightmare. This project aims to create a XUL Runner version of the Canvas3D extension which will be easy to download and run, and can update itself as the project progresses.<br />
|[[User:Vesper|Leonard Lee]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Canvas3D JS Library]]<br />
|A project to add JS APIs on top of the canvas3d element in order to support 3D and game development.<br />
|[[User:Catherine.leung|Cathy Leung]]<br />
|Mozilla<br />
<br />
|-<br />
|[[C3DL Collision Detection]]<br />
|Adding the collision detection ability to C3DL<br />
|[[User:Pplam3|Patrick Lam]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Mozilla Developer Resource Kit]]<br />
|A project to create a resource kit (i.e., DVDs) containing the tools, documentation, source code, and learning materials necessary for a new developer or student to begin developing Mozilla. <br />
|[[User:David.humphrey|David Humphrey]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Create Local MXR]]<br />
|Many developers without highspeed network access would like to be able to use [http://mxr.mozilla.org MXR] but can't. Build a lightweight, installable Windows package that gives the full functionality of MXR locally. Create a [http://labs.mozilla.com/featured-projects/#prism Prism] front-end specific for the task of using this local MXR.<br />
|[[User:David.humphrey|David Humphrey]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Add an Infobar style warning for window resize/move]]<br />
|Many (poorly behaved) web sites attempt to move and/or resize your browser window. It is possible to stop this behaviour (cf. dom.disable_window_move_resize) but it would be nice to have an infobar that informed the user that a web page attempted to move/resize the window, and allow it or ignore it (default). This behaviour is similar to the current Pop-up Blocker already present in Firefox. NOTE: it is not clear whether such a feature would be accepted in the tree or if this would need to be done as an extension. <br />
|[[User:Twlai1|Tony Lai]]<br />
|Mozilla<br />
<br />
|-<br />
|[http://zenit.senecac.on.ca/wiki/index.php/Contribute_to_Private_Browsing_Tests Contribute to Private Browsing Tests]<br />
|The new Private Browsing feature (see [https://bugzilla.mozilla.org/show_bug.cgi?id=248970 bug 248970] and the [https://wiki.mozilla.org/User:Ehsan/PrivateBrowsingTests test plan]) needs thorough tests written in order to insure its proper functionality. This will involve collaborating with those writing the patch and tests in order to develop a full suite of tests.<br />
<br />
|[[User:AaronMT|Aaron Train]]<br />
|Mozilla<br />
<br />
|-<br />
|[http://zenit.senecac.on.ca/wiki/index.php/Thunderbird_Image_Auto-Resize Thunderbird Image Auto-Resize]<br />
|Write an extension for Thunderbird that gives functionality similar to that of Outlook, where image attachments in an email can be automatically re-sized to one of a set of smaller sizes. This is helpful for users who would otherwise try to send megabytes of image data, when they can safely scale the images down and still share their pictures with friends.<br />
<br />
References: #maildev<br />
<br />
|[[User:zghansar|Zaid Ghansar]]<br />
|Thunderbird<br />
<br />
|-<br />
|[[NetworkManager Web Authentication]]<br />
|NetworkManager knows how to connect to many different types of networks, both wired and wireless, and can auto-authenticate to WEP and WPA networks. However, it can't auto-authenticate to networks that require a web-based login, which includes many wired and wireless networks such as SeneNET and AirYork.<br />
<br />
Modify NetworkManager so that it talks (though dbus) to a Firefox extension for automatic login to a web-authenticated network.<br />
<br />
Resources: ctyler, (roc, callion for dbus) <br />
|[[user:jtarka|Jason Tarka]]<br />
|Fedora/Mozilla(?)<br />
<br />
|-<br />
<br />
|-<br />
|[[Make Ubiquity Work In Thunderbird]]<br />
|Ubiquity is a cool extensible natural language front-end to Firefox. It could do wonders in Thunderbird as well. Aza Raskin and other Ubiquity hackers are happy to help someone do that with their Ubiquity knowledge, and #maildev will be happy to assist w/ Thunderbird knowledge.<br />
<br />
Resources: aza, ubiquity-firefox mailing list) <br />
|[[user:Scott|Scott Lunel]] and [[user:Tjbro|Thomas Brown]]<br />
|Thunderbird<br />
<br />
|-<br />
<br />
|-<br />
|[[User:Ashughes/BirdTorrent|Add Bit Torrent support to Songbird]]<br />
|[http://getsongbird.com Songbird] is the best music player in the known universe! Unfortunately, it does not have support for importing media directly from a torrent to the user library. This project will provide that support.<br />
<br />
Resources: stevel, mook, mfinkle, preed, mossop, [http://developer.mozilla.org Mozilla Developer Center], [http://developer.songbirdnest.com Songbird Developer Center] ) <br />
|[[user:ashughes|Anthony Hughes]]<br />
|Songbird<br />
<br />
|-<br />
<br />
|-<br />
|[[User:Jamesboston/nsIProcess|Fix nsIProcess]]<br />
|Create a new spec for the nsIProcess API and implement interprocess commmunication. The current API is not fully implemented and lacks ipc.<br />
<br />
See this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=442393<br />
<br />
Resources: humph, bsmedberg<br />
<br />
|[[User:Jamesboston|James Boston]]<br />
|Mozilla<br />
|-<br />
<br />
|-<br />
|[[Import sqlite test suite]]<br />
|Mozilla uses an embedded version of SQLite extensively to store data such as bookmarks, history, etc. To insure that it runs properly within Mozilla, it would be good to add the entire sqlite test suite to Mozilla's tests, so that testing the browser also means testing sqlite. The sqlite test suite is written in TCL and needs to be ported to JavaScript. Some work has already been done, but more is required to get full test coverage. <br />
<br />
Resources: sdwilsh) <br />
|[[user:kwpark1|Park, KiWon]]<br />
|Mozilla<br />
<br />
|-<br />
<br />
|-<br />
|[[Colour Management Tests]]<br />
|Write [http://developer.mozilla.org/en/docs/Creating_reftest-based_unit_tests reftests] to compare images in order to deal with floating point tolerance. This includes dealing with things like Monitor Profiles, profiles in JPEG (i.e., JPEGs get changed based on colour profile info). See discussion of colour profiles in Firefox 3 [http://www.dria.org/wordpress/archives/2008/04/29/633/ here]. It would be useful to be able to compare to PNGs with a reftest, perhaps creating an image diff tool, where pixels outside a floating point tolerance (> 0.n) would somehow be highlighted so you can see what is different. <strike>Little CMS (lcms) needs test coverage too.</strike> Done.<br />
<br />
This will require some graphics and image knowledge (i.e., Photoshop, what colour is on a computer, etc).<br />
<br />
Resources: #gfx, joe, vlad, bholley, [http://bholley.wordpress.com/2008/09/12/so-many-colors/ discussion of Mozilla colour profiles <br />
|[[user:Evmarbella|Ezadkiel Villarico Marbella]]<br />
|Mozilla<br />
<br />
|-<br />
<br />
|-<br />
|[[Bugzilla Unit Tests Using Test::More]]<br />
|Add unit tests using Test::More for every method in every object in Bugzilla. <br />
|[[User:felis|Irina Sh.]]<br />
|Bugzilla<br />
<br />
|-<br />
<br />
|-<br />
|[[Adding_tel_support_for_Windows_Mobile]]<br />
| Adding the ability to click on tel: links in Fennec on Windows Mobile and having the dialer dialog popup allowing you to call that number.<br />
|[[User:nadavers|Nino D'Aversa]]<br />
|Mozilla<br />
<br />
|-<br />
<br />
|-<br />
|[[Add_GPS_Support_for_Windows_Mobile]]<br />
| Add GPS Support to Fennec on Windows Mobile.<br />
|[[User:nadavers|Nino D'Aversa]]<br />
|Mozilla<br />
<br />
|-<br />
| [[Package JBoss]]<br />
|JBoss is a Java middleware project with a large number of sub projects. Packaging JBoss and maintaining them is a challenging task and would require several weeks of full time work. Since OpenJDK and a number of Java components is already in Fedora 9, it should help get started.<br />
|[[User:John64|John Ford]]<br />
|Fedora/JBoss<br />
<br />
|-<br />
|[[Per-Site/Per-Tab User-Agent Modification]]<br />
|Create an extension that lets a web developer modify the User-Agent string on a persistent per-site, per-tab basis. There's already a user-agent-switcher in the FF-addons (https://addons.mozilla.org/en-US/firefox/addon/59) but it doesn't isolate the user agent per site or per tab. Strong features might include a separation of the browser identification and language support, optional persistence across browsing sessions and a UI that by default hides the UA string behind the name/version of the browser it represents. See this discussion of the UA's history. <br />
|[[User:johpan|Johann Manzano]]<br />
|Mozilla<br />
<br />
<br />
|-<br />
|[[Func - Users And Groups Module]]<br />
|Func is a network applications framework that allows for powerful remote manipulation and scripting of very large numbers of Fedora machines. This idea is to expand Func by writing lots of useful modules to do all sorts of powerful remote things, making it into the world's best API for remote scripting Fedora over lots of machines at once -- with an emphasis on integrating Func with other tools we already have in Fedora. This would be a particular good project for someone who had an interest in networking, clusters, automation, or security related topics. Contributions to Func wouldn't be limited to just writing modules, as anything networking/automation related is fair game. <br />
<br />
This entry is for the subset of the project relating to the creation of a module to allow the management of users and groups.<br />
|[[User:bombshelter13|Gregory Masseau]]<br />
|Fedora<br />
<br />
|-<br />
|[[Func/Rpms Module - Function Verify]]<br />
|Func is a network applications framework that allows for powerful remote manipulation and scripting of very large numbers of Fedora machines. This idea is to expand Func by writing lots of useful modules to do all sorts of powerful remote things, making it into the world's best API for remote scripting Fedora over lots of machines at once -- with an emphasis on integrating Func with other tools we already have in Fedora. This would be a particular good project for someone who had an interest in networking, clusters, automation, or security related topics. Contributions to Func wouldn't be limited to just writing modules, as anything networking/automation related is fair game. <br />
|[[User:Milton.paiva|Milton Paiva]]<br />
|Fedora<br />
<br />
<br />
|-<br />
|[[Mercurial history browsing ]]<br />
|We're just starting to use an exciting new distributed version control tool: Mercurial.One of the exciting things about Mercurial is that the history—the list of all the changes that have ever been checked in—is not linear. It frequently has branches and merges. This is actually a good, important feature, as you know if you've read a little about distributed version control. The downside is that the history becomes a maze of twisty little passages. Benjamin Smedberg's demo shows the history of a repository with lots of merges (each box is a check-in; you can click on the boxes to move around).There have been a couple attempts at showing history in an intuitive, graphical way. Mercurial comes with a web UI for browsing the repository, including history (here's what it looks like). It also comes with an "hg glog" extension that draws history as ASCII art, and an "hg view" extension that does roughly the same thing with a little GUI. Sadly, none of these applications qualifies as awesome.Your mission is to rectify this sad situation by writing an awesome browser-based UI for navigating Mercurial repository history. <br />
|[[User:Crulshorukh|Siddharth Kalra]]<br />
|Mozilla<br />
<br />
|-<br />
|[[ PGO Related Bugs ]]<br />
|On Windows, Mozilla has begun using profile-guided optimization to make execution of the browser faster (i.e., you run your binary and see how it is likely to run, and optimize for those code paths). Currently, there are parts of the Mozilla source code that have bugs or crash when run in PGO builds. This project will mean trying to isolate these bugs by doing PGO builds of these components, creating test cases, debugging, and hopefully fixing things.<br />
<br />
Resources: ted, sdwilsh, and others based on component. <br />
|[[User:cbishop2|Chris Bishop]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Implementing an Archive Method for Auto-saving Mail]]<br />
|(Bug 451995) Currently in Thunderbird, there is no way to archive emails. This project will implement an archive method to save messages so that they are available for searching and other uses but are no longer visible in the users Inbox. Instead they will be moved to a archived folder.<br />
|[[User:Bbarcick|Bartosz Barcicki]]<br />
|Thunderbird<br />
<br />
|-<br />
|[[XUL Application Packaging]]<br />
|Help to develop an automated packaging system for XULRunner applications.<br />
<br />
Resources: plasticmillion, mfinkle, #mozpad, #prism <br />
|[[User:jsdoodna|Joshua Doodnauth]]<br />
|Mozilla<br />
<br />
|-<br />
|<br />
|[[Add DTrace Probes and scripts for Mozilla Code base]]<br />
DTrace was created by Sun in OpenSolaris to allow developers to write simple scripts in order to probe and instrument executing programs in a way not possible otherwise. One of the advantages of DTrace is that it allows you to turn on probing when you need it, but not incur an execution penalty with regard to performance (i.e., when probes aren't being scripted, they aren't run). This requires developers to add "probes" to their source code. For example, if you wanted to know when a particular function is entered/exited, get info about what happened, etc. you could add probes to the particular function. Writing the probes is not difficult, however there are hundreds or thousands of probes that Mozilla would like across its code base. <br />
<br />
Resources: sayrer<br />
|[[User:Hellwolf36|Chris Cameirao]]<br />
|Mozilla<br />
<br />
|-<br />
|[[ Finish Weave/Thunderbird integration ]]<br />
|[https://wiki.mozilla.org/Labs/Weave Weave] is Mozilla's services project. It currently allows different Firefox installations to synchronize bookmarks, etc. We'd like Thunderbird to be a full-fledged Weave client as well. Some [??? work has already been done], but more is required to get utility. Possible scenarios include:<br />
* thunderbird accounts synchronized (configure once, use everywhere)<br />
* automatic bookmarking in Firefox of URLs sent to/from friends<br />
* access to Thunderbird address book from Firefox <br />
References: [https://bugzilla.mozilla.org/show_bug.cgi?id=446444 bug 446444]<br />
Resources: dmose <br />
|[[User:cdpatel1|Chinmay Patel]]<br />
|Thunderbird<br />
<br />
|- <br />
|[[Create Content Security Policy test suite]]<br />
| <br />
Adding Content Restrictions functionality to Firefox means that sites could restrict types of locations for loaded scripts and other unsafe content. The Content Security Policy is intended to mitigate a large class of Web Application Vulnerabilities: Cross Site Scripting. In order for this to be written properly, a full test suite is required, which can test such things as inline scripts, javascript URLs, all event handler attributes (onclick, etc), plugins, frames, data urls, and XBL.<br />
<br />
References: http://people.mozilla.org/~bsterne/content-security-policy/, bug 411791, bug 390910<br />
<br />
Resources: bsterne, dveditz, shaver <br />
|[[User: ptmahent| Piratheep Mahenthiran]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Func - Yumcmd Module]]<br />
|Func is a network applications framework that allows for powerful remote manipulation and scripting of very large numbers of Fedora machines. This idea is to expand Func by writing lots of useful modules to do all sorts of powerful remote things, making it into the world's best API for remote scripting Fedora over lots of machines at once -- with an emphasis on integrating Func with other tools we already have in Fedora. This would be a particular good project for someone who had an interest in networking, clusters, automation, or security related topics. Contributions to Func wouldn't be limited to just writing modules, as anything networking/automation related is fair game. <br />
|[[User:vsjhand| Varinder Singh]]<br />
|Fedora<br />
<br />
|-<br />
|[[ Wubi port to Fedora ]]<br />
|The Windows Ubuntu Installer: Wubi make trying out Ubuntu Linux as easy as possible. Unlike a regular dual-boot configuration, Wubi doesn't require users to create a partition on their hard drives for Ubuntu. When Ubuntu is installed with Wubi, it can be uninstalled directly from the Add/Remove Programs utility in Windows. This project is to have a Wubi style install for Fedora. <br />
|[[ lsdaly | Louis Daly ]]<br />
|Fedora/Ubuntu<br />
<br />
|-<br />
|[[ Apport port to Fedora ]]<br />
|Apport is a bug-reporting tool for Ubuntu. When a program crashes, it catches information about the program and what happened, and then sends that information off to the developers, so that they can (hopefully) fix the problem. This would be a useful thing to have in Fedora, since it would help developers gather information about bugs, and it allows users to have a simple, user-friendly way to contribute bug reports and whatnot. <br />
|[[ evets | Stephen Carter ]]<br />
|Fedora/Ubuntu<br />
<br />
|-<br />
|[[ Manage downloads to Temp Directory ]]<br />
|Often files downloaded by the browser are put in a temporary folder that is emptied on close. Users (and especially novice users) should be protected from inadvertent data loss as a result of important files being saved to this temp folder. This project will add fixes to the browser so that users are protected.<br />
<br />
|[[ CeeJay | Clifton Fernandes ]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Spellcheck Extension for Arbitrary Web Pages]]<br />
|Write an extension to leverage the existing spellcheck code in Mozilla and add the ability to highlight spelling mistakes for a given web page (i.e., vs. a textbox).<br />
|[[User:ajhooper|Aaron Hooper]]<br />
|Mozilla<br />
<br />
|-<br />
|[[Add Source Server Support for Mercurial ]]<br />
|Previously we added [[Mozilla Source and Symbol Server|source indexing to release builds]] using CVS as a backend for pulling source files. Since then, Mozilla has moved to Mercurial from CVS. This project will add support so that Mercurial can be used too. See [https://bugzilla.mozilla.org/show_bug.cgi?id=440001 bug# 440001]. <br />
|[[User:JesseV|Jesse Valianes]]<br />
|Mozilla<br />
<br />
|-<br />
|[[HTML page set sanitizer]]<br />
|The Talos performance testing system at Mozilla currently runs on a large set of web pages pulled from the Alexa Top 500. These pages can't be redistributed, since they're mirrors of copyrighted web pages. In addition, many of them contain adult content. This makes it difficult for people to duplicate the Talos results or to test changes that have an expected performance impact.<br />
|[[User:cricket69|Neil David]]<br />
|Mozilla<br />
|<br />
<br />
|-<br />
|[[Mozilla BuildBot Trending]]<br />
|Currently, it is very difficult to figure out how much time is being spent in each part of the build system. Very high level tasks are timed, like checkout, build, test, but individual steps aren't being timed. For DPS911, this project will aim to create a local buildbot environment, patch buildbot to insert granular timestamps into logs, design a database for timing information and write a log parser to insert data into the database. During Summer 2009 a system to display trending information will be completed as well as historical view for buildbot.<br />
|[[User:John64|John Ford]]<br />
|Mozilla<br />
|<br />
<br />
<!--<br />
|-<br />
|[[Update Condor Build System]]<br />
|At the foundation of many good applications is its build infrastructure. The latest generation of tools includes GNU make with a very powerful interpreted language and ever increasing functionality in autotools. Condor has a build system from a few generations back. It uses imake, originally designed for building X. While new systems are more powerful and provide enhanced functionality, there isn't always a clear mapping to features of older systems. Don't only find a way to use newer tools to build Condor, but find a way to use the power of current generation tools in ways that aren't just a straight mapping of need satisfied by older systems.<br />
|[[User:pdirezze|Paul DiRezze]]<br />
|Fedora<br />
--><br />
<br />
|-<br />
|[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Fix_Mousewheel_Jump_in_Calc Fix Mousewheel Jump in Calc]<br />
| '''Mouse Wheel behavior:''' Each mouse wheel stroke makes the cursor move one cell back or forth. The desired behavior is to move one line at a time (in edit mode of a cell) instead of one cell at a time. <br />
'''Down Arrow Key Behavior:''' If the cursor is at the bottom of the page and there are still lines ahead of cursor in the cell which are not seen, pressing the down key on the keyboard will take the cursor out of the page and lets you edit lines without seeing them. The desired behavior is to shift the cell content upward so that each time you press the down key one line is appeared from the bottom and one line becomes hidden from the top, so that this prevents you from editing unseen content of the cell. <br />
<br />
|[[User:Lzahir|Ladan Zahiroleslam Zadeh]]<br />
|OpenOffice.org<br />
|<br />
<br />
|-<br />
|[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles Improve Impress/Attach Impress Animations to Styles]<br />
| <br />
* discover how are managed styles in the code<br />
* define a design for the impress one<br />
* implement a proof of concept<br />
* improve<br />
|[[User:dmoon4|Daeseon Moon]]<br />
|OpenOffice.org<br />
|}<br />
<br />
== Historical Projects ==<br />
<br />
See the [[Historical Projects]] page for projects which were previously active.</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Winter_2009_Open_Source_Students&diff=24460Winter 2009 Open Source Students2009-03-13T02:18:53Z<p>Dmoon4: /* Students */</p>
<hr />
<div>Please add a all relevant personal/project info below in the provided table:<br />
<br />
= Professors =<br />
<br />
* [[User:David.humphrey|David Humphrey (humph)]]<br />
* [[User:fardad|Fardad Soleimanloo (fardad)]]<br />
* [[User:JAnastasiade|Jordan Anastasiade (_jordan)]]<br />
<br />
= Students =<br />
<br />
{| class="wikitable sortable" border="1" cellpadding="2"<br />
! Name !! IRC Nick(s) !! Project(s) !! Course<br />
|- <br />
| [[User:achan66|Aaron Chan]] || achan66 || OO.o - B - To De Decided || OSD600<br />
|- <br />
| [[User:arbraini|Andrew Braini]] || aBraini || OO.o - A - To De Decided || DPS909<br />
|- <br />
| [[User:ashughes|Anthony Hughes]] || ashughes || [http://zenit.senecac.on.ca/wiki/index.php/User:Ashughes/BirdTorrent Birdtorrent] || DPS911<br />
|- <br />
| [[User:cdpatel1|Chinmay Patel]] || chinmay|| To De Decided || DPS911<br />
|-<br />
| [[User:Wfred|Fred Wang]] || WFred || OO.o - [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Document_Impress_Code Understand the Impress application (6)] || DPS909<br />
|-<br />
| [[User:Jatinder.singh|Jatinder Singh]] || Jatinder || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=203257#c0 Bug 203257], Severity - Normal, Priority - P2 || DPS909<br />
|-<br />
| [[User:Jtpau|Jerry Pau]] || jPau || OO.o || OSD600<br />
|-<br />
| [[User:heyqule|Jian Feng Allen Xie]] || heyqule || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=218101 Bug 218101], Normal, P3 || OSD600<br />
|-<br />
| [[User:John Dang|John Dang]] || JohnDang || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=255894 Bug 255894], Normal, P3 || DPS909<br />
|-<br />
| [[User:John64 | John Ford]] || John64 || Something from [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=mozilla.org&component=Release+Engineering%3A+Future&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= here] || DPS911<br />
|-<br />
| [[User:Jsdoodna| Joshua Doodnauth]] || Jsdoodna|| [[XUL Application Packaging]] || DPS911<br />
|-<br />
| [[User:jrgoncal| Justin Goncalves]] || jrgoncal || To be decided || DPS909<br />
|-<br />
| [[User:Khanh.Vu|Khanh Vu]] || kevinvu || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=240698 Bug 240698], Normal, P3 || OSD600<br />
|-<br />
|-<br />
| [[User:lyang42|Le Yang]] || lyang42 || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=243799 Bug 243799], Normal, P3|| OSD600<br />
|-<br />
| [[User:Vesper | Leonard Lee]] || Vesper || [[Canvas3D_XUL_Runner_App|Portable Canvas]] || DPS911<br />
|-<br />
| [[User:nadavers| Nino D'Aversa]] || ndaversa|| Add GPS and Camera Support to Fennec (link to be added later) || DPS911<br />
|-<br />
| [[User:Pplam3|Patrick Lam]] || Patrick_PC_Lam|| [http://zenit.senecac.on.ca/wiki/index.php/C3DL_Collision_Detection C3DL Collision Detection] || OSD700<br />
|-<br />
| [[User:rmwang|Ryan Wang]] || rmwang || OOo - B - To be decided || DPS909<br />
|-<br />
| [[User:Crulshorukh|Sid Kalra]] || Sid|| [http://zenit.senecac.on.ca/wiki/index.php/Mercurial_history_browsing/ Mercurial History Browsing] || <br />
|-<br />
| [[User:Twlai1 | Tony Lai]] || TonyLai|| [http://zenit.senecac.on.ca/wiki/index.php/Add_an_Infobar_style_warning_for_window_resize/move Add an Infobar Style Warning for Window Resize] || OSD700<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] || daeseon || OOo - [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles Improve Impress/Attach Impress Animations to Styles] || OSD600<br />
|-<br />
| [[User:JesseV|Jesse Valianes]] || JesseV || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209289 Bug #209289] || DPS911<br />
|-<br />
| [[User:Lzahir|Ladan Zahiroleslam]] || l_zahir || OO.o -[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Fix_Mousewheel_Jump_in_Calc 4.4 Fix MouseWheel jump in Calc]|| OSD600<br />
|-<br />
| [[User:Evmarbella| Ezadkiel Villarico Marbella]] || ezadkiel_ || [[nsIdleService tests fail on maemo]] [[Pause image animation when system idle.]] || DPS911<br />
|-<br />
| [[User:Minicheong|Frankie Law]] || Mini_Cheong || OOo - A -_To be decided || OSD600<br />
|-<br />
| [[User:nkhan26|Nabeel Khan]] || nkhan26 || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=227760 Bug 227760], Normal, P3 || DPS909<br />
|-<br />
| [[User:Bbarcick|Bartosz Barcicki]] || BartB || OOo - A -_To be decided || DPS909<br />
|-<br />
| [[User:ShelleyShi|Shelley Shi]] || shelley || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=137822 Bug 137822]|| OSD600<br />
|-<br />
| [[User:tlo5|Tommy Lo]] || Tlo || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=236404 Bug 236404], Normal, P3 || DPS909<br />
|-<br />
| [[User:Tiago|Tiago Moreira]] || Kamots || OOo - C - To be decided || DPS909<br />
|-<br />
| [[User:Pliu|Peter Liu]] || pliu || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=256185 Bug 256185], Normal, P3 || OSD600/DPS909<br />
|-<br />
| [[User:Tahereh|Tahereh Salimi]] || tsalimi || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244862 Bug 244862], Normal, P3 || DPS909<br />
|-<br />
| [[User:cbishop2|Chris Bishop]] || chrisBee || WTP ... to be decided || OSD700<br />
|-<br />
| [[User:Davoud|Davoud Salahi Rad]] || davoud || WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168784 Bug 168784], Normal, P3 || DPS909<br />
|-<br />
| [[User:Farhad|Farhad Norouzi]] || Farhad|| WTP - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=240167 Bug 240167], Normal, P3 || DPS909 <br />
|-</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Project_List&diff=24145OOo Project List2009-02-26T17:20:54Z<p>Dmoon4: /* Taken Projects */</p>
<hr />
<div>==Open Office Projects for Seneca Students:==<br />
=== Available Projects ===<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Complete_feature_send_active_document_as (Seneca 1) Support of more mail clients for send active document as (click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Use_system_security_API (Seneca 2) Use system security API on Mac OS X ( click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Scanner_Use (Seneca 3) Improve Scanner Use (click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort#.28Seneca_4.29_Build_OOo_on_OpenSOlaris (Seneca 4) Build OOo on OpenSolaris]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/OpenGL_Transitions_Windows Impress 1 : (Seneca 5) complete the Windows port for 3D OpenGL transitions ( + write documentation ) ]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles Impress 4 : (Seneca 8) Attach Impress animations to styles https://bugzilla.novell.com/show_bug.cgi?id=380041 (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Create_Diagramming_Sidebar_Extension Impress 5 : (Seneca 9) Create a diagramming sidebar extension for OOo Draw/Impress (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Create_Visio_Import_Filter Impress 6 : (Seneca 10) Create a Visio import filter for Draw (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Add_Animation_Flash_Export_Impress Impress 7 : (Seneca 11) Add animation support to Impress Flash export (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Autocad_Vector_Import Impress 8 : (Seneca 12) Implement an AutoCAD vector import for OOo (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/PDF_Layout_Import_Other_Formats Impress 9 : (Seneca 13) Use PDF import's layout recognition for other vector formats (e.g. postscript, wmf/emf) (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/OpenGL_canvas_backend Impress 10 : (Seneca 14) OpenGL canvas backend (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Standalone_presentation_viewer Impress 11 : (Seneca 15) Standalone presentation viewer (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Additional_3D_Transitions Impress 12 : (Seneca 16) Implement additional 3D slideshow transitions (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Step_back_slideshow_effects Impress 13 : (Seneca 17) Step back slideshow effects (click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/PyUNOupgrade (Seneca 18) Upgrade Python to 2.6 (click me)]<br />
<br />
=== Taken Projects ===<br />
<table border="1"><br />
<tr><br />
<th>Project Link</th><th>Candidate Name</th><th>Date</th><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Math_baseline_alignment Implement Math Baseline Alignment (19)]</td><td>Ladan Zahiroleslam (l_zahir)</td><td>Feb 24, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Impress_Master_Copyable Make Impress master pages copyable https://bugzilla.novell.com/show_bug.cgi?id=380039 (7)]</td><td>Bartosz Barcicki (Bbarcick)</td><td>Feb 24, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Document_Impress_Code Understand the Impress application (6)]</td><td>Fred Wang (Wfred) & Ryan Wang (rmwang)</td><td>Feb 24, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort#.28Seneca_4.29_Build_OOo_on_OpenSOlaris (Seneca 4) Build OOo on OpenSolaris]</td><td>Tiago Moreira (Kamots)</td><td>Feb. 25, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/PyUNOupgrade (Seneca 18) Upgrade Python to 2.6 (click me)]</td><td>Andrew Braini (Arbraini)</td><td>Feb. 26, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles (seneca 8)Attach Impress animations to styles]</td><td>Daeseon Moon</td><td>Feb. 27, 2009</td><br />
</tr><br />
<br />
</table></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Project_List&diff=24144OOo Project List2009-02-26T17:19:59Z<p>Dmoon4: /* Taken Projects */</p>
<hr />
<div>==Open Office Projects for Seneca Students:==<br />
=== Available Projects ===<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Complete_feature_send_active_document_as (Seneca 1) Support of more mail clients for send active document as (click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Use_system_security_API (Seneca 2) Use system security API on Mac OS X ( click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Scanner_Use (Seneca 3) Improve Scanner Use (click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort#.28Seneca_4.29_Build_OOo_on_OpenSOlaris (Seneca 4) Build OOo on OpenSolaris]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/OpenGL_Transitions_Windows Impress 1 : (Seneca 5) complete the Windows port for 3D OpenGL transitions ( + write documentation ) ]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles Impress 4 : (Seneca 8) Attach Impress animations to styles https://bugzilla.novell.com/show_bug.cgi?id=380041 (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Create_Diagramming_Sidebar_Extension Impress 5 : (Seneca 9) Create a diagramming sidebar extension for OOo Draw/Impress (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Create_Visio_Import_Filter Impress 6 : (Seneca 10) Create a Visio import filter for Draw (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Add_Animation_Flash_Export_Impress Impress 7 : (Seneca 11) Add animation support to Impress Flash export (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Autocad_Vector_Import Impress 8 : (Seneca 12) Implement an AutoCAD vector import for OOo (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/PDF_Layout_Import_Other_Formats Impress 9 : (Seneca 13) Use PDF import's layout recognition for other vector formats (e.g. postscript, wmf/emf) (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/OpenGL_canvas_backend Impress 10 : (Seneca 14) OpenGL canvas backend (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Standalone_presentation_viewer Impress 11 : (Seneca 15) Standalone presentation viewer (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Additional_3D_Transitions Impress 12 : (Seneca 16) Implement additional 3D slideshow transitions (clickme)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Step_back_slideshow_effects Impress 13 : (Seneca 17) Step back slideshow effects (click me)]<br />
* [http://wiki.services.openoffice.org/wiki/Education_Project/Effort/PyUNOupgrade (Seneca 18) Upgrade Python to 2.6 (click me)]<br />
<br />
=== Taken Projects ===<br />
<table border="1"><br />
<tr><br />
<th>Project Link</th><th>Candidate Name</th><th>Date</th><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Math_baseline_alignment Implement Math Baseline Alignment (19)]</td><td>Ladan Zahiroleslam (l_zahir)</td><td>Feb 24, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Impress_Master_Copyable Make Impress master pages copyable https://bugzilla.novell.com/show_bug.cgi?id=380039 (7)]</td><td>Bartosz Barcicki (Bbarcick)</td><td>Feb 24, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Document_Impress_Code Understand the Impress application (6)]</td><td>Fred Wang (Wfred) & Ryan Wang (rmwang)</td><td>Feb 24, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort#.28Seneca_4.29_Build_OOo_on_OpenSOlaris (Seneca 4) Build OOo on OpenSolaris]</td><td>Tiago Moreira (Kamots)</td><td>Feb. 25, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/PyUNOupgrade (Seneca 18) Upgrade Python to 2.6 (click me)]</td><td>Andrew Braini (Arbraini)</td><td>Feb. 26, 2009</td><br />
</tr><br />
<tr><br />
<td>[http://wiki.services.openoffice.org/wiki/Education_Project/Effort/Improve_Impress/Attach_Impress_Animations_to_Styles (seneca 8)]</td><td>Daeseon Moon</td><td>Feb. 27, 2009</td><br />
</tr><br />
<br />
</table></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Hacking_procedure_on_Fedora&diff=23697Hacking procedure on Fedora2009-02-15T02:14:27Z<p>Dmoon4: /* Make a change */</p>
<hr />
<div>== Make a change ==<br />
For example, have a hack at vcl/source/window/menu.cxx (Menu::SetItemText); (near line 1821) I suggest manually applying this change:<br />
<pre><br />
- pData->aText = rStr;<br />
+ pData->aText = String(rStr).Reverse();<br />
</pre><br />
then save it<br />
<br />
== Rebuild your source ==<br />
== Installing ==<br />
* [[Installing]]<br />
== Run ==<br />
* your_installation_dir/program/soffice</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Hacking_procedure_on_Fedora&diff=23696Hacking procedure on Fedora2009-02-15T02:06:46Z<p>Dmoon4: New page: == Make a change ==</p>
<hr />
<div>== Make a change ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=23695DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-02-15T02:05:45Z<p>Dmoon4: /* Week 5 (Feb 9) Navigating the source code */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) Course introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using Wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common Editing tasks, History, Reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ DistCC]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc installation]], Managing and Building large source trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local Working Copy<br />
*** Typical read-only activities: Checkout, Update<br />
* Using Make to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) Make]<br />
* Building Large Open Source Projects from Source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control With Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install disstcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to complie localy and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
<br />
== Week 4 (Feb 2)Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or Submitting [http://qa.openoffice.org/issue_handling/basic_rules.html Rules]<br />
*** Only one problem per issue<br />
*** Summery (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaboratively Create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) Navigating the source code ==<br />
* Learning to be Lost Productively<br />
** Adding to Open Office is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org Source Code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers Guide]<br />
** OOo directory structure<br />
* Searching for Code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to Make Changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers Tutorials]<br />
* [[Hacking procedure on Fedora]]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** complete week 4 Todo<br />
** run, maka a change, build, run</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=DPS909_and_OSD600_Winter_2009_OpenOffice.org_Weekly_Schedule&diff=23693DPS909 and OSD600 Winter 2009 OpenOffice.org Weekly Schedule2009-02-15T01:36:24Z<p>Dmoon4: /* Week 5 (Feb 9) Navigating the source code */</p>
<hr />
<div>=Introduction=<br />
<br />
The course is broken into two parts. First, general open source and and community specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of the OpenOffice.org project and its community. Second, students are taught about extensibility models, and how to write Add-ons and Extensions.<br />
<br />
=Part I – Essential Open Source Development Skills and Concepts= <br />
<br />
<br />
== Week 1 (Jan 12) Course introduction ==<br />
<br />
* Course introduction<br />
* Intro to open source<br />
* Intro to the OpenOffice.org project<br />
** [[OpenOffice.org Overview]]<br />
** [http://www.openoffice.org/dev_docs/guidelines.html Becoming a contributor]<br />
** Sun, Community<br />
<br />
* '''Readings/Resources'''<br />
** [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/578/499 "Cathedral and Bazaar"] by Eric Raymond <br />
** [http://video.google.ca/videoplay?docid=7707585592627775409&q=open+source "Revolution OS"] [film] (see also http://www.revolution-os.com/ or QA 76.9.A25 R68 2003)<br />
<br />
* '''TODO'''<br />
** Create an '''account''' on this wiki for yourself<br />
** Create a '''personal wiki page''' on this wiki<br />
** Add a link for yourself to the [[People]] page and the [[Winter 2009 Open Source Students]] page<br />
** Create a '''blog''' ([http://wordpress.com/ WordPress] or [https://www.blogger.com/ Blogger] or whatever) and create a feed category or tag called "open source"<br />
** Read the [[Blog Guidelines]] for instructions on how to use your blog in the course<br />
** Add your '''blog feed''' and info to the [[Open Source@Seneca Planet List]] so that it appears in the [http://zenit.senecac.on.ca/~chris.tyler/planet OpenSource@Seneca Planet]<br />
** '''Blog''' on your reactions to the readings for this week.<br />
** Begin learning how to use [[Irc|IRC]] for communication. We'll cover this in detail next week, but it's better to get started early.<br />
<br />
== Week 2 (Jan 19) - Collaborative and Community Development Practices ==<br />
<br />
* Collaborative development using on-line tools<br />
* [[Irc|Intro to Internet Relay Chat (IRC)]] <br />
* [http://en.wikipedia.org/wiki/Blog Blogs] and [http://en.wikipedia.org/wiki/Planet_(blog) Planets]<br />
** [http://planet.go-oo.org/ Novell's OpenOffice.org Planet]<br />
** [http://planetopenoffice.org/ Planet OpenOffice.org]<br />
** [http://zenit.senecac.on.ca/~chris.tyler/planet/ OpenSource@Seneca Planet]<br />
* Using Wikis for collaborative writing<br />
** [http://www.wikipedia.org Wikipedia] and [http://www.mediawiki.org/ MediaWiki]<br />
** Intro to course wiki<br />
*** "Yes, you can edit it!"<br />
*** Common Editing tasks, History, Reverting changes<br />
*** Watches, [[Special:Recentchanges|Recent Changes]]<br />
*** Comparing selected versions (cf. diff)<br />
*** [http://en.wikipedia.org/wiki/How_to_edit How to Edit a page]<br />
** Wikis used by OpenOffice.org<br />
*** http://wiki.services.openoffice.org/wiki/Main_Page<br />
*** http://wiki.services.openoffice.org/wiki/Education_Project<br />
<br />
<br />
<br />
* '''Readings/Resources'''<br />
** [http://contributing.openoffice.org Participating in OpenOffice.Org]<br />
** [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html OpenOffice.Org Issues]<br />
** [http://wiki.services.openoffice.org/wiki/Education_ClassRoom OOo Education Classroom]<br />
** [http://svn.services.openoffice.org/ooo/ SVN OOo]<br />
** [http://www.owlnet.rice.edu/~comp314/svn.html Source Control in Ten Minutes: a Subversion tutorial]<br />
** [http://distcc.samba.org/ DistCC]<br />
<br />
<br />
* '''TODO'''<br />
** Ensure all TODO items from week 1 are '''completed'''<br />
** '''Comment''' in at least one other student's '''blog''' with your feedback to what they wrote. <b>Reminder: Comments have to be approved for them to be be shown on your blog. Check your blog settings.</b><br />
** Download the [http://www.openoffice.org/licenses/sca.pdf "Sun Microsystems Inc. Contributor Agreement (SCA)"] from [http://contributing.openoffice.org/programming.html OpenOffice.Org Programming], sign it and email it to Copyrightfax@sun.com and CC it to Fardad.<br />
** Subscribe to "dev AT education DOT openoffice DOT org" by sending an email to "dev-subscribe AT education DOT openoffice DOT org" and then confirming it by replying to the confirmation email.<br />
** Add this wiki page to your watch list.<br />
** Here is the [http://zenit.senecac.on.ca/wiki/index.php/CDOT_Development_Systems '''IP addresses''' of the CDOT continent] for you to log in to!<br />
** [[Distcc Setup|Setup distcc on assigned computers]]<br />
<br />
== Week 3 (Jan 26) - Complete [[Distcc Setup|distcc installation]], Managing and Building large source trees ==<br />
* Revision Control Systems (RCS)<br />
** Introduction to RCS<br />
** [http://en.wikipedia.org/wiki/Concurrent_Versions_System cvs], [http://en.wikipedia.org/wiki/Subversion_(software) svn], [http://en.wikipedia.org/wiki/Mercurial_(software) hg]<br />
** Common concepts and tasks<br />
*** Repository<br />
*** Local Working Copy<br />
*** Typical read-only activities: Checkout, Update<br />
* Using Make to build software<br />
** Intro to [http://en.wikipedia.org/wiki/Make_(software) Make]<br />
* Building Large Open Source Projects from Source<br />
<br />
<br />
* '''Readings/Resources (to be completed)'''<br />
** [http://svnbook.red-bean.com/ Version Control With Subversion (Online Book)]<br />
** [http://www.gnu.org/software/make/manual/make.html GNU Make]<br />
** Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples]<br />
**[http://wiki.services.openoffice.org/wiki/Cpp_Coding_Standards Cpp Coding Standards]<br />
**[http://wiki.services.openoffice.org/wiki/Writer_Code_Conventions Writer Code Conventions]<br />
<br />
<br />
<br />
* '''TODO (to be completed)'''<br />
** Install disstcc to work with all linux boxes at CDOT<br />
** Check out the code with latest milestone from svn://svn.services.openoffice.org/ooo/tags/DEV300_mXX and time it and blog about it.<br />
** Make two copies of the code and configure them; one to complie localy and other using distcc.<br />
** Start Building <br />
*** [[OOo Fedora Build]]<br />
*** [[OOo Mac Build]]<br />
*** [[OOo Windows Build]]<br />
<br />
<br />
== Week 4 (Feb 2)Building Open Office (Continued), Issues == <br />
* Build<br />
** Complete your build and update relative build wiki pages<br />
** If completed move to next platform (at least two)<br />
* [http://qa.openoffice.org/issue_handling/project_issues.html Issues] <br />
** Filing or Submitting [http://qa.openoffice.org/issue_handling/basic_rules.html Rules]<br />
*** Only one problem per issue<br />
*** Summery (recognizable, descriptive, meaningful)<br />
*** Able to recreate (step by step instructions)<br />
*** Providing samples <br />
*** Use attachments<br />
*** Avoid links, add relevant info. instead<br />
** [http://qa.openoffice.org/issue_handling/ Handling] and [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf "Life Cycle"]<br />
** [http://qa.openoffice.org/issues/query.cgi "Issue Tracker"] (a modified version of [https://bugzilla.mozilla.org/ Bugzilla])<br />
*Useful Links for Quality Assurance Testing (QAT/Reporting a Bug)<br />
** [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Priority Levels]<br />
** [http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html Bug Writing Guidelines]<br />
** [http://www.openoffice.org/scdocs/issue_lifecycle.html Issue Life cycle ]<br />
** [http://qa.openoffice.org/issue_handling/project_issues.html About Issues]<br />
* '''TODO'''<br />
** Complete the build at least on two platforms<br />
** Collaboratively Create and complete [[OOo Issues]] wiki page. A brief document from creating an issue to closing it.<br />
<br />
== Week 5 (Feb 9) Navigating the source code ==<br />
* Learning to be Lost Productively<br />
** Adding to Open Office is not like writing a program from scratch<br />
** Leverage the existing code by reading, studying, and copying existing code<br />
* OpenOffice.org Source Code structure and style<br />
** [http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.pdf Developers Guide]<br />
** OOo directory structure<br />
* Searching for Code<br />
** [http://svn.services.openoffice.org/opengrok/ {OpenGrok]<br />
* How to Make Changes<br />
** [http://wiki.services.openoffice.org/wiki/Building Building]<br />
** [[Installing]]<br />
** [http://wiki.services.openoffice.org/wiki/Hacking Hacking]<br />
** [http://wiki.services.openoffice.org/wiki/Tutorials Hackers Tutorials]<br />
<br />
<br />
* '''Resources'''<br />
** [http://kohei.us/ooo/ "Roundtrip to Shanghai via Tokyo!!!"]<br />
* '''TODO'''<br />
** complete week 4 Todo<br />
** run, maka a change, build, run</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Issues&diff=23598OOo Issues2009-02-12T04:08:11Z<p>Dmoon4: /* Issue Life Cycle */</p>
<hr />
<div>== Before Filing an Issue ==<br />
# Before you begin filing an issue, please do take a moment to check if there are existent issue already been reported.<br />
:: You may use the '''Issue Tracker Query''' http://www.openoffice.org/issues/query.cgi<br />
:: You may use the '''Advance Search''' http://www.openoffice.org/servlets/Search<br />
<br />
== Guideline to Filing an Issue (Important) ==<br />
* '''One problem - One issue'''<br />
:: Meaning, you are to ONLY file one problem at a time even if you found several problems in the same area.<br />
:: ''For example: I found several problems with the 'save as' option <br />
::: 1/ File name increment option does not increment, but rather decrement.<br />
::: 2/ The save button sometimes grayed out for no reason <br />
::: 3/ Obscure characters are allow to be enter as a file name ''<br />
:: This considered as 3 issues and should be file separately.<br />
<br />
<br />
* '''Provide a meaningful summary'''<br />
:: Be descriptive of your discovery to the problem and avoid using generalize statement(s) that may potentially mean a different thing.<br />
:: Generalizing the description will result your issue being ignore and review at later time.<br />
:: Remember, open office has a large library of source code to search through, providing a concise description will save the community members time.<br />
:: Some ideas what you can put in your description...<br />
::: ''Where did it happen?'', ''What trigger the event?'', ''What is the result?'', etc<br />
<br />
<br />
* '''Provide step-by-step descriptions'''<br />
:: This reinforces the guideline of providing a meaningful summary, software today are becoming more robust as programmer tries to implement additional features that perform the same job simply for the sake of convince for the end user. If you encountered a problem with font changing, please provide a step by step guide for the community the steps you took to generate that result.<br />
:: ''An example of a non-descriptive instruction: I try to apply bold text''<br />
:: ''An example of more descriptive instruction:<br />
::: 1/ Highlight the text in which you want to apply changes to.<br />
::: 2/ Open the edit menu.<br />
::: 3/ Select Font<br />
::: 4/ Check off the bold check box<br />
::: 5/ Press OK<br />
::: 6/ Crashes''<br />
<br />
# Provide sample documents, if possible<br />
# Use Attachments where possible<br />
# Put all relevant information into the issue<br />
<br />
== How to File an Issue ==<br />
# Create an account with OpenOffice.org at '''http://www.openoffice.org/'''<br />
::Once you logged in you will be in your '''My Start Page'''<br />
::Look at the left panel where it says '''My Tool''' and click on '''File Issue'''<br />
<br />
== Issue Life Cycle ==<br />
# Open state issues<br />
##UNCONFIRMED : This issue has recently been added. No one has validated that this issue is true. Users who have the "Project Issue Tracking - Change" permission set may confirm this issue, changing its state to '''NEW'''. or, it may be directly resolved and marked '''RESOLVED'''.<br />
##NEW : This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become '''STARTED''', passed on to someone else, and remain '''NEW''', or resolved and marked '''RESOLVED'''.<br />
##STARTED : This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become ''NEW'', or resolved and become ''RESOLVED''.<br />
##REOPENED : This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked '''STARTED''' or '''RESOLVED'''<br />
#Resolved state issues<br />
##RESOLVED : A resolution has been taken, and it is awaiting verification by QA. From here issues are either re-opened and become '''REOPENED''' are marked '''verified''' OR are closed for good and marked '''CLOSED'''.<br />
##VERIFIED : QA has looked at the issue and the resolution and agrees that the appropriate resolution has been taken. Issues remain in this state until the product they were reported against is actually released. at which point they become '''CLOSED'''.<br />
##CLOSED : The issue is considered dead. the resolution is correct. A closed issue can be reactivated by marking it '''REOPENED'''.</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Issues&diff=23597OOo Issues2009-02-12T04:02:29Z<p>Dmoon4: /* Issue Life Cycle */</p>
<hr />
<div>== Before Filing an Issue ==<br />
# Before you begin filing an issue, please do take a moment to check if there are existent issue already been reported.<br />
:: You may use the '''Issue Tracker Query''' http://www.openoffice.org/issues/query.cgi<br />
:: You may use the '''Advance Search''' http://www.openoffice.org/servlets/Search<br />
<br />
== Guideline to Filing an Issue (Important) ==<br />
* '''One problem - One issue'''<br />
:: Meaning, you are to ONLY file one problem at a time even if you found several problems in the same area.<br />
:: ''For example: I found several problems with the 'save as' option <br />
::: 1/ File name increment option does not increment, but rather decrement.<br />
::: 2/ The save button sometimes grayed out for no reason <br />
::: 3/ Obscure characters are allow to be enter as a file name ''<br />
:: This considered as 3 issues and should be file separately.<br />
<br />
<br />
* '''Provide a meaningful summary'''<br />
:: Be descriptive of your discovery to the problem and avoid using generalize statement(s) that may potentially mean a different thing.<br />
:: Generalizing the description will result your issue being ignore and review at later time.<br />
:: Remember, open office has a large library of source code to search through, providing a concise description will save the community members time.<br />
:: Some ideas what you can put in your description...<br />
::: ''Where did it happen?'', ''What trigger the event?'', ''What is the result?'', etc<br />
<br />
<br />
* '''Provide step-by-step descriptions'''<br />
:: This reinforces the guideline of providing a meaningful summary, software today are becoming more robust as programmer tries to implement additional features that perform the same job simply for the sake of convince for the end user. If you encountered a problem with font changing, please provide a step by step guide for the community the steps you took to generate that result.<br />
:: ''An example of a non-descriptive instruction: I try to apply bold text''<br />
:: ''An example of more descriptive instruction:<br />
::: 1/ Highlight the text in which you want to apply changes to.<br />
::: 2/ Open the edit menu.<br />
::: 3/ Select Font<br />
::: 4/ Check off the bold check box<br />
::: 5/ Press OK<br />
::: 6/ Crashes''<br />
<br />
# Provide sample documents, if possible<br />
# Use Attachments where possible<br />
# Put all relevant information into the issue<br />
<br />
== How to File an Issue ==<br />
# Create an account with OpenOffice.org at '''http://www.openoffice.org/'''<br />
::Once you logged in you will be in your '''My Start Page'''<br />
::Look at the left panel where it says '''My Tool''' and click on '''File Issue'''<br />
<br />
== Issue Life Cycle ==<br />
# Open state issues<br />
##UNCONFIRMED : This issue has recently been added. No one has validated that this issue is true. Users who have the "Project Issue Tracking - Change" permission set may confirm this issue, changing its state to '''NEW'''. or, it may be directly resolved and marked '''RESOLVED'''.<br />
##NEW : This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become '''STARTED''', passed on to someone else, and remain '''NEW''', or resolved and marked '''RESOLVED'''.<br />
##STARTED : This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become ''NEW'', or resolved and become ''RESOLVED''.<br />
##REOPENED : This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked '''STARTED''' or '''RESOLVED'''</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Issues&diff=23559OOo Issues2009-02-11T15:11:44Z<p>Dmoon4: /* Issue Life Cycle */</p>
<hr />
<div>== Before Filing an Issue ==<br />
# Before you begin filing an issue, please do take a moment to check if there are existent issue already been reported.<br />
:: You may use the '''Issue Tracker Query''' http://www.openoffice.org/issues/query.cgi<br />
:: You may use the '''Advance Search''' http://www.openoffice.org/servlets/Search<br />
<br />
== Guideline to Filing an Issue (Important) ==<br />
* '''One problem - One issue'''<br />
:: Meaning, you are to ONLY file one problem at a time even if you found several problems in the same area.<br />
:: ''For example: I found several problems with the 'save as' option <br />
::: 1/ File name increment option does not increment, but rather decrement.<br />
::: 2/ The save button sometimes grayed out for no reason <br />
::: 3/ Obscure characters are allow to be enter as a file name ''<br />
:: This considered as 3 issues and should be file separately.<br />
<br />
<br />
* '''Provide a meaningful summary'''<br />
:: Be descriptive of your discovery to the problem and avoid using generalize statement(s) that may potentially mean a different thing.<br />
:: Generalizing the description will result your issue being ignore and review at later time.<br />
:: Remember, open office has a large library of source code to search through, providing a concise description will save the community members time.<br />
:: Some ideas what you can put in your description...<br />
::: ''Where did it happen?'', ''What trigger the event?'', ''What is the result?'', etc<br />
<br />
<br />
* '''Provide step-by-step descriptions'''<br />
:: This reinforces the guideline of providing a meaningful summary, software today are becoming more robust as programmer tries to implement additional features that perform the same job simply for the sake of convince for the end user. If you encountered a problem with font changing, please provide a step by step guide for the community the steps you took to generate that result.<br />
:: ''An example of a non-descriptive instruction: I try to apply bold text''<br />
:: ''An example of more descriptive instruction:<br />
::: 1/ Highlight the text in which you want to apply changes to.<br />
::: 2/ Open the edit menu.<br />
::: 3/ Select Font<br />
::: 4/ Check off the bold check box<br />
::: 5/ Press OK<br />
::: 6/ Crashes''<br />
<br />
# Provide sample documents, if possible<br />
# Use Attachments where possible<br />
# Put all relevant information into the issue<br />
<br />
== How to File an Issue ==<br />
# Create an account with OpenOffice.org at '''http://www.openoffice.org/'''<br />
::Once you logged in you will be in your '''My Start Page'''<br />
::Look at the left panel where it says '''My Tool''' and click on '''File Issue'''<br />
<br />
== Issue Life Cycle ==<br />
# Open state issues<br />
##UNCONFIRMED : This issue has recently been added. No one has validated that this issue is true. Users who have the "Project Issue Tracking - Change" permission set may confirm this issue, changing its state to '''NEW'''. or, it may be directly resolved and marked '''RESOLVED'''.<br />
##NEW : This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become '''STARTED''', passed on to someone else, and remain '''NEW''', or resolved and marked '''RESOLVED'''.<br />
##STARTED : This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become ''NEW'', or resolved and become ''RESOLVED''.<br />
##REOPENED : This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked ''STARTED'' or ''RESOLVED''</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Issues&diff=23557OOo Issues2009-02-11T15:02:37Z<p>Dmoon4: </p>
<hr />
<div>== Before Filing an Issue ==<br />
# Before you begin filing an issue, please do take a moment to check if there are existent issue already been reported.<br />
:: You may use the '''Issue Tracker Query''' http://www.openoffice.org/issues/query.cgi<br />
:: You may use the '''Advance Search''' http://www.openoffice.org/servlets/Search<br />
<br />
== Guideline to Filing an Issue (Important) ==<br />
* '''One problem - One issue'''<br />
:: Meaning, you are to ONLY file one problem at a time even if you found several problems in the same area.<br />
:: ''For example: I found several problems with the 'save as' option <br />
::: 1/ File name increment option does not increment, but rather decrement.<br />
::: 2/ The save button sometimes grayed out for no reason <br />
::: 3/ Obscure characters are allow to be enter as a file name ''<br />
:: This considered as 3 issues and should be file separately.<br />
<br />
<br />
* '''Provide a meaningful summary'''<br />
:: Be descriptive of your discovery to the problem and avoid using generalize statement(s) that may potentially mean a different thing.<br />
:: Generalizing the description will result your issue being ignore and review at later time.<br />
:: Remember, open office has a large library of source code to search through, providing a concise description will save the community members time.<br />
:: Some ideas what you can put in your description...<br />
::: ''Where did it happen?'', ''What trigger the event?'', ''What is the result?'', etc<br />
<br />
<br />
* '''Provide step-by-step descriptions'''<br />
:: This reinforces the guideline of providing a meaningful summary, software today are becoming more robust as programmer tries to implement additional features that perform the same job simply for the sake of convince for the end user. If you encountered a problem with font changing, please provide a step by step guide for the community the steps you took to generate that result.<br />
:: ''An example of a non-descriptive instruction: I try to apply bold text''<br />
:: ''An example of more descriptive instruction:<br />
::: 1/ Highlight the text in which you want to apply changes to.<br />
::: 2/ Open the edit menu.<br />
::: 3/ Select Font<br />
::: 4/ Check off the bold check box<br />
::: 5/ Press OK<br />
::: 6/ Crashes''<br />
<br />
# Provide sample documents, if possible<br />
# Use Attachments where possible<br />
# Put all relevant information into the issue<br />
<br />
== How to File an Issue ==<br />
# Create an account with OpenOffice.org at '''http://www.openoffice.org/'''<br />
::Once you logged in you will be in your '''My Start Page'''<br />
::Look at the left panel where it says '''My Tool''' and click on '''File Issue'''<br />
<br />
== Issue Life Cycle ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23173OOo Mac Build2009-02-05T01:15:30Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || || Build Success<br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
<br />
== Build ==<br />
<pre><br />
build --all -P4<br />
</pre></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23172OOo Mac Build2009-02-05T01:10:46Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || || Build Success<br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
<br />
== Build ==<br />
<pre><br />
build --all -P4<br />
</pre></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23170OOo Mac Build2009-02-05T00:46:11Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
<br />
== Build ==<br />
<pre><br />
build --all -P4<br />
</pre></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23163OOo Mac Build2009-02-04T22:08:47Z<p>Dmoon4: /* Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US de fr" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
<br />
== Build ==<br />
<pre><br />
build --all -P4<br />
</pre></div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23162OOo Mac Build2009-02-04T22:08:40Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US de fr" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23161OOo Mac Build2009-02-04T22:08:13Z<p>Dmoon4: /* Bootstrapping */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US de fr" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
* Build<br />
<pre><br />
build --all -P4<br />
</pre><br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23160OOo Mac Build2009-02-04T22:08:07Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US de fr" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
<br />
* Build<br />
<pre><br />
build --all -P4<br />
</pre><br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23159OOo Mac Build2009-02-04T22:07:32Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
* Put mozilla prebuilt archives to src_root/moz/zipped/<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIinc.zip MAXOSXGCCIinc.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIlib.zip MACOSXGCCIlib.zip]<br />
** [http://eric.bachard.free.fr/mac/moz/seamonkey_Intel/MACOSXGCCIruntime.zip MAXOSXGCCIruntime.zip]<br />
* type "configure -options..." or create build.sh like what eric did<br />
<code><br />
#!/bin/sh<br />
export BASE=`pwd`<br />
export OOVERSION=`echo $BASE|sed 's/^\/.*\///'`<br />
echo Building from : $BASE<br />
echo OpenOffice Version: $OOVERSION<br />
./configure \<br />
--with-lang="en-US de fr" \<br />
--disable-odk \<br />
--disable-pasf \<br />
--disable-gtk \<br />
--disable-headless \<br />
--disable-build-mozilla \<br />
--with-build-version=$OOVERSION-`date +%d-%m-%y` \<br />
--disable-fontconfig \<br />
--without-nas \<br />
--with-use-shell=bash \<br />
--with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home \<br />
--with-stlport=no \<br />
--disable-mediawiki \<br />
--enable-werror \<br />
--disable-vba<br />
</code><br />
* If you create build.sh, then put this file ~/bin and give proper permission<br />
<pre><br />
mv build.sh ~/bin<br />
chmod ug+x ~/bin/build.sh<br />
ln -s ~/bin/build.sh your src_root(DEV300_m41)/build.sh<br />
</pre><br />
* execute build.sh<br />
* bootstrapping<br />
<pre><br />
./bootstrap<br />
source MacOSXX86Env.Set.sh<br />
cd instsetoo_native<br />
export TMP=/tmp<br />
export SYSTEM_OPENSSL=YES<br />
</pre><br />
* Build<br />
<pre><br />
build --all -P4<br />
</pre><br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23158OOo Mac Build2009-02-04T21:56:27Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* Apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<pre><br />
<br />
cp moz2seamonkey_connectivity.diff DEV300_m40<br />
cd DEV300_m40<br />
<br />
Fake the patch application :<br />
<br />
patch --dry-run -p0 < moz2seamonkey_connectivity.diff<br />
<br />
And if nothing wrong occurs, apply it for true :<br />
<br />
patch -p0 < moz2seamonkey_connectivity.diff<br />
<br />
</pre><br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23157OOo Mac Build2009-02-04T21:54:23Z<p>Dmoon4: /* Configuring The Source */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
* apply the following patch to your tree [http://eric.bachard.free.fr/mac/aquavcl/patches/aqua_November_2008/26th_november/moz2seamonkey_connectivity.diff patch for moz2seamonkey zipped archives]<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23156OOo Mac Build2009-02-04T21:53:14Z<p>Dmoon4: /* Setting C and C++ compilers */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
* Bash shell<br />
** Without ccache<br />
*** export CC=gcc<br />
*** export CXX=g++<br />
** With ccache<br />
*** export CC="ccache gcc"<br />
*** export CXX="ccache g++"<br />
<br />
== Configuring The Source ==<br />
<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23155OOo Mac Build2009-02-04T20:17:03Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
<br />
<br />
== Configuring The Source ==<br />
<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Mac_Build&diff=23154OOo Mac Build2009-02-04T20:16:47Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
* Who is working where?<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:dmoon4|Daeseon Moon]] (irc:Daeseon)|| Russia || building DEV41 || <br />
|}<br />
<br />
== Getting the Source ==<br />
[http://wiki.services.openoffice.org/wiki/AquaBuild OpenOffice Max OS X AquaBuild instructions]<br />
<br />
== Setting C and C++ compilers ==<br />
<br />
<br />
== Configuring The Source ==<br />
<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23122OOo Fedora Build2009-02-03T20:03:18Z<p>Dmoon4: /* Setting Distcc for OO build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it .'''Building again M40...'''trying to get it done with distcc || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic links in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
* Read this as well [http://tools.openoffice.org/dmake/dmake_4.3.html dmake Man Page]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''<br />
<br />
== Build Issue ==<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=91641 rhino fails to build with OpenJDK]<br />
*[http://qa.openoffice.org/issues/show_bug.cgi?id=84787 libnss3 patch]<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=97715 rpmbuild buildroot error]</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23121OOo Fedora Build2009-02-03T20:02:27Z<p>Dmoon4: /* Setting Distcc for OO build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it .'''Building again M40...'''trying to get it done with distcc || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic links in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
* [http://tools.openoffice.org/dmake/dmake_4.3.html dmake Man Page]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''<br />
<br />
== Build Issue ==<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=91641 rhino fails to build with OpenJDK]<br />
*[http://qa.openoffice.org/issues/show_bug.cgi?id=84787 libnss3 patch]<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=97715 rpmbuild buildroot error]</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23120OOo Fedora Build2009-02-03T19:53:19Z<p>Dmoon4: /* Build issue */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it .'''Building again M40...'''trying to get it done with distcc || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic link in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
* [http://tools.openoffice.org/dmake/dmake_4.3.html dmake Man Page]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''<br />
<br />
== Build Issue ==<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=91641 rhino fails to build with OpenJDK]<br />
*[http://qa.openoffice.org/issues/show_bug.cgi?id=84787 libnss3 patch]<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=97715 rpmbuild buildroot error]</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23119OOo Fedora Build2009-02-03T19:48:49Z<p>Dmoon4: /* Build issue */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it .'''Building again M40...'''trying to get it done with distcc || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic link in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
* [http://tools.openoffice.org/dmake/dmake_4.3.html dmake Man Page]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''<br />
<br />
== Build issue ==<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=91641 rhino fails to build with OpenJDK]<br />
*[http://qa.openoffice.org/issues/show_bug.cgi?id=84787 libnss3 patch]<br />
*[http://www.openoffice.org/issues/show_bug.cgi?id=97715 rpmbuild buildroot error]</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23118OOo Fedora Build2009-02-03T19:31:28Z<p>Dmoon4: /* Setting Distcc for OO build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it .'''Building again M40...'''trying to get it done with distcc || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic link in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
* [http://tools.openoffice.org/dmake/dmake_4.3.html dmake Man Page]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''<br />
<br />
== Build issue ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23117OOo Fedora Build2009-02-03T19:29:55Z<p>Dmoon4: </p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it .'''Building again M40...'''trying to get it done with distcc || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic link in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''<br />
<br />
== Build issue ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23107OOo Fedora Build2009-02-03T17:27:01Z<p>Dmoon4: /* Setting Distcc for OO */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it . || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO build ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic link in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=23106OOo Fedora Build2009-02-03T17:26:47Z<p>Dmoon4: </p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) Aaron (irc:achan66)|| Australia || building DEV40 || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it . || Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Setting Distcc for OO ==<br />
* Create directory "/usr/lib/distcc/bin"<br />
* Make symbolic link in the directory<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/g++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/c++<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/cc<br />
** ln -s /usr/bin/distcc /usr/lib/distcc/bin/gcc<br />
* Add the directory at the first of your PATH environment variable<br />
** export PATH=/usr/lib/distcc/bin:$PATH<br />
* After configuration is done, add MAXPROCESS in environment variable<br />
** export MAXPROCESS=8<br />
* Execute dmake with option "-E"<br />
** dmake -E<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=22981OOo Fedora Build2009-02-02T01:37:52Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) || Australia || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success</b> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it|| Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=22980OOo Fedora Build2009-02-02T01:37:39Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) || Australia || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || <b>Build Success<b/> || Distcc: Done<br />
|-<br />
|Ladan Zahiroleslam(irc:l_zahir)|| China|| '''Build ended''' on Sat Jan 31 22:47:11 2009 (but it was done locally) I nead help to get distCC work with it|| Distcc: Done<br />
|-<br />
| [[User:Tiago|Tiago]] (IRC: Kamots) || India || Building OOo || Regular Build: in progress<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || <b>Build Success!!</b> <br/> Started: Jan 30 - 9:41pm <br/> Ended: Jan 31 - 1:53am || Distcc: Done<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
* export CC='distcc gcc'<br />
* export CXX='distcc g++' <br />
<br />
* Read this as well:[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc]<br />
<br />
== Configuring The Source ==<br />
Configuring error is different for every machine.<br/><br />
Here is some errors and fixes for it.<br />
<br />
{| border="1" width="500"<br />
! Issues !! Solutions<br />
|-<br />
| no cups/cups.h || yum install cups-devel<br />
|-<br />
| no JDK installed || yum install java-1.7.0-icedtea-devel.x86_64<br />
|-<br />
| no gperf || yum install gperf.x86_64<br />
|-<br />
| no Ant || yum install ant.x86_64<br />
|-<br />
|Can't locate Archive/Zip.pm in @INC ||yum install perl-Archive-Zip<br />
|}<br />
<br />
== Setting Environment Variables ==<br />
<br />
source LinuxX86-64Env.Set.sh<br />
<br />
== Bootstrapping ==<br />
./bootstrap<br />
<br />
== Build ==<br />
dmake '''2>~/errorLog'''</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=22896OOo Fedora Build2009-01-31T00:08:19Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
<br />
{| border="1" width="700"<br />
|+ CDOT Computer Status - Who is working where<br />
|-<br />
! Student Name !! CDOT Computer Name !! Operation !! Status<br />
|-<br />
| [[User:Bbarcick|Bartosz]] (irc:BartB) || Australia || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Hong Kong || <Fill in this> || Distcc: Done<br />
|-<br />
| Fardad (irc:fardad) || Ireland || <Fill in this> || Distcc: Done<br />
|-<br />
| Daeseon Moon (irc:daeseon) || Germany || Building OOO || Distcc: Done<br />
|-<br />
| [[User:Minicheong|Frankie]] (IRC: Mini_Cheong) || Liberia || ./configure || Distcc: Done <br/> OOo: Checked Out<br />
|}<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
<br />
<br />
== Configuring The Source ==<br />
<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=OOo_Fedora_Build&diff=22873OOo Fedora Build2009-01-30T16:55:41Z<p>Dmoon4: /* Openoffice.org Fedora Build */</p>
<hr />
<div>= Openoffice.org Fedora Build =<br />
* Resources<br />
** [http://wiki.services.openoffice.org/wiki/Build_Software_Requirements "Build Software Requirements"]<br />
** [http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org "Building OpenOffice.org"]<br />
* Who is working where?<br />
** '''Australia''' (distcc done)<br />
*** [[User:Bbarcick|Bartosz]] (irc:BartB)<br />
** '''Hongkong''' (distcc done)<br />
*** Fardad (irc:fardad)<br />
** '''Germany''' (distcc done)<br />
*** Daeseon Moon<br />
**** Building OpenOffice<br />
** '''Ireland''' (distcc done<br />
*** Fardad (irc:fardad)<br />
<br />
== Getting the Source ==<br />
Use:<br />
<pre><br />
svn co http://svn.services.openoffice.org/ooo/tags/DEV300_m40<br />
</pre><br />
to checkout the source.<br />
Make sure you are using http instead of svn, if you are checking the source out in Seneca.<br />
<br />
== Setting C and C++ compilers ==<br />
<br />
<br />
== Configuring The Source ==<br />
<br />
<br />
== Setting Environment Variables ==<br />
<br />
<br />
== Bootstrapping ==<br />
<br />
<br />
== Build ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Distcc_Setup&diff=22853Distcc Setup2009-01-30T04:33:48Z<p>Dmoon4: /* Assigned machine */</p>
<hr />
<div>= Task Name =<br />
<br />
Setting up [http://distcc.samba.org/ distcc], distributed compilation for c/c++ compilers on Linux machines in CDOT.<br />
<br />
<br />
= Task Description =<br />
<br />
The goal is to eventually set up distcc on all Linux boxes in CDOT, so compiling on any of the computers is distributed on all others.<br />
<br />
= Resources =<br />
<br />
[http://www.gentoo.org/doc/en/cross-compiling-distcc.xml DistCC Cross-compiling Guide]<br /><br />
[http://distcc.samba.org/faq.html Frequently asked questions]<br /><br />
[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc Linux Knowledge Base: DistCC]<br /><br />
[http://www.opensource.apple.com/darwinsource/DevToolsDec2003/distcc-19/linuxdoc/html/distcc.html#toc2 DistCC User Manual]<br /><br />
[http://daeseonmoon.wordpress.com/ Deaseon Moon's Blog]<br /><br />
(add more)<br />
<br />
== Assigned machine ==<br />
<br />
* Ireland (142.204.133.26) - Tested & Working - [[User:Minicheong|Frankie Law]] (irc Mini_Cheong), [[User:dmoon4|Daeseon Moon]] (irc daeseon)<br />
* Germany (142.204.133.102) - Tested & Working - Andrew Braini(aBraini)<br />
* Australia (142.204.133.24) - Tested & Working - [[User:wfred|Fred Wang]] (WFred)<br />
* China (142.204.133.36) - Tested & Working - Aaron Chan (achan66)<br />
* Liberia (142.204.133.123) - Tested & Working - [http://lzahir.blogspot.com/2009/01/my-distcc-setup-and-distributed.html Ladan Zahiroleslam] (irc: l_zahir, LZahir)<br />
* Hongkong (142.204.133.30) - Tested & Working - [[User:jtpau|Jerry Pau]] (jPau)<br />
* India (142.204.133.28) - Tested & Working - [[User:rmwang|Ryan Wang]] (rmwang), [[User:Tiago|Tiago Moreira]] (Kamots)<br />
<br />
'''Status'''<br />
* '''India'''<br />
** network connection went down again around 2pm, could not complete distcc setup --- [[User:Tiago|Tiago]]<br />
** Ran through tutorial on Australia and it seemed good. I managed to compile Apache --- [[User:Tiago|Tiago]]<br />
<br />
*'''Germany'''<br />
** distccd user created, hosts file setup, tested and working on Thu 29 Jan, 2009 --- [[User:Arbraini|ABraini]]<br />
<br />
*'''Australia'''<br />
** distccd is running under distcc account<br />
*** hosts file setting done<br />
*** user "distcc" created for running distccd. --- [[User:dmoon4|Daeseon Moon]]<br />
<br />
*'''Hong Kong'''<br />
** distcc user created, hosts file setup done<br />
<br />
*'''Ireland'''<br />
** distcc user created, hosts file setup done<br />
<br />
*'''India'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
*'''Liberia'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
*'''China'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
= distcc Setup Steps =<br />
'''Installation'''<br />
<br />
To install distcc using yum log on as root "su -" and type “yum search distcc”. Two packages available, install both to run as both client and server. At prompt type “yum install distcc-server” to install server package and “yum install distcc” for client package.<br />
<br />
'''Configuration'''<br />
<br />
Create a new user the daemon will run under without a home dir or workgroup<br />
<pre>$ adduser distcc -N -M </pre><br />
<br />
Start the distcc daemon <br />
<pre>$ distccd --daemon --user distcc --allow 142.204.133.0/24</pre><br />
Argument --user is if distccd gets executed as root, change to user USER, --allow IPADDR[/MASK] instructs distccd to accept connections from the IP address. A CIDR mask length can be supplied optionally after a trailing slash, e.g. 192.168.0.0/24, in which case addresses that match in the most significant MASK bits will be allowed.<br />
<br />
Now we need to setup the IPTABLES to allow connections to the distcc daemon. Before doing anything make a backup file of the original iptables file located in /etc/sysconfig/iptables. <br />
<pre>$ cp /etc/sysconfig/iptables [backupfile name]<br />
$ iptables -I INPUT 7 -i eth0 -p tcp -s 142.204.133.0/24 --dport 3632 -j ACCEPT<br />
$ service iptables save </pre><br />
<br />
*Important Note: It seems the -I INPUT 7 argument is confusing a lot of people. -I INPUT 7 was used in Daeson's case for the machine he was working on at the time, however this may not be the same for all machines. In Daeson's case there was a REJECT line in the INPUT CHAIN at line 8. So in order for us to get our port open we need to insert ie. -I into the INPUT CHAIN at line 7 before the REJECT line. On Machines with an INPUT CHAIN shorter then 7 lines this will cause an error. On machines without a REJECT line a simple "-A" appened aurgument can take the place of "-I INPUT 7". On a machine with a REJECT INPUT on a line before 8 you simply need to change the number to one smaller as long as it is before the REJECT line.<br />
<br />
** I'm not sure if we need to do this command, because if the file "HOSTS" at /etc/distcc/ is configured to have all the hosts name - distcc seems to distribute all compilation throughout the hosts. <br />
<br />
Argument -I is insert and -i is and network interface device and -p is protocol -s is source ipaddress and subnet, –dport is destination port and -j is rule.<br />
<br />
On the client machine the server names need to be added to the hosts listed in the file located at <br />
<pre>/etc/distcc/hosts</pre><br />
<br />
To close/shut down the daemon (do not unless needed)<br />
<pre>$ service distccd stop</pre><br />
'''Testing'''<br />
<br />
Open two SSH connections into the client machine.<br />
<br />
In Terminal 1 enter:<br />
<pre>$ distccmon-text 1</pre><br />
<br />
In Terminal 2 enter:<br />
<pre>$ wget http://apache.mirror.rafal.ca/httpd/httpd-2.2.11.tar.gz<br />
$ tar xzvf httpd-2.2.11.tar.gz<br />
$ cd httpd-2.2.11<br />
$ CC=distcc ./configure<br />
$ make -j9 CC=distcc >log 2> error </pre><br />
<br />
(complete this collaboratively) TO-DO<br />
<br />
* hosts saved in hosts file<br />
* better formatting<br />
* creating new distccd user with no home-dir for daemon<br />
* things forgotten or left out.<br />
== How to compile with distcc ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Distcc_Setup&diff=22852Distcc Setup2009-01-30T04:33:36Z<p>Dmoon4: /* Assigned machine */</p>
<hr />
<div>= Task Name =<br />
<br />
Setting up [http://distcc.samba.org/ distcc], distributed compilation for c/c++ compilers on Linux machines in CDOT.<br />
<br />
<br />
= Task Description =<br />
<br />
The goal is to eventually set up distcc on all Linux boxes in CDOT, so compiling on any of the computers is distributed on all others.<br />
<br />
= Resources =<br />
<br />
[http://www.gentoo.org/doc/en/cross-compiling-distcc.xml DistCC Cross-compiling Guide]<br /><br />
[http://distcc.samba.org/faq.html Frequently asked questions]<br /><br />
[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc Linux Knowledge Base: DistCC]<br /><br />
[http://www.opensource.apple.com/darwinsource/DevToolsDec2003/distcc-19/linuxdoc/html/distcc.html#toc2 DistCC User Manual]<br /><br />
[http://daeseonmoon.wordpress.com/ Deaseon Moon's Blog]<br /><br />
(add more)<br />
<br />
== Assigned machine ==<br />
<br />
* Ireland (142.204.133.26) - Tested & Working - [[User:Minicheong|Frankie Law]] (irc Mini_Cheong), [[User:dmoon4|Daeseon Moon]] (irc daeseon)<br />
* Germany (142.204.133.102) - Tested & Working - Andrew Braini(aBraini)<br />
* Australia (142.204.133.24) - Tested & Working - [[User:wfred|Fred Wang]] (WFred)<br />
* China (142.204.133.36) - Tested & Working - Aaron Chan (achan66)<br />
* Liberia (142.204.133.123) - Tested & Working - [http://lzahir.blogspot.com/2009/01/my-distcc-setup-and-distributed.html Ladan Zahiroleslam] (irc: l_zahir, LZahir)<br />
* Hongkong (142.204.133.30) - Tested & Working - [[User:jtpau|Jerry Pau]] (jPau)<br />
* India (142.204.133.28) - Tested & Working - [[User:rmwang|Ryan Wang]] (rmwang), [[User:Tiago|Tiago Moreira]] (Kamots)<br />
<br />
'''Status'''<br />
* '''India'''<br />
** network connection went down again around 2pm, could not complete distcc setup --- [[User:Tiago|Tiago]]<br />
** Ran through tutorial on Australia and it seemed good. I managed to compile Apache --- [[User:Tiago|Tiago]]<br />
<br />
*'''Germany'''<br />
** distccd user created, hosts file setup, tested and working on Thu 29 Jan, 2009 --- [[User:Arbraini|ABraini]]<br />
<br />
*'''Australia'''<br />
** distccd is running under distcc account<br />
*** hosts file setting done<br />
*** user "distcc" created for running distccd. --- [[User:dmoon4|Daeseon Moon]]<br />
<br />
*'''Hong Kong'''<br />
** distcc user created, hosts file setup done<br />
<br />
*'''Ireland'''<br />
** distcc user created, hosts file setup done<br />
<br />
*'''India'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
*'''Liberia'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
*'''Liberia'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
= distcc Setup Steps =<br />
'''Installation'''<br />
<br />
To install distcc using yum log on as root "su -" and type “yum search distcc”. Two packages available, install both to run as both client and server. At prompt type “yum install distcc-server” to install server package and “yum install distcc” for client package.<br />
<br />
'''Configuration'''<br />
<br />
Create a new user the daemon will run under without a home dir or workgroup<br />
<pre>$ adduser distcc -N -M </pre><br />
<br />
Start the distcc daemon <br />
<pre>$ distccd --daemon --user distcc --allow 142.204.133.0/24</pre><br />
Argument --user is if distccd gets executed as root, change to user USER, --allow IPADDR[/MASK] instructs distccd to accept connections from the IP address. A CIDR mask length can be supplied optionally after a trailing slash, e.g. 192.168.0.0/24, in which case addresses that match in the most significant MASK bits will be allowed.<br />
<br />
Now we need to setup the IPTABLES to allow connections to the distcc daemon. Before doing anything make a backup file of the original iptables file located in /etc/sysconfig/iptables. <br />
<pre>$ cp /etc/sysconfig/iptables [backupfile name]<br />
$ iptables -I INPUT 7 -i eth0 -p tcp -s 142.204.133.0/24 --dport 3632 -j ACCEPT<br />
$ service iptables save </pre><br />
<br />
*Important Note: It seems the -I INPUT 7 argument is confusing a lot of people. -I INPUT 7 was used in Daeson's case for the machine he was working on at the time, however this may not be the same for all machines. In Daeson's case there was a REJECT line in the INPUT CHAIN at line 8. So in order for us to get our port open we need to insert ie. -I into the INPUT CHAIN at line 7 before the REJECT line. On Machines with an INPUT CHAIN shorter then 7 lines this will cause an error. On machines without a REJECT line a simple "-A" appened aurgument can take the place of "-I INPUT 7". On a machine with a REJECT INPUT on a line before 8 you simply need to change the number to one smaller as long as it is before the REJECT line.<br />
<br />
** I'm not sure if we need to do this command, because if the file "HOSTS" at /etc/distcc/ is configured to have all the hosts name - distcc seems to distribute all compilation throughout the hosts. <br />
<br />
Argument -I is insert and -i is and network interface device and -p is protocol -s is source ipaddress and subnet, –dport is destination port and -j is rule.<br />
<br />
On the client machine the server names need to be added to the hosts listed in the file located at <br />
<pre>/etc/distcc/hosts</pre><br />
<br />
To close/shut down the daemon (do not unless needed)<br />
<pre>$ service distccd stop</pre><br />
'''Testing'''<br />
<br />
Open two SSH connections into the client machine.<br />
<br />
In Terminal 1 enter:<br />
<pre>$ distccmon-text 1</pre><br />
<br />
In Terminal 2 enter:<br />
<pre>$ wget http://apache.mirror.rafal.ca/httpd/httpd-2.2.11.tar.gz<br />
$ tar xzvf httpd-2.2.11.tar.gz<br />
$ cd httpd-2.2.11<br />
$ CC=distcc ./configure<br />
$ make -j9 CC=distcc >log 2> error </pre><br />
<br />
(complete this collaboratively) TO-DO<br />
<br />
* hosts saved in hosts file<br />
* better formatting<br />
* creating new distccd user with no home-dir for daemon<br />
* things forgotten or left out.<br />
== How to compile with distcc ==</div>Dmoon4https://wiki.cdot.senecacollege.ca/w/index.php?title=Distcc_Setup&diff=22851Distcc Setup2009-01-30T04:26:45Z<p>Dmoon4: /* Assigned machine */</p>
<hr />
<div>= Task Name =<br />
<br />
Setting up [http://distcc.samba.org/ distcc], distributed compilation for c/c++ compilers on Linux machines in CDOT.<br />
<br />
<br />
= Task Description =<br />
<br />
The goal is to eventually set up distcc on all Linux boxes in CDOT, so compiling on any of the computers is distributed on all others.<br />
<br />
= Resources =<br />
<br />
[http://www.gentoo.org/doc/en/cross-compiling-distcc.xml DistCC Cross-compiling Guide]<br /><br />
[http://distcc.samba.org/faq.html Frequently asked questions]<br /><br />
[http://www.linux-tutorial.info/modules.php?name=ManPage&sec=1&manpage=distcc Linux Knowledge Base: DistCC]<br /><br />
[http://www.opensource.apple.com/darwinsource/DevToolsDec2003/distcc-19/linuxdoc/html/distcc.html#toc2 DistCC User Manual]<br /><br />
[http://daeseonmoon.wordpress.com/ Deaseon Moon's Blog]<br /><br />
(add more)<br />
<br />
== Assigned machine ==<br />
<br />
* Ireland (142.204.133.26) - Tested & Working - [[User:Minicheong|Frankie Law]] (irc Mini_Cheong), [[User:dmoon4|Daeseon Moon]] (irc daeseon)<br />
* Germany (142.204.133.102) - Tested & Working - Andrew Braini(aBraini)<br />
* Australia (142.204.133.24) - Tested & Working - [[User:wfred|Fred Wang]] (WFred)<br />
* China (142.204.133.36) - Tested & Working - Aaron Chan (achan66)<br />
* Liberia (142.204.133.123) - Tested & Working - [http://lzahir.blogspot.com/2009/01/my-distcc-setup-and-distributed.html Ladan Zahiroleslam] (irc: l_zahir, LZahir)<br />
* Hongkong (142.204.133.30) - Tested & Working - [[User:jtpau|Jerry Pau]] (jPau)<br />
* India (142.204.133.28) - Tested & Working - [[User:rmwang|Ryan Wang]] (rmwang), [[User:Tiago|Tiago Moreira]] (Kamots)<br />
<br />
'''Status'''<br />
* '''India'''<br />
** network connection went down again around 2pm, could not complete distcc setup --- [[User:Tiago|Tiago]]<br />
** Ran through tutorial on Australia and it seemed good. I managed to compile Apache --- [[User:Tiago|Tiago]]<br />
<br />
*'''Germany'''<br />
** distccd user created, hosts file setup, tested and working on Thu 29 Jan, 2009 --- [[User:Arbraini|ABraini]]<br />
<br />
*'''Australia'''<br />
** distccd is running under distcc account<br />
*** hosts file setting done<br />
*** user "distcc" created for running distccd. --- [[User:dmoon4|Daeseon Moon]]<br />
<br />
*'''Hong Kong'''<br />
** distcc user created, hosts file setup done<br />
<br />
*'''Ireland'''<br />
** distcc user created, hosts file setup done<br />
<br />
*'''India'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
*'''Liberia'''<br />
** distcc user created<br />
** hosts file modified<br />
<br />
= distcc Setup Steps =<br />
'''Installation'''<br />
<br />
To install distcc using yum log on as root "su -" and type “yum search distcc”. Two packages available, install both to run as both client and server. At prompt type “yum install distcc-server” to install server package and “yum install distcc” for client package.<br />
<br />
'''Configuration'''<br />
<br />
Create a new user the daemon will run under without a home dir or workgroup<br />
<pre>$ adduser distcc -N -M </pre><br />
<br />
Start the distcc daemon <br />
<pre>$ distccd --daemon --user distcc --allow 142.204.133.0/24</pre><br />
Argument --user is if distccd gets executed as root, change to user USER, --allow IPADDR[/MASK] instructs distccd to accept connections from the IP address. A CIDR mask length can be supplied optionally after a trailing slash, e.g. 192.168.0.0/24, in which case addresses that match in the most significant MASK bits will be allowed.<br />
<br />
Now we need to setup the IPTABLES to allow connections to the distcc daemon. Before doing anything make a backup file of the original iptables file located in /etc/sysconfig/iptables. <br />
<pre>$ cp /etc/sysconfig/iptables [backupfile name]<br />
$ iptables -I INPUT 7 -i eth0 -p tcp -s 142.204.133.0/24 --dport 3632 -j ACCEPT<br />
$ service iptables save </pre><br />
<br />
*Important Note: It seems the -I INPUT 7 argument is confusing a lot of people. -I INPUT 7 was used in Daeson's case for the machine he was working on at the time, however this may not be the same for all machines. In Daeson's case there was a REJECT line in the INPUT CHAIN at line 8. So in order for us to get our port open we need to insert ie. -I into the INPUT CHAIN at line 7 before the REJECT line. On Machines with an INPUT CHAIN shorter then 7 lines this will cause an error. On machines without a REJECT line a simple "-A" appened aurgument can take the place of "-I INPUT 7". On a machine with a REJECT INPUT on a line before 8 you simply need to change the number to one smaller as long as it is before the REJECT line.<br />
<br />
** I'm not sure if we need to do this command, because if the file "HOSTS" at /etc/distcc/ is configured to have all the hosts name - distcc seems to distribute all compilation throughout the hosts. <br />
<br />
Argument -I is insert and -i is and network interface device and -p is protocol -s is source ipaddress and subnet, –dport is destination port and -j is rule.<br />
<br />
On the client machine the server names need to be added to the hosts listed in the file located at <br />
<pre>/etc/distcc/hosts</pre><br />
<br />
To close/shut down the daemon (do not unless needed)<br />
<pre>$ service distccd stop</pre><br />
'''Testing'''<br />
<br />
Open two SSH connections into the client machine.<br />
<br />
In Terminal 1 enter:<br />
<pre>$ distccmon-text 1</pre><br />
<br />
In Terminal 2 enter:<br />
<pre>$ wget http://apache.mirror.rafal.ca/httpd/httpd-2.2.11.tar.gz<br />
$ tar xzvf httpd-2.2.11.tar.gz<br />
$ cd httpd-2.2.11<br />
$ CC=distcc ./configure<br />
$ make -j9 CC=distcc >log 2> error </pre><br />
<br />
(complete this collaboratively) TO-DO<br />
<br />
* hosts saved in hosts file<br />
* better formatting<br />
* creating new distccd user with no home-dir for daemon<br />
* things forgotten or left out.<br />
== How to compile with distcc ==</div>Dmoon4