Spam detection software, running on the system "mail.haskell.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: I've posted comments on the Github thread, to try and clarify a few points before I cast my vote. On Thu, 26 Jan 2023 at 03:02, Richard Eisenberg <lists@richarde.dev> wrote: > Spam detection software, running on the system "mail.haskell.org", has > identified this incoming email as possible spam. The original message > has been attached to this so you can view it (if it isn't spam) or label > similar future email. If you have any questions, see > @@CONTACT_ADDRESS@@ for details. > > Content preview: +1 from me, too > On Jan 23, 2023, at 1:27 PM, Chris > Dornan > <chris@chrisdornan.com> wrote: > > +1 to this proposed change to the > nominations > process. > >> On 2023-01-23, at 14:24, Joachim Breitner < > mail@joachim-breitner.de> > wrote: >> >> Hi, >> >> our current by-law kinda bind our hands in case > some > motivated comes >> along and would like to join the committee, and Simon > PJ suggested that >> we should give us the discretion to hold membership

votes > out-of-season >> as well. The suggested wording change is in >> https://github.com/ghc-proposals/ghc-proposals/pull/572 > >> >> Please discuss and cast your vote within two weeks (preferably > earlier, > >> as you can guess this change is not happening completely out of the > >> > blue.)

...

...

...

I’m in favor. >> >> Cheers, >> Joachim >> >> >> -- >> > Joachim > Breitner >> mail@joachim-breitner.de >> http://www.joachim-breitner.de/ >

...

...

> ghc-steering-committee mailing list >> > ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee ghc-steering-committee mailing list > > ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee [...] > > Content analysis details: (5.0 points, 5.0 required) > > pts rule name description > ---- > > -0.0 SPF_HELO_PASS SPF: HELO matches SPF record > 5.0 UNWANTED_LANGUAGE_BODY BODY: Message written in an undesired language > 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid Forwarded message > From: Richard Eisenberg <lists@richarde.dev> [...]

Content analysis details: (5.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 5.0 UNWANTED_LANGUAGE_BODY BODY: Message written in an undesired language 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.