Re: Extension API?

2009-09-27 Thread Sebastien Douche

On Tue, Aug 11, 2009 at 08:59, Christian Hammond  wrote:
> Hi Sebastien,

Hi Chris

> The plan is to put it into either a 1.5 or 2.0 release (depending on some
> other factors).

ok

> Now, all that being said, if you're fine with dealing with all that, we
> wouldn't mind having someone begin work and figure out what will be needed
> in the extension API. It should just be considered *highly* experimental,
> and mostly broken.
>
> I'm actually technically on vacation this week, so I won't be able to make
> this public this week, but let me know.

Hmm, I'm super busy at this moment (bad excuse I know) but I'm
interested to see what i can do with the code.




-- 
Sebastien Douche 
Twitter: http://bit.ly/afkrK (agile, python, open source)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---



Re: Extension API?

2009-08-11 Thread Christian Hammond
Oh, another thing that could be relevant to this work.

One of our Summer of Code students, Helder Ribeiro, is working on webhook
support that will basically allow you to configure a URL that Review Board
will POST to on new review requests, updates, reviews, etc. Your script can
take this info and then do something, such as grab the latest diff from
Review Board and feed it to buildbot. This will probably work perfectly fine
for buildbot. The code checking guidelines would require use of the JSON API
to post the reviews, but that's also doable.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com


On Mon, Aug 10, 2009 at 7:47 PM, Sebastien Douche  wrote:

>
> Hi there,
>  I want to know the state of extension project. I need to work on 2
> extensions:
>
> - checking code (guidelines...)
> - integration with buildbot
>
> --
> Sebastien Douche 
> Twitter: http://bit.ly/afkrK (agile, python, open source)
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---



Re: Extension API?

2009-08-11 Thread Christian Hammond
Hi Sebastien,

The plan is to put it into either a 1.5 or 2.0 release (depending on some
other factors).

Right now, we're working on 1.1, which has a couple more features going into
it before we begin the alpha/beta/rc/release cycle. There will probably be a
1.2 after that, which would be a mostly short release. I believe the
following would end up being 1.5/2.0.

The extension code exists as a private branch on git.review-board.org right
now. We can make it public, but there are a few important things to note:

1) This is not updated for Review Board 1.0.1 or SVN. It won't track HEAD
very often (though, using Git, you're free to merge and resolve conflicts in
your tree).
2) Absolutely nothing in the current extension API is set in stone, and is
definitely subject to change without notice.
3) A lot of functionality simply does not exist yet. Many things will, but
it's likely that you'll need to add new hooks into Review Board for the
things you need.
4) We can't actually support anything on this branch. If stuff horribly
breaks, we'll accept patches for fixes, but it's not going to be a priority
for us yet.

Now, all that being said, if you're fine with dealing with all that, we
wouldn't mind having someone begin work and figure out what will be needed
in the extension API. It should just be considered *highly* experimental,
and mostly broken.

I'm actually technically on vacation this week, so I won't be able to make
this public this week, but let me know.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com


On Mon, Aug 10, 2009 at 7:47 PM, Sebastien Douche  wrote:

>
> Hi there,
>  I want to know the state of extension project. I need to work on 2
> extensions:
>
> - checking code (guidelines...)
> - integration with buildbot
>
> --
> Sebastien Douche 
> Twitter: http://bit.ly/afkrK (agile, python, open source)
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---



Extension API?

2009-08-10 Thread Sebastien Douche

Hi there,
 I want to know the state of extension project. I need to work on 2 extensions:

- checking code (guidelines...)
- integration with buildbot

-- 
Sebastien Douche 
Twitter: http://bit.ly/afkrK (agile, python, open source)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---