VOTE 1: Disable the Watchlist by default and enable all Notifications
features on XWiki 10.1 RC 1
+1
VOTE 2: Disable the Watchlist by default and enable all Notifications
features on XWiki 9.12.3 so the LTS has good options enabled by default
+1
Thanks,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi,
I would like to request the "macro-kanban" repository to publish a macro
which allows to make kanban views of AppWithinMinutes data. It also allows
to drag and drop items to change the value of a field.
Thanks
Ludovic
--
*Ludovic Dubost*
*Founder and CEO*
ludovic(a)xwiki.com
skype: ldubost
Blog: http://blog.ludovic.orgTry XWiki on the cloud
<http://www.xwiki.com/en/products/try-xwiki-cloud> - Try Cryptpad: Secure
realtime Wysiwyg Editing <https://cryptpad.fr>
Hi devs,
Here’s a proposed roadmap discussed with XWiki SAS devs (Thomas, Guillaume, Caty) who are available to work on 10.1.
Scope
=====
* Finish moving to FS-based attachments by default (it was planned for 10.0 already) - Assignee: Thomas
* Finish polishing/tuning/fixing Notifications and remove watchlist - Assigne: Guillaume
** Idea: enable mails by default when notifs are enabled.
* Prevent accidental move/renames - http://jira.xwiki.org/browse/XWIKI-14591 - Assignee: Thomas
* Start discussions to agree about usability proposals listed at http://design.xwiki.org/xwiki/bin/view/Proposal/Usability/Tasks5/Prioritiza… so that the first ones can be done during 10.2 and 10.3 - Assignee: Caty
* Skin refresh investigation (including Bootstrap 4) - Assignee: Caty
Dates:
=====
* 10.1RC1: 19 Jan 2018
* 10.1Final: 26 Jan 2018
Let me know if you have any remarks/issues or if you wish to contribute something extra to this roadmap.
Thanks
-Vincent
Hi developers,
We have never really decided what we will do with javascript frameworks in
the future. Angular was a good candidate at some point, and we have even
used it in the File Manager application. But then we have been very
disappointed when we discovered the new versions of Angular were not
retro-compatible. It may have been fixed since then, but I have not really
followed the news about it.
An other disadvantage of AngularJS is that it does too much. For example,
they have a custom component system with a kind of dependencies injections.
But we already can do that with RequireJS, for which it is the job. I have
already started to split my JavaScript's code in several components thanks
to RequireJS, and it works well. I think it's good to continue with
RequireJS. It is currently our go-to library when we need to use jQuery, or
even... Angular.
I have worked a lot on a new version of the Nested Pages Migrator last
year. The new version has never been released, because of blocking bugs on
the XWiki Platform's core-side. But I now have some experience with the
library I used: KnockoutJS.
It's a very simple library that does only one job and does it well: two-way
data-bindings. It plays well with RequireJS and it does not re-invent its
own component mechanism. The HTML code is not polluted by non-valid tags
(instead it uses "data-" properties and special HTML comments). The
documentation is extremely clear, and tutorials are great.
It's not the most popular library out there, but it's stable and still
alive. The trends are changing so quickly in the JS world (React was the
star not so long ago, but now it is hated because of a license change...),
but Knockout is still there. If the project dies, I think it will be easier
to replace it with an other simple library than a big "framework".
This is not a proposal or a vote, but only a feedback about this library.
You can test it there: http://knockoutjs.com/
Thanks,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs.
Last week, we failed to release XWiki 10.0 Release Candidate 1 on time. The
reason was the build was still not passing on Wednesday's evening. That is
why Vincent, Thomas and I decided that it does not worth to release it
knowing that we need to release XWiki 10.0 final today.
We had not followed the usual practice about sending an email to the
community first, and we want to apologize for that.
Thanks,
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi!,
I am Prateek Bilung, a second-year undergraduate student at B.I.T., Mesra
(India). I am new to open source community and want to contribute to this
organization. I know basics of javascript, DOM manipulation and interested
in the project "Translation in context". Please guide me on this.
Thanks!
Hi devs,
We’ve been using the surefire plugin from the beginning even for functional tests.
However it would be more correct to use the failsafe plugin for functional tests since this allows to perform some actions if a test fails (like stopping XWiki - Note that right now this is not affecting us since we start/stop XWiki from Java so we’ve implemented this behavior ourselves).
I need this for using the fabric8 docker plugin for ex so that if some functional test fails the docker containers will be stopped.
Ok with everyone?
For reference: http://maven.apache.org/surefire/maven-failsafe-plugin/
Thanks
-Vincent
Hi devs,
These are the current code style rules for committed XML wiki pages:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiXMLFilesCodeStyle
= Proposal 1 =
I was personally not aware we had documented these practices that we had
been applying since forever. It's good that we have them, but there seems
to be no mention about committing changes for the "creationDate", "date"
and "contentUpdateDate" fields.
Part of the committers (including myself) are applying the old practice of
omitting changes to the date fields when committing a change to an XML wiki
page. However, since this practice is not written and agreed upon, its
usage is not consistent.
So, the proposal is to include the rule of not committing changes on the
date fields of XML wiki pages.
The rationale, AFAIR, includes:
* After an upgrade, users should not see "ghost" modifications in their
wiki (e.g. when sorting by date in the Page Index). This affects even more
manual imports with the "as backup" option enabled.
* On release, any date changes of a default translation XML page will
produce N other XML page changes, for each translation of the modified page
(due to the way l10n exports the translations based on the latest version
of the default language of that page).
* others?
= Proposal 2 =
Now, building on this, I would like to make a second proposal (which I
don't believe deserves a separate thread):
1) Let's remove all date fields from committed XML wiki pages in our source
repository
2) Let's make sure that the XAR import properly handles empty or missing
date fields and falls back on the current date
3) Let's update the xar:format goal to remove the date fields
(configurable, since it could they might still be needed by some content
projects, etc.)
4) Let's make the build fail (xar:verify) if the XML wiki pages contain
date fields (again configurable, as above)
Note: All the above still depend on the first proposal of not committing
date changes to XML files (which will be simplified by point 3) above).
The rationale for this is that we have always wanted to fix our "dates
problem", since after installation, the wiki is populated with pages
created in 2009, which is extremely odd to users that have just installed
XWiki. This second proposal sounds to me like a solution for that.
WDYT?
Thanks,
Eduard
Hi guys,
I’m trying to use the Job REST API but the doc is pretty poor at http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/XWikiR…
For example to execute a job it says that you only need to pass a “jobType” described as "The type of the job to pass to the Job Executor” … errr what’s the type and what are the valid values? Would be nice to have some example too.
Also it doesn’t mention any payload that I have to send but I guess I need to describe the job that I need to execute. What’s the format?
It also says:
“
Since 9.2RC1 jobs started trough the REST API automatically get their runtime context injected with the following REST HTTP request context properties:
• current wiki
• current user
• request URL and parameters
“
What if I want to specify the wiki, user for ex? How do I do that?
At the end there are examples of file format at http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/XWikiR… but nothing for jobs.
Could someone help improve the doc so that I can try to use it?
Thanks!
-Vincent
Hi devs,
This proposal is related to the following discussion on IRC :
https://botbot.me/freenode/xwiki/2018-01-08/?msg=95495049&page=5
Abstract: We currently have an abstraction of the notion of a
"container" defined in xwiki-platform-container-api [1]. This
abstraction is very basic, but allows XWiki to support two different
types of containers : Servlet and Portlet, and maybe support other types
in the future.
Problem: As those abstractions are very basic, it's quite hard to use
them without downcasting them. A common example is the following: if I
want to send a redirection in a Response object [2], I will need either
to forge my own output that returns the correct HTTP code, with the
correct header, etc … or I can downcast the given Response to all of its
possible implementations and, for each implementation, find the correct
method to use for sending a redirect.
In order to avoid such tricks in the future, we could implement
decorators that will allow Request and Response implementations to
handle certain actions. In my previous example, a Response implementing
RedirectResponse would expose a method `#sendRedirect(String url)`. The
advantage here is that we don't really need to know on which Response
implementation we are working on.
WDYT ?
Thanks,
Clément
[1]
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwi…
[2]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…
Hi devs,
According to our rule, non active committers become Emeritus committers. I’ve cleaned up the list of core committers on github and the following devs are now Emeritus:
* Alex Busenius
* Andreas Jonssson
* Fabio Mancinelli
* Jean-Vincent Drean
* Jerome Velociter
* Marta Girdea
This means that you guys are now discharged from VOTEs and such.
If you ever want to commit stuff again you won’t need to be VOTEd again. You just need to send us an email and we’ll add you back to the active committer list.
Thank you for all your work over all those years!
You’re now listed in the hall of fame under emeritus:
http://dev.xwiki.org/xwiki/bin/view/Community/HallOfFame#HEmeritusCommitters
Thanks
-Vincent
Hi devs and all,
Here’s a proposal for XWiki 10.0 discussed internally at XWiki SAS and based on the available developers for this period. Feel free to add items you’d like to implement too in the period! Also feel free to comment on the proposed items.
Note that there’s still some stabilization work that’s needed on XWiki 9.x, especially in the domain of Notifications. The idea is to release new versions of XWiki 9.x every 2 weeks at max.
# Topics
* Finish notifications - Guillaume (will be backported in 9.x)
* FS attachments by default - Thomas
* Performance - Thomas
* Skin refresh investigation + continue on usability for onboarding of admins and users (examples: inviting and adding users, creating the initial hierarchy of pages, change the logo, create the top menu) - Caty
# Dates
* 10.0RC1: 22nd of Jan 2018
* 10.0Final: 29th of Jan 2018
Thanks
-Vincent