> -----Original Message----- > From: Dave Fisher [mailto:w...@apache.org] > Sent: Wednesday, December 30, 2020 4:47 PM > To: dev@openoffice.apache.org > Subject: Re: Policy to deal with old web content - Archiving pages? >
> The two websites are in a Git repository and changes can be > reverted. There is no need to be concerned about mistakes. > > MediaWiki pages track versions. I think (but need > confirmation) that as long as pages are not moved or deleted > that changes can be reverted. > > I fail to see a need to officially archive separately when > our tools already fill this need. I don't see such a need either *IF* things are as you describe. But are things really like that? Personally, I don't know if things are like that because I lack the technical background knowledge. what I'm wondering is, therefore: Is the git repository a reliable archive in the long run? Does the existence of the git entries also make it possible to access the old website/wiki at any time and not only its 'technical background platform' (=entries in git)? For me, for example, it is unclear that if we have Git and also have a CMS, what happens when we switch to the new CMS. If (I don't know) the old Git entries are then no longer 'displayed' because the old CMS is no longer running, the Git entries are no good as an archive. > Plus, the Way Back Machine - web.archive.org is crawling our > websites since 2011. absolutely unusable, because no complete archive! Even my private archive of our web pages and wiki is more complete, although far from complete. Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
