You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by Rahul <rs...@xebia.com> on 2012/07/12 09:45:06 UTC
Mahout wiki migration
I have migrated Mahout confluence wiki to CMS Markdown format, see :
http://rahul-summit.rhcloud.com/content/mahout-wiki.html.
All of the pages have been moved but they are missing the comments
section, as the same could not be retrieved from confluence.
The tar file for the migrated content can be found
athttps://docs.google.com/open?id=0B9t-MulUcHvyQWxJSF9YOUFBZEk
<https://docs.google.com/open?id=0B9t-MulUcHvyQWxJSF9YOUFBZEk>
In order to comple the migration, the migrated content needs to be
committed in Mahout svn in the following structure :
$REPO/trunk/
content/
lib/
cgi-bin/
templates/
After that a ticket needs to be raised in
https://whimsy.apache.org/officers/cmsreq by a mentor.
regards,
Rahul
Re: Mahout wiki migration
Posted by Rahul <rs...@xebia.com>.
After looking at a few migrated projects what I made out is this :
The links will point to all static content residing at the same location
as the landing page of Mahout. Unlike Confluence, there will be no
separate domain/sub-domain for documentation.
The CMS content will be in repository at :
http://svn.apache.org/viewvc/mahout/site/trunk/content/ and will be
compiled and copied to the http://mahout.apache.org.
eg. In Lucene the documentation has links like like
/http://lucene.apache.org/whoweare.html/,
which are exported from content at
/http://svn.apache.org/repos/asf/lucene/cms/trunk/content/whoweare.mdtext
/People can directly change the content in the repository/or /you can
have a plugin(ref cms page)//that can assist the same.
As per docs, when you click edit page in the plugin it will change the
svn version of the same.
On 12-07-2012 21:50, Ted Dunning wrote:
> Yes. Confluence will go away and we will link to CMS eventually.
>
> But where will the link piont to? Where will the CMS content be?
>
> On Thu, Jul 12, 2012 at 3:43 AM, Rahul <rs...@xebia.com> wrote:
>
>> Then new wiki when exported by CMS is all static html content. The pages
>> will have a link from Mahout site. So I feel like the pages get copied at
>> the same location as the index page of http://mahout.apache.org.
>>
>> As for Confluence wiki, I think it will be wiped out in some time. Some of
>> the projects that have adopted this either do not exist on Confluence or
>> have a clean wiki.
>>
>>
>> On 12-07-2012 15:37, Sean Owen wrote:
>>
>>> Dumb question but do you know under what URL of the new wiki appears?
>>> I assume Confluence doesn't disappear... there's another bit of work
>>> later in posting redirects from existing pages to the new ones.
>>>
>>> On Thu, Jul 12, 2012 at 11:04 AM, Rahul <rs...@xebia.com> wrote:
>>>
>>>> For usage the CMS docs (http://www.staging.apache.**org/dev/cms.html<http://www.staging.apache.org/dev/cms.html>)
>>>> states
>>>> the following :
>>>>
>>>> //
>>>>
>>>> * /Install the bookmarklet from the cms
>>>> <https://cms.apache.org/#**bookmark<https://cms.apache.org/#bookmark>>
>>>> page.You only have to do this once./
>>>> * /Navigate to the page you wish to edit (on the live site, not in the
>>>> cms)./
>>>> * /Click the bookmarklet.There will be a short pause while the CMS
>>>> system is initialised for you./
>>>> * /Click on |Edit| (to skip this step hack the bookmarklet to add an
>>>> 'action=edit'param to the bookmarklet's query string)/
>>>> * /The page editor should then be displayed./
>>>> * /Click |Submit| to save your edit to the workarea/
>>>> * /Click |Commit| to save the updated file to SVN and trigger a staged
>>>> build. (to skip this step click on the "Quick Commit" checkbox in
>>>> the |Edit| form)./
>>>> * /The results should appear shortly on the staging
>>>> <http://www.staging.apache.**org/dev/cms.html<http://www.staging.apache.org/dev/cms.html>>
>>>> site. (You may have to
>>>> force the page to refresh in order to see the updated content)/
>>>> * /Once you are happy with the updated page, click on |Publish Site|
>>>> to deploy./
>>>>
>>>> The plugins mentioned here are only accessible to committers.
>>>>
>>>> Alternatively I think we can directly update the mdtext files and that
>>>> should put things on the staging site in sometime. Then it can be
>>>> published
>>>> from there.
>>>>
>>>> regards,
>>>> Rahul
>>>>
>>
Re: Mahout wiki migration
Posted by Ted Dunning <te...@gmail.com>.
Yes. Confluence will go away and we will link to CMS eventually.
But where will the link piont to? Where will the CMS content be?
On Thu, Jul 12, 2012 at 3:43 AM, Rahul <rs...@xebia.com> wrote:
> Then new wiki when exported by CMS is all static html content. The pages
> will have a link from Mahout site. So I feel like the pages get copied at
> the same location as the index page of http://mahout.apache.org.
>
> As for Confluence wiki, I think it will be wiped out in some time. Some of
> the projects that have adopted this either do not exist on Confluence or
> have a clean wiki.
>
>
> On 12-07-2012 15:37, Sean Owen wrote:
>
>> Dumb question but do you know under what URL of the new wiki appears?
>> I assume Confluence doesn't disappear... there's another bit of work
>> later in posting redirects from existing pages to the new ones.
>>
>> On Thu, Jul 12, 2012 at 11:04 AM, Rahul <rs...@xebia.com> wrote:
>>
>>> For usage the CMS docs (http://www.staging.apache.**org/dev/cms.html<http://www.staging.apache.org/dev/cms.html>)
>>> states
>>> the following :
>>>
>>> //
>>>
>>> * /Install the bookmarklet from the cms
>>> <https://cms.apache.org/#**bookmark<https://cms.apache.org/#bookmark>>
>>> page.You only have to do this once./
>>> * /Navigate to the page you wish to edit (on the live site, not in the
>>> cms)./
>>> * /Click the bookmarklet.There will be a short pause while the CMS
>>> system is initialised for you./
>>> * /Click on |Edit| (to skip this step hack the bookmarklet to add an
>>> 'action=edit'param to the bookmarklet's query string)/
>>> * /The page editor should then be displayed./
>>> * /Click |Submit| to save your edit to the workarea/
>>> * /Click |Commit| to save the updated file to SVN and trigger a staged
>>> build. (to skip this step click on the "Quick Commit" checkbox in
>>> the |Edit| form)./
>>> * /The results should appear shortly on the staging
>>> <http://www.staging.apache.**org/dev/cms.html<http://www.staging.apache.org/dev/cms.html>>
>>> site. (You may have to
>>> force the page to refresh in order to see the updated content)/
>>> * /Once you are happy with the updated page, click on |Publish Site|
>>> to deploy./
>>>
>>> The plugins mentioned here are only accessible to committers.
>>>
>>> Alternatively I think we can directly update the mdtext files and that
>>> should put things on the staging site in sometime. Then it can be
>>> published
>>> from there.
>>>
>>> regards,
>>> Rahul
>>>
>>
>
>
Re: Mahout wiki migration
Posted by Rahul <rs...@xebia.com>.
Then new wiki when exported by CMS is all static html content. The pages
will have a link from Mahout site. So I feel like the pages get copied
at the same location as the index page of http://mahout.apache.org.
As for Confluence wiki, I think it will be wiped out in some time. Some
of the projects that have adopted this either do not exist on Confluence
or have a clean wiki.
On 12-07-2012 15:37, Sean Owen wrote:
> Dumb question but do you know under what URL of the new wiki appears?
> I assume Confluence doesn't disappear... there's another bit of work
> later in posting redirects from existing pages to the new ones.
>
> On Thu, Jul 12, 2012 at 11:04 AM, Rahul <rs...@xebia.com> wrote:
>> For usage the CMS docs (http://www.staging.apache.org/dev/cms.html) states
>> the following :
>>
>> //
>>
>> * /Install the bookmarklet from the cms
>> <https://cms.apache.org/#bookmark> page.You only have to do this once./
>> * /Navigate to the page you wish to edit (on the live site, not in the
>> cms)./
>> * /Click the bookmarklet.There will be a short pause while the CMS
>> system is initialised for you./
>> * /Click on |Edit| (to skip this step hack the bookmarklet to add an
>> 'action=edit'param to the bookmarklet's query string)/
>> * /The page editor should then be displayed./
>> * /Click |Submit| to save your edit to the workarea/
>> * /Click |Commit| to save the updated file to SVN and trigger a staged
>> build. (to skip this step click on the "Quick Commit" checkbox in
>> the |Edit| form)./
>> * /The results should appear shortly on the staging
>> <http://www.staging.apache.org/dev/cms.html> site. (You may have to
>> force the page to refresh in order to see the updated content)/
>> * /Once you are happy with the updated page, click on |Publish Site|
>> to deploy./
>>
>> The plugins mentioned here are only accessible to committers.
>>
>> Alternatively I think we can directly update the mdtext files and that
>> should put things on the staging site in sometime. Then it can be published
>> from there.
>>
>> regards,
>> Rahul
Re: Mahout wiki migration
Posted by Sean Owen <sr...@gmail.com>.
Dumb question but do you know under what URL of the new wiki appears?
I assume Confluence doesn't disappear... there's another bit of work
later in posting redirects from existing pages to the new ones.
On Thu, Jul 12, 2012 at 11:04 AM, Rahul <rs...@xebia.com> wrote:
> For usage the CMS docs (http://www.staging.apache.org/dev/cms.html) states
> the following :
>
> //
>
> * /Install the bookmarklet from the cms
> <https://cms.apache.org/#bookmark> page.You only have to do this once./
> * /Navigate to the page you wish to edit (on the live site, not in the
> cms)./
> * /Click the bookmarklet.There will be a short pause while the CMS
> system is initialised for you./
> * /Click on |Edit| (to skip this step hack the bookmarklet to add an
> 'action=edit'param to the bookmarklet's query string)/
> * /The page editor should then be displayed./
> * /Click |Submit| to save your edit to the workarea/
> * /Click |Commit| to save the updated file to SVN and trigger a staged
> build. (to skip this step click on the "Quick Commit" checkbox in
> the |Edit| form)./
> * /The results should appear shortly on the staging
> <http://www.staging.apache.org/dev/cms.html> site. (You may have to
> force the page to refresh in order to see the updated content)/
> * /Once you are happy with the updated page, click on |Publish Site|
> to deploy./
>
> The plugins mentioned here are only accessible to committers.
>
> Alternatively I think we can directly update the mdtext files and that
> should put things on the staging site in sometime. Then it can be published
> from there.
>
> regards,
> Rahul
Re: Mahout wiki migration
Posted by Rahul <rs...@xebia.com>.
For usage the CMS docs (http://www.staging.apache.org/dev/cms.html)
states the following :
//
* /Install the bookmarklet from the cms
<https://cms.apache.org/#bookmark> page.You only have to do this once./
* /Navigate to the page you wish to edit (on the live site, not in the
cms)./
* /Click the bookmarklet.There will be a short pause while the CMS
system is initialised for you./
* /Click on |Edit| (to skip this step hack the bookmarklet to add an
'action=edit'param to the bookmarklet's query string)/
* /The page editor should then be displayed./
* /Click |Submit| to save your edit to the workarea/
* /Click |Commit| to save the updated file to SVN and trigger a staged
build. (to skip this step click on the "Quick Commit" checkbox in
the |Edit| form)./
* /The results should appear shortly on the staging
<http://www.staging.apache.org/dev/cms.html> site. (You may have to
force the page to refresh in order to see the updated content)/
* /Once you are happy with the updated page, click on |Publish Site|
to deploy./
The plugins mentioned here are only accessible to committers.
Alternatively I think we can directly update the mdtext files and that
should put things on the staging site in sometime. Then it can be
published from there.
regards,
Rahul
On 12-07-2012 15:07, Sean Owen wrote:
> Superb! this is great work Rahul. I committed this to
> mahout/site/trunk, as per the examples. I also submitted the ticket.
> We'll see what happens.
>
> The existing mahout.apache.org website is still there under
> (ironically) mahout/new_website. That stays. new_website = web site,
> site = wiki.
>
> Now I suppose we all need to figure out how to use the CMS!
>
> On Thu, Jul 12, 2012 at 8:45 AM, Rahul <rs...@xebia.com> wrote:
>> I have migrated Mahout confluence wiki to CMS Markdown format, see :
>> http://rahul-summit.rhcloud.com/content/mahout-wiki.html.
>> All of the pages have been moved but they are missing the comments section,
>> as the same could not be retrieved from confluence.
>> The tar file for the migrated content can be found
>> athttps://docs.google.com/open?id=0B9t-MulUcHvyQWxJSF9YOUFBZEk
>> <https://docs.google.com/open?id=0B9t-MulUcHvyQWxJSF9YOUFBZEk>
>>
>> In order to comple the migration, the migrated content needs to be committed
>> in Mahout svn in the following structure :
>>
>> $REPO/trunk/
>> content/
>> lib/
>> cgi-bin/
>> templates/
>>
>> After that a ticket needs to be raised in
>> https://whimsy.apache.org/officers/cmsreq by a mentor.
>>
>> regards,
>> Rahul
Re: Mahout wiki migration
Posted by Sean Owen <sr...@gmail.com>.
Superb! this is great work Rahul. I committed this to
mahout/site/trunk, as per the examples. I also submitted the ticket.
We'll see what happens.
The existing mahout.apache.org website is still there under
(ironically) mahout/new_website. That stays. new_website = web site,
site = wiki.
Now I suppose we all need to figure out how to use the CMS!
On Thu, Jul 12, 2012 at 8:45 AM, Rahul <rs...@xebia.com> wrote:
> I have migrated Mahout confluence wiki to CMS Markdown format, see :
> http://rahul-summit.rhcloud.com/content/mahout-wiki.html.
> All of the pages have been moved but they are missing the comments section,
> as the same could not be retrieved from confluence.
> The tar file for the migrated content can be found
> athttps://docs.google.com/open?id=0B9t-MulUcHvyQWxJSF9YOUFBZEk
> <https://docs.google.com/open?id=0B9t-MulUcHvyQWxJSF9YOUFBZEk>
>
> In order to comple the migration, the migrated content needs to be committed
> in Mahout svn in the following structure :
>
> $REPO/trunk/
> content/
> lib/
> cgi-bin/
> templates/
>
> After that a ticket needs to be raised in
> https://whimsy.apache.org/officers/cmsreq by a mentor.
>
> regards,
> Rahul