Re: INFRA-6774

2013-11-20 Thread Daniel Shahaf
Joseph Schaefer wrote on Tue, Nov 19, 2013 at 23:18:11 -0500:
 
 On Nov 19, 2013, at 10:50 PM, Joseph Schaefer joe_schae...@yahoo.com wrote:
 
  
  On Nov 19, 2013, at 10:40 PM, Jordan Zimmerman randg...@apache.org wrote:
  
  Can someone please explain to me what I need to do to have 
  curator.incubator.apache.org redirect to curator.apache.org?
  
  You need to create an .htaccess file at the top-level of your tree with the 
  following contents
  
  RewriteCond %{HTTP_HOST} curator.incubator.apache.org
  RewriteRule (.*)  https://curator.apache.org/
 
 Sorry, that last part needs an $1 tacked onto the end: 
 https://curator.apache.org/$1

No htaccess is needed, it happens automagically once the TLP dist area
is created.  See vhosts/zzzothers.conf on eos.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-20 Thread Joseph Schaefer
Oh snap Daniel nice job with that.  I didn’t
even notice that stanza in the config file
before!

On Nov 20, 2013, at 6:30 AM, Daniel Shahaf d...@daniel.shahaf.name wrote:

 Joseph Schaefer wrote on Tue, Nov 19, 2013 at 23:18:11 -0500:
 
 On Nov 19, 2013, at 10:50 PM, Joseph Schaefer joe_schae...@yahoo.com wrote:
 
 
 On Nov 19, 2013, at 10:40 PM, Jordan Zimmerman randg...@apache.org wrote:
 
 Can someone please explain to me what I need to do to have 
 curator.incubator.apache.org redirect to curator.apache.org?
 
 You need to create an .htaccess file at the top-level of your tree with the 
 following contents
 
 RewriteCond %{HTTP_HOST} curator.incubator.apache.org
 RewriteRule (.*)  https://curator.apache.org/
 
 Sorry, that last part needs an $1 tacked onto the end: 
 https://curator.apache.org/$1
 
 No htaccess is needed, it happens automagically once the TLP dist area
 is created.  See vhosts/zzzothers.conf on eos.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread Jake Farrell
Please follow the incubation graduation guide
http://incubator.apache.org/guides/graduation.html see the
Transferring resources
#3.2 user Websites

Websites

   1. Transfer the podling website
  1. Load the website into its new home. See infra
noteshttp://www.apache.org/dev/#web
  .
  2. Update the incubator/site-publish/.htaccess entry to redirect
  traffic from the old URLs to the new. (svn location is at
  http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess
  )
  3. Delete the podling website from /www/
  incubator.apache.org/content/${podling-name} on people.apache.org if
  possible. It won't be possible to remove the ${podling-name} directory
  (because incubator uses svnpubsub). If the podling also used svnpubsub it
  won't be possible to delete the files either. File a JIRA ticket under
  INFRA and ask for the remains to be removed.
  4. Post an announcement to user and development lists
  5. When using Maven: update pom.xml for the location of the website,
  as well as the place where the site plugin will deploy the web site (when
  applicable).



-Jake



On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.orgwrote:

 Can someone please explain to me what I need to do to have
 curator.incubator.apache.org redirect to curator.apache.org?



Re: INFRA-6774

2013-11-19 Thread Jordan Zimmerman
When I tried to commit the change, I get:

svn: E175013: Commit failed (details follow):
svn: E175013: Access to '/repos/asf/!svn/me' forbidden


On Nov 19, 2013, at 7:49 PM, Jake Farrell jfarr...@apache.org wrote:

 Please follow the incubation graduation guide 
 http://incubator.apache.org/guides/graduation.html see the Transferring 
 resources #3.2 user Websites
 
 Websites
 Transfer the podling website
 Load the website into its new home. See infra notes.
 Update the incubator/site-publish/.htaccess entry to redirect traffic from 
 the old URLs to the new. (svn location is 
 athttp://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess)
 Delete the podling website from 
 /www/incubator.apache.org/content/${podling-name} on people.apache.org if 
 possible. It won't be possible to remove the ${podling-name} directory 
 (because incubator uses svnpubsub). If the podling also used svnpubsub it 
 won't be possible to delete the files either. File a JIRA ticket under INFRA 
 and ask for the remains to be removed.
 Post an announcement to user and development lists
 When using Maven: update pom.xml for the location of the website, as well as 
 the place where the site plugin will deploy the web site (when applicable).
 
 
 -Jake
 
 
 
 On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.org 
 wrote:
 Can someone please explain to me what I need to do to have 
 curator.incubator.apache.org redirect to curator.apache.org?
 



Re: INFRA-6774

2013-11-19 Thread Joseph Schaefer

On Nov 19, 2013, at 10:40 PM, Jordan Zimmerman randg...@apache.org wrote:

 Can someone please explain to me what I need to do to have 
 curator.incubator.apache.org redirect to curator.apache.org?

You need to create an .htaccess file at the top-level of your tree with the 
following contents

RewriteCond %{HTTP_HOST} curator.incubator.apache.org
RewriteRule (.*)  https://curator.apache.org/

HTH. Please if you get this working well go back and document it for others to 
use.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread Joseph Schaefer

On Nov 19, 2013, at 10:50 PM, Joseph Schaefer joe_schae...@yahoo.com wrote:

 
 On Nov 19, 2013, at 10:40 PM, Jordan Zimmerman randg...@apache.org wrote:
 
 Can someone please explain to me what I need to do to have 
 curator.incubator.apache.org redirect to curator.apache.org?
 
 You need to create an .htaccess file at the top-level of your tree with the 
 following contents
 
 RewriteCond %{HTTP_HOST} curator.incubator.apache.org
 RewriteRule (.*)  https://curator.apache.org/

Sorry, that last part needs an $1 tacked onto the end: 
https://curator.apache.org/$1

 
 HTH. Please if you get this working well go back and document it for others 
 to use.
 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread David Crossley
Jordan Zimmerman wrote:
 Can someone please explain to me what I need to do to have
 curator.incubator.apache.org redirect to curator.apache.org?

You asked this a few hours ago on infrastructure@ and were given
complete and additional answers by various separate people.
Now you have more people at infra involved in the same stuff.
And now expaned to include all of Incubator.
What is up?.

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread David Crossley
David Crossley wrote:
 Jordan Zimmerman wrote:

  Can someone please explain to me what I need to do to have
  curator.incubator.apache.org redirect to curator.apache.org?
 
 You asked this a few hours ago on infrastructure@ and were given
 complete and additional answers by various separate people.
 Now you have more people at infra involved in the same stuff.
 And now expaned to include all of Incubator.
 What is up?.

Ah, i was answering from the infrastructure@ list. Now i see
additional information about svn access in the Incubator thread.
However, your question above seemed to be a repeat.

-David

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread Joseph Schaefer
No there’s a difference.  Before he was asking what
infra was going to do to magically make this happen.
That request was denied.


Now we have a better question: what can he do himself
to make this happen?  Here there are some answers to
questions that should be addressed in the incubator docs
but aren’t, because this particular website graduation is
OUTSIDE of the typical incubator.apache.org/foo sub site.

Technically this is a non-event by design from infra’s
standpoint because once DNS is enabled we have done all
we need to do to start serving up the new traffic, other
than capture any site source relocations in our svnpubsub
config file.  All a project like curator needs to do now
is add an appropriate .htaccess file to the top-level of
their site with the two RewriteCond / RewriteRule directives
to move traffic away from their incubator subdomain and to
their top-level domain.


On Nov 20, 2013, at 12:18 AM, David Crossley cross...@apache.org wrote:

 David Crossley wrote:
 Jordan Zimmerman wrote:
 
 Can someone please explain to me what I need to do to have
 curator.incubator.apache.org redirect to curator.apache.org?
 
 You asked this a few hours ago on infrastructure@ and were given
 complete and additional answers by various separate people.
 Now you have more people at infra involved in the same stuff.
 And now expaned to include all of Incubator.
 What is up?.
 
 Ah, i was answering from the infrastructure@ list. Now i see
 additional information about svn access in the Incubator thread.
 However, your question above seemed to be a repeat.
 
 -David
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread David Crossley
Jordan Zimmerman wrote:
 When I tried to commit the change, I get:
 
 svn: E175013: Commit failed (details follow):
 svn: E175013: Access to '/repos/asf/!svn/me' forbidden

Are you able to commit to other stuff?
e.g. your podling status page
or to podlings.xml file.
You would have had that access while you were in
the Incubator and should still have it AFAIK.

How are you doing this process?
e.g. via the CMS
or via svn checkout on your workstation
or ...

-David

 On Nov 19, 2013, at 7:49 PM, Jake Farrell jfarr...@apache.org wrote:
 
  Please follow the incubation graduation guide 
  http://incubator.apache.org/guides/graduation.html see the Transferring 
  resources #3.2 user Websites
  
  Websites
  Transfer the podling website
  Load the website into its new home. See infra notes.
  Update the incubator/site-publish/.htaccess entry to redirect traffic from 
  the old URLs to the new. (svn location is 
  athttp://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess)
  Delete the podling website from 
  /www/incubator.apache.org/content/${podling-name} on people.apache.org if 
  possible. It won't be possible to remove the ${podling-name} directory 
  (because incubator uses svnpubsub). If the podling also used svnpubsub it 
  won't be possible to delete the files either. File a JIRA ticket under 
  INFRA and ask for the remains to be removed.
  Post an announcement to user and development lists
  When using Maven: update pom.xml for the location of the website, as well 
  as the place where the site plugin will deploy the web site (when 
  applicable).
  
  
  -Jake
  
  
  
  On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.org 
  wrote:
  Can someone please explain to me what I need to do to have 
  curator.incubator.apache.org redirect to curator.apache.org?
  
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread Joseph Schaefer
Already resolved.  A Forbidden response instead
of a failed auth request almost always implies
committing using http.

On Nov 20, 2013, at 12:28 AM, David Crossley cross...@apache.org wrote:

 Jordan Zimmerman wrote:
 When I tried to commit the change, I get:
 
 svn: E175013: Commit failed (details follow):
 svn: E175013: Access to '/repos/asf/!svn/me' forbidden
 
 Are you able to commit to other stuff?
 e.g. your podling status page
 or to podlings.xml file.
 You would have had that access while you were in
 the Incubator and should still have it AFAIK.
 
 How are you doing this process?
 e.g. via the CMS
 or via svn checkout on your workstation
 or ...
 
 -David
 
 On Nov 19, 2013, at 7:49 PM, Jake Farrell jfarr...@apache.org wrote:
 
 Please follow the incubation graduation guide 
 http://incubator.apache.org/guides/graduation.html see the Transferring 
 resources #3.2 user Websites
 
 Websites
 Transfer the podling website
 Load the website into its new home. See infra notes.
 Update the incubator/site-publish/.htaccess entry to redirect traffic from 
 the old URLs to the new. (svn location is 
 athttp://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess)
 Delete the podling website from 
 /www/incubator.apache.org/content/${podling-name} on people.apache.org if 
 possible. It won't be possible to remove the ${podling-name} directory 
 (because incubator uses svnpubsub). If the podling also used svnpubsub it 
 won't be possible to delete the files either. File a JIRA ticket under 
 INFRA and ask for the remains to be removed.
 Post an announcement to user and development lists
 When using Maven: update pom.xml for the location of the website, as well 
 as the place where the site plugin will deploy the web site (when 
 applicable).
 
 
 -Jake
 
 
 
 On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.org 
 wrote:
 Can someone please explain to me what I need to do to have 
 curator.incubator.apache.org redirect to curator.apache.org?
 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread David Crossley
Joseph Schaefer wrote:
 No there’s a difference.  Before he was asking what
 infra was going to do to magically make this happen.
 That request was denied.
 
 
 Now we have a better question: what can he do himself
 to make this happen?  Here there are some answers to
 questions that should be addressed in the incubator docs
 but aren’t, because this particular website graduation is
 OUTSIDE of the typical incubator.apache.org/foo sub site.
 
 Technically this is a non-event by design from infra’s
 standpoint because once DNS is enabled we have done all
 we need to do to start serving up the new traffic, other
 than capture any site source relocations in our svnpubsub
 config file.  All a project like curator needs to do now
 is add an appropriate .htaccess file to the top-level of
 their site with the two RewriteCond / RewriteRule directives
 to move traffic away from their incubator subdomain and to
 their top-level domain.

Would someone please merge Joe and the following docs
so we can get out of these loops.

Jake Farrell wrote:

 Please follow the incubation graduation guide
 http://incubator.apache.org/guides/graduation.html see the Transferring
 resources #3.2 user Website

Thank you!

One wonders why projects are not following these guides.

There is also clear direction here:
http://www.apache.org/dev/infra-contact#requesting-graduation

-David

 David Crossley wrote:
  David Crossley wrote:
  Jordan Zimmerman wrote:
  
  Can someone please explain to me what I need to do to have
  curator.incubator.apache.org redirect to curator.apache.org?
  
  You asked this a few hours ago on infrastructure@ and were given
  complete and additional answers by various separate people.
  Now you have more people at infra involved in the same stuff.
  And now expaned to include all of Incubator.
  What is up?.
  
  Ah, i was answering from the infrastructure@ list. Now i see
  additional information about svn access in the Incubator thread.
  However, your question above seemed to be a repeat.
  
  -David
  
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
  
 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread David Crossley
Joseph Schaefer wrote:

 Already resolved.  A Forbidden response instead
 of a failed auth request almost always implies
 committing using http.

Great, thanks for following up.

What a committer trap that one is.

A while ago we added that to the FAQ:
Google: site:apache.org/dev committer https
http://www.apache.org/dev/committers.html#commit-403
(although that seems to use old terminology).

http://www.apache.org/dev/version-control.html#https-svn

Would someone please clarify the docs.

-David

 David Crossley wrote:
  Jordan Zimmerman wrote:
  When I tried to commit the change, I get:
  
  svn: E175013: Commit failed (details follow):
  svn: E175013: Access to '/repos/asf/!svn/me' forbidden
  
  Are you able to commit to other stuff?
  e.g. your podling status page
  or to podlings.xml file.
  You would have had that access while you were in
  the Incubator and should still have it AFAIK.
  
  How are you doing this process?
  e.g. via the CMS
  or via svn checkout on your workstation
  or ...
  
  -David
  
  On Nov 19, 2013, at 7:49 PM, Jake Farrell jfarr...@apache.org wrote:
  
  Please follow the incubation graduation guide 
  http://incubator.apache.org/guides/graduation.html see the Transferring 
  resources #3.2 user Websites
  
  Websites
  Transfer the podling website
  Load the website into its new home. See infra notes.
  Update the incubator/site-publish/.htaccess entry to redirect traffic 
  from the old URLs to the new. (svn location is 
  athttp://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess)
  Delete the podling website from 
  /www/incubator.apache.org/content/${podling-name} on people.apache.org if 
  possible. It won't be possible to remove the ${podling-name} directory 
  (because incubator uses svnpubsub). If the podling also used svnpubsub it 
  won't be possible to delete the files either. File a JIRA ticket under 
  INFRA and ask for the remains to be removed.
  Post an announcement to user and development lists
  When using Maven: update pom.xml for the location of the website, as well 
  as the place where the site plugin will deploy the web site (when 
  applicable).
  
  
  -Jake
  
  
  
  On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.org 
  wrote:
  Can someone please explain to me what I need to do to have 
  curator.incubator.apache.org redirect to curator.apache.org?

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: INFRA-6774

2013-11-19 Thread Bertrand Delacretaz
On Wed, Nov 20, 2013 at 7:05 AM, David Crossley cross...@apache.org wrote:
 ...A while ago we added that to the FAQ:
 http://www.apache.org/dev/committers.html#commit-403
 (although that seems to use old terminology).

 http://www.apache.org/dev/version-control.html

I have moved (and linked) the 403 - cannot commit FAQ from
dev/committers.html to /dev/version-control.html#commit-403 to make
sure the svn FAQ is in one place.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org