On Mon, Sep 12, 2016 at 10:54 AM, Vincent Massol <[email protected]> wrote:
> > > On 12 Sep 2016, at 09:43, Thomas Mortagne <[email protected]> > wrote: > > > > On Mon, Sep 12, 2016 at 8:23 AM, Vincent Massol <[email protected]> > wrote: > >> > >>> On 11 Sep 2016, at 20:36, Vincent Massol <[email protected]> wrote: > >>> > >>> Hi devs, > >>> > >>> Status as of 11 Sep 2016: > >>> > >>>> On 17 Aug 2016, at 20:44, Vincent Massol <[email protected]> wrote: > >>>> > >>>> Hi devs, > >>>> > >>>> I’m sorry to be so late to send this email. I thought I had sent it > before going on holidays but apparently I didn’t. Sorry about that. > >>>> > >>>> So here’s the proposal: > >>>> > >>>> * Thomas: > >>>> ** Priority 1: l10n support for nested pages > >>> > >>> Done > >>> > >>>> ** Priority 2: Curated extensions feature in EM (curated extensions > listed + ability to see others if explicitly asked) > >>> > >>> @Thomas: have you started? What’s the status? I hope you’ll have > enough time to deliver something for 8.3. > > > > This one is still tricky since it depends on standardizing at > > Repository application and REST API levels the way to indicate that an > > extension is Recommended. Right now EM simply does not receive any > > information about that. So first we need to finish was is currently > > only an e.x.o. internal thing. > > Yes that’s the point, to bring back what’s currently on e.x.o inside EM. > > What I think would be nice to have in 8.3: > * Bring back what’s on exo into the Repository app > * Introduce a new “recommended” property in EM > * Have a way to see that an extension is recommended in the EM list > (possibly when viewing details only for now) > > WDYT? Doable? > > Another point I was thinking about: If someone starting using the > Repository app, when you don’t have that many extensions, you may not care > about the notion of recommended so I think we’ll need a config option for > the Repository app to enable/disable the recommended view on the home page > (would be off by default). WDYT? > > Thanks > -Vincent > > > ** Priority 3: Fix various existing NS issues (example: office macro on > NP) + continue improving tools > >>>> ** Priority 4: Paying + Trial feature in EM (see that an app is > paying + has a trial and show it) > >>>> > >>>> * Marius: > >>>> ** Priority 1: Fix performance issue in Document Tree + fix "Add > support for sorting the pages by their title in the document tree" at the > same time > >>> > >>> Done > >>> > >>>> ** Priority 2: Fix various existing NS issues (example: office macro > on NP) + continue improving tools. Includes as priority "Viewing a PPT / > ODP with the Office Macro fails when on a nested page” > >>> > >>> @Marius: I know the doc tree took quite longer than planned (M1 + M2). > You also fixed a few issues (see below). Will you have the time to make > some progress on NS stuff? > >> > >> BTW we also have the issue of being able to upgrade the contrib > extensions we bundle in the XE flavor, see http://markmail.org/message/ > mbut2lhatyeu6wzv > >> > >> ATM this issue we’ve unfortunately introduced seems even more important > than other planned things and we need someone to work on it before 8.3RC1. > Who would be ok to work on it? > >> > >> Thanks > >> -Vincent > >> > >>> > >>>> ** Priority 3: Bring back XCS flavors in XE (involves dropping XE and > replacing it with a KB flavor and start using the platform distribution > instead of XE) > >>> > >>> This is actually related to the mail I’ve just sent: > >>> http://markmail.org/message/tutpy6uu2hju233s > >>> > >>>> * Caty: > >>>> ** Priority 1: Complete Templates (set of sample templates (partially > done already) + templates in each App and in AWM) in XE > >>>> ** Priority 2: Demo content extension for XE > >>>> ** Priority 3: Curated extensions feature in EM (curated extensions > listed + ability to see others if explicitly asked) > >>>> ** Priority 4: Mouseflow + Inspectlet analysis for xwiki.org > >>>> ** Priority 5: Task for Usability (investigation) > >>> > >>> @Caty: could you update us on what you’ve done for the 8.3 timeframe > and what’s your status re the various tasks listed above? > >>> > >>> I remember your help on the exo home page, applying the design you did > in the previous period. > >>> > >>>> * Vincent: > >>>> ** Priority 1: Curation of extensions.xwiki.org > >>> > >>> Done > >>> > >>>> ** Priority 2: Playground flavor > >>> > >>> Not done. I had started it in the previous period. I need to continue > it. > >>> > >>>> ** Priority 3: Continue Confluence + MediaWiki comparison pages + > present XWiki as the best Confluence alternative > >>> > >>> Not done > >>> > >>>> ** Priority 4: Improvement to activeinstalls to capture some more > information (email hash for unicity, country, number of users) > >>> > >>> I worked on this and added some new data but it requires upgrading > Elastic Search to a recent version and this is difficult (requires > migrating some data and updating code as APIs/behaviors have changed). > >>> > >>>> * Guillaume: > >>>> ** Priority 1: <internal XWiki SAS work - Infra work for XWiki Cloud > if you’re curious ;)> > >>>> ** Priority 2: Fix various existing NS issues (example: office macro > on NP) + continue improving tools > >>> > >>> @Guillaume: Will you have time to work on NS stuff in this period? > >>> > >>>> * Alex: > >>>> ** Priority 1: <internal XWiki SAS work - prepare one paying app and > setup an XWiki SAS store> > >>>> ** Priority 2: Demo content extension for XE > >>> > >>> The priority 1 is taking much longer than planned (I had 2 weeks max > in my head but I’m always a bit optimistic :)) and from what I see Alex > won’t have time to work on priority 2. @Alex: is that so? > >>> > >>>> ** Priority 3: Fix various existing NS issues (example: office macro > on NP) + continue improving tools > >>>> > >>>> * Edy: > >>>> ** Priority 1: <internal XWiki SAS work - Network work, this is XWiki > SAS’s customer portal: issue tracking, subscriptions, etc> > >>>> ** Priority 2: Complete Templates (set of sample templates (partially > done already) + templates in each App and in AWM) in XE > >>>> ** Priority 3: Fix various existing NS issues (example: office macro > on NP) + continue improving tools > >>> > >>> @Edy: I think I saw some commits related to templates last week. > Anything you’re planning to do for 8.3 in XE? > >>> > >>>> Top JIRA issues to fix: > >>>> * Viewing a PPT / ODP with the Office Macro fails when on a nested > page - XWIKI-11611 > There's an inconsistency here between the issue title and issue key: * "Viewing a PPT / ODP with the Office Macro fails when on a nested page" is http://jira.xwiki.org/browse/XWIKI-13256 (still Open) * XWIKI-11611 is "Presentation Office documents (.ppt & .pptx) aren't displayed with LibreOffice 4.3.0.1+" >>> > >>> Fixed by Marius! > >>> > >>>> * Cannot delete document with many large attachments - XWIKI-8910 > >>> > >>> Not done > >>> > >>>> * Extend "Add Application" UIX with an order parameter - XWIKI-13075 > >>> > >>> Not done > >>> > >>>> * Rename and copy page operations don't update the page title - > XWIKI-12776 > >>> > >>> Fixed by Marius! > >>> > >>>> * Presentation Office documents (.ppt & .pptx) aren't displayed with > LibreOffice 4.3.5.2+ - XWIKI-13256 > >>> > >>> Not done > >>> > >>>> Dates: > >>>> > >>>> * 8.3M1: 22 August 2016 (one more week than usual to account for > Holidays) > >>>> * 8.3M2: 12 Sep 2016 > >>> > >>> This is tomorrow! :) > >>> > >>>> * 8.3RC1: 26 Sep 2016 > >>>> * 8.3final: 10 Oct 2016 > >>>> > >>>> Let me know what you think and reply if you’re interested to > participate to this roadmap and you wish to implement/contribute some other > stuff. > >>> > >>> Please update with your status. > >>> > >>> Thanks > >>> -Vincent > >>> > >>>> > >>>> Thanks > >>>> -Vincent > >>> > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
