User talk:Lsanabria

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search
Archives:

Tech ambassadors, "take two"[edit]

Hello tech ambassador! This month has seen a good influx of new faces in this crew \o/ , so it is time to reactivate our conversations. Now that we have a pretty good coverage of so many different projects, here are some topics for your consideration.

  1. Are there further thoughts on the role itself? I hope the questions available on Meta can help spark them. Please weigh in at Talk:Tech/Ambassadors/List#Tech ambassadors, take 2.
  2. How about we try and organise future collective work in a Phabricator workboard? Talk:Tech/Ambassadors/List#A Phab workboard for us? has all the details to explore this proposal.
  3. Finally, you are also welcome to comment at https://phabricator.wikimedia.org/T177923, should you happen to have suggestions for the Community Liaisons team, currently wondering how to measure "Wiki projects requesting beta features and other early deployments".

We hope to be able to host a live discussion in early 2018; until then, we're looking forward to hearing from you on Meta! All the best, --Elitre (WMF) (talk), on behalf of the Community Liaisons

Translation request for New Readers Inspire Campaign-- and thanks![edit]

Inspire NewReaders icon still.png

Hi there! I'm contacting you because you've volunteered your time in the past to help translate Inspire Campaigns, or you've expressed an interest about helping to translate. We have a new campaign starting soon about new readers, as we try to encourage contributors to develop ideas on how to inform and invite people to use Wikipedia, especially in places where folks are not aware of it. There are two pages that will need translation:

There will be one additional page for translation that includes the questions we will be asking idea creators when they submit ideas for the campaign. I will notify you when that prose is ready.

Finally, thank you for your support; it's very important to me that these campaigns are accessible to folks across non-English Wikimedia projects, and I wouldn't be able to do that without your time and effort. In appreciation, I'd like to send you a postcard from Chicago where I reside. If you'd like to receive a postcard from me, please e-mail me with an address I contact you at to my work e-mail, cschilling@wikimedia.org. I realize this is private information, so if you would prefer not to receive a postcard, that is understandable. Your work to make our projects accessible to everyone is no less appreciated. Please let me know if you have any questions about the prose regarding translation. Thanks, I JethroBT (WMF) 20:33, 8 January 2018 (UTC)

Getting started on Phabricator[edit]

Ambox warning green construction.svg

Greetings, ambassador!

As recently discussed within this group, we are ready to experiment with setting up a project and its related workboard on Phabricator, the platform used in the Wikimedia movement for project management, software bug reporting and feature requests. It will help us coordinate and cooperate better on projects that should require ambassadors' involvement.

For the time being, I'm just asking that you please add your Phabricator nickname next to your name in the ambassadors' table (you can create an account now if you don't have one already). I will send you further information soon! Thanks for your patience as we get to the operational stage of this effort :) Best, --Elitre (WMF) (talk) 14:52, 16 January 2018 (UTC)

Ready for translation: Editing News #1—2018[edit]

Pendiente-traducir.png

Hi! This is an invitation to join translators working on the upcoming issue of the multilingual newsletter for the visual editor, which will be widely delivered when it's end of Friday in Central Europe. Thanks in advance for your help with this: getting to interact with fellows so skilled like the translators are is among my favorite things about my job :) Best, Elitre (WMF) 10:29, 27 February 2018 (UTC)

PS: Here are some instructions. Please go to the translation page: your language should be available from the drop-down menu on the right. Once you've selected it, you'll see the document in English side by side with any translation work already done in your language. You can add new translations or modify existing ones. Please let us know about difficulties you experience with the translation memory system.

Help us design granular blocks![edit]

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.

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:

  1. What do you think of the proposed implementation?
  2. 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?
  3. 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.)
  4. 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:49, 9 May 2018 (UTC)