Messages 81xx


00: Re: Why "open-source" means "free to distribute"? (jcowan.reutershealth.com)
01: "open-source" x "free software" (Guilherme C. Hazan)
02: Re: Why "open-source" means "free to distribute"? (Lawrence Rosen)
03: Re: "open-source" x "free software" (Fabian Bastin)
04: Re: Why "open-source" means "free to distribute"? (Ian Lance Taylor)
05: Re: Why "open-source" means "free to distribute"? (clay graham)
06: Re: "open-source" x "free software" (Rick Moen)
07: Re: "open-source" x "free software" (Fabian Bastin)
08: Re: "open-source" x "free software" (Ian Lance Taylor)
09: Re: "open-source" x "free software" (Guilherme C. Hazan)
10: Re: Submitting a new license or using the current ones (Rod Dixon, J.D., LL.M.)
11: Re: "open-source" x "free software" (John Cowan)
12: Re: "open-source" x "free software" (Guilherme C. Hazan)
13: Re: "open-source" x "free software" (Robin 'Roblimo' Miller)
14: Re: Why "open-source" means "free to distribute"? (Alex Rousskov)
15: Re: Why "open-source" means "free to distribute"? (clay graham)
16: Re: Why "open-source" means "free to distribute"? (Eugene Wee)
17: Re: Why "open-source" means "free to distribute"? (Alex Rousskov)
18: Re: Why "open-source" means "free to distribute"? (Rod Dixon)
19: Which OS license should we use? (Clint Oram)
20: Re: Why "open-source" means "free to distribute"? (jcowan.reutershealth.com)
21: Re: Which OS license should we use? (Danese Cooper)
22: Re: Which OS license should we use? (jcowan.reutershealth.com)
23: Adaptive Public License v0.1C (Carmen Leeming)
24: Re: Which OS license should we use? (Mahesh T. Pai)
25: Re: Which OS license should we use? (Alexander Terekhov)
26: looking for a license (Adrian Sandor)
27: Re: looking for a license (Marius Amado Alves)
28: Re: looking for a license (Adrian Sandor)
29: Re: looking for a license (Marius Amado Alves)
30: Browsewrap Agreements (Lawrence Rosen)
31: Re: Browsewrap Agreements (John Cowan)
32: Re: Browsewrap Agreements (Lawrence Rosen)
33: Re: Browsewrap Agreements (Mahesh T. Pai)
34: Re: BSD/MIT-like licence with European clause (Thorsten Glaser)
35: For Approval: AT&T Source Code Agreement (Stephen C. North)
36: Re: BSD/MIT-like licence with European clause (Mikko Valimaki)
37: "Malicious Intent" (was Re: RFD: BSD/MIT-like licence with European clause) (Ruth A. Kramer)
38: Re: BSD/MIT-like licence with European clause (Thorsten Glaser)
39: Re: BSD/MIT-like licence with European clause (DJ Anubis)
40: Re: For Approval: AT&T Source Code Agreement (Mahesh T. Pai)
41: For Approval: ZPL 2.1 (Hadar Pedhazur)
42: Re: Next draft of MySQL FLOSS license exception (Zak Greant)
43: Re: Next draft of MySQL FLOSS license exception (John Cowan)
44: Re: Next draft of MySQL FLOSS license exception (Zak Greant)
45: Re: [off-band] Re: FYI: Next draft of MySQL FLOSS license exception (John Cowan)
46: Re: [off-band] Re: FYI: Next draft of MySQL FLOSS license exception (Alexander Terekhov)
47: Question re attribution for derived works... (Claire Giordano)
48: Re: Question re attribution for derived works... (John Cowan)
49: CVS problems (Don Jarrell)
50: Re: Question re attribution for derived works... (Rod Dixon, J.D., LL.M.)
51: Re: Question re attribution for derived works... (Stephen C. North)
52: Re: CVS problems (Nick Moffitt)
53: For approval: wxWindows-to-wxWidgets license name change (Julian Smart)
54: Re: For approval: wxWindows-to-wxWidgets license name change (Ernest Prabhakar)
55: Re: For approval: wxWindows-to-wxWidgets license name change (Russell Nelson)
56: Re: Why "open-source" means "free to distribute"? (Russell Nelson)
57: Re: Pixelglow Source License (nospam+pixelglow.com.pixelglow.com)
58: Re: Pixelglow Source License (Russell Nelson)
59: Which license to use for MFC based software? (Carsten Kuckuk)
60: Re: Which license to use for MFC based software? (Nick Moffitt)
61: Re: Which license to use for MFC based software? (Rick Moen)
62: Re: Which license to use for MFC based software? (Arnoud Engelfriet)
63: Re: Which license to use for MFC based software? (Carsten Kuckuk)
64: Re: Which license to use for MFC based software? (Carsten Kuckuk)
65: Re: Which license to use for MFC based software? (Evan Prodromou)
66: Re: Which license to use for MFC based software? (Carsten Kuckuk)
67: Re: Which license to use for MFC based software? (Robert Osfield)
68: Re: Which license to use for MFC based software? (Carsten Kuckuk)
69: Re: Which license to use for MFC based software? (Rick Moen)
70: Re: Which license to use for MFC based software? (Mahesh T. Pai)
71: Re: Which license to use for MFC based software? (Carsten Kuckuk)
72: Re: Which license to use for MFC based software? (Mahesh T. Pai)
73: Re: Which license to use for MFC based software? (Rod Dixon, J.D., LL.M.)
74: Re: Which license to use for MFC based software? (Rick Moen)
75: Re: Which license to use for MFC based software? (Stephen C. North)
76: Re: Which license to use for MFC based software? (Rod Dixon, J.D., LL.M.)
77: Re: Which license to use for MFC based software? (Rod Dixon, J.D., LL.M.)
78: Re: Which license to use for MFC based software? (Rick Moen)
79: Re: Which license to use for MFC based software? (John Cowan)
80: Re: Which license to use for MFC based software? (John Cowan)
81: Re: Which license to use for MFC based software? (Lawrence Rosen)
82: Re: Which license to use for MFC based software? (Stephen C. North)
83: Re: Which license to use for MFC based software? (John Cowan)
84: Re: Which license to use for MFC based software? (Arnoud Engelfriet)
85: Re: Which license to use for MFC based software? (Mahesh T. Pai)
86: Re: John Cowan announces the "Unix Power Classic" (John Cowan)
87: Dual licensing (nospam+pixelglow.com.pixelglow.com)
88: Creative Commons Attribution (Evan Prodromou)
89: Re: Dual licensing (jcowan.reutershealth.com)
90: Re: Dual licensing (Nick Moffitt)
91: Re: Creative Commons Attribution (Ernest Prabhakar)
92: Re: Dual licensing (Marius Amado Alves)
93: Re: Creative Commons Attribution (Evan Prodromou)
94: Re: Dual licensing (Rick Moen)
95: The myth of copyright license permissions (dlw)
96: Re: Dual licensing (Marius Amado Alves)
97: Re: Dual licensing (Rick Moen)
98: Re: The myth of copyright license permissions (John Cowan)
99: Re: Dual licensing (Marius Amado Alves)