Thomas wrote: > Hi Adam and the rest of the group ! Hi Thomas!
> Adam you talked about implementing it with python, it will take me a lot > of time since i haven't used python before so I rather do it in Java. Fine as well :-) We want to have you as productive as possible. If you can be productive working in a certain way, chances are other people can too, which is a Good Thing(tm) as it means more potential gump developers! I'm hoping you'll be able to get deep enough into Apache Cocoon (more below) to be productive. If not, consider a python-based webapp (or something purely servlet-based) as an alternative. I've stubbed out a little in that direction as well. > But if you whant it in python fine I'll take the time and sit to to > learn python. Final result will take abit longer with python thats all. > The choice of language allso depends on what server we have. > > So whats next? Did you get something to run on your machine yet? Did you get any instructions for getting "dynagump" running? (I'm afraid we haven't been paying very close attention so far) Anyway, go get https://svn.apache.org/repos/asf/gump/branches/Gump3/ from SVN, take a look at http://wiki.apache.org/gump/VmgumpConfig for some of the things you might need to get through to run something, and go take a look at the stuff in https://svn.apache.org/repos/asf/gump/branches/Gump3/dynagump/ In particular, if you get it to run properly (its jetty+cocoon), https://svn.apache.org/repos/asf/gump/branches/Gump3/dynagump/webapp/results/projects.xsp ends up as http://localhost:8080/results/projects.xsp or something similar. > I think I need a push in the back to get started so just hit me and we'r > off. Go get yourself a running dynagump. Play with it. Read through some of the codebase. Try and learn a little about Apache Cocoon. Holler if you run into problems. Try and see if you can put in some SQL queries somewhere that result in some output. Generate a patch ("svn help diff") and send the results to this mailing list so people (eg Stefano :-)) can give some tips. Try and see if you can put some simple "workflow" in there, for example getting from the "projects" list to a "build details" page. You can get a feel for the problem and how dynagump may help solve it and hopefully you can find your way to the next steps. I think the "workflow" aspect of gump is real interesting. We generate *a lot* of data (take a look at Gump2 output: http://vmgump.apache.org/gump/public/ ) and presenting it well is a big challenge... > What exactly do I need to get started, do i need svn or can I get > the code through cvs? I have never used svn before so a short > introduction would be nice. SVN is real easy :-) There's a great book about it http://svnbook.red-bean.com/ here's how to do a checkout: http://svnbook.red-bean.com/en/1.1/ch03s04.html > how much of the Gump code do I need to know to do my task, Is it enough > to know what the database contains or do I need to integrate with the > rest of the program. I think you'll probably need to take a look at some python code to get some context about what the stuff in the database *means*. > Is the presentation a standalone webapplication? Dynagump is. > If > that is the case then I should only need to focus on the databasecontent > and the mening of it. As it is now I don't realy know what you whant me > to do and from reading some oldposts from the mailing list you don't > realy know either. Basically "gump2" generates this: http://vmgump.apache.org/gump/public/ as static HTML every day. The results from the previous day are thrown away. Gump3 is not going to generate that stuff, but instead dynamically serve up the same information, plus a lot more, as a web application. For this web application, a "stub" or "proof of concept" exists ("dynagump"). We want you to turn it from a proof of concept into something useful. At a minimum this webapp will present the same info as Gump2, but there's many more possibilities. I'm certainly not expecting you'll "get everything right" in designing this thing. It's a *big* task. Mind you, we've been thinking about this problem for over 2 years and we don't have something shiny or fancy at all yet. Gump3 is an active codebase under "heavy" development. Based on your ideas on this, the workflows and queries and web pages you design, we're probably going to be making lots of changes to the python code and the database schema, discovering and fixing bugs, etc. So we're putting you right in the middle of things :-) > Looking forward to hear your opinions and a fun and educational time > with summer of code. Woohooh! Do keep asking questions :-) cheers, Leo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
