Re: How can I become a developer

[cmanolache]

> The best place to start, to get a feeling of the thing yourself, is the source
> code itself. There's about 40K lines right now in 3.3m1, so take it easy.
> 
> Perhaps the class diagrams will help you to start:
> 
> http://nagoya.apache.org/~costin/tomcat3

And since I don't have an index.html, the diagrams and docs are
 all contributed by Alex, I just saved them in my public_html.


> I think I read somewhere that the most important thing was to have fun, sorry
> I cannot remember the exact source. So you can pick from existing bug-reports,
> build a challenging and complicated system, write javadoc or user
> documentation, do some code-reviewing, build new test suites... Whatever you
> feel you're better at.

+1 !
( either have fun or get a paycheck :-)

Costin
( having fun )


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

Re: How can I become a developer

[cmanolache]

IMHO, the best way to become a tomcat developer is to resolve your own
problems and itches related with tomcat.

If it works fine for you and you don't need anything - then just use
it :-)

There are many areas where we need help - and you don't have to be an
expert in tomcat to help. Try to install it - is it simple enough ? Do you
find the documentation confusing ? - then try to make it better. 

Try to use it - can it integrate with your existing infrastructure ? If
not, try to make a module ( for example to authenticate against whatever
is used on your network ).

Is it easy to configure ? If not, either send documentations or fixes to
improve that. Is it fast enough ? 

In general - find something that bothers your, and fix it.

Right now what bothers me is:
- fixing the bugs from the database
- configuration - I want it to be easier to set up and manage
- scalability - what happens if you have 500 webapps ?
- facade23

Costin

> I have been following the messages from this thread.
> 
> I have also been thinking of trying to join this group.
> 
> I have read all the documentation, the open-source articles, etc.
> 
> It occurs to me that the only way to join is to find a problem by running
> it on your own system through various personallized test, and then
> informing the group of the problem, and then coming up with your own
> solution.
> 
> Is this the only way, or have I missed a note as to were a log of existing
> problems is that I can choose from and start working on?
> 
> Thanks
> Gareth
> 
> 
> 
> 
> Jon Stevens <[EMAIL PROTECTED]> on 27/02/2001 23:10:34
> 
> Please respond to [EMAIL PROTECTED]
> 
> 
> 
> To:   <[EMAIL PROTECTED]>
> cc:
> Subject:  Re: How can I become a developer
> 
> 
> on 2/26/01 8:37 PM, "jerry123" <[EMAIL PROTECTED]> wrote:
> 
> > Hi guys,
> >
> > I want to be a developer in your team. Could you tell me how to do it?.
> >
> > Thanks a lot.
> >
> > Michael
> 
> http://jakarta.apache.org/site/getinvolved.html
> 
> -jon
> 
> --
> If you come from a Perl or PHP background, JSP is a way to take
> your pain to new levels. --Anonymous
> <http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 



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

RE: How can I become a developer

[Jones, Stephen]

There is a bugzilla bug database for Tomcat at:

http://nagoya.apache.org/buzilla/

I'm not sure if they are all for Tomcat, but there is a query engine
attached to it.

Steve

> -Original Message-
> From: Alex Fernández [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 28, 2001 9:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: How can I become a developer
> 
> 
> Hi Gareth!
> 
> I'm sure someone more knowledgeable will correct me if I'm 
> wrong -- I'll offer
> you what I've found out.
> 
> [EMAIL PROTECTED] wrote:
> 
> > Hi,
> >
> > I have been following the messages from this thread.
> >
> > I have also been thinking of trying to join this group.
> 
> So are many of us. However, it seems that this works like 
> secret societies:
> they must appoint you to be a committer ;)
> 
> Anyway, no need to commit (that is, full access to the CVS 
> tree) to join in
> all the fun. All you have to do is spot a problem you'd like 
> solved, and Just
> Do It!(tm)
> 
> > I have read all the documentation, the open-source articles, etc.
> 
> The best place to start, to get a feeling of the thing 
> yourself, is the source
> code itself. There's about 40K lines right now in 3.3m1, so 
> take it easy.
> 
> Perhaps the class diagrams will help you to start:
> 
> http://nagoya.apache.org/~costin/tomcat3
> 
> > It occurs to me that the only way to join is to find a 
> problem by running
> > it on your own system through various personallized test, and then
> > informing the group of the problem, and then coming up with your own
> > solution.
> 
> You don't need personalized tests, just use your servlets or 
> JSP application.
> If you don't have one, now is the time to begin!
> 
> > Is this the only way, or have I missed a note as to were a 
> log of existing
> > problems is that I can choose from and start working on?
> 
> I think I read somewhere that the most important thing was to 
> have fun, sorry
> I cannot remember the exact source. So you can pick from 
> existing bug-reports,
> build a challenging and complicated system, write javadoc or user
> documentation, do some code-reviewing, build new test 
> suites... Whatever you
> feel you're better at.
> 
> Again, please note that I'm also learning how the whole thing 
> works, so take
> my opinions cum mica salis (that's what english folks would 
> say "with a grain
> of salt" :)
> 
> Un saludo,
> 
> Alex.
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 

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

Re: How can I become a developer

[Alex Fernández]

Hi Gareth!

I'm sure someone more knowledgeable will correct me if I'm wrong -- I'll offer
you what I've found out.

[EMAIL PROTECTED] wrote:

> Hi,
>
> I have been following the messages from this thread.
>
> I have also been thinking of trying to join this group.

So are many of us. However, it seems that this works like secret societies:
they must appoint you to be a committer ;)

Anyway, no need to commit (that is, full access to the CVS tree) to join in
all the fun. All you have to do is spot a problem you'd like solved, and Just
Do It!(tm)

> I have read all the documentation, the open-source articles, etc.

The best place to start, to get a feeling of the thing yourself, is the source
code itself. There's about 40K lines right now in 3.3m1, so take it easy.

Perhaps the class diagrams will help you to start:

http://nagoya.apache.org/~costin/tomcat3

> It occurs to me that the only way to join is to find a problem by running
> it on your own system through various personallized test, and then
> informing the group of the problem, and then coming up with your own
> solution.

You don't need personalized tests, just use your servlets or JSP application.
If you don't have one, now is the time to begin!

> Is this the only way, or have I missed a note as to were a log of existing
> problems is that I can choose from and start working on?

I think I read somewhere that the most important thing was to have fun, sorry
I cannot remember the exact source. So you can pick from existing bug-reports,
build a challenging and complicated system, write javadoc or user
documentation, do some code-reviewing, build new test suites... Whatever you
feel you're better at.

Again, please note that I'm also learning how the whole thing works, so take
my opinions cum mica salis (that's what english folks would say "with a grain
of salt" :)

Un saludo,

Alex.



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

Re: How can I become a developer

[GARETH . LEACHMAN]

Hi,

I have been following the messages from this thread.

I have also been thinking of trying to join this group.

I have read all the documentation, the open-source articles, etc.

It occurs to me that the only way to join is to find a problem by running
it on your own system through various personallized test, and then
informing the group of the problem, and then coming up with your own
solution.

Is this the only way, or have I missed a note as to were a log of existing
problems is that I can choose from and start working on?

Thanks
Gareth




Jon Stevens <[EMAIL PROTECTED]> on 27/02/2001 23:10:34

Please respond to [EMAIL PROTECTED]



To:   <[EMAIL PROTECTED]>
cc:
Subject:  Re: How can I become a developer


on 2/26/01 8:37 PM, "jerry123" <[EMAIL PROTECTED]> wrote:

> Hi guys,
>
> I want to be a developer in your team. Could you tell me how to do it?.
>
> Thanks a lot.
>
> Michael

http://jakarta.apache.org/site/getinvolved.html

-jon

--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>


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






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

Re: How can I become a developer

[Jon Stevens]

on 2/26/01 8:37 PM, "jerry123" <[EMAIL PROTECTED]> wrote:

> Hi guys,
> 
> I want to be a developer in your team. Could you tell me how to do it?.
> 
> Thanks a lot.
> 
> Michael

http://jakarta.apache.org/site/getinvolved.html

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
 && 


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