I'm all for it to fork, and I'm willing to put some of the limited resources to helping it to work on Mac OSX.
Good luck, Richard Dereck Martin wrote: > Yeah as gentoo user, I say gentoo is a great community for getting some > user support for this project. Hell, I am running gentoo-sparc on a Sun > e450 and dspam runs on that with postfix =) > > ~D > > Paul Cockings wrote: >> Thanks for all the great posts about the dspam fork. I'll stick my >> hand up and say that I'm ready to setup sf.net and fork this project >> right away. I'm going to do this for the reasons: we can't commit >> back, track changes or get a response from Sensory networks. >> >> If I'm offending anyone please say now, I'm not here to offend I just >> want to help. >> >> The short term goals will be based around a place to track and fix >> bugs, improve existing docs and generally reawaken the dspam project. >> features etc can come later. >> >> The most important bit to start is the new project name. Any >> suggestions welcome (Mine aren't very creative) >> dspam-new? >> open-dspam? >> de-spam? >> death-droid? >> >> >> >> >> >> Mark Rogers wrote: >>> Steve wrote: >>>> Be sure that everyone using DSPAM and capable of coding or doing >>>> other thins for DSPAM and some spare time will work on and for a >>>> forked DSPAM. Gentoo as community based Linux distro will sure be on >>>> board. I don't mean just me. All of the Gentoo users and maintainers. >>>> >>> >>> I'd say this swings it if similar responses are found from other >>> communities (or if other communities aren't sufficiently active with >>> dspam to voice an opinion, as I suspect is the case with Debian at >>> present). If the active developers and the distros follow the fork, >>> it'll work. If not, it won't. >>> >>> The first step has to be to incorporate patches and get into a >>> "release often" position. Too many forks (imho) fail by starting out >>> with grand ideas about the future direction of the project. >>> >>> As far as I can tell (correct me if I'm wrong?) there is no way at >>> present for the community to contribute to dspam releases, as the >>> current owners are not doing anything with it so there's nowhere to >>> send patches to that could be formally adopted? If so that's what >>> forks are for. There's already enough for at least a new 3.8.x >>> release, and it can't currently happen without a fork. >>> >> >> >> !DSPAM:474c5628244461804284693! >> >> >
