At http://en.wikipedia.org/wiki/The_Cool_Wall we had a complete list
of cars which appear on the BBC Top Gear "Cool Wall". I removed this
as being almost certainly a violation of copyright. It is now being
argued that reproducing the list in full does not violate copyright,
because it is not published in the show's magazine or on the website
and has been compiled by collating the lists from numerous shows. It
is further asserted that compiling the list from these shows does not
constitute original research, although there is no known reliable
secondary source for any of the data, let alone the complete collated
list
Original research? You decide.
Copyright? I think so, but what do I know?
Fancruft? Ooooh, tricky :-)
Guidance appreciated.
Guy (JzG)
--
http://www.chapmancentral.co.ukhttp://en.wikipedia.org/wiki/User:JzG
Just to let you guys know, prescriptive, descriptive and most
importantly 'thoughtful' essays are welcomed at:
http://en.wikipedia.org/wiki/Wikipedia:Ethics
Best wishes to all Wikipedians for the new year
When you have an issue you cannot solve who do you go to? DR process isn't
helping and my problem is with the DR as I consider it to be broken.
I want to be able to get a problem I see addressed and fixed. I want to deal
with this without being constantly accused of random things.
I currently lack such a median and am open to suggestions.
- White Cat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
In my opinion as well, it is much more annoying to have to
scroll through multiple copies of the entire digest, or over-
long threads, as opposed to the privacy headers. Personally, I
prefer the in-line ASCII headers as opposed to the MIME
attachments, as for those of us subscribed in digest mode, it is
often hard to match the signature to the text. At least in the
clearsigned version, that's obvious.
White Cat, you share this list with many others, many of whom
value both their privacy and the ability to confirm their wiki
identities when necessary.
Avi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32) - GPGshell v3.64
iEUEAREDAAYFAkg/LzcACgkQy6A/RnheoimdGQCggdmnbCsGV3pn1p5yWeHaNp7j
B3kAl27bPb+Lfw6QzNlkh+AZdEDOSps=
=ni5h
-----END PGP SIGNATURE-----
From: "White Cat" <wikipedia.kawaii.neko(a)gmail.com>
To: "English Wikipedia" <wikien-l(a)lists.wikimedia.org>
Date: Thu, 29 May 2008 21:38:28 +0300
Subject: [WikiEN-l] -----BEGIN PGP SIGNED MESSAGE-----?
Some emails start and end with "-----BEGIN PGP SIGNED MESSAGE-----", can
people please disable that thing when emailing mailing lists. It looks quite
ugly.
- White Cat
--
en:User:Avraham
----
pub 1024D/785EA229 3/6/2007 Avi (Wikipedia-related) <aviwiki(a)gmail.com>
Primary key fingerprint: D233 20E7 0697 C3BC 4445 7D45 CBA0 3F46 785E A229
http://news.bbc.co.uk/1/hi/entertainment/7428104.stm
"Q: If Wikipedia can stay free of advertising why can't the BBC? The
worst decision the Trust has made, in my view."
(I must note that I personally don't object to ads on Wikipedia, but I
do think it would be a public relations disaster externally as well as
internally, and should be avoided as hard as we can. I'm posting the
above for anecdotal interest.)
- d.
Some emails start and end with "-----BEGIN PGP SIGNED MESSAGE-----", can
people please disable that thing when emailing mailing lists. It looks quite
ugly.
- White Cat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
best*
I was eating and talking about chicken when I composed that. Sorry.
Best,
Jon
- -------- Original Message --------
Message-ID: <483F3C10.30308(a)datascreamer.com>
Date: Thu, 29 May 2008 18:28:16 -0500
From: Jon <scream(a)datascreamer.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: English Wikipedia <wikien-l(a)lists.wikimedia.org>
Subject: Re: [WikiEN-l] -----BEGIN PGP SIGNED MESSAGE-----?
References:
<27ee9bfb0805291533u66e7883g20c12a09c911545a(a)mail.gmail.com>
<a3f807830805291600k623d12c9je669f355a1fbe69d(a)mail.gmail.com>
<483F35D1.3070509(a)datascreamer.com>
<a3f807830805291605g42218915h7b7a0cb7785402cf(a)mail.gmail.com>
<7c865bab0805291610k54f86d4dw4858092c695e88f3(a)mail.gmail.com>
<483F38A9.5070102(a)datascreamer.com>
<a3f807830805291618o314f2976hc0b9da5a1326d566(a)mail.gmail.com>
In-Reply-To: <a3f807830805291618o314f2976hc0b9da5a1326d566(a)mail.gmail.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
White Cat wrote:
> I really do not see the point at all.
> - White Cat
>
Fall back on that we all share this list :) and some if not most use
PGP. I apologize for the inconvenience.
Very breast,
Jon
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIPzwQ6+ro8Pm1AtURApnyAJ0ZJgvwW9opJXUOtirJHbcBtAgLSgCgnTCK
FOgzUAVqX4bfglS8KuWElgI=
=EGhM
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIPzxH6+ro8Pm1AtURAq++AJ0dYqgAl6v6XWreK+5QHR9xLaiQBACgm4jD
j1PkUQ/ensjqw+CB6HBvPao=
=svn6
-----END PGP SIGNATURE-----
> [..] What is also frequently a concern is that material is frequently
>added to articles based on scholarly resources or books that are not
online. >If the original addition is carefully worded to closely
paraphrase a point >in the secondary source, a copyeditor concerned
about >style might well - >and frequently does - come in and change that
such that it is no longer >sufficiently faithful to the nuances in the
source, since the copyeditor >does not have access to the source.
>RR
True, what helps against this is giving quotes of the dead tree sources
in the footnotes.
Andries
Folks,
Please bear with me while I run a test of my e-mail service. Comcast has
been having problems for the past 24 hours & for some reason I haven't
received any posts from any of the various WP-related Mailing Lists for that
period of time.
Marc
Not necessarily related to upload forms but:
a & b) works good and looks good:
* http://www.freebase.com/view/en/pentax_k10d (using AJAX) -- Please note
the "With the exception of Wikipedia summaries and some images the content
on this page is typically distributed under the Creative Commons Attribution
license <http://www.freebase.com/signin/licensing.html> or Public Domain."
* http://www.larousse.fr/encyclopedie/ (AJAX & Flash) - using slideshows and
other image effects
* http://www.wikiprofessional.org/portal/
Fayssal F.
On Thu, 29 May 2008 20:52:57 +0100 "David Gerard" <dgerard(a)gmail.com> wrote:
> Subject: [WikiEN-l] Fwd: [Commons-l] On upload forms
> To: "English Wikipedia" <wikien-l(a)lists.wikimedia.org>
> Message-ID:
> <fbad4e140805291252g4f5d9b04jfeba918462e1b3d0(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> FYI
>
>
> ---------- Forwarded message ----------
> From: Brion Vibber <brion(a)wikimedia.org>
> Date: 2008/5/29
> Subject: [Commons-l] On upload forms
> To: Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> For a long time we've had to suffer with an image upload form which was
> pretty bare-bones, while attempting to shoehorn more smarts into it
> through templates and JavaScript hacks.
>
>
> Well, I think it's about time we prioritize really doing this thing
> right. Commons, and MediaWiki generally, needs an upload form which:
>
> a) Works sensibly
>
> b) Looks good
>
> c) Allows you to upload the file, extract metadata, compare duplicates,
> make sure it's sensibly named, and *then* commit it into the system.
>
> d) Handles batch uploads with a minimum of fuss (or at least, as
> minimally fussy as one can get with HTML file upload forms :)
>
>
> Note that this isn't going to be done by tacking JavaScript and
> templates onto the existing form; this is going to be a real effort to
> redesign it from scratch into something that handles today's actual needs.
>
>
> I'd appreciate hearing from people interested in helping out in the
> following capacities:
>
> * Designing user interface mockups
> * Helping code it up in MediaWiki
> * Testing the new form under development
> * Providing constructive criticism as we work
>
>
> This effort will probably take from a few weeks to a few months to get
> to the point where it's really live; we may even try experiments like
> having the old and new forms available side-by-side on the live site so
> people really have a chance to bang at it in real usage without forcing
> an in-flux test system on everyone.
>
> - -- brion vibber (brion @ wikimedia.org)
> _______________________________________________
> Commons-l mailing list
> Commons-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/commons-l
>
>