The number of votes required is determined at the time the ballot is created (since the number of organizational members changes from month-to-month.) Or, you could always check the ballot notice for the ballot that's currently out for vote in tc-announce archives ;)
On Sep 24, 2010, at 8:04 AM, Barnhill, William [USA] wrote:
Thanks
Will. That's very good to know. I've sent to Mary so that if 51 is not
the number of YES votes that we need then she can
correct.
John's right I
think..we ned to get the big guys in early. John, do you know someone who
might be willing to approach Tony or someone who knows the MS voting member?
-Bill
By my count, there are 334 OASIS members listed between the pages:
We need 15% "yes" votes, which would be 51. Though I'm not 100% sure
if I'm counting the OASIS Organizational members correctly.
-will
On Thu, Sep 23, 2010 at 1:05 PM, John Bradley <jbradley@mac.com>
wrote:
It would be a good idea to line up the
required yes votes.
The problem will be if there are no votes, it doesn't take many to kill
it.
I doubt there will be any organized opposition this time.
Getting some of the big guys in early will be important.
MS will probably abstain because of their policy of not voting on specs
that they are not participating in. We can ask Tony if they will make an
exception though he is not the voting member.
John B.
On 2010-09-23, at 3:58 PM, Barnhill, William [USA] wrote:
What
does everyone think of an organized voting/socialization campaign for this
vote? By that I mean we...
1)
Collectively determine which reps we know and list them, then determine who
will approach each in a 1-1 manner (face2face, phone,
email)
2) Track
responses we get from 1on1s, including responses on whether they would be
able to do a yes vote in August and detailed feedback on the
spec
3) When
we get some # of votes needed (min + ?) then we submit
4) If
necessary revise and regen a new community draft based on
comments
You know
me..I can't resist saying that an OASIS Tool to do the above would be very
nice..maybe vote.oasis-open.org (and wrap voting on specs in their as
well). I know there's not enough cycles, but food for
thought.
In theory, yes, I _think_ we have time to request an OASIS
Standard vote before July 15. However, that would place the actual vote in
August. And the actual voting itself always takes place the last two weeks
of the month. So a very real question is: do we want to try for an
OASIS Standard vote in August, when more than half the members are on
vacation? Or should we wait for September? Mary: the TC could really
use your input on this. Thanks, =Drummond
On Thu, Jul 1, 2010 at 6:51 PM, Will Norris <willnorris@google.com> wrote:
we
now have the required 2/3 'yes' votes for Committee Specification.
Assuming we don't get 4 'no' votes between now and Sunday, the
ballot will pass. So time to start planning for the next steps...
- once the vote is final, i'll generate the new CS version of
the spec, and get that to Mary to be published.
- we need three "statements of use". Mary, do you have a
few examples we can reference for what those should look like? Also,
do they need to come from the Organizational Member's primary contact, or
can it be anyone within the organization?
- do we know that we have three organizations that can provide
Statements of Use? Looking at the TC Process, it appears that they
must come form "Organizational Members", which means Yahoo! will not be
able to count as one of the three. Google certainly can, and I
believe George indicated that AOL would likely be able to. Who will
be the third? Is XDI currently publishing or consuming XRD?
Once this current CS vote is closed and we have the three statements
of use in hand, we must have one final vote to request that XRD be
submitted for an OASIS Standard vote. That must commence before the
15th of the month. If we move quickly, we can do that by July 15th,
otherwise we can do it next month.
(and even though we do have the required votes for CS, I'd like to
have as near a unanimous decision as possible.... please go vote if you
haven't already)
-
will
|