[xwiki-devs] [XWiki Day] BFD#198
Hello devs, This Thursday is BFD#198: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingday Our current status is: * -44 bugs over 120 days (4 months), i.e. we need to close 44 bugs to have created bugs == closed bugs * -139 bugs over 365 days (1 year) * -155 bugs over 500 days (between 1 and 2 years) * -367 bugs over 1600 days (4.3 years) See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#198 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14342 Good luck at fixing bugs, Lavinia
Re: [xwiki-devs] [Proposal] WCAG exception: consecutive line breaks
Hello, On Wed, Nov 21, 2018 at 5:36 PM Simon Urli wrote: > > Hi everyone, > > one of the most validation error we have with WCAG is about consecutive > line breaks: basically a presents in a page. > > This happens mostly in our translation pages since the linebreaks in > plain syntax are translated in tags. > Caty provided a lot of details about this error on the related issue: > https://jira.xwiki.org/browse/XWIKI-15666. > > Currently we have around 140 validations failure because of this. > > Different proposal have been made in order to fix it, that I will try to > sum-up here: > >A. Remove completely this validation check -0, I think the validation can be useful at least to keep good practices. >B. Add an exception for the translation pages +1, simplest one. >C. Triggers the error only if more than 2 consecutive breaks is > encountered -1, it doesn't really makes sense to do that, it's like B. but badly done. >D. Create a rendering syntax dedicated to translation pages +1, could be a good idea but might be complicated. > > > A. Remove completely the validation check > > pros: >* the easiest one >* apparently the rule is not checked in other accessibility test, so > its real purpose for accessibility is unclear > > cons: >* IMO this rule is useful for checking the good practice of not using > > > B. Add an exception for the translation pages > > pros: >* same as for A > > cons: >* ? > > C. Triggers the error only if more than 2 consecutive breaks is encountered > > pros: >* ? > > cons: >* we would miss some consecutive that are used only for style > and we would catch some others in translations if we do 3 linebreaks > instead of 2. IMO it's only moving the problem > > D. Create a rendering syntax dedicated to translation pages > > pros: >* remove completely the problem of consecutive in translations >* can maybe be used to present them in another way? > > cons: >* need to develop/test/maintain a new rendering syntax > > I'd personnaly vote like this: > A: +0 > B: +1 > C: -1 > D: +0 > > WDYT? > > Simon > -- > Simon Urli > Software Engineer at XWiki SAS > simon.u...@xwiki.com > More about us at http://www.xwiki.com
[xwiki-devs] [Proposal] WCAG exception: consecutive line breaks
Hi everyone, one of the most validation error we have with WCAG is about consecutive line breaks: basically a presents in a page. This happens mostly in our translation pages since the linebreaks in plain syntax are translated in tags. Caty provided a lot of details about this error on the related issue: https://jira.xwiki.org/browse/XWIKI-15666. Currently we have around 140 validations failure because of this. Different proposal have been made in order to fix it, that I will try to sum-up here: A. Remove completely this validation check B. Add an exception for the translation pages C. Triggers the error only if more than 2 consecutive breaks is encountered D. Create a rendering syntax dedicated to translation pages A. Remove completely the validation check pros: * the easiest one * apparently the rule is not checked in other accessibility test, so its real purpose for accessibility is unclear cons: * IMO this rule is useful for checking the good practice of not using B. Add an exception for the translation pages pros: * same as for A cons: * ? C. Triggers the error only if more than 2 consecutive breaks is encountered pros: * ? cons: * we would miss some consecutive that are used only for style and we would catch some others in translations if we do 3 linebreaks instead of 2. IMO it's only moving the problem D. Create a rendering syntax dedicated to translation pages pros: * remove completely the problem of consecutive in translations * can maybe be used to present them in another way? cons: * need to develop/test/maintain a new rendering syntax I'd personnaly vote like this: A: +0 B: +1 C: -1 D: +0 WDYT? Simon -- Simon Urli Software Engineer at XWiki SAS simon.u...@xwiki.com More about us at http://www.xwiki.com
Re: [xwiki-devs] [ANN] XWiki 10.10-rc-1 released
https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/#HMacrocontentcanbedeclaredtobeinlineeditable I've not put it at the beginning of my summary since it's targeted for developers right now. I don't want user complaining because they cannot update a macro content with the "inline" mode. AFAIK there is no macro right now that handle it? Le mer. 21 nov. 2018 à 16:31, Vincent Massol a écrit : > Hi Guillaume, > > > On 21 Nov 2018, at 16:21, Guillaume Delhumeau < > guillaume.delhum...@xwiki.com> wrote: > > > > The XWiki development team is proud to announce the availability of XWiki > > 10.10-rc-1. > > Thanks! > > > For users, this version brings a protection when a page containing an > > XClass is moved or renamed. By default, the PDF export looks better now. > In > > addition, the recent auto-suggestion feature has been enabled in a few > > places. > > It’s auto-suggestion of page references actually. > > > For developers, a new asynchronous framework has been created. It allows > > the execution of desired parts of the rendering of a page to be executed > > asynchronously, with an AJAX request. This makes the rendering of the > page > > faster, making the least important parts visible after the page is > loaded. > > > > Among other things, Wiki Macros can now have typed parameters and it is > now > > possible to make the content of a macro editable inline with the WYSIWYG > > editor. > > This is really the key highlight for users IMO. I would have put this at > the top as the main user feature. > > Also and very importantly it’s missing from > https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/. > That’s bad since it’s the main feature :) Did I miss something? > > Thanks > -Vincent > > > To finish, more than 30 bugs have been fixed since XWiki 10.9. > > You can download it here: > https://www.xwiki.org/xwiki/bin/view/Main/Download > > > > Make sure to review the release notes: > > https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/ > > > > Thanks for your support > > -The XWiki dev team > > -- Guillaume Delhumeau (guillaume.delhum...@xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
Re: [xwiki-devs] [ANN] XWiki 10.10-rc-1 released
Hi Guillaume, > On 21 Nov 2018, at 16:21, Guillaume Delhumeau > wrote: > > The XWiki development team is proud to announce the availability of XWiki > 10.10-rc-1. Thanks! > For users, this version brings a protection when a page containing an > XClass is moved or renamed. By default, the PDF export looks better now. In > addition, the recent auto-suggestion feature has been enabled in a few > places. It’s auto-suggestion of page references actually. > For developers, a new asynchronous framework has been created. It allows > the execution of desired parts of the rendering of a page to be executed > asynchronously, with an AJAX request. This makes the rendering of the page > faster, making the least important parts visible after the page is loaded. > > Among other things, Wiki Macros can now have typed parameters and it is now > possible to make the content of a macro editable inline with the WYSIWYG > editor. This is really the key highlight for users IMO. I would have put this at the top as the main user feature. Also and very importantly it’s missing from https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/. That’s bad since it’s the main feature :) Did I miss something? Thanks -Vincent > To finish, more than 30 bugs have been fixed since XWiki 10.9. > You can download it here: https://www.xwiki.org/xwiki/bin/view/Main/Download > > Make sure to review the release notes: > https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/ > > Thanks for your support > -The XWiki dev team
[xwiki-devs] [ANN] XWiki 10.10-rc-1 released
The XWiki development team is proud to announce the availability of XWiki 10.10-rc-1. For users, this version brings a protection when a page containing an XClass is moved or renamed. By default, the PDF export looks better now. In addition, the recent auto-suggestion feature has been enabled in a few places. For developers, a new asynchronous framework has been created. It allows the execution of desired parts of the rendering of a page to be executed asynchronously, with an AJAX request. This makes the rendering of the page faster, making the least important parts visible after the page is loaded. Among other things, Wiki Macros can now have typed parameters and it is now possible to make the content of a macro editable inline with the WYSIWYG editor. To finish, more than 30 bugs have been fixed since XWiki 10.9. You can download it here: https://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/ Thanks for your support -The XWiki dev team
Re: [xwiki-devs] [Proposal] Roadmap for XS 10.11
Hi devs, I also forgot to propose one item for 10.11: fixing WCAG failing tests. We currently have 260+ failing WVAG tests and we need to fix/reduce that number of failing tests. Please let me know if personally you’re ok to commit to fix at least some of them? Thanks -Vincent > On 19 Nov 2018, at 13:42, Vincent Massol wrote: > > Hi devs, > > Here’s a roadmap for XS 10.11 which is the last release of the 10.x > cycle/year. > > Goal: Mostly stabilization release (bug fixing and last moment polishing of > features introduced in the 10.x cycle) > > * All: BFD (20%) > * Thomas/Vincent: Improve STAMP KPIs (20%) > * All: Bug fixing/small polishing focus on items added during 10.x > * Marius/Adel: Auto complete of references in WYSIWYG Macro Dialog (+ > grouping feature so that users don't get both "page" and "reference" at the > same time + "deprecated"/"priority" to show "page" more proeminently than > "reference") > * Thomas: More async/caching of UIX. > * Thomas: Bug: https://jira.xwiki.org/browse/XWIKI-14635 : Unsupported > character exception is warned in console when downloading attachment > > Dates: > > * 10.11RC1: 17th of Dec 2018 > * 10.11Final: 24th-31st of Dec 2018 (I’m putting a range since it’s Christmas > and we don’t know who’ll be there) > > Let me know if you have remarks/questions. > > Thank you > -Vincent
