On 10/11/05, Lars Aronsson <lars(a)aronsson.se> wrote:
GerardM wrote:
The idea of making it even easier to change
pictures would make
this situation worse.
If you want to reference a certain version, you should be able to
reference that version. The same goes for the text of an article.
The best and only way is by not overwriting existing pictures. It is you who
things there is this "need" to change images. It is best to keep
"updated"
pictures under a different name.
*When there is a picture of a painting; changing the
colours is
BAD. A photo reflects what the picture looks
like. Changing the
colours arbitrarily because it "looks good" is falsifying what
the picture is about.
The same goes for the text of an article. Don't change the facts
only for the purpose of making the lines rhyme. But if the text
is wrong or the picture was taken with the wrong exposure, this
can be corrected afterwards. Images have talk pages, just like
text articles. Revert vandalism, but allow improvements.
Perhaps a "diff" function for images is the first function we
need, so versions could be compared against each other.
The first issue is a big NONO, the second
requires a more
proactive stance of the foundation and its chapters. But my
message to you is NO !! DO NOT CHANGE PICTURES !!
Then you should use a no-derivates (ND) Creative Commons license,
and/or lock the image from modifications. The same goes for texts.
I don't see the principal difference. It's a wiki.
Guess what, this "suggestion" of using ND was done to one of the people who
complained about this undiscrimatory urge to change pictures. The result was
that the pictures were deleted as ND licensed material are incompatible with
the accepted licenses.
The problem is that replacing an existing picture with an "improved" picture
is often a bad idea. The claim that pictures could be locked or that a
different license could be used is against Commons policy. In your answer
you do not address any of the concerns that have been raised.
So, I already have the ability (Gimp) to modify an image offline
and upload a new version, and I'm already
encouraging people to do
this for some images. I'm now looking for examples of how to
design a web application to make this procedure less complicated
for the average user.
You may encourage people to change pictures. This is however not something
that is without controversy. It is better to have it a complicated thing to
do than to have even more of the resulting bad blood.
Thanks,
GerardM