xwiki-devs August 2019

xwiki-devs@xwiki.org

11 participants
17 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] [XWiki Day] BFD#222

by Simon Urli

Hello devs, This Thursday is BFD#222: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingday Our current status is: * -19 bugs over 120 days (4 months), i.e. we need to close 19 bugs to have created bugs == closed bugs * -85 bugs over 365 days (1 year) * -147 bugs over 500 days (between 1 and 2 years) * -374 bugs over 1600 days (4.3 years) See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#222 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14439 Good luck at fixing bugs, Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

4 years, 11 months

[xwiki-devs] [ANN] XWiki 11.7 released

by Marius Dumitru Florea

The XWiki development team is proud to announce the availability of XWiki 11.7. This release brings a new date picker and various merge improvements. Developers will also be able to reuse the standard color picker and the merge API give more details about the conflicts. 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.7 Thanks for your support -The XWiki dev team

4 years, 11 months

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

by Oana-Lavinia Florean

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

4 years, 11 months

Re: [xwiki-devs] Map Application - GSoC 19

by Fawad Ali

Hi all, I wanted to ask if it was possible to have a custom class sheet and the editing options of a normal page available at the same time? As it stands, for the PointSheet, we will have to skip the WYSIWYG editor for editing the page. However, one thing could be that instead of taking the page's content for the Point's popup, we could introduce a new class property popupContent and have the popup content inside that. This way, we can use WYSIWYG as well. Another approach could be to keep the current Point Editor and use that create points without any sheet. The same questions apply for the Shape Editor as well. What do you think? Best, Fawad On Fri, Aug 2, 2019 at 2:53 PM Fawad Ali <m.fawaadali98(a)gmail.com> wrote: > Stéphane, > > Yes, sure. > In the meantime, I will be working on the PointSheet. > However, I do want to ask if the Shape Editor is necessary at this point > if we are going with GeoJSON. We can refer the user to http://geojson.io > for creating the features. What do you think? > > Best, > Fawad > > > On Fri, Aug 2, 2019 at 12:04 PM Stéphane Laurière <slauriere(a)xwiki.com> > wrote: > >> OK Fawad, >> >> Meantime since Caty is off, and since today might actually be a bit early >> for me I'm afraid, I'd propose we have the call on Monday 15:00 UTC on >> Monday if that's ok with you . >> >> Cheers >> >> Stéphane >> >> >> Fawad Ali: >> > Stéphane, Ecaterina, >> > >> > About the call, I think we should have it so that we all converge on >> the things to be done. >> > However, tomorrow (Friday), I have a call with the Pakistan's GSoC >> community at about 5 PM UTC. If the call will be finished in two hours I am >> fine with it or we could reschedule it to 2:30 PM UTC or else Monday. >> > >> > Best, >> >> >> -- >> Stéphane Laurière >> XWiki – https://xwiki.com >> >>

4 years, 11 months

[xwiki-devs] [Proposal] Remove XWiki.User enable property and introduce email_check property

by Simon Urli

Hi everyone, I recently (in XWiki 11.6RC1) introduced a new property "enabled" in XWiki.User as part of https://jira.xwiki.org/browse/XWIKI-12654 to distinguish between inactive users (who have not confirm their registration with the token sent by email), and disabled users (who are deactivated by an admin, or by a security mechanism). Now as Marius noticed those two properties are quite redundant, especially when you want to know which users are really active. So it introduces unnecessary complexity and we might even need to change existing extension to check enabled users (cf the last comments on XWIKI-12564). So before doing those changes, I propose to fix immediately the issue by removing that newly introduced property and by introducing a new property only for assessing that users' email are checked. Then we will only have to check "active" property to check if a user is active or not, and we could rely on it to set them enabled or disabled in the admin. The email_check property would be used only for the check email mechanism, so it will avoid any confusion in the semantic. WDYT? Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

4 years, 11 months

[xwiki-devs] Application pages layout best practices

by Stéphane Laurière

Hi everyone, I'm following up on a thread started in 2015 about the best practices regarding app pages organization: - https://xwiki.markmail.org/message/657vcm6ylkz4yytc - https://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPr… In this thread, the idea of introducing a dedicated common root area for all application technical pages was suggested by Denis: https://xwiki.markmail.org/message/kk5l3dwjmpfelkzp I'm wondering why this idea was not pushed further (it's not strictly incompatible with the current best practices, but most of the recent applications have their top level area, except a few like Notifications or ChartJS). Comparing with how other platforms do is inspirational (Microsoft Windows "Program Files" was mentioned in the thread). On Debian, the Maven package is installed in /usr/share/maven/ while files used and produced by Maven can be located anywhere. Along the same line, I would see as a user and developer experience improvement if we had the following structure: 1) Code: XWiki |- MyApp |- MyAppClass |- MyAppSheet |- ... 2) Data: the pages created by MyApp could then typically be located by default in a MyApp space at the root of the wiki, the user could however choose which default space to use, or leave it empty (then the space from where the user fires the create action could be used, for instance, or any scriptable rule). Another issue I see with the current practice (raised by Clément A. orally) is that some application names may conflict with names the user would like to use for content that is not strictly related to the app. Not necessarily a big deal with one thousand of applications, but might become one with more, wouldn't it? I understand that the layout proposed above would raise technical issues (XWiki space permissions for instance, mentionned in the 2015 thread, and others), however what's your view on it from a design perspective? (sorry if I overlooked strong arguments already expressed against it) Cheers Stéphane

4 years, 11 months

[xwiki-devs] [ANN] XWiki 11.7 RC1 released

by Thomas Mortagne

The XWiki development team is proud to announce the availability of XWiki 11.7 RC1. This release brings a new date picker and various merge improvements. Developers will also be able to reuse the standard color picker and the merge API give more details about the conflicts. 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.7RC1 Thanks for your support -The XWiki dev team

4 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2019