On Thu, 2008-02-21 at 22:42 +0100, Jörn Nettingsmeier wrote: > Michael Wechner wrote: > > so I would ask, why has it actually been added to the sandbox if none of > > the other devs was ever interested in these two modules? > > > > So it makes sense to me to move them outside. > > -1 > > as long as we don't really have a totally cluttered sandbox, i'd say > let's leave the stuff in there. it's a lot easier to discuss and work on. > if it turns out someone who is not yet a lenya committer (and thus does > not have sandbox access) takes interest in one of those modules, s/he > can fork it for a while and we can re-sync when some interesting > development is finished (and maybe the developer will then become a > committer anyway). > > i wouldn't want to have all the administrative work that comes with > creating a new repo somewhere else. or does anyone have issues with the > asf license and therefore does not want their work in svn? if so, let > those people set up a new repo. >
Very well said Jörn. I completely share your point of view. As for hosting modules outside of our trunk I think we should be able to support this. Let me explain. In forrest we have plugins and they to not need to be hosted on the ASF. Matter of fact we have a POD plugin that is hosted outside from a non forrest committer. This shows nicely a feature but I would expect the module on foreign server hosting situation under the following circumstances: - ASF incompatible license issues - author is not committer in lenya - module strives against the development focus of lenya Regarding the development of modules in our sandbox IMO that is totally alright and I do not see the need to ask for permission if one want to add new code there. Having said this the sandbox should not become an "external" storage facility for committers. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
