[xwiki-devs] Curriki in the XWiki Forge and the XWiki forge in general (was Re: [xwiki-notifications] r4670 - xwiki-products/curriki/branches)

[Vincent Massol]

Hi David,

On Sep 5, 2007, at 6:32 PM, David Ward wrote:

> Vincent,
>
> I am not sure exactly how the pom versions are supposed to relate to
> the application versions,

They're one and the same.

> but with the difficulty in doing builds
> against the 1.1 xwiki branch before I created this branch I am afraid
> to touch those and just left them as you originally created them
> (there was issues finding some 5-SNAPSHOT version of something even
> though it should have been there).  The x.y.z versioning method was
> just introduced (with those tags and branch) as before this Curriki
> was not using any straight-forward versioning scheme (more of a
> description).
>
> Splitting the SVN and Mailing lists for curriki might be an idea if it
> bothers anyone.

I just don't see any reason to have them be the same since:
* the communities are separate
* the committers are separate
* the development practices are separate

>   The increase in svn revs don't bother me as that's
> just how svn works (commits to branches, tags, etc. all increase the
> repo revision).

Yes you're right.

> Having a separate trunks-devs could be nice as well.  Of course, right
> now I have to adjust things manually anyway on the checked out version
> (since we're using the xwiki 1.1 branch).

I think Curriki is the perfect project for XWiki's Forge. What this  
would mean:
* A dedicated SVN (or at least a separate root tree)
* A dedicated JIRA project (shoud be the same as now)
* Dedicated mailing lists
* A dedicated wiki

This also means that xwiki.org would be redesigned (we need to do  
that anyway since we now have XEM and Watch in addition to XE) to be  
an umbrella site for all the XWiki ecosystem projects: XWiki  
Platform, XE, XEM, Watch, Curriki, etc. So each project would get its  
own wiki:
* enterprise.xwiki.org
* manager.xwiki.org
* watch.xwiki.org
* curriki.xwiki.org

Actually it's not just curriki but any project in the xwiki sphere  
that reaches a certain level of maturity and which outgrows the xwiki  
platform could also be elected to top level status in the forge (same  
as what is done in Apache land).

What do others think?

Thanks
-Vincent

> On 8/30/07, Vincent Massol <vincent at massol.net> wrote:
>> Hi David,
>>
>> On Aug 30, 2007, at 7:51 PM, David Ward wrote:
>>
>>> Author: dward
>>> Date: 2007-08-30 19:51:15 +0200 (Thu, 30 Aug 2007)
>>> New Revision: 4670
>>>
>>> Added:
>>>    xwiki-products/curriki/branches/curiki-1.2/
>>> Log:
>>> - Branch created for Curriki 1.2 release
>>>
>>>
>>> Copied: xwiki-products/curriki/branches/curiki-1.2 (from rev 4669,
>>> xwiki-products/curriki/trunk)
>>
>> It seems the version numbers in the pom.xml files for curriki are
>> wrong since that you're tagging some old revs with 1.2.x. Poms says
>> 1.0-SNAPSHOT.
>>
>> Should that be fixed?
>>
>> Thanks
>> -Vincent
>>
>> PS: I think we should have dedicated SVN/Mailing lists for curriki
>> since it's not meant to follow the same practices than xwiki. Also
>> every time curriki makes a commit, it increases the svn revs for
>> xwiki and vice-versa. We need to think about that. Last trunks-devs/
>> users for xwiki/curriki should be separate IMO. WDY?
>>
>> _______________________________________________
>> devs mailing list
>> devs at xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
> _______________________________________________
> devs mailing list
> devs at xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs