On Jun 29, 2012, at 12:11 PM, Jared Johnson wrote: >>> At any rate, if a branch like this exists and someone else had the time >>> and motivation to do the leg work of applying enhancements from the >>> various forks to the core branch, I would most definitely ask my employers >>> to put most of our codebase at your disposal to do this. Even if the >>> result wasn't something we could use, and we had to remain forked... at >>> least it would be useful to _someone_ :) >> >> https://github.com/qpsmtpd-dev/qpsmtpd-dev > > OK, as promised, I've asked my employers to put most of our codebase at > your disposal to do this :) I'm waiting on a response -- my boss is a > very busy guy, but he's also very friendly to FOSS. Hopefully I'll be > able to make most or all of our code available via public read-only SVN > soon. > > -Jared
Calling all forks. If you have a fork of QP and would like to become much less forked, or perhaps even be able to use QP without being forked at all, this would be a great time to bring out your fork. My biggest goal for the forked dev branch is to push QP forward to the point where the main branch is usable for everyone. Ideally, by twiddling a few bits in config/*, everyone can get exactly the behavior they want. Yes, I know it's probably not possible, but I believe it's a worthy goal. I'm taking greater liberties with QP core than the main branch does. For example, I've added methods in Plugin.pm, which have me with resistance (passive or active, doesn't matter). I don't care if they exist there or in some other class I can inherit. They just need to have a place, and I'm not going to waste time guessing where Ask or Robert might approve. If many forks come forward, I expect to do more of this. With any luck, the -dev branch will be much better for it, and the results can be merged back into the main QP branch, in whatever fashion the bit keepers see fit. Matt
