Thanks Robin and Chet. I will take a look at this approach and see if it might work for us. I will report back to you in case you want to use our experience as a (hopefully) success story for other TCs to try should they find themselves in a similar boat. From:
xliff@lists.oasis-open.org [mailto:
xliff@lists.oasis-open.org] On Behalf Of Robin Cover Sent: Tuesday, October 15, 2013 11:25 AM To: Schnabel, Bryan S Cc:
xliff@lists.oasis-open.org; Robin Cover; Chet Ensign Subject: Re: [xliff] Re: Asking David to send private meeting notice Re: On Tue, Oct 15, 2013 at 12:48 PM, Chet Ensign <
chet.ensign@oasis-open.org > wrote: Bryan, Robin Cover reminded me of another, possibly more convenient, solution. You can create an Action Item in the TC's Kavi group and make that action item private - only visible to TC members who log on to the OASIS site and go to the action item. That way, the dial-in info is persistent and you don't need to keep a mailing list up to date over time. Best, /chet Bryan, I don't know that use of an action item has been tested for a TC, but as far as I know, the solution could work to make the meeting information OASIS-Member-Only visible (only users with a Kavi account can see AIs). You could call it a "commandeered action item" -- which is clunky but may work and may be preferable to hand-maintenance of a BCC: notification list just for the current TC members. CAVEATS: You need to be sure that you do not send a notification about the AI to the TC (Kavi group). If you do that, the information will (IIRC) be sent to the TC's mailing list archive, and become world-read [that's not what you would want]... When you create the AI, you should assign it to yourself. Then, before creating the AI, observe in the interface this section: Email Notifications: Notify Group or Owner ** UNcheck or leave UNchecked : - Notify the Action Item owner - Notify the group chair(s) - Notify the group about this action item I think the latter two are unchecked by default, but as a discipline I would recommend UNchecking all three in their checkboxes. In particular: make sure "Notify the group about this action item" is NOT checked. Similarly: when you modify the AI to eg., update the meeting access code(s), be sure not to "Notify the group". I attach an image file showing a bogus example of the text you can create for such a commandeered action item; you can include any truly private information, but please don't use the AI to hide information that should be visible to the public: only the contact and access information should be included. File: TC-ActionItem-MemberOnlyInfo.png (example only) Let us know if you test that workaround (clunky as it is)... - Robin Cover On Tue, Oct 15, 2013 at 12:08 PM, Chet Ensign <
chet.ensign@oasis-open.org > wrote: Bryan, sorry that this happened to you. It has happened to a few other TCs and seems to be the hi jinx du jour for people with nothing better to do. The only reliable solution that we have found is to send around the call in information privately. Some member companies apparently have conference calling systems that allow you to keep people in a lobby until the meeting organizer confirms their identity and adds them onto the call. However, most TCs don't have that at their disposal and we don't have a facility like that to offer. Again, sorry that you got hit by the pranksters. Best, /chet On Tue, Oct 15, 2013 at 11:15 AM, Schnabel, Bryan S <
bryan.s.schnabel@tektronix.com > wrote: We seem to be victims of pranksters. This happened to the DITA tc as well. David, please send meeting notices for today privately to members. I will get with Chet to see how we can resolve this -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Check your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen Twitter:
http://twitter.com/OASISopen Facebook:
http://facebook.com/oasis.open -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Check your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen Twitter:
http://twitter.com/OASISopen Facebook:
http://facebook.com/oasis.open -- 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/people/staff/robin-cover Cover Pages:
http://xml.coverpages.org/ Newsletter:
http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783