gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Simons <>
Subject Re: Gump presentation
Date Wed, 10 Aug 2005 17:29:26 GMT
Thomas wrote:
> Hi !


> I have made some progress and I'm wondering where to send my code is it
> ok to just add a sub catalog to the existing svn tree if so do I have
> permisson to do so and where should I put that folder if not.

I guess that should be

I say you get to pick a fancy name :-). One suggestion would be
dynagump2, but feel free to be a little more creative.

> Where can I mail it? to this list? With a specifik format for the mail?
> Adam talked about [jira] but couldn't give me a good answer to that.

Jira has a web interface. Don't send it email.

I suggest:

1) go to

   and create a user account for yourself.
2) go to

   click on "Create a new issue in project Gump"
   create a new issue (gump project, dynagump component) describing what
   it is your uploading (eg summarise your readme or whatever). Don't
   need to be verbose.
3) create a zipfile or tarball containing *all* your sources and project
   files but no binaries (eg if you have an ant script that can generate
   the stuff don't include it) or servlet engine. Do include eg the jars
   that you use like velocity.jar or whatever that are not provided by
   the servlet engine.
   The developer submitting your patch will probably not commit
   everything in the tarball, and that might be the best possible way to
   "get" this.
4) create a new attachment to the jira issue with your zipfile

Someone'll take a look at your tarball and try and run it. People will
add comments to the jira issue (maybe they have trouble getting your
stuff to run on their systems or whatever). You can revise the attachment.

Documentation on what jira is and how to use it is at

I'm not sure whether we decided whether Gump SoC students get svn
accounts yet or what the policy is.

Two reasons for using jira:

1) there's a checkbox that says "I submit this under my CLA"
2) its how open source often works (eg you load your stuff into an issue

> Since this is my first commit to a openscource project I'm also
> interested in information of whats needed in my commit.

Actually, what you're doing is submitting a "patch". Committing means
interacting with the CVS or subversion repository directly. There's lot
of guidelines on how to submit patches for different projects:

a lot of the process is the same for different project. How to make
commits is documented in many different places as well, eg

is a neat reference.

Furthermore, it ain't that much of a "patch" (I assume you're not doing
a 'diff' against the current source tree) as much as it is a new
codebase. We just don't have slang for that ;)

> I know I need to
> have a README with installation and requirements. Also I need a TODO to
> describe what more I think can/should be done to the project.

Don't worry too much about stuff like that at the moment. It doesn't
need to be perfect. Just send what you have. We're pretty good at
reading source code. We'll no doubt provide you with lots of feedback.

> The project is build by ant to a .war archive should I make some .sh and
> .bat files for the build part.

nope. We've got ant :-)

> Should I have it as a .war or should I
> leav it as an open archive?

I don't particularly care :-)

> (.war = web archive used to make the deployment on an application server
> easyer. packs the webapplication to one single file that you deploy)
> just eager to get my code out there and to get some responce and
> feedback on it.

good! Just chuck whatever you have at the moment into jira.


- Leo

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message