Xalanites: for legal or coordination issues, please followup-to:[EMAIL PROTECTED]; for specific technical issues about how we'd address these points followup-to:xalan-dev.
A few comments/opinions from my perspective and comments on xalan-related items. -sc ---- you Dirk-Willem van Gulik <[EMAIL PROTECTED]> wrote ---- > ... > So no matter what - we need to have the jar's with licenses which > prohibits the ASF of having them there in CVS zapped ASAP - i.e. within > days - even if this is at the expense of zapping a bit too much. > ... >Could you folks get me an opinion ? > >1. Fixing the problem > Option 1.2 > Within the next 72 hours - each projects > makes sure it's jar's adhere to the guidelines > below. All others are zapped. +1 to 1.2; let each subproject try to resolve this themselves to start with. If anyone lags behind, then the PMC or whoever feels the need can come around later and delete any un-officially-processed .jars that remain. -sc >2. Getting our code to work again. > > Option 2.1 > Each project put's their jar's back in - but > according to the guidelines below. +1 to 2.1; at the current time I think it's better to let each subproject manage this themselves as long as they follow guidelines (I like the /lib/ area and the requirement for clearly-named license/readme files to match external .jar files) -sc The central external .jar repository is a nice one but I'm not sure we're quite ready to do that yet; anyways perhaps someday we'll have a magic JJAR/CJAN/Gump/whatever project that helps magically get external dependencies anyway. -sc >Below is a list of jar's. > ... (list only includes xalan-related items with my comments) >Part I > >Third party JAR's - which do not seem to be ASF originated (according to >my judgment/cursory scanning - I am going to be wrong !) >runtime . > xml-xalan This is used only in the xsltc code in xml-xalan; not sure of status. >bsf . 2.2 . . . > xml-cocoon xml-cocoon2 xml-fop xml-stylebook xml-xalan This is IBM's Bean Scripting Framework; not sure of the details of the license from this particular version but I thought it was an ASF-friendly IBM public license of some type. >idb . > xml-xalan This has already been removed from CVS by dleslie. >java_cup . > xml-xalan This is used only in the xsltc code in xml-xalan; not sure of status. >BCEL . > xml-xalan This is used only in the xsltc code in xml-xalan; not sure of status of this release; current BCEL implementation is available at jakarta however the xalan code hasn't updated to those packages yet. >JLex . > xml-xalan This is used only in the xsltc code in xml-xalan; not sure of status. >Part II > >Jars which I ignored - as I am fairly sure they are 100% ASF. Please >correct me if I am wrong :-) >xerces . 1.4.4 3.1 4.4.1 > xml-cocoon2 xml-fop xml-stylebook xml-xalan xml-xerces xml-xerces xml-xindice > xml-security > xml-batik OK - This is an xml-xerces shipment and thus ASF code. >xalanjdoc 2 > xml-xalan OK - This is xalan-related code that happens to be checked in as a .jar for convenience - all ASF stuff. >xercesImpl . > xml-xalan OK - This is an xml-xerces shipment and thus ASF code. >xml-apis . . 1.0 > xml-cocoon2 xml-xalan xml-xindice OK - This is an xml-commons shipment and thus the .jar itself is ASF code although the sources in xml-commons are from external sources and probably need separate review. >ant 3 1.1 4_1 . 1 1.4.1 . > xml-cocoon2 xml-fop xml-xalan xml-xalan xml-xerces > xml-batik > xml-cocoon xml-xindice OK - This is a jakarta-ant shipment and thus ASF code. >stylebookb_xalan-2 1.0 1.0 3 > xml-batik xml-xalan OK - This is an xml-stylebook shipment and thus ASF code. - Shane ===== <eof aka="mailto:[EMAIL PROTECTED]"; "http://www.otnemem.com/"=.sig /> __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
