I think the earth contains a significant amount of lead. 
Maybe we should label the earth...

On Mon, 24 Sep 2018 17:11:38 +0000, Stadem, Richard D <[log in to unmask]> wrote:

>Yes, if you write code that includes the words "lead", "chromium", "BPA", "bromines" or "Bromidated", etc, you need to label the software with a warning that the software may contain these words and could scare the living crap out of the Californians.
>
>-----Original Message-----
>From: TechNet [mailto:[log in to unmask]] On Behalf Of Robert Kondner
>Sent: Monday, September 24, 2018 11:08 AM
>To: [log in to unmask]
>Subject: Re: [TN] Prop 65 and RoHS compliance
>
>Wow,
>
>  Glad that I do more software now days.
>
>Does the Great State of California have a label requirement for software? 
>
>Bob K.
>
>-----Original Message-----
>From: TechNet <[log in to unmask]> On Behalf Of Blair Hogg
>Sent: Monday, September 24, 2018 11:42 AM
>To: [log in to unmask]
>Subject: [TN] Prop 65 and RoHS compliance
>
>Hello Technetters,
>
>Since now anybody and everybody can be sued in Cali if you don't put a label of some kind on your products, We've been labeling just about everything. I'm sure you all are doing the same, and maybe have been for some time. 
>
>From what I understand, the label has to state the bad stuff that the product contains - lead, chromium, BPA etc. 
>
>I've been told that even an RoHS compliant product should be labeled for lead as there is enough lead in the copper used to make the board that it will need the label. Any thoughts on this? I'm aware that there can be lead internal to the components in the assembly and still be RoHS compliant, which would require a label, but without researching every component, there is no way to determine this. If the copper in the PCB does contain lead, I don't need to check the components. 
>
>Thanks all,
>Blair