Author: jleroux
Date: Mon Jun 20 20:22:06 2016
New Revision: 1749396
URL: http://svn.apache.org/viewvc?rev=1749396&view=rev
Log:
Fixes misc. minor syntax issues
Modified:
ofbiz/site/apache-ofbiz-getting-started.html
ofbiz/site/apache-ofbiz-project-overview.html
Modified: ofbiz/site/apache-ofbiz-getting-started.html
URL:
http://svn.apache.org/viewvc/ofbiz/site/apache-ofbiz-getting-started.html?rev=1749396&r1=1749395&r2=1749396&view=diff
==============================================================================
--- ofbiz/site/apache-ofbiz-getting-started.html (original)
+++ ofbiz/site/apache-ofbiz-getting-started.html Mon Jun 20 20:22:06 2016
@@ -39,11 +39,11 @@
<!-- content-wrap starts -->
<div id="content-wrap" class="clearfix">
<div id="main">
- <h2>Apache OFBiz® Getting Started</h3>
+ <h2>Apache OFBiz® Getting Started</h2>
<h3>The What, Why and How of Apache OFBiz</h3>
-<P>The basic structure and driving force behind OFBiz has a lot to do with the
goals and actualization of the release process.</p>
+<p>The basic structure and driving force behind OFBiz has a lot to do with the
goals and actualization of the release process.</p>
<p>OFBiz is and always has been a community-driven open source project. There
is no central commercial organization that drives the development of OFBiz or
derives a project from the intellectual property of the software or other
project assets. This is formalized now that OFBiz is a project in the Apache
Software Foundation.</p>
<p>Because of this OFBiz always has been and always will be just what users
who contribute to the project want it to be. There are many different
individuals and groups involved with many different needs and our goal is to
define and follow development and release policies that serve the needs of
these parties.</p>
<p>So, let's start with that...</p>
@@ -51,21 +51,21 @@
<h3>How Do I Decide What to Use?</h3>
<p>From a project user perspective there is one main question that can help
determine which way they will want to get OFBiz: <b>Do I want to contribute to
the open source project?</b></p>
-<p>For this question there are 3 main answers:
+<p>For this question there are 3 main answers:</p>
<ol>
<li><b>Yes, definitely</b>: I want to contribute to design, coding, and
testing efforts and thereby collaborate with others to more effectively and
efficiently satisfy the long-term requirements from me, my clients, or my
employer</li>
<li><b>Kind of</b>: I want to stay on the cutting edge and participate
with testing and feedback, but I'm not in a position to participate in
development and/or in the near future I will need something more reliable and
supported and that won't change very much</li>
<li><b>Not really</b>: I'm happy to offer feedback, but I really need
something that will work well now and well into the future so we can get things
going in our organization</li>
</ol>
-</p>
-<p>For each answer there is a recommended way to get OFBiz:
+
+<p>For each answer there is a recommended way to get OFBiz:</p>
<ol>
<li>Get the code straight from the code repository (SVN) <b>trunk</b> and
update frequently through development, stopping before your integration or
final pre-deployment testing, and periodically even after production deployment
according to your ongoing develop/deploy plan; note that when you are not
updating from SVN you should continue to watch the commits for bug fixes to
patch into your code base</li>
<li>Get the code from the code repository (SVN) <b>release branch</b> and
keep updated or patched regularly as fixes are committed and the branch
stabilizes over time; when getting started choose the most recent branch, even
if it is very new; when new release branches are created update to them soon
after the branch is done</li>
<li>Get a built release package or the code from a release branch tag, and
update as new pre-built release packages and tags are created; these will only
represent fixes and unless a major issue arises they will be backward
compatible and generally safe to update or patch to; when getting started
choose a release branch that has been around for at least 2-3 months and that
has no major outstanding issues in the issue tracker to assure that it has
stabilized; when new release branches are created wait until you are ready to
do a major upgrade and possibly need to modify your code and configuration, and
wait at least until the prospective branch has stabilized before moving to
it</li>
</ol>
-</p>
+
</div>
<!-- main ends -->
Modified: ofbiz/site/apache-ofbiz-project-overview.html
URL:
http://svn.apache.org/viewvc/ofbiz/site/apache-ofbiz-project-overview.html?rev=1749396&r1=1749395&r2=1749396&view=diff
==============================================================================
--- ofbiz/site/apache-ofbiz-project-overview.html (original)
+++ ofbiz/site/apache-ofbiz-project-overview.html Mon Jun 20 20:22:06 2016
@@ -240,8 +240,8 @@ Campaigns including advertisements, part
<h4>Work Effort</h4>
<p>A Work Effort can be one of many things including a task, project, project
phase, to-do item, calendar item, or even a Workflow Activity.</p>
<p><b>Notice</b> : OFBiz gave up on Workflow Engines. Shark was implemented
last but never really used in OFBiz. Instead of
-using a Workflow Engine, OFBiz uses an <A
href="http://en.wikipedia.org/wiki/Event_Driven_Architecture";
class="external-link"
- rel="nofollow">Event Driven Architecture (EDA)</A> and ECAs (SECA,
EECA, MECA) are used in OFBiz to drive the Workflow. ECA is the
+using a Workflow Engine, OFBiz uses an <a
href="http://en.wikipedia.org/wiki/Event_Driven_Architecture";
class="external-link"
+ rel="nofollow">Event Driven Architecture (EDA)</a> and ECAs (SECA, EECA,
MECA) are used in OFBiz to drive the Workflow. ECA is the
acronym of Event Condition Action. SECAs are for Services (triggered on
services conditions), EECA are for Entity (triggered on
entities conditions), MECAs are for Mail.</p>
<!--
