Encouragement of contributions.

[as...@ufl.edu]

I've got a lazy suggestion (I.E. a suggestion which, if implemented, will
permit me to be more lazy).  I'm interested in messing with the Ant code, in
the hopes of eventually becoming a useful contributer.  Of course, being a new
zealot, I want to manage all my dinking -with- ant.  So I want to update my
local copy of the source by something like

ant update_source

and submit my changes with something like

ant submit_cvs

which might extract a patch from the latest reference build, and mail it to
the Right People.


So what about making such targets availiable in the build.xml that is
presented with the source dist?  It would encourage ant development, and it
would provide examples of

1) the syntax to do this additional interesting task.

2) the behavior of a development organization interested in encouraging more help.


It might even catch on in other projects.



... On the other hand, it might not be your desire to encourage new
developers -that- much. :) 


- Allen S. Rout

Re: Encouragement of contributions.

[Steve Loughran <st...@iseran.com>]

----- Original Message -----
From: <as...@ufl.edu>
To: <an...@jakarta.apache.org>
Sent: Monday, June 04, 2001 22:58
Subject: Encouragement of contributions.


>
>
> I've got a lazy suggestion (I.E. a suggestion which, if implemented, will
> permit me to be more lazy).  I'm interested in messing with the Ant code,
in
> the hopes of eventually becoming a useful contributer.  Of course, being a
new
> zealot, I want to manage all my dinking -with- ant.  So I want to update
my
> local copy of the source by something like
>
> ant update_source

this could be a target using the CVS tasks

>
> and submit my changes with something like
>
> ant submit_cvs
>
> which might extract a patch from the latest reference build, and mail it
to
> the Right People.

I think producing the patch files is practical and worthy; sending the files
could use the mimemail task posted onto this list a while back.

However, I am dubious about fully automating the submission process as there
is the need to follow the submission guidelines, especially the bits about
meaningful subjects and message bodies.

If we automate the process completely, then everyone who has edited some
code will keep on submitting it till they get a response, and without
meaningful subjects it will be hard to make sense of the submissions.

I would prefer, therfore, some task which did a cvs diff and down the tree
and stuck the diffs into a submissions directory, to a full 'workflowesque'
submission process.

Re: Encouragement of contributions.

[Peter Donald <do...@apache.org>]

At 01:58 AM 6/5/01 -0400, asr@ufl.edu wrote:
>
>
>I've got a lazy suggestion (I.E. a suggestion which, if implemented, will
>permit me to be more lazy).  I'm interested in messing with the Ant code, in
>the hopes of eventually becoming a useful contributer.  Of course, being a
new
>zealot, I want to manage all my dinking -with- ant.  So I want to update my
>local copy of the source by something like
>
>ant update_source
>
>and submit my changes with something like
>
>ant submit_cvs
>
>which might extract a patch from the latest reference build, and mail it to
>the Right People.
>
>
>So what about making such targets availiable in the build.xml that is
>presented with the source dist?  It would encourage ant development, and it
>would provide examples of
>
>1) the syntax to do this additional interesting task.
>
>2) the behavior of a development organization interested in encouraging
more help.
>
>
>It might even catch on in other projects.
>
>
>
>... On the other hand, it might not be your desire to encourage new
>developers -that- much. :) 

Actually sounds like a good idea - perfect opportunity for you to
contribute your first patch ;)

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*