Vincent Massol wrote:
The more I think about the more I like idea b) below. This means there would be 2 options for anyone wanting to contribute code:
1) If the person is interested in xwiki in general, the best is the contribute it in xwiki's SVN itself and have the person be made a committer 2) if the person is interested only in a specific thing, like a macro he has developed, a plugin, an app, and is looking for a place where he/she can contribute with others on it, then this special forge project is the perfect place.
Now we need to find a name for it and then creating it is quick and easy.
I propose to name it "xlet" which means an xwiki extension in general. Any other idea?
I do like both idea b) and the name "xlet". As I keep trying to enter this great developing universe, the availability of this "special forge" could ease things. Let me guess much more people are in my same situation. What I don't know is how complicated would be for "core devs" to be sure the code developed for any of the coming xlets (I've already added this new word to my dictionary :) is not dangerous for a XWiki installation. Or perhaps this must not be a concern at all for core devs and they will be used on each one's risk. Vincent, I am not so sure about this "macro" doesn't deserve its own project. Although I am just an entry level TeX user, if Paul's team is able to work out the dvi inclusion in the print channel (just copying what Paul said in his message), doesn't open the door to use TeX in many other ways? TeX tables, for instance. Thanks! -- Ricardo RodrÃguez Your EPEC Network ICT Team