xwiki-devs February 2016

xwiki-devs@xwiki.org

21 participants
47 discussions

[xwiki-devs] [Proposal] Restart BFD starting this Thursday

by vincent＠massol.net

Hi devs, We’re loosing once more on the bug count and we need to get back to doing regular BFDs every Thursday. Here’s the current status on (bugs closed - bugs created): * Overall: -526 bugs * Last 1600 days: -24 bugs * Last 365 days: -117 bugs So I propose to restart the BFD at least till we get to 0 for both the 1600 and 365 day periods. Thanks -Vincent

9 years, 1 month

[xwiki-devs] [Proposal] Terminology for xwiki.org

by vincent＠massol.net

Hi devs, Now that we’ve voted on the "XWiki Core” concept and that we’ve agreed that the xwiki organization on github should focused on offering core extensions only (and the rest should be moved to contrib) we need to ensure that we use the same terminology everywhere. I’d like to start updating xwiki.org accordingly but first I want to be sure we agree on the terminology: * The "XWiki Runtime”: the XWiki WAR that you get from the various distributions that you can find on xwiki.org. It’s a minimalistic runtime on top of which you can install Extensions. Documentation for it will be available at http://platform.xwiki.org. * “XWiki Core”: Represents the set of XWiki APIs/sources making up the "XWiki Platform”. The sources are available in github in the xwiki-commons, xwiki-rendering and xwiki-platform repositories. More globally can be meant to represent all the sources found in the xwiki github organization. * “XWiki Contrib”: Extensions to the "XWiki Runtime”. Located under the xwiki-contrib organization in github. * The "XWiki Core Development Team” or “XWiki Core Team” (previously called "XWiki Development Team"): the list of committers of the “xwiki" github organization. * “XWiki Platform”: synonymous for “XWiki Core”. Since “XWiki Platform” could also represent the xwiki-platform github repository, it’s better to use “XWiki Core” when wanting to name the full content of the xwiki github organization. For example: “The XWiki Core Development Team works on XWiki Core”… * “Flavor”: a set of Extensions (usually with a purpose) that can be installed all together in a XWiki Runtime or when creating a subwiki inside the XWiki Runtime. * The “Default Flavor”: the unique flavor provided by the “XWiki Core Development Team”. Contrib projects and more generally anyone else can contribute other flavors on extensions.xwiki.org. These flavors will appear in the XWiki Platform when you first run it or when you create a new subwiki. The Default Flavor is going to replace “XWiki Enterprise” (and enterprise.xwiki.org will be removed and folded into platform.xwiki.org - the same will happen for xwiki-enterprise which will be folded into xwiki-platform in github) * “XWiki Committers” or “XWiki Team". Vague terms that represent the full set of committers of both the xwiki and xwiki-contrib github organizations. * “XWiki N.P”. Shortcut for the “XWiki Runtime” version N.P (e.g. “XWiki 7.4.1”). * The “XWiki Project”. Generic term that includes the work done by XWiki Contrib Committers, XWiki Core Committers and by extensions the work done by the full community of contributors to both xwiki and xwiki-contrib github organizations. Do you agree with this? Any other terms that we should define? Once agreed I’ll kickstart the work by updating xwiki.org pages by creating a Terminology page and update some existing pages. However it’ll be up to everyone to follow the terminology. Thanks -Vincent

9 years, 1 month

[xwiki-devs] [VOTE] Move to Java 8 as minimal version for XWiki 8.0+

by vincent＠massol.net

Hi devs, I’d like to propose that we move to Java 8 as the minimal Java version supported for XWiki 8.0+. The rationale is: * Java 7 is end of life since April 2015. * It brings [Default Methods|https://docs.oracle.com/javase/tutorial/java/IandI/defaultmethods.h…] which would make retro compatibility a lot easier for us (it's very hard to add new features to existing API right now). * Required for: ** Infinispan 8 ** JGroups 4 ** Jetty 9.3+ seems to require Java 8 (or maybe it's just optimized for it, http://download.eclipse.org/jetty/ is not crystal clear about what "Java 8+" means exactly) Nice to have * Lambda Expressions * Repeating Annotations which would probably allow us to use several times \@Named instead of \@Component(hints=\{"hint1", "hint2"\}) for example * New date/time APIs (pretty much what is in Joda Time). We should refactor our $datetool velocity tool to make the java.time api available from velocity * more… See http://jira.xwiki.org/browse/XCOMMONS-878 Here’s my +1 and my +1 to start requiring Java 8 for 8.0M2. Thanks -Vincent

9 years, 1 month

[xwiki-devs] [VOTE] First set of extensions to move out of wiki-platform

by vincent＠massol.net

Hi devs, Following the “XWiki Core” VOTE (http://markmail.org/message/rqgqzbepzms3p6h2), I’m now proposing to move the following extensions out of xwiki-platform and into xwiki-contrib: I’ll also start moving some extensions from platform, starting with: - xwiki-platform-blog - xwiki-platform-faq - xwiki-platform-jira - xwiki-platform-release - xwiki-platform-selenium Please vote. Here’s my +1 Thanks -Vincent

9 years, 1 month

[xwiki-devs] Creation of user profile under custom space

by Vishal Erande

By default, user profile application creates profile page under /xwiki/bin/view/XWiki Instead, i want the profile pages be created in xwiki/bin/view/UserSpace How can i do that

9 years, 1 month

[xwiki-devs] [Contrib] Demo flavor

by vincent＠massol.net

Hi, I’d like to request a github repo in xwiki-contrib for a Demo flavor extension. The idea is that: - since we want to demonstrate the power of xwiki on playground.xwiki.org - and since the xwiki github org will focus on providing generic runtime only (made only with core extensions), it would be interesting for users testing xwiki to have a demo flavor that users can pick from on the DW screen (in addition to the default flavor). In the future we expect the community to create a lot more flavors but that’s for later, won’t happen overnight. So I’m proposing to create a demo flavor that includes a maximum number of high-quality extensions that we have in xwiki-contrib: To start with: - Blog - File Manager - Meeting Manager - Forum - Task Manager - Idea - FAQ - Diagram In addition, in term of layout I’m proposing: * Navigation panel on the left * App bar on the right * A demo text on the home page and beneath the activity stream (one under another so that clicking edit makes it easy to update the page) WDYT? Thanks -Vincent

9 years, 1 month

[xwiki-devs] [Brainstorming] xwiki/1.0 syntax leftovers in platform

by vincent＠massol.net

Hi devs, Point 1: We still have some leftovers of the xwiki/1.0 syntax in platform. To give 2 examples: * XWikiDocument.getUniqueWikiLinkedPages() * XWikiDocument.getSections() In both cases the code is like: public List<DocumentSection> getSections() throws XWikiException { if (is10Syntax()) { return getSections10(); } else { … new rendering algorithm… Point 2: We still have a lot of pages (hundreds) written in xwiki/1.0 syntax on xwiki.org (old release notes, old FAQ entries, the curriki wiki, etc) Some details (http://www.xwiki.org/xwiki/bin/view/Admin/Syntaxes): * platform: 49 pages (5%) * xwiki: 530 pages (13%) * curriki: 398 pages (37%) * dev: 126 (3%) * xclams: 29 (6%) * etc total of pages for the wikis supported by the xwiki dev team: 770 pages. Possible actions ================ A - Migrate xwiki.org content. Hard and tedious to do since there are lots of pages. B - Discard content written in xwiki/1.0 syntax on xwiki.org (and migrate the few pages that are in 1.0 but still needed, like the site Survey page) C - Continue to support the xwiki/1.0 syntax located in xwiki-contrib to ensure it doesn’t break so that we can install it on xwiki.org when we migrate to 8.x in the future. D - Continue moving xwiki/1.0 code from platform into the contrib module for xwiki/1.0. This means doing some refactoring and introducing some component. I think it would be interesting to deprecate XWikiDocument.getUniqueWikiLinkedPages() and XWikiDocument.getSections() (and move them to legacy) and instead introduce some new components somewhere TBD. Generally speaking I’m in favor to not manipulate the XDOM inside of the XWikiDocument class (just let it return the XDOM but consider it a black box) and instead do any XDOM manipulation elsewhere (refactoring module or other modules). E - Break the xwiki/1.0 syntax by removing the code in platform, i.e. the is10Syntax() above for example. We would need to decide when it’s ok to do this. In 8.x? In 9.x? Later? I see 2 main strategies that seem valid to me: - Strategy 1: Do C and D. This would mean continuing to leave the old content of xwiki.org in xwiki/1.0 syntax and convert only the few pages that are still used today such as the site Survey page - but for example not translating old release notes. - Strategy 2: Work as a task force (i.e. with everyone helping actively do the work) to migrate the content of xwiki.org (and possibly move away curriki and some older instance of xwiki). Consider that xwiki/1.0 syntax is not working anymore if you install XWiki 8.x (9.x? later?). That’s A and E. Any other ideas? Thoughts? WDYT? Personally I’d be ok with both. Thanks -Vincent

9 years, 1 month

[xwiki-devs] [Proposal] Delay 8.0M2 release by 1 week

by vincent＠massol.net

Hi devs, With the work done for 7.4.1 we’ve delayed the release of 8.0M1 a lot (by 2 weeks until now!). Thus 8.0M2 only has 1 more work before we should release it (was planned for 15th of Feb) and we haven’t released 8.0M1 yet… I’m thus proposing that we push the RC1 release by one week, and use the following updated dates: * 8.0M1: 8 or 9th of Feb * 8.0M2: 22nd of Feb * 8.0RC1: 3rd of March * 8.0final: 14th of March (same date as originally planned) WDYT? See also http://www.xwiki.org/xwiki/bin/view/Roadmaps/ Thanks -Vincent

9 years, 1 month

[xwiki-devs] [ANN] XWiki 8.0 Milestone 1 released

by Ecaterina Moraru (Valica)

The XWiki development team is proud to announce the availability of XWiki 8.0 Milestone 1. This is the first milestone release of the 8.x cycle. With this occasion we deprecated and retired multiple projects like Colibri Skin, Color Themes, old XWiki 1.0 syntax, etc. We also continued to polish our Nested Pages feature introduced in 7.2, by adding improvements such as: asynchronous copy and rename page actions, improved location picker for simple users and the ability to omit "WebHome" in wiki links syntax. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki80M1 The following people have contributed code to this release (sorted alphabetically): Alexandru Cotiugă Denis Gervalle Ecaterina Moraru (Valica) Eduard Moraru Guillaume Delhumeau Marius Dumitru Florea Sergiu Dumitriu Thomas Mortagne Vincent Massol Thanks for your support -The XWiki dev team

9 years, 1 month

[xwiki-devs] [ANN] XWiki 7.4.1 released

by Thomas Mortagne

The XWiki development team is proud to announce the availability of XWiki 7.4.1. This is a bug fix release including some important improvements such as: asynchronous copy and rename page actions, improved location picker when copying and renaming, ability to omit "WebHome" in wiki links and images syntaxes. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki741 The following people have contributed code to this release (sorted alphabetically): acotiuga Denis Gervalle Eduard Moraru Guillaume Delhumeau Marius Dumitru Florea Thomas Mortagne Vincent Massol Thanks for your support -The XWiki dev team

9 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs February 2016