[xwiki-devs] [Proposal] Officially deprecate GWT WYSIWYG editor and don't fix issues related to it
Hi devs, I’d like that we agree on an official position re the GWT WYSIWYG editor. We’ve already decided to make CKEditor the default editor and to keep the GWT editor bundled (but off by default) till the end of the 8.x cycle. I’d like now that we agree about 2 points: * We don’t fix issues related to the GWT editor that do not reproduce on the CKEditor editor. * Now remains the question as to whether we close them as won’t fix or not. Ideally the best IMO is to create a new JIRA project for the GWT Editor in the Contributed Extensions category, and move all opened JIRA issues to it. We create a version labelled “Previous versions when the GWT editor was in platform” so that we can use that as affects. Of course another option would be to not touch those issues FTM and wait till we do the move in 9.0+. I prefer moving the issues now if we agree now that we don’t fix issues related to the GWT editor. WDYT? Thanks -Vincent
Hi, If we retire it to contrib, then indeed, it needs its own jira project and the existing opened issues (bugs/improvements/etc) need to be move there. However, do keep in mind that we would still need to keep (or duplicate) the issues that still apply to the current WYSIWYG (CK) editor, specially on the improvements/new features side. +1 to move. Thanks, Eduard On Thu, Oct 13, 2016 at 8:38 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
I’d like that we agree on an official position re the GWT WYSIWYG editor.
We’ve already decided to make CKEditor the default editor and to keep the GWT editor bundled (but off by default) till the end of the 8.x cycle.
I’d like now that we agree about 2 points:
* We don’t fix issues related to the GWT editor that do not reproduce on the CKEditor editor. * Now remains the question as to whether we close them as won’t fix or not. Ideally the best IMO is to create a new JIRA project for the GWT Editor in the Contributed Extensions category, and move all opened JIRA issues to it. We create a version labelled “Previous versions when the GWT editor was in platform” so that we can use that as affects. Of course another option would be to not touch those issues FTM and wait till we do the move in 9.0+. I prefer moving the issues now if we agree now that we don’t fix issues related to the GWT editor.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 to move issue to a new jira project and duplicate those that reproduce in the new WYSIWYG On Fri, Oct 14, 2016 at 2:56 AM, Eduard Moraru <[email protected]> wrote:
Hi,
If we retire it to contrib, then indeed, it needs its own jira project and the existing opened issues (bugs/improvements/etc) need to be move there.
However, do keep in mind that we would still need to keep (or duplicate) the issues that still apply to the current WYSIWYG (CK) editor, specially on the improvements/new features side.
+1 to move.
Thanks, Eduard
On Thu, Oct 13, 2016 at 8:38 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
I’d like that we agree on an official position re the GWT WYSIWYG editor.
We’ve already decided to make CKEditor the default editor and to keep the GWT editor bundled (but off by default) till the end of the 8.x cycle.
I’d like now that we agree about 2 points:
* We don’t fix issues related to the GWT editor that do not reproduce on the CKEditor editor. * Now remains the question as to whether we close them as won’t fix or not. Ideally the best IMO is to create a new JIRA project for the GWT Editor in the Contributed Extensions category, and move all opened JIRA issues to it. We create a version labelled “Previous versions when the GWT editor was in platform” so that we can use that as affects. Of course another option would be to not touch those issues FTM and wait till we do the move in 9.0+. I prefer moving the issues now if we agree now that we don’t fix issues related to the GWT editor.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 to move the issues that don't affect CKEditor. On Thu, Oct 13, 2016 at 8:38 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
I’d like that we agree on an official position re the GWT WYSIWYG editor.
We’ve already decided to make CKEditor the default editor and to keep the GWT editor bundled (but off by default) till the end of the 8.x cycle.
I’d like now that we agree about 2 points:
* We don’t fix issues related to the GWT editor that do not reproduce on the CKEditor editor. * Now remains the question as to whether we close them as won’t fix or not. Ideally the best IMO is to create a new JIRA project for the GWT Editor in the Contributed Extensions category, and move all opened JIRA issues to it. We create a version labelled “Previous versions when the GWT editor was in platform” so that we can use that as affects. Of course another option would be to not touch those issues FTM and wait till we do the move in 9.0+. I prefer moving the issues now if we agree now that we don’t fix issues related to the GWT editor.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 Thanks, Caty On Mon, Oct 17, 2016 at 2:07 PM, Marius Dumitru Florea < [email protected]> wrote:
+1 to move the issues that don't affect CKEditor.
On Thu, Oct 13, 2016 at 8:38 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
I’d like that we agree on an official position re the GWT WYSIWYG editor.
We’ve already decided to make CKEditor the default editor and to keep the GWT editor bundled (but off by default) till the end of the 8.x cycle.
I’d like now that we agree about 2 points:
* We don’t fix issues related to the GWT editor that do not reproduce on the CKEditor editor. * Now remains the question as to whether we close them as won’t fix or not. Ideally the best IMO is to create a new JIRA project for the GWT Editor in the Contributed Extensions category, and move all opened JIRA issues to it. We create a version labelled “Previous versions when the GWT editor was in platform” so that we can use that as affects. Of course another option would be to not touch those issues FTM and wait till we do the move in 9.0+. I prefer moving the issues now if we agree now that we don’t fix issues related to the GWT editor.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (5)
-
Ecaterina Moraru (Valica) -
Eduard Moraru -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol