Following Christian Hammond’s last post about ReviewBoard, I figured I would give ReviewBoard a try. Basically, it’s a good solution if you’re using any kind of pastebin website to share patches and get people to review it. It has syntax highlighting, a pretty good diff viewer. You can alter the patches and add comments,... It’s still a beta so expect rough edges, but it’s really neat. It’s not really a replacement for a bugtracker, but it completes it quite well IMHO.
I’ve created an account for each developer, following the model forums.freebsd.org is using (‘@’ as a suffix). There doesn’t seem to be a way to reset a lost password, so I have to choose between setting a default password for everybody, asking interested people to mail me a password hash (algo$salt$hash, e.g. sha1$$<hash>, django supports a few algorithms), or just delete all the accounts and let people register themselves (I would just need to promote them with a ‘@’ afterwards).
Oh yeah, it’s happening here. Feel free to send bug reports upstream (when appropriate).
Comments? Suggestions?
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
I haven’t used ReviewBoard, but I’m a big fan of web based code review tools, and I spend hours each week using an internal one at my day job. I’d like to drum up more support for the need for a centralized LDAP server for all these different accounts we now have for freebsd.org services. Perforce, wiki, forums, reviewboard, and more should not all have separate accounts. It would be great to start with a simple LDAP server and gradually convert some of these services to use a centralized authentication service.
That’s what I suggested on #that-secret-channel but Simon didn’t seem too eager
I’ve done quite a lot of work with LDAP at $work lately so I’d be more than willing to help with install/admin/maintainance. We’ll have to make sure that applications can use both LDAP and another type of authentication as a fallback, cause we don’t want to store accounts for non-(developers|guests) in LDAP.
In short, +1.
LDAP would also help with looking up the full name of a developer when writing E-mail.
I had to write a script to create an address book of all developers and mailing lists at least for Alpine. The build and update scripts I use are on freefall in my bin directory.