Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8B54410799 for ; Sat, 10 Aug 2013 11:14:54 +0000 (UTC) Received: (qmail 50300 invoked by uid 500); 10 Aug 2013 11:14:53 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 49862 invoked by uid 500); 10 Aug 2013 11:14:44 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 49846 invoked by uid 99); 10 Aug 2013 11:14:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Aug 2013 11:14:43 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates 209.85.217.181 as permitted sender) Received: from [209.85.217.181] (HELO mail-lb0-f181.google.com) (209.85.217.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Aug 2013 11:14:39 +0000 Received: by mail-lb0-f181.google.com with SMTP id o10so3804395lbi.12 for ; Sat, 10 Aug 2013 04:14:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VOOZbV3MRlhI2zFhHygaHMaOdeakRTgkO6OixrAhu2c=; b=QmZGNIF1Yo+DHWiifQiVvex/4JA/gM7VvK8j6o/co8ZMlpnxxiMm9b0Mo04h3R1xjS 6ebVHhqMDJIeUM0C6smRjGeR0QHoW+JyO0KlA8chC/FOpG73nPfThqvV3rw4MZBzBxQn cc6cZZB8M1UUUSlHRPwhINepdsau4q8RVf9U1hOPrW94DNRkF6Tu9OfzTCHZFgAQVYZe wYLF8eheFRWpLIOUOUMfZsQdYpPzctlXkuFX7MEc45xyDOMqrQ/Qnpnq1u88FryGa+hk k8mOfm5ZUO8taXLGUkACX5nGor7YarMmF67Fdm8RkrmpZNPBeH83nQfXMykjl1uTKU+7 hgCQ== MIME-Version: 1.0 X-Received: by 10.152.115.176 with SMTP id jp16mr5278202lab.17.1376133257767; Sat, 10 Aug 2013 04:14:17 -0700 (PDT) Received: by 10.114.184.99 with HTTP; Sat, 10 Aug 2013 04:14:17 -0700 (PDT) In-Reply-To: <51FBA8EC.5060606@cord.dk> References: <51FBA8EC.5060606@cord.dk> Date: Sat, 10 Aug 2013 07:14:17 -0400 Message-ID: Subject: Re: [DISCUSS] Dropping the E-word from mod_lua (SFW) From: Jeff Trawick To: Apache HTTP Server Development List Content-Type: multipart/alternative; boundary=001a11c35096fe337204e395fdf8 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c35096fe337204e395fdf8 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Aug 2, 2013 at 8:41 AM, Daniel Gruno wrote: > Hi dev@, > Though this is mainly a question for docs@, I thought I'd drop this > email into the dev@ list instead, since this is where I think > objections, if there are any, will arise. > > Today, on various Internet channels, I have had to do my very best to > defend the use of mod_lua, ranging from people asking if it's safe to > use to people claiming that it should never be used in a production > environment. Why? because of one word in particular: Experimental. > > In our documentation, we write the following: > ---- > mod_lua is still in experimental state. Until it is declared stable, > usage and behavior may change at any time, even between stable releases > of the 2.4.x series. Be sure to check the CHANGES file before upgrading. > ---- > > To a committer/programmer, this may seem totally sane, but to a user of > httpd - and I sincerely hope that users are our aim in the documentaion > - this wording screams "BACK OFF, this may explode at any given time!". > As a "long time" developer and user of httpd/mod_lua for both personal > and professional sites/manoeuvres/jobs, I find it sad that I have to > defend a module in otherwise perfect working condition with no > discernible faults at all, simply because of a wording that scares off > regular users of httpd. So I'd really like to change the wording into > something less scary, so users can both know that it's still in a > development phase, but it won't blow up your computer or spread germs if > you use it on a production server. > > I'd like to change the note to something along these lines: > ---- > mod_lua is in a state of continuous development. Usage > and behavior is subject to change at any time, even between stable > releases of the 2.4.x series. Be sure to check the CHANGES file before > upgrading > ---- > That text sounds fine but I don't see that as being reassuringly non-"Experimental" from the point of an enterprise distributor or a site administrator. Given that declaration, it would be naive to make your production site dependent on a fair amount of interesting code for mod_lua unless you think you can drop everything to tweak your scripts in order to pick up a httpd security fix at some arbitrary future time, or you can watch mod_lua development steadily to be prepared ahead of time. "Status: Experimental" is the flag we have to say "watch out for this module", which seems appropriate still. > > From a programming point of view, I can understand if there are > reservations towards this change, but I ask you to look at it from a > user point of view, and I hope you'll welcome this proposal for change. > > I hope we won't have to put something as tiny as this to a vote, and if > I do not hear any strong objections within the next 72 hours, I will > assume lazy consensus and commit this change to the documentation. > > With regards, > Daniel. > -- Born in Roswell... married an alien... http://emptyhammock.com/ --001a11c35096fe337204e395fdf8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Aug 2, 2013 at 8:41 AM, Daniel Gruno <rumble@cord.dk= > wrote:
Hi dev@,
Though this is mainly a question for docs@, I thought I'd drop this
email into the dev@ list instead, since this is where I think
objections, if there are any, will arise.

Today, on various Internet channels, I have had to do my very best to
defend the use of mod_lua, ranging from people asking if it's safe to use to people claiming that it should never be used in a production
environment. Why? because of one word in particular: Experimental.

In our documentation, we write the following:
----
mod_lua is still in experimental state. Until it is declared stable,
usage and behavior may change at any time, even between stable releases
of the 2.4.x series. Be sure to check the CHANGES file before upgrading. ----

To a committer/programmer, this may seem totally sane, but to a user of
httpd - and I sincerely hope that users are our aim in the documentaion
- this wording screams "BACK OFF, this may explode at any given time!&= quot;.
As a "long time" developer and user of httpd/mod_lua for both per= sonal
and professional sites/manoeuvres/jobs, I find it sad that I have to
defend a module in otherwise perfect working condition with no
discernible faults at all, simply because of a wording that scares off
regular users of httpd. So I'd really like to change the wording into something less scary, so users can both know that it's still in a
development phase, but it won't blow up your computer or spread germs i= f
you use it on a production server.

I'd like to change the note to something along these lines:
----
mod_lua is in a state of continuous development. Usage
and behavior is subject to change at any time, even between stable
releases of the 2.4.x series. Be sure to check the CHANGES file before
upgrading
----

That text sounds fine but I don= 9;t see that as being reassuringly non-"Experimental" from the po= int of an enterprise distributor or a site administrator. =A0Given that dec= laration, it would be naive to make your production site dependent on a fai= r amount of interesting code for mod_lua unless you think you can drop ever= ything to tweak your scripts in order to pick up a httpd security fix at so= me arbitrary future time, or you can watch mod_lua development steadily to = be prepared ahead of time. =A0"Status: Experimental" is the flag = we have to say "watch out for this module", which seems appropria= te still.
=A0

>From a programming point of view, I can understand if there are
reservations towards this change, but I ask you to look at it from a
user point of view, and I hope you'll welcome this proposal for change.=

I hope we won't have to put something as tiny as this to a vote, and if=
I do not hear any strong objections within the next 72 hours, I will
assume lazy consensus and commit this change to the documentation.

With regards,
Daniel.



--
Born in Rosw= ell... married an alien...
http://emptyhammock.com/
--001a11c35096fe337204e395fdf8--