Karl Fogel wrote:
> Michael W Thelen <email@example.com> writes:
>> Probably closer to a few minutes a day... when I was reading the mailing
>> list regularly, it was very easy to push patches through the process
>> described above. Once I started getting distracted by other things, it
>> turned into about an hour of work every three weeks or so, whenever I
>> caught up on reading the list. Speaking of which, I will catch up again
>> on any patches that have been posted in the past week, and will make the
>> Ruby script and a database dump available online. I'll post again when
>> it's ready.
Sounds like you've gotten it figured out pretty well. I've been playing
around with a python script to do the same thing. It logs into my mail
server, filters for messages with PATCH, and determines if there are any
responses. It still requires some human intervention, but I can see why
it would only take a few minutes a day.
>> By the way, I have no problem with either you or Kamesh taking over the
>> position, but I think it's probably not my decision to make. Any other
>> developers, what do you think?
> If Kamesh and Hyrum think they can do it in tandem, so much the
> better. If they think (or one of them thinks) it's better to keep it
> centralized in one person, then I suggest whoever responded first take
> it. Unless some other factor can be found: for example, if one of
> them is really busy and is glad for the other to do it, then that
> answers the question.
> IOW, best for them to figure it out. (I'd be happy to flip a coin if
> they want that, but it may not be needed.)
Based on Michael's description of the process, I think that there is
probably too little work to split it up. I've been following the list
(and submitting the very occasional patch) for more than a year and
would like to contribute. I've got a good understanding of the
subversion community, as well as the code, but not enough time to do
anything major. Managing patches is a simple task that I can do right now.
So, I basically am willing and would like to be the patch manager. I
think it would allow Kamesh to continue to focus on development, as well
as give me an easy way to contribute. Ultimately, I'm happy with
whatever is best for the project.
Received on Sat Sep 9 01:16:10 2006