- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] Survey Personas 2017
by Ecaterina Moraru (Valica) 02 Apr '18

02 Apr '18

Hi devs, I've analyzed the 31 responses we got on the XWiki Feedback form in 2017. The purpose was to know our users better and to try to define some personas. http://design.xwiki.org/xwiki/bin/view/Proposal/SurveyPersona It would be nice to have more data to analyze or to know which users we want to target / focus on when deciding what to prioritize for development. Let me know if you find the findings interesting and if they match your hypothesis. The pool is not that big and is relative. Thanks, Caty P.S. We also have some older stats on these responses that can be used for comparison on http://www.xwiki.org/xwiki/bin/view/Blog/XEFeedbackSummary

1 0

[xwiki-devs] [Proposal] e.x.o improvements: grid, icons, colors
by Ecaterina Moraru (Valica) 02 Apr '18

02 Apr '18

Hi devs, Here are some ideas about how the repository application used on extensions.xwiki.org could look like if we were to provide multiple display layouts for extensions, require the contributors to add custom icons, colors and screenshots. http://design.xwiki.org/xwiki/bin/view/Proposal/exoGrid In terms of design I tried to make it look as a proper application store, but it will be heavily influenced on users providing ratings for extensions and contributors on providing quality icons / colors/ description / screenshots. In terms of interaction, the biggest change would be a revamp of the search functionality. Currently users are using it, but it's a generic search, focused on text results. Let me know what you think, Caty P.S. Proposal ideas iterated with Marius, Alex and Eduard.

4 4

[xwiki-devs] Please review my proposal!
by Vivek Iyer 30 Mar '18

30 Mar '18

Hi everyone! I've made my proposal for the blockly editor and since the deadline is tonight (India time) it would be great if this could be reviewed ASAP! The link for my proposal is: https://docs.google.com/document/d/1oKmfXGZnxVSGnShkIZ8irfuX4qhR1br3LtKczmc… Thanking you, Regards, Vivek Iyer

2 1

[xwiki-devs] [XWiki Day] BFD#171
by Alex Cotiugă 30 Mar '18

30 Mar '18

Hello devs, This Thursday is BFD#171: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status is: * -47 bugs over 120 days (4 months), i.e. we need to close 47 bugs to have created bugs # = closed bugs # * -96 bugs over 365 days (1 year) * -111 bugs over 500 days (between 1 and 2 years) * -313 bugs over 1600 days (4.3 years) * -720 bugs since the beginning of XWiki See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#171 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14093 Happy Bug Fixing Day, Alex

1 1

[xwiki-devs] Add a REST API to XWiki Notifications
by nikos delis 28 Mar '18

28 Mar '18

Hi all, I am new on this mailist and thanks for the invite.I have do proposal for Add a Rest API to XWiki Notifications. mr Clément Aubin came into contact with me with some helpful links to understand how notifications is impliment on Xwiki platform and how notifications works.I see that you have a complete Notificaton API that works perfect for Xwiki platform therefore you want to make a REST API to take notifications from other platforms to Xwiki platform? I understood this from the speech .Second REST API will be created from scratch? or will build up on the existing? Thanks for reading Nikos.

4 8

[xwiki-devs] [ANN] XWiki 9.11.4 released
by Alex Cotiugă 27 Mar '18

27 Mar '18

The XWiki development team is proud to announce the availability of XWiki 9.11.4. This is a bugfix release that covers important issues that we have discovered since 9.11.3 has been released. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/9.11.4/ Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] replacing XSL-FO
by Mohamed Ashraf 27 Mar '18

27 Mar '18

If we should replacing the XSL-FO which we use to export PDF file out of XML, with XML and CSS only with open-source library , and I think * ”CSS Paged Media “ * is this good enough to do that , or there are any suggestion

4 10

[xwiki-devs] Hello!
by Vivek Iyer 27 Mar '18

27 Mar '18

Hi everyone, My name is Vivek Iyer (username: remorax on riot and on github) and I'm a Computer Science student from IIIT, Hyderabad, I'm in my second year and I would like to contribute to XWiki as part of GSoC. I have experience contributing to open source earlier, and I'm reasonably comfortable with the technology stack too and I'm passionate about coding and open source so I would love to contribute to XWiki! I'm in the process of making my proposal for the same, should I mail it here only for review, once its done? Do get back to me ASAP! Looking forward to working with you all, Regards, Vivek Iyer

2 1

[xwiki-devs] [ANN] XWiki 10.2 released
by Marius Dumitru Florea 26 Mar '18

26 Mar '18

The XWiki development team is proud to announce the availability of XWiki 10.2. This release has a fresh look thanks to its new default color theme. A new Figure macro is available for content creators to add illustrations along with optional captions. Renaming and moving standard pages is now discouraged with a warning message that should prevent editors from breaking XWiki. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.2/ Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] [Proposal] Invest in a new translation service
by Vincent Massol 26 Mar '18

26 Mar '18

Hi devs, We started discussing this yesterday on the xwiki chat. Here’s the rationale for changing: * l10n is slow and is preventing users to contribute translations (it’s much harder than it should be) * it’s costing us maintenance that we shouldn’t have to do (it’s not our role to maintain a translation service, even though it was nice to eat our own dog food initially). I see this very similar to when we switched from our GWT-based WYSIWYG editor to CKEditor. * It’ll allow us to benefit from new features/bug fixes the external service develops * Right now it’s taking an hour or more every time we release to integrate the translation changes and this slows us down to increase our release delivery speed * We’re putting the onus on the RM only to validate that the proposed translations are good. So only 1 pair of eyes. * We have no time to fix any translation if they’re not correct. A system where when someone proposes a new translation generates a PR that we apply as they come in would be much better and solve both the review and lateness issues. Of course it’ll mean some plugins/customizations to develop in the service we will use since it’s not going to support some custom formats we have such as our XAR XML format. So we need to pick a tool that allows for this. The proposal: * Start investing in implementing XWiki translation using an external tool. * Start by looking at weblate: https://weblate.org/en/ since ** it seems to offer lots of features we need (automatic PR - see https://docs.weblate.org/en/latest/vcs.html#github, quality checks, plugins). See https://weblate.org/en/features/ ** it’s open source itself and in case the service goes down we can ask XWiki SAS to host it for us (see https://github.com/WeblateOrg/weblate) ** We need to ask them if they can host us, see https://weblate.org/en/hosting/ and the part about "Hosting for free software”. ** We could also ask XWiki SAS if they’d accept paying a “Basic” plan (200 euros/year which is affordable IMO vs hosting it ourselves) ** There’s a REST API so that if we want we can provide a view/status of the translations from xwiki.org: https://docs.weblate.org/en/latest/api.html . We could even imagine using this API to convert from a format to our own format, if need be. * Propose to have a developer work on this in an upcoming roadmap (to be defined but as early as possible since l10n is not in good shape) * Fix l10n as much as we can without spending too much time on it, until we have the new translation service ready to be used Things to look at: * Ability to register custom formats or more generally how to handle our custom format * How do we handle deprecated translations keys * How do we handle global rename/move of keys from one resource file to another * <add more here> WDYT? I’d like to have especially Thomas’s POV since he’s the one who spent the most time on l10n and I’d like to make sure he’s ok with this. Thanks -Vincent

3 3