Goto https://GitHub.com/Apache/OpenOffice-org/ to enter the current website “house”.
Read the docs and look at the branches. Educate yourself to the current technical details. Ask educated questions after Jan 1 in a single email in a new thread. We also have the svn repos which has all the changes from Dec 2011-Oct 2020. Trust me for now. I’ll provide a URL in a few days. The ASF keeps all of repositories on our infrastructure forever. All changes and builds are logged. Look at comm...@openoffice.apache.org Thanks, Dave Sent from my iPhone > On Dec 31, 2020, at 1:30 AM, Jörg Schmidt <joe...@j-m-schmidt.de> wrote: > > > >> -----Original Message----- >> From: Peter Kovacs [mailto:pe...@apache.org] >> Sent: Wednesday, December 30, 2020 11:06 AM >> To: dev@openoffice.apache.org >> Subject: Re: Policy to deal with old web content - Archiving pages? >> >> >>> On 30.12.20 00:08, Dave Fisher wrote: >>> >>>> On Dec 29, 2020, at 11:50 AM, Fernando Cassia >> <fcas...@gmail.com> wrote: >>>> >>>> On Tue., 29 Dec. 2020, 05:55 Jörg Schmidt, >> <joe...@j-m-schmidt.de> wrote: >>>> >>>>> >>>>> >>>>> Much easier, and imho functionally sufficient, would be a >> footer on each >>>>> archive page informing that this is an archive page plus >> a link to the >>>>> start page (web and wiki) of the current pages. >>>>> >>>> I like the model used by Mozilla here: >>>> >>>> >> https://developer.mozilla.org/en-US/docs/Archive/Web/Browser_D >> etection_and_Cross_Browser_Support >>>> >>>> Header " *This is an archived page.* It's not actively maintained." >>>> >>>> Blurb: " *Warning:* *The content of this article may be >> out of date.* This >>>> article was written in 2003" >>> I like that approach. >>> >>> I’ll work to support it. >> >> I can work with this too. However currently you can select one or the >> other for all our pages. >> >> In the discussion we have to go through each page and decide >> what we do >> with this page. I do not believe there is any way to get around the >> principle. >> >> That is why I would like to have a basic concept that we can >> apply. And >> the concept should encourage work and not block it. In this >> context this >> seems like a fair approach > > The basic concept is simple: > > 1. create an archive of all web and wiki pages (a static archive should > suffice). > > 2. create a basic structure for the new web and wiki (start with one of them) > and consider technical constraints (e.g. the new CMS) > > 3. fill this basic structure with new pages by either: > -creating a new page from scratch > -taking an existing old page and updating it and adding an edit note to this > old page in the archive and a link to the new page. > > > And all we should do NOW! is to start with point 1. or finally clarify why it > can not be started. > What is nonsense is to wait with point 1. BECAUSE we have not yet clarified > all Details for 2. and 3. > > > > Why? > When I build a house, I also build the walls and the roof without having > discussed beforehand which color the carpet should have later. > > > Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
