On Sat, Jan 7, 2012 at 10:24 PM, Roy T. Fielding <field...@gbiv.com> wrote: > If there is a community > and that community doesn't want Apache to fork the code that they created, > then we will not fork that code at Apache. If the original developers of the > code do not want their license changed, then we will not fork the code at > Apache. > We only accept voluntary contributions (contributions == the stuff we take on > as > change-controller and managed as such by one of our collaborative projects). > We use other open source code and include that other code in our own releases, > but we don't take change-control over it without the blessing of the original > authors.
[Citation Needed] While I agree with the general idea, the closest I can find to it being written down is http://incubator.apache.org/guides/proposal.html#template-community which is not very close at all. Did the subject actually come up before or is this the first time you wrote this down? Also, we should consider that the modus operandi of open source is changing. The default behavior on github for example is to put a "fork me on github" button on your project website, which doesn't mean a "community fork", but for the healthier projects it does mean "community chaos" as forks and pull requests simply happen all over the place. So the relationship between "take change-control" and "community fork" is a bit different in those instances. You could say that the "fork me on github" (or just using github) is in fact inviting everyone to take as much change control as they want. cheers, Leo --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
