Le 18 sept. 07 à 04:06, Yen-Ju Chen a écrit : > Here is a list of licenses in -trunk. > We can ignore the experimental components like Mantella or Babbler. :) > EtoileFoundation has one file in GPL, which conflicts with its BSD > license.
If it's UKPluginsRegistry, that's probably because I forgot to change the license notice to LGPL at some point. I'm pretty sure I already asked Uli about relicensing this class when i wrote PreferencesKit. I'm going to check that out. > Bundles/Camaelon - LGPL2 > Bundles/EtoileBehavior - BSD > Bundles/EtoileWildMenus - LGPL2 or later > Bundles/PowerMenulet - BSD > Bundles/ServiceMenulet - BSD > Bundles/VolumeControlMenulet - BSD ok > Frameworks/AddressesKit - LGPL2 Probably going to be deprecated and rewritten for compatibility reason as a thin API layer over OrganizeKit/CoreObject. > Frameworks/BookmarkKit - LGPL2 (Derivate work from AddressesKit) > Frameworks/CollectionKit - LGPL2 (Derivate work from AddressesKit) These two frameworks are probably going to be deprecated in favor of OrganizeKit/CoreObject. By the way, if you don't mind I would like to put current OrganizeKit in a branch and rename trunk version as CoreObject. I would replace OK prefix by CO one too. > Frameworks/DistributedView[1] - GPL2 Will be deprecated when EtoileUI will provide an equivalent. > Frameworks/EtoileFoundation[2] - BSD > Frameworks/EtoileSerialise - BSD > Frameworks/EtoileUI[2] - BSD > Frameworks/IconKit - BSD > Frameworks/InspectorKit - BSD > Frameworks/LuceneKit - Apache 2 (Derivate work from Apache Lucene) ok > Frameworks/MultimediaKit - GPL (Derivate work from mplayer-osx in GPL) This one is a bit problematic, but it isn't really our big focus right now so it can wait. iirc we already discussed about a bundle architecture that loads GStreamer backend by default to avoid license conflicts and still provides MPlayer as an extra backend. > Frameworks/OPMLKit - BSD > Frameworks/OgreKit - BSD ok > Frameworks/OrganizeKit - MIT ok > Frameworks/PaneKit - LGPL2 This framework is probably going to move to BSD once EtoileUI will be ready and PaneKit can be updated to sit on top of it. > Frameworks/PopplerKit - GPL (Derivate work from xpdf in GPL) > Frameworks/RSSKit - LGPL2 ok > Frameworks/ServicesBarKit - LGPL2 > Frameworks/SystemConfig - LGPL2 Both can be relicensed under BSD (well if Guenther is ok for SystemConfig). iirc I'm the only to have worked on ServicesBarKit. > Frameworks/UnitKit - Apache2 ok > Frameworks/XWindowServerKit - BSD > Services/Private/AZBackground - BSD > Services/Private/AZDock - BSD > Services/Private/AZSwitch - MIT Just out of curiosity, why AZSwitch isn't under BSD like other AZ modules? > Services/Private/Azalea - GPL (Derivate work from OpenBox3) ok > Services/Private/Busy - MIT > Services/Private/Composite - MIT > Services/Private/Corner - BSD > Services/Private/Idle - Unknown We need to fix this one. > Services/Private/LaunchBox - MIT > Services/Private/Login - BSD ok > Services/Private/MenuServer - GPL If Saso is ok, why not move it to BSD. > Services/Private/System - LGPL I will relicense it under BSD if Saso is ok with it (it's based on its initial > Services/Private/SystemToolsBackends - GPL Doesn't really matter since these are perl scripts we can use through NSTask. > Services/Private/TrashCan - BSD > Services/User/AddressManager - LGPL (Derivate work from AddressesKit) Will probably be deprecated once ObjectManager is ready, the only thing we may want to reuse is Gorm files. I'm not sure whether it is necessary to dual-license Gorm files to do so. > Services/User/Babbler[3] - MIT > Services/User/Calc - BSD ok > Services/User/CodeEditor - LGPL2 Yen-Ju, is it possible to relicense it under BSD? > Services/User/ColloquySetStatus - Unknown Must be fixed. BSD? > Services/User/DictionaryReader - MIT > Services/User/FontManager - BSD ok > Services/User/Grr - BSD (GPL for bundles). ok > Services/User/Hardware - LGPL2 I'm going to relicense it under BSD. > Services/User/Installer - GPL2 I don't know really what are our current plans about Installer… See Frederic Munoz mail posted today. > Services/User/Jabber - BSD > Services/User/LookAndBehavior - LGPL2 I'm going to relicense it under BSD. > Services/User/Mantella - MPL 1.1/GPL 2.0/LGPL 2.1 Lovely Mozilla multi-licensing ;-) > Services/User/MicroblogPushExample - Unknown > Services/User/Microblogger - Unknown Must be fixed. BSD? > Services/User/NewsStand - Apache 2 (Derivate work from Vienna 2) > Services/User/OuterSpace - BSD ok > Services/User/Sketch[4] - Apple Does anybody know whether this can be considered as a true BSD license? I'm asking that because I'm currently using a NSCell subclass taken from Apple code examples in Container/EtoileUI. Container is licensed under BSD. May be as a precaution, I should remove this piece of code before merging Container into EtoileUI? > Services/User/Spot - Unknown I will put it under BSD. > Services/User/TermX - MIT ok > Services/User/Terminal - GPL2 (Derivate work from iTerm) We should deprecate it now I think. Because it's GPL2, it isn't probably worth trying to reuse iTerm i18n support in TermX. > Services/User/Typewriter - BSD > Services/User/Vindaloo - GPL2 (Link to PopplerKit) > Services/User/Workflow - BSD ok Thanks for the in-depth license report :-) Quentin. _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
