Reporting.
The ability to see things like
- how many review requests a given developer has open at the moment.
- How many reviews and review requests a given developer has done in the
last X days
- Stats on review requests. Average length, Min/max. etc.
We have also had the situation where with m
Hey :) Thanks!
I think one of the things I'd really like to see is:
1) The DVCS work mentioned in this thread.
2) Maybe some work on the extensions branch.
3) File attachments
4) Some creative UI for better tracking review requests and reviews.
I'd love to see what people would brainstorm separa
ClearCase :)
On Mar 9, 5:44 pm, Christian Hammond wrote:
> Hi everyone,
>
> We've signed up again this year to take part in Google's Summer of Code.
> We're still awaiting acceptance, but want to brainstorm some ideas that
> students can work on.
>
> First of all, for those who aren't familiar wi
Now you have! Congrats!
What would you like the most seen implemented?
[]s
Eduardo.
On Thu, Mar 11, 2010 at 7:35 PM, Christian Hammond wrote:
> We haven't even been accepted yet (though we've had several student
> applications already!) so no huge hurry. Ideally, though, within 1-2 weeks.
>
>
We haven't even been accepted yet (though we've had several student
applications already!) so no huge hurry. Ideally, though, within 1-2 weeks.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Mar 11, 20
When do the suggestions need to be in by?
The company that I work for uses Reviewboard across several
international sites. I'm attempting to collect suggestion from the
other users.
Cheers,
Paul
On Fri, Mar 12, 2010 at 7:41 AM, Stephen Gallagher
wrote:
> On 03/10/2010 04:32 PM, Dan Savilonis wr
On 03/10/2010 04:32 PM, Dan Savilonis wrote:
> I would generalize Stephen's idea and just call it general support for
> distributed vcs workflow since RB isn't really built around that model
> and we're kind of stuffing it in after the fact.
>
I found some time today and decided to extend post-
It's not the complexity so much.
LDAP, AD, and S3 are things masked by auth and storage backends in Django.
We can get those cheaply and there's no user-facing UI for any of it.
Furthermore, those are needed for core operations of Review Board.
Features like advanced bug tracker integration or
bu
On Thursday 11 March 2010 05:39:29 pm Christian Hammond wrote:
> I would love integration like this, but it's going to have to wait until we
> land Extensions support in 2.0. Otherwise we end up complicating the
> codebase, dependencies, UI and settings.
I respect your call on this, but my (hackish
I would love integration like this, but it's going to have to wait until we
land Extensions support in 2.0. Otherwise we end up complicating the
codebase, dependencies, UI and settings.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. -
On Wednesday 10 March 2010 08:44:48 am Christian Hammond wrote:
> Hi everyone,
>
> We've signed up again this year to take part in Google's Summer of Code.
> We're still awaiting acceptance, but want to brainstorm some ideas that
> students can work on.
I'd like to see integration with buildbot (v
Hi, Christian.
I think the post-review tools can make some improvements on CVS like
file-revision-independent Repository. As to the dashboard of
Reviewboard, If it gives users ( super user ) the ability to Creating
and Customizing New columns, that would be cool. And more strict
permission system a
I spent some time on review.source.android.com a bit earlier and you're
right, it's much snappier.
I'm going to spend some time looking into what the slowdowns are. Part of it
may be due to the Django templating. Part of it is likely Pygments syntax
highlighting. I'll spend some time poking around
I think it's just a general performance comparison, though initial
diff loading is particularly slow. I haven't profiled it, but if you
compare loading reviews.reviewboard.org dashboard to
review.source.android.com, or one of the diffs, the latter just feels
much more instantaneous. I don't know ho
Agreed on both parts.
There's a bit more that Review Board does than Gerrit and Rietveld under the
hood, but we should certainly strive to make things faster. Is there a
specific area where Review Board feels slower to you?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - htt
I would generalize Stephen's idea and just call it general support for
distributed vcs workflow since RB isn't really built around that model
and we're kind of stuffing it in after the fact.
I'd also love to see performance improvements. I haven't done any real
comparisons, but Rietveld and Gerrit
It was discussed in another thread, but I think it would be great to improve
the git support by handling patch-sets in post-review.
The idea would be to support the following workflow:
Create a branch based on the upstream master (the repository that RB is
storing).
Apply several patches on that
Hi everyone,
We've signed up again this year to take part in Google's Summer of Code.
We're still awaiting acceptance, but want to brainstorm some ideas that
students can work on.
First of all, for those who aren't familiar with this, Google Summer of Code
is a yearly program from Google where st
18 matches
Mail list logo
