Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (herse.apache.org: domain of philip.luppens@gmail.com
 designates 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=OIxvbqdYjXEMdh5si11lThHQwlJG01MPDVd9FPXBn7vUHFxxNO+4DxTWBSBKSWWajuRjbqJOIMftBtaUd+aGQy2tj9KtmuoCncFJq7oXinjdo21mMtBix8iy6bfQr5OxqSY4OI2NX/xl7DlR7ttD3dC3BzZOCyBGNC+Q5sPd4vw=
Message-ID: <74ac90460701020152l7bc49e2cqf85e6d6ac63f37ca@mail.gmail.com>
Date: Tue, 2 Jan 2007 10:52:34 +0100
From: "Philip Luppens" <philip.luppens@gmail.com>
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: [S2] XWork Status Quo
In-Reply-To: <8b3ce3790701011311l5c0467a7x1285f97123b7f06c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_175360_18541855.1167731554731"
References: <8b3ce3790612311155i54f717f5o7f2b021465a6da88@mail.gmail.com>
	 <5494678.1167602943685.JavaMail.os-j2ee@opensymphony01.managed.contegix.com>
	 <50047.217.235.210.39.1167619318.squirrel@strato.aixcept.de>
	 <8b3ce3790701011311l5c0467a7x1285f97123b7f06c@mail.gmail.com>

------=_Part_175360_18541855.1167731554731
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Where would these mailing list/forum/chat/.. be located ? I can create an
XWork forum over at OpenSymphony in a moment, but I think we need Patrick to
set up the mailing list (but we can sync to an apache mailing list as well).
Would it be better to go for XWork 2 or an XWork forum in general ? With all
this Apache/OS crossing, I could use a little guidance if you guys want me
to do something useful.

Happy 2007 everyone,

Phil

On 1/1/07, Ted Husted <husted@apache.org> wrote:
>
> On 12/31/06, Rainer Hermanns <hermanns@aixcept.de> wrote:
> > Thoughts?
>
> I think the way to address any problems with XWork involvement is to
> followup on Patrick's post and create the usual project
> infrastructure: A user list, a dev list, and a commits lists for the
> automatic posts from Subversion, JIRA, and Confluence.
>
> I also think it would be helpful if we distributed the bits and let
> the community decide if the they are GA or not. It's fine to have a
> roadmap, but a roadmap is artificial. The map is not the land. If the
> community tells us the bits are ready for primetime, then we should
> not let a roadmap stand in the way of a "General Availability"
> release.
>
> Documentation is a great way to build community, but we don't deploy
> documentation. Meanwhile, the quickest way to destroy community is to
> never create a production-ready release, which is what is happening
> now.
>
> So, please, lets setup the usual lists for XWork, and dub the next
> XWork 2 distribution XWork 2.0.3. Then we can distribute it with
> Struts 2.0.3, and let the community tell us if the bits are ready for
> primetime or not.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


-- 
iDTV System Engineer
"Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live." - John F. Woods

------=_Part_175360_18541855.1167731554731--