Am 28.01.2015 um 16:39 schrieb Axb:
On 01/28/2015 03:58 PM, Reindl Harald wrote:* third: if you would be a smart upstream in case of a company admin asking for a change instead "write a patch" you could make a offer talking about money to include the change in the next upstream version - we sponsored changes and maintainance of projects like DBMail, Netatalk and others multiple times in the last years - just because instead pertly responses a friendly "i am not that much interested but i guess the amount of time will be xx hours for xx € per hour and so i am open"I'm not a usable Perl programmer either but I put my cash where my mouth is and have $pon$ored several major features in SA.
so would i sponsor things if it's worth
Instead of complaining, ranting and/or being frustrated, it's way more productive to open a feature request in bugzilla and sweet talk one of the main devs to add your enhancement (if they consider it worthy) or get someone to code it for you so you can use it in your deployment/SA fork. I promise you, it works.
the ranting and beeing frustrated comes from the hostile manner on that list as repsonse to *every question* starting with the reply to my first post last year in the style "go away, we don't care about milter" up to "you are outright lying" until i proved that my observations are right
frankly the intention of writing first a mail to a mailing-list before make a feature request is to find out if theres a way to change behavior via configuration and all the "creep away"-style responses don't do anything good for starting "sweet talk" nor do they give the feeling any feature request is welcome at all
another reason for first writing a mail to a list is my own developer expierience where users hundrets of times asked for things and i was able to change some behavior regression free while the user is still on the phone - not every change needs bureaucracy
BTW it is not visible which users are core-developers on this list and which are not - until now i thought you are as example
signature.asc
Description: OpenPGP digital signature
