[curriki-devs] Commit rights request

[Joshua Marks]

Ludo,

 

The proposal looks good. You can make me code committer just in case. We can
keep Dave for now but he might want out. JohnWu might also need to commit at
some point and similarly with Todd. 

 

Regarding #3, lets discuss with Paul in a couple of weeks. 

 

Joshua Marks

CTO

Curriki: The Global Education and Learning Community 

jmarks at curriki.org

www.curriki.org 

US 831-685-3511

 

I welcome you to become a member
<https://www.curriki.org/xwiki/bin/view/Main/JoinCurriki>  of the Curriki
community, to follow us on Twitter <http://twitter.com/Curriki>  and to say
hello on our blog <http://www.curriki.org/xwiki/bin/view/CurrikiBlog/> ,
Facebook <http://www.facebook.com/group.php?gid=26295197410>  and LinkedIn
<http://www.linkedin.com/groupInvitation?groupID=1826931&sharedKey=277A033FE
F70>  communities.

 

 

  _____  

From: Ludovic Dubost [mailto:ludovic at xwiki.com] 
Sent: Tuesday, November 02, 2010 2:21 PM
To: jmarks at curriki.org; curriki-devs at xwiki.org
Subject: Re: [curriki-devs] Commit rights request

 


+1 too

Joshua, it might be the time to refresh the official commiter list of
curriki and set somes rules about:

1/ How decisions are made concerning the open source curriki code
2/ Who is the official commiter list
3/ Define what should be/should be not commited in the branches and in the
trunk

For 1/

On the XWiki side we would have:

- Ludovic
- Flavius
- Ciprian

On Curriki side
- Joshua (not for code but for votes)
- Dave
- Paul

Anybody else that should be commiter ?

For 2/ 

For the decision process i propose the same one used on XWiki.org which is
based on the Apache Foundation process which basically is concensus off
commiters:

http://dev.xwiki.org/xwiki/bin/view/Community/Committership

For 3/

The 1.8 branch is for curriki.org only.
The trunk is for a 2.0 based Curriki with the old skin and a new skin based
on XWiki 2.x color themes and should only receive code that is not specific
to any curriki installation or new modules.

This means that each project using the curriki code based might need to have
their overridding from their own repository. This might be more contraining
for curriki that the 1.8 branch but is the way to go to have the code base
being used by multiple projects at once (which is now the case with 1
project using the 2.0 branch besides curriki and another one starting soon).

WDYT ?

Ludovic


Le 02/11/10 18:39, Joshua Marks a écrit : 

+1

 

Joshua Marks

CTO

Curriki: The Global Education and Learning Community 

jmarks at curriki.org

www.curriki.org 

US 831-685-3511

 

I welcome you to become a member
<https://www.curriki.org/xwiki/bin/view/Main/JoinCurriki>  of the Curriki
community, to follow us on Twitter <http://twitter.com/Curriki>  and to say
hello on our blog <http://www.curriki.org/xwiki/bin/view/CurrikiBlog/> ,
Facebook <http://www.facebook.com/group.php?gid=26295197410>  and LinkedIn
<http://www.linkedin.com/groupInvitation?groupID=1826931&sharedKey=277A033FE
F70>  communities.

 

 

  _____  

From: curriki-devs-bounces at xwiki.org [mailto:curriki-devs-bounces at xwiki.org]
On Behalf Of Paul Libbrecht
Sent: Tuesday, November 02, 2010 1:53 AM
To: curriki-devs at xwiki.org
Subject: [curriki-devs] Commit rights request

 

Hello fellow Curriki developers,


So as to perform a few adaptations for curriki.org <http://curriki.org/>  I
would like to request commit rights for
http://svn.xwiki.org/svnroot/xwiki/curriki

My user-name on jira is polx.

thanks in advance

paul

 
 
_______________________________________________
curriki-devs mailing list
curriki-devs at xwiki.org
http://lists.xwiki.org/mailman/listinfo/curriki-devs






-- 
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xwiki.org/pipermail/xclams-devs/attachments/20101102/e7bc2ac8/attachment.html>