[Secretariat] Re: [CESG] Joining CCSDS Mailing Lists vs. Code of conduct

[Kearney, Mike W. (MSFC-EO01)]

We routinely tell external folks (observer agencies, etc.) that they can participate and contribute without joining the meeting.  Restricting someone from electronically participating unless they attend a meeting is really not a good idea.  Besides, the CMC has encouraged the CESG/WG Chairs to do more work between meetings and have less dependence on meetings.   This suggestion takes the opposite approach.

We ask attendees to sign up to the code of conduct whenever they get a CWE ID and whenever they register for a meeting.  I think also requiring it to also read and sign the code of conduct before being admitted to a mail list is hitting them over the head with it a bit too much.  Anyone that signs up for a mail list will also sign up for a CWE ID (profile) so I think that is adequate assurance of their compliance with the code of conduct.

   -=- Mike

Mike Kearney
Lead Technology Manager
Mission Operations Laboratory
NASA MSFC EO-01
+1-256-544-2029

"Good ideas are not adopted automatically. They must be driven into practice with courageous impatience."
                                         - ADM Hyman G. Rickover

From: secretariat-bounces at mailman.ccsds.org [mailto:secretariat-bounces at mailman.ccsds.org] On Behalf Of Shames, Peter M (313B)
Sent: Wednesday, July 31, 2013 10:08 AM
To: Gian.Paolo.Calzolari at esa.int; CESG -- CCSDS-Engineering Steering Group
Subject: [Secretariat] Re: [CESG] Joining CCSDS Mailing Lists vs. Code of conduct

Hi Gippo,

Interesting point, but I worry that requiring meeting attendance first may have the effect of stifling particpation.    After all, how better to learn if you are really interested (in between meetings) than by looking at the work plans, charters, presentations and docment drafts that are only accessible in the CWE?

For SEA I tend to ask for background, interests, and agency endorsements for any newcomers, especially those who are not part of a member agency.  I think we could easily solve the "Code of Conduct" problem by having the Secretariat send out a copy of that every time they add a new user access (by the current way).

Regards, Peter





From: Gian Paolo Calzolari <Gian.Paolo.Calzolari at esa.int<mailto:Gian.Paolo.Calzolari at esa.int>>
Date: Wednesday, July 31, 2013 6:51 AM
To: CCSDS Engineering Steering Group - CESG Exec <cesg at mailman.ccsds.org<mailto:cesg at mailman.ccsds.org>>
Subject: [CESG] Joining CCSDS Mailing Lists vs. Code of conduct

Dear All,
        recently we had a request for joining a mailing list by a person that did not participated to past meeting of that group.
In this sphere, I had some discussion with Gilles and we agreed that it may be good to agree about a common approach.

Nowadays each mailing list owner can approve a new subscription request based on individual criteria (e.g. ask reason for interest, ask endorsement by an agency, etc).
However, after the recent discussions for the "Code of conduct" it looks that it may be better to allow subscribing to mailing list only to persons that have attended a meeting (i.e. have accepted the CCSDS Code of conduct).
In this way this could also be a valid condition for getting CWE login (i.e. access to CWE private).

What do you think about it?

Nestor, up to yopu to see whether this should be in the agenda for the mid term telecon or for San Antonio.

Regards

Gian Paolo & Gilles


This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender.



Please consider the environment before printing this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/cesg/attachments/20130731/5cc1d859/attachment.html