User talk:Jo-Jo Eumerus

This is Jo-Jo Eumerus's talk page, where you can send them messages and comments.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83: 7 days

Please, restore the article Rodrigo Silva

I have requested the restoration of the article Rodrigo Silva, because it was a very important article about a famous Brazilian archaeologist and was excluded without reasons. The article contained reliable sources, was very well described, there were no spelling errors and followed the standards and norms of Wikipedia. --DavidStarIsrael7 (talk) 18:47, 29 April 2018 (UTC)[reply]

Well, yes, but these sources either were not independent or mentioned him in passing, as noted in the deletion discussion. Jo-Jo Eumerus (talk, contributions) 19:19, 29 April 2018 (UTC)[reply]

Now at Wikipedia:Deletion review/Log/2018 April 29. —Cryptic 22:27, 29 April 2018 (UTC)[reply]

Were added new reliable sources, please check it at Wikipedia:Deletion review/Log/2018 April 29, and restore the article. --DavidStarIsrael7 (talk) 01:16, 3 May 2018 (UTC)[reply]

According to that same page, it does not seem like the sources are actually adequate. Please consider the possibility that the topic just can't have an article and that no amount of editing can overcome a lack of notability. Jo-Jo Eumerus (talk, contributions) 06:16, 3 May 2018 (UTC)[reply]

Independent Music Awards

Hi! Once upon a time you deleted this page. Can I have a copy of the last revision please? Kind regards and thank you. Doc Taxon (talk) 05:08, 1 May 2018 (UTC)[reply]

Greetings, Doc Taxon. Do you prefer by email or by undeletion. Jo-Jo Eumerus (talk, contributions) 06:44, 1 May 2018 (UTC)[reply]

use wikimail please Doc Taxon (talk) 08:02, 1 May 2018 (UTC)[reply]

@Doc Taxon: So done. Jo-Jo Eumerus (talk, contributions) 16:45, 1 May 2018 (UTC)[reply]

I didn't get it, but the mail address in the preferences is okay. Please try it once more. Doc Taxon (talk)

@Doc Taxon: Tried another time. Jo-Jo Eumerus (talk, contributions) 16:19, 3 May 2018 (UTC)[reply]

thank you Doc Taxon (talk) 17:30, 3 May 2018 (UTC)[reply]

DYK for Paniri

On 2 May 2018, Did you know was updated with a fact from the article Paniri, which you recently created, substantially expanded, or brought to good article status. The fact was ... that as of 2009, the highest location where crustaceans had been discovered was in the crater lake of Paniri? The nomination discussion and review may be seen at Template:Did you know nominations/Paniri. You are welcome to check how many page hits the article got while on the front page (here's how, Paniri), and it may be added to the statistics page if the total is over 5,000. Finally, if you know of an interesting fact from another recently created article, then please feel free to suggest it on the Did you know talk page.

Gatoclass (talk) 12:02, 2 May 2018 (UTC)[reply]

File:NGS Honorable Mention Award to THFFI.jpg Deletion

You recommended deletion of this file. I responded with the reasons why it should not be deleted but you seem to have never seen my response. At least, you never reacted to my response.

Charles C. Morgan (me) is a member of the Board and the Treasurer The Hungerford Family Foundation, Inc. (THFFI). I am also the editor of The Hungerford World Tree, the Newsletter that was given the award by the National Genealogical Association (NGS).

The image that was deleted is a scan done by Charles C. Morgan (me) of the certificate given to THFFI by NGS as the winner of the NGS 2017 Family Association Newsletter Competition. As stated above, Charles C. Morgan is a Member of the Board and Treasurer of THFFI as well as the editor of the THFFI Newsletter that was given the award. Having been given to THFFI by NGS, both the certificate itself and the scanned image of that certificate are owned by THFFI and, consequently, THFFI is the copyright owner of both the certificate and the image. Charles C. Morgan, as an officer and Member of the Board of THFFI, has granted permission for use of this image on Wikipedia. Charles C. Morgan has the authority to grant that permission.

FYI, I am an attorney and have a good understanding of Intellectual Property law, including Copyright law and the facts regarding ownership rights underlying a claim to a copyright. THFFI has a rightful, unambiguous claim to the copyright of this image since the certificate was given to (transferred to, donated to, relinquished to, granted to, delivered to) THFFI without any reservation of rights by the NGS. Charles C. Morgan scanned the certificate. As an officer and member of the Board with authority to act on behalf of THFFI, Charles C. Morgan had the power to vest copyright ownership of the image in THFFI.

The NGS press release announcing the granting of the award to THFFI can be seen at this link: <href>https://www.ngsgenealogy.org/galleries/press/AWARDSOpeningSessPRFINAL210MAY2017.pdf</href>

Please undelete this image at your early convenience and authorize its use on my draft article about THFFI.

Charlie (talk) 15:36, 6 May 2018 (UTC)[reply]

@Cochituate: Well, we need proof that NGS gave the copyright to THFFI, not just an assertion. You need to confirm the ownership of the file copyright to WP:OTRS, preferably through an official e-mail. Jo-Jo Eumerus (talk, contributions) 15:47, 6 May 2018 (UTC)[reply]

Well, as a lawyer, I KNOW that what you are saying is absolutely incorrect. You clearly have no clue about ownership rights under facts like this. Requiring me to obtain an email from NGS amounts to harassment and is imposing inappropriate administrative burdens on me and NGS. I will go get that email and try to figure out how to get it to you, but please go do some research on copyright ownership and become educated on the subject. Charlie (talk) 16:07, 6 May 2018 (UTC)[reply]

I received the following from NGS this evening:

Charlie,

I received it and have been checking into this. There is not a copyright on the certificate. The certificate is not something that we would go to the trouble and expense to copyright. If we did that we would have to do that for each certificate and could not afford the cost. If you need something that says you have permission to publish a scanned copy of the certificate, we could probably do that. As far as taking a picture of the certificate, who ever took the picture would own the copyright to the picture. But there again it would run into money to register a copyright.

Chuck

From: Charlie Morgan [1] Sent: Wednesday, May 09, 2018 3:44 PM To: Charles S. Mason, Jr Subject: RE: The Hungerford Family Foundation, Inc. =Winner of the NGS Family Assocciation Newsletter Competition

Chuck –

Did you receive my email below? I need a response from NGS to give to Wikipedia.

Charlie

From: Charlie Morgan [2] Sent: Sunday, May 6, 2018 12:13 PM To: 'cgrs791@verizon.net' Subject: RE: The Hungerford Family Foundation, Inc. =Winner of the NGS Family Assocciation Newsletter Competition

Chuck –

Everything worked out just fine. Your staff at the convention was (is) first-rate. Again, thanks for the award. And thank you for your support and assistance.

I’m drafting an article about THFFI for publication on Wikipedia. They are trying to tell me that THFFI is not the copyright owner of the award certificates given to us last year (honorable mention) and this year (first place). They are saying that you (NGS) must send me an email stating that THFFI is the copyright owner of the certificates that you’ve given us and that THFFI is the copyright owner of the scanned images of the certificate that I want to include in the article.

Could you, or someone else in authority at NGS, send me an email confirming that THFFI is the copyright owner of the certificates and the scanned images that we have made of those certificates?

Charlie

What more do I need to give you? How do I send you a print of the emails?Charlie (talk) 03:08, 10 May 2018 (UTC)[reply]

SALT request

You closed The Riott Squad article as redirect. This was the second AfD on the article and in the 3 days since it has already been recreated. Can you lock down the article? Thanks - Galatz ^Talk 18:19, 6 May 2018 (UTC)[reply]

Eh, I don't think that one single recreation merits page protection. Jo-Jo Eumerus (talk, contributions) 19:25, 6 May 2018 (UTC)[reply]

Two sources to apply

Perhaps also Lake Cahuilla. Jo-Jo Eumerus (talk, contributions) 19:54, 6 May 2018 (UTC)[reply]

Tech News: 2018-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

The Wikimedia Commons mobile app has a new version. It is now easier to find nearby places that need pictures. It helps you with direct uploads and title and category suggestions. The app only works on Android phones. [3]

Problems

The abuse filters had a problem with blocks where you had changed how long they last. It used the default length everywhere. This was in late April. Abuse filter users should make sure the right block length is used and change them if needed. This is only for filters where how long blocks last had been changed. [4]

Changes later this week

The advanced search function beta feature will be on all Wikimedia wikis. It makes it easier to use some of the special search functions that most editors don't know exist. [5]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 May. It will be on non-Wikipedia wikis and some Wikipedias from 9 May. It will be on all wikis from 10 May (calendar).

Meetings

You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 8 May at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 9 May at 15:00 (UTC). See how to join.

Future changes

All wikis with fewer than 100 high-priority linter errors in the main namespace will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 16 May. Other wikis will switch soon when they have fixed the errors that must be fixed. Tidy will be removed on all wikis before July 2018. [6][7]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

16:28, 7 May 2018 (UTC)

GAN Backlog

Hi Jo JO Eumerus. I am looking to encourage suitable editors to review more articles at WP:GAN. Currently you have 16 nominations awaiting review and as you are probably aware there is a large backlog. This means you and other editors may have to wait months before your articles are reviewed. According to User:GA bot/Stats you have reviewed 9 articles and your user page shows 33 passed good articles. This suggests that you are familiar with the criteria and able to contribute more reviews. Without editors reviewing articles the process falls apart. If you need some help with reviewing feel free to ask me or leave a note at the help desk. Regards AIRcorn (talk) 11:45, 9 May 2018 (UTC)[reply]

Help us design granular blocks!

Hello :-) The Anti-Harassment Tools team at the Wikimedia Foundation will start building these granular blocking tools in a few weeks and we've asked WMF designer Alex Hollender to help us make some wireframes so the tools are intuitive to MediaWiki users.

Tracked in Phabricator
Task T190350

We have a first draft of how we think this tool should work. You can read the full proposed implementation here but here are the significant parts:

Granular blocks (page, category, namespace, and file uploading) will be built on top of Special:Block. These blocks will function as if they were regular blocks and allow for the same options, but only take effect on specific pages.
We will add a new checkbox for "Block this user from the whole site" which will be checked by default. When it is unchecked the admin will be able to specify which pages, categories, and/or namespaces the user should be blocked from editing.
Granular blocks can be combined and/or overlap. (For example, a user could be simultaneously blocked from editing the articles Rain, Thunder, Lightning, and all pages inside the Category:Weather.)
Only one block is set at a time, to adjust what the user is blocked from the administrator would have to modify the existing block.
Block logs should display information about the granular block
When a blocked user attempts to edit an applicable page, they should see a block warning message which include information on their block (reason, expiration, what they are blocked from, etc.)
If a category is provided, the blocked user cannot edit either the category page itself and all pages within the category.
If the File: namespace is blocked, the user should not be allowed to upload files.

We like this direction because it builds on top of the existing block system, both a technical and usability wise. Before we get too far along with designs and development we'd like to hear from you about our prosposal:

What do you think of the proposed implementation?
We believe this should be an expansion of Special:Block, but it has been suggested that this be a new special page. What are your thoughts?
Should uploading files be combined with a File namespace block, or as a separate option? (For example, if combined, when a user is blocked from the File namespace, they would neither be able to edit any existing pages in the File namespace nor upload new files.)
Should there be a maximum number of things to be blocked from? Or should we leave it up to admin discretion?

We appreciate your feedback on this project's talk page or by email. For the Anti-Harassment Tools team, SPoore (WMF) (talk) , Trust and Safety Specialist, Community health initiative (talk) 20:54, 9 May 2018 (UTC)[reply]