Micheletb
Archives
edit- User talk:Micheletb/archive1 archived Michelet-密是力 05:58, 17 May 2007 (UTC)
- User talk:Micheletb/archive2 archived Michelet-密是力 (talk) 06:58, 4 December 2008 (UTC)
- User talk:Micheletb/archive3 archived Michelet-密是力 (talk) 13:11, 12 July 2009 (UTC)
- User talk:Micheletb/archive4 archived Michelet-密是力 (talk) 19:18, 24 July 2015 (UTC)
- User talk:Micheletb/archive5 archived Michelet-密是力 (talk) 08:53, 5 September 2016 (UTC)
- User talk:Micheletb/archive 6 archived Michelet-密是力 (talk) 17:13, 8 July 2019 (UTC)
Reference of the cursive style
editWhat is the reference for the cursive gif? Are there any other characters also showing the cursive stroke order? --Backinstadiums (talk) 13:56, 17 July 2019 (UTC)
- Hello @Backinstadiums: and sorry for overlooking your message. The only reference I know is Dictionnaire des Formes Cursives des Caractères Chinois by Stanislas Millot. Michelet-密是力 (talk) 07:05, 24 November 2019 (UTC)
Google Code-In 2019 is coming - please mentor some documentation tasks!
editHello,
Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.
I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!
From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.
If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.
Thank you!
De-adminship warning (Feb 2020)
editDear Micheletb. I am writing to inform you that you are in danger of losing your adminship on Commons because of inactivity.
If you want to keep your adminship, you need both to sign at Commons:Administrators/Inactivity section/Feb-Mar 2020 within 30 days of today's date, and also to make at least five further admin actions in the following six months. Anyone who does not do so will automatically lose administrator rights.
You can read the de-admin policy at Commons:Administrators/De-adminship. 4nn1l2 (talk) 03:07, 10 February 2020 (UTC)
Hello! Is this image from http://xiaoxue.iis.sinica.edu.tw/qinwenzi?kaiOrder=318 (not a Chu Silk image but a Qin Silp image)? --沈澄心✉ 06:42, 26 March 2020 (UTC)
- Yes, that's the one. Michelet-密是力 (talk) 06:51, 26 March 2020 (UTC)
- Could you please move this file to File:列-slip.svg without creating redirects? Thanks! --沈澄心✉ 02:23, 27 March 2020 (UTC)
- OK, done. Michelet-密是力 (talk) 04:49, 27 March 2020 (UTC)
- Could you please move this file to File:列-slip.svg without creating redirects? Thanks! --沈澄心✉ 02:23, 27 March 2020 (UTC)
COVID-19 Chart
editHi Micheletb,
Thank you, sincerely, for creating this chart: https://en.wikipedia.org/wiki/2020_coronavirus_pandemic_in_the_United_States#/media/File:CoViD-19_US.svg
Can you create another one, but for the world? (Not just the US.)
Daniel.inform (talk) 15:43, 26 March 2020 (UTC)
- @Daniel.inform: That wouldn't make sense, the pandemic spreads very differently in different places, so the growth rates are heterogeneous, and combining them blurs the logic of the situation. I'll try to do something relevant for the worldwide discussion. Michelet-密是力 (talk) 15:55, 26 March 2020 (UTC)
- Thank you @Michelet-密是力, you are correct - rates vary by location. You may have seen this, for example: https://ourworldindata.org/grapher/covid-confirmed-cases-since-100th-case
- we see that ROW (rest of world) cases and deaths have been following a line (on log scale - exponential growth) since February 22nd. Perhaps we can extend the axes and draw the vertical lines in, so that people can easily see our current ROW trajectory. Daniel.inform (talk) 04:48, 27 March 2020 (UTC)
Regressions on log-log plots: Hi Micheletb - thanks for the work you've put into this but I just wanted to add to the above re: linear regressions. I've reviewed plenty of plots like this for journals in my day job so please don't take this as personal criticism:
It's certainly valid to fit them to exponential growth processes by linearising the data, but one always has to be extremely careful since small variations in the slope on the log plot have much, much bigger implications in temrs of the original data --- and this is especially true if you're also attempting to extrapolate the data for prediction, as here. A good step is always to check the biological realism of the prediction.
For instance, the implication of the lines as fitted in your contribution to the UK covid-19 page is that at some point (around the 2nd week of April as far as I can tell, although the axes have been cropped) covid-19 deaths will outstrip the number of cases. This is clearly impossible(!).
Yes, the use of linear regression lines to clarify the nature of the trend (exponential) is perfectly sensible but I'd argue extending them for extrapolation without also showing the prediction intervals (or at least confidence intervals) of the slope is probably not statistical best-practice, and something we'd wish to avoid.
Can I suggest future plots either (a) limit the line segment to cover just the ovserved data range, rather than extrapolating; or (b) include confidence or prediction intervals if an extrapolation is desired (see link above). Cheers again for all your hard work - and please get in touch if you want any help implementing this. Comrade jo (talk) 08:32, 27 March 2020 (UTC) (or joe.parker@soton.ac.uk)
- Hello @Comrade jo: I'm aware of this uncertainty problem, and obviously the extrapolation on the UK graph is incorrect. As would be an extrapolation beyond the local population... In all disciplines regression is fine for interpolation and hazardous for extrapolation, but extrapolation can give you a general idea on what to expect in the near future. The regression lines are meant to be a visual aid to see where and when the real curve departs from an exponential behavior, the point being for public health policy to bring the data curve to horizontal (like in China), which it must eventually do (another reason for the regression not to be a prediction). For instance, in Italy, the curves are bending under the regression line which is rather good news. In Spain it is not, which is too bad for them. And when the growth regime obviously changes, I make partial regressions on restricted data series - the ones that "seem" straight enough to be underlined. Michelet-密是力 (talk) 09:59, 27 March 2020 (UTC)
It came under renewed discussion at the main pandemic page at en:Talk:2019-20_coronavirus_pandemic#Unclear_references_for_future_predictions_in_image, and to be comfortably reinserted there should be considerable cropping of the lines that predict the future, unless you want to integrate external sources for projections, such as here. Mikael Häggström (talk) 15:26, 30 March 2020 (UTC)
Spain COVID-19 chart
editHi, thanks for creating this chart ... but please can you indicate the last updated time every time you update it (e.g., last updated on 2020-03-26). https://en.wikipedia.org/wiki/2020_coronavirus_pandemic_in_Spain#/media/File:CoViD-19_SP.svg -- 15:59, 26 March 2020 (UTC)
- It's hard to update on my Excel form, it would not be translingual, and is somehow useless, since the curves stops at the update time... But feel free to make a derived work. Michelet-密是力 (talk) 16:12, 26 March 2020 (UTC)
- OK no need to add a title but can you update daily? Alternatively I'm thinking on using this (chart at the beginning of the page) -- ChaTo (talk) 16:39, 30 March 2020 (UTC)
- Hi, @ChaTo: actually the evolution (bending down the curve) is quite slow. The WHO data is updated daily, I update the graphics every two days and I feel that's enough for the time being (when things will be stabilized, no update will be needed, of course). Your first graph would be fine, but for two words of advice : for visual perception the scale should be adjusted so that the main part of the curb goes at a ~ 45° angle ; and (IMHO) avoid bullets on the curve. Michelet-密是力 (talk) 17:14, 30 March 2020 (UTC)
- OK no need to add a title but can you update daily? Alternatively I'm thinking on using this (chart at the beginning of the page) -- ChaTo (talk) 16:39, 30 March 2020 (UTC)
US COVID-19 Chart
editHi Micheletb, I believe "CoViD-19 US.svg" has some missing data: There are "flat" areas where the data did not change; but both cases and deaths (as reported by the CDC, in your reference link) have changed every day.
Also, the bolded vertical lines should correspond with the dates written below, but they are two days off.
(And apologies if I did not add this note correctly). — Preceding unsigned comment added by Extropian314 (talk • contribs) 23:38, 31 March 2020 (UTC) ~ Extropian314
- Hello @Extropian314: The data is as reported by the US to the WHO. I do know the US official often have not reported, hence the flat areas ; this is caused by their messy report and I can't help it. Yours, Michelet-密是力 (talk) 04:35, 1 April 2020 (UTC)
interpolations on Covid-graphs: pretty, but not in accordance with numerous rather important guidelines
editHello Micheletb, how exactly do you arrive at the linearizations provided in these plots? In lack of detailed information, which should be right there in the file info on Commons, I have to assume they use an arbitrarily picked method applied to an arbitrary number of arbitrary time periods... so, to plot a line wherever it "looks right". That doesn't seem to conform to wikipedia:WP:NOR, as it makes up trends; wikipedia:WP:VER, as it provides no source for these trends; and wikipedia:WP:FUTURE, as it draws these trends into the future. I'd like to ask you to correct your graphs to remove the predictive part, and provide information on how the interpolations were achieved. Otherwise, I think they have to be removed, as they spread speculative information without any reasonable, scientific basis. -- Theoprakt (talk) 05:58, 1 April 2020 (UTC)
- See above. Michelet-密是力 (talk) 06:23, 1 April 2020 (UTC)
- "But I am using a perfectly fine interpolation" is not an answer to the problem. The problem is to arbitrarily pick a period, declare the trend from that arbitrary period to have a meaning (WP:NOR) and project that trend into the future (WP:FUTURE). The trends in these graphs violate two major guidelines of Wikipedia, and by inclusion in various articles, spread misleading information. I really think you should remove the interpolations from all your graphs, to comply with essential guidelines. -- Theoprakt (talk) 09:16, 5 April 2020 (UTC)
CL COVID-19 Chart
editHi, thank you for your great work! I was wondering if you could produce a logarithmic scale for Chile? It would be very useful. Thanks a lot! 3BRBS (talk) 03:42, 4 April 2020 (UTC)
- Hi, @3BRBS: There is nothing special about Chile, the pandemic there is not really significant. My rule of thumb is to include countries with more than 100 deaths, which would now include Denmark and Ecuador, but Chile is spared so far. Let's hope for them it keeps being that way. Michelet-密是力 (talk) 05:22, 4 April 2020 (UTC)
- If that is your rationale, then I hope you don't need to produce the table. Thanks a lot for your reply! Merci beaucoup :]
Covid-19 files
edit- image:CoViD-19 AR.svg
- image:CoViD-19 AT.svg
- image:CoViD-19 BE.svg
- image:CoViD-19 BR.svg
- image:CoViD-19 CA.svg
- image:CoViD-19 CH.svg
- image:CoViD-19 CL.svg
- image:CoViD-19 CO.svg
- image:CoViD-19 DE.svg
- image:CoViD-19 DZ.svg
- image:CoViD-19 EC.svg
- image:CoViD-19 FR.svg
- image:CoViD-19 GB.svg
- image:CoViD-19 ID.svg
- image:CoViD-19 IE.svg
- image:CoViD-19 IN.svg
- image:CoViD-19 IQ.svg
- image:CoViD-19 IR.svg
- image:CoViD-19 IT.svg
- image:CoViD-19 KR.svg
- image:CoViD-19 MX.svg
- image:CoViD-19 NL.svg
- image:CoViD-19 PE.svg
- image:CoViD-19 PH.svg
- image:CoViD-19 PL.svg
- image:CoViD-19 PT.svg
- image:CoViD-19 RO.svg
- image:CoViD-19 RU.svg
- image:CoViD-19 SE.svg
- image:CoViD-19 SP.svg
- image:CoViD-19 TR.svg
- image:CoViD-19 US.svg
- image:CoViD-19 World.svg
- image:CoViD-19 ZA.svg
More thanks
editRegarding those who initially removed your log charts, I'd like to point out to them the use of such at BBC, such as found at bottom of article "Coronavirus: New York virus deaths surge past 3,500" or here "How the UK’s coronavirus epidemic compares to other countries" from March 28 (about 4 screens down). It was madness to object to log charts. Thank you for persisting. Shenme (talk) 01:38, 5 April 2020 (UTC)
Covid-19-chart for Switzerland
editHello, in the Swiss chart the deaths go down at one point. Isn't this cumulative data? Probably just a typo in your spreadsheet.
Also thank you for your work. Your charts are great. Judith Sunrise (talk) 16:59, 15 April 2020 (UTC)
- Hi, @Judith Sunrise: The swiss data is indeed surprising, but that's the data series in the WHO records. I presume that some deaths attributed to CoViD19 have been recategorized to something else, but I have no specific data. Anyway, that is not a typo, but ... something strange, indeed. Michelet-密是力 (talk) 18:06, 15 April 2020 (UTC)
- That is very strange. It looks nothing like the data in the article en:2020 coronavirus pandemic in Switzerland - which presumably uses Swiss sources. According the WHO there were 805 deaths until April 11th, according to the Swiss article there were 1032 deaths. Even more interestingly, according to the Swiss Ministry of Health there are only 973 deaths as of today. I am confused, I give up. Judith Sunrise (talk) 12:05, 16 April 2020 (UTC)
About your stroke order files.
editBonjour, I checked your Contributions and in the last page there are Stroke-order.files all of them without a SOlicense. So my question is, may I add it the SOlicense just like they did with for example this file of yours 作-order.gif? FanNihongo (talk) 02:15, 28 April 2020 (UTC)
- Hello, @FanNihongo: No problem, all stroke order files are meant to beused with this SOlicense. Since the User:Micheletb/order.gif licence puts them in public domain anyway, there is no harm in adding a slightly more restricting licence, as long as you do not remove the first one. Michelet-密是力 (talk) 04:41, 28 April 2020 (UTC)
- OK, thank you for your answer. FanNihongo (talk) 05:10, 28 April 2020 (UTC)
Remaking your Stroke Order Files.
editBonjour, Since I started contributing to the Stroke Order Project, I have been making order.gif images as I need them. But then I had an idea, what if I remake the images that I don't like from the other contributors. For example the 100px images. Till this point all is OK. But then I started thinking of more... let's say exigent and perfectionist ideas. So I end up with the idea of remaking almost all your images.
I let you know this, because I didn't know if to tell you or simply do it(because if I simply do it you'll end up with the surprise that almost all your .gif images are now old versions and that could cause some kind of problems between us). So the question is, would you mind if I do that? (Note: If you are curious about what I don't like about your images I made a new .gif tutorial. It is explained in the ante penultimate bullet point). FanNihongo (talk) 00:18, 4 August 2020 (UTC)
- Hello @FanNihongo:
- Make sure you understand the Commons rule for replacing files. A major improvement may be acceptable within the project, but this must stay within the project, it would be otherwise unacceptable (and reverted if needed).
- The 100px images are a very primitive approach of theproject and may of course be overwritten when given the opportunity. If so, make sure you adjust the licence as well by adding the SOlicense (it would be against the rules to merely suppress the existing licence).
- Don't overdo things. The project is about showing a calligraphic stroke order, not making pieces of art. A file like File:永-calligraphic-order.gif is OK as far as it is meant to be used for aesthetics and decorative reasons (I myself indulged into drawing Image:無-cursive-order.gif ) but this should clearly be kept outside of the project, because such graphic fantasies are distracting instead of being helpfull. The author's skill should just invisibly serve the ledgibility of the picture and not be itself (immediatly) apparent. Those files should simply make the stroke order immediately clear for the average reader, and should limit themeselves to that.
- There is no need for mandatory "exigent and perfectionist ideas" : they may discourage contributors, and special cases should be treated so the general feeling of the character gets right, not "by the rules". You may of course be exigent and perfectionist with respect to yourself, which is a different question. Overspecifying is conterproductive.
- I'm not sure I understand what you don't like about "my images", you should be more specific.
- An image like File:背-order.gif is a bit to mechanical for a beginner reader : the strokes are going a bit to fast (a beginner may find it a bit hard to follow), and the intervals between the three character components are not marked (the beginner has no time to realise he knows that component before the next one is arrivintg). Take your time !
- A file like File:金-order.gif seems OK, though I would have put more time interval between the character components.
- Michelet-密是力 (talk) 06:24, 4 August 2020 (UTC)
- @Micheletb I just I want to clarify something: you told me to be more specific about, what I don't like about your images, I was surprised because I thought I explained well. So let me explain again: first clic this link. That will take you to a tutorial of my authorship. There in the "Guidelines about strokes" section, on the ante penultimate bullet point it explains what I don't like. Besides you don't know it but I am also remaking my order.gif files. For example this [%E7%9D%80-jorder.gif](clic on it) check its file history, it was corrected for the clarification explained above.
- I am not sure if proceed with the remake or not, because you told me: "Make sure you understand the Commons rule for replacing files. A major improvement may be acceptable within the project, but this must stay within the project, it would be otherwise unacceptable (and reverted if needed)." with this I understand that I still can do the remake but following the rules for replacing files(I will read it carefully) and the changes must harmonize with the Stroke Order Project, of course your calligraphic files are left out.
- Well, if I someday remake your 300px order.gif files I promise that I will respect the time interval of the file, accept your critics or if I don't have your approval then I will stop making remakes. That maybe take me months to start because I first will remake the 100px files. There are other things I want to discuss too, so I will start another topic for that. FanNihongo (talk) 00:34, 5 August 2020 (UTC)
- @Micheletb I just I want to clarify something: you told me to be more specific about, what I don't like about your images, I was surprised because I thought I explained well. So let me explain again: first clic this link. That will take you to a tutorial of my authorship. There in the "Guidelines about strokes" section, on the ante penultimate bullet point it explains what I don't like. Besides you don't know it but I am also remaking my order.gif files. For example this [%E7%9D%80-jorder.gif](clic on it) check its file history, it was corrected for the clarification explained above.
Remaking your 100px Stroke Order Files.
editBonjour, I will remake your 100px order.gif images, so I have a question: Do you want me to add a (800ms) of interval between components? FanNihongo (talk) 05:23, 5 August 2020 (UTC)
- Hello @FanNihongo: there is no need to be specifc about the delay. The point is just, make it slow, slower still in curves, and add iextra nterval between components. Michelet-密是力 (talk) 07:53, 5 August 2020 (UTC)
- Ok, got it, thank you for your answer and for your time, I will assume you also have read my last answer in the above topic. FanNihongo (talk) 14:13, 5 August 2020 (UTC)
- @FanNihongo: Yet another piece of advice : short ideograms with few strokes may be traced slowly, because people wondering how they are traced will be beginners, and the overall drawing time will stay reasonably short. Complex ideograms may be drawn more quickly, because advanced ideograms are not for beginners, and the overall drawing time needs to be kept reasonably short - but then, if individual components may be drawn very quickly, the interval between components should still remain long enough for them to be assuredly identified. The balance between those constraints is an art, don't try to put rigid figures on it, it's just indications. Ill try to follow some of your productions from time to time. Michelet-密是力 (talk) 17:19, 5 August 2020 (UTC)
- Ok, thank you for your advice, now I see that the creation of these images is more complex than I thought. That advice clarifies many things. FanNihongo (talk) 01:20, 6 August 2020 (UTC)
- @FanNihongo: Yet another piece of advice : short ideograms with few strokes may be traced slowly, because people wondering how they are traced will be beginners, and the overall drawing time will stay reasonably short. Complex ideograms may be drawn more quickly, because advanced ideograms are not for beginners, and the overall drawing time needs to be kept reasonably short - but then, if individual components may be drawn very quickly, the interval between components should still remain long enough for them to be assuredly identified. The balance between those constraints is an art, don't try to put rigid figures on it, it's just indications. Ill try to follow some of your productions from time to time. Michelet-密是力 (talk) 17:19, 5 August 2020 (UTC)
- Ok, got it, thank you for your answer and for your time, I will assume you also have read my last answer in the above topic. FanNihongo (talk) 14:13, 5 August 2020 (UTC)
COM:AN
edit
Best, —Mdaniels5757 (talk) 18:30, 14 August 2020 (UTC)
File:Giuk stroke alt.gif has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
FanNihongo (talk) 00:51, 7 September 2020 (UTC)
- Note: KEPT. FanNihongo (talk) 07:32, 25 March 2022 (UTC)
Glyph's size
editHello Micheletb, I don't remember we discussed changing the conventional svg size ? It makes it a bit confusing now to explain to newbies. Should we chose 270 or 290px ? The first is a 5% margin on each side. The later is a 1.5% margin on each side. It may also have broken the harmony of our datasets. Yug (talk) 12:17, 11 September 2020 (UTC)
- Hi Yug. It does'nt really matter, anything near 280 is fine in the 300x300 square. The size can be adjusted according to the glyph's shape. Michelet-密是力 (talk) 12:36, 11 September 2020 (UTC)
File:直-jorder.gif has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Mikamoto~ruwiki (talk) 12:22, 5 October 2020 (UTC)
- Note: KEPT, this issue is now solved, by uploading a new version. FanNihongo (talk) 02:43, 18 February 2022 (UTC)
About the user that upload images from https://kakijun.jp/
editI want to let you know that one collaborator is not doing the things right and is uploading copyrighted material, he is a Russian user: Mikamoto~ruwiki, he has been uploading images from https://kakijun.jp/ , although he knows about the project he is not doing the things right, because those images do not fit on the Stroke Order Project.
I also wrote about this on the user talk of Magog the Ogre(Other administrator), here is a fragment of what I wrote "I've been doing research, at first I was not sure if it was a copyright violation, but now I am completely sure: On this link is the page that talks about the copyright of those images uploaded by Mikamoto~ruwiki. It is in Japanese, I used google translate to undestand it, here is the first paragraph translated. It says that "All copyrights of the contents (images, sentences, html, scripts, etc.) contained in this homepage belong to this site and kakijun...".".
It is not my intention to be a harasser, that is why I first wrote him a message on his user talk in Russian and in English, to let him know the situation. Instead of start nominating his pages for deletion. FanNihongo (talk) 05:30, 7 October 2020 (UTC)
@Micheletb: He didn't answer, I don't know what to do, I left him a message to solve this the better possible(discussing). For now I will start nominating his files for deletion. FanNihongo (talk) 04:42, 9 October 2020 (UTC)
- @FanNihongo: If the files are from a copyrighted site they must be deleted anyhow. The only point is to warn him not to continue, and that has hopefully been done. If he insists on doing that he can eventually be blocked. Michelet-密是力 (talk) 06:55, 9 October 2020 (UTC)
File source is not properly indicated: File:Briquet.png
editThis media may be deleted. |
A file that you have uploaded to Wikimedia Commons, File:Briquet.png, is missing information about where it comes from or who created it, which is needed to verify its copyright status. Please edit the file description and add the missing information, or the file may be deleted.
If you created the content yourself, enter If someone else created the content, or if it is based on someone else's work, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you! |
Veverve (talk) 01:13, 13 January 2021 (UTC)
Template:NoFoP-France has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this template, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. |
Please participate in the Universal Code of Conduct consultation on Wikimedia Commons!
editDear Micheletb
Thank you for your hard work to create the sum of all knowledge that is freely sharable to every single human being across the world. As our diverse community grows, we need a guideline that will help all of our work collectively and constructively where everyone feels safe, welcomed, and part of a team. That is why the Wikimedia movement is working on establishing a global guideline called the Universal Code of Conduct, often referred to as UCoC.
After the months-long policy consultation, we have prepared a policy (available in many languages) that has been ratified by the Board of Trustees. We’re currently in the second phase of the process. During this round of consultation, we want to discuss the implementation of this policy. As a member of the functionary team of Wikimedia Commons, your opinion on enforcement is of great value. We want to hear from you on how this policy can be enforced on the Wikimedia Commons community and what might be needed to do so. There are a few enforcement questions so you can easily outline your answers based on them. Please do not hesitate to bring any more questions/challenges you think are not yet discussed.
The discussion is taking place on Commons:Universal Code of Conduct consultation. You can also share your thoughts by replying to this message (Please ping me so I get notified), posting your message on my talk page. I am aware that some thoughts cannot be expressed publicly, so you can always share your opinion by emailing me as well.
As a valued member of the Commons community, please share your thoughts, ideas, and experiences that relate to UCoC. Let us know what needs to be improved so we can build a more friendly and cooperative space to increase editor engagement and retention of new users.
Wikimedia projects are governed by you. So, it is you who needs to step up to ensure a safe, comfortable, and pleasant working environment.
Let me know if you have any questions.
Thank you! Wikitanvir (WMF) (talk) 10:18, 5 February 2021 (UTC)
File:阝-torder.gif has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
FanNihongo (talk) 01:43, 12 February 2021 (UTC)
- Note: REDIRECTED, this file was deleted, and it only exists as a redirection link. FanNihongo (talk) 02:33, 18 February 2022 (UTC)
Please take a short survey regarding UCoC
editHello Micheletb,
I would like to inform you that we now have a survey in place to take part in the UCoC consultation. It is not a long one and should take less than 10 minutes to complete. You can take the survey even if you have already participated in the on-wiki consultation. It has a different set of questions and allows you to participate anonymously and privately.
As a member of the Commons functionaries, your opinion is especially essential. Please click here to participate in the survey.
You are still welcome to participate in the on-wiki discussions. If you prefer you can have your say by sending me an email. You can also drop me an email if you want to have a one-to-one chat.
Thank you for your participation! Wikitanvir (WMF) 13:54, 12 February 2021 (UTC)
File:世-order.gif has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
FanNihongo (talk) 23:06, 1 March 2021 (UTC)
- Note: KEPT, the version from @VulpesVulpes42, which should be deleted, was kept after all. FanNihongo (talk) 02:30, 18 February 2022 (UTC)
Copyright status: File:Chisholm -2.png
editCopyright status: File:Chisholm -2.png
This media may be deleted. |
Thanks for uploading File:Chisholm -2.png. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.
If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you. |
This action was performed automatically by AntiCompositeBot (talk) (FAQ) 20:05, 13 March 2021 (UTC)
File:廴-torder.gif has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
I really appreciate your contributions, but @Llf: pointed out that File:鬯-order.gif doesn't match File:鬯-jbw.png. Since the latter one maybe Japan style, would I know the reference of File:鬯-order.gif?
For myself, well, I never cares about the order. EdwardAlexanderCrowley (talk) 07:21, 20 April 2021 (UTC)
- I find out that 鬯's order doesn't match File:鹵-order.gif or 鬱, so maybe a mistake. EdwardAlexanderCrowley (talk) 07:29, 20 April 2021 (UTC)
- Hello @EdwardAlexanderCrowley: Indeed the first to strokes of File:鬯-order.gif are inverted. I'll try to correct it ASAP. Michelet-密是力 (talk) 08:22, 20 April 2021 (UTC)
- Done The file was already corrected. FanNihongo (talk) 02:37, 18 February 2022 (UTC)
Hello again. This file's pronunciation is incorrect. Since the author is not a wikimedian, would you re-record the audio, or just start the deletion process? EdwardAlexanderCrowley (talk) 07:49, 5 May 2021 (UTC)
- Hello @EdwardAlexanderCrowley: The prononciation is correct (from northen france, most probably urban). The only thing (apart from being misnamed) is that the saying is « un adaptateur » (an adaptator) instead of just « adaptateur » - but I would'nt delete it for that. Michelet-密是力 (talk) 08:27, 5 May 2021 (UTC)
- OK. I hope "adapteur" will take the place, instead of simply moving this to Fr-adaptateur.ogg EdwardAlexanderCrowley (talk) 08:41, 5 May 2021 (UTC)
- Please move the page without redirect, thanks. There're bots like DerbethBot recognizing and adding ogg files. EdwardAlexanderCrowley (talk) 03:24, 7 June 2021 (UTC)
- OK. I hope "adapteur" will take the place, instead of simply moving this to Fr-adaptateur.ogg EdwardAlexanderCrowley (talk) 08:41, 5 May 2021 (UTC)
Report
editHello, please take a look at this report: Commons:Administrators' noticeboard#Files named with meaningless/disruptive names (motivated renaming was reverted without any valid reason) as these are serious everyday violations of the Commons rules and protection of meaningless names (in this case, Kalumny which translates as Columns). User Kazimier Lachnovič with filemover rights constantly performs violations of the Commons rules, creates instability issues and protects meaningless names, thus creates confusion. His Commons admin rights previously were lifted, but it is clear that it is not enough. -- Pofka (talk) 17:21, 26 May 2021 (UTC)
Hello Micheletb. Can you update this file? Thanks. —hueman1 (talk • uploads) 14:57, 3 June 2021 (UTC)
- Hello @HueMan1: I would suggest using File:Daily CoViD PT.svg instead to reflect the pandemic evolution, the total deaths/cases does not make sense after a few months.
Commons:Stroke Order Project/Graphics guidelines/Bitmap animations has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this project page, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. |
FanNihongo (talk) 01:11, 30 July 2021 (UTC)
- @Micheletb: 😐Read what is in the deletion request from above, 😦because that is the reason I am telling you this(🙁I will assume you already did that):
- 😠Three months have passed, and I was patient. I was hoping that this situation never happen, 😞but at the end you sadly have disappointed me. I am not waiting for your answer anymore. FanNihongo (talk) 07:07, 1 December 2021 (UTC)
- @FanNihongo: You should master your agressivity if you want to prosper on these projects. The answers to the deletion requests have been quite clear : the pages should be kept and updated as necessary. Michelet-密是力 (talk) 09:35, 1 December 2021 (UTC)
- @Micheletb: 😑Before answering you, I will tell you a little bit of me, I am a person, of which is difficult to read other people's intentions. Especially if that person is from a non English speaking country and is not a native English speaker. I don't mean to offend you, but you are one of those persons.
- Besides I am the type of person, that if you have promised something you have to fulfill it.
- 😒Sorry but in this case the disappointed and the offended person is me. 😠I want to point out that you made a promise saying this: "Just back from a no-ww-wnet zone, I'll have to proofread the whole thing before giving an opinion. Be patient." then, because you left me in the dark I asked this "One final comment: I only ask you for a clarification(not for your opinion, of which I will be patient): (Again)What do you mean by proofread? What will you do exactly? will you try out my method? Will you correct my or your method?". 😒In my opinion you were the one who started all of this.
- 😅With that explanation I hope you understand the aggressiveness shown before. 😀Finally I want to tell you an anecdote. 😐I once met a certain Anglophone user from Germany, he was not an English native speaker, 😞I am sure it was not his intention but at the end he also disappointed me, I am not going to enter into details about what exactly happen, 😕I tried to solve the things many times, but sadly, very late I realized that, no matter what I do, 😧the things with him could never be fixed. So I stopped talking with him. 🙁I hope that doesn't not happen with you.
- 😐Well, thank you for your opinion, 😒but I am still disappointed and that does not compensate it. 😧I do not know if you understand how I feel, but if you disappoint me again, 😔then the better is that I don't speak to you again and do not take what you say seriously. FanNihongo (talk) 04:42, 2 December 2021 (UTC)
- Hi @FanNihongo: I've been working on other subjects and haven't made animated gifs for a while, so I hadn't any opportunity to compare the values of such or such modus operandi. Anyway, on this kind of project you can do pretty much what you want, including modifying the page you want to delete if there is something to modify. Creating another (concurrent) page is generally not a good approach. But deleting a page when there is no good reason to isn't the correct approach. As to your Asperger-like problem you're not the only one, most of them eventually learn how to survive on the internet (the others quit). You can't expect everybody to meet your conditions in a universe where contributions are motivated by good will only. Michelet-密是力 (talk) 05:09, 2 December 2021 (UTC)
- Bonjour @Micheletb: 🙁Thank you for your answer. 🤔Maybe in another circumstances we could get along well, and work in harmony. 😔But sadly this is not the case. 😦There are still many differences to solve between us, and many topics to discuss with you about the SOP. But If it will be this hard to discuss with you and to having an effective communication with you, then we cannot fix those issues. 😒I don't need to explain it but in the deletion request 😞is more than clear why you disappointed me. 🤔I think the problem is that you neglect things or do not read everything that I write to you. 🙁At any rate, I will stop talking to you. 😐And the day when you become less puzzling and more responsible about this things, that day we will talk. 😥Bonne journeé FanNihongo (talk) 07:28, 3 December 2021 (UTC)
- Hi @FanNihongo: I've been working on other subjects and haven't made animated gifs for a while, so I hadn't any opportunity to compare the values of such or such modus operandi. Anyway, on this kind of project you can do pretty much what you want, including modifying the page you want to delete if there is something to modify. Creating another (concurrent) page is generally not a good approach. But deleting a page when there is no good reason to isn't the correct approach. As to your Asperger-like problem you're not the only one, most of them eventually learn how to survive on the internet (the others quit). You can't expect everybody to meet your conditions in a universe where contributions are motivated by good will only. Michelet-密是力 (talk) 05:09, 2 December 2021 (UTC)
- @FanNihongo: You should master your agressivity if you want to prosper on these projects. The answers to the deletion requests have been quite clear : the pages should be kept and updated as necessary. Michelet-密是力 (talk) 09:35, 1 December 2021 (UTC)
File source is not properly indicated: File:Briquet.png
editThis media may be deleted. |
A file that you have uploaded to Wikimedia Commons, File:Briquet.png, is missing information about where it comes from or who created it, which is needed to verify its copyright status. Please edit the file description and add the missing information, or the file may be deleted.
If you created the content yourself, enter If someone else created the content, or if it is based on someone else's work, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you! |
Notification about possible deletion
editSome contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.
If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Affected:
And also:
Yours sincerely, Yann (talk) 21:36, 23 November 2021 (UTC)
File:Ajaccio blason.png has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
File:Ajaccio pseudo.png has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
How we will see unregistered users
editHi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:11, 4 January 2022 (UTC)
Hi! Could you please delete this redirect page? --沈澄心✉ 15:30, 20 February 2022 (UTC)
- Hello 沈澄心 the file (as redirection) seems to be used by some wikiprojects. Why should it be deleted? Michelet-密是力 (talk) 19:12, 20 February 2022 (UTC)
- File:與-bronze-spring.svg is in Spring and Autumn period, not Western Zhou. The redirection makes the glyph shown erroneously on wikt:與. 沈澄心✉ 07:09, 22 February 2022 (UTC)
File:勽-bronze.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Chinese Character illustrations
editHi, thank you for the pictures on the pages for "ACC containing xyz". I have found them helpful in illustrating the etymology.
I have a question about two of them:
Character | Illustration | Meaning / Etymology |
---|---|---|
咢 | Beating a drum / startle | |
各 | Pictograph of ?foot and an opening |
What is the link to the characters for these two pictures? I am not sure.
For the page below, what do you think about these suggestions?:
Page | Original | Suggestion | Reason |
---|---|---|---|
叔 | Your choice is fine - perhaps this isn't worth changing. I think of picking in the sense of 'plucking' a berry from a bush. | ||
反 | hands-climbing-climb-socket-6146846 | Etymology makes me think of the hands of a climber on a wall |
Luke --Lxs602 (talk) 13:22, 21 March 2022 (UTC)
- Hello @Lxs602: The explanation of the picture is in what is represented by the original character ; the French wiktionnary =click on (see wiktionnary : en, fr, ja, zh, ) gives full explanations. Just translate the "type" section into whatever you want. Michelet-密是力 (talk) 13:53, 21 March 2022 (UTC)
- Thank you. I will look at the french wiktionary page, as the explanations are missing from the english wiktionary page. Lxs602 (talk) 14:07, 21 March 2022 (UTC)
- I hope I don't offend you by suggesting different pictures for 反 and 叔. I thought the best thing would be just to ask your opinion. Lxs602 (talk) 14:13, 21 March 2022 (UTC)
- It'OK, I think the one for 叔 (bean picking) is a good one. Michelet-密是力 (talk) 14:22, 21 March 2022 (UTC)
- @Lxs602: On the other hand, 反 would be a bad idea. The original meaning intended is turning one's hand downside up = upside-down, alteration, reverse. Things are complicated... But feel free to add meaningful pictures if you are inspired. Michelet-密是力 (talk) 17:32, 21 March 2022 (UTC)
Sound Logo
editHello,
I am messaging you because a contest for a sound logo for Wikimedia is being developed and your opinion as a Wikimedia Commons admin is appreciated. My team would like to know if it is possible for the top finalist sound logos in the contest to have attribution temporarily hidden from public view until all the votes are final? The idea is to let the public judge the sound logo contestants based on the merit of the logo, not the person or people who made it. Again, any feedback is appreciated.
Thank you,
VGrigas (WMF) (talk) 18:05, 17 June 2022 (UTC)
- Hi @VGrigas (WMF):
- As I understand it, sounds will be created within and for the Sound logo contest, so the "attribution" will be limited to participants. If I'm wrong there may be catches (but not big ones). If I'm right, it's no big deal, the participants need only to accept the special rules.
- For instance, just set as contest rules making clear that :
- (1) Though meant to be published under CC-by-SA, attributions for the sounds will be temporarily hidden from public view until all the votes are final, this rule must be accepted by all participants (penalty of disqualification) ;
- (2) Contributions must be uploaded "anonymously" with respect to participants ids (IP, or one-shot account, or Sock puppet account, or whatever) (penalty of disqualification) ;
- (3) Attributions must be sent simultaneously to the upload (let's say, within 10 minutes - to prevent robberies) through an OTRS ticket, the ticket referring to the contest for a sound logo and mentioning the present dispositions (so that OTRS managers know they must do nothing with respect to file attribution) ;
- (4) The submission of the sound as Sound logo contest candidate can only be made after sending the OTRS ticket (to prevent false attribution) ;
- (5) Submitters may fill the "attribution" for the files after votes are final ; those attributions must be guaranteed by the OTRS ticket number (verify, etc).
- Now, if the contributor is outside the project and cannot assent to these rules, there may be a (small) legal issue, insofar as his sound would have been temporarily published without attribution.
- Another (bigger) issue is that in any case, if a project sound is published without attribution AND under CC-by-SA, anybody could copy it and diffuse it, losing the attribution track.
- To solve both problems I recommand to :
- (2bis) Publish the candidates under a temporary licence saying that "Though meant to be published under CC-by-SA, this file is submitted for the "contest for a sound logo for Wikimedia" ; and attributions for the sounds will be temporarily hidden from public view until all the votes are final ; any reproduction outside this "contest for a sound logo for Wikimedia" project is not authorized". Mention the closing date for better credibility. And, of course, no other licence that would enable to bypass that.
- There still would be that (small) legal issue, insofar as an outsider produced sound would have been temporarily published without attribution. Well, Heck, I'd say I'd react after the project is over in that case... And of course say the file must be deleted if the attribution hasn't got right by then.
- Yours, Michelet-密是力 (talk) 18:51, 17 June 2022 (UTC)
De-adminship warning
editDear Micheletb. I am writing to inform you that you are in danger of losing your admin rights on Commons because of inactivity.
If you want to keep your adminship, you need both to sign at Commons:Administrators/Inactivity section/Aug-Sep 2022 before 13 September, and also to make at least five further admin actions in the following six months. Anyone who does not do so will automatically lose their rights.
You can read the de-admin policy at Commons:Administrators/De-adminship.
Thank you! -- CptViraj (talk) 18:51, 12 August 2022 (UTC)
Meaning of stars in Triple-Junction drawing
editMicheletb, you are listed as the creator of the drawing at https://commons.wikimedia.org/wiki/File:Points_triples_entre_plaques_continentales.svg which shows the major tectonic plates, the faults where they meet, and the Triple Junctions where three plates meet. When I look at it at high resolution, I see many gold stars, some near faults and some far away. Can you update the legend to tell a viewer what the stars mean? Thank you! SandyJax (talk) 04:29, 24 January 2023 (UTC)
- Hello @SandyJax: I have no idea and can't remember where the underlying map was. Sorry. Michelet-密是力 (talk) 05:58, 24 January 2023 (UTC)
Round 1 of Picture of the Year 2022 voting is open!
editRead this message in your language
Dear Wikimedian,
Wikimedia Commons is happy to announce that the 2022 Picture of the Year competition is now open. This year will be the seventeenth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2022) to produce a single Picture of the Year.
Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year are all entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.
For your convenience, we have sorted the images into topical categories. Two rounds of voting will be held: In the first round, you may vote for as many images as you like. The top 30 overall and the two most popular images in each category will continue to the final. In the final round, you may vote for just three images to become the Picture of the Year.
Round 1 will end on UTC.
Thanks,
the Wikimedia Commons Picture of the Year committee
You are receiving this message because you voted in the 2021 Picture of the Year contest.
Delivered by MediaWiki message delivery (talk) 09:14, 20 April 2023 (UTC)
De-adminship warning
editDear Micheletb. I am writing to inform you that you are in danger of losing your admin rights on Commons because of inactivity.
If you want to keep your adminship, you need both to sign at Commons:Administrators/Inactivity section/Aug-Sep 2023 before 13 September, and also to make at least five further admin actions in the following six months. Anyone who does not do so will automatically lose their rights.
You can read the de-admin policy at Commons:Administrators/De-adminship.
Thank you! -- CptViraj (talk) 19:32, 12 August 2023 (UTC)
Copyright status: File:Ruqa'a لم.png
editCopyright status: File:Ruqa'a لم.png
This media may be deleted. |
Thanks for uploading File:Ruqa'a لم.png. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.
If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you. |
This action was performed automatically by AntiCompositeBot (talk) (FAQ) 18:05, 29 April 2024 (UTC)
Round 1 of Picture of the Year 2023 voting is open!
editDear Wikimedian,
Wikimedia Commons is happy to announce that the 2023 Picture of the Year competition is now open. This year will be the eighteenth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2023) to produce a single Picture of the Year.
Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year are all entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.
For your convenience, we have sorted the images into topical categories. Two rounds of voting will be held: In the first round, you may vote for as many images as you like. The top 30 overall and top 5% of most popular images in each category will continue to the final. In the final round, you may vote for just three images to become the Picture of the Year.
Round 1 will end on UTC.
Thanks,
the Wikimedia Commons Picture of the Year committee
You are receiving this message because you voted in the 2022 Picture of the Year contest.
MediaWiki message delivery (talk) 17:01, 1 October 2024 (UTC)
Round 2 of Picture of the Year 2023 voting is open!
editRead this message in your language
Dear Wikimedian,
You are receiving this message because we noticed that you previously voted in the Picture of the Year contest. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2023) to produce a single Picture of the Year.
Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.
In this second and final round, you may vote for a maximum of three images. The image with the most votes will become the Picture of the Year 2023.
Round 2 will end at UTC.
If you have already voted for Round 2, please ignore this message.
Thanks,
the Wikimedia Commons Picture of the Year committee
MediaWiki message delivery (talk) 17:10, 16 October 2024 (UTC)
Vitrail 108 de la cathédrale de Chartres
editBonjour et merci pour ton énorme travail sur cet article,
Je suis en train de relier Commons, Wikidata et Palissy sur ces éléments. Dans Category:Stained glass windows of the choir of Cathédrale Notre-Dame de Chartres baie 108, l'image File:Chartres 108.jpg ne me semble pas en cohérence avec Palissy et l'image de gauche présentant les baies 108, 110, 112, 114. Mais peut-être me suis-je moi-même trompé pour cette numérotation...
Dans l'attente de ton éclairage avisé, bien cordialement, Le Passant (talk) 09:40, 17 October 2024 (UTC).
- Bonjour @Le Passant:
- Le File:Cathédrale de Chartres-Plan de situation des vitraux.jpg indique bien que la baie 108 est à gauche de la 110, et sur l'image de File:Chartres 108.jpg on voit sur la droite la tête avec une pierre autour du cou de la File:Vitrail Chartres-110g.jpg, donc pour moi c'est correct (du moins par rapport à la 110). Et la notice renvoie sur une grisaille, ce qui est cohérent. Bonnes réflexions, Michelet-密是力 (talk) 10:10, 17 October 2024 (UTC)
- Merci de ce retour rapide ! Désolé pour ma sollicitation intempestive, mais, après une recherche complémentaire, ma question est infondée (sens de lecture des numéros impairs erroné). Bonne continuation, Le Passant (talk) 14:27, 17 October 2024 (UTC).