Craig L Russell wrote:
>
> On Jul 28, 2009, at 3:50 PM, Ralph Goers wrote:
>
>> That doesn't seem right either. I think members should still be able
>> to access it read-only.
>
> Fair enough. I just don't think it should be readable by the public.
But members? Why not just authenticated commi
On Jul 28, 2009, at 3:50 PM, Ralph Goers wrote:
On Jul 28, 2009, at 2:32 PM, Craig L Russell wrote:
I think we need to consider the risk to Apache of leaving the svn
repo in a r/o state.
According to the XAP status page, http://incubator.apache.org/projects/xap.html
the copyright and di
Carsten - Sorry to see you go.
All - I have been thinking a lot about the project and part of my
problem is being unsure of what documentation needs to be included in
the project so we can get a release out. Luciano has done a fabulous
job so far and I would hate to see the project go any mor
On Jul 28, 2009, at 2:32 PM, Craig L Russell wrote:
I think we need to consider the risk to Apache of leaving the svn
repo in a r/o state.
According to the XAP status page, http://incubator.apache.org/projects/xap.html
the copyright and distribution rights have not been verified, so
IMHO
I think we need to consider the risk to Apache of leaving the svn repo
in a r/o state.
According to the XAP status page, http://incubator.apache.org/projects/xap.html
the copyright and distribution rights have not been verified, so
IMHO the repository has not been vetted.
I think we shoul
Clearly my chance never came, so let's make it happen now.
The task itself is trivial - send an email to each email address listed
in a file once a month, using a different file for each of a three month
rotation cycle.
Now, the questions are:
1. What date do we send the email out on?
2. Do we
