From: Ulrich T. <Ulr...@gm...> - 2005-07-25 16:54:53
|
Hi, > >>6 - You've already got sourceforge release notes for each update.... > >> you could also give the person news access also to notify sf of > >> thier new release > well, I strongly encourage all wxCode mantainers to use SF news system > to inform others of their updates. I fully agree. After the release of a component a message on SF news reaches all wxCode users through the wxCode website and probably additional SF users. > I think that a mantainer should do: > - a new SF entry > - a message to wxcode-users > - a message to wxusers > when he is releasing its new component... Could this be automated somehow? > >>8 - I really think this should be something like wxWidgets or something > >>compatable and less restrictive > > [...] > > How about this: > > "Each component must be submitted under the wxWindows license or a > > license that is compatible and less restrictive, such as the BSD, MIT, > > and zlib/libpng." > Maybe this is the best. > > 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... In my opinion the components in wxCode should all have the wxWidgets license. This would take from the user of a wxCode component the burden to check several different licenses whether they allow the planned use or not. AFAIK the wxWidgets license is very liberal and allows commercial use. What more is needed? Maybe a developer could license his component under several licenses? Ulrich Telle -- E-Mail privat: Ulr...@gm... E-Mail Studium: Ulr...@Fe... World Wide Web: http://www.stud.fernuni-hagen.de/q1471341 |