Re: [wxCode-users] Monthly status report

[John L. <jla...@gm...>]

On 7/25/05, Francesco Montorsi <f18...@ya...> wrote:
> > I think the website has it's own "news" which would suffice, but
> > Francesco would know better. I'll check into this.
> sorry John; I do not understand what you mean... are you saying that you
> prefer a message to wxcode-users mailing list on new releases ?

I didn't realize that the wxcode news *is* the sf news.
=20
> I wrote that any component should use the "wxWidgets" license only
> because wx developers told me that an important point in moving contrib
> stuff to wxCode is that all the sources at wxCode must be easily
> integrable in wxWidgets, eventually.
> So wxWidgets-license should be used for the components that hope to be
> integrated in wx...
> however, I do understand that many other components are not designed to
> be integrated in wx at all ... so using a license different from
> wxWidgets one is okay...

It's not that they'll be integrated into wxWidgets, but that they're usable=
.=20

I think Ryan's idea is best, they can dual licence it if they like,
but one of them has to the wxWindows license. As he pointed out, I
completely missed the ramifications of the BSD license clause and I'm
sure it can get much uglier than that. I've seen quite a few licenses
with catches like, "for commercial use you must merely contact me...".
What if you're not around anymore? The more I think about it, we
should be fairly strict about licensing since it'll only cause
problems later.

How about the wording below, I think we need a compelling explanation
why we want the wxWindows license and a note about 3rd party libs
since it's bound to come up as a question eventually.

"Each component must be made available under the wxWindows license.
This is to ensure that there will be no misunderstandings by users of
your code or clashes between components that may rely on each other.
Remember; this code repository is designed to facilitate code reuse.
Small third party libraries that you may include or link with your
component will (of course) maintain their original license and you
should note that in your documentation."

Regards,
    John Labenski