On Tue, Nov 13, 2012 at 7:00 AM, Petr Kadlec wrote:
> On 13 November 2012 15:47, Chad wrote:
>
>> I'm not entirely sure I understand. If it's customization for the
>> extension,
>> shouldn't it go in the Math[0] extension?
>>
>
> Note that t
doesn't
even exist. We don't use it, and they're unrelated.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Nov 13, 2012 at 7:21 AM, Brad Jorsch wrote:
> On Tue, Nov 13, 2012 at 6:11 AM, Chad wrote:
>> On Tue, Nov 13, 2012 at 3:26 AM, Amir E. Aharoni
>> wrote:
>>> At another commit I made once (forgot which one) somebody commented
>>> that I shouldn't h
process in GitHub
> anyway, so I see no reason not to give the most weight to aesthetic /
> populistic considerations. Let's make it github.com/wikimedia/mediawiki.
> Visibility helps!
>
This is not possible. Repos are the same name on the source
and destination.
-Chad
___
de this change.
>
> I'll volunteer to do so if no one else wishes to.
>
HTTPS Everywhere should've been updated some time ago to use
the native https urls.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
/Git/Workflow
> * https://www.mediawiki.org/wiki/Git/Tips
> * https://www.mediawiki.org/wiki/Gerrit
> * https://www.mediawiki.org/wiki/Gerrit/Navigation
>
> + https://www.mediawiki.org/wiki/Git/Gerrit
>
Indeed. I'm thinking this is getting a little out of control. We
*
Fwiw, wi.ki isn't really available. I looked into it years ago, and
Kiribati charges excessive amounts for their domains (like 10 grand). Dunno
if that's changed.
-Chad
On Nov 17, 2012 3:29 PM, "MZMcBride" wrote:
> Hi.
>
> I know this has come up a few times and it&
here's no way in the Gerrit UI to delete a tag, but this is
the standard Git way to do it.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Nov 21, 2012 at 4:47 PM, Željko Filipin wrote:
> On Wed, Nov 21, 2012 at 10:27 PM, Chad wrote:
>> `git push origin :refs/tags/mytag`
>
> Should we be able to delete branches too? This does not work for me:
>
> $ git push gerrit :debug
> remote: Processing changes
ase my inclination is to licence the whole extension (containing
> the external library) as Apache2.0 but I'm happy to defer to normal process
> if there is one.
>
If you can't use an Apache library in a GPL extension, then licensing
start purging all pages on
$theseWikis from Squid/Varnish" would also be nice.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
bureaucrats, pending decision or finding of consensus."
I have very tough questions that need answering before I can support this
candidate.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
;
>
Is there a reason for this? We had this hack in place to keep BZ
from spamming IRC/wikibugs-l when only the CC list changes...
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
he only one, so you're
always self-merging), you should almost never merge your own
code unless you're fixing an immediate problem (site outage, sytax
errors).
Merging non-critical code so fast before anyone even has a chance
to say "
On Tue, Dec 4, 2012 at 3:27 PM, Chad wrote:
> On Tue, Dec 4, 2012 at 3:24 PM, Tyler Romeo wrote:
>> Don't we have some sort of policy about an individual merging commits that
>> he/she uploaded?
>>
>
> Yes. We've been over this a dozen times--if you&#
On Tue, Dec 4, 2012 at 3:46 PM, Daniel Friesen
wrote:
> On Tue, 04 Dec 2012 12:37:02 -0800, Chad wrote:
>
>> On Tue, Dec 4, 2012 at 3:27 PM, Chad wrote:
>>>
>>> On Tue, Dec 4, 2012 at 3:24 PM, Tyler Romeo wrote:
>>>>
>>>> Don't we h
On Wed, Dec 5, 2012 at 5:05 AM, Krinkle wrote:
> On Dec 4, 2012, at 9:46 PM, Daniel Friesen wrote:
>
>> On Tue, 04 Dec 2012 12:37:02 -0800, Chad wrote:
>>
>>> On Tue, Dec 4, 2012 at 3:27 PM, Chad wrote:
>>>> On Tue, Dec 4, 2012 at 3:24 PM, Tyler Romeo
cky and people preferred the
plaintext. Do others have thoughts? Should we turn the default
back?
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Dec 5, 2012 at 2:57 PM, Brion Vibber wrote:
> On Wed, Dec 5, 2012 at 11:53 AM, Chad wrote:
>
>> On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapper
>> wrote:
>> > bugzilla.wikimedia.org is operational again and is now running the
>> > latest sta
On Fri, Dec 7, 2012 at 9:29 AM, Andre Klapper wrote:
> On Wed, 2012-12-05 at 00:29 +0100, Andre Klapper wrote:
>> On Tue, 2012-12-04 at 14:53 -0500, Chad wrote:
>> > On Tue, Dec 4, 2012 at 2:44 PM, Andre Klapper
>> > wrote:
>> > > The only (potenti
r option for this than defaulting the cc'er as
> wikibugs?
>
> I doub't there are that that many people that want the wikibugs-l list
> to receive a copy of every single change (Eg: cc changes) to the bug,
> But that is probably a discussion for another thread.
>
This.
here would be the verified -1).
>
> Lets open the can of worm here :)
>
> Chad came up with another idea that would be to rename Verified to
> Automatic Tests and extends it to a range of -2 .. +2 where +1 will be
> lint ok and +2 unit tests ok. Not sure how feasible it is to tweak
&g
ould show diffs of (rather than a zip download of the
file). All text-
based filetypes are already shown by the browser as diffs, but most binary
filetypes aren't shown on diff. Images originally suffered this problem, but
we fixed it[0].
There's not a config switch for what the OP is asking
it and not be afraid of messing up a real article.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Dec 12, 2012 at 1:46 PM, Ryan Kaldari wrote:
> On 12/12/12 4:44 AM, Chad wrote:
>>
>> On Wed, Dec 12, 2012 at 3:09 AM, Ryan Kaldari
>> wrote:
>>>
>>> I found a solution to the problem:
>>> If a gerrit administrator declares the mimetypes of
o you really mean http://test2.wikipedia.org? AFAIK the wikidata team uses
> this installation as a testing client for http://wikidata.org repository
> concerning the interwiki-links.
>
Indeed. I think VE will be fine though.
-Chad
___
Wikitech-l mail
f you encounter issues (like you can't review
something you used to be able to), please let me know.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I'm looking at this now.
-Chad
On Thu, Dec 13, 2012 at 4:57 PM, Bartosz Dziewoński wrote:
> I just noticed that I can no longer +1 on mediawiki/core, nor anywhere else.
>
> -- Matma Rex
>
> ___
> Wikitech-l ma
This should be fixed for all users.
-Chad
On Thu, Dec 13, 2012 at 5:02 PM, Chad wrote:
> I'm looking at this now.
>
> -Chad
>
> On Thu, Dec 13, 2012 at 4:57 PM, Bartosz Dziewoński
> wrote:
>> I just noticed that I can no longer +1 on mediawiki/core, nor anyw
es.
So, anyone who's got Verified permissions on a repository
(project owners, this means you), beginning tomorrow at around
13:00 UTC you will see extended Verified options. We'll let
everyone know when this is complete.
--
The Gerrit/CI guys
Chad & Antoine
___
On Mon, Dec 17, 2012 at 11:45 PM, Chad wrote:
> Hello,
>
> After some of the recent changes to the Gerrit workflow with
> Jenkins and Zuul, we've received some complaints about how
> Jenkins is reporting its results. Right now, it is using both the
> "Verified" a
licy? If not,
> where should we state the policy so that people are aware of it?
>
test is very similar, only it doesn't run off the full cluster, just a
single apache (and uses the nfs copy, so it's good to use before
scapping). Whatever policy we come up with should clarify when
to
).
> Followers will be unaffected.
>
This shouldn't be renamed imho, since it's not about MediaWiki--it's about
Wikimedia tech generally.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Dec 18, 2012 at 2:50 PM, Quim Gil wrote:
> On 12/18/2012 11:21 AM, Chad wrote:
>>
>> On Tue, Dec 18, 2012 at 1:14 PM, Quim Gil wrote:
>>>
>>> * @wikimediatech is fine as a bot driven account. As soon as I find out
>>> who
>>> ha
e areas
> (projects, subfolders etc)?
> Letting new contributors search manually for a patch reviewer feels as
> wrong as letting new bug reporters search for an assignee or somebody to
> comment on their report.
>
No. I remember hearing some mutterings about a plugin to do
think we should *fail*
patches for something that's almost always harmless. The only
reason I ask is because you say warning here but failure on the
bug.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
's currently very popular
> with us techies (but broadening its base).
>
Fwiw, I've never even heard of this until now.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Jan 2, 2013 at 3:02 AM, Thomas Gries wrote:
> mwbook #06 MediaWiki Git Guide (MGG)
>
Please do not add more pages to the Git documentation.
It's confusing enough for people as it is.
-Chad
___
Wikitech-l mailing list
k any action since September last year.)
>
We're still not on 2.5.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
to bikeshed (a little) on the "SNAPSHOT-for-1.21" tag
names, but I was looking for something that would be unlikely to
conflict with people's existing tags/branches, and clear that it's a
snapshot in most instances.
I don't have an exact date picked for deployment
On Mon, Jan 7, 2013 at 7:15 PM, Krinkle wrote:
> On Jan 7, 2013, at 8:03 PM, Chad wrote:
>
>> I'm thinking we configure $wgExtDistBranches as follows:
>>
>> $wgExtDistBranches = array(
>> 'master',
>> 'SNAPSHOT-for-1.21',
>>
On Tue, Jan 8, 2013 at 7:01 AM, Chad wrote:
>> Why not use what we already use: REL1_20 etc.
>>
>
> At the time, I thought it might conflict with something. However,
> you're probably right and it'll be easier to remember :)
>
I've now tagged all ext
On Thu, Jan 10, 2013 at 10:32 AM, Chad wrote:
> On Tue, Jan 8, 2013 at 7:01 AM, Chad wrote:
>>> Why not use what we already use: REL1_20 etc.
>>>
>>
>> At the time, I thought it might conflict with something. However,
>> you're probably right and it
bmitted. But hopefully this will
be much easier for people soon :)
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
n-
> fortunately) never be closed.
>
> Is there another software project that uses the summary line
> in a similar way to MediaWiki?
>
Really, we should be using them in the footer so gerrit can track them.
Eg:
===
Some awesome new feature
Blah blah blah
I did stuff
Fixed this too.
Bug: 1234
Change-Id: I
===
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
of the box or require
> an extension to fully support?
>
I'd say extension. I can think of lots of wikis that don't use
disambiguation pages. If we really want, we can stash it in
the default tarball along with the other bundled extensions.
-Chad
__
s to fix these from the UI means we won't need
to mark people as -1 to do so.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
the exit code 139, you can reattempt
> a merge of it by revoting CR+2 or sending a rebased patchset.
>
>
> Our bug (with MediaWiki backtraces)
> https://bugzilla.wikimedia.org/show_bug.cgi?id=43972
>
> Upstream bug:
> https://
On Wed, Jan 16, 2013 at 6:07 PM, Tim Starling wrote:
> On 17/01/13 00:14, Chad wrote:
>> Really, I think the whole thread is moot with the pending upgrade.
>> Typos should always be fixed before merging (I think we all agree?),
>> and the new abilities to fix these from the U
Hi,
There's been a lot of bikeshedding topics recently. On things ranging
from spaces, to typos, to naming things. I was kind of tired of these
mundane threads, so I decided to start one on something productive.
What color should the bikeshed be?
I vote blue.
gt; they can do a quick grep search on the commit log and find the relevant
> commits.
>
It's even easier than that:
https://gerrit.wikimedia.org/r/#/q/bug:43523,n,z
Gerrit indexes these values, so you can search for
bug:123 or rt:456.
-Chad
___
from converting extensions or other code to
Git if someone decides to resurrect a project. Finally, this does not
affect the Wikimedia repository, which still has a couple of active
projects.
-Chad
[0] http://www.mediawiki.org/wiki/Special:Code/MediaWiki
__
On Thu, Jan 24, 2013 at 1:05 PM, Chad wrote:
> Hi all,
>
> I've been taking a look at the SVN history[0], and it doesn't look like
> anything is actively using SVN anymore. Looking at the logs, it doesn't
> look like much of anything has been committed in the last
2] I had some code in 1.20 that created a namespace via a
> wgExtensionFunctions hook that I recall working does not
>
Is there a reason you can't just add them to $wgExtraNamespaces?
As long as the wikis are known (meta, testwiki, etc), then you can
just apply the name
rybody loves '.tab.', forever, that's fine with me too!
>
I really don't like .tab.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
yIndexOutOfBounds errors you saw in some diffs.
* Ability to leave comments on a whole file (instead of just a line in a
file)
* Search suggestions
* More unicorns!
We're planning to do this on 1:00-2:00UTC on February 12th (that's
17:00-18:00 PST on February 11th) --
On Mon, Feb 4, 2013 at 9:19 AM, Mark A. Hershberger wrote:
> On 02/04/2013 06:44 AM, Chad wrote:
>> ** We'll be replacing Gitweb with Gitblit once the initial dust of the
>> upgrade settles
>
> Does this mean new links will be in place? I've used links like
&
On Mon, Feb 4, 2013 at 10:21 AM, Sébastien Santoro
wrote:
> On Mon, Feb 4, 2013 at 3:29 PM, Chad wrote:
>>> Does this mean new links will be in place? I've used links like
>>> https://gerrit.wikimedia.org/r/gitweb?p=mediawiki%2Fcore.git;a=commit;h=f04103185a071f
(as in,
granted to all registered gerrit users), so anyone should be able
to do anything on it they want (direct pushing, make branches,
tag something, review, submit, etc).
As always, please let me know if you have any problems.
-Chad
___
On Mon, Feb 4, 2013 at 6:44 AM, Chad wrote:
> Hi,
>
> After much delay, Gerrit 2.6 will be coming to our servers. This release
> brings a *lot* of really cool features and fixes, but I'd like to outline a
> couple of the major ones:
>
> * A stable, documented REST
iki. I give it
> up. :-(((
>
Sharepoint? You have my deepest condolences.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ot;nobody wants to see how a
sausage is made." :)
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ncluded.
> So yes, I think it should be merged, better late than never.
>
Yes, and you weren't alone in thinking (or saying) that.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
l:Import). I don't see any
reason we couldn't start importing things.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ainly
> hasten the process.
>
+1. With the important caveat that incremental improvements
are always easier to review and merge than omnibus rewrites.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.
I think that this is a solution in search
of a problem.
-Chad
On Feb 7, 2013 1:18 AM, "Tyler Romeo" wrote:
> Yes, but we don't have to keep all three extension pages. As the MediaWiki
> community, don't we want to make things simpler for sysadmins? We can't
>
Until we forbid pasting code on-wiki,
I don't see how there's anything we
can do.
-Chad
On Feb 7, 2013 1:28 AM, "Q" wrote:
> On 2/7/2013 12:24 AM, Chad wrote:
> > I think that this is a solution in search
> > of a problem.
> >
>
> How about saying,
>> extensions are largely unmaintained (all popular and active extensions have
>> long since moved to Gerrit). As always, these extensions will remain in SVN
>> should anyone still want the code.
>
> Also worth mentioning, our SVN is now read-only.
>
This ac
On Mon, Feb 4, 2013 at 6:44 AM, Chad wrote:
> Hi,
>
> After much delay, Gerrit 2.6 will be coming to our servers. This release
> brings a *lot* of really cool features and fixes, but I'd like to outline a
> couple of the major ones:
>
I realized a little bit ago that I
Hmm, you're right. Guess I forgot to mention it in the project status. Oh
well, it's just SVN ;-)
-Chad
On Feb 9, 2013 6:09 PM, "Platonides" wrote:
> On 07/02/13 21:54, Chad wrote:
> > On Thu, Feb 7, 2013 at 3:50 PM, Platonides wrote:
> >> Also wort
the store.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I believe Mariya is talking about the internal APIs available to extensions,
(eg: User, Title, EditPage, so forth), not the public API.
Yay, acronyms!
-Chad
On Mon, Feb 11, 2013 at 8:14 AM, Yuri Astrakhan wrote:
> Mariya,
>
> Could you be more specific? What types of changes caused e
On Fri, Feb 8, 2013 at 8:52 AM, Chad wrote:
> Rest assured--we will still be getting the latest and greatest. And we're
> still
> on target for late Monday/early Tuesday.
>
Friendly reminder that Gerrit will be coming down in about an hour
for the upgrade. During the upgrade, y
On Mon, Feb 11, 2013 at 6:49 PM, Chad wrote:
> On Fri, Feb 8, 2013 at 8:52 AM, Chad wrote:
>> Rest assured--we will still be getting the latest and greatest. And we're
>> still
>> on target for late Monday/early Tuesday.
>>
>
> Friendly reminder that Gerri
On Mon, Feb 11, 2013 at 11:57 PM, Matthew Flaschen
wrote:
> On 02/11/2013 09:33 PM, Chad wrote:
>> There might be a few problems left over with the IRC notifications,
>> I'll tackle those tomorrow (making sure replication is working properly
>> now). If you spot any oth
On Tue, Feb 12, 2013 at 1:45 PM, Matthew Walker wrote:
> I am liking the new UI features. However -- I notice that I seem to have
> lost +2 rights to mediawiki/core. Are we rolling back the policy that all
> foundation developers have +2?
>
No, this should not have chang
On Tue, Feb 12, 2013 at 4:18 PM, Merlijn van Deen wrote:
> Hi Chad,
>
> On 12 February 2013 03:33, Chad wrote:
>> Took a few minutes longer than expected, but we're back up and
>> everything's live. We had to deploy a newer version to grab one
>> last f
sts/wiki/wikitech/319925
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
"can review all extensions" group is easy, but allowing for
exemptions will be a pain to manage the ACLs for. For every extension
that opts out of being reviewed by this group, we'd have to adjust its
ACL to block the inherited permissions.
-Chad
___
's not
maintained by anyone, I think we can just AGF.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
x27;s no
multiple inheritance), so things in mediawiki/extensions/* all have the
same permissions. So having rules that apply to only some of those
repositories requires editing ACLs for each repository in each "group."
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Feb 13, 2013 at 9:33 PM, Marco Fleckinger
wrote:
>
>
> On 02/14/2013 03:28 AM, Chad wrote:
>>
>> On Wed, Feb 13, 2013 at 9:22 PM, Marco Fleckinger
>> wrote:
>>>>>
>>>>> Having a "can review all extensions" group is e
to have this ability any time soon?
>
Yes, a library has been written for Scribunto called "ustring" to
handle unicode. We've actually got docs for this (and a couple
of other libraries) available on mw.org[0].
-Chad
[0] https://www.mediawiki.org/wi
;t do that--for the same reason we can't do automatic whitespace
fixing. Changing a commit would alter the sha1, which would mean
people's clones wouldn't match up with the remote (eg: you push a
change, merge it, and git pull wouldn't be able to just fast forward)
-Chad
__
On Tue, Feb 19, 2013 at 2:36 AM, MZMcBride wrote:
> Hi.
>
> I wrote <https://www.mediawiki.org/wiki/Gerrit/Reports> over the weekend.
>
This is really cool--glad to see the new API getting some usage.
-Chad
___
Wikitech-l maili
rit? I think it's great that we're expanding test coverage, but
without feedback on people's patches they're usually unaware that they're
breaking things.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Fri, Feb 22, 2013 at 11:30 PM, MZMcBride wrote:
> Matthew Flaschen wrote:
>>On 02/22/2013 09:38 PM, Chad wrote:
>>>So, I've seen this site tossed around quite a bit recently, and I'm
>>>curious: is there any plan to start integrating this jenkins and our
&
On Sat, Feb 23, 2013 at 12:19 AM, Brian Wolff wrote:
> On 2013-02-23 1:15 AM, "Chad" wrote:
>>
>> On Fri, Feb 22, 2013 at 11:30 PM, MZMcBride wrote:
>> > Matthew Flaschen wrote:
>> >>On 02/22/2013 09:38 PM, Chad wrote:
>> >>>So, I&
On Sat, Feb 23, 2013 at 12:27 AM, Brian Wolff wrote:
> On 2013-02-23 1:24 AM, "Chad" wrote:
>>
>> On Sat, Feb 23, 2013 at 12:19 AM, Brian Wolff wrote:
>> > On 2013-02-23 1:15 AM, "Chad" wrote:
>> >>
>> >> On Fri, Feb 22
etc).
I'm curious if other tools like BZ have similar switching costs.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
;m in favor
of dropping that one altogether.
- MSSQL would be nice to improve.
- Oracle support's not bad (maybe not perfect), freakolowsy would
know more.
- Postgres support needs major work. There's a lot of inconsistencies
between PG and the other backends (especially for install/upgrad
On Mon, Feb 25, 2013 at 7:48 AM, Mark A. Hershberger wrote:
> Other than that, I can only add my +1 to dropping DB2 support. I don't
> know of it being used anywhere.
>
https://gerrit.wikimedia.org/r/#/c/50764/
-Chad
___
Wikitech-
On Mon, Feb 25, 2013 at 9:53 AM, Sumana Harihareswara
wrote:
>> * Make a meta-schema so that we no longer use tables.sql as a canonical
>> source. Chad and Max started in
>> http://svn.wikimedia.org/viewvc/mediawiki/branches/abstract-schema/ .
>> See
>>
t my notes if anyone wants some examples of the
> type mapping issues. I think an abstract tables.sql is a good general
> approach, but getting from here to there is going to require a lot
> of work slogging through those data types.
>
This was exactly what we tried with the abstract
>
As I said earlier in the thread, it's still in SVN. I didn't bother migrating
it because nobody was caring at the time. If anyone's wanting to dust
it off and make a new branch for core, we can do that.
-Chad
___
Wiki
nel, nobody would object.
>
+1. No new channels, no new mailing lists, it just serves to fracture
discussion even further.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
cker, but it's early and I haven't had any caffeine.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ll sorts?
> Not just #mediawiki devs and so, but also bot devs, tool devs etc...
> that's what gry meant
>
I have no problem with this.
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Feb 27, 2013 at 10:08 PM, Bináris wrote:
> Is there any news in this case? How can we get Module translated?
>
Submit a change to Gerrit. Follow the examples set here:
https://gerrit.wikimedia.org/r/#/c/51207/
https://gerrit.wikimedia.org/r/#/c/49826/
It's not worth losing your
job just to hang out on IRC :)
-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
1 - 100 of 1218 matches
Mail list logo
