Vincent Massol wrote:
> On Sep 19, 2009, at 9:47 PM, Jerome Velociter wrote:
>
>> Hi Vincent,
>>
>> does that mean we create a XWEB module as well ?
>
> I think it can be left in the new XCORE for now since we release them  
> together.

I don't really see the point here.

For me it's the perfect timing to extract web out of this new core 
(modules/components) JIRA project and let it have its own components (JS 
API, Velocity Templates, UI components, etc.)

The fact we release web with core is not enough : we release XE with 
core/web too, though it has its own JIRA module. IMHO the "web" 
component in the XCORE project you propose will look a little odd and 
won't belong next to the other core components.

My 2 cents,
Jerome.
>
> -Vincent
>
>> Jerome.
>>
>> Vincent Massol wrote:
>>> Hi,
>>>
>>> Following our previous discussion (see 
>>> http://markmail.org/thread/5lsaq274tvczr5wd)
>>> , I'd like to move this forward. Here's what I propose now:
>>>
>>> 1) We create a new "XWiki Core" (key: XCORE) jira project which is
>>> where we put the new components and where we invite everyone to  
>>> create
>>> new core issues.
>>> * In this new jira project we use the rule of one jira component per
>>> module, whatever the size of the module.
>>> ** For example for the rendering module (which is our largest module
>>> right now) this means one jira component only. In order to make it
>>> easy for users we should name it with something like "Rendering (wiki
>>> syntaxes, macros, ...)"
>>> ** Users will simply need to explain what it's about in the issue
>>> title. For example instead of having a "Rendering - Macro - RSS"
>>> component the issue will be named "Add blahblah feature to the RSS
>>> macro"
>>> ** Having lots of modules might look better but I think 1) having too
>>> many components make it hard for end users to find the right one and
>>> 2) I don't see real needs for them. Do you see any?
>>>
>>> 2) We keep the existing "XWiki Core" (key: XWIKI) jira project but:
>>> ** we change its permissions so that no new issues can be created  
>>> in it
>>> ** we change its name to "XWiki Core - Old"
>>> ** we change its description to tell people to use the other one with
>>> a link to it
>>> ** we add a welcome message in the default dashboard to explain the
>>> change and point people to the new jira project.
>>> ** we slowly move whatever issues we can from it to the new project.
>>> For example we can easily move all Rendering 2.0 issues or all GWT
>>> WYSIWYG issues. For the rest we can move other time whenever we
>>> encounter an issue that should go in the new jira project
>>>
>>> 3) We change our existing jira filters so that they include both  
>>> XCORE
>>> and XWIKI jira projects.
>>>
>>> WDYT?
>>>
>>> If we agree, I can start doing this.
>>>
>>> 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

Reply via email to