France's military mission in Armenia raises concerns amidst tensions in the South Caucasus, Azerbaijan. In the wake of the Second Karabakh War, the geopolitical picture of the South Caucasus has undergone profound shifts with France and some Western nations adopting strategies that are raising eyebrows in Baku. Head of the State Security Service of Azerbaijan, Ali Nadyev has voiced apprehensions regarding France's recent establishment of a military mission in Armenia suggesting that it could potentially escalate tensions and even provoke another conflict. Speaking at an event commemorating the 105th anniversary of Azerbaijan's security agencies, Nadyev pointed out that rather than fostering peace, France's actions seem to be fueling instability by supplying weapons and ammunition to Armenia, which has occupied Azerbaijani territories for decades. Nadyev's concerns are reported by Interfax Azerbaijan highlight the perceived threat of France's covert activities aimed at destabilizing the region. The decision by Paris to deploy a military mission in Armenia has been interpreted by Azerbaijani authorities as a provocative move signaling France's intention to turn the South Caucasus into a battleground. Nadyev accuses France of not only arming Armenia but also engaging in clandestine operations through its intelligence service, allegedly forming spy networks that undermine Azerbaijan's security interests. Nadyev emphasized the vigilance of Azerbaijan's State Security Service in uncovering and countering such threats. He pledged to take necessary measures to safeguard the country against potential destabilization efforts orchestrated by external actors. The rhetoric underscores Azerbaijan's determination to defend its sovereignty amidst growing regional tensions. In addition to addressing external threats, Nadyev highlighted the role of Azerbaijan's security system in combating terrorism and transnational organized crime. He pointed to the expansion of international relations as a crucial aspect of the State Security Service's operational effectiveness, emphasizing cooperation with nearly 100 intelligence agencies worldwide. If the official photos are anything to go by, Emmanuel Macron's three-day trip to Brazil has been more romantic getaway than international diplomacy. Macron's trip to Brazil left him swooning, according to social media. In one photo released on 78-year-old Brazilian President Luis Inácio Lula des Silva social media channels, the two beaming heads of state can be seen clasping hands on a boat while gazing out at the Guama River. In another, they appear to be blightly skipping under the Amazon canopy. There were hugs and handshakes of plenty, smiles and selfies, too. Lula on Thursday bestowed the highest honor for a non-citizen on Macron, draping a medal around his neck. Brazilian social media gobbled up the bonomy with gusto, and users posted photos of the duo that many said looked more like a wedding album than a state visit. On the last evening of his trip, Macron joined in, associated press informs. Some people compared the images of my visit to Brazil with those of a wedding, and I say to them, it was a wedding, he posted on X along with a photo of himself and Lula Photoshopped onto the movie poster from La La Land in place of Ryan Gosling and Emma Stone. France loves Brazil and Brazil loves France. Lula replied to his post with the flags of their two nations and an emoji of swirling hearts. Lebanese Prime Minister Najib Makati mistook an aide to Georgia Maloney for the Italian Prime Minister herself when a delegation from Rome arrived in Beirut, Makati was waiting on the tarmac at Beirut Airport for the Italian leader to descend the stairs from her plane, according to the national news. As one of Maloney's delegation descended ahead of her, Makati greeted her with a kiss on each cheek, apparently thinking she was the Italian Prime Minister that he was quickly informed that he had instead greeted Maloney's personal assistant Patricia Scurdi, who looked somewhat similar to her, the Italian Prime Minister exited the plane soon after, and was greeted with a handshake and a kiss on each cheek by Makati. National news notes that Maloney is in Beirut amid the continuing cross-border conflict on. Lebanon's southern border between Israeli forces and the Lebanese militant group Hezbollah. Italian Nova News Agency reported that Maloney reaffirmed her country's commitment to supporting Lebanon's stability. Maloney also stressed the need to avoid the risk of escalation along the border with Israel and expressed her support for any initiative aimed at an immediate truce, according to the news agency.


Welcome! Let's explore setting up Class Link Sharing Rules. If you're using Class Link with your student information system, or CIS, you can use Class Link to roster your classes in CSaw. Setting up your sharing rules in Class Link allows you to share certain sections from your CIS into CSaw. Each section shared will be made into a class in your CSaw for Schools dashboard. It's important that your sharing rules are accurate. Any data that is not included in your sharing rules will not be visible to CSaw team members or included in your CSaw and Class Link sync. Sign in to your Class Link admin account. You must be a tenant admin in Class Link in order to set up sharing rules. To set up Class Link sharing rules, first you will need to install Roster Server in Class Link. Roster Server makes one roster format data available to CSaw and is where you will configure your sharing rules. Note, this is a different application from the SSO application. In Roster Server, tap Imports, Import Now to import your rosters. If you need help installing and setting up Roster Server, please contact Class Link Support as CSaw will not have access to your data until it is shared with us. Next, add CSaw in Roster Server. From your dashboard in Roster Server, tap Applications or Apps at the top of the screen, then tap Add on the right hand side of the applications page. Search for CSaw and tap the blue Add button. You've downloaded Roster Server and added CSaw. Next, you will be prompted to choose your permissions. For CSaw, we recommend that you set custom permissions in order to not share too many classes or students. The goal with setting custom permissions is to create a digital copy in CSaw of each school that you have purchased CSaw for schools for. After adding CSaw, you will be prompted to set your permissions. Tap Custom Permissions. You can also edit permissions at any time by tapping the pencil and paper icon next to CSaw in your list of apps in Roster Server. In the Orgs tab, all orgs or schools will be selected by default. Unselect any orgs or schools that will not be using CSaw this year. You may need to set the Select by Settings to Select by List in order to make selections. In the Courses tab, select the courses that should be using CSaw. We recommend sharing only homeroom advisory courses if possible. A single class may be split up into multiple subject areas in your CIS for grading purposes. However, sharing multiple subjects or courses in Class Link will create a unique CSaw class for each subject, which can be confusing for younger students. For help with setting up your sharing rules, please contact Class Link Support. Once you have set your sharing rules, check the data you are sharing within Roster Sync using Sanity Check. Tap Applications and find CSaw. Hover over the box next to the paper and pencil icon and tap to run a Sanity Check. Sanity Check shows what you are going to share with CSaw. CSaw will only be able to view data that is visible in this Sanity Check. If something is missing in Sanity Check, revise your sharing rules. To make sure everything is correct, check that the number of students matches your CSaw for Schools subscription purchase and that only the correct classes have been shared. Your data will not automatically begin syncing with CSaw. Take the time to make any edits you need to your data in Class Link. Once your data in Class Link is accurate and ready, you can reach out to CSaw Support to have our team review your data. For your data to begin syncing with CSaw, you will need to manually initiate a full sync from your CSaw Roster Sync dashboard. This begins the flow of data between Class Link and CSaw. Once your first sync is complete, data in Class Link will be exactly matched in CSaw. That's it! That's how you set up sharing rules in Class Link. If you need assistance with your Roster Sync dashboard or with your first sync, reach out to CSaw Support. Find more setup steps and resources here. We recommend bookmarking this page for quick access. Thanks for joining us today. See you again soon!


My can you check your audio and video for us? Sorry. There we go Cool. Thank you. Yeah, can you can you see me? Okay? Yeah, can you hear me? Okay? I can all right. I'll mute it and stop Thanks. Well, it looks like it's 11 o'clock. So I'm gonna call the meeting to order I'm gonna call to order the July 5th meeting of the subdivision development advisory committee By way of short introduction. I'm Charles Carter. I'm on the planning commission and I act as chairman of this this Committee which is subcommittee to the planning commission any decisions by this committee are Appealable to the planning commission in the city of Santa Rosa The first item on our agenda is public comment and less Lonnie you have anything else I need to cover Okay, so this is the portion of the agenda where Take comments on items not listed on the agenda So if there's any member of the public here that wishes to speak to this committee on any item Not listed on the agenda. This is now the time if you wish to make the comment. You can raise your hand No comment, and we don't have any participants via zoom. Okay? Then it does not appear we'll have any random public comment I'll close the public comment period and move on to the schedule item scheduled items on our agenda The first scheduled item item 3.1 is a public hearing for a parcel map waiver certificate of compliance for 1042 hopper avenue file C C 22 dash 002 Is the planner here Yes, I am via zoom. Can you hear me? Okay We can Yeah, so good morning. I'm mike wixen a contract planner with the city and I've been facilitating this project through the process and So we'll start with the presentation just generally where it is that It's on hopper avenue 1042 and 1050 hopper avenue The project itself So this is slide two connor Um Is to Redivide six parcels that's consisting of about six acres a little bit more And we'll then recreate three new parcels one of 2.2 acres one of 1.1 acres and then parcel 3 would be 3.18 acres um The project itself is in a light industrial zone And a light industrial general plan. So we're reviewing this against the standards of the light industrial zoning district And then ensuring its Yeah, in conformance with the general plan land use designation Um the required entitlements are a tentative map with a parcel map waiver So that is what has been submitted and is in front of the subdivision committee this morning So if we can go to the next slide Uh, the next slide shows the location of the project site relative to the land uses around it that are existing in it So this is the aerial photo South hopper avenue Pretty much all the way around it is light industrial uses right now There is a an apartment complex immediately to the east And if you follow that blue line on the east side of that project site Basically to the right of the star It's it's that third parcel right in the middle there that I believe is the So it's an apartment complex use right now as a residential use So if you can go to the next slide, please And this is just a blow up of the project site And you you can see that the site has been developed And it's primarily storage buildings and then light industrial uses within the storage buildings There's a small little area up front at the northeast corner That might be developed in the future at some point but For the most part the site has been developed and uh is being resubdivided To facilitate some new financing for the project site So go to the next slide, please Again, I mentioned it was a light industrial general plan land use designation And then also a light industrial zoning designation And this is just meant to show the surrounding land uses And as you can see the red To the left, you can see the red is a commercial general commercial services land use The light or the white is light industrial land use and then Kind of the darker brown just to the north is a I believe it's a medium density residential And then to the left is a single family residential land use But you can see right now that it's pretty much like a It's it's pretty much a commercial or light industrial surrounding land uses And then also Uh the same with the zoning commercial or light industrial surrounding zoning designations So if we can go to the next slide, please So this is the tentative map itself and it's Colorized this isn't this was done by staff just to kind of highlight And make it more visible to see What's going on here? And so you can see the red lines are showing the new proposed property lines relative to the green buildings And then the pink area is basically a series of Easements for both access and then utilities And uh, and basically you can see lot one I'm sorry. Lot lot one is on the left side Kind of runs north and south lot two is in that northeast corner And then lot three is that leftover area in the southeast part of the site Plus a little bit more um, but basically the buildings are again all compared and The design and configuration of the lots are all compared against the current building code. Sorry current zoning code standards and just making sure all the zoning code setbacks are met and Other issues related to development standards for zoning And staff has found that this project meets all the zoning code standards um, basically one of the unique aspects in this particular zone is that The the creation of these lots Will establish the setbacks the new setbacks That then become used going forward for any project So each setback is shown on Each particular lot and those setbacks will then become the setbacks going forward And that can always be modified with the new project that comes in so if new buildings are constructed That can always be evaluated and then are re-evaluated and changed at that point in time So if we can go to the next slide, please Basically in the environmental review component of this project, it's a categorically exempt project It's a minor land division So no further sequel analysis is really needed for this project And I have to go to the next slide, please Um future development will be required to meet the zoning building code requirements at that time And at this point, there are no unresolved issues Um staff hasn't received any communications regarding the project I'm sorry. That's on the next slide And so at this point, we have no issues. We're recommending approval of the project with the Resolution shown in front of you and then also with those conditions recommended both by planning fire building and engineering And if there's any questions, I believe cleave is there And uh, he's from the engineering division can help answer questions For engineering. I believe bill sumski is there as the applicant and then related to planning questions or issues I'm happy to try and help answer those as well And that would conclude the presentation Okay, thank you mike before I proceed With any questions or anything I should We didn't do the x parte and I'll disclose that I have visited the site as part of that Any disclosures from the other committee members? Um from engineering aspect, we reviewed the project and it complies with all the city code All seems I know the subject of that So no additional comments from staff. I'm assuming uh, is the applicant here Do they wish to make any comments or a presentation at this time? I'm here for the applicant. Okay I don't have any other comments Maybe we'll have you state your name for the record. I'm sorry Judy Connor. Thank you. Thank you So I guess we'll move on to the public hearing and open the public hearing on this item Do we have anyone on zoom our conference call for the public comment period? Yes, um We have two participants. I believe one of them is um Part of the applicant team Um But if you wish to make a public comment via zoom you can do so by raising your hand There's a raise your hand icon feature at the bottom of your zoom screen And if you're calling in please press star nine Chair Carter, there are no hands raised at this time Can I assume there's no one here In person that wants to make any comment on this public? Okay, but that said I'll close the public hearing on this item um And as the secretary would call for a vote Okay, um cleave gritty Tara carter I um, and then mike wixen Hi Okay, so this passes with three eyes no naves and no absences. You're welcome We'll move on to item 3.2 It's a public hearing for parcel map waiver And certificate of compliance for 2248 gernville road file cc 22003 It's to reconfigure an existing legal parcel into 10 new parcels and we have Planner connor mckay here for the presentation. Thank you chair carter. Good morning everybody. Um, you know like Chair Carter said this is a parcel map waiver located at 2448 gernville road This would divide a single legal parcel into eight airspace condominiums with a common parcel consisting of the parking lot No change in land use and the required entitlements are a parcel map waiver certificate of compliance The building the subject property is currently an office building With some single family and multifamily residential uses Scattered to the south and the west Here is a zoom in on the existing office building I kind of cropped the general plan and zoning snippets a little bit too heavily, but you can see that the general plan land use designation of the site is office and the zoning district for the property is office commercial Like I said the surrounding areas are primarily residential and office spaces as well Here we have the site plan you can see the parcels are being divided into airspace condominiums like I mentioned with that common space being the parking lot This project was also found reviewed in compliance with the california environmental quality act Categorically exempt pursuant to the minor land division section We have not received any communications about this project and can make the required findings to recommend approval And i'm available for any questions Is there any other staff within the additional comments or questions for staff on this item? Okay, is there a representative from the applicant here? Okay, do you wish to make a presentation or make any comments at this time? um Not at this time, but I could respond if someone else has questions. Okay. Can you uh state your name for the record? Yeah, josh hammer thank you um With no questions from staff or comments I guess we can open the public hearing on this one. Do we have anyone Standing by by phone or zoom Um, we do have somebody via zoom. It looks like they're raising their hand carol um, I'm not sure if she's part of our staff or um member of the public Okay, um, can we get the public hearing timer up then? Yes Give me one second. All right. Is are you carol dugas? No carol small and member of the public Okay, give me a second to get the timer going. Okay. I'll be brief Alrighty, uh, go ahead Yes, hi I um am a resident of the pinebrook town homes. It's to the left of where the well to the west of where the um proposed air condominiums are can someone translate what that means is that a mobile home? um Lots or what exactly is an air condominium? Carol if you have more questions, you can keep going and then once your public comment period Is over then we can um address your questions or concerns. Okay. I just want to kind of understand the impact um on the little um, I think it's 54 or 58 um town homes that exist very close by And how long the construction is estimated to take or the demolition Do you have any more questions carol? No, thank you. Well, thank you for your questions and comments I think we have uh representative of the uh applicant here who can respond to that question and we can follow up with staff comments as necessary Go ahead sir. Okay. Yeah, I think there there's a lot of um Maybe people around don't understand quite what's happening And so I just wanted to shed a little light on that and clarify There there would be no building no construction No changes And no changes to the use of the building it would still be all the same Businesses that are in there. It's primarily dental and medical offices that are in there And so that would all stay the same The process of this is just to make it so that the businesses that are already there could Buy their section so they they could have ownership of their section So it would just be dividing what's there everything stays the same rather than they're just being One ownership of the whole building. Uh, just the individual there would be a condo association But it wouldn't be for residential would be for the exact same type of businesses that are there And um, but those business owners could then you know have some ownership in in their office And I'll add um any future Residential development would be subject to um permitting requirements and currently the zoning district is office commercial Which is generally pretty limited as to what can be developed for residential uses Um, so if there was For some reason a plan in the future for that it would be a completely separate process And this process has nothing to do with any future residential development Thank you Thank you So just in summary what we're hearing is it's a change in ownership status And there's no proposal for change in land use or new development with this project So just to clarify Um, do we have any further public comments? Um, that was it. We only have Carol participating via zoom. Is there anybody else in person who wants to make a comment? Sure. Um, go that out Ready Would you define the airspace condominiums again, I can't quite wrap my head mind around that it's just Mr. McKay Yeah, I'll take a crack at it. Maybe thank you my engineer friends can correct me if I'm wrong But my understanding is that a stand a standard parcel is lines on the ground um an airspace condominiums is basically creating Parcels that are on top of each other. So the airspace is that there's technically a legal lot that's In the air above an existing above a separate Parcel so it's basically like legal lots that are on top of each other And it's common in residential condos, but in this case It's creating an office building where individual tenants become owners of Their suites in a larger building Okay, that helps. Thanks. And then the the parking landscaping those are all held in common by the the condominium owners of the individual office spaces I haven't heard that term before yeah condominium most folks Assume residential, but this is an office condominium Thank you uh See no more Hands raised for public comment. I'll now close the public comment period on this one and Ask the secretary to call for Gabe were you working on this one? Okay, Gabe Osburn. Hi Chair Carter. Hi Connor McKay. Yes So this passes with three eyes No nays and zero absences And just a reminder that this decision is final unless it's an appeal is filed with the planning and economic development department within the next 10 calendar days Hey, that brings us I'll give you a second during for Uh item three point through public hearing Parcel map waiver and certificate of compliance for 2498 Kernville road file cc 22 dash 004 I will disclose that I have visited the site and ask other members of the committee if they have any exparte disclosures I have not visited the site Good morning. This is my name is norbisla and the project before you is a request for a parcel map waiver certificate of compliance for 2498 Kernville road The proposal would split the existing law into two separate lots It is currently a 0.86 acre parcel with a bank and a veterinary hospital on it The site is zone neighborhood commercial and the general plan land use designation is retail and business services Here's the site plan that would divide the existing law. It would be split Down the middle here and there's sufficient parking on both sides The proposal doesn't need all city code requirements including parking and setbacks The project is categorically exempt from the california environmental environmental quality act as it's a minor land division And therefore it is recommended by the planning and economic development department that the sub subdivision committee approve a certificate of compliance To divide the property at 2498 Kernville road into two lots For any questions, this is my contact information. I do believe we have a representative of the applicant team on zoom as well and cleave was the engineer on this project So he can answer any engineering questions. Okay Let's see I'm good. I I do have a question. I'm just trying to figure out when's the best time to ask um, I there was not a formal parking analysis within the staff materials for this particular one and if I just look at the The proposed map I see 30 something parking spaces on one site in about 11 or 12 on the other um Can we confirm that those that the parking on the resulting parcels will Comply with the zoning requirements. Yes. I don't have the exact numbers um off the top of my head, but I did compare them to city code with the appropriate land uses that On both sides. Yeah in total it looks pretty certain. I it just looked like there were far fewer parcels are parking Slots on the one side than the other than the bank on the bank side and on the veterinarian side Is there a representative here today that can shed a little more light on that? I'm not seeing him on zoom. Oh, okay My name is rick swent on what's bk of engineers So I can address any questions you have rewritten the site. Yeah, just the driveway going out of the bank site there's a bunch of parking spaces on both sides yet those to the South appear to be across the property line. Can you Perhaps on the site plan show me how the parking is distributed for the two parcels I believe that the based on the usage Be honest with you. It's it was addressed based on the existing conditions I don't think there's any there are no proposed changes or anything with these buildings Understood. Um Miss bees look if you could put that site back up there So if we look at the driveway in the middle Uh, there are some parking with the angled parking some angled parking against the bank parcel And then some angled parsing Some angled parking on the other side this right there Those are across the property line and they seem to be Are oriented for use of the other parcel Did you have a chance to look at that in terms of numbers? Numbers wise on either parcel there is enough parking for the use I don't know the exact number that would be required, but I There was an analysis done with the city code I could speak a bit to it on this one our engineering conditions approval we wrote Um, but the afghans engineer surveyor Shall evaluate the need for any easements And we make a reference to any parking Access easements cross a lot. Okay, that would be needed. Um, and then those who need to be submitted with a separate subdivision map or Um separate instruments with like legal descriptions and plots great that that's that's what I was looking for so if If that's in the conditions of approvals, I think we can As I said, I think in total we've got the number of parking, but it looked like it might be an easy situation So thank you for including that engineering department So with that all my questions have been answered. I'll go ahead and open the public Comment on this item where the applicant or members of the public can make comment Sorry, give me a second here Um, is there anybody in person wishing to make a comment? Um, if you're attending via zoom and wish to make a comment, please raise your hand You can do so by selecting the icon at the bottom of your zoom screen Chair Carter, there are no hands raised at this time. Okay So then I will close the public hearing on this item And ask the secretary to call for the vote Uh, gave Osburn Clape Granny Chair Carter. I Uh, nor B's left. I That passes with three i's no nays and zero absences Once again, this decision is final unless an appeal is filed with the planning and economic department within the next 10 calendar days and uh That concludes our meeting for today


In one of its most inspired moments, the United Nations decided to set aside June 5th annually for reflection on the environmental state of reform. The Ministry of Environment in collaboration with critical stakeholders have developed a national strategy for the phasing out of non-bound degradable plastics. The Ministry has also developed a national plastic waste recycling programme involving the establishment of plastic waste recycling plans across the country. Nigeria is in a good place to lead Africa and indeed the world in beating plastic pollution. There is no need to reinvent the wheel, there are a good number of effective initiatives already that we are considering as we develop policies.


Like, I often don't know if I'm going to get a book of your thought and if I'll have comments and I'll not. Me too. I'll not ask for it. Right. Yeah. That's fine. Well, I think that's a good point. Well, and they don't understand this. They're like, why did you come to this? You really have a problem? It's a problem. You know what I mean? A diffusion is not, it's not, it's not a squirt. It is, right? It is. Well, I would argue that an idea is a game. Oh, right. It pertains to pure speech for me. Right. I mean, there's nothing in your numeric about it. Definitely. But I'm sure the situation in French will be worse. Is that okay? Yes. No, in the French, when you get to the second meter, you mark the situation and you start making new comments. I don't know if I'm doing it right, but I've been wrong before. I know that there's still a lot of things to do. I know that there's still a lot of things to do. I think that's a good point. I think that there's a lot of things to do. There's a lot of things to do. There's a lot of things to do. I mean, if it's no other unidentifiable. Pure speech. No, it's not. It's totally just something I've never heard of before. My understanding is that it's just a huge, intractable problem. Intractable problem. Where every time they approach it, they realize... It's just a matter of... It's like we should know these are both... It's a very annoying piece of... No, I mean, what I mean is that... Gid is Gid. And then you put your eyes on Gid. So it's a lot to me because I'm multiple. Oh, except that Gid is a... Gid really has no concept of this sort of social kind of... I actually have a lot of my life. There's some things to do someday to...  I want to see the conversation that it was all about. That's what I want to see. And it's a true thing to do. Amen. Thank you. Yeah, I mean, I've not seen that done. But I'm sure they make sense. Maybe it's Microsoft. It's me. Any time you want to start. There's nobody here. Even better. Even better. That's right. Well, yeah, we've been doing that. We have Cordo. So Chase and I have a presentation. That's right, Chase. You're part of this presentation. Yes. Last year... Is somebody supposed to be here directing this? I think it just goes and whatever it sees, it sees. I don't believe it's recorded. I think we're supposed to have somebody try to take notes underneath your pad. There's probably some lists somewhere of things we're supposed to do. There's my card. I don't know if I'm still looking. It's smaller. Yeah. Somebody can yell at you at the same time. Yeah, if you find the schedule page on wiki.org, I think there's already a hotline. Do you mind watching IRC? Yeah, on the off chance that there's anybody on the planet. Hello, planet. Yeah, so about the time of Wikimedia, whatever it was, 2016, and... We were all in an IRC channel being upset that some tools were dying. And I said, God damn it, I should make a presentation and give it at Wikimedia. And this is my second dry run before I try to do it in Montreal. But the format here is quite a bit different, I think, than the Montreal one, where I will be talking out to people who are largely the editor community on wiki. What I really like from this talk is more ideas about things related to what hopefully we'll set up here at the beginning. So, developing community norms provide lots of tools, or don't let your brother-in-law be the only person who keeps your community running. At the beginning here, Chase is going to have to talk, because he needs some slides. We can go quickly. Some slides about language norms. What are the terms we're going to be using? Everyone, I think, here knows, but it's better to be explicit. So we have OpenStack Cloud, which we use as a service. You can have a DM or a project that has quota. And we, being the foundation, have our own sort of projects, which we run officially and unofficially, I would argue. Next slide. Tool Labs. Tool Labs is one of these projects. And it's a low-marrier-to-entry environment where you can, in theory, run write code and run it with the minimum amount of pop-up certain states. And then there are a lot of things running on the platform. We have long-running bots, short-running bots, one-time bots, recurring bots, which I guess would be scheduled by jobs, head-off process. You've got a bunch of people doing research, and then you have somewhere in excess of a thousand different web services that are written by everyone. We use Tool as a generic for all of these things. I think officially, when we send out the annual survey, there's officially a sense in there that says, we don't have a definition for what Tool is. It's all the things. If it's like a distinct entity that is meant to be run on the platform, then we call it Tool. And then it's really ham-fisted to put open source up at this conference. But the reason I did it is because as far as making our code available, we just stink at it. We have tons of people who have written all kinds of really important bots. And wherever the code lives, if they've deployed some binary thing half the time, we don't know. And the worst part about that is that historically it's just been fine. We've just kind of rolled with it. If you wrote something that now with media Germany depends on for all of their work every day and no one has the source code to it, historically that wasn't viewed with sort of the evil eye. Now it is, that's what we're saying. And then just what norms are basically expected behavior, community standards, technical, non-technical. So this is kind of a thesis for the talk that was basically happening. The tools are actually a vital, it is to say critical instead of vital, and MC gave me a whole bunch of run around about the word critical. So the word critical became vital. But a vital resource for automatically content creation and curation activities. This was kind of the rallying statement that got me the job that I started in April 2016 as community tech's outreach liaison slash helper, slash whatever to the tool labs environment. And I have some stuff here that I think to some extent backs up my thesis. Maybe it doesn't prove it. This is a number from a 90 day period from September to November of 2016. 24.67% of edits across all the keys on all the media run properties originated from IP addresses in the labs environment. If I had my speaker notes here, I've got some breakdowns too, but it was wiki data was on the order of 50% of wiki data and it came out. And I think just under 8% of the wiki edits. Is 53% of wiki data and 8.9% of the wiki. Thank you. And another for basically the same time period of 90 day window, 3.8 billion individual API requests originated from the labs IP space to the wiki media farm. And again, I don't have my speaker notes. I think this was about, let's say on the order of 10% of all the API requests that were made in the Action API. I like this number because any time you can say billion, it's pretty quick. And here's something that's a little less like Lucy, let's throw up some random numbers. So, Africa was a co-author of a paper in 2013 about CluBodyNG, which is just one of the up team Zilean bots that runs in labs. The time period measured was the first quarter of 2011. And the bot at that time was having some, it would go up and go down and go up and go down. And so he had this data that he could look at when it was up and CluBodyNG was doing what it does, which is basically revert things that look like obviously bad edits. The meantime to revert, it's about 12 and a half minutes for an edit that was eventually going to disappear to disappear. And when it was down, that time came close to double, so the bots a lot faster than human beings. But one of the interesting things in the paper was that things did eventually go away. So the bots aren't critical, but they're critical. Well, this is just one bot, right? I know most of the people who watch for edit revision history do some of the other bots. Yeah, this is just whenNG is just one very, very, very weak AI. It's just a little collection of characteristics that basically, if it sees an edit that blanks a page and says no, you can't do that. If it sees several other kinds of things like that, it backs them out. So, all tools are unique snowflakes. We have 100-ish tool accounts. Some are maintained by full-time professional software developers. Some are maintained by somebody who figured out how to use Stack Overflow last week. And I don't mean that to be disparaging. It's just the reality of it. Some tools have multiple maintainers that have 10 or 15 different people that will show up and fix them. Most tools have a single maintainer. Some tools use version control. Most tools don't. Well, that's maybe a little bit too much. Some do, some don't. They're written in just about every programming language that I've ever seen actually used to do anything in the real world. We have one that's written in tickle. But not just annual tickle. It's written in a custom compiled tickle that does something different than any other tickle that ever existed. They don't mean any of that to be disparaging about how anything is built or why anything is built or who does it. Everybody who's doing things in tool labs is doing awesome things that are within the bounds of capability and time and other resources that they have. But there's no, every tool is E-neased. There's no prototypical tool. There's no, this is how they all work. In this great and varying ecosystem, I've noticed a few things that go wrong more often than I would like them to. And so I've got two stories. And again, in the Wikimedia version of this talk, this is the meat of the whole thing. It's telling these like, there was this thing and this thing and this thing. We're going to kind of fast forward through that, but we'll get a little bit of it. So the first one is just the tiniest little thing, but it's the hugest thing. There's a tool that exists, it's a web service, and it does KML data files. So it makes data representations that can be overlaid on Google Maps or Google World to look at things. And it's used to extract geocordinates from articles and then make these overlays. And it is, there's a template on Ian Wiki, there's a template on German Wikipedia and several other Wiki, pretty large Wikis that have pretty highly transparent templates that make direct links in this tool. And it started having some problems. It was having frequent out-of-memory errors, it was crashing. People cared so much about it that they came on IRC to find us and say, hey, can you restart this web service because it's down? UV and Alhalla both over the course of about two months spent at least a week's worth of time trying to make this thing better, trying to keep it up, moving it. It was one of the first things that was moved under our Kubernetes service because we thought that the Kubernetes system would be more robust and stable for it. And things got better, but it wasn't great. And it got to the point that somebody filed a fabricator task proposing basically a rewrite method to fix it up. And the reason that they went that far was that they had tried on Wiki and on Fabricator to contact the sole tool linkator and give them to provide some information. Nothing happened to that initially. Eventually I noticed the fabricator task and I went and used my powers of bugging people every five minutes until they pay attention to me to get a response from the original author. And he had a perfectly fine story. He said like, hey, you know, I made that thing and it's cool that people use it, but I'm not interested anymore. I'm over here working in Wikidata now and I think they're doing better than some geo-coordinates. So I don't really care about that thing. But hey, if anybody wants to take it and take it over, that's fine, they should do that. And one of the problems with that that I pointed out in the request to him, there was no license for the tool. So it was a single Perl file sitting in a directory with no license information in header, no license information in body, footer, inside and anything. And his, their response on Fabricator was, yeah, software licenses, I don't know, just do whatever you want with it, I don't care. And the reason it's really bad is that we can't just do that, right? Just like I can't take some random thing I find on the street and put it on commons and say, well, I don't know, I found this thing on the street, nobody was looking after it and we need to take care of it. So it's on commons now, right? Like the communists would, rightly, you don't have license, you don't have ownership, you can't do that. In the United States, if you don't provide a license and you don't somehow release your intrinsic ownership copyright, I have to wait until 70 years after you're dead to take over your stuff. And that 70 years number is just going to keep getting larger as long as the mouse is still around. That's a little thing, that was supposed to be short, but it was really long. So this other one, I keep making eye contact with Brandon because I knew this slide was coming. Not a little thing, this particular death of a tool story is about one where every little thing all happened over the course of 283 days until there was no more that we could do for it. So there's a bot that's a very active editing bot on German Wikipedia. We noticed as we were doing the wind down tasks for the conversion from HTTP to HTTPS that this particular bot was pretty high on the leader list of things that we're still making on a regular basis in HTTP connections instead of HTTPS. And so I think Brandon made the first contact, Brandon pinged the author on the mega tracking bug that we were doing about all the things that were on the leaderboard. And the author showed up and said, hey, yeah, I'd love to fix my thing, but it's written in Java and you guys have a crappy old version of Java, and I just can't fix my code with the crappy old version of Java that you're running that thing with, 1.7 running on tool apps and they wanted 1.8. So that was written down, kind of got lost in the noise a little bit. I don't think we condemned it the author very well at the time, but we had already by this time investigated a Java 1.8 upgrade and had a pretty detailed task that laid out. These are all the things that we look for about how we can fix it and we can't do it right now. A couple months went by, we looked at the scoreboard again. I think at that point this particular user was the number one. I think we knocked off the ones above them and they were left at the very top. Pinged them again and fundamentally got the same response, moved on with their lives. Another month went by and another user who had been watching the mega tracking bug filed a new bug again asking for the Java upgrade. Again, I think the haul of this time went through and did try just about every idea that we could try to try to figure out how to get Java upgraded. The story kind of goes on like this in these bad circles and I'm not telling it with near the force that it makes my stomach hurt. We could upgrade the OS to get Java 1.8, but I think Redemption wouldn't work on it. If it stayed with Redemption, it would work but not get its job. Right, it was Redemption based. Yeah, that was basically it. So then we were getting near the end of the time window when we said we were going to keep the secret loophole open that kept all this stuff working. And I finally looked into what did this mock do because it was making a lot of requests. Were these requests actually useful and that's when I found out that it performed like two-thirds of the archiving tasks on all of German Wikipedia, like daily, weekly, monthly archiving and all kinds of other things.  So I tried reaching out to the author again and I didn't get any answer. So then I actually went and contacted Wikipedia Germany and see if they could hook us up with the author or with somebody else who would know something about it. We were at the Anyone Who Cares stage. Yeah, this is about probably about two weeks from shutdown. The last, like, really big blocker that we were in though. And we found out the author was on a wiki break, not a wiki break that they really wanted to be on, but they were on a wiki break and there wasn't really anything they were going to do about it. So we weren't going to be able to get their help for a while. So after much hemming and hawing about this isn't my job, but damn it, somebody's got to do it, so I rolled up my sleeves and jumped into the tool using the superpowers I had at the time as a co-container on tools. And found out that, yes the tool was written in Java, no there was no visible license, and no there was no visible source code. So there were compressed JAR files and shell scrapers that executed the compressed JAR files. So the first thing we tried was we tried to write our first proxy. We tried to make it not be Brandon's problem and instead be my problem and push him in between. That almost worked except some requests were getting redirected. Actually no, the majority of the requests were getting redirected, some were getting proxied. So I decided, okay well as long as I'm playing the hero, let's really play the hero. And I decompiled the JAR file and figured out what libraries he was using and found that he was using an Apache wrapper over the HTTP connections that through the beauty and wisdom of whoever wrote it in the Apache project didn't recognize, by default did not respect the standardized proxy flags that you can give to Java. But instead offered an opportunity to write your own custom shim to tell it how to use a proxy. That's pretty much the end of the story. At that point I was not willing to... There's one more minor point that you did too. At one point I was taking the author to claim that he switched over his license, then he was in a lower license. That was his whole statement on it, but then we're providing an indirect switch for us as well. Correct.   There's an even longer version with more parts about this, but the perfect storm is that there were lots of little places along the way. The shutdown date was 283 days after the first contact date and there were lots of places along the way that something could have been made better by somebody if we'd done something. But it didn't happen. The bot got shut down. Luckily, during Wikipedia it still survived. Some people came in, wrote some new bots, took over the tasks. They were boosted savers to kind of loop some people in and add desperation loudly enough and also said... So the whole process of reverse engineering one single bot, it's completely not scalable and there are so many bots tools in this sort of state that if there comes a time when it's just not possible for the Royal League or people to do this continually. And so we essentially told that we will do anything to help you, but we don't have the ability to reinvent those. It must be important because they found people. Yeah, it must not have been that hard to fix because as far as I know like a week later... It was quite fast, yes. So yeah, thinking about that, that was about the time then that this talk came into being right around then. And one of the things that I talk about as those couple of examples and we have some others that have existed is that there are a few, what I think are pretty simple norms that we can borrow from most open source culture and try to promote that might help with these things. So this is kind of the list of things that... Again, I'm going to be speaking at Wikimedia too. Trying to get the body prover groups and the various groups that are on the Wikis that interact with these things where they turn into a giant pile of myths to try to kind of like adopt and promote to people. Pick a license. I'm going to work on... It's on my personal team roadmap for this January to March quarter to actually make that easier to do. And actually to try to integrate it into the act of creating a tool account itself that when you say, my tool is named foo, its license is bar. And if you don't put in a license, the former just keeps coming back and saying, like, no, I'm sorry, I don't see a license here. You need to have a license. And obviously, you know, like a lot of tools are hard to pick any license for so it won't be like you can't have another file that's in the directory that's underneath another license. If there's no license stated, this is the default license. Well, and it's worth noting that it's technically always better this way. We don't run code and it's not available to the source. It's just no one ever really worried about what that meant. You know what I mean? You can't run code source code on the platform, but we have code which is not available.  Yeah. And it's fundamentally an enforcement problem, right? Like, we don't self-merge except, well, we all self-merge. So we're going to try to make it harder to get around that particularly. To publish the code, I'll make a tar ball once on every third Wednesday and put it somewhere. Use version control. Hey, I've got tools and I'll be glad to help you use version control. Do something. You and I have some ideas about lowering the bar for this even farther for people who don't like version control systems. Have multiple maintainers. This is one of the big ones for that. Both of them really, but fundamentally for the second use case. If there had been one other person on the planet who had any idea what this tool did and any idea how it did it, they probably would have also had source code. And they would have been able to either work on fixing it or help us help them learn. And that leads, I think, to multiple maintainers and to write some documentation kind of code hand in hand. We've made a special namespace on Wikitech in case there's nowhere else in the world that you can figure out how to document your stuff. Write down, how do I start this thing? How do I stop this thing? And ideally, again, some idea of what it does, what other resources does it use? Does this melt when redness is gone? And Chase said this last one, and it's a good one. I feel bad that I hadn't seen this last bullet point when I was writing things down before. Participate in the community. And by community is a loaded word, especially in the Wikimedia Foundation. But particularly here, we mean the Tool Labs Developer Community. And I think the next slide, here's the Labs Developer Community. We've got some mailing lists. We've got an IRC channel. We've got Wikitech Wiki. And once a year, two years running, so we can actually say annual survey now. That's great. We try to do a survey to ask you, like, do we suck? Do we not suck? Do we do something good? Do we have some feedback? It may not be highly visible yet how we're actioning on those surveys, but we do talk about them a lot. We're using them to change some of the direction as slowly about where we're going. So then, we've also been working, the whole Tool Labs community's been working with me kind of being the ringleader over the last six to eight months now on filling in some policies that were never there. Just stuff that nobody ever got around to make it up before. So we've got two that went through drafts and comments and reviews and all the way to RSC votes on Meta approved by the community. In the final stages now of both of these policies, I'll talk a little bit more about them, involve a volunteer committee to help make them happen, to help get action on them. And we're in the final stages of putting together that committee. So hopefully over the next couple of weeks, we'll be able to send out some nice announcements about yours or shiny new committee and your shiny new policies. Let's do some stuff. The two that came up with the right to fork policy is kind of a codification of our existing open source requirement. And what it fundamentally says is that every tool has to have an OSI approved license. You can do a license if you want, if you want to do it under MIT plus what the public license. You can do that, but one of them's got to be an OSI non-crayon license. That's the only must in the policy for a tool maintainer.  Should publish your code. Should have multiple maintainers. Should, should, should. And then the place where the committee comes in, then it defines for anybody who's not the maintainer of a tool a path to say, I would like to make this tool better. And I've talked to the maintainer and they don't want me to fix their tool. So I'd like a copy of it to start from. I'd like to fork it and go do my thing. And it gives a procedure, a general checklist procedure about how to do that. And then the place where the committee comes in is that the committee is kind of the arbiter between the current maintainer slash copyright owner slash whatever, and the people who want to do it to try to facilitate that and get it done. And the abandon tool policy builds on copyright fork policy. I would really like to see people fork. Yeah. So part of that whole deal is sort of born out of some social etiquette particulars that come up quite often, which is one user has a tool, someone shows up, it's down. We haven't seen the primary maintainer in who knows. But that's not unusual. We have people who do it only when they're at college. We have people who disappear for six weeks during the holidays. Every schedule you can imagine. Not being able to get a hold of someone for a month is not crazy. But what do we do? It's somewhat not polite to just add a co-maintainer for them without talking to them, but yet their tool made me try. And historically we've sort of gone with a desperation slash consensus model, which says, if a bunch of people show up and say this is important and no one who knows about it is around and you're willing to fix it, then we're gonna add you and we're just gonna do our best to let the original people know because that's the best we can do. But with some kind of, I don't know that oversight's the right word, but with some committee in place to kind of keep everyone honest and so that folks know up front. If you wrote a thing and it's awesome and people are really using it, try to be communicative because if not, you may end up with a co-maintainer. So I think it's sort of around just establishing these social norms that are so odd because we have so many state projects and the people who control that may or may not be available depending on the place of the living. Yeah, so that forcibly adding a co-maintainer is step one in the abandoned tool policy. That's adoption. And then if you adopt successfully and everything goes well and the original maintainer never shows up or the original maintainer comes back, definitely. Is there a kind of co-maintainer if you're more responsive when it's at 60 days or something and you're gonna start a co-maintainer? Yeah, we put some stuff in there and we tried to strike a balance between long enough that it was annoying that people wouldn't come in like five seconds and sit down and say, like you need to put me in there now, but not so long that the tool is down forever. What is that first way of time before we might look at the co-maintainer? I think we... It's written in the policies on what you're taking. It's 14 days, which three various drafts over a year and a half that went from 90 days to three days that I think we did at 94. So that's... Yeah, I mean... And so that's for the... There's like two stages of the abandoned tool. There's adoption and usurpation. And so adoption is you get at it as a co-maintainer and you can go in there and try to fluff it up. And then usurpation is now it's yours and you can kick the old person out. And that can't happen. There's a much longer timeline for that and a whole bunch of the things that are shoulds in the right to foreign policy have to flip to musts. So you have to basically show that you're an exemplar maintainer and you're doing everything just right and okay, now it's yours. I think that we... The tool at that is not all of which by any means are foundation employees pretty much always deserve the right to go and kick it then. So that's just part of the deal. Yeah. And we'll see how it works. Like this is a policy written on a wiki. So we can make changes to it as it goes along. That a big part of both of these for me too was putting a volunteer committee in control. This is not WMF action by fiat. This is your peers who are doing the same things you are who are all the comedians and they're taking care of it. Speaking of which, there are people on these committees who are here. They're not in this room. So... You may watch this video later. Oh, you're here. No, no, I'm not. I had a question. So would this be a long wiki process, some of it like cross-prediction or something like that? Yeah, we think very similar. So that part is not strictly codified yet because I want to get the committee together and let the committee do it. I basically want to treat them like the storage group. These are really smart, dedicated people who are going to do good things. So let's give them some space and let them figure out what's going to work. Because again, it's not my radio. It's not the WMF's baby. This is about full-labs community building. Yeah. And there have already actually been suggestions that it gets expanded beyond full-labs to all of labs. But we want to... Let's crawl before we run. Extensions. Yeah. Yeah. But on wiki, it's not such a big problem. And extensions, it's not such a big problem, right? Because an extension doesn't go on to clustering lessons in Gary. And when it's in Garrett, it's owned by everything. Somebody may be the one that we look to, the plus two things, but it's owned by everybody. Tools, again, because every one's a unique snowflake, they're a little different. So yeah, it's better to adapt, right? We don't know that these rules are going to work. I don't know that the proposed FOSS kind of guidelines are going to work. But we want to get started and then fix it as we go along. I think the committee ended up being seven people. Yeah. None of whom are foundation employees. And we got to turn... Oh, wait. Okay, one person. I assume that's Nick. Yeah. And we turned people down. So there's interest. That's the interesting part. Yeah. Yeah, this was all really much better received than I had been led to believe. It was going to be when I started off til they get the window. So this is really... Now we're at the part, and hopefully I didn't burn up all the time just sweating and yammering up here. Now we're at the part where I want feedback from anybody who's interested in giving feedback in this room about, like, beyond what I've talked about, what are we missing? What else can we do? Like, what kind of tools? So, like, one thing I think would be cool is to implement all this, which all this is really awesome to see happening. With me, I don't know, maybe we do this categorization or something, but the idea of, like tying an SLA to a checklist of practices. Like, sure, we have all these norms and there's just things we want you to do. But, you know, if you do the bare minimum, you know, then we make a certain effort to keep your tool alive. But, you know, if you have checked all 10 boxes and been verified, they have a published source code that's home sourced with a list of group languages that have a repository, blah, blah, blah. You know, we put a different flag over it, so if we guarantee more maintainability, then we can work with this. Right. And then that flag system kind of gives also the Wiki communities, you know, D, Wiki can say, well, we rely on those 10 boxes and we look at that list, eight of them are in a really good SLA category or two of them are not so well maintained categories. Maybe we should be concerned about them, totally. When some kind of concept like that I wrote, so I have this task that I've been assigned to me for like two years, and something in me just won't let it go. I have no other tasks that I haven't unassigned because I haven't closed them. With this one task, I just, something in me can't read the English. And that is essentially two defined support levels across labs, which is more general, but that's the idea we came up with, which is markers that indicate basically your commitment, which allows us to mirror, you know what I mean, or at least ideally. The barriers there are, we honestly probably don't have time to reflect the goodwill of everybody. If everyone showed up and did everything right, we'd be like, oh, we're screwed now. Which may be a decent place to be, I don't know. And then, I think the other thing is, we're working towards that checklist, and we just haven't written it down. I think we all have, right, we've internalized some version of that. And what happens is, some bot tool goes down, you go and look at it, and you run through, okay, there's not a license, and it's written in mono, and whatever, written in C-sharp, and it's running through the mono, and whatever. And maybe you're thinking, oh dear God. But, eventually, we usually come out the other side, telling the person who maintains the tool, like, here's what we can offer, you know, and it might not be much, but something. Well, it would just be good to have those up front, right, because eventually when you hit that emergency, and that tool is down and someone is trying to fix it, you're going to run into well, here's the slowdown, here's the bottlenecks for why we couldn't fix it for you very easily, because you did all these road blocking things that are not necessarily the best norms. At least you can, instead of flagging, instead of figuring out how to flag those things on the front, you can categorize to the support levels, you know. Yeah. If you check all these boxes, not all of which are strictly required, but you can go outside that, you can check all these boxes, you know, we're going to provide you a higher level of support and flag your bot as more improved. Do you think, I don't, I don't, I like the idea of having a video camera and it's like that for people that can fly, but the thing is that it's, certainly in Brian's examples, the people that suffered when the tools died were not the people that were able to use, and so, so the incentives aren't aligned very well. But see, if there was some way for, I think that we could do that by having, ultimately the status being a flag on that tool, like when it makes edits on DEE, it's by whatever bot, and it's got a little icon next to it that says like, super good bot versus questionable bot. Right, so all these evidence are mapping from this not very well maintained bot. Yeah, so I use this financial app to track our stuff and it analyzes your stuff, like, do you have any money, say, do you spend more than you make and it does this, like, yeah, or, oh no, and it also has an exit, it has like, how do you compare to your peers? We broke, and some version of that would be cool. And as far as like, defining what those checkboxes are, but obviously, these are two things that we're committing all of that and they're kind of norms and standards and these policies are just starting to come. And at the other end of the spectrum, we can look at where we, at least in some areas, define production practices, right? Because the ultimate goal, moving up that chain is your code is so important and so well maintained and it moves into, like, immediately with the extension as part of our internal stuff and everything, right? So that's, I'm just saying that in the second half of the spectrum, it's like a drum list of languages that we support without production developers and like, we're able to get prepository that they can hear. Right. It provides it's hard to attain the checkboxes toward the categories, right? Well, the most extreme example would be if we got the waiting people to decline a lot of water. Yeah. And that's, that's the one that we found out that's the, like, yeah, right? Like, but it, like, but, and your, your idea is a good one, like, and then we, uh, it actually came up, uh, Valhalla was at, uh, an Edithon, a well-known volunteer. Yeah. Sorry. Sorry, yeah, yeah, he's a, he's one of the two volunteer admins in Toollabs. So he's gotten full-routed in Toollabs and he does all kinds of awesome stuff for us. Um, he was at, uh, an Edithon somewhere around and I had him, he was like, I'm going to meet these people. What should I say, though? I was like, ask him about this stuff. And that was one of the suggestions they came back with, was some sort of, you know, like A plus to D minus sort of rating system that could somehow be paid-visible. Like, how to make it visible, that's, that's a whole other question. Yeah. I, I really feel the pain. And so, what I worry about is I end up causing more pain in that room. Like, before, you know, I've heard that, like, there's a year-long pain for the whole foundation. But like, those changes are coming even more rapidly. You know, I've now wrote it. And like, when we're looking at those from a public-facing perspective, we're not trying to be very opinionated. Usually, when we finally kill something from a public perspective, it's like, and there's this .01% of crappy browsers from the world that aren't compatible with this and we're really feeling like, things that haven't been passed in eight years. But now we know that, like, some of them also fall that far behind on software levels and so on. And, I mean, the pace of innovation to change and the necessity of change for security reasons and all that will continue to increase and we will have more of those purposeful moments.  Well, it's all happening in a way, because we're, you know, in science. And so, yeah, I guess. Yeah, yeah, we're going through another long-tail phase of it right now. So we have this, I'm sorry, go ahead. Oh, no, I'm just going to go through the internal narrative and like the labs team, which is, we're really overloaded and there's just no way we can get all of this done. That's a good thing. The platform's really popular and like, there's too many tools for us to support and, you know, all these people are showing up saying, these tools are down and it's really impactful to their workflow and we're like, I'm not sure how we're going to get to this, but the platform's really used a lot. Like, that's really kind of amazing to me. So, we have this sort of so, I'm thinking about the issue around like, a lot of people groups in the different projects and like, a lot of them, I don't want to require open sourcing code and what I've written along these pages. Like, a lot of the arguments are made and it's like, oh, this could be too dangerous for anyone to be able to use in the vandal on this amateur game, you know. But I'm wondering if there could be some sort of offering like, private repository or something like that. Do you have to offer a lot of people groups and say, if you want to develop the code not open source to the world, but at least like a central thing, here's what you could require as opposed to saying, I don't buy into that. So, I mean, it's a topic that's come up before and the potential for a code escrow service, I mean, it's there, but I do not believe any of the arguments that there is such super-secret mega-sauce in any of these tiles and red-axes. I mean, I'm not in the position they are to actually affect any of this that I'd be my patient with as well, those are the lowest arguments I mean, we probably shouldn't entertain those arguments because we should set people straight and that's not the way to do this. Wait, wait, and I think the other way to look at it is to help people understand like, honestly, a lot of people don't want to share their source code because they're ashamed of their source code. Right, and so the other thing to really help people understand is that we're all ashamed of our source code. Right? So one of the more returning points as a developer is when you realize your home for the socks they always build and everybody's for the socks they always build and there's no reason to be ashamed. Right. I have talked to a lot of okay, this is random hearsay, but I've talked to several foundation employees that that was the scariest thing for their first six months of working here was that every code review so we don't I'll push you then for like, why don't we work with them and require open source in the code it has always been a requirement Well, so there's a difference between licensing and publication Yeah and it's always been a requirement to have a license license Ryan, if Ryan Lane was here he could tell us what his intent was when he wrote some big words on the wiki or something and somebody had that license to it or else there's no license license to it Yeah It's hand-waving you know what I mean Yeah but yeah I mean that would be my suggestion Honestly, in rare cases where there is a need for a secret it should be secret code it should be secret data and that's a whole different nation a resource code that loads the time instead of secret data Yeah, and there are some things we're hoping to work towards that especially with the Kubernetes migration and the whole system built inside of it for and when that's separating Yeah I have one I just want to give you a Yeah five Thank you I have one too and now I'm going to do that because we started service and I discovered that and it's probably my own and I don't get the results so I'm not sure I'd love to monitor you monitor your metrics Yeah and you'd love to have it on that So in theory the big brother system tries to keep great engine submitted jobs that are set up with it right in theory in practice it may or may not work for years but funny thing about trying to write your own reconciliation system on top of a great engine is that web service has it now built to Well I think he's primarily talking about verification regardless of auto-detection Yeah, because if you don't don't restart it We're terrified Some people have written their own and there's a project which either we just created and coded to remember where several tool apps were basically trying to solve the problem on their own but it's been we don't have a few things in this arena or a lot of things we don't have like a hey this would be a great release process for you to do on this platform you know what I mean like here's sort of the vanilla version of that maybe you need to add something to the beginning at the end but it makes it predictable for everybody we don't have a good log aggregation we don't have any log aggregation system and that's like a ginormous main point and then we also don't have like real deal user tool monitor I mean we have people who have written their own we have a lot of ad hoc stuff and then we have the grid has some function for like if your job gets killed unexpectedly they'll send it in whatever but it's all pretty reading so I could say that you're just right what you want is perfectly reasonable yet it doesn't exist yet and in my mind those things have standards like so everyone because one thing about even if someone has a dog hadn't been proactive and written something to monitor their tool that's awesome but then like I have to not only figure out your tool but like how you're monitoring it what that means and everyone's doing this slightly different or we have a lot of people who have maybe they've used like the native I found wrong rotation but more than likely not they probably wrote some thing that just offers a bunch of files and who knows what shuts their own service down and doesn't move on a directory and you know eventually that falls apart and they don't know if it's us or them but the real life value of each there is that there's no one single sort of curator way to do it and that is in my mind sort of on this list next if there was another slide here definitely and we know it's not you it's us yeah but I think the future is one of these future possibilities it's like a just a standard for monitoring yeah totally like we expect everybody to you know if they want good support to write a tool that conforms to that like a script that does a nodgeo style exit codes and checks whoever needs to check about process states and provide you an email address right or something like that I mean we standardize something we can write a script for the exit code and how does whatever you want to talk about the tool for writing an ability yeah the hardest part for me about that like I totally like that is an answer right like that is the answer we would use in production that is the that's a one percenter solution right like I know that most of the people that are using tool labs to do stuff they can't do it they can't do it because they don't have the time they don't have the energy they don't have to communicate right like if they could do that stuff we would have already hired them and they would be there's stuff they could produce right or they would be constantly fending us off from trying to hire them yeah but so some some things we're not going to make any promises because making promises is there's a way to just make people sad but we were trying last quarter and I don't know that we've necessarily succeeded but we've been trying to collect a series of requirements for a true platform as a service product so replace open grid engine with we're replacing open grid engine with Kubernetes that's that is a known thing that is happening that's in progress what we would like to do is rather than make our own collection of pearl and Python scripts that figure out how to put jobs into Kubernetes which aren't called jobs anymore but let's just say jobs into Kubernetes we're talking about the push to the play a second yeah we would like to get a true a third party developed open source well supported platform as a service layer to put on top of Kubernetes and that's certainly one of the criteria that we've got on the checklist is what kind of monitoring what kind of notification what kind of what kind of feedback loops does it have to help people we've got a whole lot of eggs of hope in the basket could open shift or DS or some other product that we haven't yet identified that exists in the marketplace give us you know give us a big boost right like not just like a little incremental like it's a little bit better but like no look at all this stuff because when we bring that out it's gonna hurt people right like it's gonna be worse than the tool server to lapse migration it's going to be a whole other migration where I have to put my stuff in some different format do some different things I don't have any time and 20% of tools are just going to disappear because of it right when you get it you're just going to be like I don't even care anymore so it needs to it needs to fulfill lots of some pretty good things for us to make people that made for my mind that maybe one of the better meta things going on we have an occasional sea change to shake things up and everybody would look at their stuff about data you know yeah it's when the infrastructure goes stagnant for like five years running and it needs to get really out yeah shake things up in the long now view yeah like in the we're a movement that's trying to distribute collect all information and knowledge so that we can redistribute to everybody stuff all washes out like all these short term like oh my god and half of people left and they're mad at me like that's fine because 75 years from now those people aren't around to be mad at me anymore anymore right that's this you eat much better than I do also one other thing is is that kind of what you're talking about all exist natively in kubernetes like right now if you write a web service and you go to run it on kubernetes we essentially like lobbed up a deployment which then creates a single replica set which tells the kubernetes stuff that basically the manager the reconciliation loop that says is it running should it be running and we basically keep one instance going at all times right and the way that it does that is essentially is the container up and then is there a health check which is a native mechanism that allows it to be like more contextual about what is it of meaning so we have that baked in but part of the issue is once we present it the first time to users as if we want them to use it it better be the way that we want them to use it for the next X number of years because that's a really expensive thing to give your mind around and the underlying mechanism right now it's pretty low level I'm not saying that people aren't smart enough but I'm not sold on sort of evangelizing either but I mean it's there hopefully the there's two kind of contenders for a pass like solution Red Hat has one sort of a gorilla in the room called Open Shift which I believe is something I've seen presentation or whatever and then there's another place that is sort of like the Open Shift model is let's wrap everything up let's put a pretty little bow on it so we can charge people we have you know the Red Hat it's their whole thing right like we have an Open Shift origin which then becomes our product which we can now sell and there's no real difference and in fact when we went to Qcon whatever that was over in November a lot of the coming access control stuff is all being backboarded from Open Shift to Core and Kubernetes so I think it's pretty tight integration there and it's possible but the alternative is a third party called Deus and I think their product is also called Workflow and their whole model is essentially you should run all the components that enable this push to the play model as containers and it's all just kind of baked in you know what I mean like they eat their own dog food for running the sort of layers that flush this out I don't know which is better I think that one might be more flexible but Open Shift is cool I'm hoping that one of those two things makes that model that you're talking about like one thing that might be done today is there's plus oh maybe not but I know one that will do a health check for free on like 500 points is that something that people write or is there something that like no that's free if you if you can find some uptime monitoring as a service thing out on the universe and you want to point it at your web service do it yeah and that was the project that Chase mentioned earlier that there's a I think at least a couple of volunteers that are involved in trying to spring that up they're basically trying to build a labs project next to tool labs that would just do that that its job would be to be at that the problem there is you can't tell if there's no connectivity into labs outside of labs right that kind of that's awesome and I hope they can succeed I'm not sure that's the long-term solution I don't know that it's magically scalable but it's worth letting somebody give it a shot basically if you're interested in solving this problem we're happy to like sure yeah well so the Kubernetes VMs pieces are OpenStack themed so basically OpenStack is the infrastructure to service it handles the networking networking compute memory storage stuff for us today and then Kubernetes sends in pieces on top of that and it it does that's on the step about it yeah there are probably standard things all of them in Kubernetes it's regular it's not that's not all of them and I think that's not necessarily like we could run Kubernetes on very much like so in the grid that they're setting up in production I believe it's on very low also we could use NEET which is a container orchestration you know kind of a narrow Kubernetes on but besides it can be it's and it might just be it's it's I guess we rambled through all of it great time now but if there are things people want to keep talking about these things I'm around for the rest of the day I'll be here tomorrow Fabricator IRC email BD808 Fabricators probably the best for a lot of these kind of like longer theory like the monitoring things and so then I think if you go I don't have the numbers memorized because I'm not that guy but I'm pretty sure if you go look at the tools labs project you'll see a big ticket that says Jesus Christ why don't we have a monitoring and I don't think there's a good place to vent on these people tomorrow but on the other side you can stall for three years right at least it's persistent so the next time we have the conversation we can go back and say hi we're going to be right beside you okay thanks yep thank you


Welcome to a demonstration of reflowable layout. This video was created with support from the Government of Canada's Social Development Partnerships Program, Disability Component. The opinions and interpretations in this video are those of the creator, and do not necessarily reflect those of the Government of Canada. It was produced with sighted assistance. Folks that allow for reflowable content are usually easy to navigate and read with assistive technology. When play is pressed, the content is well narrated. Colonization. In this text we have studied the effects of a number of invasions, conquests, and waves of settlement in the history of English. In contrast, books produced in fixed layout present a choppy and disjointed reading experience. Introduction. Capital T. T. Cattle. Industry. Fixed layout is a poor choice for lengthy titles and should only be used for children's picture books.


I think the Federal Ministry of Health and the National Family Healthcare Development Agency deserve our commendation for providing this very important platform, for providing this very important platform for rethinking primary healthcare in Nigeria, especially in the wake and aftermath of the COVID-19 pandemic. The pandemic was an eye-opener for me in at least five important respects. The first is that a health challenge of sufficient enormity can cripple the global economy and severely worsen the circumstances of the weakest economies and most vulnerable groups. And we saw this happening with global growth in negative territory for months, even a year, massive supply chain disruptions leading to inflation, and millions more going into unemployment and extreme poverty, all on account of a sincere enough health challenge. The second is how some of the wealthiest and most developed economies in the world were tragically unprepared to handle a public health crisis on the scale and uncertainty of COVID-19, whereas countries with more modest economic profiles quickly developed a public health framework, especially at the primary level, that was responsive and effective, which emphasizes that smart and effective management of healthcare is probably as important if not more important than just availability of resources. The third is that when there is a global health crisis on the scale of the COVID-19 pandemic, we cannot expect any or much help from anyone. Every nation is in such times on its own. The vaccine nationalism first responds to the distribution of vaccines was certainly a wake up for poorer countries. Happily things have improved with the greater availability of vaccines, and we must of course commend those countries that have made very general donations to African countries and other developed economies. The need for more effective health security plans since what we saw with the vaccine nationalism has since occupied the thoughts of leaders at national, sub-regional and regional levels, and there is, as we heard, cheering news about the preferment of our country, of vaccine production in our own region. The other is that despite infrastructural weaknesses, we have an experienced and robust public health system in Nigeria, people by some of the best personnel in the world, and you heard Dr. Faisal, and you heard Dr. Faisal a few moments ago bragging about how we maintain 56% in routine immunization even during the pandemic. The fifth is a conclusion from the preceding point, and this is that a health system is only as strong as its primary health system. No matter how robust we want a health system to be, it can only be as strong as our primary health system, and this is true either in dealing with infected patients in a pandemic or effective vaccination program, especially in popular countries, but it is especially the case that because of the preventive focus of primary health care, any investment in health care is a wise investment in the social and economic well-being of society. Since invariably fewer people will be ill and thus not require the more expensive, especially scare. So this year, and today especially, as we mark about four decades of the anniversary of the Alma Ata Declaration on Primary Health Care, I think it's appropriate that we should reflect on the state of primary health care in Nigeria, and we've heard a lot already, especially tracking the progress in some of the key components of primary health care, especially public education, nutrition, clean water and sanitation, maternal and child health care, immunization, local disease control, accessible treatment, and drug provision. We've heard already of some of the very exceptional problems that have been made in the provision of some of these components. The basic health care fund, we've heard already, seeking to address the cost of health care for the poor, the freshly designed primary health care facilities that are to have steady water supply, solar power, staff water, perimeter fencing, and even in some areas in the hinterland, the care care and pet mini ambulances. Also, the federal government of Nigeria's COVID-19 response measures, and these measures were considered, including the health sector component of the economic sustainability plan, the establishment of the healthcare sector intervention fund, which disbursed somewhere in the order of 80 billion naira to finance the acquisition and installation of critical medical equipment, and the expansion of production lines in some pharmaceutical companies. They are also the worst initiatives, especially the clean Nigeria use the toilet campaign, led by the federal minister of water resources. Then the extensive work of the national council on nutrition and the food systems galons, and the special initiative on large scale food fortification, such as the food processing and nutrition leadership forum, led by Alagi Aliko Dangoti. I think it was on March the 10th that that forum was held, and of course with very effective local participation as well. However, I think it's evident, and we've heard from practically every speaker that has come forward today, that a lot more needs to be done. And permit me just three trends of thought very quickly, as we re-emerging primary healthcare in Nigeria. The first of course is dealing with out-of-pocket expenses. And I think we clearly need composite health insurance, where premiums for certain categories of vulnerable groups are paid by government. And the only minister of finance has already said that our target is 100% coverage for the poor and vulnerable in the short to medium term. There is no way that healthcare funding can be paid by government budgets alone. It's simply impossible. The size of the federal government budget itself is so constrained that there is absolutely no way that we can expect to fund healthcare by just budgets. And so healthcare insurance is an important pool of resources for funding healthcare on the scale that would be required for a country of 200 million people or more. The second is addressing some of the drawbacks occasioned by the concurrent constitutional status of primary healthcare. There's a great need for synergies to prevent a situation where the federal, state governments and local governments and private persons duplicate primary healthcare facilities. And there is no real planning around what should be where. The first is encouraging and supporting serious private sector interventions. And two examples come to mind. We've heard one already, which is they adopt a primary health facility program, pioneered by Mr. Idemokwede's ABC Health in collaboration with Private Sector Health Alliance of Nigeria, which was also founded again by Aliko Dangote, Mr. Idemokwede and Jimovia. Their goal, as we've heard, is to establish a chain of primary healthcare centers across Nigeria in all of the 774 local government areas and apply market bills reforms to provide low cost health services at decent standards for the poor and the vulnerable. And I think this is an important initiative. And we will see that it will bring in some of the private sector efficiencies into primary healthcare delivery. The other is the EHA clinics. This operates mainly in Kano and Bautistae for now, led by Dr. Hananiya. And it has a program, which is called the REACH program, which has brought effective healthcare to over 11,000 people in Kano state alone. The effort leverages on partnerships with non-governmental organizations and pharmaceutical companies. They negotiate treatment prices so that costs of drugs will be affordable for the vulnerable, for the poor and the vulnerable. And they also train community health attention workers to provide affordable healthcare to people in those communities. So, aside from the funds that the private sector will bring to the task, they would also bring important models of efficiency and cost-taving driven by market ideas and all that. On the 27th of January, 2022, Mr. President inaugurated the Healthcare Reform Committee, a robustly constituted committee with representation from the states, healthcare professionals, healthcare-related professional groups and associations, and medical academia, and so many other groups. The primary objective is to re-engineer our healthcare delivery system, so that it becomes, in the President's own words, people-centric, modern, and viral. A healthcare system that addresses the depressing health indices frontally. I was asked to chair that committee by Mr. President, and since then I've interacted with a broad range of institutions and individuals. And it's evident that there's a great deal of excitement and expectations about what is possible. And we're expecting the next few months to see some progress in redesigning our healthcare system with so many of the great ideas that we've already had. Finally, let me again commend the Honourable Minister of State, the Honourable Minister of Health, Dr. Osagie Henry, whose openness to ideas and innovation, and his own personal commitment, has advanced his cause of healthcare in Nigeria. He is the very able and supporting colleague, the very experienced and knowledgeable Dr. Long Nibbe Mamura, and of course, Dr. Faisal Shuai, the dynamic hard-working and innovative EDCO of the MPH CDA and his team. It is now my very special pleasure and privilege to formally declare open the Primary Healthcare Summit 2022. Thank you very much.