Comments on: Buildr goes Apache, and see you next week at ApacheCon http://labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/ Tue, 15 May 2012 02:41:51 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Assaf http://labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/comment-page-1/#comment-138942 Assaf Sat, 01 Dec 2007 02:54:16 +0000 http://blog.labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/#comment-138942 Martijn, wish I saw your comment before. We're keeping the RubyForge project alive and we'll keep using it to distribute Gems, but we redirect from there to Apache instead of the other way around. Apparently, there's no official Apache policy on moving Web sites or even mailing lists, but no one at ApacheCon could tell me what works within their guidelines. Martijn, wish I saw your comment before. We’re keeping the RubyForge project alive and we’ll keep using it to distribute Gems, but we redirect from there to Apache instead of the other way around.

Apparently, there’s no official Apache policy on moving Web sites or even mailing lists, but no one at ApacheCon could tell me what works within their guidelines.

]]> By: Sterling Camden http://labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/comment-page-1/#comment-138832 Sterling Camden Mon, 12 Nov 2007 18:20:16 +0000 http://blog.labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/#comment-138832 Congrats, Assaf! Congrats, Assaf!

]]> By: Martijn Dashorst http://labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/comment-page-1/#comment-138819 Martijn Dashorst Fri, 09 Nov 2007 09:37:03 +0000 http://blog.labnotes.org/2007/11/08/buildr-goes-apache-and-see-you-next-week-at-apachecon/#comment-138819 As for the website, keep the old one alive. You may need to use it to publish (stable) releases there for your community. The incubator site is a good place to develop your new, ASF approved site, but you should only attract big numbers of users and links to it when you graduate and moved it to the final destination (buildr.apache.org?). This way you can keep your rank using a perm redirect from your old site to the new site. This worked great for Wicket. As for the website, keep the old one alive. You may need to use it to publish (stable) releases there for your community.

The incubator site is a good place to develop your new, ASF approved site, but you should only attract big numbers of users and links to it when you graduate and moved it to the final destination (buildr.apache.org?). This way you can keep your rank using a perm redirect from your old site to the new site.

This worked great for Wicket.

]]>