Re: [Website] Project homepage
I have stopped reading the Apache Incubator mailing list some time ago due to such debates. If you think that it is important to create new senseless rules for new projects - do so. But please do not create new useless work for those projects which already exist in the Incubator. Thanks, Andreas - Original Message - From: Noel J. Bergman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 7:15 PM Subject: RE: [Website] Project homepage Dion Gillard wrote: James Strachan wrote: Lenya, which has a URI, http://cocoon.apache.org/lenya/, outside of the incubator domain. Hmmm, how come Lenya got a URI? Can we have one too? I guess so if Lenya already has? As an outsider, this is very confusing. Lenya 'is not an ASF project', as it's being incubated, but the URL sure makes it seem like it is a sub project of cocoon. In total fairness to Lenya, the first paragraph of their home page talks about incubation. However, I agree as a policy matter that the site should be moved, with a redirect put in place, as described below. After a project leaves the incubator, a redirect can be put in the incubator's .htaccess to reference its new location. To demonstrate the technique, and further illustrating why web-sites should be maintained in CVS (as Lenya's is :-)), I just issued the following command: cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic \ checkout -d lenya cocoon-site/site/lenya from /www/incubator.apache.org. You will notice that a copy of the lenya site is now at http://incubator.apache.org/lenya. All that is left for the Cocoon project to do now is to place: Redirect Permanent /lenya http://incubator.apache.org/lenya in .htaccess in their site root, and the location change should be transparent to all. I won't do that, though. That is a change for them to make. When the lenya site is updated, someone just needs to do: cd /www/incubator.apache.org/lenya cvs update -Pd rather than doing the exact same thing in /www/cocoon.apache.org/lenya. The process is simple, and should not be disruptive to their progress at all. It is actually rather cool that things can be this simple. --- Noel cc: lenya-dev@ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Website] Project homepage
Stefano Mazzocchi wrote: ... The process is simple, yes, but it would break all the links to Lenya. When we started lenya, the rules of the incubator were not there yet, so we took lenya closer to the community that it depends on. Before breaking all the links, I would like to know if the above is just a suggestion or a rule that incubated projects have to follow. We have decided that this is the policy that has to be used for all projects that still have to setup a website. We have not decided what to do with current projects, although we would certainly appreciate if something like this can be done. As for the implementation of it for projects that already have a site, Noel's was just an example of what can be done, not of what has to be done. More sophisticated things can be done with mod_rewrite: http://httpd.apache.org/docs-2.0/misc/rewriteguide.html Practically publishing under the incubator rather than under Cocoon is really trivial, it just needs to do the CVS update from the incubator dir on the web server, but the problem is with legacy links, and AFAIK it can be solved. What do others think? I'm personally fine with either solution for projects in the same situation as Lenya (ie publishing under incubator or current place and redirecting from the other site), as long as the logo is changed to be the one of the Incubator Project and not that of the final proposed destination. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Website] Project homepage
On 18 Nov 2003, at 10:15, Noel J. Bergman wrote: Dion Gillard wrote: James Strachan wrote: Lenya, which has a URI, http://cocoon.apache.org/lenya/, outside of the incubator domain. Hmmm, how come Lenya got a URI? Can we have one too? I guess so if Lenya already has? As an outsider, this is very confusing. Lenya 'is not an ASF project', as it's being incubated, but the URL sure makes it seem like it is a sub project of cocoon. In total fairness to Lenya, the first paragraph of their home page talks about incubation. However, I agree as a policy matter that the site should be moved, with a redirect put in place, as described below. After a project leaves the incubator, a redirect can be put in the incubator's .htaccess to reference its new location. To demonstrate the technique, and further illustrating why web-sites should be maintained in CVS (as Lenya's is :-)), I just issued the following command: cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic \ checkout -d lenya cocoon-site/site/lenya from /www/incubator.apache.org. You will notice that a copy of the lenya site is now at http://incubator.apache.org/lenya. All that is left for the Cocoon project to do now is to place: Redirect Permanent /lenya http://incubator.apache.org/lenya in .htaccess in their site root, and the location change should be transparent to all. I won't do that, though. That is a change for them to make. When the lenya site is updated, someone just needs to do: cd /www/incubator.apache.org/lenya cvs update -Pd rather than doing the exact same thing in /www/cocoon.apache.org/lenya. The process is simple, and should not be disruptive to their progress at all. It is actually rather cool that things can be this simple. --- Noel cc: lenya-dev@ The process is simple, yes, but it would break all the links to Lenya. When we started lenya, the rules of the incubator were not there yet, so we took lenya closer to the community that it depends on. Before breaking all the links, I would like to know if the above is just a suggestion or a rule that incubated projects have to follow. NOTE: I'm just wondering. I'm not criticizing or anything, just curious. -- Stefano. smime.p7s Description: S/MIME cryptographic signature
