Open main menu


Senator2029





Contents

Thanks for the barnstarEdit

Thank you for giving me a barnstar. I really didn’t think it would, but it means a lot to me! Ariadacapo (talk) 12:04, 25 January 2013 (UTC)

Picture of the Year 2013 R1 AnnouncementEdit

Round 1 of Picture of the Year 2013 is open!Edit

 
2012 Picture of the Year: A pair of European Bee-eaters in Ariège, France.

Dear Wikimedians,

Wikimedia Commons is happy to announce that the 2013 Picture of the Year competition is now open. This year will be the eighth 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 (2013) 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 most popular image in each category will continue to the final. In the final round, you may vote for just one image to become the Picture of the Year.

Round 1 will end on . Click here to learn more and vote »

Thanks,
the Wikimedia Commons Picture of the Year committee

You are receiving this message because you voted in the 2012 Picture of the Year contest.

Picture of the Year 2013 R2 AnnouncementEdit

Round 2 of Picture of the Year 2013 is open!Edit

 
2012 Picture of the Year: A pair of European Bee-eaters in Ariège, France.

Dear Wikimedians,

Wikimedia Commons is happy to announce that the second round of the 2013 Picture of the Year competition is now open. This year will be the eighth 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 (2013) 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.

There are two total rounds of voting. In the first round, you voted for as many images as you liked. The top 30 overall and the most popular image in each category have continued to the final. In the final round, you may vote for just one image to become the Picture of the Year.

Round 2 will end on . Click here to learn more and vote »

Thanks,
the Wikimedia Commons Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

This Picture of the Year vote notification was delivered by MediaWiki message delivery (talk) 19:23, 22 February 2014 (UTC)

Picture of the Year 2013 Results AnnouncementEdit

Picture of the Year 2013 ResultsEdit

 
The 2013 Picture of the Year. View all results »

Dear Senator2029,

The 2013 Picture of the Year competition has ended and we are pleased to announce the results: We shattered participation records this year — more people voted in Picture of the Year 2013 than ever before. In both rounds, 4070 different people voted for their favorite images. Additionally, there were more image candidates (featured pictures) in the contest than ever before (962 images total).

  • In the first round, 2852 people voted for all 962 files
  • In the second round, 2919 people voted for the 50 finalists (the top 30 overall and top 2 in each category)

We congratulate the winners of the contest and thank them for creating these beautiful images and sharing them as freely licensed content:

  1. 157 people voted for the winner, an image of a lightbulb with the tungsten filament smoking and burning.
  2. In second place, 155 people voted for an image of "Sviati Hory" (Holy Mountains) National Park in Donetsk Oblast, Ukraine.
  3. In third place, 131 people voted for an image of a swallow flying and drinking.

Click here to view the top images »

We also sincerely thank to all 4070 voters for participating and we hope you will return for next year's contest in early 2015. We invite you to continue to participate in the Commons community by sharing your work.

Thanks,
the Picture of the Year committee

You are receiving this message because you voted in the 2013 Picture of the Year contest.

Delivered by MediaWiki message delivery (talk) 23:00, 26 March 2014 (UTC)

Irrationally large SVG imageEdit

Hi Senator2029, you have marked my image “Welcome in sixteen languages.svg” as being “irrationally large.” I understand this and other drawbacks of the method used by me, and would really like to use the SVG <text> element thus reducing file size, making text searchable, etc.

On the other hand I want this image to look exactly as it does now and therefore cannot rely on the Wikimedia SVG fonts. The following fonts would be needed but aren’t present: “Gentium Plus” (or some other version of “Gentium”) for Latin and Cyrillic text; “FZKaiS-Extended” for simplified Chinese; “全字庫正楷體” for traditional Chinese; “EPSON 正楷書体M” for Japanese; and “Symbola” for the hand. (“Scheherazade” for Arabic is there.)

The SVG solution with the <text> element would be to define an SVG font in the same file using the SVG <‌font> element and its sub-elements (<glyph>, <hkern>, etc.). This is certainly feasible, but it would take me a long time to get it right — what is most difficult is to exclude redundant font information from the original fonts while retaining everything that is required for this image. As I do not want my efforts to be a waste of time my question is: Does the current MediWiki rendering software display embedded SVG fonts correctly? —LiliCharlie (talk) 16:34, 31 March 2014 (UTC)

Tech News: 2014-35Edit

09:21, 25 August 2014 (UTC)

Tech News: 2014-36Edit

07:49, 1 September 2014 (UTC)

Tech News: 2014-37Edit

09:33, 8 September 2014 (UTC)

Tech News: 2014-38Edit

08:34, 15 September 2014 (UTC)

File tagging File:Security Now.jpgEdit

беларуская (тарашкевіца)‎ | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | español | euskara | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | italiano | 日本語 | 한국어 | lietuvių | македонски | മലയാളം | मराठी | Plattdüütsch | Nederlands | norsk | polski | português | română | русский | sicilianu | slovenčina | slovenščina | српски / srpski | svenska | Türkçe | українська | اردو | Tiếng Việt | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media was probably deleted.
Thanks for uploading File:Security Now.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or send an email with copy of a written permission to OTRS (permissions-commons@wikimedia.org). This also applies if you are the author yourself.

Please see this page for more information on how to confirm permission, and Commons:Permission if you would like to understand why we ask for permission when uploading work that is not your own.

The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the OTRS-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Security Now.jpg]]) and the above demanded information in your request.

Leyo 09:00, 15 September 2014 (UTC)

Tech News: 2014-39Edit

09:05, 22 September 2014 (UTC)

Tech News: 2014-40Edit

09:44, 29 September 2014 (UTC)

Tech News: 2014-41Edit

06:10, 6 October 2014 (UTC)

Tech News: 2014-42Edit

08:53, 13 October 2014 (UTC)

Tech News: 2014-43Edit

13:47, 20 October 2014 (UTC)

Tech News: 2014-44Edit

05:20, 27 October 2014 (UTC)

Tech News: 2014-45Edit

17:28, 3 November 2014 (UTC)

Tech News: 2014-46Edit

15:00, 10 November 2014 (UTC)

Categories removed from File:Brokaw Bullet.jpgEdit

Hi, thanks for your comment on my talk page. First, my edit to the image file followed the categorisation of two additional images of the Brokaw Bullet, that were previously only crudely categorised as "Aircraft". I assume that you are already familiar with the Wikimedia Commons policy article on Categories, in which the section COM:OVERCAT is located. The article explains how the primary purpose of categorising here is to facilitate the finding of files via a hierarchical schema (as opposed to a flat keyword schema). In the case of the subject image, Three-wheeled motor vehicles is inappropriate, because the Brokaw Bullet (eventually) comes under Aircraft, which already comes under Vehicles, and an aircraft is not classified as a motor vehicle anyway. Vehicles in Florida is inappropriate, because the image is already categorised as a type of vehicle, and the location is in a category under Florida. Blue and white aircraft is inappropriate, because it does not satisfy the aim of being able to find files; if that category is ever populated with all blue and white aircraft images (many thousands), it would not be easy for anyone to find what they might be seeking. In this case, and in the next few minutes, I plan to categorise the three Brokaw Bullet images into the more precise method we use for most aircraft images, and if you apply Category:Blue and white aircraft, I doubt that it would materially help anyone without the knowledge already contained in the category tree, such as aircraft make/model, configuration, registration, and exact location. Many people apply the categories of colour to aircraft images, and we often tolerate them to avoid conflicts, but the above parameters for aircraft makes colour redundant. If the subject were an item with no other useful context (eg blue and white balls), they might have a purpose, but not for aircraft in a highly defined schema for aircraft images. I hope this helps you understand my rationale. There are many aircraft images needing basic or comprehensive categorising, and I'm sure we would all welcome your assistance in categorising, eg all those that (should) come under Florida Air Museum.PeterWD (talk) 11:51, 16 November 2014 (UTC)

Tech News: 2014-47Edit

18:28, 17 November 2014 (UTC)

Tech News: 2014-48Edit

19:31, 24 November 2014 (UTC)

An update on the File metadata cleanup driveEdit

Hello Senator2029,

I wanted to thank you for offering to help with the File metadata cleanup drive on Commons. We now have numbers to measure the amount of Commons files missing machine-readable information. Most of the files here have a license template, but there still about 500,000 remaining files (out of 24 million) missing an {{information}} template, and that's where your help would be invaluable.

We're currently trying to find groups of files whose description pages are alike, so that we can use bots to automatically take that information and put it into an information template. If you still want to help, it would be great if you could look at the list of files and see if you can find such groups. You can also use the no_information tool to limit the results by uploader, or the first characters of the file name; this can help identify batch uploads.

Once you find groups of files with information in the same order or format, you can add a section to the bot requests page, so that a bot can go through them and fix them all automatically (or you can do it yourself if you have a bot, or with VisualFileChange).

In 10 days, we've already managed to add information templates to over 10% of the 500,000 remaining files. I'm hoping you can help us keep this momentum and get through the rest so we can get rid of this backlog once and for all :)

Thank you, and I wish you happy end-of-year holidays if you celebrate them! Guillaume (WMF) (talk) 19:13, 23 December 2014 (UTC)


File:Ben Carson, MD.jpgEdit

 
File:Ben Carson, MD.jpg 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Pdxuser (talk) 18:04, 5 September 2015 (UTC)

Categories for File:Gtech.jpgEdit

The file is in Category:Office buildings in Rhode Island, which is a subcat of Category:Buildings in Providence, both technically (the cat tag in the former) painfully obviously in concept. It seems like a fairly blatant an example of what COM:OVERCAT tells us not to do. Could you clarify your reasoning here? DMacks (talk) 08:14, 5 October 2015 (UTC)

Round 2 of Picture of the Year 2015 is open!Edit

You are receiving this message because you voted in R1 of the 2015 Picture of the Year contest.

Dear Senator2029,

Wikimedia Commons is happy to announce that the second round of the 2015 Picture of the Year competition is now open. This year will be the tenth 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 (2015) 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.

There are two total rounds of voting. In the first round, you voted for as many images as you liked. In Round 1, there were 1322 candidate images. There are 56 finalists in Round 2, comprised of the top 30 overall as well as the top #1 and #2 from each sub-category. In the final round, you may vote for just one or maximal three image to become the Picture of the Year.

Round 2 will end on 28 May 2016, 23:59:59 UTC.

Click here to vote »

Thanks,
-- Wikimedia Commons Picture of the Year committee 09:43, 22 May 2016 (UTC)

Copyright status: File:Seminole Towne Center logo.svgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Seminole Towne Center logo.svg. 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 OTRS 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.

Yours sincerely, Magog the Ogre (talk) (contribs) 04:16, 26 July 2016 (UTC)

Copyright status: File:Usc1010250 145.jpgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Usc1010250 145.jpg. 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 OTRS 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.

Yours sincerely, Magog the Ogre (talk) (contribs) 03:05, 9 August 2016 (UTC)

File:Stihl logo.jpgEdit

 
File:Stihl logo.jpg 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Techtri (talk) 20:54, 20 September 2016 (UTC)


Code issues in User:Senator2029/common.cssEdit

Hi Senator2029, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Senator2029/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 17 new prettyCss issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. WARNING: suggest-relative-unit:px: line 14 char number 26 - Evidence: 2px
  2. WARNING: suggest-remove-unit:px: line 26 char number 15 - Evidence: 0px
  3. WARNING: suggest-relative-unit:px: line 26 char number 15 - Evidence: 0px
  4. WARNING: suggest-remove-unit:px: line 30 char number 14 - Evidence: 0px
  5. WARNING: suggest-relative-unit:px: line 30 char number 14 - Evidence: 0px
  6. WARNING: suggest-relative-unit:px: line 30 char number 18 - Evidence: 1px
  7. WARNING: suggest-relative-unit:px: line 30 char number 22 - Evidence: 1px
  8. WARNING: suggest-remove-unit:px: line 31 char number 13 - Evidence: 0px
  9. WARNING: suggest-relative-unit:px: line 31 char number 13 - Evidence: 0px
  10. WARNING: suggest-relative-unit:px: line 34 char number 9 - Evidence: 1px
  11. WARNING: invalid-value: line 36 char number 19 - Evidence: -moz-linear-gradient
  12. WARNING: suggest-remove-unit:px: line 41 char number 14 - Evidence: 0px
  13. WARNING: suggest-relative-unit:px: line 41 char number 14 - Evidence: 0px
  14. WARNING: suggest-relative-unit:px: line 41 char number 18 - Evidence: 1px
  15. WARNING: suggest-relative-unit:px: line 41 char number 22 - Evidence: 1px
  16. WARNING: suggest-relative-unit:px: line 44 char number 9 - Evidence: 31px
  17. WARNING: suggest-relative-unit:px: line 66 char number 13 - Evidence: 1px
  18. WARNING: invalid-value: line 68 char number 23 - Evidence: -moz-linear-gradient

Your CommonsMaintenanceBot (talk) at 09:05, 27 December 2016 (UTC).


Code issues in User:Senator2029/common.cssEdit

Hi Senator2029, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Senator2029/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new prettyCss issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. WARNING: suggest-relative-unit:px: line 14 char number 26 - Evidence: 2px
  2. WARNING: suggest-remove-unit:px: line 26 char number 15 - Evidence: 0px
  3. WARNING: suggest-relative-unit:px: line 26 char number 15 - Evidence: 0px
  4. WARNING: suggest-remove-unit:px: line 30 char number 14 - Evidence: 0px
  5. WARNING: suggest-relative-unit:px: line 30 char number 14 - Evidence: 0px
  6. WARNING: suggest-relative-unit:px: line 30 char number 18 - Evidence: 1px
  7. WARNING: suggest-relative-unit:px: line 30 char number 22 - Evidence: 1px
  8. WARNING: suggest-remove-unit:px: line 31 char number 13 - Evidence: 0px
  9. WARNING: suggest-relative-unit:px: line 31 char number 13 - Evidence: 0px
  10. WARNING: suggest-relative-unit:px: line 34 char number 9 - Evidence: 1px
  11. WARNING: invalid-value: line 36 char number 19 - Evidence: -moz-linear-gradient
  12. WARNING: suggest-remove-unit:px: line 41 char number 14 - Evidence: 0px
  13. WARNING: suggest-relative-unit:px: line 41 char number 14 - Evidence: 0px
  14. WARNING: suggest-relative-unit:px: line 41 char number 18 - Evidence: 1px
  15. WARNING: suggest-relative-unit:px: line 41 char number 22 - Evidence: 1px
  16. WARNING: suggest-relative-unit:px: line 44 char number 9 - Evidence: 31px
  17. WARNING: suggest-relative-unit:px: line 66 char number 13 - Evidence: 1px
  18. WARNING: invalid-value: line 68 char number 23 - Evidence: -moz-linear-gradient
  19. WARNING: font-family-one-generic: line 78 char number 3 - Evidence: font-family

Your CommonsMaintenanceBot (talk) at 19:13, 29 January 2017 (UTC).

Copyright status: File:AtlasGlobal logo.pngEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:AtlasGlobal logo.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 OTRS 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.

Yours sincerely, Magog the Ogre (talk) (contribs) 02:53, 4 February 2017 (UTC)

SVG (Scalable Vector Graphics)Edit

беларуская (тарашкевіца)‎ | Deutsch | English | español | français | hrvatski | italiano | 日本語 | português | português do Brasil | македонски | ಕನ್ನಡ | ತುಳು | +/−

 
Thank you for uploading some images! Did you know that Wikimedia Commons recommends the SVG (Scalable Vector Graphics) format for certain types of images? Scalable Vector Graphics are designed to look appropriate at any scale, and SVG images are easier to modify and translate, helping Wikimedia to distribute knowledge to all of the world. A lot of modern programs support SVG export. If you encountered problems or have questions, don't hesitate to ask me, a member of the Graphic Lab, or the Graphics village pump. Uploading images in SVG format isn't mandatory, but it would help. (To avoid any misunderstandings, please don't just put raster images into a svg container as embedded raster.) Thanks, and happy editing!

EugeneZelenko (talk) 15:36, 4 February 2017 (UTC)

Copyright status: File:Relay Engineering logo.pngEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Relay Engineering logo.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 OTRS 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.

Yours sincerely, Magog the Ogre (talk) (contribs) 04:00, 9 February 2017 (UTC)

Category:Ogv_videos_of_yeastEdit

grendel|khan 10:06, 9 February 2017 (UTC)

File:Idaho State University wordmark.pdfEdit

 
File:Idaho State University wordmark.pdf 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Ras67 (talk) 19:50, 27 February 2017 (UTC)

Notification about possible deletionEdit

 
Some 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Affected:

And also:

Yours sincerely EugeneZelenko (talk) 15:26, 7 March 2017 (UTC)

Copyright status: File:Hospital Records logo horizontal.pngEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Hospital Records logo horizontal.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 OTRS 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.

Yours sincerely, Magog the Ogre (talk) (contribs) 05:42, 8 March 2017 (UTC)

File:Find A Grave logo.gifEdit

 
File:Find A Grave logo.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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Sebastian Wallroth (talk) 20:06, 8 March 2017 (UTC)

Collaboration products newsletter: 2017-03Edit

17:02, 20 March 2017 (UTC)

Collaboration products newsletter: 2017-04Edit

13:04, 18 April 2017 (UTC)

Image without licenseEdit

File:Tweakers logo.svgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 17:05, 29 April 2017 (UTC)

Collaboration products newsletter: 2017-05Edit

15:19, 16 May 2017 (UTC)

Your VFC installation method is deprecatedEdit

Hello Senator2029, we are aware that using the old installation method of VFC (via common.js, which you are using) may not work reliably anymore and can break other scripts as well. A detailed explanation can be found here. Important: To prevent problems please remove the old VFC installation code from your common.js and instead enable the VFC gadget in your preferences. Thanks! --VFC devs (q) 16:24, 22 May 2017 (UTC)

File source is not properly indicated: File:Elon University primary wordmark 2016 hi-res.pngEdit

العربية | asturianu | беларуская (тарашкевіца)‎ | বাংলা | català | čeština | dansk | Deutsch | Ελληνικά | English | español | euskara | فارسی | suomi | français | galego | עברית | magyar | italiano | 日本語 | 한국어 | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | polski | português | português do Brasil | русский | sicilianu | slovenčina | slovenščina | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
A file that you have uploaded to Wikimedia Commons, File:Elon University primary wordmark 2016 hi-res.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 {{own}} as the source. If you did not add a licensing template, you must add one. You may use, for example, {{self|GFDL|cc-by-sa-all}} or {{Cc-zero}} to release certain rights to your work.

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.

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!

Corkythehornetfan (ping me) 07:50, 8 June 2017 (UTC)

Collaboration products newsletter: 2017-06Edit

08:41, 23 June 2017 (UTC)

Image without licenseEdit

File:Deluxe D logo 2016.svgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 21:33, 28 June 2017 (UTC)

Collaboration products newsletter: 2017-07Edit

16:43, 24 July 2017 (UTC)

Copyright status: File:Allina Health logo horiz.svgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Allina Health logo horiz.svg. 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 OTRS 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.

Magog the Ogre (talk) (contribs) 20:21, 27 July 2017 (UTC)

File:Amazon Prime logo.jpgEdit

 
File:Amazon Prime logo.jpg 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Louperivois Ψ @ 18:56, 8 August 2017 (UTC)

Image without licenseEdit

File:Adminsys wordmark.pngEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 20:03, 11 August 2017 (UTC)


File:170620-N-N0824-001.JPGEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 03:33, 18 August 2017 (UTC)


File:Ngulogoeng.svgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 20:11, 29 August 2017 (UTC)


File:Ouzoud Waterfall.jpgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 16:39, 21 September 2017 (UTC)

Global Collaboration products newsletter: 2017-09Edit

17:10, 29 September 2017 (UTC)

File:Binghamton University State University of New York logo (7).jpgEdit

 
File:Binghamton University State University of New York logo (7).jpg 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

128.226.104.52 20:08, 30 October 2017 (UTC)

Global Collaboration products newsletter: 2017-11Edit

15:35, 21 November 2017 (UTC)

Global Collaboration products newsletter: 2017-12Edit

14:31, 19 December 2017 (UTC)

Global Collaboration products newsletter: 2018-01Edit

00:56, 25 January 2018 (UTC)

Image without licenseEdit

File:Hershel "Woody" Williams provides remarks (3820663).jpgEdit

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Esperanto | español | فارسی | suomi | français | galego | hrvatski | magyar | íslenska | italiano | 日本語 | македонски | മലയാളം | Nederlands | norsk nynorsk | polski | português | português do Brasil | русский | sicilianu | slovenščina | svenska | українська | 中文(简体)‎ | 中文(繁體)‎ | +/−


There seems to be a problem regarding the description and/or licensing of this particular file. It has been found that you've added in the image's description only a Template that's not a license and although it provides useful information about the image, it's not a valid license. Could you please resolve this problem, adding the license in the image linked above? You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file. This page may give you more hints on which license to choose. Thank you.

This message was added automatically by MifterBot (TalkContribsOwner), if you need some help about it please read the text above again and follow the links in it, if you still need help ask at the   Commons:Help desk in any language you like to use. --MifterBot (TalkContribsOwner) 15:33, 18 February 2018 (UTC)

Collaboration products newsletter: 2018-02Edit

11:29, 5 March 2018 (UTC)

File:Salt Lake County, Utah logo.pngEdit

 
File:Salt Lake County, Utah logo.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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Taivo (talk) 11:03, 22 March 2018 (UTC)

Collaboration products newsletter: 2018-03Edit

12:25, 26 March 2018 (UTC)

Edit that broke a linkEdit

Hi. Could you provide an explanation for this edit from September last year? -- (talk) 21:22, 8 April 2018 (UTC)

File:Ayn Rand.jpgEdit

 
File:Ayn Rand.jpg 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Kelly (talk) 02:12, 24 April 2018 (UTC)

Interwiki link syntaxEdit

Greetings, Senator2029! You recently edited an interwiki link between a commons image and an English wikipedia article. ([Here] and [here], changing the syntax from:
1. "The Israeli symbol for [[:en:Highway 443 (Israel)|Road 443]]" to
2. "{{en|The Israeli symbol for [[:en:Highway 443 (Israel)|Road 443]]}}".

Over the years, I have created many interwiki links (commons to English as well as English to other languages) using the first syntax. I am no expert in markup language; I merely copy the markup used in other articles and it works. Is there an advantage to my changing all of my interwiki links to the second syntax? Perhaps you could point me to the help page or the template page describing the syntax which you are using. Kind regards, @Efrat (talk) 14:37, 24 May 2018 (UTC)

@Atefrat: Thank you for writing to ask. I don't think there is a change in the link syntax (I'll double check that), but I just wrapped in in a template which marks the whole sentence as English language text.}}. This is probably most useful when a description contains other languages as well, because if a logged in user has set a language preference, then only that will be displayed instead of it showing all the available languages. My no means is using{{En}} mandatory, though I often get in a mindset to make all the details of a file page perfect. Senator2029 ➔ “Talk” 13:06, 31 May 2018 (UTC)

Latest message for Collaboration team newsletter; Growth team's newsletter inviteEdit

Hello

Sorry to use English if that's not your favorite language.

You are receiving this message because you were reading the Collaboration team newsletter.

The Collaboration team doesn't longer exists. That team was working on building features that encourage collaboration. This is the latest message for that newsletter.

The Growth Team, formed in July 2018, supports some former Collaboration projects. The Growth Team's main objective is to ease new editors' first steps on wikis, through software changes. You can discover all objectives and missions of the Growth team on its page.

If you wish to be informed about Growth team's updates about easing new users first steps, you can subscribe to the new list to get updates. The first message from Growth –with a call for feedback on a new project– will be posted in a few days!

If you have questions or you want to share experiences made on your wiki about new users' first steps, please post them on the team talk page, in any language.

On behalf of the Growth team, Trizek (WMF) (talk) 10:29, 22 August 2018 (UTC)


Code issues in User:Senator2029/common.cssEdit

Hi Senator2029, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Senator2029/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 3 new prettyCss issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. WARNING: suggest-relative-unit:px: line 14 char number 26 - Evidence: 2px
  2. WARNING: suggest-relative-unit:px: line 23 char number 19 - Evidence: 2px
  3. WARNING: suggest-relative-unit:px: line 26 char number 12 - Evidence: 3px
  4. WARNING: suggest-relative-unit:px: line 44 char number 12 - Evidence: 1px
  5. WARNING: suggest-relative-unit:px: line 47 char number 14 - Evidence: 2px
  6. WARNING: suggest-relative-unit:px: line 47 char number 18 - Evidence: 2px
  7. WARNING: suggest-relative-unit:px: line 47 char number 22 - Evidence: 5px
  8. WARNING: font-family-one-generic: line 67 char number 3 - Evidence: font-family

Your CommonsMaintenanceBot (talk) at 08:29, 23 August 2018 (UTC).

Growth team updates #1Edit

Welcome to the first newsletter for the new Growth team!  

The Growth Team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects. We will be starting with Wikipedias, but we hope these changes will benefit every community.

8 ideas we consider: tell us what you think about them!

We are considering new features to build, that could retain new editors in mid-size Wikipedias. We will be testing new ideas in Czech and Korean Wikipedias, and then we'll talk to more communities (yours!) about adopting the ideas that work well.

We have posted the 8 ideas we are considering. We would really appreciate your thoughts and the thoughts from your community. Please share the ideas, and tell us what do you and your community think of those ideas before September 9.

Share your experiences with newcomers

We want to hear about what is working and what is not working for new contributors in your wiki. We also want to hear any reactions, questions, or opinions on our work. Please post on the team’s talk page, in any language!

Learn more about us

You can visit our team page to find out why our team was formed and how we are thinking about new editors, and our project page for detailed updates on the first project we'll work on.

Growth team's newsletter prepared by the Growth team and posted by botGive feedbackSubscribe or unsubscribe.

Growth team updates #2Edit

Coraceros Polo ClubEdit

Sorry but you are wrong. The logo is mine, I did it based on a free image (see here) and also it was inspired on the real logo (see here), but is not an official logo. As a result, the file Coraceros Polo Club logo.png is a fictional logo. --Juanchocarbonero (talk) 05:01, 16 October 2018 (UTC)

What is the purpose of uploading a logo if it isn't real? And the file name should and description should say so, otherwise it is easy for someone to think it is real. I will withdraw the speedy delete request. Senator2029 ➔ “Talk” 05:12, 16 October 2018 (UTC)
I understand that is not very useful but its a representative image. Wikimedia Commons has a lot of fictional logos and this is abailable. Im going to edite the file name too. But at present the description of the image explains this situation too. --Juanchocarbonero (talk) 05:25, 16 October 2018 (UTC)

Category:Law_firm_logosEdit

-- numbermaniac (talk) 06:41, 1 November 2018 (UTC)

Growth team updates #3Edit

Welcome to the third newsletter for the new Growth team!  

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

Two Growth team projects to be deployed in next two weeks

We will be deploying the "Understanding first day" and "Personalized first day" projects on Czech and Korean Wikipedias in the coming weeks. See the new project pages below for full details on the projects, and our project updates page for their progress.

  • Understanding first day: learn about the actions new editors take right after creating their accounts. We will be careful with user privacy, and we hope to share initial results in December.
  • Personalized first day: learn about new editors' objectives by adding some optional questions to the new editor’s registration process, and personalizing their onboarding. We hope to share initial results in December.

Third Growth team project begins

  • Focus on help desk: direct newcomers to the local help desks where they can ask questions to help them make their first edits. We hope to have an initial experiment running in December.

Best practices for helping newcomers

We are going to direct newcomers to help desks. But what's the best way to reply to a newcomer there? We have gathered some best practices for successful interactions, based on community experiences and some external documentation. The page has also been reviewed by some experienced community members who suggested some changes. That page is now open for translations. Comments and suggestions are still welcome!

We are still looking for volunteers

Do you want to participate to our experiments? We are looking for new communities to work with us (especially a new mid-size wiki), and people to become ambassadors to help us to communicate with the different communities. Discover how you can involve yourself or your community.

Also, please share this update with your community and interested people!

Learn more about us

You can visit our team page to find out why our team was formed and how we are thinking about new editors, and our project page for detailed updates on the projects we'll work on.

Growth team's newsletter prepared by the Growth team and posted by bot, 13:30, 7 November 2018 (UTC) • Give feedbackSubscribe or unsubscribe.

Growth team updates #4Edit

Welcome to the fourth newsletter for the new Growth team!  

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

We need your feedback!

We have two requests for community members:

  1. Now that data is coming in for the welcome survey, we are planning how to use that data to personalize the newcomer's first day. See our current thoughts here, and join the conversation here.
  2. Try out the help panel's interactive prototype, and read about how we're planning to roll it out, and post any thoughts or reactions here.

Two Growth team projects have been deployed (detailed updates here)

  • Personalized first day (welcome survey) was deployed on November 20 on both Czech and Korean Wikipedias.
    • The survey is now being shown to half of new users (A/B test). Responses are being recorded in the database. We'll report on initial results during December.
    • We are planning to test a second version of the survey, called "Variation C", which we think will maximize the number of users who complete the survey and stay on the wiki.
    • The original objective of this project was to give newcomers the materials they need to achieve their goals, and so now we are currently planning how we will use the information collected in the welcome survey to personalize the newcomer's experience. We hope community members will read our current thinking and join the conversation here. Some of the plans we are considering include:
      • Making it easy for newcomers to see editing activity around the topic areas in which they indicated that they're interested.
      • Connecting interested newcomers to experienced editors.
      • Surfacing the help content most relevant to the reason for which the newcomers created their accounts.
  • Understanding first day (EditorJourney) was deployed on November 15 on both Czech and Korean Wikipedias. It has been done after a longer security review and final testing than expected. Data is now being recorded for all new users on those wikis, and we've been auditing the data and preparing to make initial reports during December. Stay tuned for the next newsletter!

Help panel is under construction

  • Focus on help desk (help panel) is planned to be deployed during the week of January 7 on both Czech and Korean Wikipedias.
  • This interactive prototype is the best way to see the design and wording in the feature.
  • We ran live user tests on the prototype, with results posted here.
  • In addition to giving the ability to ask a question, the help panel will also contain a set of links to existing help content. Our ambassadors on Czech and Korean Wikipedias are determining the right initial set of most helpful links in this task.
  • We encourage community members to try out the prototype and read about the rules for who will get the feature, and add any thoughts to this discussion.

We are still looking for volunteers

Do you want to participate to our experiments? We are looking for new communities to work with us (especially a new mid-size wiki), and people to become ambassadors to help us to communicate with the different communities. Discover how you can involve yourself or your community.

Also, please share this update with your community and interested people!

Learn more about us

You can visit our team page to find out why our team was formed and how we are thinking about new editors, and our project updates page for detailed updates on the projects we work on.

Growth team's newsletter prepared by the Growth team and posted by bot, 09:31, 7 December 2018 (UTC) • Give feedbackSubscribe or unsubscribe.

Ronald RaddeEdit

Hello. I believe the moves you have made from Ronald Radde to Ronald Radd are wrong. They are different people. The former is a Brazilian play writer [274]. Can you please undo? Thanks. --Joalpe (talk) 20:45, 30 December 2018 (UTC)

  Fixed – Created Category:Ronald Radde, and moved all files to it. Thank you for bringing this to my attention. Senator2029 05:52, 31 December 2018 (UTC)

Growth team updates #5Edit

Welcome to the fifth newsletter for the new Growth team!  

The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.

New projects for discussionEdit

We began the "Personalized first day" project with the welcome survey so that we could gather information about what newcomers are trying to accomplish. The next step is to use that information to create experiences that help the newcomers accomplish their goal – actually personalizing their first day. We asked for community thoughts in the previous newsletter, and after discussing with community members and amongst our team, we are now planning two projects as next steps: "engagement emails" and "newcomer homepage".

  • Engagement emails: this project was first discussed positively by community members here back in September 2018, and the team how has bandwidth to pursue it. The idea is that newcomers who leave the wiki don't get encouraged to return to the wiki and edit. We can engage them through emails that send them the specific information they need to be successful – such as contact from a mentor, the impact of their edits, or task recommendations. Please read over the project page, and comment on its discussion page with any ideas, questions, or concerns. Do you think this is a good idea? Where could we go wrong?
  • Newcomer homepage: we developed the idea for this project after analyzing the data from the welcome survey and EditorJourney datasets. We saw that many newcomers seem to be looking for a place to get started – a place that collects their past work, options for future work, and ways to learn more. We can build this place, and it can connect to the engagement emails. The content of both could be guided by what newcomers say they need during their welcome survey, and contain things like contact from a mentor, impact of their edits, or task recommendations. Please read over the project page, and comment on its discussion page with any ideas, questions, or concerns. Do you think this is a good idea? Where could we go wrong?

Initial reports on newcomer activityEdit

We have published initial reports on each of the team's first two projects. These reports give the basic numbers from each project, and there are many more questions we will continue to answer in future reports. We're excited about these initial findings. They have already helped us define and design parts of our future projects.

  • Welcome survey: the initial report on welcome survey responses is available here. Some of the main findings:
    • Most users respond to the survey, giving it high response rates of 67% and 62% in Czech and Korean Wikipedias, respectively.
    • The survey does not cause newcomers to be less likely to edit.
    • The most common reason for creating an account in Korean Wikipedia is to read articles—not for editing—with 29% of Korean users giving that responses.
    • Large numbers of respondents said they are interested in being contacted to get help with editing: 36% in Czech and 53% in Korean.
  • Understanding first day: the initial report on what newcomers do on their first day is available here. Some of the main findings:
    • Large numbers of users view help or policy pages on their first day: 42% in Czech and 28% in Korean.
    • Large numbers of users view their own User or User Talk page on their first day: 34% in Czech and 39% in Korean.
    • A majority of new users open an editor on their first day – but about a quarter of them do not go on to save an edit during that time.

Help panel deploymentEdit

The help panel was deployed in Czech and Korean Wikipedias on January 10. Over the past four weeks:

  • About 400 newcomers in each wiki have seen the help panel button.
  • About 20% of them open up the help panel.
  • About 50% of those who open it up click on one of the links.
  • About 5% of Czech users ask questions, and about 1% of Korean users ask questions.

We think that the 20% open rate and 50% click rate are strong numbers, showing that a lot of people are looking for help, and many want to help themselves by looking at help pages. The somewhat lower numbers of asking questions (especially in Korean Wikipedia) has caused us to consider new features to allow people to help themselves. We're going to be adding a search bar to the help panel next, which will allow users to type a search that only looks for pages in the Help and Wikipedia namespaces.

How to create a good feedback page?Edit

What is the way to built a good help page? What blocks you when writing an help page? Your replies will help to create better help contents to newcomers, that would be used on Help panel.

Growth team's newsletter prepared by the Growth team and posted by bot, 14:15, 13 February 2019 (UTC) • Give feedbackSubscribe or unsubscribe.

Problem with automatic categorization templateEdit

Hello, not finding the dedicated template I created the {{Brazilphotomonthyear}} on the basis of others already existing and now standard, or at least I believed, as well as {{Italyphotomonthyear}} {{Germanyphotomonthyear}} etc, but only now I have discovered your {{Brazil photographs taken on navbox}}. And now what do you do?--Threecharlie (talk) 19:13, 25 February 2019 (UTC)

  In progress – Thank you for writing. I'm not clear on the question, but I will look at the templates you mention and see what's going on. Allow me some time, will be able to reply later this evening. Senator2029 19:48, 25 February 2019 (UTC)
  Info – Are you asking where to use the different templates? {{Brazilphotomonthyear}} and is for the Category:February 2019 photographs of Brazil. {{Brazil photographs taken on navbox}} is for Category:Brazil photographs taken on 2019-02-25 . Senator2029 22:36, 25 February 2019 (UTC)

Growth team updates #6Edit

18:19, 18 March 2019 (UTC)


Code issues in User:Senator2029/common.cssEdit

Hi Senator2029, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Senator2029/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new prettyCss issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. WARNING: suggest-relative-unit:px: line 14 char number 26 - Evidence: 2px
  2. WARNING: suggest-relative-unit:px: line 23 char number 19 - Evidence: 2px
  3. WARNING: suggest-relative-unit:px: line 26 char number 12 - Evidence: 3px
  4. WARNING: suggest-relative-unit:px: line 44 char number 12 - Evidence: 1px
  5. WARNING: font-family-one-generic: line 45 char number 5 - Evidence: font-family
  6. WARNING: suggest-relative-unit:px: line 48 char number 14 - Evidence: 2px
  7. WARNING: suggest-relative-unit:px: line 48 char number 18 - Evidence: 2px
  8. WARNING: suggest-relative-unit:px: line 48 char number 22 - Evidence: 5px
  9. WARNING: font-family-one-generic: line 68 char number 3 - Evidence: font-family

Your CommonsMaintenanceBot (talk) at 18:00, 19 March 2019 (UTC).

Copyright status: File:Miss Florida 1966 Christine Torgeson riding in Governor Kirk's inauguration parade - Tallahassee, Florida.jpgEdit

Copyright status: File:Miss Florida 1966 Christine Torgeson riding in Governor Kirk's inauguration parade - Tallahassee, Florida.jpg

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Miss Florida 1966 Christine Torgeson riding in Governor Kirk's inauguration parade - Tallahassee, Florida.jpg. 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 OTRS 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.

Magog the Ogre (talk) (contribs) 15:55, 24 March 2019 (UTC)

File:Ieee blue.jpgEdit

 
File:Ieee blue.jpg 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 remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

D Y O L F 77[Talk] 14:55, 21 April 2019 (UTC)

Growth team updates #7Edit

16:19, 29 April 2019 (UTC)

Call for submissions for the Community Growth space at Wikimania 2019Edit

Welcome to a special newsletter from the Growth team! This special newsletter is not about Wikimedia Foundation Growth team projects. Instead, it is a call for submissions for the Community Growth space at Wikimania 2019. We think that many people who receive this newsletter may have something valuable to contribute to this space at Wikimania. We haven't translated the newsletter, because Wikimania's language is English.

Please see below for the message from the organizers of the Community Growth space at Wikimania.

---

Wikimania 2019 is organized into 19 “spaces”, which are all accepting proposals for sessions. This message comes from the team organizing the Community Growth space.

Since you are interested b Growth team projects, and potentially involved in welcoming newcomers initiatives on your wiki, we would like to invite you to submit a proposal to the Community Growth space because of the actions you’ve done around newcomers on wikis. The deadline for submission is June 1. See below for Community Growth submission topics and session formats. Topics and sessions have to be in English.

In the Community Growth space, we will come together for discussions, presentations, and workshops that address these questions:

  • What is and is not working around attracting and retaining newcomers?
  • How should Wikimedia activities evolve to help communities grow and flourish?
  • How should our technology and culture evolve to help new populations to come online, participate and become community members?

Recommended topics: please see this link for the list for the list of recommended topics. If you do not plan to submit a proposal, you can also suggest additional topics here. If your topic does not fit into our space, remember that there are 18 other spaces that could welcome you sharing your knowledge and perspective.

Types of session. We prefer sessions that are participatory, interactive, promote conversations, and give a voice to parts of our movement that are heard less often. Please see this link for the list of recommended session formats.

Poster submissions. Posters are also a good way to introduce a topic, or show some results of an action. Please consider submitting one!

More information about the Community Growth space, topics, and submission formats is available on the proposal page.

Please submit your proposal. The reviews will happen at the beginning of June.

If you have questions about Wikimania in general, please ask them on the Wikimania wiki.

On behalf of the Community Growth leadership team, Trizek (WMF), 11:44, 16 May 2019 (UTC)

Return to the user page of "Senator2029".