Hi,
On Thu, Dec 01, 2011 at 01:55:15AM +0100, Reinhold Kainhofer wrote:
KDE uses reviewboard... Until a few years ago, patch reviews were only
done for patches by newcomers, and that went over the mailing lists.
But now more and more features are reviewed on reviewboard.
Well, it doesn't
Hi,
On Wed, Sep 21, 2011 at 11:18:40PM +0100, Graham Percival wrote:
Think of the question in marriage ceremonies: if anybody knows of a
reason why these two should not be wed, speak now or forever hold your
peace..
Despite what one reads[1] in trashy romance novels, that question is
Hi,
On Thu, Sep 22, 2011 at 11:23:10AM +0200, m...@apollinemike.com wrote:
I don't know anything about open source projects outside of LilyPond,
but could someone branched into other GNU projects perhaps collect
this sort of info?
Having participated in or followed a number of free software
On 2011-11-30 23:27, olafbuddenha...@gmx.net wrote:
Having participated in or followed a number of free software projects
(both GNU and other) over the years, I don't know of *any* besides
LilyPond that uses a dedicated patch review tool. (Including the very
largest ones, such as Linux or GCC.)
Openocd has been using gerrit for a month now. You can go to
openocd.zylin.com to see how it's being used, and read the HACKING file in
the source tree to see how it should be used.
On Nov 30, 2011 5:52 PM, olafbuddenha...@gmx.net wrote:
Hi,
On Thu, Sep 22, 2011 at 11:23:10AM +0200,
2011/9/24 Graham Percival gra...@percival-music.ca:
I don't see this proposal (really more of a set of musings)
going anywhere. There's been a bunch of ideas:
- tool X, tool Y
- make better use of our current tools
- do a survey of what other projects do
but nothing has made a
On Sat, Sep 24, 2011 at 08:18:27AM +0100, Peekay Ex wrote:
1 Devs who put up a Rietveld put up a tracker too and use the *exact*
same title (even if it is very cryptic) the description can be simply
the link to the Rietveld URL.
Dead horse.
If I had spent *one quarter* as much time writing
On 11-09-25 03:57 AM, Janek Warchoł wrote:
2011/9/24 Graham Percivalgra...@percival-music.ca:
I don't see this proposal (really more of a set of musings)
going anywhere. There's been a bunch of ideas:
- tool X, tool Y
- make better use of our current tools
- do a survey of what other
2011/9/25 Colin Campbell c...@shaw.ca:
FWIW, Janek's bit above is just what I've been saying, and I believe it is
also what James has been suggesting. The meta-problem seemas to be that
there are developers who see the world as patches submitte4d and discussed
by email, and there are Frogs,
On Sun, Sep 25, 2011 at 10:53:13PM +0200, Janek Warchoł wrote:
I can't
see why locating and implementing a code management system which handles the
process as well as centralising the discussion, is a Bad Thing.
I don't suppose that he meant it's a bad thing. I think Graham's
concern is
I don't see this proposal (really more of a set of musings)
going anywhere. There's been a bunch of ideas:
- tool X, tool Y
- make better use of our current tools
- do a survey of what other projects do
but nothing has made a significant amount of people go yeah, that
the right direction to
Hello,
On Sat, Sep 24, 2011 at 8:01 AM, Graham Percival
gra...@percival-music.ca wrote:
I don't see this proposal (really more of a set of musings)
going anywhere. There's been a bunch of ideas:
- tool X, tool Y
- make better use of our current tools
- do a survey of what other projects
Graham Percival writes:
Yep. I'd describe it as three websites
It's a royal mess.
There is some value in having issues.google.com than only a bugs mailing
list, but there is indeed also a cost.
Any ideas on how to deal with people who only want to deal with
email?
We may want to have a
On Sep 22, 2011, at 10:49 AM, Jan Nieuwenhuizen wrote:
Graham Percival writes:
Yep. I'd describe it as three websites
It's a royal mess.
There is some value in having issues.google.com than only a bugs mailing
list, but there is indeed also a cost.
Any ideas on how to deal with
On Thu, Sep 22, 2011 at 10:49:56AM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
Any ideas on how to deal with people who only want to deal with
email?
We may want to have a look at the new http://bugs.gnu.org ,
an implementation of debbugs.
Hmm, clunky user interface.
My
2011/9/22 Graham Percival gra...@percival-music.ca:
On Thu, Sep 22, 2011 at 10:49:56AM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
Any ideas on how to deal with people who only want to deal with
email?
We may want to have a look at the new http://bugs.gnu.org ,
an
On Tue, Sep 20, 2011 at 09:32:55AM +0100, Trevor Daniels wrote:
Graham Percival wrote Tuesday, September 20, 2011 12:09 AM
* 1-5 hours: automatically switch any Patch-review to
Patch-needs_work if there are any non-LGTM comments.
Hmm. There are often comments which don't
On Tue, Sep 20, 2011 at 09:04:39PM +0200, Janek Warchoł wrote:
My impression is that the main problem is the duplicancy of data and
e-mail threads. Over and over again i'm getting lost, for example:
I can't see that going away.
- email is the most convenient option for quick discussion
-
On Tue, Sep 20, 2011 at 07:05:04AM -0600, Colin Campbell wrote:
The remaining case is where there are no comments when a countdown
expires. I've been taking that as silence implying consent, but
with no assurance that anyone has actually reviewed the patch.
Yes, that's correct. Think of the
On 11-09-21 04:13 PM, Graham Percival wrote:
On Tue, Sep 20, 2011 at 09:04:39PM +0200, Janek Warchoł wrote:
My impression is that the main problem is the duplicancy of data and
e-mail threads. Over and over again i'm getting lost, for example:
I can't see that going away.
- email is the most
On 9/21/11 9:25 PM, Colin Campbell c...@shaw.ca wrote:
On 11-09-21 04:13 PM, Graham Percival wrote:
On Tue, Sep 20, 2011 at 09:04:39PM +0200, Janek Warchoł wrote:
One thing comes to my mind: there is some code revieving tool on
Google Code. I remember that i saw it being used in some other
On Wed, Sep 21, 2011 at 09:25:45PM -0600, Colin Campbell wrote:
I'm solidly with Janek here, Graham. As it sits, a person wanting
to follow the trail of a (bug/issue/enhancement request) has to find
the thing on two separate web-sites, where developers log in despite
your comment above, using
Graham Percival wrote Tuesday, September 20, 2011 12:09 AM
1. Find a different patch management tool
2. Find a different patch and issue management tool
3. Write a few python scripts to make our lives better
I favor the last option.
So do I
* 1-5 hours: automatically switch any
On 11-09-20 02:32 AM, Trevor Daniels wrote:
Graham Percival wrote Tuesday, September 20, 2011 12:09 AM
1. Find a different patch management tool
2. Find a different patch and issue management tool
3. Write a few python scripts to make our lives better
I favor the last option.
So do I
2011/9/20 Graham Percival gra...@percival-music.ca:
On Tue, Sep 20, 2011 at 02:08:42AM +0200, Reinhold Kainhofer wrote:
Am Tuesday, 20. September 2011, 01:09:20 schrieb Graham Percival:
** Different patch and issue managment tools
* 1-3 hours: write a script that checks that every
Appropriately enough for “unlucky” number 13, this proposal is not
well-prepared. However, I’m bringing it forward in in the interest
of transparency and possibly gathering momentum.
http://lilypond.org/~graham/gop/gop_13.html
** Proposal summary
There is a fair amount of confusion with the
Am Tuesday, 20. September 2011, 01:09:20 schrieb Graham Percival:
** Different patch and issue managment tools
I have only looked at a few code review tools...
* http://code.google.com/p/gerrit/: appears to be a fork of
Rietveld. Not certain about hosting.
While gerrit is tailored
On Tue, Sep 20, 2011 at 02:08:42AM +0200, Reinhold Kainhofer wrote:
Am Tuesday, 20. September 2011, 01:09:20 schrieb Graham Percival:
** Different patch and issue managment tools
* 1-3 hours: write a script that checks that every Patch-new
can apply to master, compiles correctly,
On 11-09-19 06:25 PM, Graham Percival wrote:
On Tue, Sep 20, 2011 at 02:08:42AM +0200, Reinhold Kainhofer wrote:
Am Tuesday, 20. September 2011, 01:09:20 schrieb Graham Percival:
** Different patch and issue managment tools
* 1-3 hours: write a script that checks that every Patch-new
29 matches
Mail list logo
