On Thu, 5 Sep 2002, Galbreath, Mark wrote:
> Date: Thu, 5 Sep 2002 12:07:15 -0400
> From: "Galbreath, Mark" <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: 'Struts Users Mailing List' <[EMAIL PROTECTED]>
> Subject: RE: [LEGAL] Apache Software License
>
> Thanks, Craig. Do I understand you to say, then, that (for example)
> shop.t-mobile.com (hosted on our servers) is required to display an
> acknowledgment to Apache? The reason I'm asking is Marketing refuses to
> display anything and the development team (naturally) wants to display the
> Struts logo (or even a footnote) on the home page.
>
You don't need to say anything about Struts in particular.
To conform to the license, you do need the Apache copyright notice
somewhere on some page that is visible to the site users.
> Mark
Craig
>
> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 05, 2002 12:02 PM
> To: Struts Users Mailing List
> Subject: Re: [LEGAL] Apache Software License
>
>
>
>
> On Thu, 5 Sep 2002, Galbreath, Mark wrote:
>
> > Date: Thu, 5 Sep 2002 09:23:34 -0400
> > From: "Galbreath, Mark" <[EMAIL PROTECTED]>
> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> > To: "Struts (E-mail)" <[EMAIL PROTECTED]>
> > Subject: [LEGAL] Apache Software License
> >
> > The license states that commercial applications built with Struts (or
> > anything else developed by Apache) must include a copyright
> > notice/acknowledgment be included either in the software documentation or
> in
> > the software itself. What does "software itself" mean?
> >
>
> "The software itself" would be relevant when you shipped a stand alone
> application (like a Swing-based GUI app). In such cases, you'd commonly
> put the attribution on a "Help-->About" menu option. This doesn't really
> apply, however, when you're doing a server side web app and the software
> stays on your server.
>
> > Public display on a web page?
> >
>
> That's the typical approach for webapps, because that's usually the way
> webapps are documented. If you also support a downloadable documentation
> bundle, it should be there as well.
>
> > Comment in the source?
>
> Nice, but not helpful (from a license perspective) unless users of the app
> can see your source code.
>
> Since you don't pay for open source software, acknowledgement and credit
> are the "method of payment," if you will. The publicity is the value to
> the open source developer -- after all, your programmers already know they
> are using it :-).
>
> >
> > Mark
> >
>
> Craig
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
