User talk:SPage (WMF)

Welcome to Meta!

Hello, SPage (WMF). Welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum (please read the instructions at the top of the page before posting there). Happy editing!

-- Meta-Wiki Welcome (talk) 03:05, 19 July 2012 (UTC)

Well thank you, but I have to wonder what the effect on editor engagement is when new users go to edit their talk page and they find

    <!--{{<includeonly>subst:</includeonly>void|{{error:not substituted|welcome}}}}--> <div class="lang-en" lang="en" style="color:black">

Username rename

Hi S! Your rename has been completed, if you go to Special:MergeAccount whilst logged in to this new username User:S Page (WMF), then you will be able to follow the instructions there to merge your account into a SUL account. Please do not login to your old user account User:SPage (WMF) on any of the wikis, to ensure that you only edit from your new user account. Thehelpfulone 15:47, 5 September 2012 (UTC)

All seems good. Thanks so much "Thehelpfulone" (the name says it all)! -- S Page (WMF) (talk) 19:01, 5 September 2012 (UTC)

Hello S! And greetings from the east coast :) –SJ talk  13:45, 15 October 2012 (UTC)

API extension documentation

Hello, I saw the comment you left over at mw:API talk:Extensions. It would be helpful if there were a way to permalink to methods in the code docs. E.g., I can create a link like this to dieUsage() or dieUsageMsg(), but as changes are made to the source, the link will eventually not work; it will take the person to the right file, but not the right method. Those anchors, which are auto-generated hashes, go out of date.

I wonder if we can create a tag file and parse it, pursuant to the tip given here. It sounds like it might require an extension to do the parsing. It might be worth it; in many cases, it's probably more efficient to link to a method rather than manually copying and pasting to, or summarizing/paraphrasing on, MediaWiki.org what doxygen already has and then try to keep that documentation up to date. Of course, a resourceful, determined programmer will be able and willing to look it up for himself, but we might as well make it as easy as we can and save the reader's time.

Another possibility would be to create a namespace on MediaWiki.org that contains all the same documentation that's in doxygen, but with MediaWiki-style headings and anchors. A bot could keep it up-to-date and put each revision number in the edit comment. Or (probably preferably) there could be a new special page created that lets one view documentation in such a format, and the special page could accept revision numbers as parameters. Or maybe there's some much easier and simpler option I'm overlooking. Leucosticte (talk) 00:38, 25 October 2012 (UTC)

Good points, file an enhancement bug? mw:Template:Git file supports a #line=42 parameter, but that will drift around just as you say the Doxygen hashes do. WMF is going to some day (soon?) shift from gitweb to gitblit, maybe the latter has syntactic anchoring or an implicit "search to this function". You can supply search links to Mozilla's source corpus browsers MXR and DXR, but they always seem to respond with a range of matches, they won't go straight to line matching the search.

For now, just linking to the file in git or SVN, using a template, is probably the best approach.-- S Page (WMF) (talk) 09:23, 25 October 2012 (UTC)

I submitted it as bugzilla:41721. Thanks. Leucosticte (talk) 02:52, 3 November 2012 (UTC)

About contribution for OWP

I am interested in applying for GNOME Outreach Program for Women. I would like to be involved in your project 'Flow Edit Filter integration'.

Could you tell what contribution I can make in order to apply to the programme, please? I have experience of PHP.

Aniuska Dominguez

Upcoming IdeaLab Events: IEG Proposal Clinics

Idea Lab

Idea Lab

Hello, SPage (WMF)! We've added Events to IdeaLab, and you're invited :)

Upcoming events focus on turning ideas into Individual Engagement Grant proposals before the March 31 deadline. Need help or have questions about IEG? Join us at a Hangout:

• Thursday, 13 March 2014, 1600 UTC
• Wednesday, 19 March 2014, 1700 UTC
• Saturday, 29 March 2014, 1700 UTC

Hope to see you there!

This message was delivered automatically to IEG and IdeaLab participants. To unsubscribe from any future IEG reminders, remove your name from this list

"you have new messages" text color

I've tried several variations of what looks like the right code at my global.css to change the text color to #070 (which works fine in the notifications string), to no avail. Feel like showing me the right code? [grin] TIA. ATinySliver (talk) 01:21, 21 April 2015 (UTC)

@User:ATinySliver, Per mw:Manual:Interface/Stylesheets, the file you want is User:Name/common.css, not global.css. Your code works for me there. -- SPage (WMF) (talk) 10:07, 21 April 2015 (UTC)

Cool, thank you! Quiddity got back to me earlier and said "!important" was required and, interestingly enough, it worked. —ATinySliver/^ATalkPage 20:24, 21 April 2015 (UTC)

Extension:Graph examples seem to have vanished

Oh no! Where did they go! They seem to have vanished for me from all of the MediaWiki pages---even though they displayed fine a week or so ago. ResMar 01:49, 22 April 2015 (UTC)