Graham Wilson wrote:
On Mon, May 24, 2004 at 09:25:44PM +0200, Matthias Andree wrote:
I have consolidated Sunil's two patches into one that I call
fetchmail-6.2.5-ss1.patch, and my add-on patch (that goes only on top
of Sunil's applied patch) is fetchmail-6.2.5-ss1-ma3.patch. This is
half a year old by now... URL:
http://home.pages.de/~mandree/fetchmail/
Matthias, do you think you might be able to split these patches and send
them to Rob? Rob, can you collect them and put them up on your page with
the other patches? I'll start going through the Debian source and
spliting out patches, and send them to you also. (Rob, if your not
interested in collecting patches, I can collect and host them instead.)
I'm fine with collecting patches, but I'd also like to get information
about which patches are considered most important. For example, I'm
pretty sure that Sunil's bugfixes patch and the nodots patch are
considered important, and the pop3x patch is not, and the various uidl
patches seem to need more time to be hashed out, but I could be wrong
about those and I'm not entirely sure about others.
This will give us a good place to start with once we have a project set
up at a community site.
Here's the order of operations as I see it:
1. Determine core maintainers
2. Determine hosting and set that up
3. Put 6.2.5 into code control
4. Add baseline patches (bugfixes etc.)
5. Coders do their thing, submitting/committing new patches
6. Further administrative details get hashed out separately
(new mailing list(s), release policies, decision-making policies, etc.)
--
==============================| "A slice of life isn't the whole cake
Rob Funk <rfunk(_at_)funknet(_dot_)net> | One tooth will never make a full
grin"
http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"