Re: CMS FAQ
On 03/27/2015 08:56 AM, Marcus wrote: Am 03/27/2015 04:21 PM, schrieb jan i: On Friday, March 27, 2015, Marcusmarcus.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. I agree with Marcus's comments. What I see is the CMS supplies the following -- 1. GUI editor for quick changes 2. The rules/underpinnings for what gets processed and how it gets processed for each web site (the perl modules contained in the /lib directory) 3. automagic markdown (mdtext) processing 4. Django template processing (uses the rules from item 2) AOO uses ALL of these! In my opinion, items 2- 4 are MOST critical, more so than the GUI. The FAQ doesn't really address the processing capabilities of the CMS. If we don't have these capabilities, then what? We can do some of this if each project were given access to its own customized http configuration and cron jobs or something but short of that, I'm not seeing an alternative solution right at the moment. 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. thats right. And because of your answers and our requirements (MD - HTML conversation, template engine, non-geek editor) I fear that it will be the easiest and fastest solution for our project when we do it with the VM. And try to find something more modern and standarized in the course of time. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- - MzK “What is the point of being alive if you don't at least try to do something remarkable?” -- John Green, An Abundance of Katherines - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: CMS FAQ
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: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: CMS FAQ
Am 03/27/2015 04:21 PM, schrieb jan i: On Friday, March 27, 2015, Marcusmarcus.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. thats right. And because of your answers and our requirements (MD - HTML conversation, template engine, non-geek editor) I fear that it will be the easiest and fastest solution for our project when we do it with the VM. And try to find something more modern and standarized in the course of time. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: CMS FAQ
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.
Re: CMS FAQ
My concern is that with the proposal the GUI is going away. On Mar 26, 2015, at 12:09 AM, jan i wrote: Hi All In the ongoing discussion (apache wide) Infra has now made a FAQ, which is worth reading. https://cwiki.apache.org/confluence/display/INFRA/CMS+Decommissioning+RFC+-+Frequently+Asked+Questions Remark, due to some disussions, Infra made this disclaimer: This is ONLY a request for commentary from the community on a proposal by Infra to work towards decommissioning the CMS. It is NOT an express statement by the infra group that we will be taking any specific action(s). We seek input from the community on this proposal so that we can make more informed decisions on the future direction of CMS support, whether that be via replacement, via resources applied to bring the existing CMS to acceptable support standards, or some other option TBD. 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). Or alternatively (something that currently seems less work): - Get a VM, install CMS and run it for us. rgds jan I. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
