Thanks Matthias...
I didn't know if the control over publishing with --
https://cms.apache.org/
still worked or not.
I will investigate on my own soon.
On Thu, Aug 1, 2019 at 11:38 AM Matthias Seidel
wrote:
> Hi Kay,
>
> Am 31.07.19 um 23:49 schrieb Kay Schenk:
> > Hi all.
> > A few questions
Hi Kay,
Am 31.07.19 um 23:49 schrieb Kay Schenk:
> Hi all.
> A few questions --
> * what's the status of the current OO website repositories -- both
> https://openoffice.apache.org/ and https://www.openoffice.org/
> in terms of updates? Are they both, as of today, still svn checkout?
It is still
Hi all.
A few questions --
* what's the status of the current OO website repositories -- both
https://openoffice.apache.org/ and https://www.openoffice.org/
in terms of updates? Are they both, as of today, still svn checkout?
* and since the CMS is broken (?), do updates to through svn go live
ins
On 31.07.19 01:29, Dave Fisher wrote:
>> they replace it with another self baked solution... :/
> No, they prefer Pelican: https://github.com/getpelican/pelican it will
> support Github’s markdown and allow the preview of content within GitHub.
>
Hmm sorry, I thought for some reason that they a
> On Jul 30, 2019, at 3:29 PM, Peter Kovacs wrote:
>
>
> On 31.07.19 00:18, Matthias Seidel wrote
>>> I don't understand:
>>> Why is migration necessary at all?
>> I already told you on users-de@. ASF Infra can not support the old (self
>> baked) CMS anymore.
>
> they replace it with another
> On Jul 30, 2019, at 3:56 PM, Jörg Schmidt wrote:
>
> Hello Peter,
>
>> From: Peter Kovacs [mailto:pe...@apache.org]
>> Sent: Wednesday, July 31, 2019 12:07 AM
>> To: dev@openoffice.apache.org
>> Subject: Re: [discussion] CMS migration
>
Hello Mathias,
> From: Matthias Seidel [mailto:matthias.sei...@hamburg.de]
> Sent: Wednesday, July 31, 2019 12:19 AM
> To: dev@openoffice.apache.org
> Subject: Re: [discussion] CMS migration
> > If we make mistakes, the loss of information will be a
> disaster. Not necess
Hello Peter,
> From: Peter Kovacs [mailto:pe...@apache.org]
> Sent: Wednesday, July 31, 2019 12:07 AM
> To: dev@openoffice.apache.org
> Subject: Re: [discussion] CMS migration
> >> Maybe it would be nice to make a openoffice.org memorial.
> publishing a
> >>
On 31.07.19 00:18, Matthias Seidel wrote
>> I don't understand:
>> Why is migration necessary at all?
> I already told you on users-de@. ASF Infra can not support the old (self
> baked) CMS anymore.
they replace it with another self baked solution... :/
With less overhead maybe.
-
lto:pe...@apache.org]
>> Sent: Tuesday, July 30, 2019 7:58 AM
>> To: dev@openoffice.apache.org; Gavin McDonald
>> Subject: Re: [discussion] CMS migration
>> I had a quick look at the content. I think we do not need to migrate
>> everything. We should think about reduc
On 30.07.19 23:32, Jörg Schmidt wrote:
> Hello,
>
> A fundamental question first:
> The "CMS migration" won't touch the wiki content? Right?
>
> (i mean: wiki.openoffice.org)
Not in the focus in this discussion. Personally I would like to. But
this is a huge amount of work too. And not something
Hello,
A fundamental question first:
The "CMS migration" won't touch the wiki content? Right?
(i mean: wiki.openoffice.org)
> From: Peter Kovacs [mailto:pe...@apache.org]
> Sent: Tuesday, July 30, 2019 7:58 AM
> To: dev@openoffice.apache.org; Gavin McDonald
> Su
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
> 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 an
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) an
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 tha
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 ma
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 our
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
fit
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 header
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 propo
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 s
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 with
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 our website pages.
>
> Marcus
>
>
Ther
24 matches
Mail list logo
