You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Erik Hatcher <li...@ehatchersolutions.com> on 2003/08/20 15:25:14 UTC
vote for me
No, not for governor of California!
But as a tapestry committer :)
I'm digging through the source code and have found some JavaDoc
corrections. Rather than creating a patch and Bugzilla issue, it'd be
easier for me to commit it myself. Why make a newbie a committer?
Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer, and well, I
promise not to screw it up. For the time being I'll just fix
documentation issues. Any coding changes I'll run by the dev list
(except, I might get crazy and put curly brackets around all one-line
if statement blocks :).
+1 - you know ya wanna!
Erik
Re: finishLoad() gets called in the wrong order (IMHO)
Posted by Colin Sampaleanu <co...@exis.com>.
I think I am ok with using the PageRenderListener. My confusion stemmed
from an incomplete understanding of the lifecycle.
I have pages and components which have some service/business interfaces
set into them via property-specifications. Some other properties
however, which ultimately get displayed on the page, need to be set via
calls to the service interfaces. So I need to ensure that the Java code
which sets this second set of properties executes after the tapestry
framework code which sets the properties based on the
property-specification.
I think I am totally ok in using the PageRenderListener to stick the
java code initializing the second set of properties in the
pageBeginRender method. At that point I have verified that the
properties set by property-specification have been set already when that
method is called, which makes sense.
I think other people will probably be doing this sort of two phase
initialization of properties, so it may be worth mentioning specifically
in the docs.
Regards,
Colin
Howard M. Lewis Ship wrote:
>Could you be a little more specific about what you are trying to accomplish? Perhaps we need yet
>another kind of event notification for your case.
>
>The PageDetachListener will not be called until the end of the request cycle, which I suspect is too
>late.
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
>
>
>>-----Original Message-----
>>From: Colin Sampaleanu [mailto:colinml1@exis.com]
>>Sent: Wednesday, August 20, 2003 6:20 PM
>>To: Tapestry development
>>Subject: Re: finishLoad() gets called in the wrong order (IMHO)
>>
>>
>>Hmm, after more investigation, I realize that things are not quite as
>>they seem. finishLoad only gests called on the initial page load, and
>>the createPropertyInitializers call is actually only setting
>>up the prop
>>initializers as a page detach listener.
>>
>>So what I think I need to do is have this component register
>>itself as a
>>page detach listener, and do the initialization there, right?
>>
>>
>>Colin Sampaleanu wrote:
>>
>>
>>
>>>I have a big problem in that for a component, I am declaratively
>>>setting some properties via 'property-specification' elements with
>>>initial values, then in finishLoad I need to set up some
>>>
>>>
>>other items
>>
>>
>>>based on the values that were set up by the property-specification.
>>>However, property-sepcification values are set up by
>>>
>>>
>>tapestry _after_
>>
>>
>>>the call to finishLoad()
>>>
>>>from PageLoader:
>>> // Finish the load of the component; most
>>>
>>>
>>components (which
>>
>>
>>> // subclass BaseComponent) load their templates here.
>>> // That may cause yet more components to be
>>>
>>>
>>created, and more
>>
>>
>>> // bindings to be set, so we defer some checking until
>>> // later.
>>>
>>> container.finishLoad(cycle, this, containerSpec);
>>>
>>> // Finally, we create an initializer for each
>>> // specified property.
>>>
>>> createPropertyInitializers(page, container,
>>>
>>>
>>containerSpec);
>>
>>
>>>Arguably, this should be reveresed, although there may be some
>>>negative implications for some other use cases that I don't
>>>
>>>
>>know of.
>>
>>
>>>What might be the best solution, and I can't think of any real
>>>negatives, is to add another callback, let's call it
>>>
>>>
>>finishLoad2 for
>>
>>
>>>the purposes of this email, called after the call to
>>>createPropertyInitializers.
>>>
>>>What does everybody think?
>>>
>>>Regards,
>>>Colin
>>>
>>>
RE: finishLoad() gets called in the wrong order (IMHO)
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Could you be a little more specific about what you are trying to accomplish? Perhaps we need yet
another kind of event notification for your case.
The PageDetachListener will not be called until the end of the request cycle, which I suspect is too
late.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Colin Sampaleanu [mailto:colinml1@exis.com]
> Sent: Wednesday, August 20, 2003 6:20 PM
> To: Tapestry development
> Subject: Re: finishLoad() gets called in the wrong order (IMHO)
>
>
> Hmm, after more investigation, I realize that things are not quite as
> they seem. finishLoad only gests called on the initial page load, and
> the createPropertyInitializers call is actually only setting
> up the prop
> initializers as a page detach listener.
>
> So what I think I need to do is have this component register
> itself as a
> page detach listener, and do the initialization there, right?
>
>
> Colin Sampaleanu wrote:
>
> > I have a big problem in that for a component, I am declaratively
> > setting some properties via 'property-specification' elements with
> > initial values, then in finishLoad I need to set up some
> other items
> > based on the values that were set up by the property-specification.
> > However, property-sepcification values are set up by
> tapestry _after_
> > the call to finishLoad()
> >
> > from PageLoader:
> > // Finish the load of the component; most
> components (which
> > // subclass BaseComponent) load their templates here.
> > // That may cause yet more components to be
> created, and more
> > // bindings to be set, so we defer some checking until
> > // later.
> >
> > container.finishLoad(cycle, this, containerSpec);
> >
> > // Finally, we create an initializer for each
> > // specified property.
> >
> > createPropertyInitializers(page, container,
> containerSpec);
> >
> > Arguably, this should be reveresed, although there may be some
> > negative implications for some other use cases that I don't
> know of.
> > What might be the best solution, and I can't think of any real
> > negatives, is to add another callback, let's call it
> finishLoad2 for
> > the purposes of this email, called after the call to
> > createPropertyInitializers.
> >
> > What does everybody think?
> >
> > Regards,
> > Colin
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> tapestry-dev-help@jakarta.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
Re: finishLoad() gets called in the wrong order (IMHO)
Posted by Colin Sampaleanu <co...@exis.com>.
Hmm, after more investigation, I realize that things are not quite as
they seem. finishLoad only gests called on the initial page load, and
the createPropertyInitializers call is actually only setting up the prop
initializers as a page detach listener.
So what I think I need to do is have this component register itself as a
page detach listener, and do the initialization there, right?
Colin Sampaleanu wrote:
> I have a big problem in that for a component, I am declaratively
> setting some properties via 'property-specification' elements with
> initial values, then in finishLoad I need to set up some other items
> based on the values that were set up by the property-specification.
> However, property-sepcification values are set up by tapestry _after_
> the call to finishLoad()
>
> from PageLoader:
> // Finish the load of the component; most components (which
> // subclass BaseComponent) load their templates here.
> // That may cause yet more components to be created, and more
> // bindings to be set, so we defer some checking until
> // later.
>
> container.finishLoad(cycle, this, containerSpec);
>
> // Finally, we create an initializer for each
> // specified property.
>
> createPropertyInitializers(page, container, containerSpec);
>
> Arguably, this should be reveresed, although there may be some
> negative implications for some other use cases that I don't know of.
> What might be the best solution, and I can't think of any real
> negatives, is to add another callback, let's call it finishLoad2 for
> the purposes of this email, called after the call to
> createPropertyInitializers.
>
> What does everybody think?
>
> Regards,
> Colin
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
RE: finishLoad() gets called in the wrong order (IMHO)
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Could you defer the initialization until PageRenderListener.pageBeginRender()?
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Colin Sampaleanu [mailto:colinml1@exis.com]
> Sent: Wednesday, August 20, 2003 5:41 PM
> To: Tapestry development
> Subject: finishLoad() gets called in the wrong order (IMHO)
>
>
> I have a big problem in that for a component, I am
> declaratively setting
> some properties via 'property-specification' elements with initial
> values, then in finishLoad I need to set up some other items based on
> the values that were set up by the property-specification. However,
> property-sepcification values are set up by tapestry _after_
> the call to
> finishLoad()
>
> from PageLoader:
> // Finish the load of the component; most
> components (which
> // subclass BaseComponent) load their templates here.
> // That may cause yet more components to be
> created, and more
> // bindings to be set, so we defer some checking until
> // later.
>
> container.finishLoad(cycle, this, containerSpec);
>
> // Finally, we create an initializer for each
> // specified property.
>
> createPropertyInitializers(page, container,
> containerSpec);
>
> Arguably, this should be reveresed, although there may be
> some negative
> implications for some other use cases that I don't know of.
> What might
> be the best solution, and I can't think of any real
> negatives, is to add
> another callback, let's call it finishLoad2 for the purposes of this
> email, called after the call to createPropertyInitializers.
>
> What does everybody think?
>
> Regards,
> Colin
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
finishLoad() gets called in the wrong order (IMHO)
Posted by Colin Sampaleanu <co...@exis.com>.
I have a big problem in that for a component, I am declaratively setting
some properties via 'property-specification' elements with initial
values, then in finishLoad I need to set up some other items based on
the values that were set up by the property-specification. However,
property-sepcification values are set up by tapestry _after_ the call to
finishLoad()
from PageLoader:
// Finish the load of the component; most components (which
// subclass BaseComponent) load their templates here.
// That may cause yet more components to be created, and more
// bindings to be set, so we defer some checking until
// later.
container.finishLoad(cycle, this, containerSpec);
// Finally, we create an initializer for each
// specified property.
createPropertyInitializers(page, container, containerSpec);
Arguably, this should be reveresed, although there may be some negative
implications for some other use cases that I don't know of. What might
be the best solution, and I can't think of any real negatives, is to add
another callback, let's call it finishLoad2 for the purposes of this
email, called after the call to createPropertyInitializers.
What does everybody think?
Regards,
Colin
Re: vote for me
Posted by Geoff Longman <gl...@intelligentworks.com>.
In a real vote I'd probably be +1
Geoff
----- Original Message -----
From: "Howard M. Lewis Ship" <hl...@comcast.net>
To: "'Tapestry development'" <ta...@jakarta.apache.org>
Sent: Wednesday, August 20, 2003 2:42 PM
Subject: RE: vote for me
> Only votes from current Tapestry committers work. At this stage, it's
informal, seeing what people
> think ... almost like a preview of a vote. Eventually, a [VOTE] message
will go around, and we'll
> tally up what the current commiters (me, MB, Geoff, Richard, David and
Neil) have to say. Did I
> forget anyone?
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: Travis McCauley [mailto:twm4g@virginia.edu]
> > Sent: Wednesday, August 20, 2003 12:27 PM
> > To: Tapestry development
> > Subject: Re: vote for me
> >
> >
> > I don't know if my vote counts but I've got to support one of
> > our local boys.
> >
> > +1
> >
> > Travis McCauley
> > thdl.org
> > University of Virginia
> >
> > >No, not for governor of California!
> > >
> > >But as a tapestry committer :)
> > >
> > >I'm digging through the source code and have found some JavaDoc
> > >corrections. Rather than creating a patch and Bugzilla issue, it'd
> > >be easier for me to commit it myself. Why make a newbie a
> > >committer? Well, I'm an ASF Member, Ant, Lucene (& Sandbox)
> > >committer, and well, I promise not to screw it up. For the time
> > >being I'll just fix documentation issues. Any coding changes I'll
> > >run by the dev list (except, I might get crazy and put curly
> > >brackets around all one-line if statement blocks :).
> > >
> > >+1 - you know ya wanna!
> > >
> > > Erik
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
RE: vote for me
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Only votes from current Tapestry committers work. At this stage, it's informal, seeing what people
think ... almost like a preview of a vote. Eventually, a [VOTE] message will go around, and we'll
tally up what the current commiters (me, MB, Geoff, Richard, David and Neil) have to say. Did I
forget anyone?
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Travis McCauley [mailto:twm4g@virginia.edu]
> Sent: Wednesday, August 20, 2003 12:27 PM
> To: Tapestry development
> Subject: Re: vote for me
>
>
> I don't know if my vote counts but I've got to support one of
> our local boys.
>
> +1
>
> Travis McCauley
> thdl.org
> University of Virginia
>
> >No, not for governor of California!
> >
> >But as a tapestry committer :)
> >
> >I'm digging through the source code and have found some JavaDoc
> >corrections. Rather than creating a patch and Bugzilla issue, it'd
> >be easier for me to commit it myself. Why make a newbie a
> >committer? Well, I'm an ASF Member, Ant, Lucene (& Sandbox)
> >committer, and well, I promise not to screw it up. For the time
> >being I'll just fix documentation issues. Any coding changes I'll
> >run by the dev list (except, I might get crazy and put curly
> >brackets around all one-line if statement blocks :).
> >
> >+1 - you know ya wanna!
> >
> > Erik
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
Re: vote for me
Posted by Travis McCauley <tw...@virginia.edu>.
I don't know if my vote counts but I've got to support one of our local boys.
+1
Travis McCauley
thdl.org
University of Virginia
>No, not for governor of California!
>
>But as a tapestry committer :)
>
>I'm digging through the source code and have found some JavaDoc
>corrections. Rather than creating a patch and Bugzilla issue, it'd
>be easier for me to commit it myself. Why make a newbie a
>committer? Well, I'm an ASF Member, Ant, Lucene (& Sandbox)
>committer, and well, I promise not to screw it up. For the time
>being I'll just fix documentation issues. Any coding changes I'll
>run by the dev list (except, I might get crazy and put curly
>brackets around all one-line if statement blocks :).
>
>+1 - you know ya wanna!
>
> Erik
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: [VOTE] Harish Krishnaswamy as committer
Posted by David Solis <ds...@legosoft.com.mx>.
David Solis: +1
> -----Original Message-----
> From: Geoff Longman [mailto:glongman@intelligentworks.com]
> Sent: Thursday, August 21, 2003 2:00 PM
> To: Tapestry development
> Subject: Re: [VOTE] Harish Krishnaswamy as committer
>
> Geoff Longman: +1
>
> Geoffrey Longman
> Intelligent Works Inc.
>
> ----- Original Message -----
> From: "Howard M. Lewis Ship" <hl...@comcast.net>
> To: "'Tapestry development'" <ta...@jakarta.apache.org>
> Sent: Thursday, August 21, 2003 11:44 AM
> Subject: [VOTE] Harish Krishnaswamy as committer
>
>
> > I would like to nominate Harish; he has been very actively and
> enthusiastically supporting Tapestry
> > in the mailing lists. I think he would be an excellent and valuable
> asset
> to the team. And hell,
> > he's relatively local --- I might actually get to meet a Tapestry
> committer in person!
> >
> > Howard Lewis Ship: +1
> >
> >
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components
> > http://jakarta.apache.org/tapestry
> >
> >
> >
> > > -----Original Message-----
> > > From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> > > Sent: Thursday, August 21, 2003 10:59 AM
> > > To: Tapestry development
> > > Subject: Re: vote for me
> > >
> > >
> > > I was going to ask, but you beat me and answered it. I am
> > > sure there are
> > > a lot of people, including me, that would love to join this
> > > team. I have
> > > done various things to prove my interest in this project
> > > except taking
> > > the "right first step"! I have been an active participant in
> > > the mailing
> > > lists since the early days of Tapestry's Jakarta incarnation. I
have
> > > provided a patch to the Script framework, and I have
> > > privately written a
> > > document on Tapestry that is awaiting Howard's approval. I think
> > > Tapestry is going to be the future of Java web development
> > > and I would
> > > like to help make it happen faster. So please nominate me as
> > > a Tapestry
> > > committer.
> > >
> > > Regards,
> > > Harish
> > >
> > >
> > > Howard M. Lewis Ship wrote:
> > >
> > > >The more the merrier. I also liked the "goodbye Struts!"
> > > posting :-).
> > > >Let's see if there's enough interest for someone else to
> > > nominate you.
> > > >
> > > >In all fairness, we've said (and Apache guidelines state)
> > > that the real
> > > >process for becoming a committer is to become a "presence" in the
> > > >community, supply docs and patches, and work your way in. The
Apache
> > > >process has treated Tapestry quite well on many levels, I
> > > don't want to
> > > >subvert it, or give the impression of subverting it.
> > > >
> > > >BTW ... to the many lurkers; Erik has the right first step
> > > here ... if
> > > >you want to become a committer, the first step is announce
> > > that your're
> > > >interested.
> > > >--
> > > >Howard M. Lewis Ship
> > > >Creator, Tapestry: Java Web Components
> > > >http://jakarta.apache.org/tapestry
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >>-----Original Message-----
> > > >>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> > > >>Sent: Wednesday, August 20, 2003 9:25 AM
> > > >>To: tapestry-dev@jakarta.apache.org
> > > >>Subject: vote for me
> > > >>
> > > >>
> > > >>No, not for governor of California!
> > > >>
> > > >>But as a tapestry committer :)
> > > >>
> > > >>I'm digging through the source code and have found some JavaDoc
> > > >>corrections. Rather than creating a patch and Bugzilla
> > > >>issue, it'd be
> > > >>easier for me to commit it myself. Why make a newbie a
committer?
> > > >>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
> > > >>and well, I
> > > >>promise not to screw it up. For the time being I'll just fix
> > > >>documentation issues. Any coding changes I'll run by the dev
list
> > > >>(except, I might get crazy and put curly brackets around
> > > all one-line
> > > >>if statement blocks :).
> > > >>
> > > >>+1 - you know ya wanna!
> > > >>
> > > >> Erik
> > > >>
> > > >>
> > > >>------------------------------------------------------------
> > > ---------
> > > >>To unsubscribe, e-mail:
tapestry-dev-unsubscribe@jakarta.apache.org
> > > >>For additional commands, e-mail:
> > > tapestry-dev-help@jakarta.apache.org
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > >
>---------------------------------------------------------------------
> > > >To unsubscribe, e-mail:
tapestry-dev-unsubscribe@jakarta.apache.org
> > > >For additional commands, e-mail:
tapestry-dev-help@jakarta.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
tapestry-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: [VOTE] Harish Krishnaswamy as committer
Posted by Geoff Longman <gl...@intelligentworks.com>.
Geoff Longman: +1
Geoffrey Longman
Intelligent Works Inc.
----- Original Message -----
From: "Howard M. Lewis Ship" <hl...@comcast.net>
To: "'Tapestry development'" <ta...@jakarta.apache.org>
Sent: Thursday, August 21, 2003 11:44 AM
Subject: [VOTE] Harish Krishnaswamy as committer
> I would like to nominate Harish; he has been very actively and
enthusiastically supporting Tapestry
> in the mailing lists. I think he would be an excellent and valuable asset
to the team. And hell,
> he's relatively local --- I might actually get to meet a Tapestry
committer in person!
>
> Howard Lewis Ship: +1
>
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> > Sent: Thursday, August 21, 2003 10:59 AM
> > To: Tapestry development
> > Subject: Re: vote for me
> >
> >
> > I was going to ask, but you beat me and answered it. I am
> > sure there are
> > a lot of people, including me, that would love to join this
> > team. I have
> > done various things to prove my interest in this project
> > except taking
> > the "right first step"! I have been an active participant in
> > the mailing
> > lists since the early days of Tapestry's Jakarta incarnation. I have
> > provided a patch to the Script framework, and I have
> > privately written a
> > document on Tapestry that is awaiting Howard's approval. I think
> > Tapestry is going to be the future of Java web development
> > and I would
> > like to help make it happen faster. So please nominate me as
> > a Tapestry
> > committer.
> >
> > Regards,
> > Harish
> >
> >
> > Howard M. Lewis Ship wrote:
> >
> > >The more the merrier. I also liked the "goodbye Struts!"
> > posting :-).
> > >Let's see if there's enough interest for someone else to
> > nominate you.
> > >
> > >In all fairness, we've said (and Apache guidelines state)
> > that the real
> > >process for becoming a committer is to become a "presence" in the
> > >community, supply docs and patches, and work your way in. The Apache
> > >process has treated Tapestry quite well on many levels, I
> > don't want to
> > >subvert it, or give the impression of subverting it.
> > >
> > >BTW ... to the many lurkers; Erik has the right first step
> > here ... if
> > >you want to become a committer, the first step is announce
> > that your're
> > >interested.
> > >--
> > >Howard M. Lewis Ship
> > >Creator, Tapestry: Java Web Components
> > >http://jakarta.apache.org/tapestry
> > >
> > >
> > >
> > >
> > >
> > >>-----Original Message-----
> > >>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> > >>Sent: Wednesday, August 20, 2003 9:25 AM
> > >>To: tapestry-dev@jakarta.apache.org
> > >>Subject: vote for me
> > >>
> > >>
> > >>No, not for governor of California!
> > >>
> > >>But as a tapestry committer :)
> > >>
> > >>I'm digging through the source code and have found some JavaDoc
> > >>corrections. Rather than creating a patch and Bugzilla
> > >>issue, it'd be
> > >>easier for me to commit it myself. Why make a newbie a committer?
> > >>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
> > >>and well, I
> > >>promise not to screw it up. For the time being I'll just fix
> > >>documentation issues. Any coding changes I'll run by the dev list
> > >>(except, I might get crazy and put curly brackets around
> > all one-line
> > >>if statement blocks :).
> > >>
> > >>+1 - you know ya wanna!
> > >>
> > >> Erik
> > >>
> > >>
> > >>------------------------------------------------------------
> > ---------
> > >>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > >>For additional commands, e-mail:
> > tapestry-dev-help@jakarta.apache.org
> > >>
> > >>
> > >>
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
Re: [VOTE] Harish Krishnaswamy as committer
Posted by Mindbridge <mi...@yahoo.com>.
Harish has been very active in supporting Tapestry, helping people on the
list, and writing docs for beginners.
Mindbridge: +1
----- Original Message -----
From: "Howard M. Lewis Ship" <hl...@comcast.net>
To: "'Tapestry development'" <ta...@jakarta.apache.org>
Sent: Thursday, August 21, 2003 6:44 PM
Subject: [VOTE] Harish Krishnaswamy as committer
> I would like to nominate Harish; he has been very actively and
enthusiastically supporting Tapestry
> in the mailing lists. I think he would be an excellent and valuable asset
to the team. And hell,
> he's relatively local --- I might actually get to meet a Tapestry
committer in person!
>
> Howard Lewis Ship: +1
>
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> > Sent: Thursday, August 21, 2003 10:59 AM
> > To: Tapestry development
> > Subject: Re: vote for me
> >
> >
> > I was going to ask, but you beat me and answered it. I am
> > sure there are
> > a lot of people, including me, that would love to join this
> > team. I have
> > done various things to prove my interest in this project
> > except taking
> > the "right first step"! I have been an active participant in
> > the mailing
> > lists since the early days of Tapestry's Jakarta incarnation. I have
> > provided a patch to the Script framework, and I have
> > privately written a
> > document on Tapestry that is awaiting Howard's approval. I think
> > Tapestry is going to be the future of Java web development
> > and I would
> > like to help make it happen faster. So please nominate me as
> > a Tapestry
> > committer.
> >
> > Regards,
> > Harish
> >
> >
> > Howard M. Lewis Ship wrote:
> >
> > >The more the merrier. I also liked the "goodbye Struts!"
> > posting :-).
> > >Let's see if there's enough interest for someone else to
> > nominate you.
> > >
> > >In all fairness, we've said (and Apache guidelines state)
> > that the real
> > >process for becoming a committer is to become a "presence" in the
> > >community, supply docs and patches, and work your way in. The Apache
> > >process has treated Tapestry quite well on many levels, I
> > don't want to
> > >subvert it, or give the impression of subverting it.
> > >
> > >BTW ... to the many lurkers; Erik has the right first step
> > here ... if
> > >you want to become a committer, the first step is announce
> > that your're
> > >interested.
> > >--
> > >Howard M. Lewis Ship
> > >Creator, Tapestry: Java Web Components
> > >http://jakarta.apache.org/tapestry
> > >
> > >
> > >
> > >
> > >
> > >>-----Original Message-----
> > >>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> > >>Sent: Wednesday, August 20, 2003 9:25 AM
> > >>To: tapestry-dev@jakarta.apache.org
> > >>Subject: vote for me
> > >>
> > >>
> > >>No, not for governor of California!
> > >>
> > >>But as a tapestry committer :)
> > >>
> > >>I'm digging through the source code and have found some JavaDoc
> > >>corrections. Rather than creating a patch and Bugzilla
> > >>issue, it'd be
> > >>easier for me to commit it myself. Why make a newbie a committer?
> > >>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
> > >>and well, I
> > >>promise not to screw it up. For the time being I'll just fix
> > >>documentation issues. Any coding changes I'll run by the dev list
> > >>(except, I might get crazy and put curly brackets around
> > all one-line
> > >>if statement blocks :).
> > >>
> > >>+1 - you know ya wanna!
> > >>
> > >> Erik
> > >>
> > >>
> > >>------------------------------------------------------------
> > ---------
> > >>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > >>For additional commands, e-mail:
> > tapestry-dev-help@jakarta.apache.org
> > >>
> > >>
> > >>
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> > >
> > >
> > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: [VOTE] Harish Krishnaswamy as committer
Posted by Erik Hatcher <li...@ehatchersolutions.com>.
+1 for Harish! :))
On Thursday, August 21, 2003, at 04:34 PM, Harish Krishnaswamy wrote:
> Thanks for nominating me Howard! I am excited, luckily this is not a
> race against Erik, I hope, or it would be virtually impossible for me
> to win. ;)
>
> -Harish
>
> Howard M. Lewis Ship wrote:
>
>> I would like to nominate Harish; he has been very actively and
>> enthusiastically supporting Tapestry
>> in the mailing lists. I think he would be an excellent and valuable
>> asset to the team. And hell,
>> he's relatively local --- I might actually get to meet a Tapestry
>> committer in person!
>>
>> Howard Lewis Ship: +1
>>
>>
>> --
>> Howard M. Lewis Ship
>> Creator, Tapestry: Java Web Components
>> http://jakarta.apache.org/tapestry
>>
>>
>>
>>
>>> -----Original Message-----
>>> From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net] Sent:
>>> Thursday, August 21, 2003 10:59 AM
>>> To: Tapestry development
>>> Subject: Re: vote for me
>>>
>>>
>>> I was going to ask, but you beat me and answered it. I am sure there
>>> are a lot of people, including me, that would love to join this
>>> team. I have done various things to prove my interest in this
>>> project except taking the "right first step"! I have been an active
>>> participant in the mailing lists since the early days of Tapestry's
>>> Jakarta incarnation. I have provided a patch to the Script
>>> framework, and I have privately written a document on Tapestry that
>>> is awaiting Howard's approval. I think Tapestry is going to be the
>>> future of Java web development and I would like to help make it
>>> happen faster. So please nominate me as a Tapestry committer.
>>>
>>> Regards,
>>> Harish
>>>
>>>
>>> Howard M. Lewis Ship wrote:
>>>
>>>
>>>> The more the merrier. I also liked the "goodbye Struts!"
>>> posting :-).
>>>> Let's see if there's enough interest for someone else to
>>> nominate you.
>>>
>>>> In all fairness, we've said (and Apache guidelines state)
>>> that the real
>>>> process for becoming a committer is to become a "presence" in the
>>>> community, supply docs and patches, and work your way in. The
>>>> Apache process has treated Tapestry quite well on many levels, I
>>> don't want to
>>>> subvert it, or give the impression of subverting it.
>>>>
>>>> BTW ... to the many lurkers; Erik has the right first step
>>> here ... if
>>>> you want to become a committer, the first step is announce
>>> that your're
>>>> interested.
>>>> --
>>>> Howard M. Lewis Ship
>>>> Creator, Tapestry: Java Web Components
>>>> http://jakarta.apache.org/tapestry
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
>>>>> Sent: Wednesday, August 20, 2003 9:25 AM
>>>>> To: tapestry-dev@jakarta.apache.org
>>>>> Subject: vote for me
>>>>>
>>>>>
>>>>> No, not for governor of California!
>>>>>
>>>>> But as a tapestry committer :)
>>>>>
>>>>> I'm digging through the source code and have found some JavaDoc
>>>>> corrections. Rather than creating a patch and Bugzilla issue,
>>>>> it'd be easier for me to commit it myself. Why make a newbie a
>>>>> committer? Well, I'm an ASF Member, Ant, Lucene (& Sandbox)
>>>>> committer, and well, I promise not to screw it up. For the time
>>>>> being I'll just fix documentation issues. Any coding changes I'll
>>>>> run by the dev list (except, I might get crazy and put curly
>>>>> brackets around
>>> all one-line
>>>>> if statement blocks :).
>>>>>
>>>>> +1 - you know ya wanna!
>>>>>
>>>>> Erik
>>>>>
>>>>>
>>>>> ------------------------------------------------------------
>>>>>
>>> ---------
>>>
>>>>> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>>>> For additional commands, e-mail:
>>> tapestry-dev-help@jakarta.apache.org
>>>
>>>>>
>>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:
>>>> tapestry-dev-help@jakarta.apache.org
>>>>
>>>>
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>
>>
>>
Re: [VOTE] Harish Krishnaswamy as committer
Posted by Harish Krishnaswamy <hk...@comcast.net>.
Thanks for nominating me Howard! I am excited, luckily this is not a
race against Erik, I hope, or it would be virtually impossible for me to
win. ;)
-Harish
Howard M. Lewis Ship wrote:
>I would like to nominate Harish; he has been very actively and enthusiastically supporting Tapestry
>in the mailing lists. I think he would be an excellent and valuable asset to the team. And hell,
>he's relatively local --- I might actually get to meet a Tapestry committer in person!
>
>Howard Lewis Ship: +1
>
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
>
>
>>-----Original Message-----
>>From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
>>Sent: Thursday, August 21, 2003 10:59 AM
>>To: Tapestry development
>>Subject: Re: vote for me
>>
>>
>>I was going to ask, but you beat me and answered it. I am
>>sure there are
>>a lot of people, including me, that would love to join this
>>team. I have
>>done various things to prove my interest in this project
>>except taking
>>the "right first step"! I have been an active participant in
>>the mailing
>>lists since the early days of Tapestry's Jakarta incarnation. I have
>>provided a patch to the Script framework, and I have
>>privately written a
>>document on Tapestry that is awaiting Howard's approval. I think
>>Tapestry is going to be the future of Java web development
>>and I would
>>like to help make it happen faster. So please nominate me as
>>a Tapestry
>>committer.
>>
>>Regards,
>>Harish
>>
>>
>>Howard M. Lewis Ship wrote:
>>
>>
>>
>>>The more the merrier. I also liked the "goodbye Struts!"
>>>
>>>
>>posting :-).
>>
>>
>>>Let's see if there's enough interest for someone else to
>>>
>>>
>>nominate you.
>>
>>
>>>In all fairness, we've said (and Apache guidelines state)
>>>
>>>
>>that the real
>>
>>
>>>process for becoming a committer is to become a "presence" in the
>>>community, supply docs and patches, and work your way in. The Apache
>>>process has treated Tapestry quite well on many levels, I
>>>
>>>
>>don't want to
>>
>>
>>>subvert it, or give the impression of subverting it.
>>>
>>>BTW ... to the many lurkers; Erik has the right first step
>>>
>>>
>>here ... if
>>
>>
>>>you want to become a committer, the first step is announce
>>>
>>>
>>that your're
>>
>>
>>>interested.
>>>--
>>>Howard M. Lewis Ship
>>>Creator, Tapestry: Java Web Components
>>>http://jakarta.apache.org/tapestry
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
>>>>Sent: Wednesday, August 20, 2003 9:25 AM
>>>>To: tapestry-dev@jakarta.apache.org
>>>>Subject: vote for me
>>>>
>>>>
>>>>No, not for governor of California!
>>>>
>>>>But as a tapestry committer :)
>>>>
>>>>I'm digging through the source code and have found some JavaDoc
>>>>corrections. Rather than creating a patch and Bugzilla
>>>>issue, it'd be
>>>>easier for me to commit it myself. Why make a newbie a committer?
>>>>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
>>>>and well, I
>>>>promise not to screw it up. For the time being I'll just fix
>>>>documentation issues. Any coding changes I'll run by the dev list
>>>>(except, I might get crazy and put curly brackets around
>>>>
>>>>
>>all one-line
>>
>>
>>>>if statement blocks :).
>>>>
>>>>+1 - you know ya wanna!
>>>>
>>>> Erik
>>>>
>>>>
>>>>------------------------------------------------------------
>>>>
>>>>
>>---------
>>
>>
>>>>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail:
>>>>
>>>>
>>tapestry-dev-help@jakarta.apache.org
>>
>>
>>>>
>>>>
>>>>
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
>
>
RE: [VOTE] Harish Krishnaswamy as committer
Posted by Richard Lewis-Shell <rl...@mac.com>.
Richard Lewis-Shell: +1
-----Original Message-----
From: Howard M. Lewis Ship [mailto:hlship@comcast.net]
Sent: Friday, 22 August 2003 3:45 a.m.
To: 'Tapestry development'
Subject: [VOTE] Harish Krishnaswamy as committer
I would like to nominate Harish; he has been very actively and
enthusiastically supporting Tapestry in the mailing lists. I think he would
be an excellent and valuable asset to the team. And hell, he's relatively
local --- I might actually get to meet a Tapestry committer in person!
Howard Lewis Ship: +1
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> Sent: Thursday, August 21, 2003 10:59 AM
> To: Tapestry development
> Subject: Re: vote for me
>
>
> I was going to ask, but you beat me and answered it. I am
> sure there are
> a lot of people, including me, that would love to join this
> team. I have
> done various things to prove my interest in this project
> except taking
> the "right first step"! I have been an active participant in
> the mailing
> lists since the early days of Tapestry's Jakarta incarnation. I have
> provided a patch to the Script framework, and I have
> privately written a
> document on Tapestry that is awaiting Howard's approval. I think
> Tapestry is going to be the future of Java web development
> and I would
> like to help make it happen faster. So please nominate me as
> a Tapestry
> committer.
>
> Regards,
> Harish
>
>
> Howard M. Lewis Ship wrote:
>
> >The more the merrier. I also liked the "goodbye Struts!"
> posting :-).
> >Let's see if there's enough interest for someone else to
> nominate you.
> >
> >In all fairness, we've said (and Apache guidelines state)
> that the real
> >process for becoming a committer is to become a "presence" in the
> >community, supply docs and patches, and work your way in. The Apache
> >process has treated Tapestry quite well on many levels, I
> don't want to
> >subvert it, or give the impression of subverting it.
> >
> >BTW ... to the many lurkers; Erik has the right first step
> here ... if
> >you want to become a committer, the first step is announce
> that your're
> >interested.
> >--
> >Howard M. Lewis Ship
> >Creator, Tapestry: Java Web Components
> >http://jakarta.apache.org/tapestry
> >
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> >>Sent: Wednesday, August 20, 2003 9:25 AM
> >>To: tapestry-dev@jakarta.apache.org
> >>Subject: vote for me
> >>
> >>
> >>No, not for governor of California!
> >>
> >>But as a tapestry committer :)
> >>
> >>I'm digging through the source code and have found some JavaDoc
> >>corrections. Rather than creating a patch and Bugzilla issue, it'd
> >>be easier for me to commit it myself. Why make a newbie a
> >>committer?
> >>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
> >>and well, I
> >>promise not to screw it up. For the time being I'll just fix
> >>documentation issues. Any coding changes I'll run by the dev list
> >>(except, I might get crazy and put curly brackets around
> all one-line
> >>if statement blocks :).
> >>
> >>+1 - you know ya wanna!
> >>
> >> Erik
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail:
> tapestry-dev-help@jakarta.apache.org
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[VOTE] Harish Krishnaswamy as committer
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
I would like to nominate Harish; he has been very actively and enthusiastically supporting Tapestry
in the mailing lists. I think he would be an excellent and valuable asset to the team. And hell,
he's relatively local --- I might actually get to meet a Tapestry committer in person!
Howard Lewis Ship: +1
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Harish Krishnaswamy [mailto:hkrishnaswamy@comcast.net]
> Sent: Thursday, August 21, 2003 10:59 AM
> To: Tapestry development
> Subject: Re: vote for me
>
>
> I was going to ask, but you beat me and answered it. I am
> sure there are
> a lot of people, including me, that would love to join this
> team. I have
> done various things to prove my interest in this project
> except taking
> the "right first step"! I have been an active participant in
> the mailing
> lists since the early days of Tapestry's Jakarta incarnation. I have
> provided a patch to the Script framework, and I have
> privately written a
> document on Tapestry that is awaiting Howard's approval. I think
> Tapestry is going to be the future of Java web development
> and I would
> like to help make it happen faster. So please nominate me as
> a Tapestry
> committer.
>
> Regards,
> Harish
>
>
> Howard M. Lewis Ship wrote:
>
> >The more the merrier. I also liked the "goodbye Struts!"
> posting :-).
> >Let's see if there's enough interest for someone else to
> nominate you.
> >
> >In all fairness, we've said (and Apache guidelines state)
> that the real
> >process for becoming a committer is to become a "presence" in the
> >community, supply docs and patches, and work your way in. The Apache
> >process has treated Tapestry quite well on many levels, I
> don't want to
> >subvert it, or give the impression of subverting it.
> >
> >BTW ... to the many lurkers; Erik has the right first step
> here ... if
> >you want to become a committer, the first step is announce
> that your're
> >interested.
> >--
> >Howard M. Lewis Ship
> >Creator, Tapestry: Java Web Components
> >http://jakarta.apache.org/tapestry
> >
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> >>Sent: Wednesday, August 20, 2003 9:25 AM
> >>To: tapestry-dev@jakarta.apache.org
> >>Subject: vote for me
> >>
> >>
> >>No, not for governor of California!
> >>
> >>But as a tapestry committer :)
> >>
> >>I'm digging through the source code and have found some JavaDoc
> >>corrections. Rather than creating a patch and Bugzilla
> >>issue, it'd be
> >>easier for me to commit it myself. Why make a newbie a committer?
> >>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
> >>and well, I
> >>promise not to screw it up. For the time being I'll just fix
> >>documentation issues. Any coding changes I'll run by the dev list
> >>(except, I might get crazy and put curly brackets around
> all one-line
> >>if statement blocks :).
> >>
> >>+1 - you know ya wanna!
> >>
> >> Erik
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail:
> tapestry-dev-help@jakarta.apache.org
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
> >
> >
>
Re: vote for me
Posted by Harish Krishnaswamy <hk...@comcast.net>.
I was going to ask, but you beat me and answered it. I am sure there are
a lot of people, including me, that would love to join this team. I have
done various things to prove my interest in this project except taking
the "right first step"! I have been an active participant in the mailing
lists since the early days of Tapestry's Jakarta incarnation. I have
provided a patch to the Script framework, and I have privately written a
document on Tapestry that is awaiting Howard's approval. I think
Tapestry is going to be the future of Java web development and I would
like to help make it happen faster. So please nominate me as a Tapestry
committer.
Regards,
Harish
Howard M. Lewis Ship wrote:
>The more the merrier. I also liked the "goodbye Struts!" posting :-). Let's see if there's enough
>interest for someone else to nominate you.
>
>In all fairness, we've said (and Apache guidelines state) that the real process for becoming a
>committer is to become a "presence" in the community, supply docs and patches, and work your way in.
>The Apache process has treated Tapestry quite well on many levels, I don't want to subvert it, or
>give the impression of subverting it.
>
>BTW ... to the many lurkers; Erik has the right first step here ... if you want to become a
>committer, the first step is announce that your're interested.
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
>
>
>>-----Original Message-----
>>From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
>>Sent: Wednesday, August 20, 2003 9:25 AM
>>To: tapestry-dev@jakarta.apache.org
>>Subject: vote for me
>>
>>
>>No, not for governor of California!
>>
>>But as a tapestry committer :)
>>
>>I'm digging through the source code and have found some JavaDoc
>>corrections. Rather than creating a patch and Bugzilla
>>issue, it'd be
>>easier for me to commit it myself. Why make a newbie a committer?
>>Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
>>and well, I
>>promise not to screw it up. For the time being I'll just fix
>>documentation issues. Any coding changes I'll run by the dev list
>>(except, I might get crazy and put curly brackets around all one-line
>>if statement blocks :).
>>
>>+1 - you know ya wanna!
>>
>> Erik
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
>
>
Re: [Vote] to welcome Erik Hatcher as committer
Posted by Mindbridge <mi...@yahoo.com>.
After a quick look around, a clear agreement :)
Mindbridge: +1
-mb
----- Original Message -----
From: "Geoff Longman" <gl...@intelligentworks.com>
To: "Tapestry development" <ta...@jakarta.apache.org>
Sent: Thursday, August 21, 2003 9:59 PM
Subject: [Vote] to welcome Erik Hatcher as committer
> I nominate Erik Hatcher. He knows the score in jakarta-land. I think its a
> great idea.
>
> Geoff Longman: +1
>
> Geoffrey Longman
> Intelligent Works Inc.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
[RESULT] Erik Hatcher as committer
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Geoff Longman: +1
Howard M. Lewis Ship: +1
Mindbridge: +1
David Solis: +1
Richard Lewis-Shell: +1
Neil Clayton: +0 (no reply)
OK, he's in! I'll update STATUS.html and drop a note to infrastructure shortly.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
http://jakarta.apache.org/commons/sandbox/hivemind/
http://javatapestry.blogspot.com
> -----Original Message-----
> From: Geoff Longman [mailto:glongman@intelligentworks.com]
> Sent: Thursday, August 21, 2003 3:00 PM
> To: Tapestry development
> Subject: [Vote] to welcome Erik Hatcher as committer
>
>
> I nominate Erik Hatcher. He knows the score in jakarta-land.
> I think its a great idea.
>
> Geoff Longman: +1
>
> Geoffrey Longman
> Intelligent Works Inc.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: [Vote] to welcome Erik Hatcher as committer
Posted by David Solis <ds...@legosoft.com.mx>.
David Solis: +1
> -----Original Message-----
> From: Geoff Longman [mailto:glongman@intelligentworks.com]
> Sent: Thursday, August 21, 2003 2:00 PM
> To: Tapestry development
> Subject: [Vote] to welcome Erik Hatcher as committer
>
> I nominate Erik Hatcher. He knows the score in jakarta-land. I think
its a
> great idea.
>
> Geoff Longman: +1
>
> Geoffrey Longman
> Intelligent Works Inc.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: [Vote] to welcome Erik Hatcher as committer
Posted by Richard Lewis-Shell <rl...@mac.com>.
Richard Lewis-Shell: +1
-----Original Message-----
From: Geoff Longman [mailto:glongman@intelligentworks.com]
Sent: Friday, 22 August 2003 7:00 a.m.
To: Tapestry development
Subject: [Vote] to welcome Erik Hatcher as committer
I nominate Erik Hatcher. He knows the score in jakarta-land. I think its a
great idea.
Geoff Longman: +1
Geoffrey Longman
Intelligent Works Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: [Vote] to welcome Erik Hatcher as committer
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
Howard Lewis Ship: +1
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Geoff Longman [mailto:glongman@intelligentworks.com]
> Sent: Thursday, August 21, 2003 3:00 PM
> To: Tapestry development
> Subject: [Vote] to welcome Erik Hatcher as committer
>
>
> I nominate Erik Hatcher. He knows the score in jakarta-land.
> I think its a great idea.
>
> Geoff Longman: +1
>
> Geoffrey Longman
> Intelligent Works Inc.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
[Vote] to welcome Erik Hatcher as committer
Posted by Geoff Longman <gl...@intelligentworks.com>.
I nominate Erik Hatcher. He knows the score in jakarta-land. I think its a
great idea.
Geoff Longman: +1
Geoffrey Longman
Intelligent Works Inc.
Re: vote for me
Posted by Erik Hatcher <li...@ehatchersolutions.com>.
On Wednesday, August 20, 2003, at 01:15 PM, Howard M. Lewis Ship wrote:
> The more the merrier. I also liked the "goodbye Struts!" posting :-).
:))
Let's just hope Tapestry makes our projects clean and fast to develop!
> In all fairness, we've said (and Apache guidelines state) that the
> real process for becoming a
> committer is to become a "presence" in the community, supply docs and
> patches, and work your way in.
Yup, I dig it. That's how I've become a committer on other projects
and Member. I'll gladly submit patches to fix "@seince" -> "@since"
and many IField -> IFormComponent (? I think - code is on a different
machine at the moment) links in JavaDoc comments, I just figured it'd
be easier to commit it myself. I've been doing a lot of digging around
in the source code in IDEA, and I see lots of red markers in JavaDoc -
its more fun for me to look at the code if I fix it locally and not see
red squigglies everywhere, so I'm already doing that locally.
> BTW ... to the many lurkers; Erik has the right first step here ... if
> you want to become a
> committer, the first step is announce that your're interested.
Well, the traditional right step is to start submitting patches and
show you know what the heck you're doing. I'll be the first to admit
I'm learning the codebase as we speak. But at the moment I'm only
proposing JavaDoc fix-ups which are fairly pervasive.
Erik
RE: vote for me
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
The more the merrier. I also liked the "goodbye Struts!" posting :-). Let's see if there's enough
interest for someone else to nominate you.
In all fairness, we've said (and Apache guidelines state) that the real process for becoming a
committer is to become a "presence" in the community, supply docs and patches, and work your way in.
The Apache process has treated Tapestry quite well on many levels, I don't want to subvert it, or
give the impression of subverting it.
BTW ... to the many lurkers; Erik has the right first step here ... if you want to become a
committer, the first step is announce that your're interested.
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> Sent: Wednesday, August 20, 2003 9:25 AM
> To: tapestry-dev@jakarta.apache.org
> Subject: vote for me
>
>
> No, not for governor of California!
>
> But as a tapestry committer :)
>
> I'm digging through the source code and have found some JavaDoc
> corrections. Rather than creating a patch and Bugzilla
> issue, it'd be
> easier for me to commit it myself. Why make a newbie a committer?
> Well, I'm an ASF Member, Ant, Lucene (& Sandbox) committer,
> and well, I
> promise not to screw it up. For the time being I'll just fix
> documentation issues. Any coding changes I'll run by the dev list
> (except, I might get crazy and put curly brackets around all one-line
> if statement blocks :).
>
> +1 - you know ya wanna!
>
> Erik
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>