nsibility to
determine what changes to make to the TDMP. They will guide a process to
solicit input and feedback on a proposal that will be open to staff and
volunteer technical contributors.
Thank you,
Moriel, on behalf of the TDMP Retro Core Group.
Core group:
- Moriel Schottlender (chai
l, on behalf of the TDMP Retro Core Group.
Core group:
- Moriel Schottlender (chair)
- Daniel Kinzler
- Chris Danis
- Kosta Harlan
- Temilola Adeleye
--
Moriel Schottlender (she/her <https://pronoun.is/she>)
Principal Software Engineer
Wikimedia Foundation https://wikim
-making process in the technical spaces.
Your voice and opinion are extremely important!
Please consider taking the time to fill out the survey, or finish
submitting it if you haven’t yet.
Thanks,
Moriel, on behalf of the TDMP Retro Core Group
Core group:
-
Moriel Schottlender (chair
öd fri kunskap, bli medlem i Wikimedia Sverige.
> Läs mer på blimedlem.wikimedia.se
>
>
> Den tis 18 juli 2023 kl 21:28 skrev Moriel Schottlender <
> mschottlen...@wikimedia.org>:
>
>> Thank you for spotting this!
>>
>> This is now fixed; it should not require an
//phabricator.wikimedia.org/T333235
>>
>>
>> How to contact the retrospective core team:
>>
>>
>>-
>>
>>Write to the core team mailing list:
>>tdf-retro-2...@lists.wikimedia.org
>>-
>>
>>The Tec
n MediaWiki talk
page:
https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Technical_Decision-Making_Process_Retrospective_and_Consultation_plan
Thank you,
Moriel, on behalf of the TDMP Retro Core Group
Core group:
-
Moriel Schottlender (chair)
-
Dan
> Here are the links to the relevant wiki page and Phab ticket:
>
>- Wiki page
>
> <https://www.mediawiki.org/wiki/Technical_decision_making/Technical_Decision-Making_Process_Retrospective_and_Consultation_plan>
>- Phabricator ticket <https://phabricator.wikimedia.org
kimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Moriel Schottlender (she/her)
Seni
://phabricator.wikimedia.org/T219441
[2] Clean up code related to blocking
https://phabricator.wikimedia.org/T225011
[3] Refactor Block to AbstractBlock, DatabaseBlock and SystemBlock
https://phabricator.wikimedia.org/T222737
--
Moriel Schottlender (she/her)
Senior Software Engineer
Tech Lead | Community
__
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
&g
t part works and I have verified that the *createWindow* method is
> called when you click the link, but the dialog is not shown. Can someone
> kindly look at my code and tell me what I am missing?
>
> Thanks,
>
> Huji
> ___
&
erico Leva (Nemo)
wrote:
> Moriel Schottlender, 08/01/19 03:53:
> > The new “Partial Blocks” feature has fundamentally changed the way
> > MediaWiki considers what “block” means;
>
> Given this was not fully considered before applying the change, the
> safest way forward i
://meta.wikimedia.org/wiki/Community_health_initiative/Per-user_page,_namespace,_and_upload_blocking
[2] Anti Harassment tools board:
https://phabricator.wikimedia.org/project/view/2660/
[3] For a discussion of this, see: https://phabricator.wikimedia.org/T210475
--
Moriel Schottlender (she/her
Heh, an apology here, my autocorrect "fixed" your name, Yaron. I apologize
for that and should have caught it.
... The trouble of multilingual corrections.
Moriel
On Mon, Jun 11, 2018, 11:37 AM Moriel Schottlender <
mschottlen...@wikimedia.org> wrote:
> I'm not going to
t throw that on others as if by making a conscious choice to avoid
spaces that have a danger of being toxic, they're personally attacking you.
Let's go back to the actual discussion at hand, instead.
Moriel
On Mon, Jun 11, 2018, 11:05 AM Yaron Koren wrote:
> Hi,
>
> Moriel Sc
our repo as
intentionally not included in the CoC.
They make a valid decision that this type of space is not for them.
That's not a personal attack. that's a valid decision about where one wants
to spend their time given the governing rules of the space.
Moriel
On Mon, Jun 11,
Yaron,
On Sun, Jun 10, 2018 at 8:35 PM Yaron Koren wrote:
> This looks to me like a violation of the Code of Conduct. I don't want to
> cause more drama in this discussion, especially since it seems like a sort
> of consensus has formed and we can all move on, but I do find it disturbing
> that
Neat! this is great! Thank you for working on this, Srishti and anyone else
involved!
On Fri, May 4, 2018 at 12:34 PM, Niharika Kohli
wrote:
> Great work! I'm sure this will be incredibly helpful to a lot of new
> developers. :)
>
> On Fri, May 4, 2018 at 11:45 AM Srishti Sethi
> wrote:
>
> >
Hi Strainu,
Let me pitch in, at least from the technical point of view to some of your
questions:
On Mon, Apr 23, 2018 at 2:39 PM, Strainu wrote:
> That's great news! I especially like the promise of replication within
> minutes from OSM, it sounds wonderful.
Just to clarify -- the change wil
Not exactly the same, but worth mentioning, there's an npm package for
grunt that was developed originally in the VE team and is used in some of
our repos that's being used in some of our repos called grunt-tyops
https://www.npmjs.com/package/grunt-tyops
I don't think it can work on the commit mes
Igal, I'm not sure what this is but a suspicion was raised as to a
potential reason.
Can you see if there's a difference in this between edits you're making in
VisualEditor versus edits that are made through the wikitext editor?
On Sun, Oct 29, 2017, 3:21 AM יגאל חיטרון wrote:
> Hi. FYI: There
I see your idea here, Igal, but I don't think it's necessary.
Developers usually have pretty good tools to see where a bug came from (for
example, we have a tool called "git bisect"[1] that allows us to analyze
not just which release the bug was introduced in, but a specific commit to
"blame" for
I think this can be solved easily if you just add the URL of what you're
looking at when you send an email or report such things.
This will help everyone understand the context even if you aren't aware of
all the other products or tools that we have.
You need to understand that sending an email sa
Thanks for raising this question, I was thinking about something similar a
little while back when I was reviewing some code without the explicit
@inheritdoc on it.
I personally think we'll gain a lot more if we stick to always documenting
our methods, including @inheritdoc. Reasoning below.
On Sa
Hi Robert,
In general, the 'data' property for items inside the GroupElement can be
strings or objects, as they represent some state of your item.
In OO.ui.mixin.GroupElement, the method "getItemFromData" can then return a
specific item based on its data property. If you use an Object for the
data
There's no single repo for this, since translation files are per repository
- but our translations are not being submitted directly through the
repositories anyways, they are being fixed through translatewiki.
If you want to provide translation fixes to various extensions, you should
go to https:/
As a side note, chrome extensions can authorize a domain and use it as if
they're requesting while on the site, it seems, to prevent cors errors.
https://developer.chrome.com/extensions/declare_permissions
That may require that your user login directly in Wikipedia rather than
through your extens
This is great, well done!
Is this the first year we'll have a stand in FOSDEM, or did we have one in
previous years?
On Mon, Dec 21, 2015 at 5:23 PM, Matthew Flaschen
wrote:
> The MediaWiki/Wikimedia stand has been accepted for FOSDEM. The main
> coordination point prior to the event will be
>
On Tue, Nov 3, 2015 at 10:04 PM, Legoktm
wrote:
>
> I (independently) spoke with Rachel about doing this today, and have
> uploaded this one to start with[1], and will work on uploading the rest
> of them to Commons.
>
> [1]
>
> https://commons.wikimedia.org/wiki/File:Tech_Talk_-_Nothing_Left_but_
I'm not sure about uploading the video to Commons properly, but this did
remind me to upload the slides to commons.
They're available here now:
https://commons.wikimedia.org/wiki/File:Nothing_Left_but_Always_Right_-_The_Twisted_Road_to_RTL_Support.pdf
On Tue, Nov 3, 2015 at 3:04 PM, Andre Klapp
On Sat, Sep 5, 2015 at 4:11 PM, MZMcBride wrote:
> Am I supposed to know what a manfeeling is? It seems weird to me that the
> push (perhaps a movement, who knows) to implement codes of conduct has
> become so enmeshed with the ultra-liberal feminist movement. I think there
> are people who sympa
Isn't this the point of this email chain and talk page, though? To open
this up to the broader community for development...?
The idea was picked up and developed in wikimania and is now being proposed
as a starting point for development by the tech community on a broader
scale. Seems to allow for
u, Jul 10, 2014 at 11:05 AM, Željko Filipin
> wrote:
> > On Wed, Jul 9, 2014 at 9:50 PM, Moriel Schottlender
> > wrote:
> >
> >> Worse, I seem to also get problems uninstalling and reinstalling
> git-review
> >> when I try to follo
t-review code, however it may be implicit (a feature of pip used) or in
> pbr somewhere.
>
> Could you provide a complete backtrace for that exception?
>
>
> On Thu, Jul 10, 2014 at 10:11 AM, Moriel Schottlender
> wrote:
>
> > >
> > > which package version do
>
> which package version do you have for 'python-setuptools', and what
> does this show:
> $ /usr/bin/easy_install --version
>
I get 'setuptools 3.3'
> I reinstalled python-setuptools, and git review 1.24 is still working for
> me. :/
>
So, when I try 'sudo pip install -U git-review' I get
(..
I'm using Ubuntu 14.04 and I get the same issues.
Worse, I seem to also get problems uninstalling and reinstalling git-review
when I try to follow the directions in the first email. I think that part
might be local to my machine -- but the general git-review 1.24 problem
doesn't seem to be limited
Hello community,
tl;dr:
I'd love to see if there's anyone in the community that can help me take
charge of ExtensionStatus development, or take it over completely.
Longer version:
About 9 months ago, just before I started Google Summer of Code 2013, I
developed "ExtensionStatus", which checks
Hello everyone!
Google Summer of Code 2013 came to an official end today with final reviews
and code submissions.
I wrote a blog post summarizing the summer internship, the deliverables,
and the thank-yous:
http://moriel.smarterthanthat.com/tips/google-summer-of-code-2013-summary/
I'd like to th
Hi everyone,
Again, thank you to for all the comments, advice and criticism!
I just wanted to send an update on the status of the extension --
I created a page for this extension on mw -
http://www.mediawiki.org/w/index.php/Extension:ExtensionStatus where I also
added a future/todo list, a scree
ay 12, 2013 at 11:26 PM, Moriel Schottlender >wrote:
>
> > Hello everyone,
> >
> > I'd like to get your opinions and critique on my very first MediaWiki
> > extension, which, I hope, will be helpful to other developers.
> >
> > I noticed that there
y themselves -- though that *could*
have been an awesome extension ;)
Please keep the comments coming! This is really helpful :)
Thanks,
Moriel
On Mon, May 13, 2013 at 12:58 PM, Mark A. Hershberger wrote:
> On 05/13/2013 12:26 AM, Moriel Schottlender wrote:
> > I'd like t
On Mon, May 13, 2013 at 4:06 AM, Markus Glaser wrote:
> I like that idea very much. In the use case I have in mind, though, I do
> have actual releases. Do you think it's possible for your extension to also
> consider tags? I am thinking of something like a tagging convention, e.g.
> "RELEASE v1.
On Mon, May 13, 2013 at 2:44 AM, Yury Katkov wrote:
> I very much lie the idea of this extension: it's very useful to know
> what changes have been made in a software one is using. Does it only
> work with WMF's gerrit? Many extensions are not hosted there. I think
> that for them you can just co
On Mon, May 13, 2013 at 2:21 AM, Daniel Friesen
wrote:
> * Your RL module should have a remote path in addition to a local one, it's
> also proper to declare the media type for your css. You should also drop
> the `@CHARSET "UTF-8"`.
> * The wfMessage calls should probably be $this->msg instea
Hello everyone,
I'd like to get your opinions and critique on my very first MediaWiki
extension, which, I hope, will be helpful to other developers.
I noticed that there's no easy way of seeing if extensions that we have
installed on our MediaWiki require update, and there are even some
extension
Quim Gil wikimedia.org> writes:
>
> On 05/08/2013 09:41 AM, Petr Bena wrote:
> > I was using these tutorials in past, and they were pretty complicated
> > for me to understand git.
>
> Have you checked recently these pages?
>
> http://www.mediawiki.org/wiki/Gerrit/Getting_started
>
> http://w
James Forrester wikimedia.org> writes:
>
> On 28 April 2013 13:04, Moriel Schottlender gmail.com> wrote:
> > Hello everyone,
> >
> > This is my second attempt for a proposal, but I think this is a project
> > that is *much* better than my previous one, an
Windows8 Metro apps as side projects, which rely heavily on javascript and
html5. However, this is my first time applying for GSoC and it's my first
time contributing to such a big project as MediaWiki and VisualEditor :)
I'd love to hear your thoughts, ideas and feedback!
Thank you again,
Hi everyone,
I posted an idea earlier this weekend to the list and received feedback --
and I really appreciate it! It made me realize that the idea I proposed was
a little vague and elaborate and sounded too complex. So I re-drafted it
and simplified it a lot, and I would really appreciate your o
Hi guys,
I've had an idea for a GSOC project that doesn't appear in the project
list. It's something I've been considering for a while, but before I write
a full proper proposal with timelines and technical outlines, I want to see
if this isn't just a random idea I am alone in wanting to see happe
50 matches
Mail list logo