CF-aficionados,
I subscribed to this list awhile ago and read the occasional emails that
relate to the standards.? I can definitely appreciate the passion in
this community!
However, I don't think forwarding all GitHub issue traffic to a mailing
list is a good idea, especially when by accident if someone can respond
to such a notification by email, cc the GitHub-subscribed list in their
email and thereby trick GitHub into assuming the list itself had
responded, rather than the list subscriber (who presumably does not have
a GitHub account or was replying with an email address GitHub didn't
recognize).
This was suggested already, but to reiterate: whoever knows the
'cf-metadata-list' GitHub account password, just log in and check the
'unsubscribe' button on this issue and spare us the spam.
Or, if the list GitHub account owner isn't out there - or on vacation
perhaps - a second option is just to take mercy on us all and close this
particular issue, move on to a new, fresh and clean calendar issue to
debate this topic, and refer back to the original trouble issue for
context (just a simple cf-conventions#148 string in the new issue will
do the trick). This way, all your discussion isn't lost, and hopefully
the 'cf-metadata-list' GitHub account problem can be sorted out in good
time without all these emails for us all to delete...
This reminds me of a really fun chain email incident we had at NOAA
recently (others here may recall), where a never-ending chain started of
'please unsubscribe me from this list' reply-all emails to a particular
email alias to which a good part of the agency is auto-subscribed, each
new email just prolonging the spam for everyone else.? I missed out on
replying-all to join in that fun, but not this time!? So.... please
unsubscribe me!!
Sincerely,
Micah
On 11/8/18 4:20 PM, Mcgibbney, Lewis J (398M) wrote:
>
> Hello Folks,
>
> I refrained from commenting on this thread for a day or two now with
> the hope that someone would sort our the cross-posting issue. As it
> has not been sorted out, I wanted to share some of the actions I?ve
> undertaken in an effort to mute the thread on my side?
>
> * I unsubscribed from the listserv
> * I tried to mute the thread on Github, which I was unable to do
> because my JPL email address has never been associated with a
> Github thread.
> * I unfollowed the repository with my personal email address and set
> notifications to off.
> * ? I was still getting notifications after the above actions, so
> I?ve resorted to trashing every message which matches
> ?cf-convention/cf-conventions? in title.
>
> This is a shame as I did for a while monitor what was going on within
> this community.
>
> Someone, somewhere has switched something to cross post every event to
> the mailing list, which is not a good thing to do unless people like
> that kind of traffic. As you can see from the sentiment which has been
> posted here, people get rather annoyed pretty quickly.
>
> I?ll maybe try joining again the mailing list in the future and see if
> this has been sorted out however until then keep up the good work on
> CF-Conventions folks.
>
> Lewis
>
> Dr. Lewis John McGibbney Ph.D.,?B.Sc.
>
> Data Scientist II
>
> Computer Science for Data Intensive Applications Group (398M)
>
> Instrument Software and Science Data Systems Section (398)
>
> Jet Propulsion Laboratory
>
> California Institute of Technology
>
> 4800 Oak Grove Drive
>
> Pasadena, California 91109-8099
>
> Mail Stop : 158-256C
>
> Tel: ?(+1) (818)-393-7402
>
> Cell: (+1) (626)-487-3476
>
> Fax: ?(+1) (818)-393-1190
>
> Email: lewis.j.mcgibbney at jpl.nasa.gov
> <mailto:lewis.j.mcgibbney at jpl.nasa.gov>
>
> ORCID: orcid.org/0000-0003-2185-928X
>
> signature_1695220620
>
> ?Dare Mighty Things
>
> *From: *<owner-cf-metadata at listserv.llnl.gov> on behalf of Chris
> Barker <notifications at github.com>
> *Reply-To: *cf-convention/cf-conventions
> <reply+01f236817c81e46a1168d208892316e4b22795fa89fc3c6192cf0000000117fc688c92a169ce1651dc7b at reply.github.com>
> *Date: *Thursday, November 8, 2018 at 1:12 PM
> *To: *cf-convention/cf-conventions <cf-conventions at noreply.github.com>
> *Cc: *CF Conventions mailing list <cf-metadata at listserv.llnl.gov>,
> Comment <comment at noreply.github.com>
> *Subject: *Re: [cf-convention/cf-conventions] Add calendars
> gregorian_tai and gregorian_utc (#148)
>
> The CF calendar attribute specifies the calendar for the reference
> timestamp and other timestamps, and the rules for converting
> between timestamps and time coordinates. This seems convenient and
> clear to me. We just need to add the new ones for (proper) UTC,
> TAI and GPS, I think.
>
> and a new one for this use case -- the current "gregorian" is NOT the
> same thing. It often (maybe mostly) is, but it is actually ambiguous
> with regard to leap seconds, and we need to keep that.
>
> Also, once we have the new "calendars", it should not be used for this
> use case, and should only be used with "metrical" values :-)
>
> ?
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/cf-convention/cf-conventions/issues/148#issuecomment-437157449>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AfI2gQ1dqKsSMK00-mBqu5icgSIhFrBXks5utJ4MgaJpZM4X8l6W>.https://github.com/notifications/beacon/AfI2gS1oHRAMrCN4SIyKICQYLDAJYXBBks5utJ4MgaJpZM4X8l6W.gif
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20181108/31c225ff/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3430 bytes
Desc: not available
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20181108/31c225ff/attachment-0001.png>
Received on Thu Nov 08 2018 - 19:06:27 GMT
