[Owasp-leaders] wiki - project versioning question?

Achim achim at owasp.org
Fri May 15 13:05:47 UTC 2015


hmm, copying something which then will be there twice and the ability to change the copy does not make sence.
mediawiki provides a version which always can be seen in the history, so there
is no need to duplicate data which is supposed to be changed later. Note that
mediawiki cannot restrict editors to chnage the copy. 
So just makeing a copy of something which mediawiki already provides just for
versioning reason renders the purpose --versioning-- ad absurdum.

I'd recommend not to copy pages which MUST be static in future.

If there is a need to keep older version visible, make a PDF or alike and
place the link in the current page.

Just my 2 pence

On 15.05.2015 14:28, Noreen Whysel wrote:
> Wikis have their own built in kind of "versioning" in its ability to render every historical change in the View History page. If you want something more obviously labeled as version 1.0, 2.0, 3.0 etc you can always create a new page or set of tabbed pages with the new version number and subordinate the old one on an archive page/tab. Just copy the content from the old version into a new page and updated it with the latest github links, news, for that version. I'd recommend keeping a general SAMM landing page perhaps with a tab to the archived versions.
> Noreen Whysel
> Community Manager
> OWASP Foundation

More information about the OWASP-Leaders mailing list