You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Adam Jack <aj...@mric.coop> on 2005/06/07 18:00:51 UTC

SummerOfCode2005 :

We have (to my knowledge) three ideas posted, the first thanks to Scott.
I've been contacted (twice, in the few days since I posted it) for
gump-presentation.

    http://wiki.apache.org/general/SummerOfCode2005#gump-and-maven
    http://wiki.apache.org/general/SummerOfCode2005#gump-and-doap
    http://wiki.apache.org/general/SummerOfCode2005#gump-presentation

BTW: Did I hear correctly that we need one person per project, we can't have
more than one work together? Also, logistically, where would the source code
go -- if folks could share?

Below is what I've replied with so far:

    ------------------------------------------------------------------

Basically we have a database (in MySQL) that is constantly updated with data
produced by Gump runs, and we wish to present this data to users, for
navigation/drill down. Currently Gump2 generates static HTML from it's runs,
and this takes a lot of effort, generates a lot of (often cluttered) data,
all of which is often unused. With Gump3 we wish to be dynamic; pulling
information from the database upon demand, allowing users to request what
they want (by click, menu, or whatever). For the old way, see [1] and some
of the painful static data at [2],[3]:

[1]    http://vmgump.apache.org/gump/public/
[2]    http://vmgump.apache.org/gump/public/gump_stats/index.html
[3]    http://vmgump.apache.org/gump/public/gump_xref/index.html

Some folks would like this to be done via Apache Cocoon, however we don't
have anybody looking into that right now. It could be done via Servlets,
JSP, Struts, or even PHP. It could also be done via some Python plug-in to
Apache, I (myself) don't currently have the skills there to mentor that. So
long as this is a simple yet powerful interface it doesn't really matter
what technology is chosen.

Perhaps scan this thread on the database to see what seems most appropriate
to the schema:

    http://marc.theaimsgroup.com/?t=110255248100003&r=1&w=2

Thanks for your interest in Apache Gump.

BTW: Please come join us on the Apache Gump mailing list for further (open)
discussion. Best you speak to all of us, than just one.

    ------------------------------------------------------------------

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Re: SummerOfCode2005 :

Posted by Leo Simons <ma...@leosimons.com>.
On 07-06-2005 18:00, "Adam  Jack" <aj...@mric.coop> wrote:
> We have (to my knowledge) three ideas posted, the first thanks to Scott.

I only knew about the first one. I brought it up in fact, on members@ :-)

> I've been contacted (twice, in the few days since I posted it) for
> gump-presentation.

Kewl.

BTW, I think gump-presentation is a really big thing to tackle. Especially
as we don't have any idea ourselves as to what the presentation should look
like, students tackling this will need a near-full understanding of how gump
works. Which is fine, of course :-)

>     http://wiki.apache.org/general/SummerOfCode2005#gump-and-maven
>     http://wiki.apache.org/general/SummerOfCode2005#gump-and-doap
>     http://wiki.apache.org/general/SummerOfCode2005#gump-presentation
> 
> BTW: Did I hear correctly that we need one person per project, we can't have
> more than one work together?

We cannot have multiple people submit the same project plan to google, or
submit it together. Multiple students can work on the same ASF (sub)project,
but they apply seperately to google. I.e. A "person per project" is a
"person per 
project-as-defined-in-the-google-summer-of-code-programme-sense-of-the-word"
.

> Also, logistically, where would the source code
> go -- if folks could share?

Working on that one :-). I hope it's mostly up to us to decide. Some people
suggested setting up a sourceforge project, others suggested an incubator
project. IMHO, it goes into Gump Jira, and if there's a lot of it, we vote
'em in as committers (ie, just like with regular contributions).

The mailing list setup for these kinds of questions and answers is
code-awards@apache.org. I think you're free to subscribe, I know all mentors
should at some point.

Cheers!

LSD



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org