Entrepreneurship is fast emerging as a transformational mega trend of the 21st century, given its capacity to reshape economies and industries throughout the world. The 21st century entrepreneurs have now become key drivers of the economy. They are the lifeblood of any expanding economy, driving the society by generating jobs, introducing new products and services, and promoting higher upstream and downstream value chain activities. In this video, I will share with you 9 things that have changed about entrepreneurship in the 21st century. 1. Financial incentives The governments of various countries of the world are beginning to encourage individuals to venture into entrepreneurship as well as equipping individuals with facilities and funds needed to be a part of the entrepreneurial revolution. While the venture capital industry continues to globalize, governments and markets are exploring a range of financing strategies to provide capital to entrepreneurs including microfinancing, crowdfunding and credit guarantee schemes. Governments and even non-governmental agencies of this dispensation offer financial incentives to their citizens to start new businesses to save the environment or end illegal activities. For example, grants are being offered in countries located near the Amazon Forest like Brazil and Colombia to complete the destruction of the Amazon by stopping login and cattle grazing on the Amazon Forest. Many countries located near the Amazon Forest are finding alternative means for their citizens to make a living. Also, governments of many African countries give loans and grants to masses to alleviate the high rate of poverty plaguing the continent. 2. Women and entrepreneurship Many countries have realized that the only way to decrease poverty in their countries is by educating and financially empowering their women. One famous African proverb says, If you educate a man, you educate an individual. But if you educate a woman, you educate a nation. Back in the days, entrepreneurship was only meant for the men, especially in the African continent, because it was believed that the woman's job is to only care for her home. However, this century has experienced a remarkable change of perception. The importance of assistant women for starting their own small business is now seen as a way to improve their family's financial situation. Women this days make up a significant proportion of those in charge of startups. In emerging markets, the G20 estimates that females, either through full or partial ownership, represent 31-38% of registered, small to medium-sized enterprises, SMEs, according to the Global Entrepreneurship Research Association. There are now even countries where females report equal or higher entrepreneurship rates than men, one of which is Qatar. 3. Collaboration Companies before have companies in the centuries past experienced synergies as it is occurring in this 21st century. Outsourcing has become almost like a basic necessity for building a formidable business. It is fundamental. The successful entrepreneur of the 21st century is one who has the spirit of making connections and creating collaborations. Big companies are starting to outsource a lot of their work to small businesses because they are beginning to see the numerous benefits of outsourcing. Companies collaborate to cut costs, create brand awareness and visibility, and break through new market grounds. Partnerships are also formed mostly between big and small organizations in a bid to get government deals, as many government agencies are now requiring large corporations to hire smaller corporations to get specific contracts. In many cases, these government agencies set aside certain percentage of bidding contracts for small and minority-owned businesses. Generally, entrepreneurs in the 21st century have turned from competitive to collaborative. 4. Social Ethics An even more recent shift has been the rise of ethical entrepreneurs. Previously, most individuals have ventured into business except for a few who were visionary did so only for profit's sake. However, touched by the social desire to stem corporate greed and in line with a growing trend for conscious consumers and environmentalism, today, entrepreneurs are no longer purely profit-driven. The aim of entrepreneurship has moved from profit to value. People set up businesses these days to provide solutions to problems, improve on existing solutions, or the desire is to build a socially conscious enterprise that returns something to the society. Companies such as Tom's, the shoe store, which runs a one-for-one policy, buy one pair of shoes and another is donated to a person in need, is a prime example of social entrepreneurship. Though also is Ecosia, the search engine that claims to use over 80% of its profits to plant trees where they are needed most. 5. Advertising Strategy While signs of advertising are detected in ancient eras, its biggest boom came around the mid-19th century in capitalist economies through the use of newspapers and magazines. Radio and television commercials during the 20th century increased the saturation of ads, covering every bit of blank space possible with marketing campaigns. The 21st century is no exception to the evolution of commerce. Social media is now the leading platform for advertising. If your business is still focusing on traditional forms of marketing, your campaign is officially outdated. Thus days, the overload of exposure has resulted in consumers seeing right through marketing strategies and people generally do not like the idea of being sold to. They want to be able to feel like they decided to buy, not that they are persuaded. Online advertising has a way of convincing customers, yet making them feel like the decision was theirs. Besides, while the print and commercial ads have their limitation in space and time, online strategies break through that barrier. Thus, every successful 21st century entrepreneur is one who has leveraged online. 6. Technology Use Even though industrial manufacturing has been in slow decline in developed nations, global entrepreneurship moved in to fill the void according to the 2017 Minaventure Report. Tech companies, e-commerce, software and technology in the UAE made up to 29% of new businesses. In the 1950s, these were a distinct minority. These days, even if a company is not a tech startup, it's highly likely to be utilizing developments such as social media apps and websites. Technology also means it's possible to work from anywhere at high speed and a normal skill. You don't necessarily have to leave where the money is anymore. And you don't have to spend your day knocking on doors. The internet has been vital to enabling this. In the quest to go global, businesses are expanding their workforce to include and take advantage of startups in smaller, developing nations as well as knowledge from around the world. And technology has made remote and virtual involvement possible. 7. Younger Entrepreneurs According to the 2013 Global Entrepreneur Monitor, nearly 50% of the world's entrepreneurs are between the ages of 25 and 44. With 25 to 34-year-olds showing the highest rates of entrepreneurial activity, high youth unemployment rates in many countries of the world, paired with changing work and lifestyle preferences, are creating a new class of young entrepreneurs. Youth entrepreneurship is high on the political agenda as a means to boost competitiveness and employment. At many of ETFs' 30 partner countries signing up to the Small Business Act for Europe, the opportunity to build the next generation of young entrepreneurs has never been better. 8. Education One of the reasons why entrepreneurs can start younger is the rise of entrepreneurial culture. A whole lot of universities now have entrepreneurship, a core for every student of the institute. And even individuals without opportunity to attend universities are not left out in this 21st century entrepreneurial revolution. They still have access to knowledge through self-learning, such as via free online courses or YouTube videos. Never before have there been so much information available for free or next to nothing. Today, every founder can read all that there is to know about running a startup online. Incubators and accelerators like Y Combinator have institutionalized experiential training in best practices, product market fit, PVOTs, agile development, etc., providing experience and hands-on mentorship and offering a growing network of founding CEOs. 9. The Demand for Skills Entrepreneurship is no longer the domain of people with bright ideas and a dream, but those with brilliant ideas and focused training to boot. Think of how different the world looked when you were much younger.  Can you accurately predict what jobs will be trending by then? What technologies will be prevalent and what will be obsolete? The 21st century entrepreneurship has shifted the focus from just competencies and hard skill to digital and soft skills. Anyone who wishes to grow in this present era must be open to learning new relevant skills from time to time. Depending on your era of expertise alone is an invitation to failure. In the 21st century, the barriers to entrepreneurship are being removed. Further, replacements with innovations are speeding up each entrepreneurial step. Some, by a factor of 10, are being made.


Welcome to the Jenkins Governance meeting. Today is October 14th. We have several contributors on the call. Alex, you have Mark White and me. Today we will go through the common agenda. We have some news to share. Then we will talk about trademark usage requests we received over the past week. We will talk about ongoing Jenkins elections and everything of several definitions and we will schedule the next meeting. Basically, that's it. You might get more topics during the call if somebody else joins. But yeah, let's start from the agenda. So, October 1st. Yeah, actually in the middle of October 1st, so it's a month-long event. We have a number of future projects published there and we need to see if there are contributions in these future projects. So far, so good. Today we had an online meetup to talk specifically about Jenkins documentation and contributing to Jenkins. You've got how many, 20 participants are there in total or so. And we will publish it according to today. So hopefully it will help to participate in the contributions a bit. But compared to the previous year, October 1st remains relatively slow. So if anybody is willing to push particular areas, you're welcome to do that. Still, there are some contributions we expected. So it's going pretty well. If you are watching this recording and if you want to contribute to Jenkins, this is a good time to do so. Okay, CDCon. So last week we had a CDCon conference. We had a few Jenkins talks there. Also, there was Jenkins Birds of Fear session where we discussed Jenkins roadmap. There were other activities in the community in the CDL booths. So thanks to everyone who participated. The conference went well. The recordings should be published by the end of the month. So stay tuned. We also plan to organize a few events to talk about specific topics. Yeah, I guess that's it with CDCon. And we didn't have any major events planned until December from what I know. In December there will be a Jenkins user conference in Japan where we have several speakers. And yeah, this conference will be entirely about Jenkins. So hopefully we will be able to have a remote booth there. Usually it's not an option, but since everything is remote this, yeah, maybe we could do that. Okay, on the technical side, last week we had the LCS release. Mark, would you like to summarize it? Yeah, so 2.249.2 was released last week with a fix for a regression in one area and a few other improvements to Jenkins 2.249.1. The release automation worked without a hitch flawlessly. It was great. Great. Thank you. Yeah, quite a number for a fix. Okay, and the next LCS version. So on October 21, according to our schedule, we will be selecting a new baseline. So if anyone is interested in this identity of feedback, yes, we had a common weekly release. So unless something terrible happens, you'll have only one release until the baseline selection. And what it means is that if you see any regressions, and it looks like there are some regressions reported, it's not working anymore in 2.6.1. I don't know what's broken. Yeah, so some, well, we updated JK. What could possibly go wrong? Yeah, but yeah, that's the point, because next week we'll be doing selection. And if you scroll down the last releases, you're not this stable, I would say. So actually 58, 57 was the last release when you had no regressions reported. So we will have a choice either to take something recent, do backporting, and for that we will need information for the next meeting so that we can make decisions whether we can backport things in time for that one. Or we proceed with conservative way, but yeah, in such case it will exclude a lot of changes. So let's see. Yeah, the decision will be made next week. So I guess Oliver will start for selection, selecting a new baseline soon. Yeah, hopefully we'll be able to stabilize it in the next weekly so that we don't have to worry about the regressions. Okay, any other news, comments? Okay, then we have two trademark usage requests, one from Techmatrix, another one from Websoft9. And basically these requests are Jenkins trademark usage. So currently we don't have specific pre-approved patterns and every request should go through the Jenkins governance meeting to be approved. And yes, there are two requests we've received. So one is for Techmatrix Jenkins support as a trademark and another one is for Jenkins on Ubuntu by Websoft9. So we need to make a decision on that. And yeah, for that, I added additional topic to discuss is whether it's a good time to actually start enforcing Linux foundation patterns. Because yeah, as a part of integration from SPI to Condizion Delivery Foundation, we expect transition trademark to the Linux foundation. And after that, this trademark usage guidelines would apply to the Jenkins project. So the trademark transition hasn't happened yet and we're going to have timeline. It's one of the topics we need to discuss later. But yeah, the principle that at some point we will need to adopt these guidelines. And actually these guidelines are very reasonable. So we will read to these guidelines since 2016 or so. But we haven't been enforcing them. So there is a lot of text. But yeah, important things that there are pre-approved trademark patterns which are considered SPI use. And just it would allow to set common rules how these trademarks should be used. Secondly, these patterns seem to be very reasonable. And my personal preference would be to proceed with adopting this trademark usage guidelines, even if the trademark is not officially transferred to the Linux foundation at the moment. I'm a plus one on that for sure. Yeah. You could reserve a right to make exception if we really see a need to do so. But yeah, as general guidance, I think this rule is fine. I do not see any problem with pre-approving these patterns. All the disclaimers say that to the least. So for me, this would be the preference. It's a good idea, I think as well. So now do any of the proposals contradict or violate the guidelines that Linux foundation offers here? Most contradict both. And yeah, so let me open approved trademarks. Yeah, this list is a bit dated. It's actually my fault because last time when I was approving trademark for Jenkins rule, it was last spring I took an action I can to migrate this page to Jenkins IO, basically somewhere. Then we had a discussion about how to store governance documents and we agreed that we can move these pages to Jenkins IO. And now I have an action I team to actually do that. But if you take a look at the list of these trademarks, we previously approved. So the situation is I guess none of them actually fits the pattern. So there are multiple reasons why it happens. Firstly, because basically if you want to use an existing trademark, you would want to put the popular term in the front. And many trademarks had Jenkins in the beginning. Some trademarks firstly put to the company name, the trademark name, then for example, called these Jenkins, it's popular. And get this how trademarks are usually organized. So that's what we have. And none of that is compliant with Linux foundation trademarks. So for me, firstly, whatever we do, you wouldn't apply this guidance retrospectively. So whatever we have already approved is approved. When Linux foundation started, they had exactly the same case because there is red hot enterprise Linux. But yeah, it also doesn't get these trademarks guidelines. So I think that for us, it's generally good. But if you take a look at these trademarks, you can just break them down. But none of them really is really compliant. So Jenkins on Ubuntu by Websoft. So Jenkins in the front, Ubuntu is additional to this part, which is another trademark being used. And I'm not sure how it should be approved in this case. But I guess it's not our problem. But yeah, this pattern doesn't work. So it could be, for example, yeah, Websoft 9 distribution for Jenkins, Websoft 9 Ubuntu distribution for Jenkins, et cetera, all of that would fit this trademark. But not like it's written now. Pretty much the same for other trademarks. So it's a Techmatrix Jenkins support. So this case is a bit more tricky because even if it doesn't match the trademark as is, we have a precedent when another simple trademark was approved, basically CloudVis Jenkins support and CloudVis Jenkins access. So even if it doesn't fit the trademark guidelines, rather than towards the same plus one for that, even if they prefer this pattern, well, I would still recommend the Linux Foundation pattern. I think if we haven't, go ahead, Mark. After you, Alex. I was just going to say, since we haven't adopted the Linux Foundation usage yet, I think we have to go with what the precedent is. So I think we need to plus one that for now. And then once we adopt the new naming conventions, we can specify that those override previous precedents and new requests should meet the Linux Foundation pre-proof patterns going forward. That's my take. And I think the Techmatrix example, for instance, if I read it correctly, could be pretty easily changed. If they were willing to do Techmatrix support for Jenkins, that fits with at least one pattern that the Linux Foundation seems to use. We shouldn't, we don't get to change their proposed trademark. I understand that I was just thinking, it's, they're not that far from the pattern that seems to be okay with Linux Foundation guidelines. So here my recommendation would be to recommend them to consider the Linux Foundation pattern as our preference, but still approving the current trademark if they want to do so. Yeah, I think that sounds like a good plan. So just to be clear, that would give them approval for Techmatrix, Jenkins support and implicit and approval for, if they chose it, Techmatrix support for Jenkins. Yeah, got it. Thanks. Okay, Techmatrix enterprise support, commercial support, it's basically they own and choose how they promote that and how they choose the name. But yeah, as long as it remains within the pre-approved trademark pattern, they don't even need to agree with us. There are some exceptions, of course, but yeah. Yeah, so they still should avoid confusion, etc. So this pattern might still be a problem, so it's not guaranteed in all cases. But yeah, I think that we should be able to pre-approve it. Everyone was a plus one for that, right? Yes. Yes. Yes, for me, yes. We'll apply a quick one retrospectively, everything remains approved. Yeah, until the transition is over, make exceptions. We'll capture it well. Any additional notes we would like to add there? So that covers the Techmatrix one. Could we go back to the Websoft nine one, or were you planning to do that already? Yeah, so let's finish with them first. I was just making the common notes. So yeah, this is Websoft. Okay. In the approval message, I'll also say, we are looking at adopting these forms. If you could change to this, that would be even better, but we do approve the Techmatrix support, Jake and Sport. Okay. Yeah. I recommend using the LF pattern. Yeah, does it capture it well, Alex? Yep, looks good. Thank you. Okay. Then we go to Websoft nine. Okay. So basically we received this request through Jenkins Government and Sport channels. So basically the original request from them was to confirm whether they need to ask for trademark approval. So basically they reached out to us to confirm and we provided clarification. There is already a hosting query this name. So they open to adjust this name as we read this and hence the request. So the problem with that, that Jenkins on Ubuntu by Websoft nine, it doesn't match existing patterns by Linux Foundation and doesn't really match the precedent. At least, I don't see a trademark which would be clearly referring to the same pattern. Is Jenkins jumpstart by CloudBees a close enough approximation or Jenkins for chosen workshop? I mean, it's not really on. So it's clearly not an exact match. Yes. Yeah. Firstly, these ones here, the trademark usage names, but they're not product names. They're not distributions. They're just workshops and whatever. Yeah, basically they ask permission for product Jenkins on Ubuntu. We have Jenkins on Ubuntu to basically provide official distribution for Ubuntu. What they actually do is provide AWS market place entry where you can get it running. So for me, it's not only, so it's potentially causes confusion. And secondly, it doesn't really represent what they do. So is this what they are asking for right here? How it would appear here? Are they asking to update this to say Jenkins on Ubuntu by as the whole thing at the top? I guess this is one of the options because what we request from other vendors that a trademark must be used as a full name always. Well, the reason I'm asking, so if you go back to the AWS market place thing, right? Yep. So you say Jenkins on Ubuntu by Websoft here. Right. Is that what they're wanting or are they just wanting how it appears here? Because here I think it's confusing, right? Because it just says Jenkins on Ubuntu and it's not like, you know, is this the official image? Is it not the official image? Who's Websoft 9? But if it's, if they change the title, the full title to be Jenkins on Ubuntu by Websoft 9, I think that would differentiate it from being like an official Jenkins on Ubuntu from the Jenkins progress. So that's my question is, is where are they, you know, is that going to be updated or not? I guess it has to be updated because for me, you know, we would vote just for Jenkins on Ubuntu. Jenkins on Ubuntu by Websoft 9. Yeah, I agree with you, Alex, that in this case it provides enough to differentiate at least from our side point of view. Again, it's not our problem whether they conduct canonical to get approval for Ubuntu, etc. Right. It's their job. So yeah, we can request the full name to be used everywhere. So on the approved trademark usage from Linux Foundation, I thought I had seen something where it had the on nomenclature, but maybe I don't know what it was for use with. Yeah, none of these trademarks actually qualifies. So yeah, it could be, let's say, Websoft 9 distribution for Jenkins, which would clarify or Web9 AWS package for Jenkins or whatever these ones will define, but there is no trademark where Jenkins will go to the front. Right. So we don't have a precedent on this one and it doesn't follow the Linux Foundation. So what would be your preference, Alex? So I would say them moving their name first, like is kind of the pattern in the Linux Foundation. So Websoft 9, Jenkins on Ubuntu or something similar. So basically requiring them to follow the Linux Foundation. Yeah. So for adopting those guidelines, are we, now that we've plus one, we're basically now going to apply those going forward, correct? Why not? So we still need to document that. But yeah, I guess it's perfectly fine if we apply it to all the requests we discuss. Yeah, I would say currently a negative one for their current proposal from me based on the Linux Foundation examples. And yeah, so I don't know if we want to come back with suggestions for them or if we just point them to that page and say, please look at these examples and give us another proposal. Okay. Because there is no precedent for that for that pattern. Okay. So would we accept if they were to, or is there one of the existing patterns that might fit more closely than something that complies with Linux Foundation guidelines? You mean one of the patterns we have here? Exactly. Yeah. That would still fit in a cloud. I didn't see any of those patterns that I thought, oh, I could understand how I might use that. So it was like a Linux Foundation. Jenkins distribution for AWS. Is there, so like on Azure and AWS, there are other Jenkins images. What are those patterns? You mean on the AWS market, please? Yeah. Yes, that is quite a lot actually. And yes, you mean this, not all of them follow all the trademark guidelines. Jenkins... Like certified by Bitnami and... Yeah, you can start from here. Jenkins on Ubuntu, Jenkins on Windows Server 2016, Jenkins with CentOS, Jenkins container for the Vine 2s, Jenkins on Ubuntu. So I mean... Yeah. If you want to be... None of those people have... Yeah, exactly. Yeah, none of those people have requested a self-license. So it is, so I think we should show our appreciation for Web... What are there? Web Logic 9, whatever, for actually requesting this self-license. That's very, not nice, but thumbs up to them, right? So at least they are doing that. So I think we don't have to bend over backwards for them, but we can try to help them out with suggestions or something like that. So maybe we maybe that's how we do it. Yeah, that's for sure. There's a ton of images on there. Well, the Linux Foundation has a logo usage guidelines. Actually, it's a good question of what would happen with Jenkins logos after that. But yeah, our logo isn't trademarked from what I know. And our logo is on the Creative Core ones. So it's not a concern for me, I mean, if I see both future. But yeah, cleaning up these things. There are lots of pages there. I have more important things to do. Yeah, yeah. So I mean, so there is some precedent that we haven't, you know, contacted these companies either, right, with their usage of the trademark. So I'm kind of now backpedaling a little bit on my minus one. Yeah, that's fine. Not that it's okay for those other companies to have done that necessarily, but there is a precedent out there. And this company is the only one who's actually contacted us about it. Yeah. So it's no longer minus one. Is it minus data? Yeah, I would say that. I think because there's a bunch of stuff out there already, and we haven't gone and contacted those companies about the trademark, I think we need to be a little bit more lenient. I think going, you know, now that we know this, we either have to go and contact these companies and say, Hey, we have a procedure for requesting to use the Jenkins trademark, you know, and things like that. And but I don't know, that's a lot of work. I don't know if we want to do or not. Well, that's a lot of work, of course, there is a nuclear tactics reaching out to AWS and raising a trademark dispute on the search base. I'm not sure how it goes and to be honest, I don't think it's appropriate. Yeah, I agree. Yeah, because we want more people using Jenkins, right? So we also have to protect the trademark so that there's not a, you know, someone provides a container that totally screws up everything and then someone gets a bad image of Jenkins. So we just have to be careful about both of those things, right? Yeah, I will say I'm a minus zero or plus zero. That's very helpful, I know. Well, I don't have sensors. But yeah, I'm sure. So I also don't have strong minus one about that a bit for sure. If it was Jenkins on Ubuntu by Websoft 9, yeah, I think it would be also okay for me. Will you Mark, what do you think? I'm okay actually with Jenkins on Ubuntu by Websoft 9 for this request. I think I'm plus one for it because they asked. Now, as a general pattern, we know, I think we have already agreed we want to go to Linux guidelines. But for this, they asked, I have no objections to granting it so long as they use the full phrase. I agree with Oleg that Jenkins on Ubuntu as listed there leaves me uncomfortable, just like Jenkins with CentOS 7. It's not clear to me who's providing it in the title. It's not clear to me. I also don't know.  It's surprising for Windows Server 2019. Yeah, that's what I mentioned. It's T2 Medium. So can you go back one? So there's also, one more, sorry. There's also this, what supported images? Is that an Amazon, that Jenkins on Ubuntu 1804? I guess it's a company. Oh, it is a company? Okay. Okay. So they had a similar thing Jenkins on Ubuntu 1804. Yeah, I'm not sure how many people are in this company, but anyway. So, well, again, it's probably a valid use case on Austin phone. Again, any vendors are welcome to provide their packaging. And the trademark is what we need to secure. Yeah, so like those Jenkins container powered by Intus, I think that's fine usage. Yeah, because, yeah, it's not a Linux foundation trademark, but I wouldn't have concern about that. So as long as there is clear differentiation in the name, or like Jenkins powered by class method, yeah, okay. Jenkins don't get container. No, it's not a case. Right. So it looks like they also have the Amazon as well for Websoft 9, that Jenkins on Amazon Linux. Yeah, we can go far. For example, we can discuss what Microsoft requested the trademark approval for the official images on Asia, but yeah. So anyway, it's something you can figure out as we go. Yeah, I'm not really sure we are ready to invest in cleaning up this mess. Those some images should be just removed because of security concerns. There is, they just treat clear risk to users. Yeah, I'm not sure what's AWS policy on that. I'm definitely not ready to spend time working with vendors directly. Yeah, I'm on plus one now. You guys have convinced me. It's like that movie 12 Angry Men, right? Yeah. But only if there is the company name as last thing. Yes. Yes. We are likely to approve it. Going forward, we can document it. Okay. Sounds good. Yeah, I guess so. And I still have an extra item to create a new trademark page on Jenkins.io. So Mark, since you're interested in doing so, what's your preference?  Given the burden that you carry, I'd be happy to take it on if you don't mind. So I am happy to do it and willing. That way, you can keep focus on other things. It's hard to reject the software. All right. Yeah, I'll submit the pull request to migrate the trademark page to some place. I assume a dedicated page on Jenkins.io is a good thing, just like we have on the Wiki today. Okay. So you have Jenkins.io? No, we don't. So what I would rather recommend. So firstly, having to under the project, because under the project is protected, which basically requires approval from the board. And here we can just introduce a new trademark section. Then we can take the content of this page, maybe a document, some recommendations, basically taking what Linux foundation documents with proper attribution. And yeah, also you have this governance document, which looks much better than it looked one year ago. But yeah, so there is also a trademark here. So this part will need to be either moved to the duplicated. I believe that all content here is perfectly valid at the moment. But most likely, we will need to migrate a trademark, trademark attribution. Yeah, by the way, yeah. So I guess all this content shouldn't be moved, just in hyperlink. Well, and I need to find a way to do redirects of interior content anyway for another purpose. So this is a great excuse to be sure I can do that here as well. Excellent. Thank you. Okay. Thanks for taking that. Any other comments about this topic? Move it on. One, election status. Yeah, I hope it won't take other 40 minutes. So yeah, the deadline for board and officer eliminations is tomorrow. We've got some eliminations. And most likely we will also have eliminations coming to the last moment, like it happened one year ago. But still we encourage all contributors, including current officers and current board members to submit their eliminations so that we have a diverse list of candidates. Wish we could kind of come from all these candidates and then have a lot of nominees published, but let's see. So we got nominations for overalls. So it's not like we on fire having no nominations somewhere. Minionations still need to be confirmed, but it looks that they are more or less set. Yeah, more nominations would be still good. One problematic topic for us right now is number of voting registrations, because we are quite low there. And since we don't have any announcement, so if you're not subscribed to the Jenkins developer, you may miss notifications. I'm actually thinking about asking the infrastructure team to dump a list of maintainers and at least limited distribution, reminding contributors to register for the actions. Have we done anything on social media as well? Yeah, but still contribution registrations are quite low. Yeah, it's like 20 or something, right? Yeah, one of the reasons is that yeah, firstly it's almost half a month until the deadline. And again, Spike usually comes a few days before the design. But yeah, I would rather start pushing Petrolia. So Mark, what do you think? Is it feasible to get a dump of maintainers, etc., and do distribution through SendGrid? I think so. Olivia certainly did a distribution through SendGrid last year using the entire LDAP database, a subset that our maintainers, where would we ask that? Is that a question we would ask of GitHub through the GitHub APIs to identify maintainers? We have repository permission on data. We have tools to dump lists of maintainers from there. And we can query LDAP to retrieve emails if you have proper access. Right, so given a GitHub ID, we can ask our LDAP for the email address associated with that ID and we can notify that. We do not even need a GitHub ID because we store artifacted IDs. Right, we need their Jenkins login name. Well, no, the Jenkins login name is basically well known. Okay, so there are all those concerns about that because we will be basically identifying a subset of our users. One may argue that identifying through main cases is also identifying a subset of users because not everyone watches them. Sure. Yeah, I'm just thinking about it as an option. We can also do mass distribution, but yeah, I'm sure we want to do that this last time. Yeah, I'm not in favor of the mass distribution again. I think last year's experience was not good enough for us to say let's do mass distribution again, but using the maintainer, generating a list of maintainers seems reasonable. Would you like me to discuss with Olivier and the infrastructure team to see their assessment of it? Yeah, if it's possible, I would appreciate that. Okay. Yeah, we can also do another push through social media because one thing I discovered last week, even if you had a jump-atron here for elections, this jump-atron was broken because URL was incorrect and it was pointing to 404. I have fixed it just one week ago or so. Okay. Well, and the fact that we heard no reports that it was 404 is a bad sign, right? That made me know an attempt to even click it. So ouch. Yeah, right. So basically, I could just fix that a while ago. We can also remove CD-Con and I guess it's no longer relevant. So we could adjust the first jump-atron to open, but yes, I'm open to other suggestions how we could boost the registrations. Is this one of those where we could ask for a list of help to do some community marketing, some things that might help us get the word out in different ways? It would be nice. So I will remove CD-Con and jump-atron. Later, you may just put another CD-Con and jump-atron. But for now, I think it's fine. Alex, will there be any of those? I've never had to deal with an election like this before. So I'm not sure I have any good ideas, but I will definitely think about it. Okay. So we still have some time. Maybe we could ask for street promotion to selections. I'll publish it in the beginning of November. Good timing, yeah. We shouldn't do it. Okay. Yeah. So let's reconvene next week and see where we stand. I think that one of the action items which we need to handle anyway is creating an email announcement mailing list, but just for announcements, low traffic one. So similarly, how to order projects too. So basically it's subscription mailing list where we announce major news, conferences, events like let's say October first, but here is really limited traffic. It won't help us with these elections, but I think that in general it would be nice to have it in the coming income. I think it's a good idea. Income stash announced, yeah, something like that. Yeah. I can take the section item because I was doing it for other projects already. So while it's actually quite easy, the difficult part is to get people subscribed not to having this mailing list again. So I will handle that. I'll do it in official definitions. You should be moving to this topic. Just have several minutes left. Yeah, I think so. Okay. So I have finally pushed a full request which summarizes what was proposed in the mailing list. So basically shifting officer role descriptions more towards cartoonating the things, the reading the teams, not doing everything on their own. Actually, yeah, it was implied expectation for a long time before when we started CX working groups. But the documentation was quite different. So I started the work and quit a bit. Your current state looks like that. So I did some documentation and you can see that the page from Jenkins team leads to team leads and officers. We is assumption that there are two types of roles. Team leads are basically roles appointed by the Jenkins governance meeting leading particular teams. Let's say hosting team like we introduced last summer, etc. And the Jenkins officer is an elected role. So the distinction basically a point from the process, but in principle it also the same is reverse to responsibilities. There are common responsibilities of the work inside the teams and CX that I lead and reporting new contributors, knowledge sharing and share officer rotation. Yeah, wording probably needs to be changed. I just wanted to put it explicitly to highlight that it's not only onboarding new contributors but also implementing a ladder within the team so that contributors could basically adopt other roles and eventually be able to take the key roles in the community. Then facilitating initiatives, maintaining the teams roadmap, ensuring the initiatives are reflected on the public Jenkins roadmap and representing the Jenkins community within their responsibility. It's also something new before that basically the Jenkins board was responsible for representing the project. Well, I think that we should try to assert the de facto state when officers represent the project. For example, Olivier Tolle talks to dozens of vendors handling infrastructure, Daniel handles security contacts. I'm also, yeah, other officers also do such communications here and there. Yeah, basically many contributors sat on behalf of the project, but I see no reason why team needs and officers shouldn't do that. So that's why I put this item and then common responsibilities. This one probably still needs, it still needs to be polished to more focus on continuing the work and leading the work. But yeah, some working changes have been over the applied and the event officer definition has been completely written. As we discussed in the last meeting, this is plus one for the current description. Okay, so I'm not sure whether we are ready to vote for that today, but it would be nice to vote for that next week so that officer terms are finalized when we announce the nominations. Sounds good, I'm good with that. So I would ask everyone to just review the list and if you see any other improvements which we could do or changes we need to make, please highlight that. Again, this document is not something which we need to finalize for one year, we can really improve it after the elections, but I think it would be important to update these expectations before the cycle happens. Sounds good, thank you for doing this update. Well, there is a lot of typos also, I will fix that. Okay, so yeah, needs to be used. Okay, anything on role definitions? So, ProLink it on October 21. Any other topics or just next meeting taking the time? Nope, not for me. So yeah, my proposal would be to have for the next meeting next week. Yeah, I know that the schedule was a bit chaotic already, but actually next week would return us to the normal schedule. Plus it will be LCS baseline selection, so I think it would be important. Sounds good to me. Okay, also an open question about the timing because I'm not sure whether you want to keep this time for governance meetings. I'm not sure how forward you for me this is a bit late, and many other contributors from Europe expressed concern that it's too late. And at the same time it's not too late so that the Asian and Pacific region can participate. I'm fine with moving it up if that would be helpful to you and Uli for sure. Me as well, earlier in the day is better for me. Whatever we do, I suggest to make it effective only in November after summer time or winter time changes are over. But yeah, it would be nice to do whatever and agree on times. And maybe we should wait for the election because different people come in and... Yeah, fair point. They have other ideas. It's totally fair because we have five officers and both members for rotation. So yeah, I agree with you then after elections. I'm good with that. That's it. So thanks everyone, especially for productive discussion about the trademarks. So we have a clear pass there. Let's keep working on the elections and other topics. Thanks everyone. Thank you. Bye.


Did this happen to you that you apply for thousands of jobs online, and you might get one or two interviews, and then you start to doubt yourself. Maybe your capabilities wasn't good, maybe your resume wasn't good, and you start to feel like life is tough. And then you start bills to pay, you need to get a job as soon as possible, but it's a black hole of applying for jobs online, throwing hundreds and thousands of applications and get no return. And this is a very stressful situation. When I applied for jobs in the last 2008 recessions, and I felt the exact same way, I actually hurt myself. I tripped myself and ended up going to interviews on crashes. Yes, I left my mind to cover myself, just felt very depressed, just because of very limited opportunities out there. But after I personally went through two recessions, I have a conflict in that we have invented a new strategy for you to land more interview opportunities much faster, with much higher success rate, and land much higher paying jobs as well. So that's what I said, when resume is dead, you need to use a part of portfolio as a new strategy. Make sure to stay until the end of this video, where I share with you free job referrals to TikTok and Uber, and then all those companies who are actually hiring with free referrals. This is Dr. Nancy Lee, a director product and featured in Forbes. I've helped 100 people land their dream P.A. job offer in fan companies, a unique from startup, and continue to get promoted as a product leader. If you're interested in product management course, we go to PMExcelerator.io for more. To learn the most effective way to become a product manager, you subscribe to the channel, hit the bell button to be notified every time, and turn on your video every Wednesday. If you like any free tips we provide today, or land more interviews just because you watch this video, make sure to smash like button, because this is the only way YouTube algorithm will recognize me. First of all, let's understand why resume is dead, and why you're not getting interviews at all. First of all, for fact, do you know that only 3% of the resumes in the ATS systems are being viewed by heavy managers? That explains the reasons why you apply for jobs online, and it's like throwing your resumes into a black hole and get burned. And the chance of you actually landing an interview by applying for jobs online is only 1%. And for most of you guys, you don't even hit the 1% success rate. Let me break it down regarding what happened and why you are getting less than 1% success rate. And first of all, shocking news. According to Wall Street Journal, about half of the ATS job openings are fake. They are not there to hire you, they are there to provide branding for the companies. Based on this article from Wall Street Journal, they interviewed over 1000 heavy managers, and guess what? 27% of them have a job opening longer than 4 months because they just want to increase the reputation of the companies to show that the company is still growing. In reality, they don't plan to hire anybody at all. And according to Clear Capital's report, that 50% of the heavy manager keeps their job openings open because they're always open to new people, new opportunities. This made me even more mad. And one third of the heavy managers said the following, that who said they tried to advertise the jobs they weren't trying to fill, but they keep the job listing up to placate the overworked employees. This is mind-boggling. What this means is that they work the employee to death and they want to make them less angry by showing that see we're hiring more people to join your company if you don't work well, we're gonna hire someone else to replace you. So please continue work hard. And they also showing that see we're still trying to hire more people, which takes us a while to hire the right people. So your overwork right now, it's okay, we're trying to solve the problems. But one third of them intentionally not trying to solve those problems. This just made me really sad. This is a very bad ethic for any heavy managers out there. That explains why you do not get any interview opportunities. That's also why your resume doesn't work anymore. Another reason that makes them want to do those fake job openings is that all HRs want to keep their job. So they pretend they're very busy posting fake job openings so that they're not going to get laid off easily. This is so bizarre, just so wrong. However, there is a bright side and the market is actually warming up. Based on the VP apart from Google, he mentioned that lots of companies started gradually hiring more people. And we have alumni working for Amazon have confirmed that Amazon start to open up more essential positions start hiring again. And in April, we also have seen recruiters from Google reach out to our students saying that hey, we start hiring again and let's get ready to schedule the next round of interview. Yes. And companies are starting forming up. So I want you guys feel like there's light towards the end of this tunnel. Now here's another market trend for non tech companies. And we have seen what laid off on during maternity leave. When she got back to land a job in April, 2023, she learned even higher paying job and was a better culture of the company. And actually there are more opportunities. So I want to get really low later folks on using the right methodology to land your next job. So therefore, if you still want to use the same methodology of applying for jobs online, and you have to rewrite your resume in a new way, your resume should highlight your achievement and your roles responsibilities, because you need to stand out from the competition to show other that you have a better experience compared with other candidates. And the second part of resume should be keywords focus because all the AKS system trying to search specific keywords to pick you from the entire thousands of resumes database to show that you actually have a higher percentage of likely to be matched with this job. And then your resume will be reviewed. If you don't know what type of keywords to be put on your resume, you definitely check out this video where I break down 15 different keywords in highlight on your resume. Definitely going to put this video in the description of this video and make sure to download the key to partner manager resume template that have been used by 9000 partner managers that is going to immediately increase your success rate getting picked by the systems. I'm also going to link the resume template in the description of this video. Now, given the resume is that the likelihood for you to actually get it picked and reviewed by the systems only 3% usually use a very different strategy, which is part of portfolio strategy. This is a brand new concept for most of you guys. So let me describe to you what is a product portfolio. Number one thing product portfolio is a collection of past product you have done in the past to demonstrate that you have end to end product management life cycle skills and experience. And you should also use the product portfolio to highlight your achievement because as we all know each job openings have hundreds of thousands applicants already. You need to show that you are better than others. So therefore it's a better way to show your achievements through a product portfolio with different kind of MVP graphic design or PR articles about your past product. And third product portfolio is also the best proof that you are the best candidate because lots of people like to bluff on the resumes and showing all the high achievers and number like 20% revenue growth. But how would you prove you actually did it product portfolio is best way to demonstrate and prove you have done exactly what you said on the resume. So product portfolio is very impactful not only help you to get interviewed but also lend you a job offer. And there are three types of product portfolio and you should use different portfolio based on different kind of purposes. For example officer and Amy she learned a job from tiktok as a product manager and getting paid significantly higher salary. That's even higher than people currently working for Google right now. This nuts. But how she used product portfolio is demonstrate that even in her past experience was being a CPA and accounting background working on B2B accounting software to be friend very boring. But she want to join a very exciting company like tiktok work on creator economy as B2C cyber business. But how she was able to bridge the gap is by creating a product portfolio to demonstrate her knowledge and experience in the B2C side even if she never worked directly on B2C product in the past. And she does another type of product portfolio which is based on people with no experience at all. For example our student youthy she had no PM experience but she was able to use her product portfolio to land a PM position. And now she's in the process getting promoted as a product manager within her company because she was able to demonstrate her great skills using her product portfolio. Now if you are the hiring manager answer this question who would you select? Would you select someone for interview for someone who just submit a resume or would you select someone who submitted a resume that was reviewed by document cd and also submit a product portfolio which has long pages of examples of their past achievements and which one would you select for an interview? Of course the second one. Now once you have your product portfolio it's also going to help you significantly during the interview. During the interview it's extremely likely the hiring manager is going to discuss the product portfolio with you saying hey I'm very impressed by the product portfolio you have done and let's talk about how you do it and this will turn into interview questions. Now this is also going to help you significantly advance yourself to compete with other candidates because no other candidate in the same interview had a product portfolio that I can talk about I can demonstrate I can do a presentation about. So definitely this is a new way for you to land more job interviews. Of course if you want to know in details regarding how should you build your product portfolio I have a separate video where I teach you five free tools to create your own customized product portfolio that's going to lend you job offer much faster with also with screenshot of the examples of how you're able to create product portfolio just like I might ask the students as well. I'm going to put this video in the description of this video make sure to check it out. Another strategy 10 times your chance of lending the next job interviews is by getting a referral and I also understand during those crazy recessions and layoffs that lots of people do not even know which company are really hiring but guess what we have B2B side up recruiting agency we're actually recruiting on the other Uber and TikTok those kind of amazing companies and we decide to open up all of our referral network for free so you can go to this website and check out different kind of referral opportunities we have and directly submit your application we're going to pass your resume to the hiring manager and I'm also going to link the website in the description of this video. All I want from you guys is comment below what you learned a job offer or you need more referrals I would like to hear from you guys and also make sure to like comment subscribe to the channel and share this video with any aspiring front managers. Make sure to watch the playlist of front manager interview simple questions and answers and use them to prepare your next round of interview. I wish all of you guys good luck. This is Dr. Nancy Lee. I'm going to see you in my next video.


Hello folks, Jen here with opensource.com bringing you another top five of the week. At number five, Seth Kenlon, our columnist on video editing, writes this how-to guide to help you get started using Natron, an open source composition tool. At number four, Ricky Inslee, the community manager at opensource.com chats with Deb Nicholson about how to say no to your boss like a boss. In this interview, she talks to her prior to her Oskan talk on the subject, so they talk about delegating and politely rejecting offers for additional work. At number three, Patrice Verlet takes a look at Docker for both developers and sysadmins, and where Docker may be headed in the future as competition emerges. At number two, an interview with Bruce Echoll, the author of Thinking in Java, Thinking in C++, and a number of other books on computer programming. Bruce is currently trying to find a new way to organize companies so that working together is a joy. He'll speak on the topic at Oskan next week. And finally, at number one, a look at what's on the horizon for LibreOffice. Don Watkins returns to using a Linux desktop as his primary system, and so begins using LibreOffice after being an open office user for almost 10 years. Happy with the change, he reached out to a founder of the Document Foundation and interviews him about what's new for LibreOffice. Thanks so much for joining us for the top five this week, and I hope to see you next time.


Mr. Speaker, perhaps the greatest challenge Israel and the United States face at this time together is the Iranian nuclear program. Let there be no doubt, Iran does not strive to attend nuclear energy for peaceful purposes.


Hello everybody, E here. Welcome back to another movie review. Today we are talking about old from M Night Shyamalan. I just not going to be a positive review at all so if you like the movie you might want to click away because I'm going to tear it apart. Also you need to expect spoilers throughout. I'll put up a spoiler card because the whole video is going to be a spoiler for the movie and all of it's relevant plot points. So if you haven't watched the movie and you want to watch it yourself definitely click away and you know watch it and form your own opinion but anyway we're just going to jump right into it. Old is about a group of people who are who receive a free vacation to this island setting and they are given a special outing to a secluded beach surrounded by rocks that you have to go through this I don't know this this crack in the rocks to get to it this trail and then once you get out there everybody starts aging. If you've seen the trailer you pretty much seen the movie other than of course the absolutely asinine twist ending. One thing I will mention and we're going to start spoilers right now so for those of you that who want the TLDW I absolutely hated this movie. I think it is Shyamalan's worst movie since Avatar. I am not an Avatar fan and even I hated the movie so but I didn't hate it because it was a bad adaptation of the source material. I hated it because it was terrible. This one I think is far far worse. The last I think the last Shyamalan movie I liked was The Village and only only so much did I enjoy The Village but I did like the the the creatures. Anyhoo so this group of people go out and they're all all these characters are absolutely one note you have the rapper you have like the Instagram model trophy wife character you have a doctor you have a nurse you have a lady who seems like her whole character development is she has epilepsy then you have a husband and wife who are on the rocks and their two kids the doctor and the model trophy wife they have a daughter also which which came to one of the most awkward not really sex scenes but one of the most awkward connotations I've ever come across. Let's go ahead and talk about that up front so the kids of course they age quickly the adults can't tell that they're aging because they're already older and the two I think six year olds end up having mentally six years old end up having sex and I know that he tried to explain this away by saying all their thoughts and everything were either is you know they were growing up mentally but yet they still acted like six year olds so I'm very confused about that all of their reactions were six year six year old reactions um but let's let's go ahead and and talk about all of the issues with the plot I am shocked beyond the pale that this movie got funding that someone read this script and said yes we want to make this movie um so here's the the hefty part of the spoilers um why don't the women have constant periods um it's they should be having one I didn't do the math they did it in the movie about how long every minute or hour was but they should have been having periods basically just bleeding constantly throughout the film because of the way the the biology works on this beach the way it speeds up the the body and you go through all of your growing cycles you go through all that stuff um why why why weren't they constantly having periods why wasn't that touched on I I don't know it could have been as easy as you know I guess passing out pads I I don't know but that was the first thing that I noticed the second thing is why didn't everybody have to eat every single minute why didn't they just blow through their food right off the bat um and to back this up the baby who who dies a minute after it's born that's from the coupling of the the two six year olds um it died because it didn't get the nourishment and care that it needed so why didn't everybody else just shrivel up and die damn near automatically there there's no explanation now there is an explanation um if I I'm just assuming here uh why the food didn't rot automatically and I feel that that explanation is because it was in the metal packaging because they talk about if they were put if they put themselves in a metal tube to get rid of the magnetization or whatever it is it causes them to grow old that they would have been fine um they even use this premise uh the two the uh the the brother and sister use this premise to uh to escape the the beach so I that's that's one plot hole that I've seen mentioned that I think has an explanation why didn't the food rot because it was in the foil packaging um the next thing and this one really really bothered me is how was the doctor able to kill the rapper also the rapper's name is mid-sized sedan moving on um so he he just he stabs him repeatedly but it was set up very early on that is soon and like when they remove the tumor from the woman as soon as they cut it heals automatically because you know it's it's going over such a period of time so why was the doctor able to stab the rapper to death I have I have no clue and since they didn't show the injuries that he sustained but even like a puncture to the heart would have would have healed automatically I mean it's even when they're doing the uh the tumor removal the guys are saying as they're holding open the wound that it's closing over their fingers also why didn't it just seal around their fingers I don't know um it just it keeps it keeps going like that there's so much to this movie so it's not even like keeping it a mystery it's not a mystery it's just bad writing it's bad storytelling um let's see here so the why didn't they need to eat um why weren't the women's having women's the women having constant periods why uh why was the doctor able to kill the rapper when everyone else healed automatically it was it wasn't a thing like cut and then you know wait it was cut and it automatically started to heal itself this movie is fucking terrible I don't once again I don't understand how it got made there's some green screen effects toward the end right at the end when they're showing the how the brother and sister escaped the beach that uh I I mean it's bad it's like ps2 bad kind of graphics uh where they're floating in the water and you see see the background it was absolutely terrible and then you have and I didn't even catch this one my buddy Josh did um how M. Night Shyamalan is over watching is watching sorry watching over all of them like the uh like the egotistical director he's the man on the mountain watching everything unfold um I thought that was a good point this movie is just utter crap and I don't want to sit here too much longer and talk about it but I was irrationally angry at this movie um Dan tried to tell me Dan tried to warn me and I was like I like to watch things for myself and we just sat there the entire movie talking about the horrendous acting that's another thing the dialogue is terrible the way the dialogue is read is terrible the reactions of the actors are terrible and this goes well beyond like that seen from the happening that everybody means uh with Mark Wahlberg uh if you if you've seen it you've seen it um I'm not going to recreate it here but it's it's it's bad the the acting is bad and these are good actors like Rufus Sewell I enjoy Rufus Sewell in everything but he was so over the top and unbelievable in this one it this is it's it's bad and I don't want to keep on harping on it so I guess I'm going to end it here this is the easily the worst M. Night Shyamalan movie so believe everything you've heard about the film um I I tell everybody to watch or read things for themselves but this time I really cannot recommend this to anyone whatsoever yet there are people who love the movie I don't know how but that's that's their own opinion and I'm completely fine with that if they're able to shut off their brain and just enjoy it for popcorn cinema I I'm fine with that because you know I enjoy the dark tower movie not as a dark tower adaptation but just as a popcorn flick I enjoy I enjoyed it um but anyways have you seen the tragedy that is old uh let me know down there in the doobly-doo whether or not you loved it you hated it you felt mad about it but if you felt any of those things explain to me in detail also if you would like to explain any of the points that I make uh why you think that these things were not plot holes please do so down there in the doobly-doo but until next time I have been E you've been you this has been another movie review I'll talk to you guys later bye bye


DK Audio presents 13 and a half incredible things you need to know about everything, read by Alex Wingfield. What will you hear? Find out things you never knew you needed to know in this catalogue of curiosities. From bees to blood. Money to mummies. Each entry offers up 13 and a half incredible facts. Keep listening to hear where you'll go next. How did Earth? Earth came into being about 4.6 billion years ago. This huge spinning ball of rock and metal is not as rigid as it seems. The surface of our planet is constantly changing as continents collide, mountains rise up and oceans widen. 1. The ground may feel firm beneath your feet, but Earth's rigid outer layer, the crust, is only a few kilometres thick in places. This rocky surface makes up just 1% of Earth's total volume. 2. The crust is broken into pieces called tectonic plates, which fit together like a giant jigsaw puzzle. However, unlike jigsaw pieces, these plates are constantly on the move, shifting around and crashing into each other. 3. Earth's largest layer, the mantle, is about 2,900 kilometres, 1,800 miles thick. The tectonic plates float on the mantle, which is made of solid rock but flows very slowly due to the extreme temperature and pressure. 4. Wrapped around the centre of our planet, the outer core is a liquid layer of iron and nickel. These swirling metals create Earth's magnetic field. 5. Tectonic plates all move at different rates, and the Nazca plate, the plate to the west of South America, is the fastest. Every year it moves approximately 8 centimetres, 3 inches, about half as fast as hair grows. 6. Earthquakes and volcanoes often happen along plate boundaries. One such hotspot is the East African Rift, where the African plate is slowly splitting in two. Eventually, a new ocean will fill the ever-widening gap. 7. Earth's continents were once joined together in a single landmass known as Pangaea. Scientists predict that in about 250 million years, the continents will merge once more. 8. Every other planet in our solar system is named after a Greek or Roman god, except ours. The word Earth comes from the Anglo-Saxon word eida, which means ground or soil, and is thought to be 1,000 years old. 9. The inner core is made mostly of iron. At 5,000 to 6,000 degrees Celsius, 9,000 to 10,800 degrees Fahrenheit, it's about as scorching as the sun. There is so much pressure at the centre of Earth that, despite the heat, the inner core is solid. 10. If you could dig a tunnel through Earth from one side to the other, it would be 12,756 kilometres, 7,926 miles long. In reality, the deepest tunnel ever dug, the Kola Superdeep borehole in Russia, barely scratches the surface at 12 kilometres, 7.5 miles deep. 11. Mountains are formed along the boundaries of tectonic plates. The longest mountain range of all, the Mid-Atlantic Ridge, is hidden deep in the ocean. It was formed by plates pulling apart, causing hot magma to erupt from the mantle and mould into stiff peaks. 12. Forget sun and sand, the world's biggest desert. Sample complete. Ready to continue?


We have previously mentioned how it's best to start each sentence with words instead of mathematical symbols It's even better to start each clause in a sentence with words instead of symbols If one does not then you can end up getting a clause that ends with like a mathematical Expression, but then it's separated by a comma Then if you start the next clause with a mathematical expression or symbols of some kind it can kind of get Congested and kind of clumpy and it becomes less clear because as things as the mathematical symbols blur together It can very much confuse the reader So to strengthen the principle be introduced earlier We're actually going to follow the convention that we should separate all mathematical symbols and expressions with words So when you look at the sentence because x squared minus one equals zero x equals one or x equals negative one Well, you could say that we really should add some like English some words there to kind of spread it out and make it easier to digest for the reader So instead we could say something like because x squared minus one equals zero. It follows that x equals one or x equals negative one just that extra little bit of words just helps with the clarity so much You can say something like it follows that or we have or it is seen There's a lot of things you could say put your own style, but put something to just separate the math Just to make it more digestible for the reader Another example unlike a union B a intersect B equals the empty set Without the extra English it can be somewhat confusing or like okay because oftentimes when we're writing like mathematics We sometimes only put commas between mathematical symbols. We don't even put the word and so it's like is this is this suggesting like Unlike both of these things like the break putting some words in there can help with a lot with that So it would be better to write something like unlike a union B the set a intersect B Equals the empty set that can improve your your writing dramatic is just following that simple Writing tip that we saw in this video now that brings us to the end of lecture 18 Thanks for watching if you learned or liked anything in these videos Please hit the like button Subscribe to the channel to see more videos like this in the future Share these videos with friends or colleagues so they can benefit from them too And if you have any questions feel free to post them in the comments below and I will answer them as soon as I can