all of our new members. In case you didn't know or got lost, this is the Marketing Committee meeting. This is our last one of the year, as we said at the beginning. So we'll see you all next year after this. Here's the conference info, but you all have it if you made it here. Also, in case you didn't hear the thing from Zoom, this call will be recorded. So if you don't want to be recorded, please don't say anything and stay off the camera. We're recording it so that you can see it in case you missed the meeting one month. You can also find all the slide decks and all the recordings on YouTube and in the committee folder too. Our next one is going to be Wednesday, January 5th. I hope to see you in the new year with like new resolutions, hopefully still not recovering from New Year's Eve, staying up too late. Yeah. And just a reminder, this is a Linux Foundation meeting and it's involving industry competitors. Please don't do anything in antitrust because this is the Marketing Committee meeting and we don't want this to be the legal committee meeting. Yeah. So don't break him and trust laws. With that, we have the same agenda as always and let's jump into it. So our first one is the announcements. So we do have a Marketing Committee and member survey open now through December 10th. We use this as an opportunity to get feedback from you as a committee and you as our members to see how we can improve our programs going into next year. So if there's something that you really love, we'd love to hear about it and see what worked well for you. If there's something you'd like improving, please also tell us that we can make the community better for you. And finally, if there's something new that you'd want to see, we'd love to hear that too. We're always, we like to be a community and like member driven organization. I think most of our best ideas have come from the community. So please provide your feedback in the survey. The next one is the nomination for the 2022 Marketing Committee Chair has been extended. And Lexi, I don't know, I think you said you wanted to add a couple things here. So yeah. Yeah. Well, I think you guys kind of covered it. It is a great opportunity for like market for networking and just to help to shape the meetings. But it's also just helpful to kind of help other people navigate through the ecosystem. And I know it's kind of intimidating to take this on. I know everybody kind of has a hefty workload in their daily jobs. But I just want to say that Bill and Christie have made it such a pleasure, and they really make it easy to take part of this. And it is a perfect chance to really help have an impact on our community. So please don't hesitate to reach out to me. I'm sorry, privately, I'm sorry, I'm a little sick right now. If you have any questions about the role and yeah, good luck to all the candidates. Thank you, Lexi. It's been a pleasure working with you this year. And I'm excited to get to see who we work with next year. So a little bit sad that you won't be our chair again. So it's all right. We could still be friends, Bill. A happy, sad cry. Cool. Moving on to other announcements. In case you missed the blog post, CNCF is going to be transitioning. Well, we have been transitioning off the Meetup platform for quite some time onto the Cognitive Community Groups platform. It's now finally, finally going to be official. The CNCF Meetup Pro subscription is going to be ending on December 31. So if you organize a Cognitive Meetup, please make sure you check out the blog post at the FAQ. This will help answer any questions that you have. If you have any more questions about it, please reach out to me. And all these stuff is going to be in the blog post. If you're one of the Meetup members who are switching, we're super happy to host you on the new Cognitive Community Group platform if you haven't switched already. Next thing is we are also end-of-lifeing the Speakers Bureau. We found that there really wasn't that much engagement on the platform. People weren't finding it useful anymore. Emails have been sent out to anyone that still uses the information there. We would strongly encourage you if you're looking for Speakers for your next event to reach out to some of our CNCF ambassadors. They're all around the globe and especially now in the global, in the pandemic times. I'm assuming a lot of people are doing things virtually and the great resources to be found in lots of different time zones around the world. So that's a great resource for finding Speakers. Next one is our KTV updates. This is our special tier of Kubernetes training partners. These are people who have the knowledge, skills, and certifications to help enterprises on their learning journey in cloud native. We now have a searchable web page for you. So thank you to Andrew and Stephanie in our community for driving this work. Like as I said before about the survey, this idea came from Andrew and Stephanie. So this is once again a community-driven initiative. If you want to have your information updated, please submit this form before September 10th. If you don't do that, you'll have to update the information on your own to the landscape, which you can do at any point, but we're just trying to simplify for this. And so to just give you an example of how this works right now, if we go to this KTP page, we can see that there's 58 of them. And then we can now sort by certification, training types, and which country that they're in. So we hope this will be a useful resource for people that are looking for their next training partner. Next one is the online programs calendar is now open for Q1. So I know I haven't set my new year's resolutions yet, but you can already for Q1. You can book in your online program. So strongly encourage you to jump the gun and get started on planning for what you're doing next year. Then finally, we'd like to celebrate a couple of the wins, because we aren't having those meetings on December 24th or December 31st. Sadly, a little sad, happy cry there. We want to celebrate a couple of wins that we've had this year. We had over 4,000 subscribers to Cloud Native TV on Twitch. We hosted our first hybrid QCon, Cloud NativeCon with over 23,000 attendees. We have had over 12 KCDs all around the world with over 7,500 attendees. As my little baby, I'm really proud of that one. Just a happy cry there. We have 12,000 views generated from CNCF online programs, 167 programs hosted, 200K subscribers on the CNCF mailing list, and we published seven case studies and have two new characters in the 50 and friends, Linky and Hazel. So yeah, a couple of the wins. I'd also like to hear about a couple of the wins from the community too. So if you're comfortable, feel free to add a couple things in the comment. What's your biggest highlight of this year? What did you learn from the community? Or if anybody wants to say a couple of words, we have a couple of minutes we can I'd love to hear about what are you celebrating at the end of the year here? Anybody? There's no wins this year? I don't believe it. We did the hybrid events this year. So that's a big one. I mean, for me at least, we survived. Yeah, that's a big one. I was just going to add, it's been a really challenging year going into 2021 not knowing with uncertainties of the pandemic. And then I think, as marketers, it's also been challenging to market events and just figure out what a hybrid looks like and all these things. So I'm glad that we've been able as a community to come together and share some of those best practices and work together on that. But we all survived, which is a huge win in itself, right? It sounds really dark for some reason. Sorry. I know, right? It was challenging, but we did it. And yeah, looking forward to 2022 and seeing what that looks like. Yeah, definitely. Also a couple of things from the chat. I would be very remiss to not mention that FitBee and Friends is now an Italian thanks to Annalisa and the team at Spark Fabric. They're doing a lot of fun stuff there. Peter is saying that he loved being on Cognitive TV Twitch. Blake is saying that KubeCon LA was awesome, definitely the highlight of the year. I think that was probably my highlight of the year, too. Just finally seeing so many awesome members of the community in person, real life. So yeah. Andrew also got to meet his team at KubeCon. So I can say the same. Apparently, I'm taller than everybody thought because everybody on the CNCF team is all about the same height.  Also, I guess anything anyone else want to add or please feel free to keep on posting them in the chat. I'd love to see all the comments about what people love this year. Really appreciate the work on customer stories and customer references. I think that was a real big transition from where we've previously been, where we're very focused on the code and now really telling more stories about how customers are using the code. Yeah, definitely. People love to hear those stories about is this some marketing? Well, this is the marketing committee, but what's the actual use case here? Our customer is actually using this. Yeah, definitely. Also, Caitlin's pointing out the Business Value Committee launched along with the Interactive Cognitive Glossary and Landscape Guide, also awesome additions. I'm just going to take a hot second here and just highlight it in case you haven't seen it yet, just because this is also one of my favorite things. Everybody always is landscape, so overwhelming. What do we even do? How do we understand it? Well, now we have a guide and this is another thing that was driven by members in the community. So big shout out to Catherine and Jason for helping put this together. If you've ever wondered how to go through it, they've written this awesome guide about each section in here too. So highly encourage you to check that out if you've ever wondering how do I figure out how native. So yeah, lots of great ones here. I feel bad. I feel like there's so many that I missed and there's just so much great stuff happening in the community that's almost hard to, it's even hard for me to keep up with it all. So yeah. Well, the KCNA exam, another great one. I have mine scheduled I think for next week. So that's the Kubernetes and Cloud Native Associate exam. Super exciting stuff there too. So with that, I don't want to spend too much time. I just wanted to throw a couple shout outs mentions there. We did I think really well this year and really blown away by everything that the community has done and super excited going into 2022. So with that, we'll move on. Happy cry there about all the great things that happened. KCD Italy, we can go on for days. Okay. So membership, silver members, welcome to all of our new silver members and user supporters and nonprofit members. Also welcome to all the people that said hello at the beginning of this call. It was super nice to meet all the people spread around the world. As you can see, we're a global community. People choose themselves from St. Louis, from Denver, from Paris. Love to see the connections all around the world. New member acquisitions. My data got acquired by Datacor. So the Cloud Native landscape is continuing to consolidate. On the training and certifications side, we have people are always signing up. Yeah, it just keeps on growing. Cloud Native keeps on going. There's about 70,000 people registered for the CKA now. There is over 8,000 registered for the CKS exam. There is 34,000 for the CKAD. Pernonka says let's get to a million by the end of this year. Other than we don't get our bonuses, so please help us out. I'm kidding. But yeah, good goals there. We already have 555 people registered for the KCNA. I know I've seen it all over my social media this week of people that are doing it. I'm really jealous that everybody has a sticker before me. So I'm trying to get that one too. Okay, so with that, I'll head over to Christie for content marketing. Awesome. Yeah, if you want to go to the next slide, we can talk about online programs. Yeah, so as Bill was saying earlier, the calendar is now open for our online programs. And if you're new, our online programs are actually our CNCF webinar programs. So previously, we just hosted live webinars and we were doing a lot of those. And then we realized that we had a couple areas to grow in in terms of expanding our audience into Twitch and also experimenting with live streams, opening it up to on-demand webinars and some other opportunities. So I always say that in this call just because we always have new people. So if you do have questions about what you're eligible for with your membership, this is a member only benefit. And it's a great way to elevate your company as well as talk about the things that you're doing within the community. So I highly recommend either reaching out to our team and actually Libby on our team is here. She's the person who runs this and would be happy to help. But just if you're curious about our programs from November, here are just some stats on views and things like that. So great opportunity to take advantage of and then you can go to the next slide. Wait, I just want to like jump in here, Christie. This is like a TV infomercial. We just got a call in from Libby. She's saying we're already having bookings from like 2022, like slots are going fast, you know, click on the link. Like a telephone, get in there. Exactly. It's all happening. Yeah, that's awesome. I love it. Awesome. And then just a reminder too, as it relates to our blogs and metrics, we did launch this, we should have added this actually into one of the wins. Charlie worked on this. It pulls the real time Google analytics data for all of our CNCF blogs. So if you've ever submitted a blog with us, or if you're curious about kind of what trending topics are really popular, or you just want general stats, this is a great dashboard that you can use the links here in the chat or in the slides and you're welcome to use that. So just a reminder that that's there for you. That was a big ask that we got from our community from last year's member survey. And then you can go to the next slide and I will actually kick it to Charlie to talk about case studies. Hey, Christy. And yes, so case studies, get your case studies in before the holidays. I have a number of folks, both members and end users who are looking to submit case studies this month. So if you have a case study and you would like us to publish it before the holidays, please get in touch ASAP. Before December 10th, ideally, because we have a lot of content production going on at the moment. So yeah, looking forward to maybe not potentially festive case studies, but case studies in the festive season. And again, the process and the link to actually kick off your case study proposal is here on the slide under GitHub. Great. Thanks, Charlie. And Bill, if you want to go to the next slide, I'll briefly talk about Q-weekly. So Q-weekly is our weekly Kubernetes and Cloud-Native newsletter. It's sent out every Friday. The content here is put together by a group of editors within the community. And as members, you're welcome to submit your own content. If you do have questions about our guidelines, how to submit, all the information is in here on the slides. But just a little update for you on where our metrics are at for November here continues to just kind of chuck along and another great place to highlight content that you've already produced. And with that, I'll hand it over to Katie on our PR team. I'm going to jump in here really quick. So Hillary is asking about how do I update my info on the landscape if I want to or for my company? And I just want to say this is all updated by the community. You can find all the information here on GitHub if you want to be able to do this. And it'll tell you how to do it. Basically, you're just going to create a pull request against the landscape YAML. And that's how you update stuff. But all the information is there. So sorry. With that, I'll hand it over to Katie for ARPR. Thank you. So yeah, we've had a good amount of coverage still rolling in from KubeCon. So just a few to highlight. We set up a couple of new projects, new incubating projects, cross plane and open telemetry to speak with the new stack at KubeCon. And so they did a great podcast there. And then the next one is one of our end user members, Niantic, who created Pokemon Go. That was a really great podcast and recommend listening to it. And then another great article on the new KCNA exam. We connected Katie Gamamji, who actually helped to create the exam to speak with one of our contacts at Container Journal. So that's another good read as well. And then we had two projects move into incubation. So the first one was Dapper. And we got some good coverage around that, which you can take a look at to learn more about the project. And then we also had Longhorn. And then I will pass it over to Carl to talk to the industry analyst highlights. Hey, everyone. Yeah, so over the past month, we've seen the past month and the upcoming month, we've seen the analyst industry and analysts publishing a lot of predictions for 2022. So Trisha and I went through and we highlighted some of the articles that car I so if you guys have subscriptions, I strongly recommend you click down into some of these and pull out some of that information. Two of note is this worldwide application performance market software forecast, as well as the cool vendors for cloud computing. But yeah, it's all pretty good. There's also been some great content coming out around in Forrester and Gartner and their blogs. So if you're looking for some great kind of holiday season reading to just kind of up level yourselves, some great free content on there for marketing and so on. And then we also this month, we also saw the Gartner Security and Risk Summit, which is one of the biggest security summits of the year. And I just wanted to pull out some of the highlights because as security is becoming more and more of a threat and it's starting to permeate and become a key buyer decision for companies, some of the cool statistics coming out of that are interesting statistics is that ransomware demands are 50, 518 percent, which is kind of incredible. And then 66 percent of CIOs increased their cybersecurity investments in this coming year will increase their cybersecurity investments for this coming year. So Gartner is also making some of those predictions for this upcoming year. And then finally 2022 Forrester predictions are out. Some highlights from that is there's this great quote that came out from there that rather than being supplementary or nice to have, cloud native will become the core of the cloud native strategy in 2022 moving forward. So that's fantastic. There's there's a whole bunch of interesting stuff to dig into there. Just go ahead and click down on that and pull out some more great information, but that's about it from the analyst community from this past month. Thanks, Carl. And then just for anyone that's new to the calls, we do track media coverage, looking at key messages and then coverage of our projects. So this first slide here is key messages. I think I'm surprisingly security is leading the way followed by storage and then networking. We saw also a big jump in over this past month. And then for the next one in terms of projects, Kubernetes continues to lead the way and Prometheus as well. And then the next one is our incubating projects. So open telemetry and cross plane just moved in. So we saw a good amount of coverage there. And that's it. Cool. Thanks, Katie and Carl. And with that, we will move to the events section. So it has been an extremely busy one for the Kubernetes community program. We had five different events going on all around the world. So there was KCD Italy, shout out to Inelisa and the team of Spark Fabric and the team for KCD Italy. Really fun stuff there. It was cool to see finally people talking about Kubernetes in Italian. I didn't understand any of it, but I still love the language. KCD Washington DC, the beginning of the month, KCD Indonesia as our largest KCD ever so far with 1,357 attendees. KCD Shanghai is our second in person one in KCD Guatemala, which is our first one that had a day just for students with just student speakers. That was actually even bigger than the day for professionals. So I'm excited to see where the community in Guatemala is going to be going after this. Stay tuned definitely. Coming up next month is going to be KCD Brazil, organized by the team here at CNCF. And there is a whole bunch more planned for next year. If you're interested in organizing or attending a KCD, I'd encourage you to reach out to me, reach out to one of the organizers. I'm always super happy to talk about the program. So yeah, please do. Is there a calendar for KCD somewhere? So the easiest way is to just look at the marketing committee slide deck every single month. It's also in all the issues on GitHub. So I can just go to the repos right now actually. Sorry. So you can find the dates in all the issues, but none of the dates have been announced for any of the other ones next year. So that's why they don't have an official date yet. Yeah. So events that will be up through the end of the year. Next week, our friends Libby and Christie will be at the risk five summit. If you want to say hi to the CNCF team, please stop by our booth there. Otavio, I'm sorry, like reminding you, thanks for the offer to help on Brazil. And I'd be super excited to have one in Portugal. I would love to see an event there. Yes, we'll also be at open source summit Japan virtually in two weeks too. There is also the open source summit, or sorry, tubecon, cloud native con plus open source summit China December 9th and 10th. We would love to see you there. And we would like to say thank you to our sponsors, especially our strategic and diamond sponsors who have iCloud, Intel and Alibaba cloud. We also, in case you've forgotten when the next QCon cloud native cons are there may 16th, the 20th in Valencia. Super excited to be there in the spring and eat some oranges there, December 24th, the 28th in Detroit, sorry, October 24th, the 28th in Detroit, Michigan. As I'm in Westerner, I'm super excited to see QCon finally landing there. And also Q4 2022 is QCon cloud native con China. So excited for all those events coming up. For the sponsorship opportunities, I know everyone's always super excited about that. The sponsorship prospectus is now available for Europe and North America with China coming later this year. If you want to request a contract already, I know some people have already been on it. Please contact sponsor at CNCF.io. And there are the important dates in case you need to know when they are. There's also the 2022 diamond sponsorship lottery. I guess the important ones are for QCon Europe. You need to have a signed contract by January 27th at midnight Pacific time. And the drawing will be on January 28th for that. For North America, once again, there's two drawings, so January 27th and for June 9th. So yeah, with that, we are done with the meeting today. Super happy to stick around, talk about any wins that anybody in the community has, any questions that people have. Yeah, I'd love to hear from you. We're also done now, so you can also feel free to drop out. We're here for whatever you want to do. If I may chime in real quick, thank you, Bill, Christy, Charlie and PRER team for an awesome meeting, for a good close out to the year. So grateful to everyone in the community who joins regularly, who is making use of all these offerings that we bring to the table. I just wanted to make a shout out that CNCF is growing and hiring, and if you or folks who are interested in operational roles, marketing type roles, or developer advocacy style roles, please feel free to connect me. I'm looking for mid-level to senior, and this is intentionally vague right now because we're figuring out job descriptions and the team and I are discussing, but we want, I wanted to put the word out there so that people who are interested, people who could be interesting, let's get the funnel going. So you know people, you're welcome to send them along to, I think the best move would be to send them to Bill or Christy and they will, we will work together and catch up with anyone we can. Thank you. Also, thanks for that, Priyanka. Also, I, going back to Sivia's question, there actually is a calendar for KCDs. I totally forgot about this. I dropped the link in the chat if you want to know about that. So it's in the community events and as you can see, the only ones that are scheduled right now is Brazil and then Amsterdam at the end of the year. So that's where they actually are all listed. The other thing from Lexi is there is now a jobs marketing channel. So Priyanka, once we have those job descriptions up, we definitely have to post them in the jobs marketing channel. Perfect. I'll drop a link to this too, so people can join that. So if you're interested in a new job, I won't tell your current employer. I'll just like send them a slackment. No, I'm kidding. You should check it out. You know, there's always lots of things happening around the cloud native community, fun companies to join or like be a part of or maybe someone in your network is looking for a job. So and if you're looking to hire, feel free to post your job opportunities in there too. This is where the community connects and gathers. So we'd love to see that as a great resource for the community too. Otavio, how can I get access to today's meeting slides? So I can drop a link for them in the chat. And then also in there, you can see the link to the folder too. Oh, thanks, Christy beat me to it. So it's a little bit too slow today. You know, it's winter here. We're just like, like, like, that's all good. I also just wanted to mention that if you're interested in more statistics about the year with CNCS, as it relates to projects and other things, we will have the annual report that Charlie is hard at work on. And I'm really excited for that to drop. That'll come probably right before Christmas. So be on the lookout for that. And then going into January 2022 will also have the results from our annual survey. So a couple of key content pieces coming from us will probably have some slides on that in our next marketing committee meeting, but just wanted to give everyone the heads up on that. Thanks, Christy. Blake, thanks for joining us today. I'm glad you enjoyed the conversation today. Thank you. Bye, everyone. Thanks, all. Happy new year. Bye.


Learn, welcome to NewsClick in today's episode of Talking Science and Tech, joined by Prabhupada Koyasta. And today, we want to talk about France and its testing of nuclear weapons in French Polynesia between the years 1966 and 1974. Recently, declassified documents and analysis of these documents has revealed the extent to which the testing impacted the citizens of French Polynesia and how France grossly underestimated the impact of the radioactive fallout. So, Prabhupada, can you start by telling us a little about this, about what happened in Polynesia in those years? You know, first is to call it French Polynesia itself, of course, is a part of the colonial history that is there in this part of the world, as well in other parts of the world. The French captured Polynesia, the Polynesian islands, which it claimed for itself. And of course, the French had a nice way of putting it, calling it first overseas territories, then calling it overseas French provinces, and so on. But in effect, there were colonial possessions. They had very little rights. They, of course, their culture was subordinated to what was the French language, the French culture. And even today, officially, they are supposed to be overseas citizens of France. But the relationship between French Polynesia and France has not really changed. It still is one of a colonial empire. And because these are small islands, therefore, their ability to fight together is limited. Therefore, they continue in a quasi-semicolonial, neocolonial mode, with France being the dominant player over there, the dominant power. Now, the history of the nuclear testing in French Polynesia clearly bears out how the French looked at the Polynesian population. They were quite aware of the extent of the fallout. They knew it was going to affect the population of the islands. They really didn't bother. And that's the entire history that we see from these documents. That how much they knew where the wind was blowing, if a test took place, in which direction the fallout would take place. Did they make any attempts to warn the people there? No. They just continued with it, taking for granted that it doesn't matter what happens to these people. So it's only much later when there were a lot of protests, a lot of writing about it, they started acknowledging, OK, there is a problem we have. Cancer rates are very high in these islands. And there seems to be a correlation between the nuclear fallout because of the tests and the consequences thereof. The radioactive fallout was finally recognized at some point and the dates are given in these documents. And they passed some laws to say, OK, we'll provide some compensation. The compensation provided had to be proven by documents that had to be submitted. Again, the reality was that most of the claims were not accepted. Most of the claims were rejected. No explanation was given. And the French government's argument was that they had actually done detailed studies to show the effect was negligible. And this had been actually rubber stamped according to them, not rubber stamped, but according to them vetted, as we Indians say, checked and verified by the IAEA, the highest international coordinating body on these issues. Now later transpired that the French did not submit any original data to the IAEA. So IAEA had really nothing to go upon, except the data submitted. And therefore their exercise was really to say there are no obvious errors in the calculations. Now the real issue was what were the data submitted? What were the data that the French had which they did not submit? Now a group, and this I must say, was really an enormous work that these groups have done in different places. Three groups, one, of course, in France, one in Norway and one in the United States in Princeton. Three groups worked together to create a complete scientific analysis based on documents which had been declassified in 2013 by France. And based on these documents, they found out the exposure was nearly of 95% of the Polynesian people had an exposure to the nuclear tests. It was also found that the levels that they encountered were much higher than what the French had claimed. And also the amount of radioactivity, therefore the people had been exposed to was much higher. Given that they have shown that it is simpler to say everybody did suffer from the radioactive fallout and if they showed the 23 possible consequences of the radioactive fallout in terms of cancers and other diseases, then they should be compensated because that would then therefore correlate to the cause itself. Now this calculations that they have done, and again, we have the details of it, really bring out that the numbers we are talking about are not huge. So France could have spent over the last 50, 60 years, very easily 20, 30 million francs to compensate the people, which they didn't want to do. So the amounts that were being talked of, now it may seem large because it's over a period of 30, 35 years that we are talking about the total compensation involved. But if you really look at it, per year compensation was insignificant compared to French economy. So this is not explained by economics, but the sheer fact that you don't want to recognize your French Polynesian citizens really as French citizens and therefore you're willing to dispense with the problems that you have caused them through your nuclear tests. So I think that is a part of the colonial heritage that people don't recognize easily. And you can see France did the same in Algeria. I will forget the ethnic violence that they imposed in Algeria for hundreds of years, but even in the nuclear test in Algeria, we have exactly similar consequences. Though again, the Algerian numbers are much smaller. This was a much longer period of tests that the French did in French Polynesia. In fact, they also continued later, they wanted to start again new tests in the 90s. And then we have the famous incident of the rainbow warrior, the Greenpeace boat which went to French, wanted to go to French Polynesia, which was sabotaged and sank, killing one of the people in that boat and for which the French government finally was held responsible because even this was clearly at the highest levels of the French government. So given all of that, the French colonial history is of course dark, like all colonial histories, but its specific impact in terms of the nuclear tests also brings out that this is not something which happened in say 100 years back, 200 years back, but this history or this attitude still continues. And I think this particular case and now the documents that have come out, the analysis which has been done, shows that this is very much a part of what we see even today. And let's face it, French Polynesia continues to be under a certain kind of colonial subjugation. It may be called colonial overseas provinces, but the reality is really France controls these islands, just as France controls the ex-African colonies through the financial levers that it has, that it really controls the exchanges, the foreign exchanges of these countries are controlled and even their budgets are passed by the French parliament. So French neo-colonialism is very much alive, whether it be Poland, Polynesia, or it is Africa. And that is something that France doesn't want to recognize. It always claims, oh, they have been very egalitarian. They made people, they are citizens and so on. But the reality is the French colonial mentality, its colonial framing still remains and its relationship with its ex-colonies and with of course what it calls French Polynesia, still very much a colonial one or a neo-colonial one at best. And we can see it in this particular example of the nuclear test. I think it brings it out most sharply when we see the reaction it had to the compensation claims the citizens made regarding legitimate cancer, that the legitimate expenses for cancer, compensation for cancer, which was a consequence of the nuclear test. I think it's a very, very sad history for French Polynesia and for the French government that I think it still continues. Right, and like you're talking about the compensation and how France was, well, it seems, I mean, most likely deliberately miscalculated the impact this radiation had on people and was able to then reject most of the claims. But now that we have this analysis, the study which shows clearly how much people were impacted, as you said, almost everyone was impacted. Do you think, is it likely that the government is now going to acknowledge this and then will take steps to rectify its actions in the past? It's a very important question for the French to answer. Unfortunately, French Polynesia doesn't have that much of an impact in the French politics. And without a strong opinion within France, will France be shamed into giving this compensation? That's a question. Will France be held to account by rest of the world? Probably no, because most of the world wants to move on from the colonial period. They know that colonial period wrongs cannot be redressed. But this is not colonial period wrong. These are actually wrongs in over the last 50, 60 years. So I think this is living history. The people who are claiming compensation are most of them are still alive. So I think if the French can be shamed, the French government can be shamed by its own people. And this is really the onus of it lies on the French people. If they can be shamed by their people, then this amount is not that high. But you know, there is another amount which French have never really compensated Haiti for. When the Haitian slaves were freed, there was a huge reparation which the French government claimed from Haiti. And it continued till about 1948 or 49. And that bled Haiti, one of the most prosperous islands in that part of the oceans, in West Indies nearby areas. And Haiti played a huge price for that. It became one of the poorest countries in the world. So I think that history of France with regards to its colonies and armed with its own aura of being a superior civilization I think is what precludes honesty to examine the colonial history of France. And I think that's the big problem that we have when you come to these issues. The recognition that they were colonial empire, they were a colonial empire and they dealt with their citizens or their colonies, the people in the colonies brutally is something the French really do not want to recognize. They've recognized it partially in Algeria but in other parts of the world, they still refuse to recognize it. And I think Haiti and the French politician, this particular example shows what is still missing in French understanding of how they dealt with the rest of the world. Thank you for joining us today. And that's all the time we have. Keep watching this clip.


My name is Sergeant Jennifer Andrade. I'm a combat photographer with Third Marine Division, Headquarters Battalion. I've covered a lot of training over Balkatan. I have taken photos of several different live fire drills, both Marine Corps specific, but also bilateral. So I've covered training between the U.S. Marines and the Philippine Marine Corps. They've done weapons familiarization, TCCC training where they've learned to take care of someone who's down in the fight. We have also covered mechanized range where they were in LAVs, AAVs and JLTVs all pushing together and firing and just working as one unit. Capturing that kind of imagery contributes to the overall objective of Balkatan because it is the only way that people are going to know what we are doing here. You know, it's that kind of transparency where we can say, like, yes, we are here. Yes, we are working with our partner nation and this is what we're doing together. You know, it's to show that we are both committed to keeping this region safe and secure. Capturing imagery of exercises like this contributes to the mission of Third Marine Division largely because it shows our presence in this region, the kind of training that we're doing and just how far our reach extends in an operational setting. You know, it shows our proficiency in all types of terrain and all types of weather and it shows the kind of connections and strong ties that we have with the militaries in the region. I think that sometimes people view Comstrat as the social media marines or, you know, pretty pictures for Instagram, but really, like in the broader sense, Comstrat is just a communication tool for the Marine Corps and that's to communicate what we are doing not only to the people in the U.S. or the people in the region that we're working in but to the entire world. So it sends strong messages to both our allies and our adversaries of what we're doing, what we're capable of, and overall, it just shows people what we can do. Comstrat stands for communication strategy and operations. What that means is that we are the communicators of the Marine Corps, we are the voice of the commanders and we are here essentially to inform the public of what we're doing and what our mission is, what our objectives are and how we carry those out. Comstrat as a whole is important because we are a big source of information communication both internally and externally. So both two marines in the Marine Corps but also a larger audience across the world. We do a wide variety of different tasks and missions from the stuff that you see out here, taking photos and videos of marines in the field, in their environment, doing their jobs, but we also do things like sensitive information handling. We do vetting for interviews and media support. We assist commanders in welcoming external media sources to events like this, to exercises like Balcutan so that they can see firsthand what we're doing. And Comstrat plays a role in all of that. I haven't met many Philippine marines so it seems like they are a bit of a rarity, but the ones that I have met have been really nice and they have been just as hardcore as any other marines that I have met out here, both US and on the Philippine Marine Corps side. There were some out, not like out with the MEC range that we did, but they were working as gunners. The female Philippine marines that I have met have been just as hardcore as any other marines that I have met out here. They work with mortars, they work with the LAVs and as gunners and there are officers in these combat MOSs out here. They have been really sweet, really awesome. I have loved meeting them for one and I honestly think that they are inspiring as well. It has been great to meet them and I guess get to meet my counterpart. What has been my experience with it? Honestly, I think it is cool. I think it is really cool to see the Philippine marines and the US marines coming together and working together in such a proficient way. There are different challenges to overcome. There are language barriers, there are issues with weather. All of those things, but they have come together in just such a cohesive way to overcome these challenges together. The Philippine marines have taught the US marines different ways to acclimate out here and the US marines have shared knowledge with the Philippine marines as well regarding weapon systems and the procedures that they use and everything. I honestly think that it has been really cool to watch them learn and grow together. Sometimes on the ground level, the big picture impact of Comstrat isn't necessarily always seen. It looks a lot like we are just running around taking pictures and posting them to Instagram but really what we are doing is we are sending a message to the world that we are ready, we are lethal, we are proficient marines and that we can operate in austere environments and all around the world and that we can work cohesively with our partner nation.  It has been a really awesome experience to be out here and experience a whole different country, see the different way of life that the people, the Filipinos live here. It has been great.  Honestly I have met some of the best people out here. I have made some great connections and I have honestly had a really great time highlighting these marines and their hard work. I think one of my favorite things out here is when I take a photo of some really cool training that they just accomplished and the marines come up and they are like oh I want to see the photos, can you show me, I want to send it home to my mom, that kind of thing and I can tell them where they can find it and how they can share that imagery themselves. I mean they love it and honestly I think that is one of my favorite things about being a ComStrat Marine.


This talk is about RPM autospec, more specific that's to relieve maintainers, package maintainers from having to maintain the release fields and change log entries in their RPM spec files manually. Okay, what's it about? So in RPM spec files, we have manually maintained release fields and change log entries, as I mentioned already, and we've had them since forever, almost since RPM exists, which is sometime in the past, 1995-ish, I think was the first Pearl-based implementation of RPM. And since then, maintainers had to bump the release field and put in some information for context, what they changed with every change to their RPM package. Meanwhile, we have a way for other people to contribute to RPM packages in federal using pull requests. Since for about four years, we have that feature with this kit being implemented on top of Pagger. So that's a problem for this workflow because for every change, you have to bump the release field, you have to put in a change log entry, and every contributor does that, and the maintainer does it on the side, like bypassing the pull request workflow with every change that gets in before you get your pull request and you have to update your pull requests and resolve conflicts and stuff like that. And then we related to that, we have more or less fragile automation for mastery builds, like they also have to bump the release fields and put in a change log entry that this is for the mastery build and then build this stuff. The work I'm presenting is a continuation of the prototype work we did last year. There are some significant changes to what we did in the prototype that were in part requested by Fesco, and also we had a couple of things which we just didn't get around to implementing last time. So who's responsible for this? First, the prototype without the work we put in there, we wouldn't have gotten that far this time. So other than myself, Pierre Vichybon, who many of you probably know as Pingu, and Adam Saleh, when the team that worked on the prototype. And this time around, we had Stephen Cody, David Kerwin, and Patrick Polakowicz. And this is for mainly maintainers. So you shouldn't have to care for the release field or the change log entries because especially the last information you put in the commit locks already. So, and for contributors, this should remove the friction, like what I described earlier with conflicts, having to update the pull requests if something else changes underneath and so forth. And for the release engineers, just less hassle with master builds. You just have to put in a commit that contains the right lock entry and build it from there. So our goals for that are objectives, like the way we wanted to achieve this is just to have static fields. You put in just a placeholder in the release field and in the change lock and the code takes care of filling in the right contents there. It determines release values automatically and also reuses the relevant parts of commit lock messages for RPM change lock entries. We wanted this to be unobtrusive to have it blend in with existing technologies and workflows. Like I shouldn't get in the way. We didn't want to introduce yet another like domain specific language for this. We didn't want to interfere with how commit lock messages are, like what they're, how they normally look like. And it should be easy to use, easy to opt in and to opt out. Especially the opting out is also a low barrier of entry because that means you can try it out. If you don't like it, you can just revert your changes. We want to have reproducible package builds. We didn't want this to be something that locks in locks a maintainer or a package into using federal infrastructure. You should take the produced SRPMs and be able to rebuild them locally in other build systems like open source OSBS. And you need, as a maintainer, you need to have the ability to fix things later. Like I can't count how often I forgot to update, like to upload the source tile ball to the look inside cache and had to check the, commit that change later. And this is something I don't want to end up in a RPM change lock. So there needs to be a way to put a little polish on the change lock if the need arises. So the final thing, what we did is mainly a Koji plug-in, like that lives on the Koji builders. It pre-processes the spec files and fills in the right content where the placeholders are before building the SRPM, which is then built into installable packages. It's also a command line tool. You can, if you have it installed, you can run RPM autospec, say generate change lock and point it to a spec file and it will generate the change lock directly in your terminal. So you can see what it would do if you were to build your package right now. It's also a Python package, which is basically, like that's where all the action happens. And that allows us to have others use the functionality integrated with tools like FET package or with RPM def pump spec. So looking back when we talked about, when I talked about release engineering, they can use RPM def pump spec all across the board. And in the case of a package that uses these features, it will simply just, I think it will prepare the commit. I'm not quite sure what it does. It will leave the spec file alone. That's the main thing here. All right, changes since the prototype. We greatly simplified the release calculation algorithm. Previously, in the prototype, we tried to emulate what a maintainer would do or what we in the team thought a maintainer normally does. And for that, we had to like keep track of from which commits packages were built. We stored them in Git tags and Fesca didn't like that too much. So they asked us to use a more simple algorithm which simply counts the number of commits since the last time the version was changed in the package. With that, we lose the ability to have multiple builds from a single commit. So if you do one build and you want to do another, without doing any changes, just maybe say rebuild that thing against the new library or doing a master build in the case of release engineering, you have to add another empty commit. It gained some functionality. We just didn't get around to last time. So it works to complete a series including merge brand merges of different branches. It will like in the case of merges, I know let me talk about that later. And the most important thing it's deployed in CoG since mid of June this year. So you can use it right now for your packages. So to stop having to maintain the release field, just put the auto release macro in it. That will do it for the most common cases. If you need to have, like, if you need to package pre-releases or snapshot releases and you don't use the, I think that was using Carrey until the characters in the version field. If you do the old way, there are flags for this too. It will include the disk text. So having just a line that says release, auto release, that will be enough. As I mentioned, it counts the numbers, a number of commits since the last time the version field was bumped. And in the case of merges, it takes the branch that has the highest value. If you merge two branches, one has three changes, one has five, the release field gets a value of five. And the simplified algorithm that affects a clean upgrade path between federal releases, that was something we cared about a lot in the past, but not so much today because upgrades nowadays do the equivalent of DNF distro sync which doesn't care about whether package gets up or down graded when doing the upgrade. So for change log entries, it just uses the percent auto change log macro in the change log blog. And individual RPM change log entries are generated from the log subject lines and who did the commit and at what time. Like if you're not familiar with Git commit logs like the usual structures, you have a single line that describes the change and then you have a, that's the so-called subject and then you have a body where you can go into detail also into reasons why you did something. And also stuff like this fixes that bug or like signed off by Lyons who worked on the change. Also you can override this in a change log file. That's the way you fix things if they go, if you notice something went wrong in the past. So you simply dump the generator change log into that file. Do the fixes commit that and then it will take these contents from then on. We're also mentioning, like so far we only use the subject lines. We know there's a demand for being able to specify longer RPM change log entries, but we're still hashing that out. And for change log entries, because you can't really know what content, what changes were relevant, like you can't programmatically find that out really. The only way, the only situation where we support that fully is if one branch like wins and the other, the content of the other branch is simply discarded. That's the case if you use the hour strategy for merging, which simply does bookkeeping merge commit and takes the whole contents of one branch and discards the rest. And in the case of normal real mergers where you might have resolved conflicts between the two branches and stuff like that, like when it can't find out on its own what the changes are, it will put in a message saying that it can't resolve this merge so you can fix it manually. Okay, what's next? I mentioned longer change log entries. There are a couple of approaches to this. There's some discussion in an open issue about that. I want to do it in a way that the git commit log messages that they still look natural in some way, like that they look like any other git commit log message that we don't have to invent something that goes against normal git workflows. And the next thing is a way to preemptively say, oh, disregard this commit for the change log. I forgot to upload the table or something like that. That's not relevant for the RPM change log that you can do it right away instead of having to patch things later. And also we want to accommodate downstream users of that that would be like the Neil Gomper does some integration with OSBS to rebuild packages from Fedora there and they have some different requirements with regards to version and release fields in the change log. So we want to accommodate them with that. All right, I'm done here. So you can find further information at the project repository at the URL you see here. Same with documentation. There's much more information inside there. And you can also look at these slides if you haven't had enough of them already. They're on like the repository where these live, the source of these slides is on Pager as well. So are there any questions? Maybe they have bubbled up because I only looked at the speaker view of this. You see there are questions. Could you show us an example of how to use it? Of course, I'm happy to do that. Let me just unshare my slides. All right, I'll go to have a demo in the source code. This is how you enable automatic release numbering. And this is how you enable the automatic change log entry generation. It's really super simple. Let me run through generating the real spec file that then gets passed to Koji for building. No, sorry. Okay. I'm in the wrong top folder of the project. So this is what happens to the spec file before Koji gets to anything from it. It puts in, find the auto-release macro, sets the release number to 11, because that's the number of commits since the last time the version was changed in this particular project. And it fills in the whole change log of the file. That's all it does. So, any other questions? Okay, let me go from, start from the bottom. I fedora packages that RHP will apparently pull into Rella. Can I use RPM Autospec or will it cause problems for them? It depends on how, that depends on how they consume it. I imagine they will want to have a clone of the Git repository and build from there. They would have to have some enablement in the building infrastructure in Redhead. But that shouldn't be a huge problem. The internal system we use there also based on Koji, the only really hard requirement we have is it needs to, the Python version needs to be 3.6 or later. So our internal systems may need updating. I don't know. I haven't looked into them in quite a long while. What are the CLI commands? Let me share the screen again because it's much easier to simply run it. We have generate change log. It just, I mean, does the things and dumps the change log on the, on standard out. And also same thing with calculate release. There's not much more. We have some ideas. I forgot that in the slides. How could that happen? I don't know. To, like to automatically convert a package to using auto release and auto change log. Also to freeze the, like to generate the change log and freeze it into the change log files for editing. This is all stuff you can do manually using two or three commands or your text editor. But it would be very convenient if you could do that in one go. Okay. You didn't get the snapshot remark. Do tilde RC1 and curate devil work and how? Yes, they do work. You just wouldn't use the, the, the flags for the, for the legacy, legacy way to encode snapshot versions into the release field. RPM or spec largely doesn't care about the, the, the version contents. It just cares about, did it change? We don't really look at what's in the, in the version field other than comparing it with the version of a previous commit. And Matt, you're asking the, the interesting question when are we going to make this mandatory for new packages and mandatory for existing packages? I mean, yeah, I wouldn't be against it. I think it's solid. Let's give it some time to prove itself in the field. And then it's, it's a policy question like when are we going to tell people you have to do it this way? I don't, I don't really know. For, for me and for the release engineering folks, probably rather sooner than later. I mean, but I'm biased here. Okay. If there aren't any other questions, we're almost out of time. How many packages are using it already? I don't know exactly. I have converted one of mine. I think we will be eating our dog. We don't yet, but we will be eating our dog food on that soon. Another unrelated package of mine uses it. I have feedback from a couple of people. I think get Kola uses it. That's one instance like where we just discovered a bug with merges, which will be deployed soon. You use that and you notice that the source opm generation takes forever. I mean that little really, and until co-gd is restarted or something. Then you've run into that bug, but we have the fix. It's in, it's released already. We just need to deploy it, but I don't want to bother Kevin with it on the weekend. Anyway, yeah. All right. Don't. I'm missing some context with fat package mock build error. Change log entries must start with a star. This is odd. I haven't seen it already, but please tell me more about it. Maybe not right here because we're out of time, but just point me to the package or the repository that's happening. All right. The co-g plugin is separate from co-g. Yes. Like you can run co-g without it. It's not part of the co-g core code base. It's a separate plugin which you have to install and configure your co-gd process for it. All right. Oh, that solved itself. That's nice. I like these. I didn't have to do anything. They're my favorites. Okay. It's the top of the hour. Thanks so much for attending. I'll stick around in the general chat and probably the museum map or something. So if you want to hit me up there or on IRC, I'm regularly there when I'm at least when I'm working. So thanks again and have a good rest of the conference, folks. Bye-bye.


ooo hi that's you guys hello and welcome back to the average or welcome to the average if you're new here i'm Steph i'm the average artist and today we have a bit of a fun video i bought a load of crayola beauty stuff from Sephora last week and i've been dying to try this video idea we're gonna destroy some eye palette shadow what am i saying some eye shadow palettes today and if you hate that please just walk away because i'm sick of putting disclaimers on my videos i think everybody takes what i do when i do silly videos very seriously and i'm like no guys please i'm just here to entertain myself and hopefully by doing that entertain you but yeah they come in these cute plastic containers that say crayola on it and crayola beauty i mean they are pretty plain i guess crayola is a cheap art supply so it's a bit strange that they make makeup now it's a bit random this came out probably about last year there's pesto she sits like here these came out i think last year i'm disclaimer number two i really like makeup but i'm not a huge expert so we're just gonna say that this is kind of cool there's some nice colors in here i'm not sure how pigmented they are i'm not a beauty guru they're not very pigmented but yeah we're gonna try and make some art with these supplies so let's just check it out we've got some neutrals and then i've got some crayola lip crayon trios and here are the okay don't open that way that's fine don't open that way the lip shake oh my god that was really irritating all the lids fell off as i took them out like what crayola why okay right they come in red very cherry and strawberry and i'm hoping to use them some way in this piece of art that i still don't know what i'm gonna draw and we also have this one the mermaid eyeshadow palette i really like the boxes that this come in with this gradient i'm a sucker for a gradient so we have these blues and pinks and purples quite nice i like them i like them a lot this is an eyeshadow review okay so i don't know what i'm doing this is we're gonna make art from these now i'm planning on using this super base that i got with this duet sample glow in the dark paint and i'm not sure it's gonna work but we're gonna try it anyway they could come out super weak and we'll see i'm gonna pull the super base in i'm not sure which way to do it uh this is all new so please bear with me folks well there's no yellow right so this could be our yellow this could be our blue and our red i guess oh i don't i don't feel good about this but let's scrape out this blue here oh my god that is so gary but fun this is gonna be messy i think okay it's gonna be some very shiny paint definitely i don't know if i've used too much pigment or not enough or whatever so we're just gonna try as we go so it's becoming this really like light pastel blue and i think that's because the super face is white obviously and the and the pigment is so light i'm gonna have to keep trying to mix it up of course i don't even know if this is gonna dry or anything so we're gonna do some swatches somewhere in my sketchbook okay of course it's very thin i mean i kind of expected that but and it dries super fast oh no we can we can work with this i think okay that took an age to sort this out so i'm just going to swatch some stuff i want to swatch these so i'm pretty sure these will never dry but we can play around with them maybe you can use them in the background or as our sketch i'm not really sure what to do with these but they could be fun to mess around with this whole point of this video is is just to experiment and have fun and i hope you guys enjoy it it took quite a while to mix it up and i think that it's just super like quite hard to work with obviously because it is makeup but i think it will have like a cool effect once i'm done with it i think it'll be fun to just see how it turns out so beginning with this really weird strange concoction that i had made i was really thinking that it was gonna not work out and it was just gonna be two or three and not make enough pigment that i need to create a painting with and i was thinking like oh maybe i could mix it with i have paints and then just say it didn't work and like show you that i'm using paints and stuff instead of just using this and using it as like a shimmery layer to help bring some shine to the image but then as i was working this paint it just got better and better because you could just layer down a um a sheet of it with your paintbrush and then when it dried it was pretty solid and you could layer down another thing over it and it was quite opaque which really surprised me because i was expecting this to not work with my tests that i did previously i think i just used water with with it the first time and because i thought like oh maybe a little bit of water would help to i don't know disperse the the lumps of pigment in the paint and yeah it kind of worked like when i was doing different layers and when i was trying to mix the paints together it worked out quite nicely so i would say if you're going to try something like this then do have a little jar of water but mostly i went in with just the paint on its own without water and it helped to create really thick layers of this kind of creamy paint and i really enjoyed it i really got lost in doing this piece i just put my music on and i got into the vibe of the painting and this sort of weird ethereal mixed painting that i wanted to do at first i was really insecure of how this painting was going because i thought like oh it doesn't look anything like a face or a body or anything like i wanted it to but as i was layering the bits down and then i would move away from one certain point of the painting and go to a different part i would find that the previous part of the painting that was working on was dry and i could go back in and do little layers and it was a little bit finicky to work with smaller details and yeah i went in with fingers i truly went in and did a finger painting here because i felt like i wanted to layer down and get rid of the pigment of the eyeshadow with it in the paint so doing that really helped layer down a a thick layer of paint underneath all the painting that comes after and then i just got really experimental with it i think like this really made me let loose and kind of relaxed into the process of making a painting because i knew this was going to be a fun video but i didn't know that the outcome was going to be something that i actually really liked and i'm really happy with the end result that you'll see but it was just a real process so yeah like i was saying with the smaller brush to do little details of the features of the face or just outlining something or hinting at that outline it was really difficult because it's a thick glob of paint and anybody knows who's painted before when you have a thick bit of paint on the paintbrush it's difficult to get that finer detail so i was really trying to thin down my paintbrush into like a sort of point and then try to kind of dot on the paints where there was smaller features like the eyes and the lips and stuff and i think that really helped and going back in like i said layering it up really worked and i can't believe that it worked because i was really i was really hopeful that it would work and then i was just expecting it not to because that's just how things go isn't it but it really worked out and i really enjoyed this whole process and getting lost in it i also really enjoyed using this lip cheek crayon it felt really smooth going down and then i blended it out to give that sort of like glow or haze or mystery to the piece and i think the mood of the piece really works well i think using makeup really lended itself well to this vibe that i wanted to get and i was thinking like oh should i just smudge her whole face so you just don't know who she is and i think that's something i would have played with next time but i wanted to see if i could do like a bit of a proper portrait if that is the correct term that i want to use and i think i got away with it i really did struggle with the proportions i didn't like the way the dress was turning out and i just thought what i would do is change it as i go so i'm sort of mixing on on the paper i'm just using a plain watercolor paper by the way for this piece so i'm just mixing the paints together and just having fun with it and yeah i really enjoyed it and i got a bit of um like a good vibe from this kind of technique and it made me realize that maybe i want to sort of do something like this for the horror comic oh if you guys don't know i say this every time i'm making a horror comic so i'm kind of trying to find the unique style that i want to do to it but this painting was particularly good because um for this development of this horror comic because what happened was as i was layering down the paint um in inverted commas the texture was building up and there was a real roughness to it so what i would do is i would get a little bit of paint lighter paint on the paint brush and kind of dry brush over the texture of the other bits of the paper where it was rougher and highlight that roughness because it just it gave a little bit of texture it highlighted the texture and it's it as if there's depth there without creating too much work so it could work well when i'm trying to hint at a background or give a certain look or feel or maybe like mist or shadows or there's something hidden in the darkness and i really enjoy doing that i used to do that when i was a teenager a lot in my work like dry brush shadows and things so it's good to remember doing that because i don't think i've done that for a long time within a piece and i really think that it worked here because it just gave the sense of the the prom queen here just glowing or something wrong something eerie and i really enjoyed painting this to talk a little bit about why i'm painting a prom queen that is going to be part of the comic and there is a character in it who is a prom queen in the 1950s 60s and i think this would be a really cool part of the story and a good costume to draw and i really like fashion so it'd be fun to look at old 1950s style but then i was thinking like i was doing some research and i was writing the other day the comic actually and i was doing a lot of research into you know what would be in the 1950s in america because i was looking up tape players and cars and different things and trying to just get like a base layer down of knowledge in my mind so i don't make any really big mistakes of like hey they went to the moon and then you know something stupid so i was just doing that and then i was thinking you know what really works like um i don't know if you've ever seen this film it follows but basically in that film there's no real set time it kind of merges different eras and decades and it works really well and i was thinking maybe i could do that as well because it lends itself to an eerie feel and i think it would be nice to sort of set it in the 1950s 60s but maybe have a hint of future or you know it's a different universe to ours i don't know so i was just looking into that to research and develop maybe an idea i don't know if i'll do that because it's just an idea a standard for and i might not follow it i might but yeah i think it helps to create the idea of um just a weird vibe within a story because no you as an audience or somebody reading it you might feel a little bit uncomfortable that you can't quite place where they are i don't know i think that's kind of the vibe that i want to go for but yeah that's the painting overall and i really enjoyed it it helped me develop my idea for the comic and that's great in my eyes and yeah i think that's it i am happy with this piece and in the end we didn't have to use any other products except for the crayola stuff and obviously the super base to actually create the paint i was thinking maybe i could try mixing it with alcohol i don't know why like to see what just what would happen i think that wouldn't probably be great and then i thought maybe i would have to use pencils to define stuff but as i said in my voiceover once i started layering down it just worked out and really enjoyed it i really got into this piece and i really like the ethereal feeling it has and kind of mysterious horror vibe that it has and yes i'm very happy and i hope you guys enjoyed this i hope you don't mind that i destroyed some palettes i it's all for the intent of fun and entertainment so and i hope that you enjoyed this video please like and subscribe for more of this stuff and more of this stuff if you enjoyed it and i will see you next time bye


Action. That's why I did IT. So I wanted anything to do with technology and computers behind the desktop and studying other things. Now my IT background— it assists me a lot because I learned online, I market my produce. Technology has come to change what my dad used to do. I can change from whatever I'm doing here, I can decide it online. Instead of now taking my budgetables to the market, We collect from home. We get your money coaitry. We ignore disturbance, and we are go somewhere. We go to the purposely. That's why people find me having these things. They are feeding them like babies. We must love whatever you are doing. We must change our mindset, and we love whatever we are doing. We achieve a lot. Yang people believe that in Nairobi it's the only place where you can get money, So, we can get employed. I take advantage of being next to Nairobi because most people in Nairobi feel from here. That was also another reason why I decided to do farming. For the youth now they should also know that agribusiness is also an employment. If you excel very well in agribusiness you can get as much as you wish to get. So you should come over and join me doing farming.


your financial statements until you pull it in from that feeds transaction and so you probably want to double check it on a manual system and then pull it over. So this one says check each payout in for review then confirm and this will automatically confirm. Connect after so this would be the disconnect if you wanted to disconnect here. If we go into the items they have the sales items which is going to be pointing to the default in QuickBooks sales Shopify item shipping Shopify shipping item and then discount Shopify discount you can edit these items here and then change change them here and so I'll cancel that these are going to be the defaults and then you've got the customers and vendors. Now note we're not pulling in all the customers all the customer data is going to be over here in your Shopify store and that's probably where you want it because you're usually going to be a bulk seller you're trying to sell a bunch of stuff unlike a Shopify or an Amazon you don't really need to know all the information about the customers other than put their email on your email list most of the time right so they're not so they need to have a customer so they're just going to put it into a generic customer meaning this is going to be one customer for all transactions that are going through your Shopify store if you need to have more detail about a particular transaction then you're not going to go to it in QuickBooks because we didn't pull in all that data but rather you're going to go to the Shopify right and then on the advanced these are the mapping accounts so these are kind of like the defaults that it sets up basically automatically so you've got a clearing account this holds Shopify payouts before they're reconciled with your bank account so just like we did in the manual method we still have to deal with this clearing account which means when the money is coming in it's not going to deposit directly into the checking account it's going to put it into the clearing account and then we can match it to the deposit that's going to clear the checking account which will bring the clearing account back down same concept as we looked at with the manual method it's just trying to automate it now then you've got the sales Shopify item sales is QuickBooks categorization Shopify sales income account shipping income this are the charges that you're going to have for the shipping it's going to go to the to the Shopify shipping income account and then you have the discounts promotions applied to sale Shopify discounts it's going to break that one out and then selling fees commissions and fees related to sales it's going to go into the Shopify selling fees if you want to adjust these accounts then you can map it differently right I can go into here here's my list of accounts I can add new accounts if I so choose so I'm going to close that but but I'm going to keep the defaults here so if you if you've been doing your system prior to this and you already have mapped out accounts then you might want to use those accounts and you can change the mapping here to the accounts that you have set up and then you've got subscription fees what you pay for your Shopify subscription Shopify subscription fees is is dick is where it's going to go and then adjustments channel adjustments and miscellaneous Shopify other adjustments and then you've got the sales tax based on your region Shopify sales tax and then we've got the reserve balance payout balance reserved by channel Shopify reserve balance so that's the general mapping so if I close this back out and I open up my chart of accounts for example if I go down to my accounting down here and I look at my chart of accounts when I set up the Shopify it set up those accounts for me right so here's a clearing account here's the Shopify item here and it set up some of those those accounts Shopify sales tax could have set that up but it's good those those accounts that are mapped out are now over here in the the chart of accounts I've added a bunch of other accounts as well when we've been doing the practice problems so it's getting a little muddled at this point notice if I go in the sales tab and I look at the customers then we've got our customers here and it set up the Shopify customer so it's not going to add all the customers of course again it's just made one customer that's going to be our lump sum customer now also remember there's the same kind of issue with this system as we had with the manual system which is that Shopify is now kind of connecting to QuickBooks so that QuickBooks can pull in the detailed information breaking out the deposit but if you're dealing with other payment processors like a PayPal or a strike for example meaning customers are paying you through PayPal or strike something other than Shopify pay like not using just our credit card for example on Shopify pay or something then you might have other items that are going to be on the PayPal level that you're gonna have to deal with for fees on that level so so this is going to be a common problem with many different kinds of integrations that we that we saw so that's something that you've got to be mindful of as well so just you know so keep in do you have so the question would be do you have PayPal turned on can they pay you through PayPal or can they only pay you through the Shopify pay if you have the PayPal turned on you want to make sure that you have a system that's going to be dealing with the PayPal component of the payment similar process or problem that we talked about with the manual system all right so then if we were going to approve these let's go back on up top into the banking and say let's go ahead and add this one so this one came through we analyzed it and we didn't auto add it we said we want to add it manually so let's go ahead and add it boom the 715 is is in place now I should be able to map that in the future I'll be able I would be able to see in the checking account that 715 and I can map I can match it out but let's see what happens over here let's let's run this for for 010123 to 1231 23 23 this time on the balance sheet so note that it's got its clearing account here but it actually puts the transaction in and out of the clearing account and does put it into the checking account ultimately so if I go into the checking account there's our 7.15 note however if I go back on over here and exit out