On Mon, Jul 21, 2008 at 5:40 AM, Prof. Dr.-Ing. Albrecht Weinert <[EMAIL PROTECTED]> wrote: > Well, some times ago I under-went the same sought for answers, > on: > How to commit? > What is Tomcat's definition of patch? > (wrt changed or new source code) etc. > It brought me to just using substantial improvements > in a very limited scope of users. > > I'm a bit consoled, seeing not to be the only > (stupid) one who can't find the answers easily. > > Sincerely > Albrecht > > To sum it up: A manual "How to become co-developper" would be a > great help.
Have you read the materials at http://www.apache.org/dev? If not, please do. If you have, please list your specific questions so we can answer them, and hopefully document the answers. To look at the above: 1. How to commit? Answered in www.apache.org/dev. Summary: send patches through the issue tracking system, we will review them and commit them. You can't commit yourself until you're a committer, by definition. 2. What is Tomcat's definition of patch? Same as virtually every other software project out there in the world. It's a set of changes to one or more files in the Tomcat source code repository, represented usually as text diffs from the existing versions in the repository. Again, answered at www.apache.org/dev. Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
