[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [dash-dev] Re: Welcome Nick Boldt as a new technology.dash Committer
|
Exploring commits? I like Search CVS better, but that's prolly just
because I helped build it. ;-) Any chance of rolling the best of both
into one combined entity? It's well-documented in the wiki, but just
in case, here's a link:
http://wiki.eclipse.org/Search_CVS%2C_Release_Notes%2C_Build_News
Of course it doesn't work for SVN, but hey. ;-)
What would be required for me to become a committer in dash-home (the
website) so I can close that bug I opened about the help doc (whether
we go the viewcvs or help.eclipse route, that is)?
N
On 10/24/07, Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> wrote:
>
> I'm sorry, Nick, no, we don't have one. I've left this email in my inbox
> for a bit here hoping to have time to write one, but what with the
> blog-o-storm and all, it's not happening. The commits explorer code is in
> org.eclipse.dash/dashboard/commits. The code consists of three parts:
>
>
> batch: the nightly (incremental) and weekly (batch) code that parses all the
> CVS and SVN histories and puts them in a giant MySQL database. Written in
> Perl and sh.
>
> web-api: web apis that read that database and return tab delimited results.
> Written in PHP.
>
> web-app: web pages that call the web-api routines and then format the output
> in pretty ways. Written in Perl CGIs. - Bjorn
>
> Nick Boldt wrote:
> Thanks! Is there a readme / faq / wiki for dash I should read?
>
> --
> [end of message]
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dash-dev
>
>