> The flip side of this is that nonprofits who should be spending
money feeding the hungry or whatever they do -- are forced to pay a lot
more money so that every customization they want can be done is such a
way that it is contributed back. <br>><br>> I can see why you would want to do it that way, but I don't think you should judge others who choose not to. <br><br>Sorry, but I have to judge, constantly, since a big (though shrinking) part of what we do is clean up other people's messes.<br>
<br>> For example, a client came to me and wanted view data in a way
that wasn't right for Views. I just added it to my custom module and
it did exactly what that client wanted. And it was done the Drupal way.
It took me a couple of hours. I guess I could have built a new
Views module -- that no one else would have ever used -- and charged 10
times as much. <br><br>I don't think you get what I'm saying. I'm saying that by offering to save a client $10 today, you are costing them $20 tomorrow. I obviously don't know the real numbers, but my point is that there are real costs to doing things on the cheap, and while it may take the sticker shock out of a sale, it certainly isn't helping set real expectations regarding the cost of a piece of technology over its lifespan.<br>
<br>I'd also ask: did your release your views code? Did you at least submit a patch that others could look at? I can't see how these things could/should take 10x the amount of time, but even if they did, your client would be thanking you as soon as the custom software you created didn't jive with the software the rest of the community used and supported.<br>
<br>In short: you are hiding costs, not lowering them, and that doesn't help non-profits any more than for-profits.<br><br>--<br>Alex Urevick-Ackelsberg<br>ZivTech, LLC<br><a href="http://zivtech.com">http://zivtech.com</a><br>
<a href="mailto:alex@zivtech.com">alex@zivtech.com</a><br>office: (267) 940-7737<br>cell: (215) 866-8956<br>skype: zivtech<br>aim: zivtech<br><br><br>2009/3/29 Sam Cohen <<a href="mailto:sam@samcohen.com">sam@samcohen.com</a>><br>
><br>><br>> On Sun, Mar 29, 2009 at 10:16 AM, Alex Urevick-Ackelsberg <<a href="mailto:Alex@zivtech.com">Alex@zivtech.com</a>> wrote:<br>>><br>>> > .. and for those who have used Drupal as more of a framework with advanced CMS components ready built.<br>
>> ><br>>> > The work I've done is firmly is the second set.<br>>><br>>> And how much of that code have you released into the wild? It strikes<br>>> me that your problem may be, well, your problem. It's not up to me to<br>
>> release your code and I can't force you to actually take an active<br>>> part in the community.<br>>><br>>> Start generalizing/releasing your code, and maybe you won't have as many issues.<br>
>><br>>> --<br>><br>> <br>> The flip side of this is that nonprofits who should be spending money feeding the hungry or whatever they do -- are forced to pay a lot more money so that every customization they want can be done is such a way that it is contributed back. <br>
><br>> I can see why you would want to do it that way, but I don't think you should judge others who choose not to. <br>><br>> For example, a client came to me and wanted view data in a way that wasn't right for Views. I just added it to my custom module and it did exactly what that client wanted. And it was done the Drupal way. It took me a couple of hours. I guess I could have built a new Views module -- that no one else would have ever used -- and charged 10 times as much. <br>
><br>><br>> Sam<br>><br>> _______________________________________________<br>> consulting mailing list<br>> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>> <a href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
><br><br>