[Infrastructure] Wiki feature requirements

[Wayne Thayer]

This is a good list Jos. The one thing I might add is some requirement on
storage capacity. Perhaps we can find out how much space files on the
current wiki are consuming as a baseline? I think our current policy is to
regularly purge meeting recordings, but if we were to decide to save those
it would add up quickly.

On Wed, Oct 31, 2018 at 10:44 AM Jos Purvis (jopurvis) <jopurvis at cisco.com>
wrote:

> Based on a quick review of our current wiki, here are the elements I saw
> us currently using that look like requirements:
>
>    1. Table of contents (automatic)
>    2. Page links with manual link display (link|title)
>    3. Hyperlinks
>    4. Tables
>       1. Header row and column
>       2. Line breaks in cells
>    5. Bullets
>    6. Numbering
>       1. Nested numbering (1 a/b/c, 2 a/b/c)
>    7. Document attachments
>       1. Listing of attachments
>       2. Linking to attachments inside pages
>       3. Versioning of attachments?
>    8. Monospaced/plain-text font as word or code block
>    9. Page versioning with diffs and reversion
>    10. GUI/Visual editing
>       1. Text-mode editing (optional?)
>       2. Markdown page language (optional?)
>    11. Per-user authentication with full content restriction (that is,
>    none of the wiki is viewable without authentication)
>    12. Wide browser support (at least Edge/Firefox/Chrome/Safari)
>
>
>
> Here are some additional requirements that we don’t have right now but
> will definitely need:
>
>    1. Separate spaces on the wiki with granular/differentiable access
>    rights
>    2. User groups (eases management of space access rights significantly)
>    3. User self-management of profiles (registration with approval,
>    password changes)
>    4. Sub-spaces with inherited or differentiated access rights
>
>
>
> In addition, we might consider these optional features as nice-to-haves
> but not requirements:
>
>    1. Polling capability (eliminate the use of Doodle)
>    2. Display of attachment content in a page (don’t just link it, show
>    the contents of the doc)
>    3. Page export to standard formats (DOCX, PDF)
>    4. Calendar capability
>
>
>
>
>
>
>
> --
> Jos Purvis (jopurvis at cisco.com)
> .:|:.:|:. cisco systems  | Cryptographic Services
> PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)
>
>
> _______________________________________________
> Infrastructure mailing list
> Infrastructure at cabforum.org
> http://cabforum.org/mailman/listinfo/infrastructure
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/infrastructure/attachments/20181031/e7807162/attachment.html>