xwiki-devs May 2019

xwiki-devs@xwiki.org

17 participants
29 discussions

[xwiki-devs] [VOTE] Use discourse for the "dev" mailing list

by Guillaume Delhumeau

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

4 years, 10 months

[xwiki-devs] [Proposal] Cleaning of flickering tests

by Simon Urli

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

4 years, 10 months

[xwiki-devs] Map Application - GSoC 19

by Fawad Ali

Hi everyone, Hope all of you are doing great. About Me I am Fawad Ali, selected as a student for Google Summer of Code. Currently enrolled in the 6th semester at University of Engineering and Technology, Taxila. I am a resident of Pakistan currently living in the city of Rawalpindi. It is a great honor to have been selected and have a chance to work with XWiki. :) *Profiles* GitHub - https://github.com/9inpachi LinkedIn - https://www.linkedin.com/in/fawadaliq/ Riot - @ginpachi:matrix.org I will be presenting my project "Map Application" to all of you. Following are the relevant details. Map Application *Mentors: *Stéphane Laurière, Ecaterina Moraru *Technologies:* JavaScript, Velocity, Java, Leaflet, other if required Overview This project is about the development of interactive maps in XWiki. Creation of an application within XWiki that will allow users to generate interactive maps which support collaboration and are easy to create so that locations can be shared, and areas can be associated with structured data. This application will open several possibilities that can be utilized within XWiki and broaden the overall scope by allowing map rich wikis where locations and areas can be presented in a way that will increase the understandability of data. It will also allow for the sharing of custom map related data which would be very helpful since users and admins will be able to present locations in an information rich map environment which will be interactive. Features > *Markers and popups* - Place markers anywhere on the map and associate popups with them. > *Path between two points* - A path will be generated by the application linking two points of interest. > *Location search* - Search any location on the map. > *Filtered list maps* - Allow the user to search for a specific kind of place (e.g. restaurants) and get a list of locations to choose from. Through the content available and binded to a location, the user will be able to learn some aspects of the location. > *Custom shapes* - Custom shapes can be used to highlight a specific area for representation. The content associated with these shapes can give useful information about the area. > *Indoor maps* - Such maps will be able to describe the internal structure or fair plan of a building or structure. They can be used to guide users in a big building and locate point of interests. > *Maps on mobile* - Special design arrangements will be made for easily viewing of maps and availing all the features of the application on mobile devices. > *Custom map backgrounds* - Custom backgrounds will make the environment of interactive maps much suitable for a specific purpose If you have any features in mind that will make the Map Application better please feel free to reply to this mail. This is all for the summary of the project, if you want to have a more deeper insight, please check out the full proposal. *Project Proposal: * https://drive.google.com/open?id=14qXC7Oy2bPUASfVtSTIsNG1sPcfm5Ikr Thanks for reading through the mail. I will be looking forward to your guidance through this summer and your contributions to the project. If you have any questions or suggestions, please feel free to reply to this mail. Au revoir. :) Best, Fawad Ali

4 years, 10 months

[xwiki-devs] [VOTE] Officially support for Tomcat 9

by Thomas Mortagne

Hi devs, tomcat9 package is now available in Debian repositories so I would like to start providing xwiki-tomcat9-* Debian packages of XWiki. Nothing complex so far but it if we provide an official tomcat 9 oriented package it would also make more sense to add Tomcat 9 in https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/ServletConta… (only Tomcat 8 right now). Another argument is that it's the current recommended stable version from Tomcat point of view so people will use it more and more. WDYT ? Here is my +1 -- Thomas Mortagne

4 years, 12 months

[xwiki-devs] Helm Chart Xwiki - GSOC'19

by Ashish Sharma

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

5 years

[xwiki-devs] [Proposal] Update database support strategy

by Vincent Massol

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

5 years, 1 month

[xwiki-devs] [Proposal] Do not write pure-developer release notes

by Vincent Massol

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

5 years, 1 month

[xwiki-devs] [Proposal] Merge on save

by Simon Urli

Hi everyone, I'm working on the merge on save for the roadmap of 11.5 and I need some decision to be taken. The main idea of the merge on save, is to try to merge users work in case of save conflict. Knowing that the merge might led to merge conflict in case of edits on the same places. Those merge conflict can be tackled automatically, but a priority will be then given to one version over another. I first propose to add an option in user profile, so users would have the possibility to choose between: 1. Always merge automatically the work, even in case of merge conflict 2. Always merge automatically, but ask what to do in case of merge conflict 3. Always ask what to do in case of save conflict Now the question is: what should be the default option? Option 1 looks like a good fit for decreasing the number of clicks to do, but I'm a bit afraid that in case of conflict they would have the same feeling as before the warning conflict window: i.e. to loose some part of their work. WDYT? Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

5 years, 1 month

[xwiki-devs] [Brainstorming] Controlling transformations

by Vincent Massol

Hi devs, I’d like to discuss about how to control transformations and when they are executed. Right now we have an all-or-nothing strategy (either the transformation is defined in the config property or it’s not). We have some needs to be able to turn on/turn off some transformations on a page level basis. Here’s the idea that I put on https://jira.xwiki.org/browse/XWIKI-15100: * Add a new xproperty to Rendering.RenderingConfigClass * Modify java code: XWikiRenderingConfiguration, ExtendedRenderingConfiguration, DefaultExtendedRenderingConfiguration, RenderingConfigClassDocumentConfigurationSource * For the wiki level, get the config in Rendering.RenderingConfig * For the page level, get the config from an xobject of type Rendering.RenderingConfigClass * Make RenderingConfiguration.getTransformationNames() search in the current page, parent pages (spaces), current wiki, and fallback to xwiki.properties Note that, as Thomas pointed out in comment of https://jira.xwiki.org/browse/XWIKI-15100 the last point is the hard one. We could imagine having a transformation cache that would be loaded at startup and updated whenever a XWiki.RenderingConfigClass xobject is modified in the wiki. Very similar to wiki components. Note: We could also implement https://jira.xwiki.org/browse/XWIKI-13167 at the same time, with the query string in the URL overriding the transformations. WDYT? Any idea of the cost of adding such a feature in term of days? Does 7 days sounds good to you? (inluding testing and doc). Thanks -Vincent

5 years, 1 month

[xwiki-devs] [XWiki Day] BFD#211

by Oana-Lavinia Florean

Hello devs, This Thursday is BFD#211: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingday Our current status is: * -18 bugs over 120 days (4 months), i.e. we need to close 18 bugs to have created bugs == closed bugs * -97 bugs over 365 days (1 year) * -156 bugs over 500 days (between 1 and 2 years) * -357 bugs over 1600 days (4.3 years) See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#211 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14418 Good luck at fixing bugs, Lavinia

5 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs May 2019