SAP ISO SR26000:20010 - listserv etiquitte was: for any hardware gurus
This subject is mostly for the list maintainers as it is in fact related to the list policy. It can get tiresome to have people send me private emails at the address they have harvested from this list. Social responsibility dictates that I have a process I may follow, albeit a voluntary one. In general if you have sent me a private email: You are not a troll; if you are on the list and I reply in kind without mentioning the word troll. If you are a troll, I told you that. I told you that because, you don't know the first rules of online etiquette. Now I have to address the OP. When you started the conversation off list, you don't respond to my online post off-list again just by putting the word off-list in the subject, we have never met face to face. On a list, if you don't know someone personally, the correct way to take it off-list is to send a post saying lets go off-list as this is not general interest or otherwise private. You are a double troll if we have never interacted and you email me privately, but that was a different person. <snip all the stuff the OP doesn't know about IO streams> I tried to be nice but this is what I finally said to the last troll. <begin_repelling_troll> "I have to remember the first rule of listserve, don't feed the trolls they are ungrateful and bite the hand that feeds them. All the techs who didn't respond, did that because you don't know the basics and they couldn't be bothered. This list is a little different, it has a lot of newbies so I bothered to ask, now I'm sorry I did. You don't know what init process is you don't know what configuration files to look for and are a Windows transplant in the world of GNU software. You are like every other user who has trolled me from this list, poorly regurgitating what someone else has told you without understanding of the basics. You know that, that is why you took it off-list and why I went back to the list after you made me do the homework you don't have a clue about. There are no how-tos for dealing with trolls, but there is a troll spotting guide and I followed it." </begin_repelling_troll> For the list maintainers. I don't know who the OP is or where they are but if they are an employed Tech, self or other, who is trying to work with hardware they don't understand, they should at least know this. In fact everyone who is employed should know this. This is why I included the SAP ISO. Canada is a first signer of this protocol. Clause 7 addresses volunteerism. -- Russell Sent by K-9 Mail
On 2017-07-28 09:50, Russell via talk wrote:
This subject is mostly for the list maintainers as it is in fact related to the list policy.
I'm the list maintainer, :wave:.
It can get tiresome to have people send me private emails at the address they have harvested from this list. Social responsibility dictates that I have a process I may follow, albeit a voluntary one.
In general if you have sent me a private email:
You are not a troll; if you are on the list and I reply in kind without mentioning the word troll.
If you are a troll, I told you that. I told you that because, you don't know the first rules of online etiquette.
I 100% agree. When I reply to an email on a mailing list I except that conversation to stay on the mailing list. But this was most likely done as a mistake as some email clients clicking the reply will only populate the sender's email not the list's email (in those email clients the proper way to reply to the list is clicking the reply-all button). This list was configured that way to satisfy Outlook.com and Yahoo email servers DMARC/DKIM policies, that have been affect most mailing list setup on the Internet. I don't want to get into it more as it's been heavily documented on the mailing list: <https://gtalug.org/pipermail/talk/2016-June/003326.html> <https://gtalug.org/pipermail/talk/2017-March/004659.html>
As someone who, as a member of the Standards Council of Canada was part of the Canadian delegation to the ISO on file formats (fighting to keep them unencumbered, FWIW) I am intrigued at the reference to ISO 26000.
In fact everyone who is employed should know this. This is why I included the SAP ISO. Canada is a first signer of this protocol. Clause 7 addresses volunteerism.
Hmm. ISO 26000 is neither a protocol nor a standard, you can't get certified to be compliant with it <http://www.sustainableplant.com/2011/there-s-no-such-thing-as-iso-26000-certification/>. It is targeted at large organizations, not people or governments. What ISO 26000 *is* is a 100-page document from ISO that will cost you 200 Swiss Francs <https://www.iso.org/standard/42546.html> to purchase the ebook. What it contains are guidelines and best practices for large organizations to tell them what it means to be "socially responsible". I am at a disadvantage in not knowing what Clause 7 includes because I'm not spending more than $250 to read ISO take 100 pages to say "please don't be a corporate dick and treat people with respect". SAP is a German database company, it might be embracing ISO 26000 but it certainly has nothing to do with the general deployment Since there is no standard and no protocol -- just a set of optional recommendations -- I am eager to know more about the level of Canadian government endorsement, and specifically what laws and regulations have been affected. To address the more pertinent issue.... There are plenty of codes of conduct that may be more directly applicable in our context, my current favourite is the Creators Covenant <http://contributor-covenant.org/> that addresses behavior within communities working on open source projects. (Just replace "project maintainers" with "forum adminsitrators".) But please let's not drag the ISO into this, it won't provide the comfort being sought simply because of its extra levels of bureaucracy. It expressly claims no authority, just suggestion. Cheers, Evan
On July 28, 2017 2:29:51 PM EDT, Evan Leibovitch <evan@telly.org> wrote:
As someone who, as a member of the Standards Council of Canada was part of the Canadian delegation to the ISO on file formats (fighting to keep them unencumbered, FWIW) I am intrigued at the reference to ISO 26000.
In fact everyone who is employed should know this. This is why I included the SAP ISO. Canada is a first signer of this protocol. Clause 7 addresses volunteerism.
Hmm. ISO 26000 is neither a protocol nor a standard, you can't get certified to be compliant with it <http://www.sustainableplant.com/2011/there-s-no-such-thing-as-iso-26000-certification/>.
I wasn't indicating certification but understanding.
It is targeted at large organizations, not people or governments.
Ahh ... the advantages of non certification, from a business perspective; you only have to follow the protocol guidance of Social Responsibilities if you want to.
What ISO 26000 *is* is a 100-page document from ISO that will cost you 200 Swiss Francs <https://www.iso.org/standard/42546.html> to purchase the ebook. What it contains are guidelines and best practices for large organizations to tell them what it means to be "socially responsible".
No there is a section for SMB's Small and Medium Business. In addition Clause 7 addresses voulnteerisim. Social Responsibility is everyones business, or not, depending on your point of view.
I am at a disadvantage in not knowing what Clause 7 includes because I'm not spending more than $250 to read ISO take 100 pages to say "please don't be a corporate dick and treat people with respect".
Perhaps you would understand my Clause 7 point better if you look up the open source images and blurbs in google. Although I didn't read anything about dicks, corporate or other. :-) Or I could, as fair use policy for this volunteer initiative, say "following the guidance of SR26000 I will print out a copy of my 2010 draft copy". The people who gave it to me won't mind if I share it, thats what they sent it to me for.
SAP is a German database company, it might be embracing ISO 26000 but it certainly has nothing to do with the general deployment
SAP is an acronym which I learned as an element of First Order Reliability Methods. Standardly Applied Protocols, as intrepreted under ISO standards, has nothing to do with a german database company who have co opted the otherwise military acronym.
Since there is no standard and no protocol -- just a set of optional recommendations -- I am eager to know more about the level of Canadian government endorsement, and specifically what laws and regulations have been affected.
Well Canada proselytized its endorsement and signed the declarations in 2010. Remember this is a collection of descriptor/protocols used for creating understanding of what was designated CSR but has been expanded to include NGO's and other organization and groups of volunteers.
To address the more pertinent issue....
There are plenty of codes of conduct that may be more directly applicable in our context, my current favourite is the Creators Covenant <http://contributor-covenant.org/> that addresses behavior within communities working on open source projects. (Just replace "project maintainers" with "forum adminsitrators".)
But please let's not drag the ISO into this, it won't provide the comfort being sought simply because of its extra levels of bureaucracy. It expressly claims no authority, just suggestion.
All ISO documents are made as suggestions, thats why they are initialised as RFC. There is no enforcement mechanisim, only adoption or rejection of the principles by any given group.
Cheers, Evan
-- Russell Sent by K-9 Mail
In the interest of remaing clear on the policy and protocol issues I am attempting to address, I am top posting the Clause 7 outline. 7 Guidance on integrating social responsibility throughout an organization .................................69 7.1 General..................................................................................................................................................69 7.2 The relationship of an organization's characteristics to social responsibility .............................69 7.3 Understanding the social responsibility of an organization...........................................................70 7.4 Practices for integrating social responsibility throughout an organization .................................74 7.5 Communication on social responsibility ..........................................................................................76 7.6 Enhancing credibility regarding social responsibility.....................................................................78 7.7 Reviewing and improving an organization's actions and practices related to social responsibility .......................................................................................................................................80 7.8 Voluntary initiatives for social responsibility...................................................................................82 On July 28, 2017 4:04:19 PM EDT, Russell <rreiter91@gmail.com> wrote:
On July 28, 2017 2:29:51 PM EDT, Evan Leibovitch <evan@telly.org> wrote:
As someone who, as a member of the Standards Council of Canada was part of the Canadian delegation to the ISO on file formats (fighting to keep them unencumbered, FWIW) I am intrigued at the reference to ISO 26000. <snip the tail> -- Russell
participants (4)
-
Evan Leibovitch -
Myles Braithwaite 👾 -
Russ -
Russell