On Friday, March 27, 2015, Marcus <marcus.m...@wtnet.de> wrote: > Am 03/26/2015 08:09 AM, schrieb jan i: > >> In the ongoing discussion (apache wide) Infra has now made a FAQ, which is >> worth reading. >> >> [...] >> >> If the CMS were to be decommissioned in the way currently suggested, we >> would have a couple of challenges: >> - Find a replacement online edtitor for our translators (who are also >> committers) >> - Find a way to keep the templates active in pure HTML >> - Decide not to use markdown but only html (BAD for our translators). >> > > I don't know if it's because I don't know how this all works together or > haven't understood it. But I've expected a bit more details what a > decommission means and a working substition could be.
There are no more details from infra. They want to stop CMS and leave projects with svnpubsub which merely publishes generated html. > > Especially the proposed replacements are unclear. Do the projects have to > find an ownsolution for their website? Or is there one solution that will > be chosen by the majority? yes projects have to fund their own solution, as stated in the FAQ Infra do no want to support a central solution. > > So, I don't know that to say or how to help - except don't change it. But > this seems not to be a solution. ;-) > > Or alternatively (something that currently seems less work): >> - Get a VM, install CMS and run it for us. >> > > You mean the one, that is planned to be shutdown? If so, as long as there > are no problems/bugs it can work. But when problems cannot be solved > anymore we are stuck and maybe no longer able to publish anything. So, > latest then we need a replacement. Well at least it buys us time. rgds jan i > > Marcus > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Sent from My iPad, sorry for any misspellings.
