Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.227 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Top level question on website migration
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <237677.35349.qm@web161426.mail.bf1.yahoo.com>
Date: Mon, 27 Jun 2011 14:43:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <074744E5-1EFB-416B-9636-69D5B58621EA@comcast.net>
References: <BANLkTimqYnNEvzMqt5MVrVSi+JGbyNYnZw@mail.gmail.com>
 <4E0897F8.6000402@gmail.com>
 <BANLkTinZ6psxkV9G_Jsh_4Viu4FSWe4_xA@mail.gmail.com>
 <4E089E95.60106@gmail.com>
 <BANLkTi=Lcfb5RV7z8Cf+OyvA2KEb1JWN5g@mail.gmail.com>
 <4AE3EAEA-11A9-4C85-9232-2F96E25D128F@comcast.net>
 <BANLkTi=MA3ebmDa5cG8DP=zHQJ0W2tG0Pg@mail.gmail.com>
 <EBD2EDB9-8FFE-49FC-A7C9-B2CD762B75C1@comcast.net>
 <20110627190526.GA5409@daniel3.local>
 <BANLkTi=DKeF+D41gmH7WbOLF1cycoyW62w@mail.gmail.com>
 <167854.80737.qm@web161428.mail.bf1.yahoo.com>
 <BANLkTikACbBFYP3-ov1A-7VbWMq_8M5B8w@mail.gmail.com>
 <497335.3990.qm@web161423.mail.bf1.yahoo.com>
 <BANLkTikB4coHjX_HpwKuLsbiDSsBiLPoGg@mail.gmail.com>
 <898868.16827.qm@web161422.mail.bf1.yahoo.com>
 <E8CA7B3E-6A3F-4CD7-9276-4178AB41314B@comcast.net>
 <627364.9323.qm@web161424.mail.bf1.yahoo.com>
 <00D9B169-D15F-4357-BDF5-6003CF8C1C5A@comcast.net>
 <237677.35349.qm@web161426.mail.bf1.yahoo.com>
To: ooo-dev@incubator.apache.org


On Jun 27, 2011, at 2:10 PM, Joe Schaefer wrote:

>=20
>=20
> ----- Original Message ----
>> From: Dave Fisher <dave2wave@comcast.net>
>> To: ooo-dev@incubator.apache.org
>> Sent: Mon, June 27, 2011 5:04:27 PM
>> Subject: Re: Top level question on website migration
>=20
>> Gotcha. Whatever Web Interface needs to be narrow,  well-defined, =
bullet proof=20
>> and well tested with a committed team behind  it.
>=20
> Easier said than done IME.  Writing client-side apps like OOo and =
writing
> public server-side apps are completely different animals.  It's better =
to
> go without than to put up something that's poorly done IMO.

Yes, I had a very big learning curve ten years ago. I've project managed =
/ led development of some B2B sites for the past 11 years.

I'm not bringing client side app writing chops to OOo, I'm bringing =
non-OOo document experience with PDF and MS Office. We generate such =
from our work websites. Creating and assembling content according to =
user's requests and producing PPT and PDF on the fly.

We've also done some development with Excel Plug-ins that talk to our =
website and exchange data.

I'm not afraid of it, but for this one we need to be very careful.

>> So, we at AOOo would have to prove we have the community and  =
procedures in=20
>> place in order to get to this point.
>>=20
>> Whatever we might do  starts on a private site, or in an approved =
Apache jail.=20
>> And if so the choices  are here,=20
>> http://www.apache.org/dev/services.html#virtual-servers,  correct?
>=20
> The solaris zone stuff is outdated.  We've replaced zones with freebsd =
jails.
> Otherwise you'd get a vmware instance, and if it's linux you want we'd =
install
> ubuntu.

Glad I asked.

Regards,
Dave