Hi Reimar, Hi Moin Team,
I moved this talk here, because to me, it did not seem appropriate to cram martins page with it. If there's an even more appropriate place, feel free to beam it there.
First of all: Your invitation honors me! Thanks a lot!
I do have questions though:
Repackaging the RatingSystemForMoin with Moin sound very good. What does it imply in practice?
- Technically: Does it mean simply including it as-is in Moin's tarball? Or does it imply code modifications?
It means more work, preferable code needs to be ported to 1.7, e.g. using the argument parser for macro calls, code needs doc strings, unit tests has to been written for py.test, later on documentations how to use it.
- Legally: I'd be willing to re-publish it under an Apache/GPL dual license, if it helps with formal licensing issues. Would that be OK?
As Martin stated it does help us. But you have to think if its what you'd like. It is necessary that we can reuse code as you did with ours. For example ImageLink becomes in 1.6 part of the parser and the macro is replaced by wiki syntax. It is bad for further devolpement if we can't change code by ourself which we were willing to add to the code base. (ImageLink was written by me and others before I joined the MoinCoreTeamGroup.)
- Technically: Does it mean simply including it as-is in Moin's tarball? Or does it imply code modifications?
- Working closer with the Moin team sound good, too. How would that collaboration look like in practice?
Depends on what you want at least. You published some interesting stuff at the wiki here. If it should be integrated it needs besides the license more work. If I look a head and you do work more and more on interesting Feature Requests or Bug reports and did know more as now about the actual developed codebase you may want to be interested to become in the future a core member too - who knows. We like to stay in contact to coders and like to talk on #moin at irc.freenode.net.
Cheers -- ZoranIsailovski 2007-11-09 17:35:18