Ludovic: I agree to commit only into the Curriki portions of the trunk. I will await separate permissions/voting to commit into the Xwiki platform portions, should the need arise in the future. For example, I would hope that some "refactoring" of curriki features becomes new core functionality in Xwiki. As I better understand the combined code-base (I just started at curriki) I will be in a better position to understand what such refactoring may entail. At that point, I would be happy to make some proposals and engage in discussion, in case such code reorganization proves mutually beneficial to xwiki and curriki. I am experienced with revision control systems (I was there when subversion<http://svnbook.red-bean.com/en/1.1/ch01s02.html>was being planned, and shaped a number of the features based on collabnet's needs back in the early days of the company when we were developing svn and SourceCast, after our experiences building-in SSL-based 2-factor authentication for cvs&web for http://ipssources.net ). I also fess up to my mistakes when I do make them, e.g.: http://markmail.org/message/2nj5sipyi3qpib4x and also fess up to not having filed a bug report on aforementioned issue ... I admit that sometimes things I like to do with code make it live on the edge-condition, but I'm not one to break the build with it. Thank you for the vote! -- Niels Mayer, http://curriki.org Curriki: The Global Education and Learning Community Ludovic Dubost <[email protected]> wrote: +1 with the reminder that Curriki commit access is full commit access but without allowance to commit in the XWiki platform part Joshua Marks wrote:

Dear Devs,

Niels, who has comment on the list before, is taking on development tasks for Curriki. As such he will need commit access to SVN. Please cast your vote to accept this request.