OK, so you're all, well, hello. Bonjour. Connichiwa. Good evening. Buenos dias. Daniel, nice to meet you. Ni hao. I can't really speak American, but I didn't consider doing it. I'll talk in a really bad American accent, but it would be really painful for everyone involved. So I hope you all understand me here in Texas. So my talks, what's that supposed to mean? And most of what I'm going to tell you is true. I've taken a few liberties to kind of fit everything into 25 minutes. But my name is Paul Batme. And on the internet, I use the username 3daymunk in lots of places. And people often ask me, what does that mean? And that's a reasonable question. It's actually a Japanese yōji jukugo, which is a four-character expression, which is itself a four-character expression. It's kind of nice. It's four-character expressions all the way down. It's kind of embarrassing. But again, that expression, mi-ka-bo-zu in Japanese, literally means three-day muck. But figuratively, it refers to someone who starts things and doesn't finish them. So that's kind of an image of someone who joins a monastery, but after three days, they finally ascetic life is too much for them. And we're all a bit like that. And so I actually chose that username kind of to broaden my own conscience into finishing the things I started. But just how do you write three-day muck in kanji in Japanese? Well, three is really easy. One stroke is one. Two strokes is two. Three strokes is three. And day isn't so hard either. What is the day, but the passage of the sun across the sky? And that's what the internet character is. It's a stylized disc of the sun. That's an old version of it from Oracle Bones from 3,000 BC. Overtime, it's got a bit squared off. But it's still one of the simplest characters. So that's three-day. But what about the muck? You could try to draw a picture of someone in monastic attire. But it was going to get a bit fiddly. It's really hard to do. And as you can see, that isn't really what's happened. So there's a more general problem here, which is if our writing system is based on drawing pictures of stuff, how do we represent things that we can't draw pictures of? In other words, how do we represent abstract concepts? Well, one way is to use things that we can draw, which sounds the same. If you've ever seen those things for typical kids, called the rebus, then you might just understand how this could work. So for this sake of argument, I suppose I want to say, I hear you. Well, I can use a picture of an eye for eye. And I can use a female sheep for you, because that's the best that I could draw. And here, well, it's not exactly the same as here, but it's close enough. And in some dialects, it's probably the same. It's actually kind of tricky to draw an ear. And exactly what an ear looks like might depend on your culture. But I digress. So we can pull these together to get I hear you, and probably people will understand what we mean.  So we decide to draw a full kind of stick of person next to them to indicate that they represent people. And that is more or less what the ancient Chinese did. So for example, how do you write an image? If everything you draw is itself an image, how do you express the concept? Well, the word in Chinese is xiang, which is conveniently exactly the same as the word for elephant. Elephants are a pretty easy thing to draw. This is an old Oracle-Bone elephant, which I could be drawn in an inkscape. So it's not exactly the same, but close enough. And it's got legs, it's got a tail, it's got a trunk. It's got a tusk, so it's recognized as an elephant. And over time, again, it's become stylized and squared off. And, personally, it's become rotated through a quarter turn. But you can still, if you sort of sit on the side and squint a bit, you can still see an elephant. So you need to have a picture of an elephant to represent the concept of image. But sometimes you might want to make it clear that you're talking about a person, so how do you draw a person? Well, we drew some stick figures earlier on, but the Chinese reduced it down to something simpler. The defining characteristic of homo sapiens is obligated to bipedalism. In other words, generally speaking, we walk around on two legs. So you can draw something like that and it's recognizably a human, and that sort of looks like a human. Or possibly it came from two arms, it's not entirely clear, looking at little characters. Either way, it's something that's sort of recognizably human. So that's what the Chinese character, the person is, but if you put it together with elephant, you get a thing that is about people and it's pronounced like elephant. And 3,000 years ago in Chinese and conveniently still today means image or a statue or portrait. And this kind of combination, which is a character for the area of meaning that is on the left, in this case, an anti-characteristic pronunciation makes up by far the largest group of Chinese characters. And in fact, of these kind of component parts, there's only a few hundred of them, they're called radicals. And so the problem of learning to read Chinese isn't quite as hard as we might seem at first, although over millennia, certainly the pronunciations have changed quite a bit. So writing Chinese on the other hand is still relatively hard. Here's a shopping list for a jiaozi, which is dumplings and the author of this is a research from the Chinese Academy of Social Sciences with a PhD and he starts writing some of these characters, given up and written them phonetically. So even for educated speakers, it can be quite hard. But Japanese is a bit harder still, as we'll see. So back in the fourth century, the Japanese didn't have their own writing system. They borrowed Chinese. And there's no shame in that. We use the Latin alphabet and the clues in the name. But Japanese and Chinese are completely unrelated languages and Chinese makes loads of assumptions which aren't even that good for Chinese always. But for Japanese, it's a very poor fit indeed. So the Japanese came up with a system called kanbun that involved firstly writing the sentence in Chinese, that's the left-hand column. Secondly, they annotated it with a set of transformations, kind of like a computer program that explains how you turn the Chinese sentence into a Japanese one. And that's the little annotations down the left-hand side of the left-hand column. Then they would execute this program and you can see the arrows. First of all, you move the third character down to the bottom. Then you swap the fifth and sixth characters. Then you move the third character down to the whatever it is. Sixth place, seventh place, sixth place, by now. And then you fill in all the blanks and you read the whole thing as in Japanese and all that's down the right-hand side. You have to go and make up on your own to work out how to pronounce it. So this was the way that the Chinese and the Japanese was written for a very long time. But luckily, some other people realized that you could just use the Chinese characters for their phonetic values and use just one character or a syllable. And this became maniogana. That, in turn, was simplified into hiragana by taking these complicated kanji and writing a cursive abbreviation of the strokes. Torontokatakana, which is the same kind of thing, another way of doing it, based on taking just a part of each sign. So there's only about 50 each of hiragana and katakana, which is kind of manageable. It's about the same order of magnitude as Latin or something, which has about 22 characters, but actually about 52, because we have lower-hand uppercase. And it's entirely possible to write Japanese just using those 50-person characters. And that's what children's books do, and it's still received as well. But in real life, it's a bit more complicated because firstly, there's a load of long words from Chinese, and those are all written in the original Chinese kanji with a bit of a kind of Japanese pronunciation. But to add on to that, Chinese words entered Japanese in about four different ways. So you've got the pronunciation from wo, or from utang, or sum, or main eras, and each of these characters can have several of these pronunciations. Then on top of that, Chinese characters are used to stand in for Japanese nouns and adjectives. Extraordinary characters are used to indicate things like the past tense or something. So that means that you end up with something like this, where red is Kazakana, black is Hiragana, blue is a Chinese loan word, and purple is a Japanese word that's written with a Chinese character. And it means that each character can have several possible pronunciations, which probably reaches its apotheosis in this character. You might recognize it from the Japanese beer label, but it's draft, it doesn't draft a bit. And in Chinese, it has one pronunciation. But in Japanese, it can be pronounced depending on context as shou, se, bi, o, u, o-o-o, o-ha, o-ki, o-nam, and so there's eight possible pronunciations for it. And none of these things. But Japanese, even despite all that, isn't that bad. There are more complicated writing systems or at least there were. So, slightly earlier than the Chinese, the Sumerians of Mesopotamia developed their own writing system, which is called cuneiform. And they started out with drawing pictures of things, which became more squared off over time. Quite anti-rosaic as well. The rotating character seems to be quite a common thing in history. Later, because it was easier to write on that angle. And then, because they were using read styles to press things into soft clay, they simplified everything to kind of pointy marks that you can easily make up with clay styles. So everything's sort of those forms of wedge shapes. And that's actually what cuneiform means, it means wedge writing. And the Sumerians sort of the problem of representing abstract concepts in the same way. Using readers, they'd use similarly pronounced characters to stand in for things that they couldn't draw. So, in the case of life, which is pronounced as teal, they would use the character for teal, which is an arrow, and that's, as in maybe we'll spell it in an arrow in a moment. It's obviously become quite simple for them by the time. And they also used something called the termers, which were signs to indicate what kind of thing they were talking about, a bird, or a name, or a tree, or something like that. And there was times someone like the Japanese, they reduced the number of symbols down and made much more use of the kind of syllabic pronunciations of signs. But this then starts to get rather confusing and ambiguous, so they took to kind of multiple redundancy approach, using low-grams and phonetic signs and deterrents all at the same time. So here is how you write raven in cuneiform. So the second character, Uga, is the word for raven. But it could also be pronounced as daga, which means soap or ash, which is a city, or Nisaba, who was the patron saint of that city. And so to make sure people knew which pronunciation was the one they wanted, they put an u at the start and a gu at the end, which, kind of to tell you, it's meant to be uga.  And the Sumerians were supplanted by the Akkadians, who spoke an unrelated language and adopted the Sumerian language system themselves. They regularised this bit into just five distinct strokes, and they used the Sumerian pronunciation before phonetic signs, and they used also the characters to represent Akkadian words. And sometimes the same sign could be either, so that's actually quite a part of Japanese. And it seems really unwieldy, I know, but cuneiforms stuck around for 32 centuries. You know, writing systems seem to, once they get traction to last for a really long time, no matter how bad they seem to fit. And then of course, there's the Egyptians. And that's kind of the same thing. They drew pictures of things they could and used them for a certain pronunciation of things they couldn't. So you know, there's a mouth, which is pronounced something like ru, and something like ra. No one really knows, because they never wrote about it.  The default was for it to just be a phonetic pronunciation. And so you end up with something like this, which is how you write the name of the god called Keppri. The scarab people is the pronunciation of most of it. Then they've added around the edge three other symbols with the same pronunciation, and then the e, and then god. And you could write, say, hieroglyphics in either direction. The way to tell this one is from left to right is that the people always face the start of the line. So I mean, they've got spacing left here. So we know that these are the end of the line. So that's Egyptian, but what's more interesting, I think, is where it went next into hierotic, into demotic. And these are kind of simplified scripts using a lot of phonetic, they were predominantly phonetic. But then it was the people who now lead them in Syria, who gave us all the evidence that we have today. They took a small number of Egyptian hieroglyphs and used them to stand for individual consonants. So that was the pretty sceniotic alphabetical that evolved into Phoenician, which gave us something more linear, more abstract, but became Greek and Latin, Aramaic, Hebrew. And in fact, a whole array of languages, including the modern things used today, is Latin, Greek, Cyrillic, Georgian, Mongolian. And I have a few different Aramaic scripts that serve South Asia or the Ghez, the Ethiopia. And those are called apiguitas, they're a bit like Alphabets, except that each character has a kind of interval vowel that's actually to it. And then you can add a diachritic to change the vowel. So the default one is, this is Devanago, it's in Hindi, it's equal to ka, then you can change it to ki, or ku, or ka, or ka, or a whole load of other vowels by adding diachritics. And this is Ghez, it's in Ethiopian, where you're going to be ka, and then you can add it to ku, or ki, or ka, or ka, or a ka. But, that's those scripts, the Parami script, which no one really knows the origin, might have come from Aramaic, so it might even go all the way back to Egyptian. But we do know that it's given rise to a whole load of other scripts. Lots of ones who used to be in India, Thai, Lao, Khmer, used in Cambodia, possibly even Korean, might have developed from an Archaic script that was developed from Tibet, but no one's really sure about that. But, you know, all of that is kind of a long-winded way of trying to communicate a simple observation, really, which is, I think that human writing has been guided by two main limitations, firstly, you can't draw everything, and secondly, you can't remember everything, and there's a reason that most of the extant writing systems are fairly simple. The hand script, the one used in Chinese and Japanese, is kind of an ally, but even that isn't tremendously complex. You know, even eight pronunciations for one's energy aren't so bad, any more than OUGH is in English, or no vowels written down is in Arabic or Hebrew. But, enough about the past. Nowadays, we have microns, and we have custom microns, and we have emoji, which is a really interesting word in itself for reasons that I won't be able to answer right now, but I'll ask you later. And that's just online. Offline, all kinds of devices have symbols representing, you know, the functions, their statuses. Here in the US, it seems like most of the kitchen appliances are marked in English, and the same kind of things change apparently in the late 90s with no Japanese. But in Europe, electrical appliances are sold in dozens of countries, with each of them as one or more for its own languages. And there's much more of a tendency to try to avoid human language in favour of a pictorial language that just works anyway. And some of these symbols share a common vocabulary. So, you know what that is? The power of symbol, right? Obviously, I see 5,000 and I stand by symbol. You see it everywhere. Andy kind of knows it means. Some of them only make sense in context. So if you see that on a weather map, you know it means the sun. On my washing machine, it means dry. And then of course, there's things that don't really make any sense at all. Anyone can ask a guess what that means? I think it's rinse and drain on my washing machine. I say my washing machine, it's not mine, it's the one that came to my apartment, and I wouldn't actually buy anything that's that horrible to use. And the really complex thing in my own back washing machine is that there's actually plenty of space to write things in English. And other things are already written in English. And it seems like this is just a really poor aesthetic choice that someone made rather than any attempt at communication. But with that in mind, I'd like to take you on a tour of some icons that I've cited in the wild. So, shout out if you know what these mean. No, we don't. We don't. That's really interesting. So, that is select all on Android. And I don't know that because I hit it once by accident. And so, mighty Google. I was talking to one of my colleagues about this talk a few weeks back. And I was telling him about some of the icons I was going to talk about. I showed him this one and he said, oh, is that what that does? And he's on Android phone, so probably no one knows. How about this one? How long is code? It was ViewSource at one time, but I think we're all sourced from it. They've changed that. I do, I'm mocking it a bit. I do understand well the motivation for this kind of thing. One time I worked on a website that was in four different languages. It was in Japanese, Korean, Chinese, and English. And it has Japanese designs. And they would give us all these layouts that expect every word in the navigation that's on to be two characters long. And that didn't work for English at all. We wouldn't work in German, even less, in fact. So how about this one? Hot water. I see. Hot water. So when I was a kid, I used to wonder why there was a picture. I thought it was just a sailing boat on the dashboard of my parents' car. And it's temperature-gated. It's, yeah, I don't remember what. How about this one? That's loud noise. That's really tiresome. Oh, it's like, teams you. So this is, I'm actually fitting a lot of parts into what no one knows what this is, because when I learned to drive, the first time I went out on a long journey, just after getting to my driving lessons, I was puzzled by this. I'd been driving for a while, like a few hours. And then I was puzzled by this warning light on the dashboard. And I knew something was wrong, because it was red, and it had an exclamation mark. And it was quite difficult to drive. But I thought, it's because something's wrong, right?  But not before I kind of destroyed the brakes, had to get in a place to create expense. My parents were absolutely delighted by that. But I think it's actually meant to look like a pair of brake shoes around the edge of a brake drum or something, but it doesn't really work. How about this one? You know what this is? So you get it. It's from something from the previous era called the floppy desk. And I'm kind of interested about this one, because it's a different word for saying. And yet, you know, no one has a floppy desk anymore. There are young designers who are going to move into the workplace in a few years who have probably never even seen a floppy desk. And you know, what do they need to do with this icon? Are they going to turn this into something more abstract? Maybe we'll just give it a say altogether, because it's probably a bad idea. I don't know. Now, the world of Java applications is particularly rich in icon art. Here's the clips. Now, I've never been in a Java program. So I can't even guess what are for these icons, me. I guess that the picture of a kind of like a scarab beetle or something is a bug or debugging. I guess the green circle in the triangle then is probably a run. I don't know what the kind of red briefcase is. I don't know what those things with the pluses are. I don't know why there's balloons coming out or something like that. I like to pen there's a plethora of arrows. It seems to me that this stuff is just there because I don't want to drop pictures. So how about this one? You might have thought so. So I think copy of this story is likely to be important on a pivotal track. I did consider putting a whole load of things from a pivotal tracker up, but because I'm obliged to use it and it has so many better icons than I thought it would be. And so I guess the final one is this, the hamburgers. I mean, this doesn't really look like a hamburger to me. It was like that black one that's ironed out in Japan. Not any hamburger I've cared to, but it's kind of rectilinear too. And it's kind of nowhere in the last few years, I think. But on the other hand, well, it doesn't really mean anything. It's so widespread, but it seems to be quite understood. I think the meaning is if you click this or press this, something will happen. It's just that we give up, kind of like. I was using something on my phone last night, and it's got a two icons like this. It's got a little bit of an Instagram. I had the white hamburger menu, which is actually a menu, and it's kind of really narrowed the hamburger menu, which is another kind of menu, and it didn't really, yeah, no obvious difference. But it wasn't my point with all this. I'm not actually sure there is a single point to a job, but one of the things that I want to observe is the recent language has evolved over thousands of years into an early and abstracted way of representing complex ideas. So we have alphabets like Latin, Greek, Cyrillic, or Korean-Hungle, and jazz like Arabic and Hebrew. Ad-hubidus, like David Adler in New York, Thai, or Slavery, like Japanese, Hylianna, or Cherokee. And the most complicated, excellent browsing system is probably Chinese, but even that's made up of a smaller set of common elements. On the other hand, though, we're currently in a situation in which every website, every app, every electrical device, every vehicle has its own visual vocabulary. And asking people to learn and remember and be able to use all of this is quite a big demand. I expect that it will follow some, oh, sorry. It's back. Yeah, I expect it will follow some of the same evolutionary paths as writing has done. But whether that means simplification and kind of reduction and getting things down to shared elements, or whether it results in the kind of explosion of difference in mutually-incorporated violence that remains to be seen. Thank you. That's me. There's some credits there, which I guess you're not gonna be able to read now. But yeah, you're not going to be L.A.M. No. Okay.


Hello. Hello. So I like is. Is this one that I thought you had said you wouldn't be able to attend are we disrupting you from. For a second. Okay, got it. So we will plan to discuss J. So to be right. I think that was on the list. Yes. I've got to look at the agenda. Sorry. I haven't, I haven't opened the agenda yet. Do you have an update from Dan and Tara from Google on this as well. So only if you're unable to attend is it sensible for us to discuss Google summer of code today should we delay the discussion for another time. Well, if you want to discuss that I will stay. Okay. All right. Thank you. Helpful. Right now. Another on other fronts. Okay. So want me to share the share the notes as a screen or do we want to. Oh, I'm on the host. Maybe I should make you the host mark. Hey, hello everybody. That would be fine if you find if you need to drop off. Yeah. Okay, so you've got the powers. Can everybody hear me okay. Thank you. So how about, should we assemble the agenda. I'm going to go ahead and share my screen and we can start working on assembling the agenda and share this screen. Got it. You should see a copy of the agenda. Yes, we can. Okay, super. So topics. Got Google summer of code 2021 planning. Good one to have discuss while all legs available for us. Other topics that we need to discuss live stream sessions with Darren Pope is that one that Alyssa you'd like to discuss. Promoting, et cetera. Any other topics that need to be on the agenda for today. I think I was just going to give a heads up about the, the Jenkins is the way ebook. Oh, yes. All right. Boston as well. Boston. Okay, good. All right. Any other items that we need to put on the agenda. And then for me, just the annual report reminder. All right. Okay, so let's put that CDF and your report. Oh, like, do we need anything on the, we had discussed at the end of your blog post for the Jenkins project already handled or the one we discussed yesterday, not handled. So, yes, and so you have market, it would be nice to discuss. Great. Okay, so how about just some cup again. Perfect. Yeah. All right. Hey, so shall we talk to Google summer of code 2021 planning first. Yeah, so I brought this up at the TOC meeting last week. And so Dan Lawrence and Tara Hernandez are both Google employees and also Tara was involved in in Google summer code as an admin last year. So Dan reached out to them about us applying under one application versus multiple. So it looks like they're, they are willing to honor all of the slots that they've given Jenkins in the past. We just have to make a note. Under the anything else section that CDF like we are going to be including Jenkins and Jenkins X under us under this application to remind them, you know, of the allocation that normally Jenkins gets. Yeah, to be seen whether we can ask for this location, because we still to prepare this approach ideas and to on board mentors. Right. Okay, good but but Jackie I think what Jacqueline what you were saying is that there was a risk previously that Google summer of code might see CDF and say hey you haven't had a large number of projects before.  And what you learned from Tara and from from Dan was they will honor that so long as we remind them. Yes, exactly in our inner application so excellent. Okay. Question about doing this under the CDF org is who will handle actual org admin duties. I don't know we'll have to ask somebody to take this on last year it was also Tara so we can we can also ask her if she'd like to do that again. So, for Jenkins, we have three contributors who really much and can be important means it's a car and me and market. I'm not sure what is our total capacity would be because everyone has other commitments as well. So should we should should I say here in the notes all like have have been or willing to or have been org admins in the past. I think I remember Cara saying that she would be happy to be like an org admin for the Jenkins and Jenkins X. And then I think last year. On the driver's side, it was Jithin who participated and I believe from the spinnaker side, it was Roslyn. I'm sorry. I interrupted. No, please finish I interrupted. Yeah, so these individuals. Will they actually be org admins or mentors. Okay, sorry. I believe they were mentors and I believe Tara was actually the one that was the org admin for the CDF. I think Tracee. You're looking to call correctly and me as a backup. So, I definitely remember that we used to all fight for admin slots. I can definitely I can org admin but I would like to know who the other org admins are going to be that will. I don't know what to say this but I'm going to just say it straight that'll that'll influence my decision whether I can do it or not, depending on who's doing it. Yeah, I don't think that's defined yet Marty. Okay. So are there are there. We know about the need for project ideas. The request has been launched. Yesterday. It needs more promotion is that. There's a lot of channels that Jacqueline or others could be acting as voice for we we tweeted about it yesterday we. We use LinkedIn. Mark, I also included it in the continuous information newsletter. And I think this, I think I saw the blog yesterday so I can always send it over to Roxanne or newsletter editor and also include it in the CDF newsletter that goes out in January. Jackie, would it be worthwhile to do a to cross post the blog and CDF blog. Yeah, yeah, I can make that submission. Yeah, I can just send it to Roxanne. I'll just send her the link and ask her to cross post and to also include it in the newsletter for next month as well. Okay, so is it Roxanne that is handling the blog post for CDF. Yeah, the blog post and the newsletter yes. Okay. And now now for the larger CDF, I guess, I guess this is Jenkins advocacy I don't have to worry about the larger CDF promotion, Jacqueline I assume you'll take care of that. Yeah, I've been, you know, I've been going around to the TOC into other meetings and letting them know about this and, you know, asking people to just also figure out what they want to do for for Google summer code. So people are aware like the stakeholders from last year are aware. I think I just have to keep pushing on to see if they're going to do anything about it and so I just, yeah, I just don't have an update on that. I haven't heard. Are there other questions relative to whether we whether the Jenkins project works under the umbrella of CDF or not funds was one that we had a discuss discussion on our payment management last time. Is that something that needs further discussion today. Not from my side. So, so budgeting. I think we can figure it out. Okay, all right. It's not an immediate issue. Good. Okay, so we have number of students we can decide how this particular money distributed quite easily. Then there are travel grants. I'm not sure that they will be pleased to please mentor summit next year. Yeah, anyway, it's definitely something. Great. Excellent. Okay. All right, so we know about the need for mentors and that's part of the part of the launch that happened yesterday. Any other topics on Google summer of code. Okay, next topic then live stream sessions with Darren Pope. So maybe you could highlight for us what, what this is and if, if you're not comfortable, I can certainly describe it but share with us what what's happening here and how it can and how it can and does help. How you're muted. Sorry about that. So, thank you, Mark. So feel free to jump in and add anything you think I might be missing Mark. But, so Darren Pope is a developer advocate for a cloud beast. And he has started a channel right now it's a live stream channel and the first one I think was the first one that he did or at least it's the first one that I was aware of is was the one that he did with Mark. And it was talking about the LTS. Mark is currently on YouTube at the moment. And on that video Mark went through a lot of really good information about LTS and some of its status updates. So what I did last night was I added it to the continuous information newsletter because I was working on it last night. I also thought might be good for us to include it in the CDF site. So what I want to do is so it's a good video wanted to see if I will work with Darren to see if we can get a blog out of it. And then we, we post that on CDF as well to promote it. And then there was another video that I found out last night was Darren interviewed Marky and Gavin as the newest members of the governance board. So I also added that to the continuous information newsletter. But it might be worthwhile to to cross post that to or get that information on CDF if Jackie thinks it's appropriate or if it's too much. It's fine too. Yeah, I think just send it to Ruta Roxy and since she's the one managing the newsletter and the blog. And then if she has any, you know, concerns she'll raise it to Tracy. So, yeah, it should be fine. Okay. Jackie, any, any feedback from you how did the session go for you was it net positive net negative insight. I thought it was, I thought it was net positive I really liked his format. It's very free flowing, but you kind of have bullet points, and he'll let you know how he's leading into a bullet point. So they'll be like banter and, and then you know you're going to get into a bullet point because he'll use a certain word. I liked it so well I told him that hey anytime you ever want me back I'll be back. He actually sent me an email and I'll be going on next week as a plugin maintainer and talking about plugin maintainers go so I really enjoyed it. So maybe that'll be a good opportunity to get more plugin content maintainers in the future. Yeah, that was the that was kind of the idea was to, we're going to highlight a series of plugins that are up for adoption. So maybe generating some interest in that I really, I really thought it was a, the format's good and I think we can really utilize what this is. Great. Thanks. So any questions from the group to Alyssa or to others about about this concept or how it's how it's working. Okay. Anything else from you Alyssa before we go on to next topic. I think I'm good. Thank you. All right. The Jenkins end of your blog post. So, I think this was one where Markey you and Oleg are working it together or how about you share for us, the status of things that we coordinate. Yeah, the, I'm still working on a document I got sick a little bit yesterday so I wasn't able to do it I'm hoping to have the Google Doc out this weekend. And then we'll get that the goal would be to Oleg would you say to have this published by before Christmas. So like before next week. Oh, I mark it looks like we lost Oleg he just dropped off. I think the goal is a good. Oh, no, I hadn't. Last year we published actually after January one. So, so before Christmas sounds really great, potentially a little aggressive. Okay, we that was just something we were just kind of throwing around so if we wanted to sheet for the, the, I think the fourth of January is kind of when everybody comes back from holiday. And I don't want to buy a shoe in terms of, of what you choose as your publication date you and you and Oleg can work it out whatever whatever you prefer this is, it was a very successful blog post last year and I, I think it's a great story to tell again this year. Yep. So I will, I'm going to tentatively shoot for the before Christmas. That'll be a tentative, but the stretch will be for the fourth of January. Okay. Great. Thank you. Anything else on the end of your blog post. I assume that you're taking you'll accept suggestions and ideas and topics. Yeah, when I send out the, I'll send out the Google doc, it'll probably go out this weekend. And then, and I'll put that in the advocacy mailing list so people can drop comments and sort of make it organic. Great. Okay. And we got Oleg back. Sorry, I remember that it was exactly this topic. So yesterday, we agreed that we'll sync up with your marquee and started this Google doc. So, yeah, this weekend. Yeah, yeah, my goal is to have the Google doc out this weekend, hopefully Saturday. And I was, I was going to try to hope that we could get this out for before Christmas. And that might be, that's my goal. But if not, I was thinking the next day would be the early January, like maybe the fourth of January is when everybody comes back tomorrow. So usually we publish it in the January. Mm hmm. But yeah, if you get it before Christmas, it would be awesome. Great. Anything else on the end of your blog post anything there Oleg that you need to coordinate or any concerns. We just need to get started and put some content. Excellent. Super. Thank you, Marki for leading it. Thanks a bunch. Thanks, Mark. So, Jacqueline, CDF annual report. Yeah, so I think I think I'll be good then if if Marki's because most of the time I just pull information from the end of your blog. So I think that will be good I can just take stuff from that that Marki puts together. So for the CDF report, Jackie, I'm going to actually send you the end of your blog report will have what I'm also going to send you separately which will just be kind of like what we used last year. It's kind of like the stats of the project. Yeah, that works. We'll also want to link back to your blog as well. Okay. Anything else on the CDF annual report you want to share the dates again just to remind everybody timeline. Yes, so our goal is to publish the week of January 18 through the 22nd. And then for projects, we gave them a deadline of, I think, January 13 to get all of their data points and blogs and all that kind of stuff done. So yeah, those are those are the two, two big ones for for projects. Excellent. All right, anything else Jack. I'm okay. Okay. Alyssa Jenkins is the way ebook status. Right. Okay, so I'm off mute mute. Okay. So the link in the chat window so that is the discussion that we've had with the developer mailing list and mark I'm not sure if you're able to pull it up but the initial the original email shows the a version of the ebook. So, basically, I went to the governance board yesterday asking if we if they would like to have their names in the under as the signers of the this letter. Oleg rightfully suggested it should be my name but I would also like to add and and or the advocacy and outreach sick. So I'm going to move forward with this draft. Based on some of the edits that Mark and Oleg has suggested previously, and then instead of the Jenkins project where Mark has highlighted, I will have Alyssa tongue as events officer for 2020, and the advocacy and outreach sick. If that's okay. I'm a person. Okay. This looks really good Alyssa. Great. Thank you. Yeah, I'll let me know when it's final so then I can tell Roxanne and she can add it to our website somewhere. Perfect. That would be great. Thank you Jackie. And that's it for me. Easy one. Great. Thank you. All right, Mark, you I think you had brought foster 2021 is a topic. Want to lead that discussion. Yes. We'll be having a Jenkins table. Jackie, I need to get with you at maybe some point this week or early next week to make sure that I'm in coordination with the CDF for that. I. Yeah, I need so yeah we should think is we haven't done anything for FOS dumb yet and I know. Yeah, I'm so out of the loop on that one. So I'll ask also Tracy. Yeah. Yeah. I'm just curious. I thought that somebody had gotten like a dev room already. Jenkins does have the, the CI CB. Yeah. Olivier will be doing that. Yeah. Alyssa shared documents with me to go out like how what we did last year to set it up. So that's what I was going to meet with you. I just haven't had a chance to actually tell you so. I'm telling you. So the next two weeks, we are out. We're taking some time off. But if you want to catch me there today or tomorrow, my calendar is up to date. Awesome. So yeah, just let me or if we can wait till the, like beginning in a new year on the fourth, let me know. Yeah, I'll get with you probably tomorrow. Okay. Thank you. Jackie, I think I sent Markey if I'm not mistaken. Collateral that that you, what you use at the booth last year. So it might be just reviewing that and see if you want to update it and then have that available for download. Yeah. Yeah. That would be great. Yeah, I'll forward to you what I sent. Markey. Super. Thank you. Last item I had was to remind that we agreed last time that we would cancel the cancel the December 31 meeting. Any objections to continuing if that plan that December 31, we won't meet. I'm a plus one. Me too. Yeah, next meeting is then whatever that date is in January, looking to see so it would be. Yeah, January seven. Thank you. Something like something like that. And I apologize. I will be, I will miss that meeting. Out for a personal adventure that day. Is it your birthday. No, no, it's nothing, nothing that cool. You're turning 24. That's right. That's right. And I tell my children that all the time turning 24. Yeah. You don't look a day over 23 to me. Keep it up. That's the way. Flatten flattery and recorded. I like that. Okay. Any other topics before we close this meeting. Okay. Actually, Mark, I have one. So I have on my calendar as December 20. December 28th is when we need to submit. Some kind of Jenkins content to Roxanne to include in the CDF newsletter. And that's for the January newsletter. Yeah, the project updates a project highlight. And so we kind of missed the vote last time when the last newsletter, but so I have it on my calendar. What was that Oleg. Yeah, maybe there are perils threads, but then Lawrence requests. The updates and the last months I definitely sent one. Yeah. Okay. So I want, I just wanted to make sure that I have it on my calendar and that I have it on my calendar. And I also want to make sure that I have it on my calendar. So it's my responsibility to, to get something over there. I mean, something needy, what, whatever it is that we want to highlight for that month. So just want to give a heads up that I'll be reaching out or at least I'll do an email, just to remind folks what we want. What do we want to highlight for the month. For from Jenkins. Okay. Jenkins has a table and there's a room, all that kind of stuff. Yeah. I think, well, I know that for at least in the continuous information newsletter, we have foster under the event section. Okay. Yeah. I just was saying, like maybe a line that says, like, Jenkins is going to participate in that. And then we, we also add like the link to foster them in the event section. Oh, okay. February 6th through the seventh. And I don't know if, if we'll publish the next edition of the, of the February newsletter in time to also capture that highlight. So that's also the only reason why I brought that up. Yeah. No, that's a good point. I'll work with Roxanne to make sure it's included. Yeah. So is it for my education, is that a place where we highlight information that we'd previously posted in blog posts. Blog post summaries go into that? What sorts of things have you done in the past? Oh, like when you've written that, or is that something we, somebody else writes and I just am not aware of it. So for status updates, it's usually something like five lines, maybe a bit more of these key updates over the months. I'm going to drop also like last, the last newsletter edition and then I'll also add. Yeah, it's. Yeah, I think December was the second time we did it and then November was the first time we did it. So here are two examples of how, what we've collected under these. Program updates or project updates, excuse me. Yeah. Project updates. There we go. Got it. Okay. All right. So it was really short last. Why did it pop up my email? Excuse me. I should not click links when I'm live recording. Should I? That's great. Okay. Yeah. So, and then on the, on the November edition, we highlighted all of the, for example, the 2020 elections committee announcement. So yeah, I think it's, it's a combo of things that we, that you can include. Got it. All right. Jackie, this page, the one that you just said, well, the one that Mark is showing right now, it kind of looks like what we, we receive in the newsletter and the email. It is. So basically we're sending out the newsletter over email first, and then we have the archive as a webpage. So Alyssa, I thought, I thought one of the, one of the challenges or one of the concerns had been, Hey, we want to be above the fold when we can, because we're a big part of CDF. Yeah. Yeah. So Jenkins, we feel that Jenkins is a very big part of CDF. And so Mark, if you go back to the other page, so I guess I was referring to the actual newsletter that, that most of us saw in our email. And it, so in one of these boxes, these black boxes, there weren't anything that was on Jenkins. And so that was a concern that was raised. And so I need to make sure. Yeah. So are you talking about the CDF newsletter specifically, Alyssa? Okay. So the thing is every month we have its theme based. So the, what Roxanne's been doing the past few months on, on the, on the newsletter is based on that theme. She took sessions from CD con and turned them into blogs. Okay. So if, you know, if, if Jenkins is in part of the theme or didn't have content, that is, that's why it's not featured there. So like last week, it was like CD and action. And so we just took from content that existed and converted it into blogs. Okay. Yeah. Okay. That's good to know. Thank you. Yeah, but I did give Roxanne a heads up that going forward that, you know, like I said, I have her deadline on my calendar. So I'll work directly with her just to make sure that we either, either we have something on there or we don't. Yeah. So the, and then the project updates is going to be a static part of the newsletter moving forward as well. So I know Dan Lawrence also bugs the TOC to get updates from the community. So, but yeah, I think that the more updates that you have, I think the better. Okay. So, so Alyssa, it feels like they're the. You, we may benefit by you bringing to us what the theme is that Roxanne's working on for the next newsletter. If she's selected that, and we can be thinking around how do we fit something into that theme? How do we answer that address that theme? Yeah. Me. Jackie, are there themes defined in advance? How far? Yes. Yes, they are. Let me, I was just going to pull up the newsletter repo. Yeah. Here you go. Yeah. So everything is outlined there. Right. That's great. Thanks, Jackie. Yeah. Yeah. So if the, I'll ask her to a reminder. I think they, she's just working with Tracy Miranda right now. I'm defining what next year's topics are going to be, but once she has all of that, she's got up to February. But yeah. Perfect. Thank you. All right. Anything else on the. CBF newsletter. Alyssa or Jackie. I'm good. Okay. Any other topics. We're good. All right. Thanks everybody. I will, I will end the meeting then and post the recording shortly. Happy holidays, everyone. Happy holidays, everybody.


Hello in this lecture, we will define form 940 according to fundamental accounting principles. Wow 22nd edition the definition of form 940 is Iris form used to report an employer's federal unemployment tax Futa on an annual filing basis when we're thinking about the form 940 We're talking about a payroll tax when we think about the payroll tax We're usually thinking about the FICA tax social security and Medicare This is going to be the federal unemployment tax and it's only going to be an employer tax meaning It's not being taken out of the employee wages. It will be based however on the employee wages But it's paid by the employer only the form is going to be done annually rather than quarterly So the 941s reporting the Medicare and the Social Security and the federal unemployment Will be on the quarterly 941s. This will be at the end of the year the 940 It's usually a lot less because the unemployment tax the federal unemployment tax generally is far less in amount The form looks something like this. This is a 2016 form from iris.gov We've got the information for the business up top in essence the calculation of the tax liability would be That we're gonna have the employee wages multiplied times the tax rate However, there's a cap on the wages something around 7,000 so every employee up to that cap very low cap So just about every employee reaches that cap if they haven't been employed for a significant amount of the year And then we're gonna take that multiply times the rate that will give us the liability We're gonna compare that liability to what has actually been paid So remember this is similar to the form 1040 for an individual in that we've already made the payments The iris expects payments to be made throughout the year and this form is really just confirming the payments as would a form 1040 For an individual a form 1040 for an individual However is almost never gonna be exactly correct and it usually results in a refund if all we have our w2 Wages because the withholdings are usually bigger than the amount of the actual tax That's how the system is set up the food attacks. However is more of a flat tax rate We don't have that the progressive system therefore it should be exact by the time we get to the end of the year We should just be filing this form to confirm the fact that we have this amount of liability for the year And that's how much we have paid during the year However, if that's not the case, then we'll have a refund or an amount due at this point in time off the payroll


this quote from Stephen Lucas from his book in 2008. Now, when you consider the organization of your presentation, I think it's best to start with your body. As Jeremy comfort explained in his book, effective presentations. Well, I studied by Jeremy in 2008, so it's that there are two basic ingredients. The second thing to consider when delivering your presentation is non-verbal communication. Barbara and M&P wrote an excellent book about this and details of which are on the final slide.