Hi All,
Please join me in welcoming S Page as Software Engineer in WMF’s Editor
Engagement Experiments (E3) engineering team.
Some interesting facts about S - yes his name really is 'S', cf. Ford
designer J Mays. S has been a ski instructor at Squaw Valley and a road
sweeper for the Royal
Rob Lanphier ro...@wikimedia.org wrote:
It would appear from reading this page that the only alternative to
Gerrit that has a serious following is GitHub. Is that the case?
Personally, it seems like Phabricator or Barkeep has the best chance
of dislodging Gerrit, but those won't probably get
On Wed, Jul 18, 2012 at 5:53 PM, Marcin Cieslak sa...@saper.info wrote:
Maybe this is because of the discussion format which was framed
as for and against Gerrit.
Is it possible to setup a copy of Phabricator in labs? What
is needed to help with this?
//Saper
John had one running just as
Le 18/07/12 02:41, Rob Lanphier a écrit :
It would appear from reading this page that the only alternative to
Gerrit that has a serious following is GitHub. Is that the case?
Personally, it seems like Phabricator or Barkeep has the best chance
of dislodging Gerrit, but those won't probably
On 07/18/2012 02:28 AM, Alolita Sharma wrote:
Hi All,
Please join me in welcoming S Page as Software Engineer in WMF’s Editor
Engagement Experiments (E3) engineering team.
Some interesting facts about S - yes his name really is 'S', cf. Ford
designer J Mays. S has been a ski instructor at
On 18/07/12 02:41, Rob Lanphier wrote:
Hi everyone,
It appears as though the discussion has continued apace for the Gerrit
evaluation process:
http://www.mediawiki.org/wiki/Git/Gerrit_evaluation
Thank you everyone for chipping in so far. The current format is a
mix of talk page and
Welcome, S!
--
Ori Livneh
o...@wikimedia.org
On Tuesday, July 17, 2012 at 11:28 PM, Alolita Sharma wrote:
Hi All,
Please join me in welcoming S Page as Software Engineer in WMF’s Editor
Engagement Experiments (E3) engineering team.
Some interesting facts about S - yes his name
On Wed, Jul 18, 2012 at 11:28 AM, Platonides platoni...@gmail.com wrote:
The evaluation is intended to determine if we want to continue with
gerrit or change. If we decide to change, we should then see what we
want to change to.
Maybe we would finally decide that all the alternatives are
On Tue, Jul 17, 2012 at 8:26 PM, Asher Feldman afeld...@wikimedia.orgwrote:
Hi All,
Ryan Lane and I are migrating gerrit's db to a server in eqiad (where the
gerrit app server is located) on Friday, and have a downtime window of
18:00-19:00 UTC (11am-12pm PDT). Actual downtime should be
On Wed, Jul 18, 2012 at 12:34 PM, Andrew Garrett agarr...@wikimedia.org wrote:
On Tue, Jul 17, 2012 at 8:26 PM, Asher Feldman afeld...@wikimedia.orgwrote:
Hi All,
Ryan Lane and I are migrating gerrit's db to a server in eqiad (where the
gerrit app server is located) on Friday, and have a
I don't think you can decide to change away from gerrit
without having an idea of what we want to use instead.
As I understand it, we're on gerrit because it's the least-
bad option. To show that it's no longer the least bad
option, you need to find a product that is less bad.
Agreed. Otherwise
What about changing gerrit to our needs? It's open source, I suppose.
On Wed, Jul 18, 2012 at 6:44 PM, Derric Atzrott
datzr...@alizeepathology.com wrote:
I don't think you can decide to change away from gerrit
without having an idea of what we want to use instead.
As I understand it, we're on
On Wed, Jul 18, 2012 at 1:18 PM, Petr Bena benap...@gmail.com wrote:
What about changing gerrit to our needs? It's open source, I suppose.
That's of course the route we're going right now. The biggest hurdle
to doing so is that it's written in Java, and Prolog. Neither of those
languages are
On Wed, Jul 18, 2012 at 9:33 AM, Andrew Garrett agarr...@wikimedia.org wrote:
I don't think you can decide to change away from gerrit without having an
idea of what we want to use instead. As I understand it, we're on gerrit
because it's the least-bad option. To show that it's no longer the
I currently have a set of internal users for our wiki that have
Administrator access. I also have a set of external users (our customers)
that can only read pages and create discussion pages.
I would like to remove the permission from our customers that allows them
to access the History tab. I
I'm forwarding this (below) on behalf of the Fanlore community, which is
seeking some volunteer help. Fanlore is an important archive for the
speculative fiction community. I'd appreciate it if someone could take
a few hours to help them with their current needs, and I'd be delighted
if you
On Wed, 18 Jul 2012 11:41:06 -0700, Ryan Lane rlan...@gmail.com wrote:
On Wed, Jul 18, 2012 at 1:18 PM, Petr Bena benap...@gmail.com wrote:
What about changing gerrit to our needs? It's open source, I suppose.
That's of course the route we're going right now. The biggest hurdle
to doing so
On Wed, Jul 18, 2012 at 6:17 PM, Daniel Friesen
li...@nadir-seen-fire.com wrote:
On Wed, 18 Jul 2012 11:41:06 -0700, Ryan Lane rlan...@gmail.com wrote:
On Wed, Jul 18, 2012 at 1:18 PM, Petr Bena benap...@gmail.com wrote:
What about changing gerrit to our needs? It's open source, I suppose.
Daniel Friesen li...@nadir-seen-fire.com wrote:
On Wed, 18 Jul 2012 11:41:06 -0700, Ryan Lane rlan...@gmail.com wrote:
On Wed, Jul 18, 2012 at 1:18 PM, Petr Bena benap...@gmail.com wrote:
What about changing gerrit to our needs? It's open source, I suppose.
That's of course the route we're
On 19/07/12 00:48, Marcin Cieslak wrote:
You can play live with the ORM mapper for example
and retrieve Java objects from the database (not just
rows).
//Saper
I'm not really convinced into playing with the database when not even
the database structure is easily readable (it is derived from
Rob Lanphier wrote:
It appears as though the discussion has continued apace for the Gerrit
evaluation process:
http://www.mediawiki.org/wiki/Git/Gerrit_evaluation
Really ought to get default to HTTPS working...
Thank you everyone for chipping in so far. The current format is a
mix of talk
While Gerrit's UI is not the best, I can work around that for the most part.
What bugs me the most about Gerrit are two things:
(a) A single commit is always the unit of review: While that is
reasonable in many cases, in other cases, what ought to be a unit of
review is a topic branch.
On Wed, Jul 18, 2012 at 9:30 PM, Subramanya Sastry
ssas...@wikimedia.org wrote:
(b) Commit amends hide evolution of an idea and the tradeoffs and
considerations that went into development of something -- the reviews are
all separate from git commit history. All that is seen is the final
On 07/18/2012 11:35 PM, Roan Kattouw wrote:
On Wed, Jul 18, 2012 at 9:30 PM, Subramanya Sastry
ssas...@wikimedia.org wrote:
(b) Commit amends hide evolution of an idea and the tradeoffs and
considerations that went into development of something -- the reviews are
all separate from git commit
On Wed, 18 Jul 2012 21:35:00 -0700, Roan Kattouw roan.katt...@gmail.com
wrote:
On Wed, Jul 18, 2012 at 9:30 PM, Subramanya Sastry
ssas...@wikimedia.org wrote:
(b) Commit amends hide evolution of an idea and the tradeoffs and
considerations that went into development of something -- the
25 matches
Mail list logo
