Dear all,
Our next Council meeting is scheduled for Tuesday, 14 January (09:00 EST, 14:00 GMT, 15:00 CET). Elisa said that she cannot make it that day and asked to move it to either Thursday, 16 Jan or Tuesday, 21 Jan. Since we already agreed to move the January Stylesheets meeting to Tuesday, 21 January, I would ask all of you to check if you are available on Thursday, 16 Jan at 09:00 EST, 14:00 GMT, 15:00 CET. Otherwise I would suggest to allocate the first 20-30 minutes of the Stylesheets meeting on 21 Jan to talking about the upcoming release with Elisa.
Best,
Martina
Von: Tei-council Im Auftrag von Elisa Beshero-Bondar
Gesendet: Donnerstag, 2. Januar 2020 20:28
An: Bauman, Syd
Cc: tei-council@lists.tei-c.org
Betreff: Re: [Tei-council] meetings and containers (was "Re: Stylesheets (and other) meeting time")
PS: Correction: If we hold the TEI Council meeting on that *day* of Tuesday 1/14, I won't be able to make it. (But I can attend on Thursday that week or the following Tuesday.)
Thanks,
Elisa
On Thu, Jan 2, 2020 at 2:25 PM Elisa Beshero-Bondar mailto:ebb8@pitt.edu> wrote:
Syd--thanks for looking ahead at calendars about meetings! I need to tell everyone in confidence that I am doing an all-day campus job interview on Tuesday 1/14, so if we are holding the TEI Council meeting that week, I may not (meaning, almost certainly cannot) attend. Since Raff and I are release techs on the next release, and since I've been doing a lot of revisions in the past month to documentation that I want to ask the group about, I really don't want to miss this particular meeting! Can we move the meeting possibly to Thursday just that week (1/16), or by one week later, to Tuesday 1/21?
Thanks all!
Elisa
On Thu, Jan 2, 2020 at 2:10 PM Bauman, Syd mailto:s.bauman@northeastern.edu> wrote:
[Originally sent Mon, 23 Dec 2019 09:51:27 -0500, but bounced due to
a networking problem here with my Northeastern machine. You may
notice that this is not a true reply, just a new e-mail with a subject line
that looks like it is a reply. Sigh.
Note that I will likely have trouble sending e-mail for some time to come.]
So, it sounds like we should move the January Stylesheets group
meeting to Tue 21 Jan 20 at 14:00Z. That is:
06:00 PST
09:00 EST
14:00 GMT
15:00 CET
(Do we have any other time zones represented on Council?)
Unless I hear strenuous objections pretty soon, we will plan on
that.
I am likely to miss the Council meeting of Tue 14 Jan 20 14:00Z. (I
will be traveling in London; depending on train schedules, my family,
etc., I may be able to make it, but I am not counting on it.)
Whether I make it or not, I hope the topic of keeping the Docker
containers updated is discussed. My thoughts on this topic follow, in
no particular order.
* It is definitely important to keep the OS running in a Docker
container up to date with security patches. It may not be as
big a problem as Martin worries it is, especially if we are all
vigilant in leaving a container running for the minimum amount of
time necessary. But it is still important enough that we should
have a process for doing it.
* The solution is probably administrative, not technical.
* It is probably unfair to insist that Peter and Hugh be solely
responsible for doing this. (That said, if they don't object, I
don't either. I would if it were only 1 person -- at least 2
people should know how to do everything that is even
semi-important.) Could be a rotating responsibility.
* My suggested administrative idea: Once a month, 1-24 hours
*before* the Council meeting, the Docker maintainer or designee
should update each container with the latest OS security patches.
(Chair should send a reminder 48 hours before the meeting.)
Immediately *after* the Council meeting each Council member should
download and install the updated container.
* Peter pointed out that doing such an update might break the build
within the container. He's right, but that's no reason not to
install security patches. It's a reason to fix the build process
so it works on a properly updated system. Doing this on meeting
day, I figure, gives us a higher chance of noticing a build fail,
finding a fix, and promulgating the solution rapidly.
_______________________________________________
Tei-council mailing list
Tei-council@lists.tei-c.orgmailto:Tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council
--
Elisa Beshero-Bondar, PhD
Director, Center for the Digital Text | Associate Professor of English
University of Pittsburgh at Greensburg | Humanities Division
150 Finoli Drive
Greensburg, PA 15601 USA
E-mail: ebb8@pitt.edumailto:ebb8@pitt.edu
Development site: http://newtfire.orghttp://newtfire.org/
--
Elisa Beshero-Bondar, PhD
Director, Center for the Digital Text | Associate Professor of English
University of Pittsburgh at Greensburg | Humanities Division
150 Finoli Drive
Greensburg, PA 15601 USA
E-mail: ebb8@pitt.edumailto:ebb8@pitt.edu
Development site: http://newtfire.orghttp://newtfire.org/
