The XWiki development team is proud to announce the availability of
XWiki 11.6RC1.
This release brings new security features related to user authentication
and management, a new way to see document changes closer to the WYSIWYG
edition, and a new macro to define part of a document that should be
asynchronously loaded for better performance.
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.6RC1
Thanks for your support
-The XWiki dev team
Hi everyone,
Thanks for having me here
About Me
I am Ashish Sharma, selected as a student for Google Summer of Code. I am
final year student enrolled in Guru Gobind Singh Indraprastha University,
Delhi. I am a resident of India.
Profiles
GitHub - https://github.com/ashish932/xwiki-helm-chart/
LinkedIn - https://www.linkedin.com/in/ashish932/
Riot - @ashish932:matrix.org
I will be presenting my project "Helm Chart for XWiki" to all of you.
Following
are the relevant details.
Helm Chart for XWiki
Mentors: Shubham Jain, Neha Gupta
Technologies: Kubernetes, Docker, other if required
Overview
The proposed project is a helm chart that would deploy xwiki as highly
available and reliable. It should be configurable with different
databases(either a standalone database or a clustered one) that are
configurable with xwiki. It would give the option to either configure solr
externally (standalone or clustered) or managed within the container. It
should deploy the app on a shared file system like a rook. It should
support Istio virtual services, istio matrix, and istio distributed tracing
and should be a secured system with RBAC and security credential rotation.
The chart should be easily deployed on GKE and amazon EKS.
Features
-> Support for different Databases
-> Choice between using an external database, a single node DB or a
multi-cluster DB setup
-> Support for shared file system
-> Support for istio and it's services
-> RBAC, SSL and other security methods
If you have any features in mind that should be added please feel free to
reply to this mail.
Some Design Questions?
-> Which Databases should be supported?
-> As we have to detach solr out of the docker container(run it in an
independent container) would be there a requirement for a code change, and
we should approach it?
-> Apart from solr is there any other stateful service that could or should
be detached from the docker container?
Here is my current repository which deploys XWiki for MySQL database using
official XWiki docker container:-
https://github.com/ashish932/xwiki-helm-chart/
Thank You
Ashish Sharma
Hi everyone,
Hope you are doing well.
I would like to request an account on http://nexus.xwiki.org for the
release of Interactive Maps Application
(org.xwiki.contrib:application-interactive-maps) version 1.0-SNAPSHOT.
*Requested username:* ginpachi
Best,
Fawad
Hi everyone,
this is a proposal to add a new wikimacro script binding for the next
release, that I also plan to backport on 11.3.x and 10.11.x branches.
We had recently a bug report (https://jira.xwiki.org/browse/XWIKI-16520)
about the WikiMacro parameter: types were introduce in 10.10 (with
https://jira.xwiki.org/browse/XWIKI-13282) but we in fact never
converted them, making their type pretty useless.
We provided a first fix to it actually broke at least one existing
macro, AttachmentSelector which was still expecting String parameter
values instead of the types used in some of those parameters.
So even if the parameters were supposed to be typed since XWiki 10.10,
in practice they never have been. We might as well consider returning a
typed values as a regression since it might break some of the existing
macros.
That's why I propose to implement right now a new wikimacro binding, to
be able to get both typed parameter values and string parameter values.
The old binding would then still be available by using $xcontext.macro
but we would deprecate its usage.
I propose that all the existing $xcontext.macro information to be
available by using $macro, and to be able to use:
* $macro.parameters.foo to get a typed parameter value
* $macro.parametersAsString.foo to get the string value parameter
Could you tell me if you agree with all those changes?
Thanks,
Simon
--
Simon Urli
Software Engineer at XWiki SAS
simon.urli(a)xwiki.com
More about us at http://www.xwiki.com
Hi guys,
We have a decision to take re the docker image.
Until now we were supporting the arm64v8 architecture. However due to some changes, it's now ony supported with java11. So we have 2 solutions for the tomcat base image to use:
1) stay on java8 and move to the adoptopenjdk base image (so that we get java patches) BUT drop support for arm64v8 architectures
2) move to java11 and move to the adoptopenjdk base image (so that we get java patches) and keep support for arm64v8 archietectures
My POV is that we should do 1) since XWiki is supposed to run well on Java11 (it may even be faster on it?) and we want it to work on it anyway. We also test it with our docker tests every week
Side note: we could also decide to move to java11 everywhere on our CI agents and keep some tests weekly on java8 (ie invert the current situation)
WDYT?
Thanks
-Vincent
