Hi John, >> >> >> How is the project team fulfilling this requirement? Is it an implied >> agreement? Is it an explicit agreement? For exmple, the first time >> StarOffice is used the users sees a license and must agree to it. Other >> projects simply have the license included in the packaging because the >> license agreement allows for that method. >> > > Yes, we are having the license included as part of the packaging > currently and a positive user agreement is not being obtained > explicitly. Checking with the attorney if that would be fine. > We have got confirmation from the attorney that an implicit agreement is fine. Quoting the same below:
"The distribution here should not be treated differently than any other Apache licensed package you have ported. I would just clarify your summary below in that based on the fact that (i) the terms of the license under which you obtained the Wiseman sources did not include an obligation to require users to "click and accept" the Apache 2.0 prior to use and installation by the users, and (ii) your distribution complies with the terms of the Apache 2.0 license, you will not need to require users to "click and accept" the Apache 2.0 license prior to installation of the Wiseman Sun package. " Thanks Bharath > >> Thanks, >> >> John >> >> >> Bharath Kumar wrote: >>> Hi John, >>> >>> Please see replies inline. >>> >>> John Fischer wrote: >>>> Bharath, >>>> >>>> Doesn't Wiseman import JAX-WS? >>>> >>> >>> Wiseman uses libraries that are exported from JAXB and SAAJ. ( >>> https://wiseman.dev.java.net/quick_start.html ) and it is mentioned >>> in the imported interfaces >>> >>>> The developer documents state that the user must agree to the Apache >>>> License agreement prior to using the project. How is the project >>>> mitigating this requirement? >>>> >>> >>> We have an approved OSR (#10652) which mentions the Apache license. >>> Please let know if you meant something else. >>> >>>> Is this also a developer release or only an end user release? >>>> If a developer release will it integrate into NetBeans and >>>> Eclipse? >>>> >>> >>> The developers and end users both could use this. No plans to offer >>> any IDE integrations over and above what the upstream community >>> offers, since this is a familiarity case. >>> >>>> This is a client/server technology. How is the server started? >>>> >>> Wiseman only provides API's using which developers can write client >>> and server applications that will deploy on webservers. Those >>> applications would take care of starting or stopping their services. >>> >>> Thanks >>> Bharath >>>> Thanks, >>>> >>>> John >>>> >>>> >>>> Mark Carlson wrote: >>>>> I am sponsoring this familarity case for Bharath Kumar. It >>>>> requests minor binding and times out 05/05/2009. >>>>> >>>>> -- mark >>>>> >>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>> This information is Copyright 2009 Sun Microsystems >>>>> 1. Introduction >>>>> 1.1. Project/Component Working Name: >>>>> Wiseman >>>>> 1.2. Name of Document Author/Supplier: >>>>> Author: Bharath Kumar >>>>> 1.3 Date of This Document: >>>>> 28 April, 2009 >>>>> >>>>> 2. Project Summary >>>>> 2.1 Project Description >>>>> >>>>> This project introduces the package of Wiseman 1.0 >>>>> into the SFW consolidation. >>>>> >>>>> 4. Technical Description: >>>>> >>>>> The wiseman project is an implementation of the >>>>> WS-Management specification for the Java SE platform. The >>>>> project scope includes server-side and client-side >>>>> implementations of the WS-Management specification and its >>>>> dependent specifications. >>>>> 5. Interfaces >>>>> >>>>> Exported interface Classification >>>>> Interface type >>>>> ================================ ============== >>>>> ============== >>>>> SUNWwisemanu Uncommitted >>>>> wiseman user package >>>>> /usr/lib/java/wiseman/wiseman-client.jar Uncommitted >>>>> Jar exporting wiseman client classes >>>>> /usr/lib/java/wiseman/wiseman-core.jar Uncommitted >>>>> Jar exporting wiseman core classes >>>>> /usr/lib/java/wiseman/wiseman-tools.jar Uncommitted >>>>> Jar exporting wiseman tool classes >>>>> /usr/bin/mViewer Uncommitted >>>>> wiseman viewer tool >>>>> /usr/bin/wise Uncommitted >>>>> wiseman tool >>>>> /usr/share/man/man3/wiseman.3 Uncommitted >>>>> Manpage >>>>> /usr/share/doc/wiseman Uncommitted >>>>> wiseman docs >>>>> SUNWwisemanr >>>>> Uncommitted wiseman root package >>>>> /etc/wiseman Uncommitted >>>>> wiseman configuration directory >>>>> /etc/wiseman/schemas Uncommitted >>>>> directory for wiseman schemas >>>>> /etc/wiseman/schemas/addressing.xsd Uncommitted >>>>> XML Schema languagage >>>>> /etc/wiseman/schemas/enumeration.xsd Uncommitted >>>>> XML Schema languagage >>>>> /etc/wiseman/schemas/eventing.xsd Uncommitted >>>>> XML Schema languagage >>>>> /etc/wiseman/schemas/transfer.xsd Uncommitted >>>>> XML Schema languagage >>>>> Imported Interfaces >>>>> Interface Name Classification Comments >>>>> ----------------------- ----------------- >>>>> -------------------------- >>>>> jdk1.5 or above committed Java >>>>> Development Kit >>>>> tomcat6 committed tomcat apserver >>>>> (PSARC/2008/711) >>>>> junit4.5 committed java unit testing >>>>> tool (LSARC/2008/633) >>>>> jaxb2.1.1 jars Uncommitted JavaBeans >>>>> Activation Framework (LSARC/2009/237) >>>>> saaj1.3.2 jars Uncommitted SOAP with >>>>> Attachments API for JavaTM (LSARC/2009/236) >>>>> >>>>> 6. Resources and Schedule >>>>> 6.4. Steering Committee requested information >>>>> 6.4.1. Consolidation C-team Name: >>>>> SFW >>>>> 6.5. ARC review type: FastTrack >>>>> 6.6. ARC Exposure: open >>>>> >>>>> _______________________________________________ >>>>> opensolaris-arc mailing list >>>>> opensolaris-arc at opensolaris.org > >
