[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fixed: Automatic notifications for Kavi Group ballots [was: Automaticnotifications for Kavi Group ballots are not working]
On 2-June-2011 we reported on a new anomaly in processing of TC/Subcommittee/MemberSection Ballots using the Kavi system: email notifications typically sent to eligible voters were not being distributed. The cause of the problem has been identified, and fixed at least for the time being (errant lock file). Should anyone observe a recurring problem, or any problem relating to Kavi ballot management, please let us know immediately. Reminder to TC Chairs and others who may create a TC ballot using the Kavi tool: the application does not send out a notification to the TC discussion list when a TC ballot is opened. Only eligible voters are notified. Or rather: only persons **reckoned as eligible** are notified. This sometimes creates surprise and frustration on the part of TC members not notified, as they may be unaware of a ballot in progress, where they feel (belatedly) that they should have been deemed eligible to vote. Best practice may be for the TC Chair or other ballot creator to send email notice to the entire TC list (subscribers) so as to keep everyone informed about a new TC ballot creation. In particular, this message to the list will provide opportunity for any TC member to ask for assistance if she/he believes voting eligibility has not been determined properly. Cheers, - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/who/staff.php#cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, 2 Jun 2011, Robin Cover wrote: > Chairs/Editors/Secretaries/Members > > OASIS Staff has been alerted to a new anomaly in > processing of TC/SC/MemberSection Ballots using the > Kavi system: email notifications typically sent by the > system to Group members (eligible voters in a poll > or ballot) are not being distributed as expected > to the voters. The problem is being investigated, > and we will let you know when it's fixed. > > Meantime, the workaround is relatively simple, but > it depends upon your participation. Whoever creates > a ballot should send an appropriate notice to the > Group (TC, Subcommittee, Member Section) mailing > list to notify Group participants of the ballot > details, and especially, the ballot URIs. The email > notice should include the public-access URI reference > as well as the password-protected URI, as required > by OASIS rules for visibility [1]. > > Example URIs: > > public: http://www.oasis-open.org/committees/ballot.php?id=2053 > password: > http://www.oasis-open.org/apps/org/workgroup/kmip/ballot.php?id=2053 > > Please feel free to contact me and/or the TC Admin > team with any questions. > > - tc-admin@oasis-open.org > - robin@oasis-open.org > > Cheers, > > - Robin > > > Robin Cover > OASIS, Director of Information Services > Editor, Cover Pages and XML Daily Newslink > Email: robin@oasis-open.org > Staff bio: http://www.oasis-open.org/who/staff.php#cover > Cover Pages: http://xml.coverpages.org/ > Newsletter: http://xml.coverpages.org/newsletterArchive.html > Tel: +1 972-296-1783 > > ============ References: > > [1] Publicly Accessible URIs > http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#accessibleURIs > > Visibility > http://www.oasis-open.org/committees/process-2010-07-28.php#visibility > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]