[Owasp-leaders] Communism
Andrew Petukhov
petand at lvk.cs.msu.su
Fri Feb 6 03:28:14 EST 2009
Sorry, Jeff, but you are mixing Totalitarianism and Communism :)
Communism is indeed political ideology that promotes the establishment
of an egalitarian, classless, stateless society based on common
ownership and control of the means of production and property in general.
But in bad implementation Communism tends to be Totalitarianism.
Agreed with Stephen
My 2c from Moscow
Andrew Petukhov
Jeff Williams пишет:
> Ha! I respond a bit to this in OWASP Podcast #7 (due out soon). The software
> market is a great example of "The Market for Lemons" as described by George
> Akerlof. There's nothing Communist about trying to fix a market failure.
>
> It's also not Communist for companies to work together to build a market. It
> might be an antitrust violation, but that's almost the opposite of
> Communism.
>
> OWASP's mission is to "make application security visible" precisely because
> that's that is causing the market failure that results in all the
> ridiculously insecure code out there. That represents a fundamental belief
> in markets and capitalism.
>
> The Communist approach to application security would be to establish a
> centralized authority to dictate how everyone should do things. Now whose
> approach is that?
>
> --Jeff
>
>
> -----Original Message-----
> From: Stephen Craig Evans [mailto:stephencraig.evans at gmail.com]
> Sent: Thursday, February 05, 2009 10:01 PM
> To: jeff.williams at owasp.org; owasp-leaders at lists.owasp.org
> Subject: Re: [Owasp-leaders] Apologies for NY/NJ Email Mistakes
>
> "I appreciate all of your efforts to help OWASP succeed in achieving a
> world where trustworthy software is not the exception."
>
> Well, thanks to Gary McGraw (podcast #5), I'm strongly motivated to be
> the best little Communist that I can possibly be :-)
>
> Stephen
>
> On Thu, Feb 5, 2009 at 3:40 AM, Jeff Williams <jeff.williams at owasp.org>
> wrote:
>> Hi,
>>
>>
>>
>> We have tracked down the problem with the NY/NJ list and we've determined
>> that it was human error. Thanks to Larry Casey (OWASP's Director of IT)
>> along with help from the community in uncovering the root cause. We
>> inadvertently added the NYC conference attendees to the NY/NJ Chapter
> list.
>> We apologize for any inconvenience and confusion this caused.
>>
>>
>>
>> OWASP is 100% committed to running responsible mailing lists, that are
>> opt-in and respect the privacy of list members. I appreciate all the
>> feedback that we got about this issue. We are going to try to restore the
>> list membership if possible. Also, we have added some rules about mailing
>> list management to the OWASP Chapter Handbook to help prevent this from
>> happening in the future.
>>
>>
>>
>> Thank you for your patience with our volunteer organization. I appreciate
>> all of your efforts to help OWASP succeed in achieving a world where
>> trustworthy software is not the exception. As always, please let me know
> if
>> you have ideas about improving the OWASP community.
>>
>>
>>
>> --Jeff
>>
>>
>>
>> Jeff Williams, Chair
>>
>> The OWASP Foundation
>>
>> work: 410-707-1487
>>
>> main: 301-604-4882
>>
>>
>>
>>
>>
>> _______________________________________________
>> OWASP-Leaders mailing list
>> OWASP-Leaders at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>>
>>
>
>
>
More information about the OWASP-Leaders
mailing list