David Reid wrote:
Bernd Fondermann wrote:
Bernd Fondermann wrote:
Fellow researchers,

to actually bring this crypto statement stuff forward I'd like to call
a vote. At first I thought lazy consensus would work, but I am not so
sure anymore (triggered by the comments in the thread starting here
[1]), so a vote is the safe way to go.

We have to report about the use of crypto code in Labs. Following the
instructions at [2], we should apply labs_crypto2.patch attached to
JIRA here [3] to its destination file found here[4].

Please vote:
[] Yes, apply the patch as described and kindly ask the Labs PMC chair
to send out the email as described in [2] afterwards.
[] I don't know, I don't care for this whole crypto stuff really much
[] No, don't apply the patch, there is something wrong with it. (Give
some reason, please)

The vote will not close before 2008-06-30 12:00 GMT.
I am cancelling this vote, it's unlikely any more votes will be cast.
There were no binding votes, so the vote fails.

Don't know what is next...

As has been pointed out, this just needs to be applied.

But applying seems to be a problem here. Nobody did it yet.

The vote really
wasn't needed...

Votes raise more awareness.
And it would have been needed to ratify that I will do it. But now I won't.

The need to submit a crypto report should probably be added to the
requirements for a lab as it's now board mandated and

+0

> each PI should be
contacted by Stefano and asked to submit one.

That has happend looong ago.

Chalk up another one for bureaucracy :-(

Yes, nobody likes to do this, we are forced to do this because of US policy. But this topic could long been resolved if every PI took one minute to complete a well-documented simple process by adding some very very simple XML to an already existing template.

(Or even simpler: run 'svn rm <lab>' and you don't even need to read any annyoing documents.)

Just do it, you will feel better afterwards. :-)

  Bernd


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to