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

2016-10-05 Thread Alexandru Cotiuga
Hello devs, This Thursday is BFD#121: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays Our current status for the 1 year period is 54 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=100 00#Created-vs-Resolved-Chart/10470 Here's the BFD#121

Re: [xwiki-devs] [Contrib][BatchImport] Release of batch import application version 1.2

2016-10-05 Thread Anca Luca
The release is done, the new version 1.2 is available on maven and will soon be available on extensions.xwiki.org as well. Anca On Wed, Oct 5, 2016 at 6:04 PM, Anca Luca wrote: > Hello all, > > Alex and I have fixed a couple of issues on the batch import application > (issues

Re: [xwiki-devs] [PROPOSAL] Stabilize filesystem templates rights

2016-10-05 Thread Eduard Moraru
+1 for 1), with the reminder that filesystem templates are considered to be managed/authored by the superadmin, while Skin template overrides will be managed/authored by the Skin document's author, so overriding a template from a skin will not give you superadmin author rights. Thanks, Eduard On

Re: [xwiki-devs] [Proposal] Change of behavior for Applications Panel and app registration in general

2016-10-05 Thread Eduard Moraru
Hi, The only thing I could say about this is that I would also prefer to have the App Panel be configured by an admin exclusively manually (i.e. not having apps added by default, when they are installed). All the installed apps should be listed in the App Panel administration section, and the

[xwiki-devs] [Contrib][BatchImport] Release of batch import application version 1.2

2016-10-05 Thread Anca Luca
Hello all, Alex and I have fixed a couple of issues on the batch import application (issues BATCHIMP-1,2,3,4,5,6) and I would like to release version 1.2 of this application. Functionally, these changes bring translations being properly activated when the app is installed, one more option

Re: [xwiki-devs] [Proposal] Change of behavior for Applications Panel and app registration in general

2016-10-05 Thread Ecaterina Moraru (Valica)
On Wed, Oct 5, 2016 at 1:35 PM, Vincent Massol wrote: > > > On 05 Oct 2016, at 12:08, Ecaterina Moraru (Valica) > wrote: > > > > On Wed, Oct 5, 2016 at 12:37 PM, Vincent Massol > wrote: > > > >> Hi devs, > >> > >> With the recent

Re: [xwiki-devs] [Proposal] Change of behavior for Applications Panel and app registration in general

2016-10-05 Thread Ecaterina Moraru (Valica)
On Wed, Oct 5, 2016 at 5:47 PM, Ecaterina Moraru (Valica) wrote: > > > On Wed, Oct 5, 2016 at 1:35 PM, Vincent Massol wrote: > >> >> > On 05 Oct 2016, at 12:08, Ecaterina Moraru (Valica) >> wrote: >> > >> > On Wed, Oct 5, 2016 at 12:37

Re: [xwiki-devs] [Proposal] Change of behavior for Applications Panel and app registration in general

2016-10-05 Thread Vincent Massol
> On 05 Oct 2016, at 12:08, Ecaterina Moraru (Valica) wrote: > > On Wed, Oct 5, 2016 at 12:37 PM, Vincent Massol wrote: > >> Hi devs, >> >> With the recent introduction of the Applications Index (see >>

Re: [xwiki-devs] [Proposal] Change of behavior for Applications Panel and app registration in general

2016-10-05 Thread Ecaterina Moraru (Valica)
On Wed, Oct 5, 2016 at 12:37 PM, Vincent Massol wrote: > Hi devs, > > With the recent introduction of the Applications Index (see > http://extensions.xwiki.org/xwiki/bin/view/Extension/ > Application+Index+Application/) we need to agree on a few things. > > In the past we

[xwiki-devs] [Proposal] Change of behavior for Applications Panel and app registration in general

2016-10-05 Thread Vincent Massol
Hi devs, With the recent introduction of the Applications Index (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Application+Index+Application/) we need to agree on a few things. In the past we had: * We wanted all new app that you installed to automatically be visible in the

[xwiki-devs] [PROPOSAL] Stabilize filesystem templates rights

2016-10-05 Thread Thomas Mortagne
Hi devs, Right now (and since forever) the default behavior for templates is to be executed with the right of the current document content author (it's not really explicit, it's just how PR works when there is no sdoc). This means that unless you explicitly indicate an author for your template