March 2019 - xwiki-devs@xwiki.org

[xwiki-devs] [VOTE] Use discourse for the "dev" mailing list
by Guillaume Delhumeau 18 Sep '19

18 Sep '19

Hi devs, I think we are now satisfied with our experimentation with the "users" mailing list on discourse. I propose you to move the "dev" ML too. My main point is that it allows advanced formatting (which is good when you have complex proposals), meanwhile the formatting is lost with our archiving tool like markmail (it's plain text). Here is my +1. Thanks, -- Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

3 5

[xwiki-devs] [Proposal] Cleaning of flickering tests
by Simon Urli 06 Sep '19

06 Sep '19

Hi everyone, I was checking our list of flickering tests in JIRA (https://jira.xwiki.org/issues/?jql=labels%20%3D%20flickering%20AND%20status…) and I noticed that we had somehow old flickering test issue concerning test that I've never seen failing. So I propose we close some of them as inactive: the ones that we don't remember having seen for a while. The ideal would be to have a mechanism to update the issue when the CI fails on a flicker, but it takes time to do properly and it's not a priority. On the contrary I propose to trust our memory: if we're wrong because we have closed a flicker that is still happening, it will allow us to remind that we have this flicker to fix and we can easily reopen the issue. As Thomas mentioned on the chat, we should also update the release plan to include the inactive flickers in the list of issue to check. So for now I propose to close the following list of issues as inactive: * XWIKI-14399: AddRemoveTagsTest#addAndDeleteTagFromTagPage is flickering (https://jira.xwiki.org/browse/XWIKI-14399) * XWIKI-14396: AnnotationsTest#addAndDeleteAnnotations is flickering (https://jira.xwiki.org/browse/XWIKI-14396) * XWIKI-14394: SectionTest.testSectionEditInWikiEditorWhenSyntax2x (xwiki-enterprise-test-ui) is flaky (https://jira.xwiki.org/browse/XWIKI-14394) * XWIKI-14386: appwithinminutes.AppsLiveTableTest.testEditApplication is possibly flaky (https://jira.xwiki.org/browse/XWIKI-14386) * XWIKI-14835: DeletePageTest#deletePageIsImpossibleWhenNoDeleteRights is flickering (https://jira.xwiki.org/browse/XWIKI-14835) * XWIKI-14860: LoginTest#testDataIsPreservedAfterLogin is flickering (https://jira.xwiki.org/browse/XWIKI-14860) And I propose in general to close the flickers we don't remember having seen after a cycle as inactive. WDYT? Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

3 20

[xwiki-devs] [Proposal] Update database support strategy
by Vincent Massol 05 Jun '19

05 Jun '19

Hi devs, We currently have https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy However, it doesn’t say explicitly which versions we officially support: * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 * For MySQL it says 5.x but doesn’t specify which specific version(s) * Same for other DBs We cannot really support every versions since supporting means testing too. So what I propose: Question 1: definition * We say we support the latest stable version of the databases for a given version cycle ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today (see https://hub.docker.com/_/mysql/) ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of today (see https://hub.docker.com/_/postgres/) ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of today (see https://www.oracle.com/technetwork/database/enterprise-edition/downloads/in…) Question 2: review what we support * For MySQL I think we could also start supporting MySQL 8.x (ie the latest version of that cycle). We have an issue open for it currently: https://jira.xwiki.org/browse/XWIKI-15215 * For PostgreSQL we could also start supporting versions 11.x (ie the latest version of that cycle) * For Oracle, we could also start supporting versions 12.x (ie the latest version of that cycle) Question 3: decide if we drop some support * Is there any cycle that we should support for? Right now I think that MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know for Oracle. * Any idea? So WDYT about the 3 questions? Thanks -Vincent

7 32

[xwiki-devs] [Proposal] Do not write pure-developer release notes
by Vincent Massol 31 May '19

31 May '19

Hi devs, Context ======= It’s been since we’ve deviated from the original purpose of the Release Notes by also adding developer-oriented release notes. The goal of the Release Notes was to **highlight** important novelties for our **users**, because looking at the JIRA list is too technical (otherwise we could simply use the Release feature of JIRA! :)). So you may ask why we do have a “Developer” Category in the RN app. These were not for pure developers but for XWiki users who are more advanced and can write scripts in wiki pages. And when it’s the case we **must** add examples, otherwise, it’s completely useless. For example this morning I saw this RN added: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/11.0/Change004/ This is typically something that has very little value to me: * It’s for pure developers (java devs) * It’s not understandable by anyone except the person who coded it or participated to the dev mailing list discussion about it * It doesn’t say more than what’s in the JIRA issue so what’s the point? * There are no examples at all in it! * Real developers can simply look at the reference documentation or can read the JIRAs. We always link the JIRA issues in the RN anyway (it was for this reason that we’re listing them). * It takes time to write RN items and thus it needs to have high value Proposal ======== * Go back to the original idea and only list developer RN items when they are for scripting users and not APIs. For example, document some new script service or some additions to existing script services. Of course Groovy would allow you to call any API so being able to use it from Groovy is not a good criteria. I’d say that the criteria should be whether the Release Note Change is useful for Velocity users. * Rename “Developers” into “Scripters” or or “Advanced Users” (any better name?) * Always put an example when writing a “developer” change and take the time to explain properly what it’s about. WDYT? Thanks -Vincent

6 14

[xwiki-devs] OpenCollective for XWiki Community
by Ecaterina Moraru (Valica) 23 May '19

23 May '19

Hi devs, This is a proposal for the content we would have if we were to create an OpenCollective account for XWiki. Take a look at https://design.xwiki.org/xwiki/bin/view/Proposal/XWikiOpenCollective The issues we need to solve / validate are: A. Decide on the URL name (xwiki is already taken by XWiki SAS) B. See if XWiki SAS can act like our Fiscal host C. Validate the tiers and content https://design.xwiki.org/xwiki/bin/view/Proposal/XWikiOpenCollective#HTiers (we might need more details on how the "Bug Fixer" works in case we agree to it) Let me know what you think, Caty

2 14

[xwiki-devs] Location for extensions ideas
by Thomas Mortagne 23 May '19

23 May '19

Hi xwikiers, I'm never sure where to put ideas of extensions I have so I often forget them or details I had tough about or gathered back then. I don't think http://design.xwiki.org is the right place until you really start designing the extension. Also it's too generic for this need and not a very good entry point for searching something IMO, more something to link to from somewhere else. I would prefer something really dedicated to this "that would be a nice thingy but not sure about the details yet" state. Would be a good source for hackathons and GSOC or for contributors who are searching for something interesting to work on. I was thinking about the following alternatives: * a new dedicated project on https://jira.xwiki.org * reuse https://jira.xwiki.org/projects/XCONTRIB after some cleanup (close everything left in it basically) but not super clean (it's just that it's a good name) * some new application on http://www.xwiki.org WDYT ? Right now my preference goes to a clean new jira project (just need to think about a good project id) where you put description and close it when the extension work really start on a dedicated location. Less work and should do the job well. -- Thomas Mortagne

4 7

[xwiki-devs] [proposal] Process to handle Pull Requests
by Ludovic Dubost 10 May '19

10 May '19

Hi devs, I don't think there is currently a process that is in place to handle pull requests and I have the feeling that the way there are handled today is a bit random. There are usually comments sent out on each pull request but sometimes it seems that some pull requests are going in sleep mode and it's not clear who is in charge. I would like to suggest that a process is put in place where it's clear who is responsible for a pull request and a status is given to the contributors that propose that pull request. Something like: Assigned developer: XXXX Status: New -> new pull request, not yet assigned Assigned -> assigned to a developer, he is in charge of reviewing the pull request and ask for modifications or accept it. The developer can auto assign it to himself. If nobody does, we need to decide how they will be taken into account. ModificationsRequired -> for now rejected with comments. Contributor needs to apply comments and then change back to Assigned for further evaluation VoteRequired -> there are no more comments, but a vote is required as the changes to XWiki core are important WaitingFinalAuthorization -> optional step for complex patches where a additional authorization would be required (need to define who would be the persons that give the authorization) WaitingApplication -> there are no more comments and no changes or vote required. The pull request can be applied and is waiting for a developer to apply it Abandoned -> contributors is abandoning the pull request (cannot do the changes, no more time, etc..) Rejected -> pull request is rejected (quality not enough, etc..) Applied -> pull request is applied What do you think ? Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

7 12

[xwiki-devs] [Brainstorming] Failing build when deprecated APIs are used in scripts?
by Vincent Massol 03 Apr '19

03 Apr '19

Hi devs, I'd like to discuss about introducing a checker in the tests to fail the test if there's a warning message about a deprecated APIs being used in scripts. For example: ``` 23:59:28.308 [main] INFO org.xwiki.test.ui.TestDebugger - GroupIT-addUserAndSubgroupToGroup started 23:59:32.593 [Exec Stream Pumper] ERROR o.x.t.i.XWikiLogOutputStream - 2019-03-28 23:59:32,593 [http://localhost:8080/xwiki/bin/view/XWiki/XWikiPreferences?xpage=getgroups…] WARN o.x.v.i.DefaultVelocityEngine - Deprecated usage of method [com.xpn.xwiki.plugin.rightsmanager.RightsManagerPluginApi.countAllMembersNamesForGroup] in 21:/templates/getgroups.vm@62,37 23:59:35.824 [Exec Stream Pumper] ERROR o.x.t.i.XWikiLogOutputStream - 2019-03-28 23:59:35,824 [http://localhost:8080/xwiki/bin/view/XWiki/XWikiPreferences?xpage=getgroups…] WARN o.x.v.i.DefaultVelocityEngine - Deprecated usage of method [com.xpn.xwiki.plugin.rightsmanager.RightsManagerPluginApi.countAllMembersNamesForGroup] in 18:/templates/getgroups.vm@62,37 23:59:41.349 [Exec Stream Pumper] ERROR o.x.t.i.XWikiLogOutputStream - 2019-03-28 23:59:41,348 [http://localhost:8080/xwiki/bin/view/XWiki/XWikiPreferences?xpage=getgroups…] WARN o.x.v.i.DefaultVelocityEngine - Deprecated usage of method [com.xpn.xwiki.plugin.rightsmanager.RightsManagerPluginApi.countAllMembersNamesForGroup] in 21:/templates/getgroups.vm@62,37 23:59:58.503 [main] INFO org.xwiki.test.ui.TestDebugger - GroupIT-addUserAndSubgroupToGroup passed ``` Rationale: * This adds warnings in the xwiki logs when users navigate to those pages which isn’t nice. * It also helps reducing the number of deprecated methods we use (I have the feeling this is not reducing) and helps us move towards being able to move the deprecated code to legacy. WDYT? Thanks -Vincent

5 8

[xwiki-devs] [Proposal] Improve our Test Coverage strategy (TAKE 3)
by Vincent Massol 03 Apr '19

03 Apr '19

Hi devs, I remember that we talked about this new global test coverage strategy but I don’t recall where and I couldn’t find an email about it. So I’m reposting the strategy that I’ve just finished implementing. * Every day the Clover job runs: https://ci.xwiki.org/view/Tools/job/Clover/ * It generates a global coverage report and compares it automatically with the first report generated for the current version * If the global coverage is reduced, then: ** an email is sent to notifications(a)xwiki.org containing the report ** the job is marked as FAILING ** A failing badge is added to the job history ** A red large text is added to the job page and a link to the report is sent * Developers MUST fix the global coverage before we can release a version, so the it means the global coverage must not be reduced during a version. * The RM should check the CI (already part of his chores) and the “Recommended Failing” view on ci.xwiki.org must not have errors or failures (so that includes pitest job and clover job). Any comments? Does that seem ok to you? If you confirm it’s ok, I’ll document it on https://dev.xwiki.org/xwiki/bin/view/Community/Testing/TestCoverage/ Note: A few minutes ago an email has been sent since the global coverage has been reduced compared to yesterday. See http://maven.xwiki.org/site/clover/20190321/XWikiReport-20190320-0128-20190… So we need to fix it now. Thanks -Vincent

3 2

[xwiki-devs] [ANN] XWiki 10.11.4 released
by Ecaterina Moraru (Valica) 28 Mar '19

28 Mar '19

The XWiki development team is proud to announce the availability of XWiki 10.11.4. This is a bugfix release that covers important issues that we have discovered since 10.11.3 has been released. 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.11.4 Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] [ANN] XWiki 11.2 released
by Vincent Massol 25 Mar '19

25 Mar '19

The XWiki development team is proud to announce the availability of XWiki 11.2. This release brings a warning to the users when they are editing a page and other users are saving the same content. The Object editor has a new way of presenting XClasses meant to increase the user experience, while the top level application pages are not displayed anymore in the Navigation Panel. In addition the performance of the Notifications feature has been improved. 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/11.2 Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] [WCAG] Reference validator
by Ecaterina Moraru (Valica) 20 Mar '19

20 Mar '19

Hi devs, I've started to analyze the 971 tests failing on webstandards related to the WCAG validation. I plan to create issues in order for us to fix the errors. The problem I have is that we were validating against the Dutch Guidelines validation tool (previously http://www.webrichtlijnen.nl/english/testing) but this tool has been discontinued by the Dutch Ministry in July 2017, see https://www.digitoegankelijk.nl/onderwerpen/testen/nieuws/2017/04/25/gewoon… The difference between the W3C WCAG rules (https://www.w3.org/TR/WCAG/) and the Dutch Guidelines was that the latest were more strict. Also WCAG specification advanced to version 2.1 in Jun 2018. Since I don't have much experience in the way we've implemented the validator, I'm asking if anyone has any idea of another validator we could replace this one with (in case we want this). Else, I will try to investigate and find a replacement for a new reference validator. Currently the plan is to fix our code to match the current definitions and in cases that are not covered by W3C WCAG and where we want to add "exceptions" I test also online on: * https://ckeditor.com/ckeditor-4/accessibility-checker/ and * http://wave.webaim.org/ Let me know if you have any objections to the 2 tools mentioned above. I've started the investigation at: https://design.xwiki.org/xwiki/bin/view/Proposal/WCAG10x we can discuss each error and "exception" on the individual issues. Thanks, Caty

3 4

[xwiki-devs] [ANN] XWiki 11.2 RC1 released
by Alex Cotiugă 19 Mar '19

19 Mar '19

The XWiki development team is proud to announce the availability of 11.2 RC1. This release brings a warning to the users when they are editing a page and other users are saving the same content. The Object editor has a new way of presenting XClasses meant to increase the user experience, while the top level application pages are not displayed anymore in Navigation Panel. 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/11.2RC1/ Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] [Feedback] Installation choices
by Ecaterina Moraru (Valica) 18 Mar '19

18 Mar '19

Hi Devs, I'm curious what you think about this direction for the Download / Install page on xwiki.org: Iteration 1 https://design.xwiki.org/xwiki/bin/download/Install/LDJEasierInstallationFl… Changes: * Download renamed to Install * Form at the beginning to select the version, OS, type and package * Depending on the user selection, there is an option to Download the package, or you just get Installation steps (personalized for each option selected). I've iterated currently just for the ZIP package (for Demo+Mac), but imagine something similar for all the other packages. What do you think? Should I continue in this direction? Thanks, Caty

4 6

[xwiki-devs] WebDAV extension failing build
by Vincent Massol 15 Mar '19

15 Mar '19

Hi Clemens, I don’t know if you’ve noticed but the WebDAV build is failing: https://ci.xwiki.org/view/All%20Failed%20Builds/job/XWiki%20Contrib/job/web… Thanks -Vincent

2 2

[xwiki-devs] asking for help, issues for a team
by Jeremi Kádár 13 Mar '19

13 Mar '19

Dear XWiki developers, I and my friends learn Computer Science at the University Of Szeged. One of our obligatory task in this semester to participate in an open source project. We decide to choose a project so our team wouldn't be randomized and we don't have to risk that we'll be put together with students who too lazy to work. I've found XWiki and seen that this would be an excellent choice since it's well known and has some history behind itself and the project itself is really interesting too. We've read the different guides about how to participate, registrated to jira, github, devmails... Our problem is that we couldn't find an issue / work item with the following criterias: - no one's working on it || not assigned ( - it's beginner friendly, not have to know *everything *from A to B about the project code ) Each of us have to take an issued or if there is 2-3 issue big enough, then on each of the issues 2-3 members of our team would work on. We have to showcase the first milestone next week, until then we should get to known to the project and get issues / task. We would be grateful if you could help us! Thanking you in advance... Sorry for the language mistakes. I'm writing this letter down in Hungarian as well, just in case: Kedves XWiki fejlesztők, Én és a barátaim Programtervező Informatikára járunk a Szegedi Tudományegyetemen. Ebben a félévben az egyik kötelező feladatunk részt venni egy nyílt forráskódú projekt fejlesztésében. Úgy döntöttünk, hogy mi választjuk a projektet, mivel így a csapatunk nem véletlenszerű lesz kiválasztva és nem fogunk olyanokkal összekerülni, akik nem akarnak dolgozni. Rátaláltam az XWiki-re és tökéletes választásnak találtam, mivel ismert, van háttere és maga a projekt is nagyon érdekes. Elolvastuk a különböző leírásokat és regisztráltunk githubra, jirara, fejlesztői e-mailekre. Az a problémánk, hogy nem találtunk issuet / feladatot az alábbi feltételek mellett: - senki sem dolgozik rajta || senkin sincs még rajta ( - kezdőknek is jó, nem kell *mindent* tudni hozzá a projekt forráskódjáról ) Mindannyiunknak kell felvennie egy issuet vagy ha van 2-3 nagyobb issue, akkor mindegyiken a csapatból 2-3 ember is dolgozhatna. Az első mérföldkövet jövő héten kell bemutatnunk, addig meg kell ismernünk a projektet és szereznünk kell feladatot is. Hálásak lennénk, ha tudnátok segíteni! Előre is köszönöm...

2 1

[xwiki-devs] Request for a nexus account
by Paul Libbrecht 12 Mar '19

12 Mar '19

Dear XWiki developers, I would like to perform releases for Apps of the https://github.com/xwikisas/ repositories. My current work is on [application-googleapps](https://github.com/xwikisas/application-googleapps/). To do this, I would need an account on nexus.xwiki.org. Thanks in advance. Paul

2 1

Re: [xwiki-devs] [xwiki-notifications] About the GSOC mentors email address
by Thomas Mortagne 08 Mar '19

08 Mar '19

You should not try to directly send mails to the mentors and instead communicate using general communication channels in which mentors will answer you. The best to to start start by reading https://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Guidelines. On Fri, Mar 8, 2019 at 1:53 AM Weiqiang Cai <caiweiqiang44144(a)gmail.com> wrote: > > Dear mentors， > > Good day. > > Hello there! sorry for disturbance. > > I am a student who is about to apply for GSOC2019. I am very interested in XWIKI, although I have not used it before. But I have spent some time to understand it. > > I am very interested in some projects, and would like to try it. So I want to have a discussion with the project’s mentor. But I find the email address in the mentor profile is incomplete. > > Would you give me some suggestions about how to get complete address? > > Thanks & Best Regards, > > CaiWeiqiang -- Thomas Mortagne

1 0

[xwiki-devs] Status on Docker + CI + Clover - Outstanding tasks
by Vincent Massol 03 Mar '19

03 Mar '19

Hi devs, I wanted to keep up to date on the list of stuff that we still need to do in the domain of Docker, CI & Clover, specifically on the domains I’ve been working on. All the items below are items I need to work on (but any help is welcome of course). 1) Clover pipeline job to modify to add docker-based functional tests: right now the global TPC is going to decrease because of MenuIT and MailIT. This needs to be fixed ASAP before we convert too many tests. 2) Also fix Clover pipeline job in general which hasn’t passed since the 22nd of October 3) Execute Docker-based tests in main pipeline job for the default config as otherwise we might have the platform job succeeding but it’ll miss several functional tests! Option 1: execute Browser outside of docker as option, Option 2: add more docker-based agents. For the moment, we might be able to run the docker tests on agent4. 4) Screenshot attachment on UI test failures to fix in pipeline job 5) Flicker recognition on tests to fix in pipeline job 6) Fix the ClosedChannelExcption/InterruptedException in our CI 7) Research running Jenkins agents in docker images and make our Docker test work (docker on docker). Once this works, set up 2 or 2 agents on a4. And then move all other agents to this. 8) Still need to apply the Clover strategy we agreed on (global TPC needs to not go down during releases). 9) Find strategy to move Docker image creation in platform build Let me know if you have questions. Thanks -Vincent PS: I didn’t list fixing tests (such and flicker fixing or WCAG test fixing) since this not infra and I wanted to limit this list to infra.

1 7

[xwiki-devs] Introduction Newbie and GSoC interested candidate
by mua rachmann 03 Mar '19

03 Mar '19

Hello everyone, I am Mua Laurent a final year student at the University of Buea Cameroon. I joined open source last year and i am completely in love with it my way of giving back to the community. I will love to contribute to this organization Sir/Madam cause i see it as a means to enhance my skills and get experience in order to help others. I have a very good knowledge of C, python , CSS3, HTML5 , JavaScript , PHP and a little java and golang. While here i would love to learn more and give in my best. Also i am interested in participating in this years GSoC with you guys. I am very much interested in the project WebHooks for XWiki. I would love to work on this very much as i love APIs and have had to implement them in the past using php , laravel framework. I am very curious on how to get started can anyone point me. Also i forked the xwiki/xwiki-platform already. I am a newbie around please will require a little assistance on how to get started thatnks

2 1