On 12/30/2020 2:18 AM, Jörg Schmidt wrote: > > >> -----Original Message----- >> From: Keith N. McKenna [mailto:keith.mcke...@comcast.net] >> Sent: Wednesday, December 30, 2020 2:29 AM >> To: dev@openoffice.apache.org >> Subject: Re: Policy to deal with old web content - Archiving pages? > >>> If only parts are outdated, then the complete page cannot >> be outdated. >>> Then we have to mark only the respective parts as outdated. >>> >> >> This has been a problem on the wiki for years, even before the project >> came to Apache. It has only gotten worse as we have hemorrhaged people >> capable of keeping these pages up to date. >> >> >>>> Many pages are seemingly(!) outdated, but in reality they >> are needed >>>> (e.g. for the daily voluntary support on mailing lists or >> in forums). >>>> Look e.g. at the extremely important pages with technical >> info for the >>>> creation of extensions: >>>> >> https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extens >> ions/Extensions >>>> >>> >>> Maybe we should send pointers to these collections of pages >> to dev@ and >>> judge case by case what to do. >>> >> That may be the best way to proceed at the moment. If we know what >> articles need work we can pool our resources and develop a plan to >> update what we can to a usable level. > > Yes, without a doubt, but it has nothing to do with archiving.
I respectfully disagree that this thread is only about archiving. The thread started as a general question about how to handle outdated wiki documentation. Some one changed the tittle of the thread and put archiving? in the tittle. That does not constitute changing the subject of the thread. At best it adds a sub-topic. > > The discussion here is already huge, but we're not making any progress > because we're talking too much about the details. That is what a discussion is supposed to be all about; discovering other ways to do what is being asked about. > > If I, comparatively, have a file whose contents I want to update, what do I > do? > > 1. I make a copy of the file first, just to be safe. > 2. I make the necessary changes to the file. > > And regarding the website and the wiki, we should first clarify how to do > point 1, where the term for this is not "copy", but "archive". > That is really a very simple question too answer. The mwiki makes a new version every time you save your edits. If the edits are not to your liking you can either edit that new version, or revert the current back to the previous one. Both Websites are now in separate repositories in or gitbox repository. any committer can make changes to the pages which will be sent first to the staging website where they can be viewed and decide whether or not they meet your intent. Like all other commits they can also be reverted if they get to the website and there are objections to them or edited again to make the needed corrections or additions. Regards Keith > > > Jörg >
signature.asc
Description: OpenPGP digital signature
