http://www.html5rocks.com/en/tutorials/appcache/beginner/
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
understand the reason cache manifests exist: for
explicitly offline applications. If your application is not an offline
application, then you should not be using cache manifests in the first
place, because that's not what it's meant for.
*-- *
*Tyler Ro
ndering options.
>
I don't have anything against this, but what's the reasoning? You now have
to parse the wikitext into HTML5 and then parse the HTML5 into PDF. I'm
guessing you've found some library that automatically "prints" HTML5, which
would make sense since b
age in Chrome
> or Safari and printing to a PDF. Future plans include using bookjs or
> the like to improve the rendering.
>
Aha awesome. Thanks for explaining.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
ogram, but I'm sure people
would agree it might be a good thing to become a mentor organization and
have students contribute to MediaWiki as part of a college credit program.
Any thoughts?
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in C
that we can still implement a maintainer system
without changing the RFC process. There's no requirement that RFC review
and maintainers be the same people. This thread is mainly a discussion
about "Architects" (or the concept thereof), and how we might want to
change the MediaWiki code
WebSockets are only supported in IE 10 and later, so you're still a bit
screwed in terms of backwards compatibility.
[1] http://www.w3.org/TR/eventsource/
[2]
https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events
[3] http://caniuse.com/#feat=eventsource
*-- *
*T
er.
>
Agreed on this. PHP isn't meant for continuous processing, regardless of if
you use SSE or WebSockets. Also it should be noted that SockJS also has
Tornado and Twisted implementations, if you want to use Python. And, of
course, if your extension needs to be scalable, they also have
ys best just to go with the flow? ;)
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
artifically, which seems to be the case.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
l free to leave it out. Thanks in advance.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
e, much much more functional, and a lot easier to use. However,
this is out-of-scope for the discussion, so if you have an opinion on
whether doing this is a good/bad idea, please start another thread.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Clas
I'll continue on the search for more third-party components, but right now
those listed seem like the main candidates (although even some of those
listed would be really difficult to do and might not happen).
*-- *
*Tyler Romeo*
Stevens Institute of Te
The RFC on third-party components may interest you:
https://www.mediawiki.org/wiki/Requests_for_comment/Third-party_components
If we use the Monolog library, which is used in Symfony and others, we can
avoid having to re-implement an entire logging framework.
*-- *
*Tyler Romeo*
Stevens
On Tue, Dec 3, 2013 at 4:39 PM, John wrote:
> VE is a BAD idea, its full of holes and bugs
Those are two separate concepts. Just because something has bugs does not
make the software itself a bad idea.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Compu
nment is never a good idea. It all depends on
what type of wikis are being run and what is being stored on them.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists
ough Gerrit.)
Right now the only somewhat proper approach to adding new core dependencies
is using Git submodules, which is not the most favorable approach for
reasons I mentioned in the beginning of the thread.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major
moot
> point for now. Though lets pretend this has already bee taken care off and
> look at solutions to the technical problem.
>
OK, in that case I will use git submodules for my upcoming third party
library patches.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of
The only things that could really be separated into libraries are the
DatabaseType hierarchy, the HTMLForm section, maybe the FileRepo / File /
FileBackend product, and maybe the JobQueue product.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 201
, but any module that is cached in localStorage will no
longer benefit from V8's compiler optimizations. It may be useful to have
an option that disables the use of localStorage for specific modules.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Scienc
On Mon, Dec 9, 2013 at 2:15 PM, Gabriel Wicke wrote:
> Are you sure this is still the case?
> https://code.google.com/p/v8/issues/detail?id=2315 seems to suggest that
> this was fixed in V8 last year.
>
Not sure if it's related, but looking at the bleeding edge compiler.cc code
directly, it expl
I'll probably try and attend, although it's during the day so there's no
guarantee my boss won't randomly schedule a meeting or something.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Tue, Dec 10, 2013 at 11:43 PM, Aaron Ha
ugging in MediaWiki.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
where
would Gadget code go? Would each gadget have its own code repository? Maybe
we'd have just one repository for all gadgets as well as common.js
(something like operations/common.js)? I don't think sending wiki edits to
Gerrit is too feasible a solution, so if this were implemented it&
now how to use it. If there were a way to submit
patchsets without using Git somehow (maybe some kind of desktop
application), it may make things easier.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wi
a sounds exciting. ;)
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
:/ There are only ten videos. Is there some sort of special upload process
that needs to be followed here? Because uploading ten things to Commons
takes all of fifteen minutes.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Wed, Dec 11, 2013 at 5
ssue, then let
people from the wikis have +2 on their wiki's Gerrit project. If the cost
of increasing site-wide security and alleviating developers' pain is a few
upset users who will get over it in a month or two, then so be it.
*-- *
*Tyler Romeo*
Stevens Institu
eview tool. Gadgets are code. It is the absolute
*correct* tool for the job. At the very least it is a more proper tool than
using wiki software. If Wikipedia wants to have any resemblance of proper
software security, having gadgets stored on wiki should disappear very
quickly.
*-- *
*Tyler
On Wed, Dec 11, 2013 at 7:26 PM, Brian Wolff wrote:
> The videos are (mostly) over 1 gb, which is our upload limit. Hence
> maintenance script needed.
>
Ah. Thanks for the clarification.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Compute
On Mon, Dec 16, 2013 at 7:08 AM, Arcane 21 wrote:
> I've tried PHP 5.5.0, had to go back to PHP 4.4.9 due to issues with
> deleting and moving pages in MediaWiki.
Is there a bug filed for this. If not please do so. MediaWiki should be
compatible with newer PHP versions.
*-- *
*
On Mon, Dec 16, 2013 at 6:54 PM, Arcane 21 wrote:
> More details can be found on the bug report I submitted on Bugzilla.
For those wondering, it is filed under bug 58532.
https://bugzilla.wikimedia.org/show_bug.cgi?id=58532
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2
ck of control structures is frustrating unless the templates are
really simple). So I'd support using Twig or something similar to it like
jinja2. Either way the RFCs can definitely be combined.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On T
hpStorm support, which is a plus.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
mption tokens. Another suggestion was to simply abandon IP blocks, since
users can easily enough change their IP addresses anyway.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing l
Right now MediaWiki installation requirements say you need MySQL 5.0.2 or
later. So my question is: is this configuration variable still necessary,
or should it be deprecated?
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Mon, Dec 30, 2013 at 5:23 PM, Thomas Gries wrote:
> This is, why we (or some core) MediaWiki developers should also attend
> such congresses like the C3 regularly.
>
Times like these living in USA is inconvenient.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
ing a software solution that makes it possible.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
s currently
is that Tor users should not be able to edit raw. Thus the issue at hand is
that there is currently no technical solution for allowing Tor users to
edit while still being able to block them. If you want to change the
consensus and unblock Tor users from editing, then it is indeed a
soci
> lets too many vandals in, we'll revoke your entire OAuth consumer key.
>
It is definitely outside of core scope, but is it within OAuth scope? If
anything I think it would be some sort of separate extension that relies on
OAuth, but is not actually part of OAuth itself.
*-
ts they go through in order to be certified for security
and whatnot (somebody correct me if I'm wrong). They have a very strict set
of software policies they must follow. Implementing a system like this to
work with donations would be extraordinarily difficult, if it's even
possible.
It's a CAPTCHA, not an article or piece of actual content. If people are
actually getting offended by randomly generated CAPTCHAs I think they need
to find something more worthwhile to complain about.
--
Tyler Romeo
On Jan 1, 2014 12:27 AM, "Benjamin Lees" wrote:
> There'
On Tue, Dec 31, 2013 at 7:56 PM, Platonides wrote:
> I think it is, for schemas created without it.
Yeah. What I mean is should it be deprecated for new installations.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Scie
On Thu, Jan 2, 2014 at 1:20 AM, VP Singh wrote:
> Donot send me spam
That email was not spam. If you don't want to receive Wikimedia development
emails, you can unsubscribe from the mailing list.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer
tion handler.
> Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to
> show detailed debugging information.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l maili
Welcome back!
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Sat, Jan 4, 2014 at 9:55 AM, Aarti K. Dwivedi
wrote:
> Welcome back Sumana! :)
>
> Cheers,
> Aarti
>
>
> On Sat, Jan 4, 2014 at 8:19 PM, Nasir Khan wrot
On Mon, Jan 6, 2014 at 2:17 PM, Terry Chay wrote:
> Shahyar G(whatever)
XD
Welcome aboard!
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
ht
How does this compare to the PECL runkit extension? Also have you
benchmarked it against Scribunto? Because Scribunto does kind of the same
exact thing except just with a different programming language (and
Scribunto uses a native interpreter rather than one written in PHP).
*-- *
*Tyler Romeo
e, and it is not worse
than a global state design; it's just different. PHP replaces global state
with things like job queues and caches, and it tends to work pretty well.
If anything it makes development easier because, not surprisingly, managing
global state is incredibly difficult.
*-- *
*
On Tue, Jan 14, 2014 at 11:07 AM, Chad wrote:
> What version is available via PEAR? Installing via that is no more
> manual than apt.
>
Also don't forget composer as well.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Co
or a while and become an established editor
4) Then ask for a global exemption
If anything it is good for stewards to not randomly grant global exemptions
to anybody who walks in off the street.
If anything I would try testing out the enwiki-specific exemption process
and see how that works out f
On Fri, Jan 17, 2014 at 10:03 PM, bawolff wrote:
> Aaron Schulz has become the first person to have approved (+2'ed) >=
> 1000 patchsets to mediawiki core
>
Wow it takes real skill to out-review the l10-bot. I'm going to have to
step up my game. ;)
*-- *
*Tyler Romeo
fuses to obey the HTTP spec. Hence the reason
why we don't have E-Tag support either.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://
ion to location, as opposed to pressing a
button and resetting my identity. Keep in mind we are not trying to
permanently block vandals, because that's impossible. We're just trying to
make vandalism difficult enough so it is no longer worthwhile.
*-- *
*Tyler Romeo*
Stevens Institute of
t if you consider your Wikipedia account to have that much value, you'd
put in the effort to make sure it is secure. To that I say see the above
paragraph.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
_
email accounts were
> hijacked.
>
This is definitely something to consider, but I feel like it would involve
changing our privacy policy. Or at the very least it would cause some
controversy related to that.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Cl
down to
the San Francisco office and show their government ID. Then we have Tim or
Brion log them in personally. ;)
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing lis
add
> that as an option.
You mean kind of like this?
https://www.mediawiki.org/wiki/Extension:SSLClientAuthentication
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailin
Can we maybe add this into Jenkins somehow? It'd be kind of nice if we
could make sure from now on that no patches break unit tests in HHVM.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Fri, Feb 7, 2014 at 3:07 PM, Ori Livneh wrote:
>
ly heard champion that rule was the Mobile Team.
>
Agreed on this. Even on Gerrit, it is hard to keep track of possible
changes and decisions being made. The mailing list is an important medium
for any significant discussion and announcements concerning MediaWiki.
*-- *
*Tyler Romeo*
Stevens
arate modules
- It provides no more information than xhprof would (and yes, xhprof is
meant for production use.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing lis
like in July or something. Once that happens we can
safely stop supporting 5.3 with the next MediaWiki release.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikim
erface
- Improved parse_url() behavior
Of course there is traits as well, but that's more of an actual new
feature, and it will be a while before MediaWiki starts using traits
everywhere.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Clas
On Wed, Feb 19, 2014 at 1:26 AM, MZMcBride wrote:
> There are likely others. What can be done to address this issue?
Only way I can think of is to improve the Lua <-> PHP API so that users can
make the queries directly.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2
.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Tue, Feb 25, 2014 at 12:16 AM, Rahul Maliakkal wrote:
> Great work Quim again!!!
>
> Regards,
> Rahul
>
>
> On Tue, Feb 25, 2014 at 12:59 AM, Harsh Kothari
> wrote:
>
o inherit
ContextSource (or hopefully have it as a trait once we move to 5.4),
but it was impossible to do that since SpecialPage decided to
implement getTitle() differently.
--
Tyler Romeo
Stevens Institute of Technology, Class of 2016
Major in Compute
e is to be more communicative with
other developers, especially when you are negating their changes or
decisions.
Thanks in advance,
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing
have to take into account extensions that incorrectly rely on
its interface, and a breakage in a deployed extension should result in an
undeployment and a fix to that extension, not a revert of the core patch.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Cla
f thing that
gets people fired at other companies.
But apparently I'm the only person that thinks this, so the WMF can feel
free to do what it wants.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
W
rging
this patch).
So to summarize, #3 is obviously not an option. For #2, are we supposed to
block core development, and let this bug persist indefinitely, because of a
much less serious bug in an extension? That really only leaves #1, but
apparently the vast minority of opponents of the original patch
as any timing
issue to consider here, I would say after a few days we'd have to reach a
solution.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@l
general rule is
> to do changes in master before cherry-picking to the branch.
>
What you're saying is that the software development process for MediaWiki
is so tightly coupled with the operations deployment process, that
development has to be held up because of problems in operations.
gt;
I think some of the things mentioned here are good solution. The biggest
problem here is that this patch was launched almost completely untested. It
should have been caught long before it was put into production.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
esponsibility of the operations team to ensure stability. Having
to revert something because that's the only way production will be stable
is not a proper workflow.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
_
rsion, are they expected to revert it within hours so that the WMF
operations team can redeploy? Or will the operations team actually test new
releases first, and refuse to update until things start working again?
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Cl
things like this happening.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
change get deployed if it "broke" tests?
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
k?
>
Yep. Hence the reason I think maybe we should work on something like the
stuff mentioned in this thread. Maybe we should be running the mobile tests
before deployment or something. I'm not sure what the exact solution is,
but I think that would be a step in the right direction.
*--
#x27;s been repeated multiple times, but I'll say it again: it is disputed as
to whether account creation was "broken". It is just a question of design
and user experience. No functionality was actually broken.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Clas
read for an explanation of how it is disputed as to whether this patch
broke anything.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wi
13/06/openstack-docker-manage-linux-containers-with-nova/
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Fri, Mar 14, 2014 at 10:43 PM, Greg Grossmeier wrote:
> But, obviously not as well integrated.
>
> --
> Sent from my phone, plea
least, does not give the opportunity for a
screwup like this.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Sun, Mar 30, 2014 at 5:23 AM, Nuria Ruiz wrote:
> >> is
> >>vulnerable, if something is set to "1234 onClick=doSome
administration.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Probably due to the Heartbleed issue. There's another thread on this
mailing list explaining that WMF has reset all user tokens and is reissuing
SSL certificates.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
I agree. I was going to attempt to fix the newest patch, but until the
semester ends I won't have a lot of time (and it seems neither does the
current patch owner).
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Fri, Apr 18, 2014 at 12:
Legoktm's patch when it's finished and merged.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ion of "mitm_and_store_in_database".
Also, fun to note that the entire application is written in CoffeeScript.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Wed, Apr 30, 2014 at 1:41 AM, James Salsman wrote:
> Would someone please
For example, Erlang with Cowboy is supposed to be a good
socket.ioimplementation, and it is truly parallel, but I've never
worked with it so
I cannot say for sure.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Sun, May 4, 2014 at 10:
conflicts? What is the rebase
process?
It's not that I'm opposed to the new system. I'm just confused as to what
the new workflow would actually be.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Mon, May 5, 2014 at 12:02 PM, Quim
r position as moderator rather than a regular user.
This idea could be applied to edits in core, and maybe posts in Flow. WMF
employees in a special user group could make an edit, and then press a
button on the history page to highlight that as an "official" edit.
*-- *
*Tyler Romeo*
.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
On Fri, May 16, 2014 at 1:47 PM, C. Scott Ananian wrote:
> On Fri, May 16, 2014 at 9:23 AM, Quim Gil wrote:
> > On Friday, May 16, 2014, Petr Bena wrote:
> >
> >> Yes. Support as ma
le account, because it's what I use for
everything.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
staying on the topic that you brought up, I do agree with keeping
skins in a separate directory than extensions. It implies a bit of control
on our part concerning how skins need to be structured, whereas if they
were extensions, we cannot place any requirements on the structure.
*-- *
*Tyle
alongside MediaWiki.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
This may be true, but like I mentioned during the IRC RFC discussion on
third-party
components, it’s a case-by-case decision, and I think in this case, SwiftMailer
is
a fairly reliable library and definitely much better than what we have
implemented
now.
--
Tyler Romeo
0xC86B42DF
From: Tony
delete it optionally for purpose X?
You can use the config script to perform database upgrades later on if you
upgrade MediaWiki versions. Most people just use the command line update.php
instead, but for some people this is not an option.
--
Tyler Romeo
0xC86B42DF
me problem, it should be split up
accordingly.
--
Tyler Romeo
0xC86B42DF
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
can be *slightly* easier.
--
Tyler Romeo
0xC86B42DF
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
be used in
the way it was shoe-horned into MediaWiki. I’m not going to re-explain this
every time because it is in multiple places on Bugzilla and in this mailing
list.
--
Tyler Romeo
0xC86B42DF
___
Wikitech-l mailing list
Wikitech-l
concerning it.
--
Tyler Romeo
0xC86B42DF
signature.asc
Description: Message signed with OpenPGP using AMPGpg
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
501 - 600 of 715 matches
Mail list logo
