On Mon, Jan 2, 2012 at 9:56 AM, Hyrum K Wright <[email protected]> wrote: > On Sat, Dec 31, 2011 at 10:57 AM, Ethan Jucovy <[email protected]> wrote: >> Hi, >>
:) [...] > > One more thing: many projects use github, and there are even mirrors > on github for Trac and its dependencies. Do you require a similar > vote every time somebody presses the "fork" button on github? How is > this instance different? > I mentioned something like this in main thread @ trac-dev . After reading a bit more it seems to me that there's a difference (in contrast to my initial view, similar to yours) . Mainly related to interactions between ALv2 & BSD when (pushing | pulling) (code | patches) back and forth . What happens (maybe extremely simplified , but I hope you get the idea ;) in Github, Bitbucket , ... is 1- Initial User1 "owns" project repository (Repos1) 2- User2 creates a fork (Repos2) , which is allowed by most (all?) open-source license 3- User2 modifies code and commits changes in Repos2, which is allowed by most (all?) open-source license 4- User2 sends a pull request so as to incorporate "his" modifications, by doing so generally this implies that User1 agrees to distribute those changes under the same terms (license) of code in original Repos1 ... if not explicitly, that decision is implicit AFAICS 5- Let's suppose User1 reviews changes and accepts to merge these with existing code base ... there's no problem considering (4) Let's suppose Repos1 = Trac-dev's and Repos2 = Bloodhound's , fact is that in this case the fomer is BSD whereas the later will be ALv2 (different to 4 above) and it seems there are unhappy interactions in this case (mentioned in main thread , no need to repeat them here ;) -- Regards, Olemis Facebook => http://www.facebook.com/olemis Twitter => http://www.twitter.com/olemislc (@olemislc) Blog ES => http://simelo-es.blogspot.com Blog EN => http://simelo-en.blogspot.com Quora => http://www.quora.com/olemis Youtube => http://youtube.com/user/greatsoftw Get a signature like this. CLICK HERE. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
