Re: [discussion] CMS migration

2019-07-29 Thread Peter Kovacs
On 29.07.19 21:11, Dave Fisher wrote: > > Please proceed with small examples and test with other languages. The whole > of OpenOffice.org is large - aka 9GB. There are decisions to make as we go > along. > > Someone needs to make a roadmap for OpenOffice.org. Someone needs to > understand how

Re: [discussion] CMS migration

2019-07-29 Thread Dave Fisher
> On Jul 29, 2019, at 12:08 PM, Peter Kovacs wrote: > > > On 29.07.19 21:06, Marcus wrote: >> >> that sounds very good. >> >> Yes, please give us a note when it's finished (or ready for a serious >> beta test) and how to use it. Then we can test a bit. Please proceed with small examples

Re: [discussion] CMS migration

2019-07-29 Thread George Karalis
Hi all, Just so you know, whatever you decide am willing to help with the migration > On 29 Jul 2019, at 22:08, Peter Kovacs wrote: > > > On 29.07.19 21:06, Marcus wrote: >> >> that sounds very good. >> >> Yes, please give us a note when it's finished (or ready for a serious >> beta test)

Re: [discussion] CMS migration

2019-07-29 Thread Peter Kovacs
On 29.07.19 21:06, Marcus wrote: > > that sounds very good. > > Yes, please give us a note when it's finished (or ready for a serious > beta test) and how to use it. Then we can test a bit. > > Thanks > > Marcus > > The infra page is already on the site. I would opt if we want to go this rout

Re: [discussion] CMS migration

2019-07-29 Thread Marcus
Am 29.07.19 um 10:48 schrieb Gavin McDonald: On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote: I have proposed some time ago the move to a static site generator — like Jekyll, Hugo etc. — as I was redesigning OpenOffice’s front-page. That would greatly help reduce tech diversity and

Re: [discussion] CMS migration

2019-07-29 Thread Marcus
Am 29.07.19 um 00:53 schrieb Peter Kovacs: On 28.07.19 23:10, Marcus wrote: Am 28.07.19 um 21:31 schrieb Peter Kovacs: Cms will be shut down soon. The question is how we deal with this. Info is in the chat protocol in my original post. OK, then we will have a big problem in order to serve

Re: [discussion] CMS migration (was: svn migration plan)

2019-07-29 Thread Peter Kovacs
Welcome back George, yes I have not forgotten your work. I do hope you continue. I am really happy on your post. I liked your proposal for the new design. I would really like to see that they move into our "production". The only thing is that in my opinion the static side generator does not

Re: [discussion] svn migration plan

2019-07-29 Thread Marcus
Am 29.07.19 um 00:17 schrieb Matthias Seidel: Am 28.07.19 um 23:12 schrieb Marcus: Am 28.07.19 um 20:29 schrieb Matthias Seidel: Am 28.07.19 um 20:12 schrieb Marcus: Am 27.07.19 um 13:45 schrieb Matthias Seidel: Am 23.07.19 um 11:08 schrieb Matthias Seidel: Am 21.07.19 um 12:27 schrieb

Re: [discussion] svn migration plan

2019-07-29 Thread Peter Kovacs
On 29.07.19 17:18, Matthias Seidel wrote: > Hi Peter, > > Am 29.07.19 um 00:39 schrieb Peter Kovacs: >> A different suggestion we use the git commit count. The command is: >> >> |git rev-list --all --count It will deliver something that looks similar >> to the svn number we already use. All the

Building AOO under Debian

2019-07-29 Thread Mechtilde
Hello developers, I'm extending my build environment to build a AOO version close to the release build. I took the configure script published in SVN. Then I stumble about not be able to download e.g. README_silgraphite-2.3.1.txt, which contains the license. Is't ok to put this file into

Re: [discussion] CMS migration (was: svn migration plan)

2019-07-29 Thread Dave Fisher
BTW - A good portion of the site is html as donated in 2011. It is extracted using additional functions in the CMS and then wrapped in the templates. There is about 9GB content and as the template was developed we hammered the CMS system. We will need to revisit how we handle NL for the

Re: [discussion] svn migration plan

2019-07-29 Thread Matthias Seidel
Hi Peter, Am 29.07.19 um 00:39 schrieb Peter Kovacs: > A different suggestion we use the git commit count. The command is: > > |git rev-list --all --count It will deliver something that looks similar > to the svn number we already use. All the Best Peter | How would such a simple count point to

Re: [discussion] CMS migration (was: svn migration plan)

2019-07-29 Thread Raphael Bircher
Hi Gavin Sounds like a load of work, Especially for the Templates. Does Pelican serve HTML and markdown mixed? Regards Raphael. On Mon, Jul 29, 2019 at 10:48 AM Gavin McDonald wrote: > > Hi all, > > On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote: > > > > Hello Peter, > > > > I have

Re: [discussion] CMS migration (was: svn migration plan)

2019-07-29 Thread Gavin McDonald
Hi all, On Mon, Jul 29, 2019 at 9:18 AM George Karalis wrote: > > Hello Peter, > > I have proposed some time ago the move to a static site generator — like Jekyll, Hugo etc. — > as I was redesigning OpenOffice’s front-page. That would greatly help reduce tech diversity > and maintenance as only

Re: [discussion] CMS migration (was: svn migration plan)

2019-07-29 Thread George Karalis
Hello Peter, I have proposed some time ago the move to a static site generator — like Jekyll, Hugo etc. — as I was redesigning OpenOffice’s front-page. That would greatly help reduce tech diversity and maintenance as only static html files will be served. Most static site generators work