Managing API review requests

[Mark Fortner]

Richard,
If it would help for me or others to provide feedback to them to perhaps
spur them on, let me know.  I'd be glad to do what I can. There are other
issues with the current JIRA configuration that I'd like them to address
that would also make things easier like SSO (I now have 3 Oracle-related
accounts and would rather just use my Facebook credentials to signon),
screen capture applet misconfiguration, and the ever pesky "what the hell
is the 'Van Ness' release" question. :-)

Cheers,

Mark



On Fri, Jan 18, 2013 at 10:05 AM, Richard Bair <richard.bair at oracle.com>wrote:

> Hi Mark,
>
> We have been evaluating Crucible for a while (along with Stash, which
> unfortunately doesn't handle mercurial yet). The hard part is there is a
> long process to get software hosted by Oracle IT (including thorough
> security audits etc) so it isn't something I can do quickly. This proposal
> should be seen as a temporary (where temporary might mean 1 year!) solution.
>
> Thanks
> Richard
>
> On Jan 18, 2013, at 10:00 AM, Mark Fortner <phidias51 at gmail.com> wrote:
>
> It might be easier to manage the review if you turned on Crucible in JIRA.
>  That way people's threaded comments are captured in the context of the
> code they're reviewing.  Crucible handles sending out the notifications,
> and you can configure it with Mercurial, Git, and SVN repos.  Reviews are
> handled on-line so you don't have to check out the code, to give feedback.
>
> You can see a quick video demo here:
> http://www.atlassian.com/software/crucible/overview
>
> Hope this helps,
>
> Mark
>
>
>
> On Fri, Jan 18, 2013 at 8:41 AM, Richard Bair <richard.bair at oracle.com>wrote:
>
>> > Who will do that? Should we wait for you doing it, or should we do it
>> ourselves when you send a "looks good" email?
>>
>> I will do it.
>
>
>
>