On 06 Jun 2016, at 11:00, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
On Mon, Jun 6, 2016 at 10:50 AM, Vincent Massol <vincent(a)massol.net> wrote:
Hi Thomas,
On 06 Jun 2016, at 10:44, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
Hi xwikiers,
I just introduced a "Project" extension type on
http://extensions.xwiki.org.
I needed a place to put a few words about OpenId Connect in general,
the goal of the project, the various modules and what is common
between them, etc. It's also the parent space of the actual
extensions. It does not shows up in Extension Manager of course.
See
http://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID+Connect/
WDYT ?
As a user I don’t think I’ll understand what “Project” means. Actually even as a dev, I
don’t really. I guess you mean it as a container for other extensions.
All those extensions are part of the same project, released together,
have the same bug tracker et source repository so "even as a dev, I
don’t really" might be a little bit exaggerated :)
The reason I said project wasn’t clear even for devs is because exo is not about
development of extensions; it’s about using binaries.
In a dev context project makes sense but in a runtime context, it doesn’t really. You
don’t install a project and you don’t consider binaries to be a project. The goal of a
project is to create something; it’s a work in progress.
You do install a Product so that might be a better word but it looks too big.
I still find “Group” the best work proposed so far.
Let’s see what others think.
Thanks
-Vincent
I think “Group” would make more sense.
"Group" could be usefull for other use cases but it's really not
strong enough here. The goal is not to group some random independent
extensions but to document a project which have a goal and produced
various installable extensions to achieve this goal.
>
> WDYT?
>
> In any case, we need a legend somewhere to explain the types.
>
> Thanks
> -Vincent
>
>
>> Thomas Mortagne