Ted,
I just setup the requested forums for XWork:
http://forums.opensymphony.com/category.jspa?categoryID=19
Next step is to setup the mailing lists. We still use the java.net
infrastructure for our mailing lists.
I need karma to add those mailing lists and setup (Pinging Jason/
Patrick for
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 ? Wi
I am willing and spending lots of my free time on Struts 2, XWork and
(still) WebWork 2.2.X. to bring this projects to high quality products as
lots of the other developers are doing, but I need more feedback to get
more of the envolved developers in. There are some open issues in Jira
where I cal
On 1/1/07, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
Before the merge, I was spending a lot of my spare time contributing
to WW and on the XWork side along with Rainer, Jason, and occasionally
a couple of more guys. The direction was clear for everybody and
everybody knew where we are heading
On 12/31/06, Rainer Hermanns <[EMAIL PROTECTED]> 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, JI
Happy new year guys. :-)
WebWork just like any other open-source project follows the open-source
spirits. It is very much driven by the community itself. Features are often
implemented when they are substantial enough, it doesn't matter if it
originated from users, commiters or the project lead
To fight philosophy with philosophy ;), the goal of Struts 2 has been
pretty much the same since we started: to simplify web development to
create a more developer-friendly framework. We've been following the
Struts Ti plan [1] roughly since late 2005. WebWork was brought on
board as it was t
First of all Happy New Year to everyone! and then a bit of a
philosophical email - something related to previous post by Rainer and
something that bothered me for the last couple of months.
Before the merge, I was spending a lot of my spare time contributing
to WW and on the XWork side along
As a first follow up, happy new year to everyone.
As Pat mentioned, the infrastructure at OpenSymphony does not have the
rules and bounds Apache has.
I have no problem to release milestones, dot releases or the like, but I
want to achieve that certain issues are fixed and targets were reached for
Ted,
Your suggestions all sound very reasonable. Rainer and I would be happy to help
set this up (I can do the forums/infrastructure, and I'm sure Rainer can help
by giving releases more compatible version numbers in the future).
---
At one point wasn't there talk of bring xwork into the apache fold. Is
that still an option or is that off the table? It seems to me that
since xwork is such a critical piece of struts2 that it should be part
of apache and not opensymphony. Then xwork would be forced to follow
the apache pro
As it stands, XWork is a "stealth" project using a beta/rc release system.
Working with XWork from Struts is problematic because
* There are no visible mailing lists that track project status
* There are no forums in which to discuss XWork 2 specific issues,
including the release roadmap and th
12 matches
Mail list logo
