Hi David, There are these separate tools available: http://codereview.appspot.com/ http://code.google.com/p/reviewboard/
I agree that it would be great to have a kind of "submit queue" where you see test results, etc. from proposed patches, and that it would be useful even for project members. However, we're a long way from offering something like that. As for getting contributions from developers, the most important thing is to have clear project goals, plans, and designs so that people know what you are trying to achieve. Then, don't be shy about making other people members of your project, that will make your project stronger in the long run. Thanks, jason! On Tue, Jun 23, 2009 at 10:19 AM, dirvine<[email protected]> wrote: > > Hi > > Like the facilities here, excellent, but we are attempting in house to > maximize our use of these fantastic tools and would like some > information on how effectively to use the code review tool. It appears > that it's a post commit review which is not really great for us as we > now work. > > Is it possible that we can have some kind of code review from even > anonymous developers who are not project members but wish to supply > path (review is way better) that we can check compile test etc. and > all post commit (as the developers would not have commit access, > yet!). Even better woudl be a manditory review before commit for all > developers but thats another story I suppose. > > Thanks again > David > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
