The XWiki development team is proud to announce the availability of XWiki
11.3RC1.
This release comes with a lot of bug fixes and a couple of small
improvements for things like the live table date filter, the Database List
field from AppWithinMinutes or the Delete User modal. There's also a new
Tomcat 9 based Debian package that you might want to try.
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.3RC1
Thanks for your support
-The XWiki dev team
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
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
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
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
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
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
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...
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
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.
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
Hi devs,
I believe one very important action to improve active installs is to improve installation of XWiki.
I’ve started listing ideas at https://design.xwiki.org/xwiki/bin/view/Proposal/InstallationImprovementIde…
Let me know what you think.
I think I’d like to propose to work on this aspect after 11.2 is out.
WDYT?
Thanks
-Vincent
Hi everyone,
we currently have some issues when performing refactoring operations on
pages that are linked from another wiki page. See:
https://jira.xwiki.org/browse/XWIKI-8346
The current implementation of the links is to keep the local name of the
current document and to create a reference containing the name of the
wiki for the target document, only if it's a document from another wiki.
So basically if I have a wiki:A pointing to subwiki:B, I will get a link
stored in DB of "wiki", containing:
- fullName: A
- link: subwiki:B
This forces us to currently iterate over all wikis, when we refactor a
page to edit all the links on the farm. That's why we currently have an
option which is disabled by default: i.e. we don't update backlinks on a
farm by default.
In order to allow such operation with less performance issues, I propose
to add a new table dedicated to store the backlinks: basically this
table would store the reversed information as Links, in the target DB.
If I take back my example, the table backlinks of "wiki" would be empty,
and I get in the table backlinks of "subwiki", the following information:
- fullName: B
- backlink: wiki:A
Then we could load all backlinks of a document just by looking in one
table.
The impact on performance would be the necessity to update links in two
tables when performing a save, but we can mitigate this by first loading
the links so we only update what needs to be (currently we delete and
recreate all links, each time...).
IMO it would really ease the understanding of links and backlinks, solve
the issues on farm and help us to maintain this code. + it doesn't break
any legacy since we keep the existing Link table.
WDYT?
Simon
--
Simon Urli
Software Engineer at XWiki SAS
simon.urli(a)xwiki.com
More about us at http://www.xwiki.com
Hi devs,
On a standard XS, if you show hidden document you see some entries that you shouldn’t see and that should be hidden. See screenshot.
Another problem is that clicking on the Dashboard, Crypto, Macros, Rendering links lead to non-existing pages.
I’m this proposing to:
1) Introduce a xwiki-platform-crypto-ui modules with a single Crypto.Webhome page and some one liner explaining what this space is about.
2) Introduce a xwiki-platform-rendering-wikimacro-ui module with a single Macros.WebHome page and some one liner explaining what this space is about. It makes sense to have it under xwiki-platform-rendering-wikimacro since it’s about providing a location for wiki macros.
3) Add a Rendering.WebHome page inside xwiki-platform-rendering-ui to explain what this space is about. The module is there and it’s just missing this page. BTW an alternative is to modify the Navigation panel algorithm to exclude spaces not having a top level WebHome page too. @Marius: any reason we’re not doing this already?
By default the Navigation panel hides top level pages that are not meant to be modified so this will remove Crypto, Macros & Rendering.
4) For Dashboard it’s a bit more complex. Ideally we would refactor Dashboard.WebHome to include a new Dashboard.WikiDashboard page that would contain the current content of Dashboard.WebHome. Thus the home page would appear as not modifiable and not appear in the Navigation panel. However, since users can have modified Dashboard.WebHome, this would cause an upgrade merge conflict. Thus, instead, I propose to do what we do for the Sandbox page and instead add Dashboard to the Exclude list of the Navigation panel.
WDYT?
Note: I’m going to do 4) right now since it’s a no-brainer.
Longer term
=========
This is *not* part of the proposal but we need to start a thread again about this and start doing something about it: Right now we have apps/extensions creating pages under the top level root. I don’t think this is good at all and we should reserve the top level root for user content. It would be much better to have a place under “XWiki”, such as “XWiki.Extensions.<extension name>.<sub spaces>.<pages>” where each extension could put its content.
We already started discussing this. The past thread(s) needs to be unearthed and the discussion resumed.
Thanks
-Vincent
The XWiki development team is proud to announce the availability of XWiki
11.1.
This release adds support for renaming apps created with App Within Minutes
and brings improvements to the WYSIWYG editor: inline editing of the Box
Macro title and macro category count displayed by the Macro Selector.
Advanced users can now copy the page reference from the Information tab at
the bottom of each page.
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.1/
Thanks for your support
-The XWiki dev team