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.
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?
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.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
