You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Karl Fogel (JIRA)" <ji...@apache.org> on 2010/11/02 03:25:23 UTC

[jira] Created: (INFRA-3134) Simple factual bug on dev/cms.html page.

Simple factual bug on dev/cms.html page.
----------------------------------------

                 Key: INFRA-3134
                 URL: https://issues.apache.org/jira/browse/INFRA-3134
             Project: Infrastructure
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Website
            Reporter: Karl Fogel
            Priority: Trivial


http://www.apache.org/dev/cms.html currently states that the new Apache CMS is "serving non-production copies of the main www.apache.org site and the Incubator site".  However, in a members@ post today, Joe Schaeffer states:

  > From: Joe Schaefer <joe_schaefer {_AT_} yahoo.com>
  > Subject: new www site is live
  > To: site-dev {_AT_} apache.org
  > Cc: members {_AT_} apache.org
  > Message-Id: <79...@web54409.mail.re2.yahoo.com>
  > Date: Mon, 1 Nov 2010 13:42:23 -0700 (PDT)
  > Reply-To: members {_AT_} apache.org
  > 
  > http://www.apache.org/ is now based
  > on the new cms:
  > 
  > http://www.apache.org/dev/cms.html
  > 
  > Enjoy.

The patch below updates the dev/cms.html page accordingly.  I'm not sure what the right route is
to get a change into a main apache.org web page -- does one commit it to staging?  Feel free to teach me how to fish.  In the meantime:

$ pwd
/home/kfogel/src/apache/staging-content/dev

$ svn info | grep "^URL: " | cut -b 6-
https://svn.apache.org/repos/infra/websites/staging/www/trunk/content/dev

$ svn diff
Index: cms.html
===================================================================
--- cms.html	(revision 778459)
+++ cms.html	(working copy)
@@ -356,9 +356,7 @@
 mandate the adoption of at least svnpubsub for all projects by the end of
 2012.</p>
 <h2 id="cmsinsvn">View the ASF CMS code</h2>
-<p>The code behind this ASF CMS system is now running on a testbed here at the 
-ASF, serving non-production copies of the main www.apache.org site and the
-Incubator site.<br />
+<p>As of 1 Nov 2010, this ASF CMS system is now running the main www.apache.org site.<br />
 </p>
 <p>The code for the CMS itself is being developed by the Infrastructure Team,
 and you can follow its <a href="https://svn.apache.org/repos/infra/websites/cms">Subversion repository</a>.</p></div></div>
$ 

(If 'staging' isn't the right place, then the corresponding production repository area is https://svn.apache.org/repos/infra/websites/production/www/content.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (INFRA-3134) Simple factual bug on dev/cms.html page.

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927342#action_12927342 ] 

#asfinfra IRC Bot commented on INFRA-3134:
------------------------------------------

<joes4> I've made the requisite changes.  You can do this yourself next time by 1) installing the requisite bookmarklet, 2) visiting http://www.apache.org/dev/cms.html, 3) clicking on bookmarklet, 4) clicking on edit, 5) editing content, 6) committing your edit, 7) examining the staging build of your commit, and finally 8) publishing your change to the site.  There are links in the cms to walk you through this process.


> Simple factual bug on dev/cms.html page.
> ----------------------------------------
>
>                 Key: INFRA-3134
>                 URL: https://issues.apache.org/jira/browse/INFRA-3134
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Website
>            Reporter: Karl Fogel
>            Priority: Trivial
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> http://www.apache.org/dev/cms.html currently states that the new Apache CMS is "serving non-production copies of the main www.apache.org site and the Incubator site".  However, in a members@ post today, Joe Schaeffer states:
>   > From: Joe Schaefer <joe_schaefer {_AT_} yahoo.com>
>   > Subject: new www site is live
>   > To: site-dev {_AT_} apache.org
>   > Cc: members {_AT_} apache.org
>   > Message-Id: <79...@web54409.mail.re2.yahoo.com>
>   > Date: Mon, 1 Nov 2010 13:42:23 -0700 (PDT)
>   > Reply-To: members {_AT_} apache.org
>   > 
>   > http://www.apache.org/ is now based
>   > on the new cms:
>   > 
>   > http://www.apache.org/dev/cms.html
>   > 
>   > Enjoy.
> The patch below updates the dev/cms.html page accordingly.  I'm not sure what the right route is
> to get a change into a main apache.org web page -- does one commit it to staging?  Feel free to teach me how to fish.  In the meantime:
> $ pwd
> /home/kfogel/src/apache/staging-content/dev
> $ svn info | grep "^URL: " | cut -b 6-
> https://svn.apache.org/repos/infra/websites/staging/www/trunk/content/dev
> $ svn diff
> Index: cms.html
> ===================================================================
> --- cms.html	(revision 778459)
> +++ cms.html	(working copy)
> @@ -356,9 +356,7 @@
>  mandate the adoption of at least svnpubsub for all projects by the end of
>  2012.</p>
>  <h2 id="cmsinsvn">View the ASF CMS code</h2>
> -<p>The code behind this ASF CMS system is now running on a testbed here at the 
> -ASF, serving non-production copies of the main www.apache.org site and the
> -Incubator site.<br />
> +<p>As of 1 Nov 2010, this ASF CMS system is now running the main www.apache.org site.<br />
>  </p>
>  <p>The code for the CMS itself is being developed by the Infrastructure Team,
>  and you can follow its <a href="https://svn.apache.org/repos/infra/websites/cms">Subversion repository</a>.</p></div></div>
> $ 
> (If 'staging' isn't the right place, then the corresponding production repository area is https://svn.apache.org/repos/infra/websites/production/www/content.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (INFRA-3134) Simple factual bug on dev/cms.html page.

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot closed INFRA-3134.
------------------------------------

    Resolution: Fixed

> Simple factual bug on dev/cms.html page.
> ----------------------------------------
>
>                 Key: INFRA-3134
>                 URL: https://issues.apache.org/jira/browse/INFRA-3134
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Website
>            Reporter: Karl Fogel
>            Priority: Trivial
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> http://www.apache.org/dev/cms.html currently states that the new Apache CMS is "serving non-production copies of the main www.apache.org site and the Incubator site".  However, in a members@ post today, Joe Schaeffer states:
>   > From: Joe Schaefer <joe_schaefer {_AT_} yahoo.com>
>   > Subject: new www site is live
>   > To: site-dev {_AT_} apache.org
>   > Cc: members {_AT_} apache.org
>   > Message-Id: <79...@web54409.mail.re2.yahoo.com>
>   > Date: Mon, 1 Nov 2010 13:42:23 -0700 (PDT)
>   > Reply-To: members {_AT_} apache.org
>   > 
>   > http://www.apache.org/ is now based
>   > on the new cms:
>   > 
>   > http://www.apache.org/dev/cms.html
>   > 
>   > Enjoy.
> The patch below updates the dev/cms.html page accordingly.  I'm not sure what the right route is
> to get a change into a main apache.org web page -- does one commit it to staging?  Feel free to teach me how to fish.  In the meantime:
> $ pwd
> /home/kfogel/src/apache/staging-content/dev
> $ svn info | grep "^URL: " | cut -b 6-
> https://svn.apache.org/repos/infra/websites/staging/www/trunk/content/dev
> $ svn diff
> Index: cms.html
> ===================================================================
> --- cms.html	(revision 778459)
> +++ cms.html	(working copy)
> @@ -356,9 +356,7 @@
>  mandate the adoption of at least svnpubsub for all projects by the end of
>  2012.</p>
>  <h2 id="cmsinsvn">View the ASF CMS code</h2>
> -<p>The code behind this ASF CMS system is now running on a testbed here at the 
> -ASF, serving non-production copies of the main www.apache.org site and the
> -Incubator site.<br />
> +<p>As of 1 Nov 2010, this ASF CMS system is now running the main www.apache.org site.<br />
>  </p>
>  <p>The code for the CMS itself is being developed by the Infrastructure Team,
>  and you can follow its <a href="https://svn.apache.org/repos/infra/websites/cms">Subversion repository</a>.</p></div></div>
> $ 
> (If 'staging' isn't the right place, then the corresponding production repository area is https://svn.apache.org/repos/infra/websites/production/www/content.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (INFRA-3134) Simple factual bug on dev/cms.html page.

Posted by "Karl Fogel (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927399#action_12927399 ] 

Karl Fogel commented on INFRA-3134:
-----------------------------------

Thanks, Joe.  Bookmarklet installed now.

> Simple factual bug on dev/cms.html page.
> ----------------------------------------
>
>                 Key: INFRA-3134
>                 URL: https://issues.apache.org/jira/browse/INFRA-3134
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Website
>            Reporter: Karl Fogel
>            Priority: Trivial
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> http://www.apache.org/dev/cms.html currently states that the new Apache CMS is "serving non-production copies of the main www.apache.org site and the Incubator site".  However, in a members@ post today, Joe Schaeffer states:
>   > From: Joe Schaefer <joe_schaefer {_AT_} yahoo.com>
>   > Subject: new www site is live
>   > To: site-dev {_AT_} apache.org
>   > Cc: members {_AT_} apache.org
>   > Message-Id: <79...@web54409.mail.re2.yahoo.com>
>   > Date: Mon, 1 Nov 2010 13:42:23 -0700 (PDT)
>   > Reply-To: members {_AT_} apache.org
>   > 
>   > http://www.apache.org/ is now based
>   > on the new cms:
>   > 
>   > http://www.apache.org/dev/cms.html
>   > 
>   > Enjoy.
> The patch below updates the dev/cms.html page accordingly.  I'm not sure what the right route is
> to get a change into a main apache.org web page -- does one commit it to staging?  Feel free to teach me how to fish.  In the meantime:
> $ pwd
> /home/kfogel/src/apache/staging-content/dev
> $ svn info | grep "^URL: " | cut -b 6-
> https://svn.apache.org/repos/infra/websites/staging/www/trunk/content/dev
> $ svn diff
> Index: cms.html
> ===================================================================
> --- cms.html	(revision 778459)
> +++ cms.html	(working copy)
> @@ -356,9 +356,7 @@
>  mandate the adoption of at least svnpubsub for all projects by the end of
>  2012.</p>
>  <h2 id="cmsinsvn">View the ASF CMS code</h2>
> -<p>The code behind this ASF CMS system is now running on a testbed here at the 
> -ASF, serving non-production copies of the main www.apache.org site and the
> -Incubator site.<br />
> +<p>As of 1 Nov 2010, this ASF CMS system is now running the main www.apache.org site.<br />
>  </p>
>  <p>The code for the CMS itself is being developed by the Infrastructure Team,
>  and you can follow its <a href="https://svn.apache.org/repos/infra/websites/cms">Subversion repository</a>.</p></div></div>
> $ 
> (If 'staging' isn't the right place, then the corresponding production repository area is https://svn.apache.org/repos/infra/websites/production/www/content.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.