Quote:
Originally Posted by Ntfu2
I think my comment may have been taken the wrong way. As it stands now (free) i think there should be 0 responsibility for coders to support their hacks if they do not want to or dont have time to, releasing them is gratitude enough IMO
Once there are paid hacks though, for them to be on vB.org i beleive they should have to support them 100% of the time for each and every user that requires it. This is also when it becomes more then a hobby.
|
i can only say that i agree with half of this. i think that even a free hack should be at least partially supported. if a coder releases something i think in good faith they should lend a hand to help some of us newbies that are still learning get it implemented. releasing a product that has bugs brings a certain responsibility of the author.
however, once it goes beyond that and into a legitimate support issue or for a major modification i see no reason why the author can't make money off of it, but as amy and others said, if they're gonna make money and treat it like a business then they should be treated the same way and that brings in the fee. you can't post here for free and then make money. pay to put your "business" on display. you're making money and you're supporting your mods. everyone winds up happen. the author gets the cash, the user gets the support and vb.org gets the money for allowing it all to happen (which i agree some should go to jelsoft).
ok so i'm long winded. i know this. i just think there's been alot of extremes said here and only a few see the gray area or the proverbial middle ground. i think partial commercialization can work and work well if done correctly.