Hi devs,
Caty and I would like to work on improving xwiki.org and the first big items that we’d like to do is:
* Move all content from platform.xwiki.org & enterprise.xwiki.org to xwiki.org (i.e. the main wiki)
* When moving pages, use redirects
* Deprecate platform.xwiki.org & enterprise.xwiki.org by adding a banner (After Header UIX)
* Move all pages to 3 locations on the main wiki: Documentation.UserGuide, Documentation.DevGuide and Document.AdminGuide
* We also replace “XWiki Enterprise” with “XWiki” and be as generic as possible
WDYT?
Thanks
-Vincent
Hi guys,
Reminder: we have an event calendar on http://www.xwiki.org/xwiki/bin/view/Main/Events
It’s using google calendar and we need to all contribute to it to add all the known XWiki events to it.
Committers should be granted edit rights already for most of them (if you don’t have the rights let me know and I’ll add you).
Thanks
-Vincent
The XWiki development team is proud to announce the availability of XWiki
9.8-rc-1.
This release introduces a new feature for the Notifications: the Watched
Entities. It is disabled by default but you should try it to experiment it
because it will replace the Watchlist Application soon.
For the users, we now have more usable notification filter settings and a
nice helper when you edit a "Database List" field.
For developers, it is easier to propose an extension containing REST
resources, or to customize the Flamingo LESS code. We have also exposes
more database columns in the Query Module for users who don't have the
programming rights. The notification filters AST (Abstract Syntax Tree)
proposes new types of nodes to create complex filter queries. There are
also new facilities to avoid using SyntaxFactory, to make Extension Manager
faster, or to identify skins elements with proper IDs.
As usual, this release brings bug fixes (15 in this one!).
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/Data/XWiki/9.8RC1/
Thanks for your support
-The XWiki dev team
Hi devs,
I’ve been thinking how to automate testing of various XWiki configurations and I’ve come up with an architecture that I’ve published in a blog post:
https://twitter.com/vmassol/status/909685486108708865
Let me know what you think and if you’d like to see this in action! :)
Also, if you’re interested in participating let me know and we can share the workload.
Thanks
-Vincent
Hi everyone !
So, recently I have been dealing with a module that uses two kind of
translation strings.
- "Static" translations : the title of a block, a xHint, … the
translation key itself is not meant to be changed over time.
- "Dynamic" translations : things like :
- mymodule.component.<componentId>.name
- mymodule.component.<componentId>.description
Those are translation strings that depend on a parameter (here
componentId) that can be part of a list.
If you want a better in-context example, check out this gist :
https://gist.github.com/aubincleme/19edb249082185deedc8ec36fe354d42
Currently, we don’t have a lot of best practices regarding the
translation keys (see the doc :
http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HTransla…),
so it may b nice to think about improving them.
Here are some proposals :
* For translation keys used for a livetable, we could use the following
: <prefix>.<liveTableId>Table.<columnName> or
<prefix>.table.<columnName> if the livetable doesn’t have a specific id.
* If we deal with "dynamic" translation keys, it would be nice to mark
them as different from the others with an underscore (_) prefix, or a
specific keyword.
WDYT ?
Thanks,
Clément
Hi devs,
Let’s do our first ProgrammingRights-Fixing Day. The goal is to modify pages part of XWiki Standard that require PR so that they don’t require PR anymore (for example by adding new APIs or using other APIs).
Here’s a list of pages that currently require PR (there are probably more):
* XWiki.DeletedDocumentsJSON
* AppWithinMinutes.DynamicMessageTool
* AnnotationCode.Style
* XWiki.DeletedDocuments
* AppWithinMinutes.LiveTableEditSheet
* AppWithinMinutes.ClassEditSheet
* XWiki.DeletedAttachments
* Main.Activity
* AnnotationCode.Script
(see http://jira.xwiki.org/browse/XWIKI-10446?focusedCommentId=83579&page=com.at… )
I suggest that we each mention which page we’re handling to avoid duplicating work.
Let’s try it! I have no idea what we’ll succeed in doing or not but we need to try :)
Thanks
-Vincent
Hi devs,
Here’s a proposal for XWiki 9.8 (1 month):
Dates
=====
* 9.8RC1: 18th of Sep 2017
* 9.8: 25th of Sep 2017
Sure
====
Regressions (highest importance):
* Put back the ability to import from office in CKEditor (as we had in the GWT editor) - Marius
Some leftovers from previous roadmaps to finish:
* Livetable improvements - Marius
** Implement bulk actions on livetable items
** Allow List of Users filtering also by entering first and last name, not just the user id
** Displaying a livetable list filter for a non-static list field is not scalable
** Support LiveTable text filtering on DBListclass columns
* Notifications - Continue work - Guillaume
** Finish replacing the Watchlist
** Replace the Activity Stream
** Add notifications for recommended apps
New:
* XWIKI-14605: REST resource installed as extension is broken when upgrading/uninstalling a JAR from the same namespace or root namespace - Thomas
Other:
* Work on restructuring xwiki.org on several aspects - Vincent + Caty
** Remove XWiki Enterprise and mention the Standard flavor instead
** Improve the navigation by adding a navigation panel on the left and reorg pages as nested pages where it makes sense
** Small improvements to the skin to make it simpler for a website
If time permits
============
* Fix the move issue: http://jira.xwiki.org/browse/XWIKI-14626
* Administration: Default values
** {{jira url="https://jira.xwiki.org" style="enum"}}XWIKI-14157{{/jira}} Display the default and inherited values in the Administration
** {{jira url="https://jira.xwiki.org" style="enum"}}XWIKI-9663{{/jira}} Show default value for date format in administration
* XWIKI-14162: Save button more visible. Position Save buttons on a fixed-bottom area. (continue from Pierre's PR)
* Improve XWiki Upgrades
** Display a notification when there’s a newer version available
** XWIKI-14377 Warnings when editing extension pages (same as for delete)
* Multipage tour feature
* Add an {{attachments}} macro
* Performance work
** Finish stuff to make filesystem attachment/history content the default (automatic migration, broken deleted attachments UI, etc.)
Let me know if anyone sees any issue with this and if other devs/contributors want to contribute something for 9.8!
Thanks
-Vincent
Greetings everyone!
I’m delighted to announce the first stable public release of the Dokuwiki importer, completing my GSOC project.
This importer can now:
> Support all supported archives from apache compress as both File and streaming input.
> Can import user data, document revision, and also attachments.
> Using the syntax parser from M2, it can convert the dokuwiki syntax to xwiki/2.1 syntax strings.
This can be downloaded from the extension page here: http://extensions.xwiki.org/xwiki/bin/view/Extension/DokuWiki/ <http://extensions.xwiki.org/xwiki/bin/view/Extension/DokuWiki/>
Note: The syntax parser can also be used separately to parse dokuwiki syntax.
Suggestions/bugs are welcome!
Thanks!
Shubham Jain
Hi devs,
We've had several complaints from users about the Navigation Panel. The 3 big needs that I’ve heard are:
1) Semi-automated by having the ability to blacklist items
2) Better performance ("It’s slow to load and reloads every time you navigate to a new page”)
3) Ability to sort entries
See for ex:
* https://forum.xwiki.org/t/your-xwiki-usability-pain-points/440/11
* https://jira.xwiki.org/browse/XWIKI-12895
Point 1
======
That Panel is critical since it’s what users see the most (without navigating anywhere) and it’s important that users be able to customize it (while keeping the automated aspect, e.g. adding a new page should add it to the tree by default as it’s done now).
Marius mentioned that adding blacklisting doesn’t make sense because we would then have different behaviors between the Navigation Panel and:
• the breadcrumb trees
• the page index tree
• the location picker tree used on create/copy/rename page
• the location picker tree used by the CKEditor link and image dialogs
• anywhere we use a tree in XWiki default user interface
However I don’t fully agree about this. If you check the Applications Panel, it’s not listing all Apps that exist. It’s only listing Apps that the admin want his/her users to see by default. To see all apps there’s the App Index. Similarly the Navigation Panel on the left should be listing what the admin wants his/her users to see, and going to the Page Index should list all pages.
In short I really believe we need to allow customizing the panel with an Admin UI that allows to blacklist some nodes).
Does anyone see a better idea to fulfill our user’s needs?
Point 2
======
The main answer I see is to implement the doc title cache so that we don’t have to load documents.
Do you see anything else?
Point 3
======
I think this is kind of already implemented with “showDocumentTitle”, right?
Thanks
-Vincent
Hi GSOC students,
This is a reminder that there’s a deadline approaching soon:
"August 21-29: Students submit their work product (code) and a final evaluation of their Mentor”
On my side, I’m mentoring 2 projects:
* The Glossary Application project. Unfortunately this one failed the first review since not enough work was done. However Sarthak mentioned to me that he wanted to continue but he probably lost faith since I haven’t seen any work done. Sarthak, could you confirm that you dropped the topic altogether?
* The RedPen integration. There’s been several commits done and several status emails sent but it seems it’s lagging behind quite substantially since we’ve yet to see any working prototype. Desheng, it’s really important that you release ASAP a first working version on extensions.xwiki.org (that’s a condition of success) that we can try and install in our own XWiki instances.
Thanks
-Vincent
Hi devs,
We have several pages requiring PR and we’re not doing much about them.
This is a major pain, for example on myxwiki.org where, every time some admin update their wikis they break features. It’s not showing XWiki in good light neither.
I’ve found at least those pages requiring PR:
* XWiki.AllAttachmentsResults
* XWiki.DeletedDocumentsJSON
* AppWithinMinutes.DynamicMessageTool
* AnnotationCode.Style
* XWiki.DeletedDocuments
* AppWithinMinutes.LiveTableEditSheet
* AppWithinMinutes.ClassEditSheet
* XWiki.DeletedAttachments
* Main.Activity
* AnnotationCode.Script
(see http://jira.xwiki.org/browse/XWIKI-10446?focusedCommentId=83579&page=com.at… )
And FTR we keep adding more over time. For example in 2012, AWM introduced a PR: https://github.com/xwiki/xwiki-platform/commit/ae09194f83b9fe1f75778e0a2501…
I’d like to propose to do a PR-fixing day for the next non-BFD day, i.e. in 2 weeks.
WDYT?
Thanks
-Vincent
Hello XWiki team!
I just write to brag a bit about *Extension Repository Connector - NPM*
that I created in 3rd phase of GSoC ;)
You can read about it here:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Extension%20Repository…
and
test it if you wish (there's an example to follow).
As before - any feedback highly appreciated :)
Have a nice day!
Best,
Krzysztof
The XWiki development team is proud to announce the availability of XWiki
9.7.
This release brings small improvements to currently established features.
The code viewer now provides a blame view by default and the notification
center now allows the user to enable or disable notifications globally on
an application, as well as toggling default notification filters provided
by the platform.
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/Data/XWiki/9.7/
Thanks for your support
-The XWiki dev team
The XWiki development team is proud to announce the availability of
XWiki 9.7RC1!
This release brings small improvements to currently established
features. The code viewer now provides a blame view by default and the
notification center now allows the user to enable or disable
notifications globally on an application, as well as toggling default
notification filters provided by the platform.
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/Data/XWiki/9.7RC1
Thanks for your support
-The XWiki dev team
Hi devs,
While thinking about what features a Technical Documentation Flavor [1]
should have, I came up with some ideas that we could integrate inside
xwiki.org in order to make it a better documentation website:
- navigation tree in the left panel, see
--
http://design.xwiki.org/xwiki/bin/download/Proposal/Flavors/TechnicalDocume…
compared to
-- http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation
- simpler skin (at least remove the comments area - lots of deprecated
questions/answers and we have now the forum for that)
- simpler menu (less entries + merge with the navbar if technical possible
now, otherwise wait for newer version)
- simpler footer area by removing the number of links displayed (we need to
look at mouseflow)
Would be great also to upgrade XWiki.org to a newer version.
There were all sorts of ideas in the past like:
- displaying 'Edit' also for unregistered in order to encourage edits
- display 'Register'/'Log-in' links in the navbar in order to encourage
edits
these are not part of the current proposal, but keep the ideas coming :) we
will try to implement them when we can.
Of course it would be great if we would had time to:
- update the docs content
- reorganize pages
- update the blog styling
- etc.
but I guess small changes will come in time.
Let me know what you think,
Caty
[1]
http://design.xwiki.org/xwiki/bin/view/Proposal/Flavors/TechnicalDocumentat…
Hi devs,
I’d like to raise a pain point.
Environment:
* myxwiki.org
* lescastcodeurs wiki
What happened:
* We upgraded myxwiki.org
* Emmanuel (an Admin user of the lescastcodeurs wiki) got the Distribution Wizard and followed it to upgrade the wiki
The problem:
* Several features are broken. For example AppWithinMinutes (some pages display red boxes saying that the last author didn’t have script rights)
The reason:
* Emmanuel was admin but didn’t have script rights (after some xwiki upgrade that caused existing users to not have script rights if not set explicitly)
* For ex on the AppWithinMinutes space: https://www.evernote.com/l/AHcaXGYEzdZJXLTQEy2Vbohcfzu5vMbxkBM
Brainstorming:
1) What should we do to not have this problem?
2) What solution do we offer to fix it easily?
Re 2) we have:
* http://extensions.xwiki.org/xwiki/bin/view/Extension/Change%20Content%20Aut…
* http://extensions.xwiki.org/xwiki/bin/view/Extension/Change%20creator%2C%20…
However none are good for me without changes since they either change all pages in the wiki (which is not what I want) or they change only a single page.
Any idea?
Thanks
-Vincent
Hi devs,
Problem
=======
We have 2 issues right now when installing an extension in XWiki:
1) It’s not clear where is the entry point of that extension.
- Example1: an app that is only for admins and only has a ConfigurableClass
- Example2: an app that provides a macro and doesn’t have a UI
2) Even when an extension registers itself in the Applications Panel, the user still need to refresh the page or navigate away to see it.
Proposal
========
* Introduce the concept of Entry point (a.k.a home page) in Extension metadata
* Have the EM UI display the extension’s entry point (when there’s one) after having installed the extension so that the user can click on it and be taken to the home page of the extension.
This would make extensions more discoverable IMO.
Implementation Details
==================
* Some maven extension metadata properties in pom.xml
* A format to represent an entry point. It shouldn’t be a full URL since that needs to be computed at runtime. Basically it should contain:
** The document reference
** The action to use (view, admin, etc) - optional, should default to “view"
** The query string to use - optional, should default to an empty query string
This corresponds to the notion of ResourceReference (EntityResourceReference to be precise). However we don’t have any textual representation of it ATM.
WDYT? Good idea? Bad idea?
Thanks
-Vincent
Hi all this is another update regarding the integration of Redpen, aka the
Content Checker extension. As of now, I have finally implemented
dictionary-based validators (validators that check for invalid or subpar
expressions). With this, most of the validators will be easily added within
the configurable class of the extension.
Feel free to check the design page for the UI implementation:
http://design.xwiki.org/xwiki/bin/view/Proposal/RedPenIntegration
<http://design.xwiki.org/xwiki/bin/view/Proposal/RedPenIntegration>
Also, the output of the document checks are currently registered in the
logs, and are separated into warnings and errors. The determination of
whether a particular validator setting gives a warning or an error is
registered in the xwiki.properties file. The automatic validation function
also cancels document saves when errors are registered by Redpen.
There are now two core milestones to be done on this extension. First and
critically, I would need to implement functional test, especially on the
Configurable classes. To this end, I would appreciate any advise on how I
can implement this (I have previously only created a functional test to test
the entry of expressions into the Dictionary part of the extension.)
After that, I would then implement the Job module of this extension. (The
Job will be accessible in another tab, 'Job', below the current Dictionary
tab in the Administration UI panel.)
I would greatly appreciate any advice on what else needs to be added
regarding the Content Checker functionality, and with the implementation of
functional tests. Thank you!
--
View this message in context: http://xwiki.475771.n2.nabble.com/GSOC-Update-5-Redpen-Integration-tp760438…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi devs !
So … it’s yet another proposition on "How should we design the
notifications center".
Today, two proposals are made in order to integrate the options that we
have currently in the watchlist preferences into the notification center UI.
We have two ideas described in this design page :
http://design.xwiki.org/xwiki/bin/view/Proposal/NotificationPreferenceCente…
and dicussed in this JIRA issue : https://jira.xwiki.org/browse/XWIKI-14597
As those two UI are quite different from each other, we would love to
get your feedback on these proposals.
WDYT ?
Thanks,
--
Clément Aubin
Web Developer Intern @XWiki SAS
clement.aubin(a)xwiki.com
More about us at http://www.xwiki.com
Greetings everyone!
I’m pleased to announce the second milestone of the Dokuwiki importer.
The additions are :
> Support for a wide range of archives in the input.
> DokuWiki Syntax parser supporting full grammar.
You can find it here: http://extensions.xwiki.org/xwiki/bin/view/Extension/DokuWiki/
Please feel free to experiment, and report any bug that you encounter.
Cheers!
Shubham