Hi devs,
Today is BFD#86:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
Our current status for the 1 year period is 78 bugs behind. See:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=1#Created-vs-Resolved-Chart/10470
Here's the BFD#86 dashboard to follow t
+0
Thanks,
Eduard
On Thu, Apr 23, 2015 at 11:21 AM, Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com> wrote:
> +0
>
> Thanks,
> Marius
>
> On Thu, Apr 23, 2015 at 10:22 AM, vinc...@massol.net
> wrote:
> > Hi devs,
> >
> > With the upgrade of BouncyCastle to version 1.52 the
> xwiki-platfo
Reminder: Don`t forget about today's BFD!
-Eduard
On Thu, Apr 23, 2015 at 11:35 AM, Eduard Moraru
wrote:
> Hi devs,
>
> Today is BFD#86:
> http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
>
> Our current status for the 1 year period is 78 bug
Last week's results:
http://www.xwiki.org/xwiki/bin/view/Blog/Bug+Fixing+Day+86
Thanks,
Eduard
On Thu, Apr 23, 2015 at 4:38 PM, Eduard Moraru wrote:
> Reminder: Don`t forget about today's BFD!
>
> -Eduard
>
>
> On Thu, Apr 23, 2015 at 11:35 AM, Eduard Moraru
> w
Hi devs,
Today is BFD#87:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
Our current status for the 1 year period is 66 bugs behind. See:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=1#Created-vs-Resolved-Chart/10470
Here's the BFD#86 dashboard to follow t
Results: http://www.xwiki.org/xwiki/bin/view/Blog/Bug+Fixing+Day+87
Thanks,
Eduard
On Thu, Apr 30, 2015 at 12:10 PM, Eduard Moraru
wrote:
> Hi devs,
>
> Today is BFD#87:
> http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
>
> Our current status for the 1
Hi,
The question is about content fields (document contet, textarea content,
etc.) and not about the document's space name and document name fields,
which will still match in both approaches, right?
As far as I`ve understood it, text_en gets less matches than
text_en_splitting, but text_en has be
://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki71M2
The following people have contributed code to this release:
Denis Gervalle, Eduard Moraru, Guillaume Delhumeau, Thomas Mortagne,
Vincent Massol
+1 on my part, as well.
Thanks,
Eduard
On Tue, Jun 2, 2015 at 1:01 PM, Guillaume "Louis-Marie" Delhumeau <
gdelhum...@xwiki.com> wrote:
> You have my +1.
>
> I'll soon get back to you, devs, with some proposals about this.
>
> Thanks,
>
> 2015-06-02 10:17 GMT+02:00 vinc...@massol.net :
>
> > Hi
+1
Thanks,
Eduard
On Thu, Jun 4, 2015 at 4:45 PM, Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com> wrote:
> +1
>
> Thanks,
> Marius
>
> On Thu, Jun 4, 2015 at 3:55 PM, vinc...@massol.net
> wrote:
> > Hi devs,
> >
> > We’ve been a bit late on the 7.1 roadmap implementation, and as a
> con
Hi,
Going on the "node" architecture, where we have only documents and child
documents, here's something interesting that pops up as "the way to go"
when storing a tree structure in SQL [1]: Closure Table [2]. It seems to
cover pretty much all use cases, as solution 1 (Path Enumeration - what we
a
+1
Thanks,
Eduard
On Mon, Jun 8, 2015 at 1:16 PM, Ecaterina Moraru (Valica) wrote:
> Hi,
>
> This mail is about dropping support for Colibri Skin [1].
>
> Colibri Skin has been developed in version 2.0 (Sep 2009) and used as a
> default Skin until version 6.2 (Sep 2014), when it was replaced by
+1
Thanks,
Eduard
On Mon, Jun 8, 2015 at 4:40 PM, Ecaterina Moraru (Valica) wrote:
> Hi,
>
> One year ago (Mar 2014) [1] we discussed dropping support for IE8 for the
> 6.x cycle. The vote did not pass.
>
> Since then, we started the support for IE10/IE11 (Jun 2014) [2].
>
> You can see some st
+1
Thanks,
Eduard
On Mon, Jun 8, 2015 at 5:40 PM, Ecaterina Moraru (Valica) wrote:
> +1
>
> Thanks,
> Caty
>
> On Fri, Jun 5, 2015 at 10:10 PM, vinc...@massol.net
> wrote:
>
> > Hi Devs,
> >
> > Here are some proposals below that I have discussed with committers from
> > XWiki SAS already.
> >
L on the web. I really like the
> > way our current parent/child works, it provides the hierarchy in the UI,
> > invisible in the URL (keeping it relevant to the current page). Hierarchy
> > anyway should we displayed in Trees, not linear in URLs, since it's hard
> to
>
Hi,
As Caty mentioned in an offline discussion, in our current rights system we
have 2 types of rights:
1) Individual rights that are self-contained and can be enabled or disable
without side-effects:
- login, view, script, delete, register, comment, createwiki
2) Roles, defined by rights that i
Hi,
On Fri, Jun 12, 2015 at 12:53 PM, Ecaterina Moraru (Valica) <
vali...@gmail.com> wrote:
> How about renaming Script right to 'Execute'?
>
You have a point here, since any user can "script", i.e. write a script in
a document's content. What the currently proposed "script" right is
actually su
Hi,
On Fri, Jun 12, 2015 at 7:23 PM, Denis Gervalle wrote:
> From the proposal done so far, I like the proposal from Cathy and Edy, they
> looks the most simple ones to understand from an end-user point of view.
>
> Superadmin role implies Admin role which implies Execute rights and more.
>
> Ju
+1. We don`t have much choice in this anyway.
Thanks,
Eduard
On Wed, Jun 17, 2015 at 11:07 AM, vinc...@massol.net
wrote:
>
>
>
> On 17 Jun 2015 at 10:04:00, Jean SIMARD (jean.sim...@xwiki.com) wrote:
>
>
>
> On 17/06/2015 10:02, vinc...@massol.net wrote:
> > We also need to do the same for:
> >
On Wed, Jun 17, 2015 at 8:17 PM, Ludovic Dubost wrote:
> Hi all,
>
> I've transformed the attached files into images and galley macros so that
> the benchmark and proposal are more easily readable.
>
Cool! Thanks, Ludovic.
-Eduard
> http://design.xwiki.org/xwiki/bin/view/Proposal/PhotoAlbumBe
Hi,
The problem with Option 2 is that in read-only mode it works, however, when
you start manipulating regular document as if they were ND (e.g. add a
child document or go to the document Administration), you need to convert
the simple document into a ND (e.g. move X.Page to X.Page.WebHome) and th
bump.
Please see the discussion in the comments of
http://jira.xwiki.org/browse/XWIKI-9292
WDYT?
Thanks,
Eduard
On Thu, Apr 30, 2015 at 6:04 PM, Thomas Mortagne
wrote:
> By the way one consequence of this bug is that any user can break a
> page that need programming right just by tagging it f
Also, TL;DR: The proposed changes are
https://github.com/xwiki/xwiki-platform/pull/409/files
Thanks,
Eduard
On Fri, Jun 19, 2015 at 5:05 PM, Eduard Moraru wrote:
> bump.
>
> Please see the discussion in the comments of
> http://jira.xwiki.org/browse/XWIKI-9292
>
> WDYT?
&g
Hi,
For 7.2, we are introducing a new right to control permissions on the
execution of scripts.
Right now, out of all the scripts we support, Velocity is special and does
not require programming rights, since it uses only the public API. Of
course, if it has PR available, it can also access privi
Hi,
On Fri, Jun 19, 2015 at 5:42 PM, Thomas Mortagne
wrote:
> On Fri, Jun 19, 2015 at 4:25 PM, Eduard Moraru
> wrote:
> > Hi,
> >
> > For 7.2, we are introducing a new right to control permissions on the
> > execution of scripts.
> >
> > Right now, o
On Sat, Jun 20, 2015 at 9:36 AM, Thomas Mortagne
wrote:
> On Fri, Jun 19, 2015 at 5:42 PM, Eduard Moraru
> wrote:
> > Hi,
> >
> > On Fri, Jun 19, 2015 at 5:42 PM, Thomas Mortagne <
> thomas.morta...@xwiki.com>
> > wrote:
> >
> >> On F
Thanks, Thomas, for the feedback. I`m moving ahead with merging it into
master, since the build looks ready for it.
-Eduard
On Mon, Jun 22, 2015 at 1:22 PM, Thomas Mortagne
wrote:
> On Mon, Jun 22, 2015 at 12:17 PM, Eduard Moraru
> wrote:
> > On Sat, Jun 20, 2015 at 9:36 AM, Tho
5 +1s, 0 -1s.
Merging the proposed PR.
Thanks everybody!
-Eduard
On Tue, Jun 23, 2015 at 3:21 PM, Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com> wrote:
> +1
>
> Thanks,
> Marius
>
> On Fri, Jun 19, 2015 at 5:35 PM, Thomas Mortagne
> wrote:
> > +1
> >
> > At least it will be more clea
Hi,
On Wed, Jun 24, 2015 at 9:28 AM, vinc...@massol.net
wrote:
>
>
>
> On 24 Jun 2015 at 07:45:20, vinc...@massol.net (vinc...@massol.net(mailto:
> vinc...@massol.net)) wrote:
>
> >
> >
> >
> >
> >
> > On 23 Jun 2015 at 17:44:01, Ecaterina Moraru (Valica) (vali...@gmail.com
> (mailto:vali...@gma
Hi,
On Tue, Jun 23, 2015 at 6:43 PM, Ecaterina Moraru (Valica) <
vali...@gmail.com> wrote:
> Hi devs,
>
> So after discussing the topic of Nested in several mails, we need to reach
> a conclusion in order to start implementing.
>
> There are several open questions that I will summarize. Please ca
Hi,
On Thu, Jun 25, 2015 at 11:59 AM, vinc...@massol.net
wrote:
> Hi Marius and all,
>
> On 25 Jun 2015 at 08:19:22, Marius Dumitru Florea (
> mariusdumitru.flo...@xwiki.com(mailto:mariusdumitru.flo...@xwiki.com))
> wrote:
>
> [snip]
>
> > >> Q1. **NS vs ND in the UI**
> > >>
> > >
> > >> Q1.1 T
Hi,
+1 for T3. It goes well with what we have now for the create action and it
allows us enough room to do whatever we want and scale it.
This means that I would also be +1 for option A (which is consistent with
the new behavior of the edit button, i.e. no submenu for it like add X, add
Y or edit
Hi,
Now that we are moving to Nested Documents, there is the question of what
do we do with the existing space and page templates[1]? How do we (still)
display them?
In the new create UI we will be showing just the option to create a Nested
Document, but for advanced users, we might also show the
I like the Drawer approach, since it hides away the clutter and focuses on
the content. The breadcrumbs should provide content-based navigation, while
out-of-context navigation is doable from the drawer (which should be easy
to find and learn to user afterwards). This also obviously helps a lot on
Hi,
Initially, I wanted to go with the dots, however the backwards
compatibility problem would force us to either use a different key than
"spaces" and deprecate "spaces" or to introduce versioning (i.e. path
prefix like /rest/v1/wikis...), as Vincent said.
However, the multiple "spaces" (I think
+1 to the proposal and +1 to ask help from a committer if the Project Lead
is not available.
Also, when asking for a committer's help to promote a release you just did
on a contrib project, theoretically that committer should also check if you
are the project's lead and if proper jira versions hav
+1 for 5 for reasons already mentioned and because I find it to be the most
natural.
Thanks,
Eduard
On Thu, Jul 9, 2015 at 2:27 PM, Gabriela Smeria
wrote:
> Hello,
>
> Thanks for your effort, Caty!
>
>- Solution1: I think in order to see the tree, there are required a
>minimum number of
i/bin/view/ReleaseNotes/ReleaseNotesXWiki72M1
The following people have contributed code to this release:
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
Hi,
I also proposed the parent-child override implementation option a while
ago, mainly because I believe there will always be people wanting to have a
shortcut in the breadcrumbs without the need to move pages around and/or
changing a page's URL in the process.
On Wed, Jul 22, 2015 at 3:18 PM,
Yep, it goes along the lines of what we are doing with displaying Nested
Documents in the UI (view mode + wysiwyg and maybe inline for edit mode),
but doing Nested Spaces in the platform (java, actions other than view,
wiki syntax edit mode, etc.).
And it also has the added bonus of allowing us to
I agree with Thomas that it would be best to use EntityReference -> JSON as
much as possible (when passing the reference from velocity to javascript,
server-side), however, man times when you need a reference you also end up
building a new reference (on the client-side, i.e. javascript) so we can`t
Hi,
On Tue, Aug 4, 2015 at 12:35 PM, vinc...@massol.net
wrote:
> Hi devs,
>
> When we create a new page through Add > Page (for example) we are still
> setting the parent ATM, even though it’s not used by default in the
> breadcrumb or elswhere.
>
> Question 1: do we still want to set it or shou
Hi,
While I understand the logic, this proposal sounds like we want to move
towards skin-level tests (and supporting multiple skins), i.e. with the
addition of a new XWiki skin, we will need a complete set of new UI tests
for the new skin, since all our existing UI tests will be associated with
th
Hi,
Reminder: since we will start using more and more require.js, we need a
solution for optimizing [1] the requireJS javascript code because otherwise
we will end up with way too many HTTP requests for each individual
requireJS module.
Thanks,
Eduard
--
[1] http://requirejs.org/docs/op
Hi,
On Sun, Aug 2, 2015 at 1:55 PM, vinc...@massol.net
wrote:
> Hi Thomas,
>
> On 2 Aug 2015 at 12:15:37, Thomas Mortagne (thomas.morta...@xwiki.com
> (mailto:thomas.morta...@xwiki.com)) wrote:
>
> > On Sat, Aug 1, 2015 at 11:08 PM, vinc...@massol.net wrote:
> > > Hi devs,
> > >
> > > I’d like t
Hi,
On Sun, Aug 2, 2015 at 12:08 AM, vinc...@massol.net
wrote:
> Hi devs,
>
> I’d like to propose the following official future organization for our
> javascript/CSS code.
>
> Note1: When I say “javascript” below, it should be understood as js + css
> (possibly less too).
> Note2: I started writ
On Thu, Aug 6, 2015 at 4:01 PM, vinc...@massol.net
wrote:
>
>
>
> On 6 Aug 2015 at 14:57:37, Eduard Moraru (enygma2...@gmail.com(mailto:
> enygma2...@gmail.com)) wrote:
>
> > Hi,
> >
> > While I understand the logic, this proposal sounds like we want to mo
Hi,
Nice idea.
I guess we would also need a way to mark an issue/topic/complaint as solved
starting with a particular XWiki version.
It would also be nice to have a list of possibly related jira issues or the
actually existing jira for the particular complaint.
Both things should be done automati
Hi,
I have re-read the original thread and scanned the remarks done by Denis
and I have to say that I kind of agree with him on some aspects (or at
least with what I understood from his message since I scanned it quite
quickly).
Basically, I also don`t see much point/value in splitting the code i
Hi,
IMO, we can use the document tree macro to achieve both usecases of the
previous documents and spaces macros, so no need to have more than 1
navigation macro for this.
+1 for (2)
Re (3), we could wait and see how the tree navigation works out and, if
users find that to be easy enough, we cou
Hi,
= Create
+1 for TIL [1]
+1 for 2.B - based on TL, with the mention that the unexpanded view is the
one above, i.e. [1], and, when expanding you get [2] which can then be
further expanded in an advanced mode to [3]. In other words, reverse in 2.B
the position of the breadcrumbs with the tree
On Mon, Aug 10, 2015 at 7:17 PM, Eduard Moraru wrote:
> Hi,
>
> = Create
>
> +1 for TIL
>
Of course, I meant TL, as can be seen from the linked image and further
explanations.
> [1]
>
> +1 for 2.B - based on TL, with the mention that the unexpanded view is the
Hi,
Initially, we wanted to update the administration UI to support nested
spaces and, in particular, to replace the select input for navigating
between space administrations with a tree.
However, it now seems that dropping it completely is a better alternative
and that we could consider the admi
+1
I guess the non-NS and non-blocker issues will be bumped to 7.3M1.
Thanks,
Eduard
On Mon, Aug 24, 2015 at 5:32 PM, Ecaterina Moraru (Valica) <
vali...@gmail.com> wrote:
> +1
>
> Thanks,
> Caty
>
> On Mon, Aug 24, 2015 at 5:08 PM, Thomas Mortagne <
> thomas.morta...@xwiki.com>
> wrote:
>
> >
Hi,
With the latest changes to the create UI [1] we`ve changed (mostly
following the agreed-ish proposal [2]) the old "Page Name" label in the
create UI to "Identifier" because we believed that having both "Page Title"
and "Page Name" on the same page would confuse users and they would not
know wh
We have 2.5 -1s for switching to "Identifier" so the conclusion is that
we`ll continue using "Page Name".
Thanks for the votes and the arguments!
-Eduard
On Wed, Aug 26, 2015 at 11:47 AM, Thomas Mortagne wrote:
> I indeed forgot about XWikiDocument#getId which move my vote to -1.
>
>
> On Wed,
24, 2015 at 8:06 AM, Marius Dumitru Florea <
> > > mariusdumitru.flo...@xwiki.com> wrote:
> > >
> > > > +1
> > > >
> > > > Thanks,
> > > > Marius
> > > >
> > > > On Fri, Aug 21, 2015 at 6:42 PM, Edua
ence, we will still have to
>>>> parse it to create an EntityReference object, and this parser does not
>>>> exist yet.
>>>>
>>>> So what is the benefit?
>>>>
>>>> I only see drawbacks:
>>>> - A JSON reference is a lot mor
+1
The model is Wiki, Space, Document, (Class), Object. It does not make much
(and seems like an arbitrary decision) to consider API for Space, Document,
(Class), Object as core API, but API for wikis to be treated as non-core
and optional.
Yes, we come from a single-wiki initial implementation,
I`m not very familiar with the refactoring module and its contents, but it
feels wrong to have extensions have to depend on it and use it in order to
achieve basic model (CRUD) operations.
Thanks,
Eduard
On Mon, Aug 31, 2015 at 6:54 PM, vinc...@massol.net
wrote:
> Hi,
>
> Right now almost all f
Would this be viewed as an improvement?
Home
|-- Subwikis
| Sub Wiki 1
| Sub Wiki 2
| ...
| Sub Wiki N
|-- Document 1
|-- Document 2
|-- ...
|-- Document N
...same logic we apply for objects, and attachments in a document.
Of course, when displaying the tree only for Sub Wiki X (
adcrumbs, though I am not sure anybody would
want/like to see such an entry in the breadcrumbs of any subwiki document.
Other ideas?
That's all I got right now.
Thanks,
Eduard
On Wed, Sep 2, 2015 at 4:19 PM, Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com> wrote:
> O
>
> On 2 Sep 2015 at 14:49:26, Marius Dumitru Florea (
> mariusdumitru.flo...@xwiki.com(mailto:mariusdumitru.flo...@xwiki.com))
> wrote:
>
> > On Mon, Aug 31, 2015 at 7:26 PM, Eduard Moraru wrote:
> > > I`m not very familiar with the refactoring module and its content
Hi,
You are free to use jQuery in XWiki [1], any other javascript library or
even standard javascript code.
For jQuery, there are tons of tutorials online on how to use a REST
service, like this [2] first result on a quick search or this [3] one (just
scanned them quickly, they will probably do).
+1
Thanks,
Eduard
On Tue, Sep 8, 2015 at 3:10 PM, vinc...@massol.net
wrote:
>
>
>
>
>
> On 8 Sep 2015 at 12:03:49, Marius Dumitru Florea (
> mariusdumitru.flo...@xwiki.com(mailto:mariusdumitru.flo...@xwiki.com))
> wrote:
>
> > On Tue, Sep 8, 2015 at 12:52 PM, vinc...@massol.net wrote:
> > >
> >
Hi,
Yes, "this is not a bug, it's a feature!" :) I had documented it in a small
paragraph [1] (see the note) but did not feel it was worthy to be mentioned
in the release notes. Please feel free to rephrase if needed.
It's not specifically about "Main", but about the current wiki's homepage
(and
Hi,
Again, this is not an XWiki related question, but a generic JavaScript (web
development actually) question on wich there are many articles, tutorials
and forum/stackoverflow answers.
As a quick reply, here's a small javascript that alerts the selected
message:
jQuery(document).on('mouseup',
s,
> Abdulkadar Patel
>
> P.S. : Don't worry, I will not get discouraged but try to learn from
> everything :)
>
>
> -Original Message-
> From: devs [mailto:devs-boun...@xwiki.org] On Behalf Of Eduard Moraru
> Sent: Tuesday, September 15, 2015 7:53 PM
> To:
the new system, I'd
> rather
> > > have *.../xwiki/bin/view/WebHome => **.../xwiki/bin/view/ *would be the
> > > whole wiki. That level would be the top level space (which is exactly
> > what
> > > has been implemented by the way). Do you see what I mean?
(Valica)
Eduard Moraru
Gabriela Smeria
Guillaume Delhumeau
Marius Dumitru Florea
Sergiu Dumitriu
Thomas Mortagne
Vincent Massol
Thanks for your support
-The XWiki dev team
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
+1
Thanks,
Eduard
On Wed, Sep 16, 2015 at 11:36 AM, Guillaume "Louis-Marie" Delhumeau <
gdelhum...@xwiki.com> wrote:
> +1, except that I'm in charge of this release, and I will not be able to
> release it the day after if we are late (I don't work the 25th).
>
> 2015-09-16 10:26 GMT+02:00 Thomas
With the introduction of Nested Spaces / Nested Documents, we find
ourselves having to expand our terminology to accommodate the tree-like
structure of spaces/documents that we are managing.
IMO, we have started going in the wrong direction with using standard tree
terminology directly in XWiki's
r UIs.
Just my concern or maybe I am being too picky, but it probably comes down
to what we want to choose to ignore, as long as it is our intentional
choice to do that.
Thanks,
Eduard
On Thu, Sep 17, 2015 at 3:10 PM, vinc...@massol.net
wrote:
>
>
>
>
>
> On 17 Sep 2015 a
On Thu, Sep 17, 2015 at 3:54 PM, vinc...@massol.net
wrote:
>
>
> On 17 Sep 2015 at 13:32:28, Eduard Moraru (enygma2...@gmail.com(mailto:
> enygma2...@gmail.com)) wrote:
>
> > With the introduction of Nested Spaces / Nested Documents, we find
> > ourselves having t
On Thu, Sep 17, 2015 at 3:59 PM, vinc...@massol.net
wrote:
>
>
>
>
>
> On 17 Sep 2015 at 14:51:32, Eduard Moraru (enygma2...@gmail.com(mailto:
> enygma2...@gmail.com)) wrote:
>
> > IMO the "sibling", "parent", "child", "leaf"
On Thu, Sep 17, 2015 at 12:46 PM, Guillaume Lerouge
wrote:
> Hi Edy,
>
> On Tue, Sep 15, 2015 at 5:10 PM, Eduard Moraru
> wrote:
>
> > Hi Guillaume,
> >
> > You propose a single top level/root document, but no top level space. How
> > does that fit into
Yeah, hoping to end up with one all-mighty solution is probably a not a
healthy objective in this ever changing world of web development frameworks.
For JavaScript I believe we`ve made quite a good choice in integrating with
RequireJS so that we can easily integrate whatever JS framework/library w
+1
Thanks,
Eduard
On Mon, Sep 21, 2015 at 5:03 PM, vinc...@massol.net
wrote:
> Hi devs,
>
> I’d like that we retire the XMLRPC feature of XWiki.
>
> Rationale:
> * We now have a REST API
> * The XMLRPC API is pretty old now, doesn’t support Nested Spaces, see
> http://jira.xwiki.org/browse/XWIK
Hi,
+1 for the planning
+0 for the 7.4 (RC1/final) dates since I`m never in favor of releases
during the winter holidays week.
+1 for restarting the BDFs. I`ll start with tomorrow.
Thanks,
Eduard
On Mon, Sep 28, 2015 at 8:29 AM, Gabriela Smeria
wrote:
> Hello,
>
> I'd like to add XPoll to this
Hi,
IMO, this starts getting overly complicated (when we start making
assumptions). We don`t really need/want to let (or strive to help) the end
user/admin have to decide what he *has* to delete. We need to simplify his
main objectives:
1) delete the data (keep the app)
2) delete the app and data
Hi devs,
Today is BFD#88:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
We've postponed BFDs during the summer because of the large amounts of work
we had on our hands with Nested Spaces / Nested Documents, but since 7.2
was released, it is now a good time to resume.
Our
Results: http://www.xwiki.org/xwiki/bin/view/Blog/Bug+Fixing+Day+88
Thanks for your participation and see you next week!
-Eduard
On Thu, Oct 1, 2015 at 11:13 AM, Eduard Moraru wrote:
> Hi devs,
>
> Today is BFD#88:
> http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HB
Hi devs,
Today is BFD#89:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
Our current status for the 1 year period is 42 bugs behind. See:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=1#Created-vs-Resolved-Chart/10470
Here's the BFD#89 dashboard to follow t
Results: http://www.xwiki.org/xwiki/bin/view/Blog/Bug+Fixing+Day+89
Thanks for participating!
-Eduard
On Thu, Oct 8, 2015 at 11:55 AM, Eduard Moraru wrote:
> Hi devs,
>
> Today is BFD#89:
> http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
>
> Our curren
Hi devs,
Today is BFD#90:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
Our current status for the 1 year period is 41 bugs behind. See:
http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=1#Created-vs-Resolved-Chart/10470
Here's the BFD#90 dashboard to follow t
AFAIR, usecases like these (together with rights management) were the
reason why most of us agreed that page administration is a good thing to
have, in addition to the existing space administration. They might be a bit
cosmeticized now with NS/ND, but the idea should remain the same (2 admin
sectio
Results: http://www.xwiki.org/xwiki/bin/view/Blog/Bug+Fixing+Day+90
Thanks to all the participants!
-Eduard
On Thu, Oct 15, 2015 at 11:46 AM, Eduard Moraru
wrote:
> Hi devs,
>
> Today is BFD#90:
> http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays
>
>
On Fri, Oct 16, 2015 at 12:31 PM, vinc...@massol.net
wrote:
> Of course we also need to think about our IRC bot which has several nice
> features we need to keep. An especially important one IMO is the ability to
> have our logs archived on xwiki.org. Of course the gitter integrations
> are very
+1 to be consistent with the create page picker's "Title" input.
Thanks,
Eduard
On Fri, Oct 16, 2015 at 12:25 PM, Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com> wrote:
> On Fri, Oct 16, 2015 at 12:09 PM, vinc...@massol.net
> wrote:
>
> > Hi Marius,
> >
> > On 16 Oct 2015 at 11:06:22, M
Please allow me to reiterate on the issues of using such terms ("siblings")
in the UI. More specifically, the biggest problems you have are
translations.
For example, in the Romanian language, there is no specific translation for
"sibling", and the word "frate" is used for both "sibling" and "brot
On Tue, Oct 20, 2015 at 4:34 PM, vinc...@massol.net
wrote:
> Hi Edy,
>
> On 20 Oct 2015 at 15:22:51, Eduard Moraru (enygma2...@gmail.com(mailto:
> enygma2...@gmail.com)) wrote:
>
> > Please allow me to reiterate on the issues of using such terms
> ("siblings"
IMO, the App bar is not very reliable nor scalable solution. Sure, it looks
nice in the vanilla distribution because we have a handful of apps, but
once the admin starts installing more, it does not scale. To fix that, the
admin would edit the list of displayed apps and limit it to a smaller set,
b
+1 for extracting it. We currently need this in the administration module,
for the template provider UI.
IMO, xwiki-platform-tree is basically about the tree widget... almost
nothing to do with XWiki's data model. In my eyes, this looks like the
technology, not the domain.
xwiki-platform-index m
Hi,
It would be really nice to get some more feedback on this, since we need it
for 7.3M2 (to fix the failing tests).
Thanks,
Eduard
On Fri, Oct 23, 2015 at 3:31 PM, Eduard Moraru wrote:
> +1 for extracting it. We currently need this in the administration module,
> for the template pr
MT+01:00 Marius Dumitru Florea <
> mariusdumitru.flo...@xwiki.com>:
>
> > On Tue, Oct 27, 2015 at 8:21 AM, Marius Dumitru Florea <
> > mariusdumitru.flo...@xwiki.com> wrote:
> >
> > > On Mon, Oct 26, 2015 at 4:37 PM, Thomas Mortagne <
> > > thomas
Hi,
Sounds nice. A notifications top menu button that, when expanded, would
show the 2 options (to watch the current page or the current page and its
children) and, below those options, we would add (in the coming future)
actual notifications about modified documents that the user is watching.
So
+1
Thanks,
Eduard
On Wed, Oct 28, 2015 at 3:16 PM, vinc...@massol.net
wrote:
> Hi devs,
>
> Some users have raised that when you click on the pencil icon in the
> Create/Delete/Move/Rename UIs, the user has to understand the “dot
> notation” (ie the reference notation) and that it’s not user-fr
e42432d3d7bfb5eebd203bbcc3ec2748
>
> WDYT?
>
> Thanks,
>
>
> 2015-10-29 14:37 GMT+01:00 Marius Dumitru Florea <
> mariusdumitru.flo...@xwiki.com>:
>
> > On Thu, Oct 29, 2015 at 3:31 PM, Eduard Moraru
> > wrote:
> >
> > > Hi,
> > &
Hi,
Here's my input on this...
TL;DR: Don`t rewrite anything and don`t put "affect children" checkboxes
under each option. Simply use a select to redirect from page admin (/admin/
action and XWiki.AdminSheet on the current page) to space admin
(XWiki.AdminSheet on the WebPreferences page, like it
+1, definitely.
Thanks,
Eduard
On Sun, Nov 8, 2015 at 1:49 PM, Thomas Mortagne
wrote:
> +1
>
> On Sat, Nov 7, 2015 at 5:11 PM, vinc...@massol.net
> wrote:
> > Hi devs,
> >
> > As you know our goal is to use myxwiki.org as a real life test platform
> to validate releases of XWiki.
> >
> > Curre
1 - 100 of 1072 matches
Mail list logo
