Hi,
Thanks Justin!
Kind Regards,
Furkan KAMACI
On Thu, Jul 25, 2019 at 1:36 AM Justin Mclean
wrote:
> Hi,
>
> > Apache DLab community wanted from me to point
> > https://dlab.opensource.epam.com/ as their website at podling page.
>
> It should move to be hosted on ASF infrastructure see [1] (a
Hi,
> Apache DLab community wanted from me to point
> https://dlab.opensource.epam.com/ as their website at podling page.
It should move to be hosted on ASF infrastructure see [1] (a little out of date
and need to be updated but has the main points).
Thanks,
Justin
1. https://incubator.apache.
Hi,
Apache DLab community wanted from me to point
https://dlab.opensource.epam.com/ as their website at podling page. I've
checked all the podling definitions and just a few of them place at a
domain rather than apache. I've mentioned to consider them to move/redirect
their website into http://dla
CloudStack dev@ should be copied in on this thread.
On Wed, Oct 3, 2012 at 7:43 AM, Bertrand Delacretaz
wrote:
> Hi,
>
> On Wed, Oct 3, 2012 at 1:22 AM, Sheng Liang
> wrote:
> ...
> > 1. When shall we redirect cloudstack.org to the Apache project page?
> (e.g., http://incubator.apache.org/projec
Hi,
On Wed, Oct 3, 2012 at 1:22 AM, Sheng Liang wrote:
...
> 1. When shall we redirect cloudstack.org to the Apache project page? (e.g.,
> http://incubator.apache.org/projects/cloudstack.html)
Podlings don't usually use that status page as their homepage, I'd
expect cloudstack.org to redirect t
I have a couple of questions regarding the CloudStack project now under
incubation. Citrix contributed the CloudStack project to ASF in April this
year. Right now Citrix still runs a project website called cloudstack.org.
1. When shall we redirect cloudstack.org to the Apache project page? (e.
B. W. Fitzpatrick wrote:
> Nicola Ken Barozzi <[EMAIL PROTECTED]> writes:
>
> > Since AltRMI and FTPServer are in the "old" URL, what about moving them
> Fine with me, just toss rewrite rules into httpd.conf so folks going to
> the old URLs don't get the dreaded 404.
I was going to setup .htaccess
Nicola Ken Barozzi <[EMAIL PROTECTED]> writes:
>
> Since AltRMI and FTPServer are in the "old" URL, what about moving them
> like this? No need to rush, it can be easily done in the next site update.
>
> http://incubator.apache.org/projects/altrmi
>|
>v
>
Since AltRMI and FTPServer are in the "old" URL, what about moving them
like this? No need to rush, it can be easily done in the next site update.
http://incubator.apache.org/projects/altrmi
|
v
http://incubator.apache.org/altrmi
http://incubator.apache.org/pro
Noel J. Bergman wrote:
Does this resolve the issues?
+1 & well said :-)
OK, then shall we document it and help the projects get setup? Geronimo has
been clamoring to have their site back. We can now tell them that they must
have their published content in CVS, and that they should checkout
/w
Leo,
Leo Simons wrote:
> cd $proj
> maven site
> cd target/docs
> cvs -z3 -d [EMAIL PROTECTED]:/home/cvs \
> import -m 'Maven-generated site' incubator-site/build/site/$proj \
> maven_site Maven_Generated_$proj_Website_$(date +%Y%m%d)
>
> replace '$proj' with the project name, replace $my_id w
> > Does this resolve the issues?
> +1 & well said :-)
OK, then shall we document it and help the projects get setup? Geronimo has
been clamoring to have their site back. We can now tell them that they must
have their published content in CVS, and that they should checkout
/www/incubator.apa
> Continuously moving stuff around (like moving the lenya website now)
> just means lots of work no-one likes to do.
I agree that it is a pain. I think we need to establish a policy, even if
we end up grandfathering some projects.
--- Noel
--
Nicola Ken Barozzi wrote:
Leo Simons wrote:
Nicola Ken Barozzi wrote:
2 - every project has this URL space where to publish the site:
http://incubator.apache.org/projectname
+1 (or under the wings of their TLP if they wish)
Actually this is the point. I tend to think that they should publish
Noel J. Bergman wrote:
Nicola Ken Barozzi wrote:
Leo Simons wrote:
Nicola Ken Barozzi wrote:
2 - every project has this URL space where to publish the site:
http://incubator.apache.org/projectname
+1 (or under the wings of their TLP if they wish)
Actually this is the point. I tend to think tha
Nicola Ken Barozzi wrote:
> Leo Simons wrote:
> > Nicola Ken Barozzi wrote:
> > > 2 - every project has this URL space where to publish the site:
> > > http://incubator.apache.org/projectname
> > +1 (or under the wings of their TLP if they wish)
> Actually this is the point. I tend to think that
Leo Simons wrote:
Nicola Ken Barozzi wrote:
...
2 - every project has this URL space where to publish the site:
http://incubator.apache.org/projectname
+1 (or under the wings of their TLP if they wish)
Actually this is the point. I tend to think that they should publish the
site here always.
Nicola Ken Barozzi wrote:
Proposal:
1 - every project site sources stay in the project CVS
sure.
2 - every project has this URL space where to publish the site:
http://incubator.apache.org/projectname
+1 (or under the wings of their TLP if they wish)
3 - every project has an incubation sta
Guys, I really wanna try and nail this down this time.
To minimize infrastructure work, we had decided on a policy that the
projects get resources done in their final pmc destination, if it's defined.
So if project X goes to the Y PMC, we would have:
[EMAIL PROTECTED]
y-x CVS module
etc..
19 matches
Mail list logo
