OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tac message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [tac] Conference Call Frequency [EXT]


Oh and maybe people that lose their voting rights and do as I say above must also "ask" to get them back. Not that it would be denied. But they show a commitmentÂto wanting to vote.Â

Thanks,
Bret
PGP Fingerprint:Â63B4 FC53 680A 6B7D 1447 ÂF2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."


On Wed, Nov 25, 2020 at 3:10 PM Bret Jordan <bret.jordan@broadcom.com> wrote:
Chet,

This is the general issue with voting and obtaining consensus. Depending on the makeup of the TC, you can get into situations where you have members from all over the planet. If the meetings are too infrequent, then it becomes hard for people to regain lost voting rights and hard to get anything done. If you have a monthly meeting that counts for voting rights with weekly design meetings then your monthly meetings become basically briefings with high level concept discussions. This also tends to give you a lot of voters that are not activelyÂinvolved day-2-day, and who may not vote on ballots. If you have weekly or biweekly meetings that count for voting rights, then you naturally limit the voting rights down to basically the design teams or mini-groups of the TC, those individuals that are highly involved and can contribute significant amounts of time. This last option allows a TC to vote and pass concepts quickly and easily, because the design team is generally all in agreement. However, this does not mean there is broad consensus.ÂÂ

SDOs and SSOs have struggled with this forever. Where is the balance and how do you gauge involvement and address objections from consensus if someone is not able to participate every week?

If ballots on work products or elements of work products were more frequent in a TC than that might be the best indicator of involvement and engagement. Then if an individual is willing to voice a yes or no response then there is a level of engagement. If they choose not to vote then they would lose their ability to vote in the next ballot. The problem we are actually trying to solve is making sure that the TC members that are engaged at some level can voice their opinions through a vote. However, if they are not engaged and unwilling to vote, then they should not be able to hold the TC hostage.

Another option is to just give everyone voting rights but get rid of the notions of Full Majority and Super MajorityÂof the entire voting population and make them Full Majority and Super MajorityÂof the votes cast. This way if people do not vote they cannot hold the TC hostage.Â

If it was up to me, I would do the following:
1) All new members of a TC obtain voting rights automatically after they have been a member of the TC for more than a month.

2) A TC member that has lost voting rights can obtain voting rights again by attending any 2 meetings within a 2 month period. The only requirement is meetings must be published via Kavi and must be posted 7 days in advance. But there is no longer meetings that count and do not count forÂvoting rights. A TC meeting becomes a TC meeting. A TC member can also gain voting rights by contributing a new draft document, a proposal for a new work product, comments and suggestions on a work product, etc. Basically, if you are going to participate you can get voting rights. But if you are just going to come and listen and observe, you must attend 2 meetings within a 2 month window.

3) The only way for a TC member to lose voting right is by not voting. If they do not vote on a ballot, then when the ballot closes, they lose their voting rights.ÂÂ

This would tend to work well if ballots become more frequent and easier to open and process.Â

Thanks,
Bret
PGP Fingerprint:Â63B4 FC53 680A 6B7D 1447 ÂF2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."


On Wed, Nov 25, 2020 at 1:40 PM Chet Ensign <chet.ensign@oasis-open.org> wrote:
Hi Patrick,Â

I think sharing recordings of meetings is an experiment worth trying out.Â

The issue of what conditions control voting rights is one that we wrestle with periodically in the Board Process Committee. So far, no one has felt that we'd come up with any better way than meeting attendance. I'm not sure how to address that in this situation.Â

/chet

On Wed, Nov 25, 2020 at 12:38 PM MARONEY, PATRICK <rx118r@att.com> wrote:
Jane, et al,

I think some kind of accommodation for meetings in general, and those that count for voting rights in particular would be a much needed improvement to our processes.

Difficulties supporting meetings go beyond just time-zone differences. I often have conflicts with mandatory work meetings that conflict with OASIS meeting schedules.

Recording the meetings and using ballots to record votes for decisions would seem to be a reasonable accommodation.

I don't to what extent we can meet OASIS Open policies/procedures and virtualize the meetings that count toward voting eligibility, as well as those that discuss key topics (I've had to miss very many of these). We'll have to hear from OASIS on this, but I would really like to find a way to extend our inclusiveness and opportunities to participate substantively.

Patrick Maroney
Principal - Cybersecurity
Chief Security Office
c 609.678.5613 |Ârx118r@att.com

-----Original Message-----
From: tac@lists.oasis-open.org <tac@lists.oasis-open.org> On Behalf Of JG
Sent: Wednesday, November 25, 2020 12:14 PM
To: Thompson, Dean <Dean.Thompson@anz.com>; tac@lists.oasis-open.org
Subject: Re: [tac] Conference Call Frequency [EXT]

Dean:

This is a really good point... and, one that we've struggled with in the CTI TC. We solved that problem by holding the two sessions for the CTI TC Monthly Calls. The TAC TC is a smaller community; therefore it might be difficult to justify such a schedule.

Would a recording of Working sessions or Monthly calls be helpful for you? I'm just wondering how we can make the real-time dialogue more accessible to our TC members in Europe and Asia/Pacific.  I can't really capture all of the nuances of the discussions in the written Meeting Notes. If we record sessions you could listen at a time that would be convenient to you, then comment on the list.

We would have to work out a different strategy for enhancing cross-timezone/cross-region engagement during official actions. I'm thinking the Ballot process has proven to be the best for that. What do you think?

Jane Ginn


On 11/24/2020 5:07 PM, Thompson, Dean wrote:
> Hi!,
>
> If the intention is to make this count towards voting rights then I think we need to be respectful of the timezones that everyone is residing in. For example, every TAC Monthly call that happens is approx. 2am to 3am local time for myself based in Australia. In some cases I have been able to make it and sometimes fallen asleep waiting for it to start. I get that the meeting time is dictated by the majority (of which I am in the minority based on my geo location), but if we want to start put working calls into the mix and we want to incorporate voting rights, then I think the timing of the meetings also need to be looked at.
>
> Regards,
>
> Dean
>
> -----Original Message-----
> From: tac@lists.oasis-open.org [mailto:tac@lists.oasis-open.org] On
> Behalf Of Ms. Jane Ginn
> Sent: Wednesday, November 25, 2020 8:52 AM
> To: tac@lists.oasis-open.org
> Subject: [tac] Conference Call Frequency [EXT]
>
> TAC TC Members:
>
> During our last monthly call a suggestion was made to increase the frequency of our Working Calls to two times a month, along with our regular Monthly Call (held on the third Tuesday).
>
> Another option was considered to increase our Working Calls to every two weeks, and have them all count towards Voting Rights. A comment was made that it would be easier for people to schedule if we made it two times a month on specified times/days with each call counting towards Voting Rights.
>
> We made a decision to reach out to the broader community for input on this matter. I've put together a Doodle Poll to try to gauge the preferences of the full membership. The link is below. Please respond by December 12th so we can make a decision at our next full TC call on December 15th.
>
> https://urldefense.com/v3/__https://doodle.com/poll/z8y37qu9zmi88hwv?u
> tm_source=poll&utm_medium=link__;!!BhdT!xE7YUv9n2N3btzYC_pR87qsmgoiFYy
> bc-MWLNJfFPM1AtsfnfBJVGmkY9BwF8tNGwg$
>
> Best wishes for the holidays!
>
> Jane Ginn, Secretary
> OASIS, TAC TC
> jg@ctin.us
> "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ Bank New Zealand Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."

--
*****************************
Jane Ginn, MSIA, MRP
Secretary, OASIS CTI TC
Sponsor, TAC TC
Sponsor, BP TC
jg@ctin.us
001 (928) 399-0509
*****************************


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://urldefense.com/v3/__https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php__;!!BhdT!xE7YUv9n2N3btzYC_pR87qsmgoiFYybc-MWLNJfFPM1AtsfnfBJVGmkY9BySAc_x4w$Â



--

ChetÂEnsign

Chief Technical Community Steward

OASIS Open

ÂÂÂ
+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]