[zeromq-dev] #zeromq meetup on Sun 23 Feb -- Curve security

[Drew Crawford]

> many corporations are designed to respond to false
> emergencies created by clients/managers/executives within hours or
> days. 

We may be drifting off-topic for this list, but just because two people have a different perspective on the severity of an issue doesn’t mean that one of them is “creating” a “false emergency”.  Software exists to serve the needs of people, and if those people are unsatisfied with the software there is no way to tell them that they are wrong to be dissatisfied.  You can tell them that nothing will be done for them and they must handle their own emergency, but whether or not some issue is an emergency is an opinion, not a fact claim, and there is no basis on which you could call it “false”.

With respect to #802, several individuals including myself have volunteered to land the feature in the patch queue.  I don’t want to minimize the help I/we would need from libzmq core, but there is a willingness here for the affected users to shoulder their own burden and put out their own fire.  I don’t think unreasonable demands are being made to the core team.

In addition, several affected users, including myself, have already landed, tested, and shipped this feature downstream of us, so strictly speaking, there is no fire.  The issue at this point is mostly how to get some solution into core where more people can benefit, and eliminate some of the incompatible implementation chaos downstream.

> I'm legally
> bound to my company until Feb 2015 before which severance is a severe
> damage to my life. 


Sounds like you learned an important lesson here.


On Feb 21, 2014, at 11:05 PM, crocket <crockabiscuit at gmail.com> wrote:

> It's normal to see an issue stall for months or years. I just wanted
> to point out that many corporations are designed to respond to false
> emergencies created by clients/managers/executives within hours or
> days. The vast majority of the global population are haunted by false
> scarcity at workplace in which people believe either they don't have
> enough time or they have to solve the issue immediately.
> 
> Actually, most issues don't require immediate attention most of time.
> 
> On Fri, Feb 21, 2014 at 10:36 PM, Drew Crawford <drew at sealedabstract.com> wrote:
>> I'm not sure I understand your question, crocket.  Are you asking why this
>> issue has stalled for so long?  Or are you asking how to do things at your
>> day job so that they stall at least as long as this #802?  ;-)
>> 
>> 
>> On Feb 21, 2014, at 7:01 AM, crocket <crockabiscuit at gmail.com> wrote:
>> 
>> terms -> in terms
>> 
>> On Feb 21, 2014 10:00 PM, "crocket" <crockabiscuit at gmail.com> wrote:
>>> 
>>> I read the issue briefly. I also am interested in 0mq security for my own
>>> purpose.
>>> 
>>> Unfortunately, I won't be able to join you guys because 10pm CET is 6am
>>> UTC+9 at which time I have to prepare for 2 hours long commute.
>>> 
>>> By the way, the issue has been going on for months. 0mq community policies
>>> are more like a social technology than a business model, but I want to
>>> address this community terms of business. A typical corporate
>>> manager/executive wouldn't be patient enough to wait for indefinite amount
>>> of time for an issue. That's why they prefer to make us suffer long commute
>>> and interrupt us in offices. How do I best apply the wisdom of crowd to my
>>> current company or my job?
>>> 
>>> On Feb 21, 2014 7:40 PM, "Pieter Hintjens" <ph at imatix.com> wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> Per issue #802, we're organizing an IRC meetup to discuss how to
>>>> improve Curve authentication in libzmq.
>>>> 
>>>> See https://github.com/zeromq/libzmq/issues/802
>>>> 
>>>> We're proposing this Sunday at 3PM CST / 10pm CET, on the #zeromq IRC
>>>> channel.
>>>> 
>>>> The meetup should last an hour or so. I volunteer as moderator; the
>>>> goal will be to focus the discussion on issue #802 first, other stuff
>>>> later.
>>>> 
>>>> -Pieter
>>>> _______________________________________________
>>>> zeromq-dev mailing list
>>>> zeromq-dev at lists.zeromq.org
>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> 
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> 
>> 
>> 
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20140221/55f5b0e9/attachment.htm>