[xwiki-devs] [Proposal] Curation process for extensions on e.x.o
Hi devs, We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. P2) It’s hard for users to locate good extensions among the rest. We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. Proposal ======= I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. Then we need to decide about the curation process: * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. WDYT? I’m willing to help do the work and mark extensions as recommended. Thanks -Vincent
+1 for the curation in general but I'm not a big fan of your proposal of displaying only recommended extensions by default in EM (90% of the users won't change the filter and will find very few extensions). We could make recommended extensions listed first when you have empty search input instead and highlight them some way in the extension displayer (like some validation icon, a different color, etc.). On Mon, May 23, 2016 at 10:39 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 Thanks, Caty On Mon, May 23, 2016 at 11:58 AM, Thomas Mortagne <[email protected]
wrote:
+1 for the curation in general but I'm not a big fan of your proposal of displaying only recommended extensions by default in EM (90% of the users won't change the filter and will find very few extensions). We could make recommended extensions listed first when you have empty search input instead and highlight them some way in the extension displayer (like some validation icon, a different color, etc.).
On Mon, May 23, 2016 at 10:39 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 for curation as I agree it fits better our size, but on the long run the ratings need to improve so that, at some point, it can take over most of the curation effort. Thanks, Eduard On Mon, May 23, 2016 at 12:19 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
+1
Thanks, Caty
On Mon, May 23, 2016 at 11:58 AM, Thomas Mortagne < [email protected]
wrote:
+1 for the curation in general but I'm not a big fan of your proposal of displaying only recommended extensions by default in EM (90% of the users won't change the filter and will find very few extensions). We could make recommended extensions listed first when you have empty search input instead and highlight them some way in the extension displayer (like some validation icon, a different color, etc.).
On Mon, May 23, 2016 at 10:39 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on
http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac... .
Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 for the idea, and +1 for the Thomas' remarks. 2016-05-23 11:38 GMT+02:00 Eduard Moraru <[email protected]>:
+1 for curation as I agree it fits better our size, but on the long run the ratings need to improve so that, at some point, it can take over most of the curation effort.
Thanks, Eduard
On Mon, May 23, 2016 at 12:19 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
+1
Thanks, Caty
On Mon, May 23, 2016 at 11:58 AM, Thomas Mortagne < [email protected]
wrote:
+1 for the curation in general but I'm not a big fan of your proposal of displaying only recommended extensions by default in EM (90% of the users won't change the filter and will find very few extensions). We could make recommended extensions listed first when you have empty search input instead and highlight them some way in the extension displayer (like some validation icon, a different color, etc.).
On Mon, May 23, 2016 at 10:39 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on
http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac...
.
Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project
On Mon, May 23, 2016 at 11:58 AM, Thomas Mortagne <[email protected]
wrote:
+1 for the curation in general but I'm not a big fan of your proposal of displaying only recommended extensions by default in EM (90% of the users won't change the filter and will find very few extensions). We could make recommended extensions listed first when you have empty search input instead and highlight them some way in the extension displayer (like some validation icon, a different color, etc.).
A "Recommended Extensions" filter (to show *only* recommended extensions) makes sense, but as Thomas said, I wouldn't select it by default (at least for now, as we won't have that many recommended extensions at the beginning). I would display all extensions by default, making sure that recommended extensions are given priority by the search (boost factor). +1 for curation otherwise. Thanks, Marius
On Mon, May 23, 2016 at 10:39 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject). The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q I’m starting the work. Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
ok I’ve started. 3 things: * I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them. - http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen... - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier Thanks -Vincent The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
On 18/08/16 21:00, Vincent Massol wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/
- http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/
experimental
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen...
middleware, not something people should see
- http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor
- http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube
experimental Thanks, Caleb
- http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Aug 18, 2016 at 10:00 PM, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ Recent+Blog+Entries+Macros/ ?
- needs cleaning
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ SunkenFlamingoTheme/
- I wouldn't recommend themes, if we like it we could replace the default (also in the future we should reduce the number of bundled themes) Thanks, Caty
- http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Suggest+LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let% 27s+Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+ Analyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+ Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+ Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Trusted+authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ ApplicationDevelopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Caty,
On 19 Aug 2016, at 09:08, Ecaterina Moraru (Valica) <[email protected]> wrote:
On Thu, Aug 18, 2016 at 10:00 PM, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ Recent+Blog+Entries+Macros/ ?
- needs cleaning
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ SunkenFlamingoTheme/
- I wouldn't recommend themes,
Why not? I have the opposite feeling: we should develop a lot more themes and make them available and visible. A downside of XWiki has always been the poorness of skins/themes compared to other softwares such as wordpress. Skins are hard to develop but that’s not the case for themes.
if we like it we could replace the default (also in the future we should reduce the number of bundled themes)
I’m not sure about this one either. Letting the user find them and install them is hard and requires knowledge. I’d prefer that we keep bundling a pack of themes in the Default/KB/XE flavor. Thanks -Vincent
Thanks, Caty
- http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Suggest+LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let% 27s+Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+ Analyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+ Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+ Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Trusted+authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ ApplicationDevelopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
On Thu, Aug 18, 2016 at 9:00 PM, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen... - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support...
This one will probably end up in XE in not too long anyway.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API?
No need to recommend this one for final users IMO, it's only supposed to be used as a dependency since it's mostly a script service.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier
You should also recommend http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Authenticator+Tru... (until I find time to merge it with http://extensions.xwiki.org/xwiki/bin/view/Extension/LDAP/Authenticator/).
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On 19 Aug 2016, at 09:58, Thomas Mortagne <[email protected]> wrote:
On Thu, Aug 18, 2016 at 9:00 PM, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen... - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support...
This one will probably end up in XE in not too long anyway.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API?
No need to recommend this one for final users IMO, it's only supposed to be used as a dependency since it's mostly a script service.
So we need to set up a rule on this: A) Do we want Recommended extensions to be only for users and not for devs? For example: http://extensions.xwiki.org/xwiki/bin/view/Extension/JIRA+Module (it’s not used as any dependency of any other module) My opinion: it’s ok not to list them we should only recommended end user extensions (i.e. for users & for admins but not for devs). B) When we have extensions that are installed as dependencies of other recommended extensions should we not list them? For example, I’ve recommended http://extensions.xwiki.org/xwiki/bin/view/Extension/JIRA+Administration/ but it’s a dependency of http://extensions.xwiki.org/xwiki/bin/view/Extension/JIRA+Macro My opinion: it’s ok not to list extensions that are dependencies of recommended extensions, *unless* there are use cases for using them directly. WDTR? Thanks -Vincent
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier
You should also recommend http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Authenticator+Tru... (until I find time to merge it with http://extensions.xwiki.org/xwiki/bin/view/Extension/LDAP/Authenticator/).
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
On 19 Aug 2016, at 11:28, Vincent Massol <[email protected]> wrote:
On 19 Aug 2016, at 09:58, Thomas Mortagne <[email protected]> wrote:
On Thu, Aug 18, 2016 at 9:00 PM, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen... - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support...
This one will probably end up in XE in not too long anyway.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API?
No need to recommend this one for final users IMO, it's only supposed to be used as a dependency since it's mostly a script service.
So we need to set up a rule on this:
A) Do we want Recommended extensions to be only for users and not for devs?
For example: http://extensions.xwiki.org/xwiki/bin/view/Extension/JIRA+Module (it’s not used as any dependency of any other module)
My opinion: it’s ok not to list them we should only recommended end user extensions (i.e. for users & for admins but not for devs).
B) When we have extensions that are installed as dependencies of other recommended extensions should we not list them?
For example, I’ve recommended http://extensions.xwiki.org/xwiki/bin/view/Extension/JIRA+Administration/ but it’s a dependency of http://extensions.xwiki.org/xwiki/bin/view/Extension/JIRA+Macro
My opinion: it’s ok not to list extensions that are dependencies of recommended extensions, *unless* there are use cases for using them directly.
WDTR?
s/WDTR/WDYT/ :) I’ve updated http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... FTM, I’ll change if we don’t agree about the proposal on points A and B. Thanks -Vincent
Thanks -Vincent
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier
You should also recommend http://extensions.xwiki.org/xwiki/bin/view/Extension/XWiki+Authenticator+Tru... (until I find time to merge it with http://extensions.xwiki.org/xwiki/bin/view/Extension/LDAP/Authenticator/).
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing). Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen... - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Latest news: * I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti...). Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti...
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti...
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+Blog+Entries+Mac... ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Fronte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtime+Netflux+Backen... - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest+LiveTable+Filte... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s+Encrypt+support... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Analyzer+Applicati... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+Adminis... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+Authent... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+authentication+... - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)" extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+Application to be not very complex. Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+messages+applicat... - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app? Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion) "Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc. Thanks, Caty On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/ xwiki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ Recent+Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Suggest+LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let% 27s+Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+ Analyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+ Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+ Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+ Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Trusted+authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ ApplicationDevelopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
How does an extensions looses it's "Recommended" status? Thanks, Caty On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/ Notes+Application to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Flash+messages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+ Listeners+Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
One difference between Recommended and Supported could be that "it's demonstrating an advanced use case build on top of XWiki and user's installing it could see the power/benefits of XWiki". Unfortunately even this "definition" is subjective. So my big problem is that I don't really understand how to say if an extension is recommended or not, and how this status is evolving/deprecating a particular extension over time. Thanks, Caty On Mon, Aug 29, 2016 at 6:17 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
How does an extensions looses it's "Recommended" status?
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+ Application to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+ messages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+L isteners+Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote: > > Hi devs, > > We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: > > P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. > > P2) It’s hard for users to locate good extensions among the rest. > > We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. > > Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. > > Proposal > ======= > > I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. > > I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. > > Then we need to decide about the curation process: > > * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. > * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). > * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): > - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) > - Need to present a polished aspect and be easily usable > - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. > > WDYT? > > I’m willing to help do the work and mark extensions as recommended. > > Thanks > -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
should "ratings" or "active installs" be part of the Recommended definition? Thanks, Caty On Mon, Aug 29, 2016 at 6:27 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
One difference between Recommended and Supported could be that "it's demonstrating an advanced use case build on top of XWiki and user's installing it could see the power/benefits of XWiki". Unfortunately even this "definition" is subjective.
So my big problem is that I don't really understand how to say if an extension is recommended or not, and how this status is evolving/deprecating a particular extension over time.
Thanks, Caty
On Mon, Aug 29, 2016 at 6:17 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
How does an extensions looses it's "Recommended" status?
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+A pplication to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+m essages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+L isteners+Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdi t+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier
Thanks -Vincent
The result is here:
> On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote: > > I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject). > > The idea is to implement something similar to what Caty proposed at > http://markmail.org/message/cr5edm27qcag6n3q > > I’m starting the work. > > Thanks > -Vincent > > >> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote: >> >> Hi devs, >> >> We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: >> >> P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. >> >> P2) It’s hard for users to locate good extensions among the rest. >> >> We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. >> >> Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. >> >> Proposal >> ======= >> >> I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. >> >> I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. >> >> Then we need to decide about the curation process: >> >> * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. >> * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). >> * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): >> - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) >> - Need to present a polished aspect and be easily usable >> - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. >> >> WDYT? >> >> I’m willing to help do the work and mark extensions as recommended. >> >> Thanks >> -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 29 Aug 2016, at 17:29, Ecaterina Moraru (Valica) <[email protected]> wrote:
should "ratings" or "active installs" be part of the Recommended definition?
Re http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+Application I may have missed it. How do you use it? (the doc is not clear). Does it have an admin UI section for configuring it? How do you enable it for a given space only for example? Re Active Installs I haven’t put since I don’t see why we would recommend it. It’s only useful for xwiki.org IMO. Thanks -Vincent
Thanks, Caty
On Mon, Aug 29, 2016 at 6:27 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
One difference between Recommended and Supported could be that "it's demonstrating an advanced use case build on top of XWiki and user's installing it could see the power/benefits of XWiki". Unfortunately even this "definition" is subjective.
So my big problem is that I don't really understand how to say if an extension is recommended or not, and how this status is evolving/deprecating a particular extension over time.
Thanks, Caty
On Mon, Aug 29, 2016 at 6:17 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
How does an extensions looses it's "Recommended" status?
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+A pplication to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+m essages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
> On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote: > > ok I’ve started. > > 3 things: > > * I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ > * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ > * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them. > > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? > - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+L isteners+Administration/ > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? > - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdi t+Macro > - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor > - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube > - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! > - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier > > Thanks > -Vincent > > The result is here: > >> On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote: >> >> I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject). >> >> The idea is to implement something similar to what Caty proposed at >> http://markmail.org/message/cr5edm27qcag6n3q >> >> I’m starting the work. >> >> Thanks >> -Vincent >> >> >>> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote: >>> >>> Hi devs, >>> >>> We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: >>> >>> P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. >>> >>> P2) It’s hard for users to locate good extensions among the rest. >>> >>> We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. >>> >>> Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. >>> >>> Proposal >>> ======= >>> >>> I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. >>> >>> I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. >>> >>> Then we need to decide about the curation process: >>> >>> * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. >>> * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). >>> * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): >>> - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) >>> - Need to present a polished aspect and be easily usable >>> - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. >>> >>> WDYT? >>> >>> I’m willing to help do the work and mark extensions as recommended. >>> >>> 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
On Mon, Aug 29, 2016 at 6:39 PM, Vincent Massol <[email protected]> wrote:
On 29 Aug 2016, at 17:29, Ecaterina Moraru (Valica) <[email protected]> wrote:
should "ratings" or "active installs" be part of the Recommended definition?
Actually my question was: in the recommended definition should we have a threshold for a value of extension's rating or active installs count in order to be recommended? For example: diagram app has 88 active installs, but no rating, etc. We could decide what is recommended based on a count of active installs > 50 and an average rating > 3, for example. This way we could automate the recommended process and also it would encourage extension authors to rate their extensions, while seeing how used the extensions are. Thanks, Caty
Re http://extensions.xwiki.org/xwiki/bin/view/Extension/ Ratings+Application I may have missed it. How do you use it? (the doc is not clear).
Does it have an admin UI section for configuring it? How do you enable it for a given space only for example?
Re Active Installs I haven’t put since I don’t see why we would recommend it. It’s only useful for xwiki.org IMO.
Thanks -Vincent
Thanks, Caty
On Mon, Aug 29, 2016 at 6:27 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
One difference between Recommended and Supported could be that "it's demonstrating an advanced use case build on top of XWiki and user's installing it could see the power/benefits of XWiki". Unfortunately even this "definition" is subjective.
So my big problem is that I don't really understand how to say if an extension is recommended or not, and how this status is evolving/deprecating a particular extension over time.
Thanks, Caty
On Mon, Aug 29, 2016 at 6:17 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
How does an extensions looses it's "Recommended" status?
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+A pplication to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+m essages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/ TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
> On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote: > > I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): > http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection > > Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing). > > Note that for an app to be recommended it must follow the rules defined on > http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension > > Thanks > -Vincent > >> On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote: >> >> ok I’ve started. >> >> 3 things: >> >> * I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ >> * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ >> * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them. >> >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+L isteners+Administration/ >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdi t+Macro >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! >> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier >> >> Thanks >> -Vincent >> >> The result is here: >> >>> On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote: >>> >>> I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject). >>> >>> The idea is to implement something similar to what Caty proposed at >>> http://markmail.org/message/cr5edm27qcag6n3q >>> >>> I’m starting the work. >>> >>> Thanks >>> -Vincent >>> >>> >>>> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote: >>>> >>>> Hi devs, >>>> >>>> We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: >>>> >>>> P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. >>>> >>>> P2) It’s hard for users to locate good extensions among the rest. >>>> >>>> We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. >>>> >>>> Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. >>>> >>>> Proposal >>>> ======= >>>> >>>> I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. >>>> >>>> I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. >>>> >>>> Then we need to decide about the curation process: >>>> >>>> * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. >>>> * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). >>>> * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): >>>> - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) >>>> - Need to present a polished aspect and be easily usable >>>> - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. >>>> >>>> WDYT? >>>> >>>> I’m willing to help do the work and mark extensions as recommended. >>>> >>>> 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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 29 Aug 2016, at 18:09, Ecaterina Moraru (Valica) <[email protected]> wrote:
On Mon, Aug 29, 2016 at 6:39 PM, Vincent Massol <[email protected]> wrote:
On 29 Aug 2016, at 17:29, Ecaterina Moraru (Valica) <[email protected]> wrote:
should "ratings" or "active installs" be part of the Recommended definition?
Actually my question was: in the recommended definition should we have a threshold for a value of extension's rating or active installs count in order to be recommended? For example: diagram app has 88 active installs, but no rating, etc. We could decide what is recommended based on a count of active installs > 50 and an average rating > 3, for example. This way we could automate the recommended process and also it would encourage extension authors to rate their extensions, while seeing how used the extensions are.
I don’t think we can automate it. And I wouldn’t even try. Re ratings, the main point of Recommended is because ratings doesn’t work :) On http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... there are extensions with low count and other with high values. Note that it wouldn’t work either in the some cases as for the Stats app which we’ve removed from the core and retire because it’s not good enough (it has a high number of installs because it was bundled ;)). Thanks -Vincent
Thanks, Caty
Re http://extensions.xwiki.org/xwiki/bin/view/Extension/ Ratings+Application I may have missed it. How do you use it? (the doc is not clear).
Does it have an admin UI section for configuring it? How do you enable it for a given space only for example?
Re Active Installs I haven’t put since I don’t see why we would recommend it. It’s only useful for xwiki.org IMO.
Thanks -Vincent
Thanks, Caty
On Mon, Aug 29, 2016 at 6:27 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
One difference between Recommended and Supported could be that "it's demonstrating an advanced use case build on top of XWiki and user's installing it could see the power/benefits of XWiki". Unfortunately even this "definition" is subjective.
So my big problem is that I don't really understand how to say if an extension is recommended or not, and how this status is evolving/deprecating a particular extension over time.
Thanks, Caty
On Mon, Aug 29, 2016 at 6:17 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
How does an extensions looses it's "Recommended" status?
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+A pplication to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+m essages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/ TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
> Latest news: > > * I’ve finished reviewing all extensions on e.x.o > * The list of extensions that I consider recommended (there are 26 as > of now) is available at http://extensions.xwiki.org/xw > iki/bin/view/ExtensionCode/RecommendedExtensions/ > * There are some extensions that I don’t know well enough to know if > they could be recommended (not sure if they have active support, how well > they work on latest XE, etc): http://design.xwiki.org/xwiki/ > bin/view/Proposal/RecommendedExtensionsSelection > > To @Extension creators: please review the list and let me know if you > have some extensions that you’d like recommended (make sure to check the > criteria defined at http://design.xwiki.org/xwiki/ > bin/view/Proposal/RecommendedExtensionsSelection). > > Next steps: > * Modify the extension sheet to visually see when an extension is > recommended > * Modify the e.x.o home page to highlight Recommended Extension (see > http://markmail.org/message/cr5edm27qcag6n3q ) > * Modify EM to add the notion of Recommended > * Merge back the new Recommended field in the Repository Application > > Thanks > -Vincent > >> On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote: >> >> I’ve started a wiki page to track which extensions we’re not sure > about (whether they should be recommended or not): >> http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE > xtensionsSelection >> >> Please edit it if you have opinion/knowledge about them (or reply on > this thread and I’ll do the syncing). >> >> Note that for an app to be recommended it must follow the rules > defined on >> http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE > xtensionsSelection#HWhatisaRecommendedExtension >> >> Thanks >> -Vincent >> >>> On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote: >>> >>> ok I’ve started. >>> >>> 3 things: >>> >>> * I’ve started defining what we mean by a recommended app, see > http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec > ommendedExtensions/ >>> * I’ve processed the first 2 pages of the LT on the home page of > e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so > far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec > ommendedExtensions/ >>> * I’m hesitating for the following extensions. Specifically I need > to know what their authors think and whether they’re ok to support them > actively. I also don’t know them enough to know of their quality. Feel free > to comment on them. >>> >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ > Blog+Entries+Macros/ ? >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF > lamingoTheme/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim > e+Netflux+Frontend/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim > e+Netflux+Backend/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi > on+Macro/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest > +LiveTable+Filter+Macro/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s > +Encrypt+support/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela > s+Script+Runner/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An > alyzer+Application/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+L > isteners+Administration/ >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ > Script+API Note: we will expose the filter app, should we also expose > the API? >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdi > t+Macro >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras > terizing+API >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted > +Headers+Authentication+Adapter >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted > +authentication+framework >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad > dress+encryptor >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav > en+Plugin Note: wrong author!!! >>> - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ > UI+Simplifier >>> >>> Thanks >>> -Vincent >>> >>> The result is here: >>> >>>> On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> > wrote: >>>> >>>> I’m starting the work on this. BTW several of you have replied > about EM but this mail was only for “e.x.o” FTM (see the subject). >>>> >>>> The idea is to implement something similar to what Caty proposed at >>>> http://markmail.org/message/cr5edm27qcag6n3q >>>> >>>> I’m starting the work. >>>> >>>> Thanks >>>> -Vincent >>>> >>>> >>>>> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> > wrote: >>>>> >>>>> Hi devs, >>>>> >>>>> We have a lot of entries on extensions.xwiki.org (869 as of > today) and this causes some problems for our users: >>>>> >>>>> P1) A lot of them are not of good quality (they don’t work with > the latest versions, they are complex to use, they’ve not been updated for > a long time and are doing old and deprecated ways of doing things such as > not providing an entry in the Applications Panel for example, they’re not > just polished, etc) and this causes frustrations for our users. Note that > this also reflects on the overall quality of the XWiki project and product. >>>>> >>>>> P2) It’s hard for users to locate good extensions among the rest. >>>>> >>>>> We’ve started addressing P1) by introducing ratings on e.x.o. This > is not fully successful so far because we don’t have enough people voting > and because those ratings are not used to display/filter extensions on the > Extensions LT or inside XWiki in the EM UI. So we need to continue this > effort. >>>>> >>>>> Note that this proposal is not addressing non-extensions such as > snippets which we’ll need to move elsewhere at some point but that becomes > less important with the proposal below. >>>>> >>>>> Proposal >>>>> ======= >>>>> >>>>> I’d like to propose an additional strategy that, IMO, is better > suited for the size of our community: curation. Curation is the process of > hand-selecting the best extensions and marking them as recommended. The > idea would be to list recommended extensions first on the e.x.o home page, > in the EM UI in XWiki and even in extension search results. In the EM UI, > an idea would also be to have a new “Recommended Extensions” filter in > addition to the existing filters (core extensions, installed extensions, > etc) and that would be the default filter on the “Add Extensions” UI. >>>>> >>>>> I propose to add a “Recommended” xproperty in the Repository app > for that. We can decide whether we want this just for e.x.o or committed in > the Repository app in xwiki-platform. >>>>> >>>>> Then we need to decide about the curation process: >>>>> >>>>> * The XWiki core committers are in charge (i.e. have the > responsibility) of monitoring the apps that are marked “Recommended”, ie. > validating that it’s done correctly. XWiki core committers have the > authorization to unset an app that was marked a recommended by a community > member. >>>>> * We wouldn’t offer a simple way in the UI to mark an extension as > recommended since we don’t want everyone who has an account on > xwiki.org to start marking apps as recommended. OTOH we want to allow > people from the xwiki community to help out. So the way to mark an > extension as recommended would be to use the object editor (for now, we can > define a better implementation mechanism later on). >>>>> * We define some basic rules that extensions need to follow at > minimum to be accepted as recommended. These will be our guidelines to > avoid conflict of opinions (although there’s always the possibility in > which case it’s resolved through a vote): >>>>> - Need to work on LTS + latest XWiki version (ie. ATM that would > be 7.4.x and 8.1) >>>>> - Need to present a polished aspect and be easily usable >>>>> - Need to follow most of the best practices defined on > http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev > elopmentBestPractices. Some important examples: technical pages are > hidden, extension is registered in the app bar when it makes sense, > extension is internationalized (if it makes sense), pages are in xwiki > syntax 2.0+. >>>>> >>>>> WDYT? >>>>> >>>>> I’m willing to help do the work and mark extensions as recommended. >>>>> >>>>> 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
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 29 Aug 2016, at 17:27, Ecaterina Moraru (Valica) <[email protected]> wrote:
One difference between Recommended and Supported could be that "it's demonstrating an advanced use case build on top of XWiki and user's installing it could see the power/benefits of XWiki". Unfortunately even this "definition" is subjective.
So my big problem is that I don't really understand how to say if an extension is recommended or not, and how this status is evolving/deprecating a particular extension over time.
I don’t understand what’s the issue with http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... Could you be specific? Thanks -Vincent
Thanks, Caty
On Mon, Aug 29, 2016 at 6:17 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
How does an extensions looses it's "Recommended" status?
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+ Application to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+ messages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+L isteners+Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier
Thanks -Vincent
The result is here:
> On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote: > > I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject). > > The idea is to implement something similar to what Caty proposed at > http://markmail.org/message/cr5edm27qcag6n3q > > I’m starting the work. > > Thanks > -Vincent > > >> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote: >> >> Hi devs, >> >> We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: >> >> P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. >> >> P2) It’s hard for users to locate good extensions among the rest. >> >> We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. >> >> Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. >> >> Proposal >> ======= >> >> I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. >> >> I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. >> >> Then we need to decide about the curation process: >> >> * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. >> * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). >> * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): >> - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) >> - Need to present a polished aspect and be easily usable >> - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. >> >> WDYT? >> >> I’m willing to help do the work and mark extensions as recommended. >> >> 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
On 29 Aug 2016, at 17:17, Ecaterina Moraru (Valica) <[email protected]> wrote:
How does an extensions looses it's "Recommended" status?
When it doesn’t obey http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... Thanks -Vincent
Thanks, Caty
On Mon, Aug 29, 2016 at 6:16 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/ Notes+Application to be not very complex.
Missing: - Blog (which is currently bundled) - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Flash+messages+application - http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting - what about Repository app?
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)? What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are? What is the difference between supported and recommended? Is it documented somewhere? Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies? And in this category we have some macros: fullcalendar, pdfviewer, etc.
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/xw iki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/ bin/view/Proposal/RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedE xtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/Rec ommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Recent+ Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/SunkenF lamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Realtim e+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Conditi on+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Suggest +LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let%27s +Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Derzela s+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+An alyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+ Listeners+Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Filter+ Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+Ras terizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +Headers+Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted +authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ad dress+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Mav en+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/Rights+ UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
> On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote: > > Hi devs, > > We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users: > > P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product. > > P2) It’s hard for users to locate good extensions among the rest. > > We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort. > > Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below. > > Proposal > ======= > > I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI. > > I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform. > > Then we need to decide about the curation process: > > * The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. > * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). > * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): > - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) > - Need to present a polished aspect and be easily usable > - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDev elopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+. > > WDYT? > > I’m willing to help do the work and mark extensions as recommended. > > 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
Hi Caty,
On 29 Aug 2016, at 17:16, Ecaterina Moraru (Valica) <[email protected]> wrote:
"Not a core Extension (i.e. not bundled by default in the base XWiki Distribution)"
extensions.xwiki.org/xwiki/bin/view/Extension/Templates+Application/ is bundled extensions.xwiki.org/xwiki/bin/view/Extension/Tour+Application is bundled extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration is bundled
They’re not in the base distribution because they’re not core extensions. That’s why they’re listed. The idea is that we’ll have several flavors. They are in the XE flavor ATM (but not in the base distribution).
I find http://extensions.xwiki.org/xwiki/bin/view/Extension/Notes+Application to be not very complex.
Missing: - Blog (which is currently bundled)
It’s bundled (part of the base distribution right now). When we move it out in contrib we should add it as recommended.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/Flash+messages+applicat...
It’s not missed. I listed it and asked about it, see http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti...
- http://extensions.xwiki.org/xwiki/bin/view/Extension/TotemApplication was also interesting
It’s not missed. I listed it and asked about it, see http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... Does someone support it actively? Is it following best practices?
- what about Repository app?
Good question. I think I missed it because it’s from the xwiki dev team. It seems ok to put it there IMO even though it’s a niche app.
Do we also provide a way for users to filter what apps are bundled (and maybe implicitely supported/recommended)?
Right now no, my proposal is about not listing core extensions.
What about extensions that have "XWiki Development Team" as author? Are they implicitly supported/recommended? Is there a way to filter and see what they are?
Doesn’t matter who’s the author for Recommended.
What is the difference between supported and recommended?
That’s already defined here: http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti...
Is it documented somewhere?
Yes: http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti...
Should the users care about this difference? (maybe the answers are found above in the thread, but I don't remember any conclusion)
Not really. We can decide if we want to show http://design.xwiki.org/xwiki/bin/view/Proposal/RecommendedExtensionsSelecti... on e.x.o somewhere (a link to a definition). IMO we should once we’ve finished the process.
"Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly." This means we don't support the apps dependencies?
Not sure what this means… Is "Don't recommend extensions that are installed as dependencies of other recommended extensions, unless there are end-user use cases for using them directly.” not clear?
And in this category we have some macros: fullcalendar, pdfviewer, etc.
I hesitated for the “fullcalendar macro” since it can also be used standalone but I considered that the use case of having a calendar was better covered by the Mocca Calendar app for users. I’m ok to add “fullcalendar macro” if we think it’s better to also have it. Re PDF Viewer, it’s in my question list (don’t know it well enough). Thanks -Vincent
Thanks, Caty
On Mon, Aug 29, 2016 at 5:44 PM, Vincent Massol <[email protected]> wrote:
Latest news:
* I’ve finished reviewing all extensions on e.x.o * The list of extensions that I consider recommended (there are 26 as of now) is available at http://extensions.xwiki.org/ xwiki/bin/view/ExtensionCode/RecommendedExtensions/ * There are some extensions that I don’t know well enough to know if they could be recommended (not sure if they have active support, how well they work on latest XE, etc): http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection
To @Extension creators: please review the list and let me know if you have some extensions that you’d like recommended (make sure to check the criteria defined at http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection).
Next steps: * Modify the extension sheet to visually see when an extension is recommended * Modify the e.x.o home page to highlight Recommended Extension (see http://markmail.org/message/cr5edm27qcag6n3q ) * Modify EM to add the notion of Recommended * Merge back the new Recommended field in the Repository Application
Thanks -Vincent
On 22 Aug 2016, at 11:20, Vincent Massol <[email protected]> wrote:
I’ve started a wiki page to track which extensions we’re not sure about (whether they should be recommended or not): http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection
Please edit it if you have opinion/knowledge about them (or reply on this thread and I’ll do the syncing).
Note that for an app to be recommended it must follow the rules defined on http://design.xwiki.org/xwiki/bin/view/Proposal/ RecommendedExtensionsSelection#HWhatisaRecommendedExtension
Thanks -Vincent
On 18 Aug 2016, at 21:00, Vincent Massol <[email protected]> wrote:
ok I’ve started.
3 things:
* I’ve started defining what we mean by a recommended app, see http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’ve processed the first 2 pages of the LT on the home page of e.x.o. (ie the first 60 extensions) and I’ve marked 11 as recommended so far: http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/ * I’m hesitating for the following extensions. Specifically I need to know what their authors think and whether they’re ok to support them actively. I also don’t know them enough to know of their quality. Feel free to comment on them.
- http://extensions.xwiki.org/xwiki/bin/view/Extension/ Recent+Blog+Entries+Macros/ ? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ SunkenFlamingoTheme/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/RtForm/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Frontend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Realtime+Netflux+Backend/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XQuiz/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Condition+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Suggest+LiveTable+Filter+Macro/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Let% 27s+Encrypt+support/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Derzelas+Script+Runner/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/XCarousel/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+ Analyzer+Application/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/Event+Listeners+ Administration/ - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Filter+Script+API Note: we will expose the filter app, should we also expose the API? - http://extensions.xwiki.org/xwiki/bin/view/Extension/ZoneEdit+Macro - http://extensions.xwiki.org/xwiki/bin/view/Extension/SVG+ Rasterizing+API - http://extensions.xwiki.org/xwiki/bin/view/Extension/Trusted+Headers+ Authentication+Adapter - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Trusted+authentication+framework - http://extensions.xwiki.org/xwiki/bin/view/Extension/Mail+ address+encryptor - http://extensions.xwiki.org/xwiki/bin/view/Extension/XWikiTube - http://extensions.xwiki.org/xwiki/bin/view/Extension/XFF+Maven+Plugin Note: wrong author!!! - http://extensions.xwiki.org/xwiki/bin/view/Extension/ Rights+UI+Simplifier
Thanks -Vincent
The result is here:
On 18 Aug 2016, at 19:36, Vincent Massol <[email protected]> wrote:
I’m starting the work on this. BTW several of you have replied about EM but this mail was only for “e.x.o” FTM (see the subject).
The idea is to implement something similar to what Caty proposed at http://markmail.org/message/cr5edm27qcag6n3q
I’m starting the work.
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ ApplicationDevelopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
Update: we now have 29 recommended extensions on http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/RecommendedExtensio... I think it’s a good start and I’m going to work with Caty to make it visible on the home page of e.x.o. Please reply quickly if you don’t agree :) Then we can iterate if you think some other extensions should be recommended. In term of process, for now, could you please avoid directly changing the recommended status for extensions on e.x.o and instead contact me or reply to this thread? (I’d like to keep some control on that FTM since this is new). Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac.... Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
I used the Presentation Application in the past and I liked it. Unfortunately I didn't had the time to improve it. I would recommend it Thanks, Marius On Wed, Aug 31, 2016 at 12:26 PM, Vincent Massol <[email protected]> wrote:
Update: we now have 29 recommended extensions on http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/
I think it’s a good start and I’m going to work with Caty to make it visible on the home page of e.x.o. Please reply quickly if you don’t agree :)
Then we can iterate if you think some other extensions should be recommended. In term of process, for now, could you please avoid directly changing the recommended status for extensions on e.x.o and instead contact me or reply to this thread? (I’d like to keep some control on that FTM since this is new).
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ ApplicationDevelopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
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
On 31 Aug 2016, at 12:39, Marius Dumitru Florea <[email protected]> wrote:
I used the Presentation Application in the past and I liked it. Unfortunately I didn't had the time to improve it. I would recommend it
But recommended means several things including having an active support for it which isn’t the case fo the presentation app ATM. We would need to find someone willing to do the support (fix bugs, make improvements, test it regularly - e.g does it work with Nested Pages, etc)? Personally and even though I’m the original author, I’m not really interested in doing this. Also, I don’t know if someone has improved it but last time I coded it, it was quite crude in term of polishing/ease of use. Thanks -Vincent
Thanks, Marius
On Wed, Aug 31, 2016 at 12:26 PM, Vincent Massol <[email protected]> wrote:
Update: we now have 29 recommended extensions on http://extensions.xwiki.org/xwiki/bin/view/ExtensionCode/ RecommendedExtensions/
I think it’s a good start and I’m going to work with Caty to make it visible on the home page of e.x.o. Please reply quickly if you don’t agree :)
Then we can iterate if you think some other extensions should be recommended. In term of process, for now, could you please avoid directly changing the recommended status for extensions on e.x.o and instead contact me or reply to this thread? (I’d like to keep some control on that FTM since this is new).
Thanks -Vincent
On 23 May 2016, at 10:39, Vincent Massol <[email protected]> wrote:
Hi devs,
We have a lot of entries on extensions.xwiki.org (869 as of today) and this causes some problems for our users:
P1) A lot of them are not of good quality (they don’t work with the latest versions, they are complex to use, they’ve not been updated for a long time and are doing old and deprecated ways of doing things such as not providing an entry in the Applications Panel for example, they’re not just polished, etc) and this causes frustrations for our users. Note that this also reflects on the overall quality of the XWiki project and product.
P2) It’s hard for users to locate good extensions among the rest.
We’ve started addressing P1) by introducing ratings on e.x.o. This is not fully successful so far because we don’t have enough people voting and because those ratings are not used to display/filter extensions on the Extensions LT or inside XWiki in the EM UI. So we need to continue this effort.
Note that this proposal is not addressing non-extensions such as snippets which we’ll need to move elsewhere at some point but that becomes less important with the proposal below.
Proposal =======
I’d like to propose an additional strategy that, IMO, is better suited for the size of our community: curation. Curation is the process of hand-selecting the best extensions and marking them as recommended. The idea would be to list recommended extensions first on the e.x.o home page, in the EM UI in XWiki and even in extension search results. In the EM UI, an idea would also be to have a new “Recommended Extensions” filter in addition to the existing filters (core extensions, installed extensions, etc) and that would be the default filter on the “Add Extensions” UI.
I propose to add a “Recommended” xproperty in the Repository app for that. We can decide whether we want this just for e.x.o or committed in the Repository app in xwiki-platform.
Then we need to decide about the curation process:
* The XWiki core committers are in charge (i.e. have the responsibility) of monitoring the apps that are marked “Recommended”, ie. validating that it’s done correctly. XWiki core committers have the authorization to unset an app that was marked a recommended by a community member. * We wouldn’t offer a simple way in the UI to mark an extension as recommended since we don’t want everyone who has an account on xwiki.org to start marking apps as recommended. OTOH we want to allow people from the xwiki community to help out. So the way to mark an extension as recommended would be to use the object editor (for now, we can define a better implementation mechanism later on). * We define some basic rules that extensions need to follow at minimum to be accepted as recommended. These will be our guidelines to avoid conflict of opinions (although there’s always the possibility in which case it’s resolved through a vote): - Need to work on LTS + latest XWiki version (ie. ATM that would be 7.4.x and 8.1) - Need to present a polished aspect and be easily usable - Need to follow most of the best practices defined on http://dev.xwiki.org/xwiki/bin/view/Community/ ApplicationDevelopmentBestPractices. Some important examples: technical pages are hidden, extension is registered in the app bar when it makes sense, extension is internationalized (if it makes sense), pages are in xwiki syntax 2.0+.
WDYT?
I’m willing to help do the work and mark extensions as recommended.
Thanks -Vincent
participants (7)
-
Caleb James DeLisle -
Ecaterina Moraru (Valica) -
Eduard Moraru -
Guillaume Delhumeau -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol