Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (nike.apache.org: domain of cmoulliard@gmail.com designates
 209.85.220.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=GtofEgk0OJ8SH1XK0qGbEeUG0d2Rv4LW2Edh5qw0EwMP/CgVNVQK6Nfokiv+0cVmCu
         ynbD+4BmoDc9I6FpRYmrUKKiyr+IU+jiOB4ZXN/zcJDpqYDtbO95BdOxRd+LWp8GC4U2
         94RKZZEJRxx52co/DTzSft9eaik3mOYOd10fM=
MIME-Version: 1.0
In-Reply-To: <4D83700C.2070606@gmail.com>
References: <AANLkTinG2S0YXDAD_YJRYmKBahYvRfES+TZrRR_nEF1=@mail.gmail.com>
	<AANLkTi=LuVUyLwpzJEn8Mb_afYmzE8vf8-NrDMRJgXkN@mail.gmail.com>
	<4D8333D0.1030100@gmail.com>
	<OF32BC334D.8DC8D4B4-ON80257857.003D8353-80257857.003E709A@uk.ibm.com>
	<AANLkTimFZFEJHgtUzGyrzEQf_Db4zG36rWXzJWGGer5F@mail.gmail.com>
	<4D83675C.1080708@gmail.com>
	<4D8368D6.6050105@gmail.com>
	<AANLkTi=PT6=JFCyqFRukNxxNrki7wGdRjkydybbjtsQa@mail.gmail.com>
	<4D83700C.2070606@gmail.com>
Date: Fri, 18 Mar 2011 16:15:14 +0100
Message-ID: <AANLkTi=oUjMvG4N-+Wi=D7fgGqJcHhkknfcCOzwdBTn0@mail.gmail.com>
Subject: Re: Permissions for changing the web site
From: Charles Moulliard <cmoulliard@gmail.com>
To: zoe slattery <zoe.slattery@gmail.com>
Cc: dev@aries.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Zoe,

As a Aries Commiter, you have the rights to commit something into SVN
which is not the case for me. So I cannot commit using svn -->

Charles-Moulliards-MacBook-Pro:modules charlesmoulliard$ svn commit -m
"Add text"
Sending        modules/jpaproject.mdtext
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden) in response
to CHECKOUT request for
'/repos/asf/!svn/ver/1082937/aries/site/trunk/content/modules/jpaproject.md=
text'

The procedure requiring a patch from CMS + open a ticket in Jira to
commit the patch seems too complicated and in fact does not work (see
ticket https://issues.apache.org/jira/browse/ARIES-597)

So what solution do you suggest to simplify the procedure for persons
who would like to improve Aries Documentation and (provide grants on
aries-site for apache committers which are not Aries committer, ....)
?

Regards,

Charles
On Fri, Mar 18, 2011 at 3:45 PM, zoe slattery <zoe.slattery@gmail.com> wrot=
e:
> On 18/03/2011 14:19, Charles Moulliard wrote:
>>
>> Here is a new patch that you can use to make a test
>>
> OK - not exactly sure what you wanted me to do with this but this is what=
 I
> did:
>
> Copied your file to patch.txt
> Changed directory to where my site is checked out (aries/site)
> cd content/modules
> patch < patch.txt
> used svn diff to check that it had been applied
> svn commit -m "Apply CM patch"
>
> So, this was pretty straightforward. The checkin generates a staging buil=
d
> of the site, your change is visible here:
>
> http://aries.staging.apache.org/modules/jpaproject.html
>
> So, I'm not sure what the issue was?
>
> Zoe
>
>> On Fri, Mar 18, 2011 at 3:14 PM, zoe slattery<zoe.slattery@gmail.com>
>> =A0wrote:
>>>>>
>>>>> =A0Then the committer applying the patch
>>>>> also needs the full site checked out and configured to build.
>>>>
>>>> This is not true. You should just be able to check out, apply patch,
>>>> commit and use the CMS tooling to verify.
>>>
>>> Hmm - on second thoughts - strictly speaking you are right.
>>>
>>> Z
>>>
>>>>>>
>>>
>
>