xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

Re: [xwiki-devs] [xwiki-notifications] About the GSOC mentors email address

by Thomas Mortagne

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

6 years, 3 months

[xwiki-devs] Status on Docker + CI + Clover - Outstanding tasks

by Vincent Massol

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.

6 years, 4 months

[xwiki-devs] Introduction Newbie and GSoC interested candidate

by mua rachmann

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

6 years, 4 months

[xwiki-devs] [ Brainstorming] Improving XWiki installation - Increase Active Installs

by Vincent Massol

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

6 years, 4 months

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

by Oana-Lavinia Florean

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

6 years, 4 months

[xwiki-devs] [ANN] XWiki 10.11.3 released

by Simon Urli

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

6 years, 4 months

[xwiki-devs] [UX][Proposal] Notifications UI 11.x

by Ecaterina Moraru (Valica)

Hi devs, http://jira.xwiki.org/browse/XWIKI-16119 wants to make the Notifications / Activity Stream look nicer. I've made a proposal at https://design.xwiki.org/xwiki/bin/view/Proposal/Notifications11x/ Let me know what you think. Thanks, Caty

6 years, 4 months

[xwiki-devs] [Proposal] Introduce a new table BackLinks for solving issues on wiki farms

by Simon Urli

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

6 years, 4 months

[xwiki-devs] [Proposal] Changes to remove Dashboard, Crypto, Macros, Rendering entries in the Navigation Panels

by Vincent Massol

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

6 years, 4 months

[xwiki-devs] [ANN] XWiki 11.1 released

by Guillaume Delhumeau

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

6 years, 4 months

← Newer
1
...
7
8
9
10
11
12
13
...
940
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs