This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-staging in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/asf-staging by this push: new 1e3ab6a git-site-role commit from build_staging.sh 1e3ab6a is described below commit 1e3ab6a5ba8183d2e5fc1fd60ef4ca1820791aab Author: jenkins <bui...@apache.org> AuthorDate: Sun Nov 1 20:59:26 2020 +0000 git-site-role commit from build_staging.sh --- content/feed.xml | 4 +- content/scproces/Tigris_to_SC.html | 754 ++++++++++++++++++++++++++++++++++++ content/scproces/process.html | 408 +++++++++++++++++++ content/servlets/Join/index.html | 32 ++ content/servlets/ReadMsg/index.html | 31 ++ content/servlets/readme.txt | 7 + 6 files changed, 1234 insertions(+), 2 deletions(-) diff --git a/content/feed.xml b/content/feed.xml index 0e81fae..ccc7480 100644 --- a/content/feed.xml +++ b/content/feed.xml @@ -6,8 +6,8 @@ <atom:link href="http://localhost:8820/feed.xml" rel="self" type="application/rss+xml" /> <description>OpenOffice.org Feed</description> <language>en-us</language> - <pubDate>Sun, 1 Nov 2020 20:57:07 +0000</pubDate> - <lastBuildDate>Sun, 1 Nov 2020 20:57:07 +0000</lastBuildDate> + <pubDate>Sun, 1 Nov 2020 20:59:22 +0000</pubDate> + <lastBuildDate>Sun, 1 Nov 2020 20:59:22 +0000</lastBuildDate> </channel> diff --git a/content/scproces/Tigris_to_SC.html b/content/scproces/Tigris_to_SC.html new file mode 100644 index 0000000..0d5af98 --- /dev/null +++ b/content/scproces/Tigris_to_SC.html @@ -0,0 +1,754 @@ + +<!--#include virtual="/doctype.html" --> +<html> + <head> + + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + + + <link href="/css/ooo.css" rel="stylesheet" type="text/css"> + <!--#include virtual="/scripts/google-analytics.js" --> + <!--#include virtual="/scripts/entourage.js" --> + </head> + <body> + <!--#include virtual="/brand.html" --> + <div id="topbara"> + <!--#include virtual="/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/scproces/">scproces</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + <style type="text/css"> body, h2, h3, h4, DIV, P, blockquote, ul, ol, li {font-family: Helvetica,Arial,sans-serif;}</style> +<h2>OpenOffice.org Process Inventory II</h2> +<p>Jeff Love, Louis Suárez-Potts</p> +<p><i>Last modified 28 June 2001</i></p> +<p><br> + This document is a modified version of one Jeff Love wrote for NetBeans's migration. + I have modified it to fit OpenOffice.org. The document contains a list of common + tasks currently undertaken by OpenOffice.org project owners and admins, and + a description of how that task will be completed in SourceCast. </p> +<p><b>NB</b> If an important element has been missed, please let me know: <a href="mailto:lo...@openoffice.org ">lo...@openoffice.org</a>. + Comments and questions should also be sent to me. If I cannot answer a question, + I will defer it to Jeff Love, who is leading the upgrade.</p> +<h4><B><br> + <br> + User Tasks</B></h4> +<p>Registering</p> +<p>How it is done now: </p> +<ul> + <li>Admin account created by member granting access</li> + <li>Issuezilla account created by User</li> +</ul> +<P> </P> +<p>General Differences (if any) in SourceCast: User creates own account; unified + issuezilla, admin and cvs access in one user</P> +<p>How to do it in SourceCast</P> +<ul> + <li>On Home Page, click <A href="//servlets/Join">Register + Now</A></li> + <li>Enter in chosen username, email address (must be valid), Real Name, Organization + (if desired)</li> + <li>Click "Register"</li> + <li>Once you press "Register", you will see the login screen and a + password will be send to your email address.</li> + <li>As soon as you receive your password, copy it into a clipboard space</li> + <li>Go to Home Page and enter username and password and hit enter</li> + <li>You will be put onto "My Home Page"</li> + <li>Click "Edit Profile" Link</li> + <li>Type in chosen password</li> + <li>Retype chosen password</li> + <li>Click Submit Changes</li> +</ul> +<h4>When do I need to Register/Login?</h4> +<p>How it is done now: </p> +<ul> + <li>Browsing Web Content: No login needed</li> + <li>CVS access: No account needed to download repository (anoncvs). Must have + admin account created by other member to gain COMMIT access to the repository.</li> + <li>IssueZilla access: Users create accounts themselves . Admin privileges granted + by other Issuezilla admins</li> + <li>Admin Access: Users don't request admin access themselves -- they must be + created by other members -- control/create mailing lists, projects,etc.</li> +</ul> +<p>General Differences (if any) in SourceCast: Users create accounts themselves + and then are approved by a SourceCast Administrator; Logging in is assumed to + be much more frequent than in Tigris. Assumptions are made once you have logged + in to SourceCast that presents certain information to you on "My Start + Page" based on the projects that you are a part of (such as news and your + project links and links to your issues on that project); If Developer or Content + Developer, allows write access to project resources, but not to configure those + resources; If role on project is project Owner -- user has access to configure + all project resources</P> +<p>How to do it in SourceCast</P> +<ul> + <li>Browsing Web Content: No login needed</li> + <li>CVS access: No account needed to download repository (anoncvs). Commit access + requires an account with Developer, Content Developer (HTML only) or project + Owner status on a project</li> + <li>Issuezilla: No login needed to QUERY and CHANGE existing bugs. Login necessary + to lodge new bugs</li> + <li>Admin Access: Always be logged in to have administrative access</li> +</ul> +<p> </p> +<h4>Downloading the CVS Repository</h4> +<p>How it is done now: </p> +<ul> + <li>Command Line or GUI client - set CVSROOT=:pserver:anon...@anoncvs.services.openoffice.org:/cvs</li> + <li>cvs login</li> + <li>password: (no password, just hit enter)</li> + <li>cvs co -c (list all projects available)</li> + <li>cvs co all (or project name, etc)</li> +</ul> +<p>General Differences (if any) in SourceCast: None</P> +<p>How to do it in SourceCast</P> +<ul> + <li>Command Line or GUI client - set CVSROOT=:pserver:anon...@anoncvs.services.openoffice.org:/cvs</li> + <li>cvs login</li> + <li>password: (no password, just hit enter)</li> + <li>cvs co -c (list all projects available)</li> + <li>cvs co all (or project name, etc)</li> +</ul> +<p> </p> +<h4>Uploading to the CVS Repository</h4> +<p>How it is done now: </p> +<ul> + <li>Command Line or GUI client - set CVSROOT=:pserver:<username>@OpenOffice.org:/cvs</li> + <li>cvs login</li> + <li>password: (username's password, hit enter)</li> + <li>cvs commit <filename></li> +</ul> +<p>General Differences (if any) in SourceCast: None</P> +<p>How to do it in SourceCast</P> +<ul> + <li>Command Line or GUI client - set CVSROOT=:pserver:<username>@OpenOffice.org:/cvs</li> + <li>cvs login</li> + <li>password: (username's password, hit enter)</li> + <li>cvs commit <filename></li> +</ul> +<p> </p> +<h4>Joining a project</h4> +<p>How it is done now: </p> +<ul> + <LI>Not done explicitly in Tigris now. Users are granted commit access to the + entire repository by a project owner.</LI> +</UL> +<p>General Differences (if any) in SourceCast: </P> +<ul> + <li>Users who actively participate should "Join a project"</li> + <li>this will signify that they are actively participating on the project;</li> + <li>It will put the user in the "Members" section of the project Resources + header</li> + <li>Give them commit access if they request a Developer Role</li> + <li> Make the project show up as a link in the "My projects" section + of the "My Start Page"</li> +</ul> +<p>How to do it in SourceCast</P> +<ul> + <li>click Join This project on the far right side of the screen in the project + Home page</li> + <li>which takes you to the project Membership Request page.</li> + <li>The radio buttons in the middle of the page present you with several role + options.</li> + <li>Think of the roles as a method of informing the project owner of how you + intend to contribute. You may request, or even be asked, to fulfill more than + one role at some point, and you can certainly fulfill other roles on different + projects.</li> + <li>To select a project role, click on the radio button to the left of the desired + role and click on the Submit Request button at the end of the list of roles. + </li> + <li>The project Owner will then need to approve or disapprove this role and + you will receive an email from the project owner when this action has been + taken.</li> + <li>Once you are a project member and your involvement progresses, you may wish + to change your role in a project. </li> + <li>The project Home page includes a Request New project Role link in the top + right corner of the same page you originally used to request membership in + the project. </li> +</ul> +<p> </p> +<h4>Choosing Role in a project</h4> +<p>How it is done now: </p> +<ul> + <li>Not done explicitly in Tigris now. Users are granted commit access to the + entire repository by a project owner.</li> +</ul> +<p>General Differences (if any) in SourceCast: The role that you choose on a project + both signifies to the community what type of participation you have on the project + as well governs what types of commit access (Developer or Content Developer)or + access to administrative functions you will have (project Owner);</P> +<p>How to do it in SourceCast:</P> +<p>The following details the various permission that the roles you have the option + to choose from carry:</P> +<b>Observer</b><br> +<ul> + <li>Views, but does not change project resources (news, files, mailing lists, + documentation, source code, issue tracking). + <li>Read-only access to most project resources. + <li>Read-only access to web content and source code (CVS). + <li>Submits issue to issue tracking (IssueZilla) + <li>Subscribes and posts to project mailing lists. +</ul> +<p><b>Developer</b><br> +<ul> + <li>Contributes directly to project -- source code and HTML. + <li>Gains write access (with approval from project Owner) to most project resources. + <li>Write access to HTML, news utility, files utility, CVS, Issuezilla. + <li>Mailing list privileges the same. +</ul> +<p><b>Content Developer</b><br> +<ul> + <li>Contributes directly to project's web content (HTML). + <li>Gains write access to project's HTML, news utility with project Owner approval, + files utility with project Owner approval, and Issuezilla. + <li>Mailing list privileges the same. +</ul> +<p><b>project Owner</b><br> +<ul> + <li>Defines the project's overall mission, direction, methodology, and community + make-up. + <li>Gains administrative access to all project functions. + <li>Grants members requested permissions on project. + <li>Administers all project mailing lists and is default moderator on all lists. + <li>Administers Issuezilla. + <li>project Owner role supersedes any other roles you may hold on a project. +</ul> +<p> </p> +<h4>Creating a News Item</h4> +<p>How it is done now: </p> +<ul> + <LI>Creating Static HTML page usually news.html in www/ directory of the project</LI> + <LI>Slightly heavyweight for sending out quick news items to project members</LI> +</ul> +<p>General Differences (if any) in SourceCast: The news utility allows for lightweight + news communication among project participants without having to write html; + Users who are Members in the project will have current News items displayed + for them on "My Start Page"</P> +<p>How to do it in SourceCast</P> +<ul> + <li>If Content Developer or Developer, user can "Suggest News Item" + and the project Owner will approve or disapprove the item once they log on</li> + <li>If project Owner, user can post news item themselves</li> + <li>Click "Suggest a News Item" or "Add News Item" as role + allows</li> + <li>Choose the date associated with this news item</li> + <li>Type in the "Headline" (sort of analogous to a Subject line on + an email message)</li> + <li>Type in the News item (can put in plain text or html markup as desired)</li> + <li>Click "Add News Item" button</li> + <li>If Content Developer or Developer, item will remain in the Pending Actions + section of the project Owner's "My Start Page" until Owner takes + action</li> + <li>If project Owner, news item gets posted immediately to Members "My + Start Page"</li> +</ul> +<p> </p> +<h4>Posting Large files for Download</h4> +<p>How it is done now: </p> +<UL> + <LI>Commit them to CVS (which wastes space)</LI> + <LI> or have Webmasters upload large file to the http://www.OpenOffice.org/downloads/ + directory</LI> + <LI>Users cannot upload to downloads directory themselves</LI> +</UL> +<p>General Differences (if any) in SourceCast: File utility is included to allow + the posting of large files for download without committing them to CVS; uploading + files is a GUI front end;</P> +<p>How to do it in SourceCast</P> +<ul> + <li>If Content Developer or Developer, user can "Suggest A Download" + and the project Owner will approve or disapprove the item once they log on</li> + <li>If project Owner, user can post files immediately</li> + <li>Click "Suggest a News Item" or "Add News Item" as role + allows</li> + <li>Hit "Browse" button and locate the file on your harddrive</li> + <li>Enter a description</li> + <li>If you wish this item to be public -- check the box -- in almost all cases + for OpenOffice.org the file should be public, but if for instance you are + uploading a draft of something you don't wish to be public right away it would + be advantageous to keep it private</li> + <li>Click "Upload File" button</li> + <li>if Content Developer or Developer, item will remain in the Pending Actions + section of the project Owner's "My Start Page" until Owner takes + action</li> + <li>If project Owner, news item gets posted immediately to File section of the + project Resources</li> +</ul> +<p> </p> +<h4>Posting Documentation for Download</h4> +<p>How it is done now: </p> +<ul> + <LI>posted in CVS (which wastes space)</LI> + <LI> or uploaded to http://www.OpenOffice.org/downloads/ directory by webmasters</li> + <LI>project Members cannot upload to downloads directory themselves</li> +</ul> +<p>General Differences (if any) in SourceCast: Documentation utility is included + to allow the categorization and display of documents that does not need to be + part of the main web content; uploading documentation for download without committing + them to CVS; uploading files is a GUI front end;</P> +<p>How to do it in SourceCast</P> +<ul> + <li>If Content Developer or Developer, user can "Suggest A Document" + or "Suggest A New Section" and the project Owner will approve or + disapprove the item once they log on</li> + <li>If project Owner, user can post documentation or categories immediately</li> + <li>Click "Suggest A Document" or "Add A New Document" as + role allows</li> + <li>Enter description of the file and the file's location, URL or enter HTML</li> + <li>Click "Add Document" button</li> + <li>if Content Developer or Developer, item will remain in the Pending Actions + section of the project Owner's "My Start Page" until Owner takes + action</li> + <li>If project Owner, news item gets posted immediately to File section of the + project Resources</li> +</ul> +<p> </p> +<h4>Creating An Issue in Issuezilla</h4> +<p>How it is done now: </p> +<ul> + <li>Must have existing Username and password</li> + <li>Enter a bug on a specific project</li> + <li>Reporter notified via email each time bug changes</li> +</ul> +<p> </p> +<p>General Differences (if any) in SourceCast: Must have Developer, Content Developer + or project Owner level access on a project to create issues</P> +<p>How to do it in SourceCast</P> +<p> Once a user becomes a member of a project, he or she is granted + additional IssueZilla permissions beyond the default database query capabilities. + Permissions can be viewed by clicking on the <strong>My Preferences</strong> + link on the <b>project Issues</b> page, or the <strong>Edit Prefs </strong> + link in the Issue Tracking toolbar. +<p> Issue tracking permissions depend upon project role: +<ul> + <li>Observers can create and modify issues, but can make changes to only + their own issues. Observers have the ability to comment on any issue. + <p></p> + <li>Developers (code or content) can report and modify their own and + other project issues. If they have been granted the "Can edit all + aspects of any issue" permission, they have the ability to alter all issue + characteristics, including milestones and issue assignments. + <p></p> + <li>project initiators automatically are granted administrative level IssueZilla + permissions with additional rights to configure issue tracking for + the project. project initiators can also assign IssueZilla-specific + permissions to other project members.</li> +</ul> +Additional permissions can be requested through the project owner. You may +need to request a new project role. +<p> +<p> +<p> </p> +<h4>Subscribing to a mailing list</h4> +<p>How it is done now: </p> +<ul> + <li>Send mail to: <mailinglist>-subscr...@openoffice.apache.org</li> + <li>Information on how to do this provided on this page which is linked off + of the main nav bar</li> +</ul> +<p>General Differences (if any) in SourceCast: None really; "Mailing Lists" + link off of project Resources tool bar allows user to subscribe by hitting a + button instead of sending email</P> +<p>How to do it in SourceCast</P> +<p> +<UL> + <LI>You can subscribe or unsubscribe to mailing lists for a particular project + by selecting "Mailing Lists" in the project Resources tool bar. </LI> + <LI> The <b>project Mail</b> page includes subscribe/unsubscribe links for either + a message-by-message or digest version of the list, as well as options to + view each project list's archives. </LI> + <LI> To begin the subscription process, click on the hyperlinked mailing list + address to which you want to subscribe and send the message from your email + client. </LI> + <LI> You should receive a response asking for a confirmation. After you reply + as indicated in the email, you will receive an email welcoming you and acknowledging + your successful mailing list subscription. </LI> + <LI> Follow the same process for unsubscribing, but substitute the + <strong>unsubscribe</strong> link.</LI> +</ul> +<p> </p> +<h4>Browsing Archives</h4> +<p>How it is done now: </p> +<ul> + <li>Browse Static HTML pages generated by Monharc</li> + <li>Messages are in this static form which makes it harder to search for particular + pieces of mail</li> +</ul> +<p>General Differences (if any) in SourceCast: archives are dynamically generated, + better search facility</P> +<p>How to do it in SourceCast</P> +<ul> + <li> To view a mailing list's archives, select the <strong>Mailing List</strong> + option in the project Resources tool bar to see a list of all mailing lists + for that project. </li> + <li> Click on the <strong>View Archive </strong>link next to the list you want + to view. </li> + <li> The default view for browsing mailing list archives is by date summary. + </li> + <li> Other summary views available are: by <strong>Author</strong>, by <strong>Subject</strong>, + and by <strong>Thread</strong>. </li> + <li> You can use the <strong>Search Archive </strong>link to add filters to + your search criteria. </li> + <li> You can enter a search text and choose to sort by <strong>Subject</strong>, + <strong>Author</strong>, or <strong>Body </strong>by choosing one from the + drop down box under the text box.</li> + <li> You can also search text strings of the archived messages using simple + Boolean operators. </li> + <li></li> + <li>Note: project/component mailing list archiving is handled by <a href="http://eyebrowse.tigris.org/"> + EyeBrowse</a>, an open source tool that stores and indexes list messages, + providing multiple options for browsing, reading, and searching mailing list + archives via a web browser. Beyond storing messages, EyeBrowse adds a database + and text indexing engine to handle rapid message search and retrieval. </li> +</ul> +<p> </p> +<h3>Administrative Tasks</h3> +<h4>Adding Members to your project</h4> +<p>How it is done now: </p> +<ul> + <li>Administrator logs in to Administrative interface</li> + <li>Chooses "List Users" from Menu</li> + <li>Clicks on a specific user</li> + <li>Puts check in "Read all CVS projects in domain"</li> + <li>Puts check in "Change all CVS projects in domain"</li> +</ul> +<p>General Differences (if any) in SourceCast: Two ways to add members: explicitly + adding them or having user request to join the project and approving their membership + and granting them privileges</P> +<p>How to do it in SourceCast</P> +<p>Explicitly adding new users:</p> +<ul> + <li>Log In as project Owner of a particular project</li> + <li>Choose Members from the project Resources toolbar</li> + <li>Click "Add A New Member" link</li> + <li>Check the box next to the username of the user you would like to add to + your project</li> + <li>Choose the Role to assign the User/Users you have selected from the list</li> + <li>Click "Grant Roles" button at the bottom of screen</li> +</ul> +<P>Approving Members Role(s) in you project</P> +<ul> + <li>Log In as project Owner of a particular project</li> + <li>at "My Start Page" look at the section labeled "Proposed + Role in project <projectname>"</li> + <li>Click the link</li> + <li>At the next screen, look at the section labeled "Requests pending approval"</li> + <li>Below that select the radio button that matches your action: approving role, + disapprove or defer action</li> + <li>Click Edit Roles</li> +</ul> +<p>Note: The other option "Invite Members" is used purely to send out an invitational + email to potential project members asking them to join your project</p> +<p> </p> +<h4>Changing mailing list configuration</h4> +<p>How it is done now: </p> +<ul> + <li>Administrator logs into Admin interface</li> + <li>Chooses "List Projects" from Menu</li> + <li>Selects Project to change from List</li> + <li>Chooses list to change</li> + <li>Changes configuration options and click "Make Changes" button</li> +</ul> +<p>General Differences (if any) in SourceCast:</P> +<p>How to do it in SourceCast</P> +<ul> + <li>Log In with project Owner status on a particular project</li> + <li>Choose "Mailing Lists" from the project Resources toolbar</li> + <li>Once there, scroll down to find the list you wish to change</li> + <li>Click the link "Edit <listname> Mailing List"</li> + <li>The options available are groupings of what was available in Tigris</li> + <li>Most of the options here are self explanatory except for list type</li> + <li>discuss is the most common mail list type, this give the list moderation + for non-subscribers, while subscribers can post without moderation</li> + <li>moderated means EACH post gets bounced to a moderator (good for low traffic + announce lists)</li> + <li>unmoderated means NO POSTS get sent to a moderator (there are no moderators)</li> + <li>discuss-bounce-to-moderator is brand new -- as of June 27th, I do not know + what the difference is here; email sent to developer about what this option + means</li> + <li>User can also click on the links at the bottom to add/delete/view Subscribers, + Digest Subscribers, Moderators, Allowed Posters</li> + <li>User can also Delete Mailing list at this point -- this link contains confirmation + and care should be taken to be cognizant that all archives are destroyed once + a mailing list is deleted.</li> +</ul> +<p> </p> +<h4>Adding a mailing list</h4> +<p>How it is done now: </p> +<ul> + <li>Administrator logs into Admin interface</li> + <li>Chooses "List Projects" from Menu</li> + <li>Selects Project to change from List</li> + <li>Chooses list to change</li> + <li>or Chooses "Add New Mailing List"</li> + <li>Creates new mailing list with appropriate options and Clicks "Create List"</li> +</ul> +<p>General Differences (if any) in SourceCast: Mail categories more grouped, mail + list options aren't just scattered unintelligible checkboxes</P> +<p>How to do it in SourceCast</P> +<ul> + <li>Log In with project Owner status on a particular project</li> + <li>Choose "Mailing Lists" from the project Resources toolbar</li> + <li>Choose the "Add New Mail List" link</li> + <li>Fill in List Name (list name will be the name before the @ symbol in the + email address -- ie. d...@netbrowser.openoffice.org</li> + <li>The options available are groupings of what was available in Tigris</li> + <li>Most of the options here are self explanatory except for list type</li> + <li>discuss is the most common mail list type, this give the list moderation + for non-subscribers, while subscribers can post without moderation</li> + <li>moderated means EACH post gets bounced to a moderator (good for low traffic + announce lists)</li> + <li>unmoderated means NO POSTS get sent to a moderator (there are no moderators)</li> + <li>discuss-bounce-to-moderator is brand new -- as of June 27th, I do not know + what the difference is here; email sent to developer about what this option + means</li> + <li>User can add users initially to the email address and thus keep them from + having to sign up themselves</li> + <li>Click button "Create Mailing List"</li> +</ul> +<p> </p> +<h4>Approving a new project</h4> +<p>How it is done now: </p> +<ul> + <li>Not done in Tigris. project must be created for user by admin and then given + project owner status on the project</li> +</ul> +<p>General Differences (if any) in SourceCast: Domain Admin will approve project + before it is posted live on the site; Users can suggest projects themselves + without the admins having to create the project for them</p> +<p>How to do it in SourceCast</P> +<ul> + <li>Log In with project Owner status on a particular project</li> + <li>on "My Start Page" look at the "Pending Actions" section + of the page</li> + <li>Click on "Proposed Mailing List in project <name>"</li> + <li>At the next screen, look at the section labeled "Requests pending approval"</li> + <li>Below that select the radio button that matches your action: approving mailing + list, disapprove mailing list or defer action</li> +</ul> +<p> </p> +<h4>Creating a new project</h4> +<p>How it is done now: </p> +<ul> + <li>Admin must login to Tigris</li> + <li>Click "Edit projects"</li> + <li>Click link "Add New project"</li> + <li>and follow instructions from there </li> +</ul> +<P> </P> +<p>General Differences (if any) in SourceCast: Users can suggest projects themselves; + do not have to rely on Administrator to create project for them</P> +<p>How to do it in SourceCast</p> +<ul> + <li> You must be a registered user and you must be logged in to start a project. + </li> + <li>Creating a new project on this site is fairly straightforward. You should, + however, come to the task prepared, with a good sense of what you want and + how you want to accomplish it. Knowing whom to invite onto your project won't + hurt, either. </li> + <li>Choose the Start a project link on "My Start Page" </li> +</ul> +<p><b>Create New project Step 1</b></p> +<ul> + <li> + <p>The fields available on the "Start a project" page allow you + to configure your project. Below, we have explained each of the fields and + their function. </p> + <P> + <P> + <blockquote><B>project Name</B> Enter what you wish to call your project. + Choose a name that both describes the project and conforms to the naming + conventions. That is, use the a-z, 0-9, and dash (but not as the first character); + no spaces, underscoring, capitalization, or other punctuation. Keep in mind + that the project name cannot be changed. An example of a name for a project + dealing with porting a sophisticated chess game to the telephone might be + "chessphone." Unimaginative, to be sure, but descriptive. + <p></P> + <P><B>Summary</B><BR> + Enter a one-line description of your project, no longer than the field + length. The description should be in plain text; HTML and formatted text + are not supported. The description will be adjacent to the name of the + project and be what registered users see first when they view the list + of available projects. It should therefore be descriptive and concise. + For instance, in the case of the chess game, you might write: "Porting + an advanced chess game to the phone." Unlike the project name, you + can edit this field at any time.</P> + <P><B>Description</B><BR> + This description makes up the bulk of your project's home page. It is + where you can present the project in as interesting a light as possible. + You can include HTML, formatted text, and so on, but keep in mind that + most developers prefer simple and fast over complicated and slow (and + confusing). State here your project's mission, background, methodology, + tasks available, and other information that a developer might need to + begin working on your project. This field can be edited at any time by + clicking on the "Edit project" link once you have finished creating + a project, but the information should remain consistent. + </blockquote> + </li> +</ul> +<p><b>Create project Step 2</b></p> +<ul> + <li> + <blockquote> + <P><B>License</B><BR> + The current licenses will be available for OpenOffice.org.</p> + <P><B>project Category</B><BR> + Select the category appropriate for your project. Because projects are + listed by category in both the Start Page and project Home pages, the + choice of category is critical for giving developers a sense of the kind + of work available. A developer who specializes in games, for example, + will not necessarily want to view projects in the productivity category. + As you can see, there are many possible options, and if you end up preferring + another category, you can change your project category at any time. To + edit this features of your project, click on "Edit project" + once you have finished creating the project.</p> + <P><B>project Profile</B><BR> + The project Profile buttons are configured to automatically create mailing + lists for your particular project. Perhaps you have a project idea that + will require much discussion and input from other developers well before + getting to the point of actual source code; this would be a "Discussion + project." If your project, on the other hand, involves reworking existing + source code, choose "Standard development project." Selecting a content + project generates one general mailing list; you would not have access + to the issue-tracking system because it would not be necessary. Selecting + the standard project profile generates five mailing lists, and gives you + access to all of the other resources of the site, including issue tracking. + It is important to stress that no matter what profile you choose, you + can change it later.</p> + </blockquote> + </li> +</ul> +<p><b>Create project Step 3</b></P> +<ul> + <li> + <blockquote><b>People To Invite</b><br> + Invite as many people as you wish by listing their email addresses, one + email address per line, or multiple addresses if each address is separated + by a comma, colon, or semicolon. Automatically generated invitations to + each invitee will be sent; you can use the field below to include a personal + message, perhaps a brief explanation of your project's purpose, why you + think he or she might find it worthwhile to join in, and a link providing + direct access to your project home page. + <p>Recipients of your invitation who are already registered with this site + log in to view your project home page. To join your project, they click + the "Join This project" link.</p> + <p>If the person you're inviting is <i>not</i> registered with this site, + the email invitation asks her to register first to obtain a login and + password by email. Then this person is able to log in and view your project + home page.</p> + <P> <B>Invitation Message</B><BR> + This message should be brief, but clear and informative. You can include + hyperlinks, and any other information that you think would promote your + project. Formatting and HTML are not, however, supported--the message, + that is, stands on what it says not on how it looks. Hint: write out what + you want to say beforehand. That way, you won't be lost for words. Finally, + all the other project information is automatically generated, so you don't + have to worry about including it again.</P> + </blockquote> + <p> + </li> +</ul> +<p><b>Project confirmation</b></p> +<ul> + <li> + <p>When you finish filling out all the fields and writing the messages, click + <b>Finish,</b> which takes you to the confirmation page. From there, you + can go to your newly created project home page. + <p>While your project's status is pending, you can do many things to enhance + your project's appeal. You can:</p> + <ul> + <li>Customize your project home page content + <li>Add, configure, or delete mailing lists + <li>Upload source files and documents + <li>Invite additional participants</li> + </ul> + <p>In short, you can use most of the project functionality while waiting for + project approval. Once your project is approved, you can accept member requests + to begin building your project team.</p> + </li> +</ul> +<p> </p> +<p> </p> +</BODY> + +</HTML> + + +<!-- /Servlet-Specific template --> + + + </TD> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + </div> + <!--#include virtual="/footer.html" --> + </body> +</html> diff --git a/content/scproces/process.html b/content/scproces/process.html new file mode 100644 index 0000000..6f61ae8 --- /dev/null +++ b/content/scproces/process.html @@ -0,0 +1,408 @@ + +<!--#include virtual="/doctype.html" --> +<html> + <head> + + +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + + + <link href="/css/ooo.css" rel="stylesheet" type="text/css"> + <!--#include virtual="/scripts/google-analytics.js" --> + <!--#include virtual="/scripts/entourage.js" --> + </head> + <body> + <!--#include virtual="/brand.html" --> + <div id="topbara"> + <!--#include virtual="/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/scproces/">scproces</a></div> + </div> + <div id="clear"></div> + + + <div id="content"> + + + +<h2><font face="Arial, Helvetica, sans-serif" color="cc6600">Process guide</font></h2> +<br> +<P> Louis Suárez-Potts<br> +<a href="mailto:lo...@openoffice.org">lo...@openoffice.org </a></p> +<h4>Contents<a name="top"></a> <br> +</h4> +<dl> +<dt><a href="#preface">Preface</a></dt> +<dt> <a href="#I">I. Communication plan: what and when</a></dt> +<dd> <a href="#Ia">a. Project leads</a></dd> +<dd> <a href="#Ib">b. Community</a></dd> +<dt> <a href="#II">II. Inventory: files moved and files added</a></dt> +<dd> <a href="#IIa">a. Files migrated</a></dd> +<dd> <a href="#IIb">b. Files added (help files, etc.)</a></dd> + <dt> <a href="#III">III. What has changed</a></dt> +<dd> <a href="#IIIa">a. Structure</a></dd> +<dd> <a href="#IIIb">b. Little has changed in content</a></dd> +<dd> <a href="#IIIc">c. Much has changed (or can change) in spirit</a></dd> +<dd> <a href="#IIId">d. Permissions and project roles</a></dd> +<dt> <a href="#IV">IV. Creating new projects: who can do it?</a></dt> +<dd> <a href="#IVa">a. Registered users</a></dd> +<dd> <a href="#IVb">b. Project leads</a></dd> +<dd> <a href="#IVc">c. How is it done?</a></dd> +<dt> <a href="#V">V. Using project features: salient points</a></dt> +<dd> <a href="#Va">a. Documents</a></dd> +<dd> <a href="#Vb">b. News</a></dd> +<dd> <a href="#Vc">c. Issues</a></dd> +<dd> <a href="#Vd">d. Source code</a></dd> +<dt> <a href="#VI">VI. Hosted tools</a></dt> +<dt> <a href="#VIII">VII. Conclusion</a></dt> +</dl> +<br> +<h4>Preface<a name="preface"></a></h4> +<ol start=1 type=A> + <li>This is a primer: It is meant to provide insight, not to answer all questions. + Please look it over. Its main virtue: it links to the help documents that + answer specific questions. </li> + <li>OpenOffice.org is currently being migrated over to SourceCast from Tigris. + Both SourceCast and Tigris use "WebMacro" technology, which dynamically + deploys HTML pages as required. Framing each page is a static structure; this + where the navbars, headers, and footers live. </li> + <li>The similarities between Tigris and SourceCast are such that most users + would probably not notice any real difference between the two platforms. </li> + <li>However, there are clearly differences, especially in functionality, and + they are important. For instance, OpenOffice.org under SourceCast relies more + on serving up pages according to a user's (visitor's) permissions; + it is more dynamically responsive and more configurable. Mailing lists, as + well, are a little different: they are more easily managed, something users + and project leads will surely appreciate. </li> + <li>This document will go over the primary differences between Tigris OpenOffice.org + (t-OpenOffice.org) and SourceCast OpenOffice.org (sc-OpenOffice.org), focusing + on those areas that are most likely to be sources of confusion. I anticipate + that this document is but a start. There will surely be issues that are not + fully covered here and that emerge only with user experience. </li> + <li>But first: Terms. </li> + <ol start=1 type=a> + <li>In t-OpenOffice.org we use the term Project Lead and Project Owner interchangeably. + Sc-OpenOffice.org uses "project owner." In t-OpenOffice.org, + Sun project leads have domain-wide read/write privileges. In effect, a t-OpenOffice.org + project lead is a domain admin. In sc-OpenOffice.org, a project owner does + not axiomatically have such privileges. Rather, sc-OpenOffice.org distinguishes + between project owner, who has total privileges over his or her project, + and a domain admin, who has privileges over the entire ensemble of projects.</li> + </ol> + <li>And second: The current version of OpenOffice.org on SourceCast is not necessarily + the final one. Think of it as a proving ground. Indeed, one of its functions + is to provide a training ground for project leads and administrators, so that + we can all learn for ourselves how SourceCast works. That means that:</li> + <ol start=1 type=a> + <li>Comments, desires, and criticisms should be brought to CollabNet's + attention as soon as possible. I, Louis (<a + href="mailto:louis@collabnet">louis@collabnet</a>), have been appointed + the contact person for these sorts of questions. To the best of my ability, + I will address questions regarding sc-OpenOffice.org use; those questions + I cannot competently answer, I will defer to Jeff Love, who is leading the + migration. </li> + </ol> +</ol> +<p><a href="#top">Back to top</a></p> +<h3><a name="I"></a> Communication plan: what and when</h3> +<blockquote> + <p> a<a name="Ia"></a>. <u>Project leads</u>. OpenOffice.org has now two categories + of project leads: Sun and non-Sun employees. This guide addresses the concerns + of both categories of project leads; no distinction is made. In truth, this + guide provides but a start; more will be added as the week progresses and + new questions surface. As stated above, please read over this guide, and use + the Help documentation in sc-OpenOffice.org. Questions should be sent to me, + and not to the discuss list. Why? Because we haven't notified the community + yet. That will happen next week.</p> + <p> b<a name="Ib"></a>. <u>Community:</u> Goolie and Louis will work on a message + for the community, to be sent out 29 June. For the casual user OpenOffice.org + on SourceCast will make little difference. However, SourceCast does use a + registration model, and even the most casual user is automatically, if invisibly, + logged in. What is more, depending on the permissions granted a user, she + will see different aspects of the site. This will be explained to the community + at large, and the advantages of registering will be explained. All this will + be detailed in the message to be sent out 29 June. We expect that the message + will be the start of a continuing explicatory phase.</p> + <blockquote> + <p> i. There might be some resistance within the OpenOffice.org community, + for the user will, for the first time, be given the option to register, + which implies both good and bad things. The messaging will have to deal + with that. I do not, actually, anticipate too many objections, for explicit + registration will bring with it considerable advantages (project leads willing). + These will include the ability to join projects and act in a manner that + is more engaged with the work at hand. But it may also create a tiered structure, + whereby visitors who are not members see one version of the site, and registered + members who are part of projects see other parts. The simpler structure + of t-OpenOffice.org gives the appearance of a horizontality that actually + still exists within sc-OpenOffice.org, although it is more nuanced. But + the appearance of that horizontality shifts.</p> + <p> ii. To overcome some of the objections, the community will have to be + apprised of the extensive and clear site documentation (the Help and Site + FAQs) that explain sc-OpenOffice.org's functionality. Concepts such as IssueZilla, + CVS, SSH, and so on, are clearly explicated, with examples, in the Hosted + Tools section of the Help. (Note: the SSH documentation will be up-to-date + by the time the site goes live.)</p> + <p> iii. Mailing List. As well, the community will be informed of the differences. + Subscribing/unsubscribing will be the same, indeed, easier. A significant + plus, however, will be the much-longed-for introduction of searchable archives. + (Note: It is anticipated that by the time the changeover is complete, in + the middle of July, OpenOffice.org will be using a newsgroup server [NNTP]. + For the sake of simplicity and clarity, this guide won't touch on that.)</p> + </blockquote> +</blockquote> +<p><a href="#top">Back to top</a></p> +<h4> <br> + II<a name="II"></a>. Inventory: files moved and files added</h4> +<blockquote> + <p> a<a name="IIa"></a>. <u>Files Migrated. </u>All the OpenOffice.org-specific + files that make up Tigris OpenOffice.org have been successfully moved to SourceCast + OpenOffice.org. The files that will be migrated at the last minute, in the + week of July 13, include those few files that have not already been migrated, + as well as files updated since the initial migration. Until then, we should + continue to proceed normally on t-OpenOffice.org; and we should also be testing + sc-OpenOffice.org.</p> + <p> b<a name="IIb"></a>. <u>Files Added.</u> Besides the test and bogus files, + the most obvious instance of added files are those that come packaged with + SourceCast, such as the SourceCast Help files and Site FAQs.</p> + <blockquote> + <p> i. Help Files, including Site FAQ. The files included here provide a fairly + thorough primer of SourceCast and how to use it. Actually, as will become + apparent, this guide will use many of the files to explain how to set permissions, + how to load files, how to edit projects. </p> + </blockquote> +</blockquote><br> +<p><a href="#top">Back to top</a> </p> +<h4> III<a name="III"></a>. What has changed</h4> +<blockquote> + <p> a<a name="IIIa"></a>. <u>Structure</u>. Both sc-OpenOffice.org and t-OpenOffice.org + manipulate CVS files. Hence, there can only be so much difference between + the two platforms. The biggest change is that sc-OpenOffice.org doesn't automatically + support the idea of a sub-project in the same way that t-OpenOffice.org does. + Rather, sc-OpenOffice.org supports the more sophisticated concept of a "resource." + But, in both cases, what is being controlled is access to a CVS module. A + resource can be thought of as a file or group of files over to which a certain + role pertains; and precise permissions can be associated with this role. A + project owner can request that a new resource be added to his project and + that a new role be associated with this resource. Once that role is available + to the project owner (something the domain admin must do), the project owner + can then add any number of project members to that project with that role, + and he or they will <i>only</i> have access to that resource. Why? Their project + role has limited their access to other resources. And, yes, a member can have + more than one role.</p> + <blockquote> + <p> i. Example. Mary wants to create a new sub-project, "talk" within the + "VoiceRecognition" project. Solution: the project owner submits a request + to the domain admin (who can add new resources to projects) that a new resource + corresponding to "voicerecognition/talk/" be added. The domain admin must + also create a new role "talkdeveloper," say, which directly corresponds + to the new resource just created. Fred, the owner of "VoiceRecognition" + can then add Mary to the project with the new role, "talkdeveloper." + If she only has that new role (the "talkdeveloper" role), she + will only have access to that "sub-project," or more accurately, resource.</p> + <p> ii. I have no doubt that there will be questions related to this modification. + Those with domain admin privileges can work through the process by logging + in, and from their Start Page, click on "Adminster Roles" in the + top, uner "Admin Options." From there, go to the "Roles & + Resources" link on the SourceCast navbar. And add a new resource. Experiment + with the provisions of the process.</p> + <p>iii. The advantage of this method is that it allows for greater precision + and ultimately security. The drawback is that it adds a step in which the + project owner must petition (send a request to) the domain admin to implement + the desired change. However, as OpenOffice.org is growing, and including + more and more non-Sun project owners, this added step is all the clearer + an advantage.</p> + </blockquote> + <p> b<a name="IIIb"></a>. <u>Categories</u>. In the current sc-OpenOffice.org, + projects are listed by generic "category." This will change, as we do not + really need to use category at all. Rather, we can create one category: OpenOffice.org, + and transplant (with some changes to prevent an immune reaction) the current + HTML page describing the projects, leaders, and purposes. </p> + <p> c<a name="IIIc"></a>. <u>Little has changed in content.</u> This implementation + of SourceCast is similar to the current OpenOffice.org implementation on Tigris. + But there are changes, both for project owners, admins, and for registered, + regular users, though the changes a typical user will encounter are fairly + minor. Among the things that have changed, the most obvious is:</p> + <blockquote> + <p> i. The Login. This login in feature will automatically login <b>any</b> + nonregistered user as "anonymous." Registered users must log in manually + each new session. The advantages of the login feature are many, including + the ability of registered users to go automatically to their "start" page + upon logging in. This page lists those projects they have joined or created, + as well as other available projects, by category. Projects in which the + user does not have a direct role are not presented by default. For instance, + sc-OpenOffice.org creates the new concept of groups for projects and members + (see: <a +href="//project/www/docs/DomAdminUserGroups.html">//project/www/docs/DomAdminUserGroups.html</a>). + </p> + <p> ii. And, from an administrative perspective, the login feature allows + some control of information and visitor traffic, if wanted. </p> + <p> iii. Logging in. Project leads—admins—must login using their + current t-OpenOffice.org account username and password to appreciate (to + use) SourceCast's sophisticated admin features. Take, for example, the Help. + When we were constructing the help system, the idea was to accord Help files + with the user. A project leader will see a different Help set of files than + a nonregistered user. Thus, to get the most out of the Help (including the + links I am citing here), project leaders must log on. And I encourage you + to use the Help files.</p> + <p> iv. Use the Help. This is especially true right now, while this site is + under construction. For instance, all of t-OpenOffice.org's many projects + are not visible unless one enters as a domain admin. This will change, to + be sure.</p> + </blockquote> + <p> d<a name="IIId"></a>. <u>Much has changed (or can change) in spirit.</u> + The great advantage of sc-OpenOffice.org is that it encourages a more engaged + role on the part both of the visitor (who can now more easily browse through + a project and its files) and of the current project owners. </p> + <blockquote> + <p> i. Users, for instance, can now more easily (with the merest click of + a button) upload documents to the project site, project lead permitting. + And users can now "join" a project, a concept more or less impossible to + realize with t-OpenOffice.org, where one might join a most a mailing list. + This means that the micro-community making up a project will interact more + with the website element, as opposed to primarily living in the mailing + list space.</p> + </blockquote> + <p> e<a name="IIIe"></a>. <u>Permissions and project roles.</u> Perhaps the + most important change has to do with the advent of a sophisticated permissions + system which allows the project leader the ability to more easily grant specific + roles to developers who have joined his project. With t-OpenOffice.org, there + were rather few permissions at play: one could read or write or read and write + any particular module; these corresponded to the CVS modules making up the + project and determined the role of the individual. SourceCast folds in a level + of useful complexity that project leaders can take advantage of. For instance, + as I discussed above, in "Structure," a project owner can modify the permissions + of a developer to grant him or her access to particular files; or can create + new roles with a mix of permissions per file. I anticipate that this, one + of the more involved areas of the process, will generate some confusion. So:</p> + <blockquote> + <p> i. For information on roles and permissions, please see the general category + of help for project owner administration: <a +href="//project/www/docs/ProjectOwnerAdmin.html">//project/www/docs/ProjectOwnerAdmin.html</a>, + and the more specific help on permissions: <a +href="//project/www/docs/DomAdminRoles.html">//project/www/docs/DomAdminRoles.html</a>. + A good description of project roles: <a +href="//project/www/docs/ProjectRoles.html">//project/www/docs/ProjectRoles.html</a> + </p> + <p> ii. However, the best way to understand the kinds of roles and permissions + over which a project leader has access is to create a practice project and + adjust the roles and privileges of willing subjects. For the most part, + this is routine; but you can grant the user a role that elevates her beyond + the casual visitor. You can even create new roles (if not permissions) that + will allow your project to grow smoothly. As well, members of the project + may request new roles of the project lead or leads.</p> + <p> iii. In fact, you can delegate much of the responsibility of running the + project to a willing user. Yes, t-OpenOffice.org effectually offers the + same advantage; these are, after all, predicated on CVS modules. But sc-OpenOffice.org + allows greater flexibility in managing users and work on a project and in + providing valuable incentive to developers interested in joining a project. + For information on how to manage project members, please see: <a +href="http://look.openoffice.org/project/www/docs/ProjectOwnerMembers.html">http://look.openoffice.org/project/www/docs/ProjectOwnerMembers.html</a> + </p> + <p> iv. Or, you can simply leave the permissions in a state that resembles + the current condition. That is, users will only be qualified as registered + users (if that) and will have few privileges. They will still be able to + view projects, and their associated files, but they will not have the full + privileges of a registered user, let alone a more trusted user. But: there + is no special need to alter the naïve state of a developer. </p> + <p> v. Getting used to the increased sophistication of sc-OpenOffice.org permissions + will doubtless take some getting used to, as it may not be apparent to project + leads why they should change the status quo. But: if granting more rights + to registered users results in growing the project and developing the code + faster….</p> + </blockquote> +</blockquote> +<br> +<p><a href="#top">Back to top</a> </p> +<h4> IV<a name="IV"></a>. Creating new projects. who can do it</h4> +<blockquote> + <p> a<a name="IVa"></a>. <u>Registered users.</u> Any registered user can propose + a new project. Will it be accepted? That depends on the domain admin, who + must decide on the project. And who is the domain admin? It can be a person, + or a group, such as is the present case, with t-OpenOffice.org. </p> + <p> b<a name="IVb"></a>. <u>Project leads.</u> Currently, project leads can + create new projects only after the proposal has been approved by other project + leads. The same can obtain with sc-OpenOffice.org. </p> + <p> c<a name="IVc"></a>. <u>How is it done?</u> <i>Very </i>easily. Or at least + the proposal simple enough to make. For information on the procedure, please + see: <a href="//">//</a> + . I recommend that everyone go through the process of creating a project. + In creating a project, one can, initially (it can be changed later), specify + the index page content (or deploy one of your own), assign roles, invite members, + and set up mailing lists and news pages. For these reasons it is very important + that project leads be familiar with the process. </p> +</blockquote> +<p><a href="#top"><br> + Back to top</a> </p> +<h4> V<a name="V"></a>. Using project features: salient points</h4> +<blockquote> + <p> a<a name="Va"></a>. <u>Documents.</u> Currently, on t-OpenOffice.org, files + (documents, etc.) are committed to a project's modules by, usually, the project + leader. This power structure can continue into sc-OpenOffice.org., and the + project lead can continue to be the sole committer of documents. Should the + project lead wish to change the power structure, however, and allow others + who have decided to join the project to contribute documents, text, or news + items, this can easily be done by changing the permissions of the registered + users to allow it. See <a +href="http://look.openoffice.org/project/www/docs/ProjectOwnerDocuments.html">http://look.openoffice.org/project/www/docs/ProjectOwnerDocuments.html</a> + for a more detailed explanation.</p> + <p> b<a name="Vb"></a>. <u>News.</u> Each project now (or can have) have a space + in which relevant news and announcements are featured. This is an advantage + that probably does not need to be highlighted, but say there is important + news relevant to the XML project. Or that the XML project lead would like + to keep tabs on what others in XML development are doing. The project news + page could be dedicated to features related to XML. For more information on + this, please see <a +href="http://look.openoffice.org/project/www/docs/ProjectNews.htm">http://look.openoffice.org/project/www/docs/ProjectNews.htm</a> + </p> + <p> c<a name="Vc"></a>. <u>Issues.</u> Sc-OpenOffice.org makes managing issues + related to a project a quite a lot easier. Not only can the project lead now + manage issues pertaining to his or her project, but he can now more easily + track those issues and assign them. For more information on this, please see: + <a +href="http://look.openoffice.org/project/www/docs/ProjectOwnerIssues.html">http://look.openoffice.org/project/www/docs/ProjectOwnerIssues.html</a> + </p> + <p> d<a name="Vd"></a>. <u>Mailing Lists.</u> There are some changes. "All project + mailing lists are created with anzu, an open-source mail alias and list management + extension of qmail simple mail transfer protocol (smtp). Anzu supports multiple + domains, enabling each project to define and manage its own unique set of + mailing lists for the project domain." This much is familiar. As is: "If you + created your project as a standard development project, your project begins + its life with five built-in, pre-configured mailing lists." What differs is + that it is much easier for project owners/leaders to edit mailing lists: to + add/delete them, as well as modify and moderate them. For more information + on this topic, please see: <a +href="http://look.openoffice.org/project/www/docs/ProjectOwnerMailingLists.html">http://look.openoffice.org/project/www/docs/ProjectOwnerMailingLists.html</a> + </p> + <p> e<a name="Ve"></a>. <u>Source code.</u> Sc-OpenOffice.org has an option + whereby each project can control its own source code. To date, OpenOffice.org + is not so modular as that is necessary.</p> +</blockquote> +<br> +<p><a href="#top">Back to top</a> </p> +<h4> + VI<a name="VI"></a>. Hosted tools. </h4> +<blockquote> + <p> a<a name="VIa"></a>. t-OpenOffice.org's documentation page attempted to + consolidate information on the tools developers use, among other things. It + still will, but the Hosted Tools link in the Help files provide a more fluid + account of the hosted tools, such as CVS, IssueZilla, etc. Please see <a +href="http://look.openoffice.org/project/www/docs/hostedtools.html">http://look.openoffice.org/project/www/docs/hostedtools.html</a> + . (For what it is worth, OpenOffice.org is still unique in using SSH2, so + that element in the help files will be changed.</p> +</blockquote> +<br> +<p><a href="#top">Back to top</a> </p> +<h4> VII<a name="VII"></a>. Conclusion. </h4> +<blockquote> + <p> a. The work that has to bed done until the new OpenOffice.org goes live + will focus on accommodating the legacy OpenOffice.org to the new structure. + For project leads, the primary focus should be on becoming familiar with managing + projects and project members. The help files are of inestimable value in this; + as are the site FAQs, which I have not touched on at all. </p> +</blockquote> + + + + </div> + <!--#include virtual="/footer.html" --> + </body> +</html> diff --git a/content/servlets/Join/index.html b/content/servlets/Join/index.html new file mode 100644 index 0000000..d134902 --- /dev/null +++ b/content/servlets/Join/index.html @@ -0,0 +1,32 @@ +<!--#include virtual="/doctype.html" --> +<html> + <head> + + <title>Joining the OpenOffice Project</title> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> + + + <link href="/css/ooo.css" rel="stylesheet" type="text/css"> + <!--#include virtual="/scripts/google-analytics.js" --> + <!--#include virtual="/scripts/entourage.js" --> + </head> + <body> + <!--#include virtual="/brand.html" --> + <div id="topbara"> + <!--#include virtual="/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/servlets/">servlets</a> » <a href="/servlets/Join/">Join</a></div> + </div> + <div id="clear"></div> + + + <div id="content"><h1 class="title">Joining the OpenOffice Project</h1> + + <h2><a href="#joining-the-apache-openoffice-project" id="joining-the-apache-openoffice-project">Joining the Apache OpenOffice project</a></h2> +<p>If you want to learn more about volunteering with the Apache OpenOffice project, please go <a href="http://openoffice.apache.org/get-involved.html">here</a></p> +<p>If you want to sign up for Apache OpenOffice mailing lists, the information you want is <a href="http://openoffice.apache.org/mailing-lists.html">here</a></p> + + + </div> + <!--#include virtual="/footer.html" --> + </body> +</html> diff --git a/content/servlets/ReadMsg/index.html b/content/servlets/ReadMsg/index.html new file mode 100644 index 0000000..69b0660 --- /dev/null +++ b/content/servlets/ReadMsg/index.html @@ -0,0 +1,31 @@ +<!--#include virtual="/doctype.html" --> +<html> + <head> + + <title>OpenOffice.org Mailing List Archives</title> + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> + + + <link href="/css/ooo.css" rel="stylesheet" type="text/css"> + <!--#include virtual="/scripts/google-analytics.js" --> + <!--#include virtual="/scripts/entourage.js" --> + </head> + <body> + <!--#include virtual="/brand.html" --> + <div id="topbara"> + <!--#include virtual="/topnav.html" --> + <div id="breadcrumbsa"><a href="/">home</a> » <a href="/servlets/">servlets</a> » <a href="/servlets/ReadMsg/">ReadMsg</a></div> + </div> + <div id="clear"></div> + + + <div id="content"><h1 class="title">OpenOffice.org Mailing List Archives</h1> + + <h2><a href="#accessing-the-openofficeorg-mailing-list-archives" id="accessing-the-openofficeorg-mailing-list-archives">Accessing the OpenOffice.org Mailing List Archives</a></h2> +<p>Sorry, but the mailing list archive you queried no longer exists at that address. However, a complete copy of the OpenOffice.org archives is hosted by <a href="http://openoffice.markmail.org/">MarkMail</a>.</p> + + + </div> + <!--#include virtual="/footer.html" --> + </body> +</html> diff --git a/content/servlets/readme.txt b/content/servlets/readme.txt new file mode 100644 index 0000000..71fd6b4 --- /dev/null +++ b/content/servlets/readme.txt @@ -0,0 +1,7 @@ +Note: This directory is not really for servlets. It is here to offer landing pages for the many external +links to the legacy OpenOffice.org website that pointing to servlets used by the legacy website for +signing up volunteers, reading list archives, joining mailing lists, etc. + +The directory structure here mimics the legacy servlet calls but substitutes static webpages +that direct the user to the appropriate content. +