Scott Sanders wrote:
>
> Agreed. Just wanted to move down the line and see if I wasn't
> beating my head on a rock.  I had no intention of keeping that
> syntax.

Chuckle!  You should of seen some of the hacks I had in place while Jon was
nudging me to publish the source.  Actually, come to think of it, I'm kinda
glad that you didn't.  ;-)

Note: when I started, I knew precisely zero about XSLT.

> Sam, you have done some excellent work and I definetly want to
> continue down the path while maintaining your reputation (for
> better or worse [BIG SMILEY]).

Oh, I have more than enough reputation.  ;-)

> Besides, I'm semi-exempt, havig not yet earned my 'Apache
> commit karma' :-)

Lets discuss this for a moment.  Clearly a few people including yourself
have demonstrated a deep understanding of what Gump is and have good ideas
about what it should become.

Let me be blunt about my concern: if I screw up, literally thousands of
people (perhaps even tens of thousands of people) will get an e-mail with
my name on it the very next morning.  Perhaps dozens.

There also are some very serious security concerns, which I do not care to
elaborate on at the present time.

So what I want to discuss before opening this up a bit is how to structure
a "staging area" for changes.  Perhaps the right thing to do is to have a
separate  branch.  Or a separate proposal directory.  And it is not that I
don't trust people, once people are given commit authority, I will trust
that they only make changes into the "live" branch/directory/whatever when
they are fairly confident.  Other changes should go into some sort of
staging area.

Thoughts?

> I'm in agreement.  More of an investigation as to whether it
> would be accepted here, and if that is the case, this is a
> very good thing.

Clearly Ant is OK.  Jon and others have said that Perl is OK.  Therefore
Python is too.

My advice is to pursue your interests.

- Sam Ruby


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to