[
https://issues.apache.org/jira/browse/MAHOUT-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855202#comment-13855202
]
Isabel Drost-Fromm commented on MAHOUT-1305:
--------------------------------------------
Just received a question for open tasks. Here is what I think should be done in
terms of (Confluence) Wiki rework:
- Delete all pages that have bogus content (comments that essentially are
questions best answered on the mailing list only, old release notes, etc.)
- Delete all pages that have been migrated to Apache CMS (or have been migrated
and later deleted from CMS for being outdated) - with one exception:
- Move all pages that in the past have been referred to in issues and on the
user/dev lists under a common parent, delete their content and instead add a
link to the new page's URL so users aren't lost.
- For the rest that remains find a structure that is easy to understand and
navigate.
The goal should be to keep stable, reliable documentation in CMS. Stuff that is
in flux or a draft only is fine to remain in Confluence.
> Rework the wiki
> ---------------
>
> Key: MAHOUT-1305
> URL: https://issues.apache.org/jira/browse/MAHOUT-1305
> Project: Mahout
> Issue Type: Bug
> Components: Website
> Reporter: Sebastian Schelter
> Priority: Blocker
> Fix For: 0.9
>
> Attachments: MAHOUT-221213-1315-15716.pdf
>
>
> We should think about completely redoing our wiki. At the moment, we're
> listing lots of algorithms that we either never implemented or already
> removed. I also have the impression that a lot of stuff is outdated.
> It would be awesome if we had an up-to-date documentation of the code with
> instructions on how to get into using mahout quickly.
> We should also have examples for all our 3 C's.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
