Account on sourceware.org for write access to gcc project

Account on sourceware.org for write access to gcc project

[Thierry LAFAGE]

Hi,

In order to obtain write access to the GCC project on the CLI back-end 
branch (svn://gcc.gnu.org/svn/gcc/branches/st), I filled in the 
mentioned form (http://sourceware.org/cgi-bin/pdw/ps_form.cgi). Then 
Erven Rohou approved my request.
Since then, I have no news, not even an acknowledgement e-mail for my 
request.
So, I dare to post in this list to ask: is this normal?
What should I do now?

Kind regards,

Thierry Lafage.

Re: Account on sourceware.org for write access to gcc project

[Christopher Faylor]

On Fri, Dec 11, 2009 at 05:28:15PM +0100, Thierry LAFAGE wrote:
>Hi,
>
>In order to obtain write access to the GCC project on the CLI back-end 
>branch (svn://gcc.gnu.org/svn/gcc/branches/st), I filled in the 
>mentioned form (http://sourceware.org/cgi-bin/pdw/ps_form.cgi). Then 
>Erven Rohou approved my request.
>Since then, I have no news, not even an acknowledgement e-mail for my 
>request.
>So, I dare to post in this list to ask: is this normal?
>What should I do now?

Sorry.

This fell through the cracks but, unfortunately, you have not followed
the right procedure to acquire write access.  Even Rohou has
"write-after-approval" and does not have the authority to sponsor
anyone for write access to the gcc repository.

You'll need to get approval from a non-write-after-approval maintainer.

Re: Account on sourceware.org for write access to gcc project

[Thierry LAFAGE]

Ok, thank you.
BTW, in http://gcc.gnu.org/svnwrite.html, I did not see that I needed to 
get approval from a non-write-after-approval maintainer.

I'll try and find one.

Regards,

Thierry Lafage.


Le 11/12/2009 17:34, Christopher Faylor a écrit :
> On Fri, Dec 11, 2009 at 05:28:15PM +0100, Thierry LAFAGE wrote:
>
>> Hi,
>>
>> In order to obtain write access to the GCC project on the CLI back-end
>> branch (svn://gcc.gnu.org/svn/gcc/branches/st), I filled in the
>> mentioned form (http://sourceware.org/cgi-bin/pdw/ps_form.cgi). Then
>> Erven Rohou approved my request.
>> Since then, I have no news, not even an acknowledgement e-mail for my
>> request.
>> So, I dare to post in this list to ask: is this normal?
>> What should I do now?
>>
> Sorry.
>
> This fell through the cracks but, unfortunately, you have not followed
> the right procedure to acquire write access.  Even Rohou has
> "write-after-approval" and does not have the authority to sponsor
> anyone for write access to the gcc repository.
>
> You'll need to get approval from a non-write-after-approval maintainer.
>

Re: Account on sourceware.org for write access to gcc project

[Christopher Faylor]

On Fri, Dec 11, 2009 at 05:59:02PM +0100, Thierry LAFAGE wrote:
>Ok, thank you.
>BTW, in http://gcc.gnu.org/svnwrite.html, I did not see that I needed to 
>get approval from a non-write-after-approval maintainer.

You should take that up with the GCC project.

cgf

PATCH for Re: Account on sourceware.org for write access to gcc project

[Gerald Pfeifer]

[ Adding gcc-patches ]

On Fri, 11 Dec 2009, Thierry LAFAGE wrote:
> BTW, in http://gcc.gnu.org/svnwrite.html, I did not see that I needed to 
> get approval from a non-write-after-approval maintainer.

This is a fair point, Thierry, and I now tried to remedy this with the
change below.  If you have a suggestion to make this more clear, I'll
happily consider it, too, of course.

Gerald

Index: svnwrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.18
diff -u -3 -p -r1.18 svnwrite.html
--- svnwrite.html	25 Oct 2008 17:09:38 -0000	1.18
+++ svnwrite.html	21 Dec 2009 08:17:39 -0000
@@ -36,10 +36,10 @@ www documents is still done using <a hre
 
 <p>We provide authenticated access via the SSH protocol.</p> 
 
-<p>If you already have an account on sourceware.org, please send
-email to <code>overseers(at)gcc.gnu.org</code> with a request
-for access to the GCC repository.  Include the name of the person who
-is sponsoring your access and CC: your email to them.
+<p>If you already have an account on sourceware.org, please send email to
+<code>overseers(at)gcc.gnu.org</code> with a request for access to the GCC
+repository.  Include the name of an existing maintainer who is sponsoring
+your access and CC: your sponsor.
 Else use <a
 href="http://sourceware.org/cgi-bin/pdw/ps_form.cgi">this form</a>
 to supply your SSH public key (which you can generate via the

Re: PATCH for Re: Account on sourceware.org for write access to gcc project

[Thierry Lafage]

Your patch's a good idea and to make it even clearer, I would suggest 
that an existing maintainer should be asked for sponsoring even for 
those who don't already have an account on on sourceware.org.

Thierry Lafage.



Gerald Pfeifer a écrit :
> [ Adding gcc-patches ]
>
> On Fri, 11 Dec 2009, Thierry LAFAGE wrote:
>   
>> BTW, in http://gcc.gnu.org/svnwrite.html, I did not see that I needed to 
>> get approval from a non-write-after-approval maintainer.
>>     
>
> This is a fair point, Thierry, and I now tried to remedy this with the
> change below.  If you have a suggestion to make this more clear, I'll
> happily consider it, too, of course.
>
> Gerald
>
> Index: svnwrite.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
> retrieving revision 1.18
> diff -u -3 -p -r1.18 svnwrite.html
> --- svnwrite.html	25 Oct 2008 17:09:38 -0000	1.18
> +++ svnwrite.html	21 Dec 2009 08:17:39 -0000
> @@ -36,10 +36,10 @@ www documents is still done using <a hre
>  
>  <p>We provide authenticated access via the SSH protocol.</p> 
>  
> -<p>If you already have an account on sourceware.org, please send
> -email to <code>overseers(at)gcc.gnu.org</code> with a request
> -for access to the GCC repository.  Include the name of the person who
> -is sponsoring your access and CC: your email to them.
> +<p>If you already have an account on sourceware.org, please send email to
> +<code>overseers(at)gcc.gnu.org</code> with a request for access to the GCC
> +repository.  Include the name of an existing maintainer who is sponsoring
> +your access and CC: your sponsor.
>  Else use <a
>  href="http://sourceware.org/cgi-bin/pdw/ps_form.cgi">this form</a>
>  to supply your SSH public key (which you can generate via the
>   

Re: PATCH for Re: Account on sourceware.org for write access to gcc project

[Christopher Faylor]

On Mon, Dec 21, 2009 at 10:40:05AM +0100, Thierry Lafage wrote:
>Your patch's a good idea and to make it even clearer, I would suggest 
>that an existing maintainer should be asked for sponsoring even for 
>those who don't already have an account on on sourceware.org.

If this really is an issue then I think you need to make it very clear what
you mean by "maintainer".

cgf