Commons:Projektplan

Alemannisch | asturianu | বাংলা | dansk | Deutsch | English | português | 中文（简体） | 中文（繁體） | +/−

Målet med Wikimedia projektet Commons er at tilbyde et centralt opbevaringssted for frie illustrationer, musik, tekster og oplæsninger, der kan benyttes direkte af alle Wikimediaprojekterne. Ideen om Commons er oprindeligt foreslået af Erik Möller den 19. marts 2004 [1]. Denne beskrivelse er en mere udbygget beskrivelse af projektet og dets mål baseret på dette forslag og den efterfølgende diskussion. Beskrivelsen her kan også ses som et mere udviklet stadie af ideerne, der er blevet luftet på m:Wikimagery.

Rationale

Som det er nu har alle de mange Wikimediaprojekter - hver enkelt Wikipedia og Wikiordbog, såvel som Wikibøger, Wikikilder og Wikicitater - hver et seperat bibliotek for filoplægning. Der er ingen pålidelig måde at referere til billeder ved søsterprojekterne, så mange gode og frie medier bliver meget nemt overset udenfor det enkelte projekt. Derfor finder unødig kopiering af mediefiler sted i stor stil mellem de forskellige projekter. Det fører til redundans og stort besvært med administration og vedligeholdelese.

Fordele ved Commons:

• Et centralt sted at behandle licens-spørgsmål
• Mindre tid forbrugt på at finde relevante mediefiler
• Et sted for billed-gallerier, der går ud over den enkelte artikels behov.
• Vi kan aktivt anmode om bidrag til Commons fra folk, der ellers ikke er interesseret i at bidrage regelmæssigt.
• Vi kan tilbyde det største lager af materiale, frigivet ved frie licenser, med en kvalitetskontrol ingen andre lignende initiativer har.
• Vi udbygger løbende vores ry ud over encyklopædi-projekterne.
• Vi høster frugterne fra et positivt navn (Commons ~ Fælles) og appelerer hermed direkte til opofrelse for fællesskabet, hvilket vil styrke vores position når vi beder om donationer.
• Vi udbreder kendskabet til copyleft-ideen, et kendskab, som indtil nu er stort set ikke-eksisterende - især for billeder, hvor de fleste mennesker frit bruger alt hvad de finder på nettet.
• Vi kan udbygge denne platform til at blive mere politisk relevant i den nuværende debat omkring copyright-lovgivningen.
• Det moderne billedformat SVG tillader at bitmap-dataene findes ét sted, mens f.eks. billedbeskrivelsen findet andetsteds.

Navngivning

...Mangler oversættelse... Wikipedia describes a commons as a "set of resources that a community recognises as being accessible to any member of that community." Such shared resources - forests, fields, fishing grounds, and so forth - have existed in many societies: ancient, medieval, and modern. In Germany, after the Middle Ages, the local commons (Allmende) in most towns and cities were confiscated by the feudal rulers of the regions, which was one of the motivations behind the German Bauernkrieg (war of the farmers against their rulers). The farmers were brutally suppressed, and the commons practically ceased to exist. To this day, descendants of the aristocrats who profited from robbing and murdering the farmers are among the richest families in Germany.

We must make sure that a true commons can exist in the digital age, and that it can never be taken away. Open content licenses assure this. For good reason, the Creative Commons licenses are named after the principle of the commons. But it would be sadly ironic if the term "commons" became associated with a single implementation only. Indeed, it would be desirable if there would be many different commons for different online projects -- a Slashdot commons, a Kuro5hin commons, and so forth -- which provide free access to a large set of resources. Establishing this idea, and this vision, this meme, is one of the reasons for the "commons" naming suggestion.

The name commons embodies the most important underlying principle of this proposal. It is not about a particular type of content, it is about free, shared access to useful resources.

Our commons should be called the Wikimedia commons because it is not just used by Wikipedia, but by all Wikimedia projects (and many external ones). Making "Wikimedia" a part of the name also increases brand recognition for our foundation, which is as yet largely unknown.

Forslag

Et centralt lager opsættes på adressen commons.wikimedia.org. Det skal indeholde:

• Fotos, diagrammer og andre billeder
• Lyd og musik
• Kunst
• Dokumenter (se herunder)
• Video (indenfor grænserne for båndbredde - grænserne fastsættes af fællesskabet)

The BBC are attempting to make their back catalogue open resource; therefore linking into the creative commons database recently created by Nutch would be a good thing.

All material in the commons would have to be licensed under one of several licenses, not necessarily the FDL, but all allowing at the very least free distribution and commercial use. For texts, modification rights would also be a requirement. [For non-text, incorporation into larger works or collections would be a requirement. -AD] There would be NO fair use material on commons.wikimedia.org.

Da dokumenter i øjeblikket behandles på Wikimedia projektet Wikisource, må denne del af Commons debateres yderligere når Commons bliver en realitet.

Kriterier for materiale på Commons

Materiale der kan uploades til Commons opfylder følgende betingelse: Hvis materialet er brugbart for et af de mange Wikimedia-projekter enten nu eller i fremtiden er det en god ide at uploade til Commons. Herudover skal materialet naturligvis være frit ifølge en af de godkendte licenser her. Fællesskabet vil definere flere kriterier f.eks. at jo mere populær en fil er jo bedre grund til at uploade til Commons.

Diskussionerne om dette emne findes på Commons:Criteria for inclusion (på engelsk).

Implementationen

Forslaget om Commons nødvendiggør en del ændringer i m:MediaWiki, men en fungerende version vil kunne sættes igang med en forholdsvis lille mængde ny kode.

Oplægningsprocessen

The MediaWiki upload form would be completely redesigned. Look at these two mock-ups:

The first selection is whether a file should be uploaded to the commons or to the local wiki (in the mock-up, the English Wikipedia). The commons would always be the default, but the local wiki could be used for things which are useful only to one wiki, or which are not allowed under the terms of the commons. For example, the English Wikipedia allows limited fair use. This option is, however, not available on the Wikimedia Commons upload form.

The second question is whether the user is the creator of the file. If they are, we narrow down the set of allowed licenses to the ones which we prefer, and the user only needs to type a description and is ready to go. We want to make things as easy as possible for original creators. There are a few more questions, however, if the user is not the copyright holder. In this case, they also need to provide source information for the image.

Note that in these mock-ups, depending on the answer to the "Are you the original creator?" question, the other part of the form is grayed out and not editable. This should make it relatively intuitive.

For another example of what the upload forms could look like, with form text translated into a number of major languages, see m:Translation/New upload form.

Wiki på Commons

The commons wiki itself should of course be multilingual as Project Sourceberg and Meta are. New uploads would show up both in the upload log of the wiki from which they were uploaded, and in the commons upload log. Without a m:single sign-on, such uploads would be logged as "Username@wiki", e.g. "Eloquence@enwiki".

There would have to be a real commons community, which would take a look at uploaded files, provide translations of image descriptions, sort media files into galleries, translate and annotate source documents, and so forth. They would also be responsible for enforcing the standards of inclusion.

Brug

Brugen af materiale fra Commons må være gennemskuelig for den enkelte bruger. Når en bruger i en artikel skriver

[[Image:Mona Lisa.jpg]]

skal forespørgslen på billedet først behandles af den lokale wiki og hvis ingen lokal kopi af materialet forefindes skal forespørgslen føres videre til Commons.

Billedbeskrivelsen skal overføres automatisk fra Commons hver gang billedbeskrivelsen ses, indtil den redigeres første gang lokalt. Herefter skal en lokal kopi gemmes.

Nødvendige MediaWiki-ændringer

These are some features which we should enter into the m:MediaWiki roadmap if we want to implement this proposal:

• Provide an interface to a shared media file directory, and to the commons wiki database (to update the commons upload log, create image pages etc.)
• Redesign upload form and resulting description pages, allow uploading either to the commons or to the local wiki
• Transparently import pages when viewing commons image pages, permanently import them when editing them

Ønskede MediaWiki-ændringer

These changes are not crucial to make the Commons work, but are desirable in the long term:

• Rename the Image: namespace to File: and revamp "image" pages to be more intuitive (allow playback of media files, for example)
• Better interlanguage handling in a single wiki installation
• Friendly user interfaces for multi file uploading
• Selectable categories for images?
• Automatic gallery generation for multiple images
• Transclusion of text from the commons (smart caching!), including individual sections

Commons som basis for et enkelt login?

Since the commons proposal requires a shared database (it would be possible to access it via HTTP, but since the Wikimedia setup allows for a shared DB, that would seem unnecessary) it would only be logical to use the commons as the basis for single sign-on.

The implementation would be as follows:

• A field user_created is added to the user table. For existing accounts, this field is filled with the date of the first contribution of the user (alternatively, the date of the creation of their user page). If neither exists, the date is set to "today".
• A new table usermatch is created in the database of each wiki with the fields "local_id" and "commons_id".
• Two tables are created in the commons database: user and user_old.
• The first user_id in the commons user table must be higher than the total number of users of all projects (to avoid attribution problems)
• All unique existing accounts are loaded into the commons user table. An account is unique if it exists only with the same password across all wikis.
• All other existing accounts are loaded into the user_old table, which may include duplicate rows.
• On the creation of a new account that does not exist in the user table, the system system checks whether the account exists in user_old. If so, it prints the name of the oldest account (e.g. "Eloquence, English Wikipedia: 2002-xx") and asks the user for the password to that account.
• If the password is entered correctly, the user now owns that account in the commons database.
• The user can "hook up" additional old accounts by entering the account password. This would be done through the user preferences.
• The edits associated with hooked up accounts would be reattributed using the usermatch tables of the respective wikis. In cases where the usernames are different, a developer would have to push a button -- such cases require changing the user_text in the CUR and OLD table of the respective wiki, which can be quite a big operation.

In the long term, we should of course get rid of the usermatch table and also the user_old table, if possible. Hopefully there will only be relatively few duplicates that do not belong to the same users.

This approach has one key advantage, it quite securely prevents account hijacking. For most users the transition would be completely transparent. The most painful cases are those where a user is forced to change their name because it is already taken by an older user. They are painful largely because of our database layout.

To the end user, it makes things a little simpler, because they can see all the edits they've ever made on all wikis. It may also make stewards obsolete, because bureaucrats can have their status transferred to all wikipedias on which they have an account so they don't have to get them individually (of course, stewards still have the almighty power to desysop someone).

From a technical perspective, the implementation is not so difficult. The filling up of the required tables and fields might take some time, but could be done on a slave database. Using the shared database for logging in is trivial, a universal cookie might be a bit more difficult across different domain names.

Hvem vil hjælpe?

Vil du hjælpe med implementeringen af Wikimedia Commons kan du skrive dig på listen nederst på den engelske udgave af denne side. Noter også på listen hvad du specifikt kan hjælpe med.

Policy Debating

Before this project is implemented a simple policy needs be laid down, please debate, discuss and poll on one of the following pages.

Commons:Criteria for inclusion - should pornography be allowed? etc.

Commons:Licensing - should we allow fair use? etc.

Commons:Features - suggest the mechanism, how should it work?

Collaboration with other projects

See Commons:Collaboration with ourmedia.