All, based on a discussion still taking place on reorg@, it is now crystal clear that avalon committers nor avalon software enjoys any kind of legal protection from the ASF (I believed otherwise until like 2 weeks ago).
This could be a rather important issue. For example, suppose an avalon committer steals code from microsoft and puts it into avalon cvs, and we all release that software into the world. Microsoft sues (of course). ASF will have a problem (by providing a distribution channel), all users will have a problem (because they use illegal software) and most committers will have a problem (by working on or aiding distribution of illegal software). We might then see users sue apache, and users sueing committers, committers sueing committers etc etc. It's all rather icky. options to make it less icky: - jakarta PMC votes on releases (not really a practical option) - avalon gets a board-installed PMC which votes on releases - destroy avalon (rather not) This sounds like a rather good argument for an avalon PMC. just something to think about. cheers, Leo -----Forwarded Message----- From: Roy T. Fielding <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Incubator, Jakarta, and new projects Date: 29 Oct 2002 19:26:45 -0800 > Assuming there is some PMC structure in which not ever committer is also > on > the PMC, but for which the PMC can maintain "active oversight", are the > actions of commmiters, within the guidelines of a project, "actively > overseen" by the PMC, which is in turn acting within the guidelines set up > by the board,legally protected by the ASF? No. Actions of the PMC are protected. If code is being released to the public without a vote by the PMC for that release, then it isn't an action of the PMC. ....Roy -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
