Hi Matthew,
This is fantastic! I'm glad you are making good use of External Data, and
some of its more advanced features like prepared SQL statements. It's great
to see the whole assembly line in one place.
I put in a link to your tutorial video here:
https://www.mediawiki.org/wiki/Extension:Exte
Hi,
For anyone interested in working with PHP and JavaScript, we have a project
to improve the InlineComments MediaWiki extension:
https://phabricator.wikimedia.org/T356436
InlineComments is a relatively new extension that allows for Google
Docs-style user annotations within pages. There are som
>
> If the developer setting $wgUseXssLanguage is set to true, then an “x-xss”
> language code becomes available and can be selected with *?uselang=x-xss*
> in the URL. When using this language code, all messages become “malicious”:
> every message is replaced by a snippet of HTML that tries to run
27;t work at all.)
-Yaron
On Sat, Aug 14, 2021 at 8:34 AM James Forrester
wrote:
> [Moving to wikitech-l; mediawiki-l is a little off-topic.]
>
> On Mon, 26 Jul 2021 at 21:27, Yaron Koren wrote:
>
>> Hi,
>>
>> I've been trying to get rid of the ESLint warning
Hi Alain,
First of all, thanks for choosing the Cargo extension! As the main author
of that extension, I'm happy you're trying it out.
So, by an amazing coincidence, over the last month or so I've been working
on creating a new extension that allows for saving and displaying BPMN
diagrams within
Hi Kunal,
On Thu, Jun 20, 2019 at 2:36 PM Kunal Mehta
wrote:
> I think it really depends for what kind of a makeup of committee we're
> looking for. I'd like to see the committee staffed with active
> Wikimedia developers who are familiar with our community norms, and
> then diversity across bac
Hi,
The Wikimedia technical spaces Code of Conduct is enforced by a committee.
That committee's selection process is defined as follows:
"The first Committee will be chosen by the Wikimedia Foundation’s Technical
Collaboration team. Subsequent members and auxiliary members of the
Committee will b
Hi everyone,
A few weeks ago I sent out a tentative announcement, but now it's more
official: the next EMWCon, or Enterprise MediaWiki Conference, will be
taking place five months from now, on April 3-5, 2019, in Daly City, right
near San Francisco. For more information, and to indicate that you'r
Nuria Ruiz wrote:
> The CoC will prioritize the safety of the minority over the comfort of the
> majority.
This is an odd thing to say, in this context. I don't believe anyone's
safety is endangered by hearing the phrase in question, so it seems like
just an issue of comfort on both sides. And w
wasn't installed
> yet. ;-) But how probably is this probably? Thank you,
> Igal
>
>
> 2018-07-18 3:43 GMT+03:00 Yaron Koren :
>
> > Hi,
> >
> > Probably... but only on a wiki that has VEForAll installed on it, of
> > course.
> >
> > -Yaron
> &
> Igal (User:IKhitron)
>
>
> On Jul 18, 2018 03:29, "Yaron Koren" wrote:
>
> Hi everyone,
>
> I'm very excited to announce the release of a new MediaWiki extension:
> VEForAll. Its name stands for "VisualEditor For All", and it provides
> something th
Moriel Schottlender wrote:
> In the gerrit commit that started this thing, you, yourself, publicly
wrote
> this:
>
> *"The Site Settings extension uses a bunch of WMF tools and services for
> its development, including hosting. If some random person sends me a patch
> for Site Settings by email, a
otential
contributor to know who "decided" to embrace this file's statement and who
didn't? Given the threat of harassment, it seems awfully risky to assume
that everyone who didn't delete the file supports it.
-Yaron
On Mon, Jun 11, 2018 at 1:23 PM Yaron Koren wrote:
> Hi,
&g
Hi,
Moriel Schottlender wrote:
> This isn't a personal attack, it's a consequence to your earlier email.
>
> You stated yourself, that one of the reasons you don't think a COC.md file
> should exist in your repository is because not all interactions are
covered
> by it. While that might be true
Gergo Tisza wrote:
> I'd still like the understand what the assumed harm is. Is this strictly a
> moral issue, where you want to avoid giving misleading information, but
> otherwise that information would be harmless? Or a liability issue, where
> your clients think that working on / using a CoC-
Hi,
Amir Ladsgroup wrote:
> One note particularly about this incident, I personally would be happy if
> Yaron thought the wording is wrong, put the file back with a better
> wording, like "gerrit part of development of this extension is covered by
> the WM CoC".
Maybe I'll do that, now that I k
Tony Thomas <01tonythomas at gmail.com> wrote:
> Scenario: I am new contributor looking at your repository (possibly
> would've contributed to couple of repos in the past in Github). As a
> maintainer of this repo, how do you want me to know that my interactions
> with your product, which might be
Chris Koerner wrote:
> I agree. I do think that as a community of practice we have many
> unwritten rules and numerous expectations of how we work together. We
> don't explicitly define the expectation of a README.MD file in repos
> either.[0] It's a best practice and cultural expectation in our s
Hi,
Antoine - thank you; I see now that your statement before to archive my
repository was just because you thought it was no longer in use. I feel
better now.
Gergo Tisza wrote:
> * There can be all kinds of reasons why the CoC file is not appropriate
for
> some repository (which is why it wasn
Chris Koerner wrote:
> “Please just assume for the sake of this discussion that (a) I'm willing
> to abide by the rules of the Code of Conduct, and (b) I don't want the
> CODE_OF_CONDUCT.md file in my extensions.”
> Ok, hear me out here. What if I told you those two things are
> incompatible? Tha
Hi,
Thanks for the responses so far.
Max Semenik wrote:
> However, users who disagree with the rules of using our resources
shouldn't be using them.
I actually agree with this. However, I'm not aware that needing to have a
CODE_OF_CONDUCT.md file is a "rule" - it was never voted on, never
anno
Hi,
CODE_OF_CONDUCT.md is a file that was added to most MediaWiki extensions
almost exactly a year ago. It reads, in full:
"The development of this software is covered by a [Code of Conduct](
https://www.mediawiki.org/wiki/Code_of_Conduct)."
This file was added on the grounds that "Now that we h
Hi,
bawolff wrote:
I actually disagree somewhat - I think it can be very rewarding to fix
> a problem that you yourself have, as opposed to fixing somebody else's
> problem. This is a traditional ideology about open source - that it is
> all about scratching your own itch.
> Although arguably m
work to
create a WMF outreach/mentorship program, I support you; I'm sure any such
effort is better than nothing.
-Yaron
On Fri, Nov 4, 2016 at 10:59 AM, Tony Thomas <01tonytho...@gmail.com> wrote:
> Hey Yaron,
>
> On Thu, Nov 3, 2016 at 5:34 PM, Yaron Koren wrote:
>
Hi Tony,
Personally, I think only projects proposed by potential mentors should be
>> considered at all, and that the documentation should state that clearly.
>> I'm not aware of any GSoC projects where the student came up with the idea
>> on their own and then executed on it successfully - with t
Hi,
I hit across this idea in the recent GSoC Mentors summit, and in the
> discussion with Srishti and Sumit on the reducing usability and scope of
> GSoC/Outreachy projects[1] among the years.
> *The problem*
> Students show up one or two weeks before GSoC or Outreachy, and propose a
> solution
Hi Quim,
Although I have used MediaWiki as a mechanism to submit conference
> proposals (here and in my previous job), I don't think I know any MediaWiki
> user or any event organizer out of Wikimedia using MediaWiki to handle a
> call for participation. Wikimania and some WikiCons do, but I don't
Hi,
> As is "unwanted attention", even if verbal, and "sustained disruption,
> interruption", which would be applicable if people are continually
> interrupting your talk on purpose (similar to the "background
> conversation" note, though not the same thing).
>
Right - I got the sense from the o
Hi,
I remembered how readily "the guys" assumed that any woman there was there
> for more than just networking and learning. I remembered having my butt
> pinched, my breasts "accidentally touched", my questions ignored or laughed
> at. I remember how the buzz of background conversation is always
Hi,
A project I've been working on for the last three months, via a Wikimedia
Individual Engagement Grant, finally had its first release today. It's the
Miga Data Viewer, and it provides a lightweight framework for browsing and
navigating through structured data in CSV file, which can for easily
b
Hi,
It seems to me that there are 15-20 distinct GSoC projects with interested
mentors, depending on how you count it. Here's the list I compiled:
Core MediaWiki:
- Automatic category redirects
- MediaWiki API 2.0
General extensions:
- Book structures
- Inline commenting
- MediaWiki-Moodle Ext
Hi,
It seems like some people are saying that getting workable code out of the
Google Summer of Code is a relatively minor aspect of the program - maybe
the third or fourth most important outcome of it, behind things like
finding new developers, getting better at mentoring, teaching software
devel
Hi,
Sorry if I overreacted - my humor calibrator might be off today.
Please carry on.
-Yaron
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Sun, Feb 12, 2012 at 9:06 AM, Guillaume Paumier wrote:
> On Sun, Feb 12, 2012 at 3:01 PM, Chad wrote:
>> On Sun, Feb 12, 2012 at 9:00 AM, Yaron Koren wrote:
>>> If you're looking for an extension name, here are some possibilities:
>>>
>>> Mobi
If you're looking for an extension name, here are some possibilities:
MobileAccess
MobileDisplay
MobileView
Mobilize (a little play on words there)
-Yaron
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/li
Happy Melon - I should have clarified how I thought this should be
implemented. I don't mean that any extensions should move locations -
the fact that everything is in one big /extensions directory is quite
helpful. I just mean that there should be some SVN settings so that
only users with a certai
Hi,
It's great to hear that Git, once MediaWiki switches over to it, will
solve some of the issues with granting access. Still, I assume no one
knows exactly when the change-over will come - and I also assume that,
even with Git in place, there will still be issues of access to the
"official" repo
Hi,
I think developer accounts on the Wikimedia SVN repository should be
easier to get. I say this because a consultant of ours at WikiWorks,
Ike Hecht, asked for a developer account last week and was rejected.
He created his first major MediaWiki extension, Ad Manager, recently,
which I added to
Hello,
Wikimania is just next week, but two months from now will be another
conference that may be of interest to MediaWiki users and developers:
SMWCon, or the Semantic MediaWiki Conference, which will be happening in
Berlin on September 21-23:
http://semantic-mediawiki.org/wiki/SMWCon_Fall_2011
Hi,
I'd like to add a hook to the getPoweredBy() function in
/includes/Skin.php - the function that sets the "Powered by MediaWiki"
button - so that other extensions or systems could add their own
buttons. I'm thinking to call it "SkinGetPoweredBy". Any objections?
-Yaron
___
Hi,
I agree that Semantic MediaWiki is the right choice here. Let me just
note two additional extensions that might be helpful here:
Semantic Internal Objects lets you store compound/n-ary, of the kind
that you find in tables (each row is its own "internal object")
http://www.mediawiki.org/wiki/
I'm in somewhat of a unique position to comment on this, since I both do
MediaWiki extension development, and run a MediaWiki consulting company
(shameless plug: wikiworks.com) - so I personally have a financial interest
in making MediaWiki more popular and more easy-to-use. I also tend to hear a
l
That would certainly simplify the format; on the other hand, it would lead
to a lot of redundancy between the different tags, which
could lead to conflicting data structures; so it's probably not a workable
solution.
-Yaron
There could be , ,
...
___
The idea of having the template specification be stored as something more
human-readable, and possibly more like wiki-text, certainly has its appeal
(at least, to those people who don't want wiki-text to be replaced by XML in
the first place!) It would be easier for users to create and edit; unless
Hi everyone,
Part of the Wikipedia Usability Initiative is a project to create a system
whereby template calls are hidden (minimized, really) for most users on the
edit page, and when users do want to edit template calls, they can do so via
a form instead of editing the template call directly. I'm
ise. That one is
different, though, in that it includes MediaWiki itself, and in fact at the
moment it's a modified, patched version of MW, which makes SMW+ somewhat
more of an application in itself. So Semantic Bundle may be the first "pure"
package of extensions.
-Yaron Koren
__
Hi,
The method showEditForm(), in the class EditPage, takes care of displaying
nearly the entire edit page. I would like to move the last section of this
method, which handles displaying the bottom of the edit page (everything
below the edit box) into its own method, perhaps called showFooter(). (
Check out the Header Tabs extension:
http://www.mediawiki.org/wiki/Extension:Header_Tabs
-Yaron
On Wed, Dec 24, 2008 at 10:05 AM, Mohsen A. Momeni wrote:
> Hi,
> I want to use tabs inside my articles in my wiki. I don't want the
> page loads again anytime a tab is clicked. Is there any simple m
Out of curiosity, are you aware of the Semantic MediaWiki extension? When
used with templates, it seems to approximate the functionality you're
talking about creating.
-Yaron
On Thu, Nov 27, 2008 at 10:56 PM, Mark Clements (HappyDog) <
[EMAIL PROTECTED]> wrote:
>
> "Platonides" <[EMAIL PROTECTED]
49 matches
Mail list logo
