Actually the answer seems simple.

Whatever the IB site publicly displays and requires, we can observe what IB
considers adequate, plus the attribution requirements of CC-by-SA and any
non-conflicting wikitravel reuse terms and attribution to the site itself
if needed.

We may do more (add diffs and other authors where omitted, link to an
explanatory page), but whatever information IB provides, if we show at
least the attribution information visible in IB's own public pages, it
would inherently be hard for IB to sustain a claim of any fork inadequately
attributing original authors.

Also attribution of "wikitravel" or "IB" itself is not a barrier.
It doesn't provides any assistance to IB in terms of their presumed goal of
preventing forking. It is trivial to meet any sane and legally necesary
acknowledgement of and/or IB, once IB stipulate (as they
inevitably must) the attribution they feel to be acceptable and its legal

Beyond that the rest is a matter for, 1/ the wikitravel community such as
care to speak on it, and 2/ any minimum attribution the wikimedia community
or the Foundation might feel is needed for best practice or license
compliance.  It may be possible in a number of ways but I'm sure a
satisfactory agreement would not involve IB-style litigatory approaches.


On Fri, Sep 7, 2012 at 9:14 PM, Nathan <> wrote:

> On Fri, Sep 7, 2012 at 4:11 PM, emijrp <> wrote:
> > When we use 1911 Britannica texts, we only attribute to the encyclopedia,
> > not its authors, so we can put "This text comes from Wikitravel".
> >
> > Anyway, if we are going to use Wikitravel texts, writing a script to
> scrape
> > just the usernames from histories is trivial
> >
> >
> That's not really accurate, and not how Wikimedia projects expect to
> be credited either. "Wikipedia" or "Wikitravel" are not the authors of
> any project content (other than, for Wikitravel, that written by
> employees in the course of their employment).
> _______________________________________________
> Wikimedia-l mailing list
> Unsubscribe:
Wikimedia-l mailing list

Reply via email to