On Tue, Sep 16, 2008 at 3:33 PM, Thomas Mortagne <[email protected]> wrote:

On Tue, Sep 16, 2008 at 2:18 PM, Jerome Velociter <[email protected]> wrote:

...

Hello everybody,

Discussing we Vincent we agreed that currently XWiki Core components on JIRA are very scattered and do not make very much sense. We propose to reorganize the project and have one component per module in platform core and web, which would be :

* action * cache * component * containers * context * xwiki-core * observation * patchservice * plexus * rendering * url * velocity * xml * xmlrpc * web-standard * web-exo * web-gwt * web-wysiwyg

+1 for that.

+1

...

A question now I have is : since it will be quite a big refactoring, do we move all issues ? or only open issues ?

What do you mean by moving issues ? web issues already are in same jira project than core...

Ok forget that, I said nothing. Mixed svn and jira.

...

Thanks, Jerome.

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

-- Thomas Mortagne

-- Thomas Mortagne

Vincent Massol wrote:

On Sep 16, 2008, at 2:18 PM, Jerome Velociter wrote:

...

Hello everybody,

Discussing we Vincent we agreed that currently XWiki Core components on JIRA are very scattered and do not make very much sense. We propose to reorganize the project and have one component per module in platform core and web, which would be :

* action * cache * component * containers * context * xwiki-core

I'd call this one "other" actually since all the other modules are core too so it's a bit misleading. And when we create new modules out of it we create the new jira component. Yes, better this way.

...

* observation * patchservice * plexus * rendering * url * velocity * xml * xmlrpc * web-standard * web-exo * web-gwt * web-wysiwyg

+1 for that.

A question now I have is : since it will be quite a big refactoring, do we move all issues ? or only open issues ?

Move the issues. That's going to be... a lot of fun :) What do we do with issues that concerns a module (for example URL), but at the time of the issue (or even currently), concerned code is not actually located in that module (but is in xwiki-core instead) ? Move it to the component url anyway ? Leave it in "other" ?

Jerome.

+1 in general.

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

On Tue, Sep 16, 2008 at 3:41 PM, Vincent Massol <[email protected]> wrote:

On Sep 16, 2008, at 2:18 PM, Jerome Velociter wrote:

...

Hello everybody,

Discussing we Vincent we agreed that currently XWiki Core components on JIRA are very scattered and do not make very much sense. We propose to reorganize the project and have one component per module in platform core and web, which would be :

* action * cache * component * containers * context * xwiki-core

I'd call this one "other" actually since all the other modules are core too so it's a bit misleading. And when we create new modules out of it we create the new jira component.

+1, I like the idea

...

* observation * patchservice * plexus * rendering * url * velocity * xml * xmlrpc * web-standard * web-exo * web-gwt * web-wysiwyg

+1 for that.

A question now I have is : since it will be quite a big refactoring, do we move all issues ? or only open issues ?

Move the issues.

+1 in general.

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

-- Thomas Mortagne

On Sep 16, 2008, at 3:47 PM, Artem Melentyev wrote:

> Jerome Velociter wrote:
>> Hello everybody,
>>
>> Discussing we Vincent we agreed that currently XWiki Core  
>> components on
>> JIRA are very scattered and do not make very much sense. We propose  
>> to
>> reorganize the project and have one component per module in platform
>> core and web, which would be :
>>
>> * action
>> * cache
>> * component
>> * containers
>> * context
>> * xwiki-core
>> * observation
>> * patchservice
>> * plexus
>> * rendering
>> * url
>> * velocity
>> * xml
>> * xmlrpc
>> * web-standard
>> * web-exo
>> * web-gwt
>> * web-wysiwyg
> +:
>  * query
>  * store
>
>> +1 for that.
>
> +1
>
>> A question now I have is : since it will be quite a big  
>> refactoring, do
>> we move all issues ? or only open issues ?
>
> +0 for only open.

This is not possible AFAIK...

Thanks
-Vincent