Re: Re: Candidates for maintaining DA, step up!

> Well, I'd probably be okay with testing and commiting patches. I'm using one
> patch from Guido Trotter which fixes the problem binding with v3 protocol
> servers against DA 1.5.1 that should probably go in. ;)
> 
> Do we have a triage (sp?) for patches?  I'd hate to have to search the list for
> all of the patches, then look to see which ones have been applied and which
> have not. Something akin to SourceForge's patch repository may be nice, or some
> bugzilla-like setup, so that we can mark which ones have been entered, which
> need work, and otherwise comment on the patches.

We do indeed have a patch manager in SourceForge.  But the ideal
situation would be me applying the patches and releasing a new version,
which for reasons known, is very probably not going to happen for some
time.  That's the reason for the maintainer search.

The maintainer role should do everything I do, or split the job between
several collaborators (most likely).  I only need one person which steps
up to maintain it: he/she's from that point on completely free to choose
whoever he/she needs to help him/her in delivering good quality DA =)  I
stress this: the maintainer needs not do everything.  He could limit
himself to patching up the source, writing the release notes, releasing
a new tarball once in a while, and let the others (packager, translator,
tester) do their job.  The infrastructure is already in place

> 
> -sandalle
-- 
    Manuel Amador
    Jefe de I+D
    Amauta
    +593 (9) 847-7372


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/