2013/9/4 Steven Benitez :
> I know it's the plan to move to Git, but that can't happen soon enough.
> Subversion is like a big cloud of sadness.
>
> On the bright side, it would be great to get a concerted effort at creating
> new documentation. I'd be happy to help.
One thing to think of when mig
Am 05.09.13 07:51, schrieb Lukasz Lenart:
> Argh.
:-)
> 2013/9/4 Christian Grobmeier :
>> When I first looked at Struts, the website was a mess. It still is (but
>> we're working on it). I was confused by countless topics. It is in my
>> genes to look at the source code immediately, but the Str
Hello folks,
given our recent discussions on the documentation I have started to
rework the Struts main page.
Please find it here:
http://svn.apache.org/repos/asf/struts/site/branches/next/
I have already pinned a lot of my "visions" here and would like to
invite you to check it out and help mak
Am 09.09.13 11:32, schrieb Lukasz Lenart:
> 2013/9/4 Steven Benitez :
>> I know it's the plan to move to Git, but that can't happen soon enough.
>> Subversion is like a big cloud of sadness.
>>
>> On the bright side, it would be great to get a concerted effort at creating
>> new documentation. I'd
Am 05.09.13 10:35, schrieb Lukasz Lenart:
> 2013/9/5 Christian Grobmeier :
>>> I had a reason to add all those src/site's ;-)
>> Is the reason still valid?
> I cannot recall what it was ;-) So maybe it ins't valid anymore ;-)
>
>> I have no problem keeping them, as I found out how to remove it from
As you might know, we had a hackathon this weekend in Augsburg, Germany
(http://strutsathon.opensource.io/) where we experimented a bit with
available options and requierements.
One of the outcomes was that we may want to start with a "real" user
guide that helps to get started and addresses commo
Am 05.09.13 21:22, schrieb Lukasz Lenart:
> 2013/9/5 Christian Grobmeier :
>> Am 05.09.13 20:43, schrieb Lukasz Lenart:
>>> Guys,
>>>
>>> are you serious? are you blaming OGNL? the hammer? 100% of
>>> vulnerability related to OGNL was our - developers - fault. We did use
>>> (and still do) the hamm
While this isn't a full review, some first impressions:
- Landing page: Key Technologies section (left bottom div) is redundant
given the Technology Primer link in the hero bar. I would rather
recommend to place the most important announcement (such as security
announcement / latest release info)
Makes sense, I changed everything as you said. Thanks, and keep the
comments coming!
Am 09.09.13 13:39, schrieb Rene Gielen:
> While this isn't a full review, some first impressions:
>
> - Landing page: Key Technologies section (left bottom div) is redundant
> given the Technology Primer link in t
Hi,
I thought a bit about our docs - for each main branch we provide docs,
i.e. /release/2.3.x/, /release/2.2.x/ etc. We also expose draft docs
as /development/2.x - all thus leads to mess when we must update
something or so.
So maybe just instead of many places with docs we should expose the
lat
10 matches
Mail list logo