Hey,
I was wondering what the qualifications are for getting a Bugzilla section
for a MediaWiki extension, and how it can be set up? (It's difficult having
to memorize or write down on notepads what things need to be fixed, and I
don't want to have to set up my own Bugzilla instance.)
*-- *
*Tyle
File a bug under Wikimedia/Bugzilla for it. Only pre-req is that you
are heavily involved in the dev of it (eg: maintainer) and you want
it.
On Wed, May 8, 2013 at 5:01 PM, Tyler Romeo wrote:
> Hey,
>
> I was wondering what the qualifications are for getting a Bugzilla section
> for a MediaWiki e
On Wed, May 8, 2013 at 3:09 AM, K. Peachey wrote:
> File a bug under Wikimedia/Bugzilla for it. Only pre-req is that you
> are heavily involved in the dev of it (eg: maintainer) and you want
> it.
>
OK, thanks!
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer
Link me to bug and I will create it right now!
On Wed, May 8, 2013 at 9:27 AM, Tyler Romeo wrote:
> On Wed, May 8, 2013 at 3:09 AM, K. Peachey wrote:
>
>> File a bug under Wikimedia/Bugzilla for it. Only pre-req is that you
>> are heavily involved in the dev of it (eg: maintainer) and you want
>
On Wed, May 8, 2013 at 4:44 AM, Petr Bena wrote:
> Link me to bug and I will create it right now!
Here's the link: https://bugzilla.wikimedia.org/show_bug.cgi?id=48252
Much appreciated.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztec
Hi,
On Wed, 2013-05-08 at 03:01 -0400, Tyler Romeo wrote:
> I was wondering what the qualifications are for getting a Bugzilla section
> for a MediaWiki extension
Basically none, though I highly appreciate if maintainers *themselves*
ask for the creation of a Bugzilla component for their extensio
I was going through our code contemplating dropping XHTML 1.1 support and
ran into the RDFa support stuff and realized how out of date and limited
it is.
I've put together an RFC for replacing our code that appears to be based
on the RDFa 1.0 from 2008 with RDFa 1.1 and expanding support fo
On Tue, Apr 30, 2013 at 2:25 PM, Indrani Sen wrote:
> I am summarizing here my proposal idea for OPW MediaWiki projects.
I have noticed that you did not provide the link to your proposal[1]. In
addition to the comments that I have posted here, I have left a few
comments on the talk page[2].
Že
On Tue, Apr 30, 2013 at 5:45 PM, Rachel Thomas wrote:
> Here is my proposal for OPW:
> https://www.mediawiki.org/wiki/User:Rachel99/OPW_proposal
>
Hi Rachel,
I have left a couple of comments on the talk page[1].
Željko
--
1: https://www.mediawiki.org/wiki/User_talk:Rachel99/OPW_proposal
___
On 05/07/2013 05:33 PM, Juliusz Gonera wrote:
> Seems interesting. Is there anyone who'd be interested in giving a talk
> or participating in a panel there?
Given that it's very close to me, and that I have quite a bit of
experience with the API, this is something I could do.
I actually had an AP
Hi all,
I don't know whether this is the correct mailing list to ask such question but
it is the one I am reading regularly…
Does anyone know about the adequate procedure to get permission to request
deleted revision information from the MediaWiki API?
I just stumbled over this problem...
{
On Wed, May 8, 2013 at 9:35 AM, Claudia Müller-Birn
wrote:
> Hi all,
>
> I don't know whether this is the correct mailing list to ask such question
> but it is the one I am reading regularly…
>
> Does anyone know about the adequate procedure to get permission to request
> deleted revision inform
On 05/03/2013 04:22 PM, Matthew Flaschen wrote:
On 04/27/2013 07:58 PM, Quim Gil wrote:
SELECTING CANDIDATES
After the deadline we will meet to prioritize GSoC and OPW candidates.
When is this meeting?
It seems that we won't need a meeting to discuss candidates. So far the
discussions of t
Le mercredi 08 mai 2013 à 09:09 -0400, Marc A. Pelletier a écrit :
> On 05/07/2013 05:33 PM, Juliusz Gonera wrote:
> > Seems interesting. Is there anyone who'd be interested in giving a talk
> > or participating in a panel there?
>
> Given that it's very close to me, and that I have quite a bit of
On 04/17/2013 02:51 AM, Mathieu Stumpf wrote:
> Le 2013-04-16 18:25, Geer Oskam a écrit :
>> Hi all,
>>
>> the GLAM Wiki Toolset-code is ready for its initial review.
>> It can be found at: https://gerrit.wikimedia.org/r/#/c/59405/
>>
>> Please help us by taking a look at it.
>>
>> Cheers,
>> Geer
Hi,
Long time ago when I started learning with git I decided to create a
simple guide (basically I was just taking some notes of what is
needed). I never thought that it could be useful to anyone so I never
announced it anywhere. However I got some feedback to it, so I decided
to inform you too.
On Wed, May 8, 2013 at 12:34 PM, Petr Bena wrote:
> Hi,
>
> Long time ago when I started learning with git I decided to create a
> simple guide (basically I was just taking some notes of what is
> needed). I never thought that it could be useful to anyone so I never
> announced it anywhere. Howeve
I was using these tutorials in past, and they were pretty complicated
for me to understand git. I don't say it should be considered some
"official" documentation, rather something what desperate people could
use.
Git/Workflow and such are written by people who already understand git
- they don't s
Well, that was the point of [[Git/Getting started]] because the Workflow
document sucks.
-Chad
On Wed, May 8, 2013 at 12:41 PM, Petr Bena wrote:
> I was using these tutorials in past, and they were pretty complicated
> for me to understand git. I don't say it should be considered some
> "officia
I guess the viewpoint and perspective from the more experienced users may
be different. The veterans may start to take some knowledge for granted, as
a given knowledge that they may thing people would already know.
For example, the underlying concept of git commit is something that I now
take for
On May 7, 2013, at 8:56 PM, Bartosz Dziewoński wrote:
> On Tue, 07 May 2013 20:51:07 +0200, Krinkle wrote:
>
>> It is the duty of repository co-owners to make wise decisions beyond
>> just code quality. About what changes go in what release (if at all),
>> whether the introduced features are in
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://www.mediawiki.org/wiki/Gerrit/Tutorial
I'm a git-idiot a
On Wed, May 8, 2013 at 8:34 PM, Petr Bena wrote:
> Hi,
>
> Long time ago when I started learning with git I decided to create a
> simple guide (basically I was just taking some notes of what is
> needed). I never thought that it could be useful to anyone so I never
> announced it anywhere. Howeve
It's a big one. I took a crack at PS2. 32 more comments.
On Wed, May 8, 2013 at 6:23 PM, Sumana Harihareswara
wrote:
> On 04/17/2013 02:51 AM, Mathieu Stumpf wrote:
> > Le 2013-04-16 18:25, Geer Oskam a écrit :
> >> Hi all,
> >>
> >> the GLAM Wiki Toolset-code is ready for its initial review.
>
On Wed, 08 May 2013 19:24:48 +0200, Krinkle wrote:
How does this make anything harder for new users? If anything, it makes it
easier by not having to worry about which file to edit, what to put in it etc.
You're either not reading what I wrote or intentionally pulling my words out of context
Biggest disadvantage I see on the official documents is they don't
contain the hypothetical situation when something is wrong, they are
relying on the fact that everything is as it's supposed to be -
perfect. That user has perfectly configured system, that user doesn't
accidentally break repository
Also note that in my document I have some hints like this:
Sometimes it's needed to use following, should you know why, feel free
to explain it:
git push origin HEAD:refs/publish/master
which I was told to use by someone else, and it works! So I noted it
somewhere in case I would get into same is
On Wed, May 8, 2013 at 3:04 PM, Petr Bena wrote:
> Also note that in my document I have some hints like this:
>
> Sometimes it's needed to use following, should you know why, feel free
> to explain it:
> git push origin HEAD:refs/publish/master
>
> which I was told to use by someone else, and it w
Le mercredi 08 mai 2013 à 18:34 +0200, Petr Bena a écrit :
> Hi,
>
> Long time ago when I started learning with git I decided to create a
> simple guide (basically I was just taking some notes of what is
> needed). I never thought that it could be useful to anyone so I never
> announced it anywher
Zeljiko,
I have updated my proposal with your suggestions, plus added a timeline
and more info under "About Me". Let me know if you have other suggestions.
Here is my update proposal for OPW:
https://www.mediawiki.org/wiki/User:Rachel99/OPW_proposal
Thank you.
-Rachel
On Tue, Apr 30, 2
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
Hi,
Since there appears to have been a little bit of trivia around fixing
these phpcs warnings, I'll open a thread instead.
Both in javascript and PHP there are various keywords that can be used
as if they are functions. In my opinion this is a misuse of the
language and only causes confusion.
I
>
> But let's not have some weird exception just because someone didn't
> understand it[1] and we all copied it and want to keep it for no
> rational reason.
I think its probably because Die, List, Array, and Exit are also keywords
but require the ().
It also makes sense when looking at language
On 2013-05-08 9:26 PM, "Krinkle" wrote:
>
> Hi,
>
> Since there appears to have been a little bit of trivia
>
> Hi,
>
> Since there appears to have been a little bit of trivia around fixing
> these phpcs warnings, I'll open a thread instead.
>
> Both in javascript and PHP there are various keyword
Recently a lot of people have been talking about what's possible and
what's necessary regarding MediaWiki, CatScan-like tools, and real
category intersection; this mail has some pointers.
The long-term solution is a sparkly query for, e.g., people with aspects
novelist + Singaporean, and it would
On 05/03/2013 03:48 PM, Puneet Kaur wrote:
> Hi all ,
>
> I know its late but still.
>
> I wished to let you all know that I have applied for the Wikidata Features
> Project Idea in GSOC 2013.
>
> I have a bit of experience in website development and designing, but I am
> not sure whether all of
On 8 May 2013 18:26, Sumana Harihareswara wrote:
> Recently a lot of people have been talking about what's possible and
> what's necessary regarding MediaWiki, CatScan-like tools, and real
> category intersection; this mail has some pointers.
>
> The long-term solution is a sparkly query for, e.g
On 05/03/2013 10:18 AM, Jeremy Coffman wrote:
> Hello,
>
> My name is Jeremy Coffman. I am a second year student studying Computer
> Science at Brandeis University, with a possible focus on natural language
> processing. I have decided to apply to work on the Incremental Data Dumps
> project. M
On Wed, May 8, 2013 at 8:26 PM, Krinkle wrote:
> delete( mw.legacy );
>
> new( mw.Title );
>
> typeof( mw );
>
> echo( $foo . $bar );
>
> print( $foo . $bar );
>
> return( $foo . $bar );
>
> … and, wait for it..
>
> require_once( $foo . $bar );
>
I mostly agree. Howev
On 2013-05-08 11:48 PM, "James Forrester" wrote:
>
> On 8 May 2013 18:26, Sumana Harihareswara wrote:
>
> > Recently a lot of people have been talking about what's possible and
> > what's necessary regarding MediaWiki, CatScan-like tools, and real
> > category intersection; this mail has some poi
On 05/09/2013 12:13 AM, Brian Wolff wrote:
> Between wikipedias or all wikimedia wikis... category structure has varried
> meaning between projects. Category:North_America has different types of
> pages in enwikinews compared to enwikipedia.
Right. It would have to be grouped by top-level project
Hi, when we edit Zero configuration, it would be very beneficial to flush
any cached pages in varnish that are related to the change.
For example, if I edit Beeline's banner settings, any objects with the
header X-CS=250-99 should be purged, hopefully without any additional
manual interaction. Wit
42 matches
Mail list logo
