on 4/13/00 9:01 PM, Chris Meyer <[EMAIL PROTECTED]> wrote:
> Has anyone had a chance to look at the stuff [look back on the messages
> from the past few days -- there aren't many so my patch should be easy to
> find]? I think I can add a lot to the overall project by pursuing
> development along this line.
Yes and no. I started to look at it but I have been extremely busy with Day
Job stuff to get a good look at it. Just so you know, I'm not ignoring you!
I will get to it, but you need to realize that we all have day jobs and it
may take a couple days...especially for stuff that looks semi complex.
> What is the procedure for getting write access to the repository? I'm
Not that much actually. Essentially you need to show strong interest in
actually working on stuff. I used to have a more open policy of just giving
it out to whomever wants it, but I have found that most of those people end
up not doing do much which kind of sucks. There are a few good gems of
course...;-)
Also, I do suggest that you make a few good patches and send them to me
first before asking for write access. This project is nearing a 2.0 release
and I'm being really careful about what is going into it at this point. The
code needs to be extremely solid. ;-)
> I'm interested in working on Turbine or else developing my own system but
> I like the idea of contributing to open source. I will be using Turbine to
> build industrial strength server systems so I will have a large stake in
> making the code work well.
That is awesome and totally appreciated. I want to you help work on this
project.
> I don't mind continuing to make small patches to the system but if the
> rest of the active developers want to add another very motivated,
> concientious, and talented programmer then please consider granting me
> write access since the development cycle for patches is too slow for any
> substantive changes in the project...
I will give it the most consideration and right now, I give you a 99.99%
chance of getting write access. I do want to review your last patch more
carefully though...that is the 0.01% that is holding things up.
> By the way, my submitted patch conflicts with the Screen.java that was
> checked in today but it is only in the end-line of the file -- most of the
> files in Turbine seem to be checked in without a concluding newline and my
> emacs editor always adds one. Go figure :)
Yea, Kawa tends to remove the ending newline for some reason.
So, the summary is:
Give me a bit of time. I WILL get to it.
thanks,
-jon stevens
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
