<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear Andrew,<br>
<br>
We previously had a volunteer manage and keep certain details of
copyright information (contact, lead, etc.) up at:<br>
<br>
<a class="moz-txt-link-freetext" href="http://crosswire.org/sword/copyright/">http://crosswire.org/sword/copyright/</a><br>
<br>
The volunteer has moved on to other things away from CrossWire and
this site is no longer kept current so we don't link to these
pages any longer.<br>
<br>
Regarding the actual license agreements with publishers, these are
not something that we would publish online. Often publishers have
agreements with many organizations and work out different
agreements with different organizations. Some pay fees; some do
not. We have had agreements where we have volunteers pay nominal
fees to keep our agreements current. Publisher expect this
information to remain confidential. This is typical. For
example, when Logos distributes a work freely or for a fee to an
end user, they never publish their actual agreement with the
publisher which states how much Logos pays per module or per annum
for the rights to make material available to their users. It
would violate the publisher's trust. Granted, the majority of our
agreements probably have nothing anyone would mind being made
public, but I am not willing to make those judgments. If a
publisher challenges our right to distribute their text, I will
certainly make our agreement available to them, but not to end
users who challenge our right to distribute a work. If they feel
they have legitimate reasons for doubting we have permission, they
should inform the publisher who can take action if they also feel
the same. I'm not encouraging you to inform publishers that we
might not have the right to distribute modules; in fact, most of
this thread has been because we are highly sensitive to honor
publisher agreements.<br>
<br>
We give publishers a choice of what they would like displayed to
the end user. We ask them to choose from our list here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://crosswire.org/wiki/DevTools:conf_Files#DistributionLicense">http://crosswire.org/wiki/DevTools:conf_Files#DistributionLicense</a><br>
<br>
They feel this is clear:<br>
<br>
<b>Copyrighted; Permission to distribute granted to CrossWire<br>
</b><br>
No other public distribution should be made. I understand your
heart to help by publicly making a text available to a developer,
and also for the mirrors. I appreciate your desire to help.
Please know that when it comes to violating copyright, we desire
to avoid even the appearance of evil. A work available on a
public website (for any purpose, however good) which is not
authorized by the publisher of the text, is against our policy. I
appreciate that you've removed the text and are working to be sure
you are no longer mirroring our other content which is licensed by
us exclusively for distribution by CrossWire. This is most
appreciated, and I hope this is all simply a misunderstanding and
that wounds can heal and we can share in positive work together.<br>
<br>
Troy<br>
<br>
<br>
<br>
<br>
On 01/06/2013 04:40 PM, Andrew Thule wrote:<br>
</div>
<blockquote
cite="mid:CAM9DYGDQ=tujUmGHgJnb6Hz8j0cd2=Tcmm-=S3NpF+VhyvGaWA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Since this has been a controversial topic recently (and
since accusations have made the matter personal), can
Crosswire please post (to the wiki) the terms of its licensing
agreements with each Copyright holder (on a module by module
basis) so that its licensing rights are known and transparent
to all?<br>
<br>
</div>
<div>Since Crosswire is asserting these rights it must be prove
it actually posses them and outline what they are (or it must
forfeit the right to exercise them). Since it is holding
module developers accountable to its licensing terms, it must
make the license public, for the sake of transparency.<br>
<br>
</div>
<div>Thanks.<br>
</div>
<div><br>
</div>
<div>~A<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
<br>
<br>
<br>
<br>
</body>
</html>