Hi everyone,
Abstract
---
This mail doubles as an invitation to come to this week's ArchCom
office hour (Phab:E285), and provides an attempt to provide answers to
questions about the agenda of the Wikimedia Developer Summit
(WikiDev17). I'm hoping we find a way to work with people who
Mediawiki supports sqlite. And you can pretty much use with any webserver -
so are you basically asking for an installer? Some sort of xulrunner-esque
thing so the interface doesnt look like a web browser?
--
Brian
On Monday, September 26, 2016, Jefsey wrote:
> The personal
On Mon, Sep 26, 2016 at 5:57 AM, Andrew Otto wrote:
> A public resumable stream of Wikimedia events would allow folks
> outside of WMF networks to build realtime stream processing tooling on top
> of our data. Folks with their own Spark or Flink or Storm clusters (in
>
There new skin called polygerrit fixes all the issues described here. It is
moving along greatly but it doesn't support all browsers yet, namely Internet
Explorer due to polygerrit using es6 and internet explorer does not support
es6. They are going to something in the q2 of next year work on
On Sun, Sep 25, 2016 at 5:41 AM, Tim Starling
wrote:
> On 25/09/16 21:09, Bináris wrote:
> > I try to familiarize myself with Gerrit which is not a good example for
> > user-friendly interface.
> > I noticed a letter B in the upper right corner of the screen, and I
> >
I developed a MediaWikiLite system many years ago which worked
reasonably well. It was for having a wiki on a memory stick that
included the content and ability to edit it in the field without net
access. It ran on SQLite and use Nanoweb, a web-server written in PHP to
reduce dependencies further.
Oh, I guess google hate yahoo.
On Monday, 26 September 2016, 16:04, Ariel Glenn WMF
wrote:
(off topic) Paladox, for some reason google seriously disliked your last 2
emails, just so you know. (Big read warning banner, etc.)
Ariel
On Mon, Sep 26, 2016 at 6:01 PM,
(off topic) Paladox, for some reason google seriously disliked your last 2
emails, just so you know. (Big read warning banner, etc.)
Ariel
On Mon, Sep 26, 2016 at 6:01 PM, Bináris wrote:
> 2016-09-26 16:54 GMT+02:00 Paladox :
>
> > What does
2016-09-26 16:54 GMT+02:00 Paladox :
> What does everyone think of using this skin https://github.com/shellscape/
> OctoGerrit it's more modern, doint know if it is mobile friendly and
> large screen friendly.
>
"Gerrit is a good tool built on a solid framework. But
What does everyone think of using this skin
https://github.com/shellscape/OctoGerrit it's more modern, doint know if it is
mobile friendly and large screen friendly.
On Monday, 26 September 2016, 15:41, Paladox
wrote:
Hi, I deployed your css hack here
On Sun, Sep 25, 2016 at 10:02 AM, Merlijn van Deen (valhallasw) <
valhall...@arctus.nl> wrote:
> You could consider not implementing streaming /at all/, and just ask
> clients to poll an http endpoint, which is much easier to implement
> client-side than anything streaming (especially when it
Hi, I deployed your css hack here http://gerrit-test.wmflabs.org/gerrit/
Please could you test it and I will then upload the change for a review and
hopefully get it merged :)
On Monday, 26 September 2016, 2:54, Bryan Davis wrote:
On Sun, Sep 25, 2016 at 6:41
Indeed, the interface is pretty terrible and pretty wide. I also have
a bunch of CSS tweaks locally (mostly to make the "Verified" column
narrower, which Bryan's CSS also does).
Another thing I would recommend is going to Settings → Preferences,
and removing a bunch of entries you don't use from
The personal way I am using wikimedia as an SQLite textbase I can
easily copy/backup from machine to machine and modifiy through
external bundled applications leads me to consider there is a need
for a wikimedia user 100% compatible "WIKILite" integrated/maintained
solution set.
1. has
Thanks for feedback so far, this is great.
> If I’m not using whatever language happens to have a library already
written, there’s no spec so I have to reverse-engineer it from an
implementation.
Brad, sorry, that is just an example on the nodejs Kasocki library. We
will need more non language
Why not expose the websockets as a standard websocket server so that it can
be consumed by any language/platform that has a standard websocket
implementation?
https://www.npmjs.com/package/ws
Pinning to socket.io versions or other abstractions leads to what happened
before, you can get stuck on
16 matches
Mail list logo