 All right welcome everybody to the final session of what I think is the seventh flock some sort of horrifically high Number we're almost at double digits with this. It might not No, Mike. Okay, there right. Yes. Sorry welcome everybody to the final session of Like the seventh. I think flock here's Ben who has made it awake for the I Thank you all for being here and for all of your energy and hard work I really felt like this was a great conference and I felt a lot of positive energy and a lot of Working together and collaboration and talking and I feel you know energized for the next year and tell till the next block If you have any feedback on the conference on anything that we could have done better There's always room to improve with like next year's to be even better yet I wish we could announce where exactly it's going to be but we're still not we still don't quite have our stuff together on that But it's going to be somewhere in the middle portion of the United States will figure out exactly exactly where to come I said Midwest and somehow Denver got onto the list because people who are making the list don't don't know what the Midwest is But yeah, anyways, here's our wrap-up session and we'll start with Adam with minimization I guess is out here presenting on Minimization is that you're okay, and I'm gonna get off the stage because I'm done Hi everyone, I'm Adam. I'm now the minimization objectively and that was one of the reasons why I'm here About that so I gave a talk we had some discussions after that and I was very happy that people say that it makes sense And I got like 10 people from the community Wanting to join the initiative and that's like, I don't know 60% red hat and not not red hat So I think like this is not just the red head objective It's just something that everyone cares about I feel so that's great And we'll be starting having first meeting next week on Wednesday and Yeah, it goes well with other things like the federal IOT Everyone wants things smaller and what I learned about IOT for example, what I didn't know is well haven't realized is that it's not just a small system that needs to be immutable and Small and whatever but It's about it's outside. It's accessible. There's no physical security and also some of the connections are super super slow so That's like one of the reasons why it also needs to be minimal not just the device is tiny Anyway, so that's minimization then we had modularity. We had a fantastic Birds of a feather event discussion. It was quite productive. We discussed topic like The modules in the build route that block many people, I guess and we have steps how to how to move forward there were some Maybe a little bit cross distro but like third party things like how to enable People to build modules without using our infrastructure using their current ways of things Like in OBS or in copper even So yeah modularity things that was great. I Talked to Ben cotton and Paul about the rom magazine. We designed a new workflow for contributors to be Much easier to make the much more easier for people to submit ideas and to pick something up and write it down So that might be interesting There was something else I forgot. Okay. I'll just let other people speak. Thanks Hello everyone So I ran the fedora loves python session So there's this fedora loves python slogan Movement whatever nobody knows what it actually is and apparently we're not getting any more stickers printed unless we have some kind of marketing story So that's what that was about We have lots of notes that we need to clean up and post somewhere on the mailing list Turns out the best thing about Python and fedora is that you can use all the multiple interpreters? We can support if You're building a fedora package. There's one you have to use but otherwise if you're fine with upstream's upstream Sources you can use anyone you want and test it on all the different versions. So people tend to like that a lot The other thing that we are missing in our sort of marketing For this is that fedora stays close to upstream, which is quite hard because we need to make the changes upstream and Argue about them a lot, but it it pays off So we need to talk about that Somewhat more. Unfortunately, there were no marketing people in the session. So Yeah We have stuff to talk about but we don't know how to talk about them So we'll try to figure that out later The other session I I was part of was py project macros So that's an initiative for not storing information in spec files, but rather Pull them from the upstream projects. So you don't have to copy paste Unfortunately, this involves changing the upstream standards to actually have a place to have this information So we had a hackfest on the current iteration That's will hopefully get it for the r32 or so and we got some useful feedback and and Some PRs merged as well So that's me Hello everyone. I had two sessions. First of all, I introduced our community shift instance Which is an open shift instance for people to prototype applications Run things that are good for fedora run community applications that we don't have time to run All that good stuff if you want access to that if you were not at the talk You can email me or file an infrastructure ticket either one and I'll be happy to add you So there was that and then we had the cpe hackfest this morning and we kind of broke up into groups there So I'll just speak of the groups that I was involved in we went up kind of over our backlog of things that we want to do that are upcoming and We scoped out several of those to a pretty good extent. We talked a lot about our monitoring story about our Logging and stuff make Matthew's life better. So he doesn't have to like look at a to be a stat stats ever again and We went over several other things that were upcoming and Kind of how we could spec them out and get them prioritized for our for our team And just had a ton of hallway discussions. I do want to mention one other thing that I didn't do Smooch could not be here This year, but he has been working on apple 8 a lot very hard And I think things are to the point where he has an announcement ready that will probably go out after flock That apple 8 is is ready to go. So that's that's awesome work from him. And I just thought I'd mention it So I was having the second group in the in the cpe hackfest And we tried to bring some a little bit on now We want the package or workflow to look like in federal in in the long term in the long term because we currently have a lot of Initiatives going on in federal about that are touching the package or workflow the package or user experience and We saw that if we don't come up with a unified vision on what the package or workflow should look like in, you know year or two or three from now We may have Contradiction initiative contradicting work than if you know We want to we want to achieve that point But then this idea which may be a good idea by itself is actually Contradictive to the to the end goal So we tried to bring some a little bit on how that workflow should look like we'll need to spend some time on On the still it's definitely it's still rough I'll try to recapitulate Recapitulate everything we've said send an email to the to the devil list for for more feedback It's not going to be something that would be you know We'll all agree on from the start But it is a discussion that I think we should be looking at so that we can actually align all of our work Within one direction The second thing which are presenting was the the right getting work So I'm very happy that's why I didn't get any rotten tomatoes We'd not nobody's run run out of the room screaming and shouting and so I'm very glad for that There will be more changes coming into that There will be more announce if you're interesting give us your feedback if you're not interesting give us your feedback if We are blocking you give us your feedback and if we are enabling you please give us your feedback and with that. Thank you Hello, I have some notes. We don't mind So this is the design team recap Renata gave a one-on-one session on UX UI and there were about a dozen attendees there We also had a fedora badges hackfest with some very lofty goals and a couple accomplishments We did a lot of brainstorming on different topics such as a pattern library How to incorporate badges into different processes and workflows in the fedora project already and our biggest idea really there was visibility really ideas would be to revive blog posts Maybe create some infographics get more on social media platforms Just kind of blast it out there as much as we can and get it in everyone's minds That this is a tool that you can use to improve your individual projects and initiatives We also talked about badge criteria and retiring some badges. Maybe that they don't work anymore Style guide updates and we discussed a lot about the look and feel of the badges and how we might want to see that evolve Renata and Tanvi ran some usability tests to get information that will inform a redesign that hopefully we can see in the next year or to happen and Renata is going to provide a report for us Some ticket triage. We kind of ran out of time on that In the afternoon, we had members of the infor team attend and We discussed pain points of the badges project things that need to be done Things that would be nice to be done things that would be Nice to have in the future such as improving the website speed Moving to Python 3 a website facelift Further social media integration on the website Potentially integration with the fedora OS interface further website subcategorization organization filters basically a better a better Experience for people using the website The biggest issue we found on the development side is automation of badges So if people want to work on that that would be great The biggest success we have on the development side is that we started a discussion and planning for an outreach He intern so hopefully we can get that moving for the next session And there is some mentor commitment behind that so overall it was a success The main thing we got out of the second this session was surprised a lot more work to do and Hope that the project is not going to die Overall for the design team You know, there was three of us here this year unless there's some people hiding in the woodworks It's it's a little discouraging I think at my first flock like five years ago There was maybe a dozen or more so it kind of feels like the team might be dwindling a little bit So I had a lot of discussions with the people who were here about why and how and where we've gotten to the point that we are right so There are things that I feel it can be changed from inside the design team like lowering the barrier entry the best that we can Creating a more welcoming environment Spending more time connecting with each other on IRC like I used to hear that the IRC was like hop in cool place to be and now It's like crickets But there are also things that can be changed from the outside and the inside working together, right? So just like any relationship we need to identify and understand those issues communicate them and Come up with solutions and then work from all sides to kind of come up and figure how we can make this a better thing So this topic brings me back to Kate Houston's talk, right? clarity capacity and Incentives and feedback, right? So I think the main incentive We can ask for from the community as a whole is recognition and feedback, right? for example Sorry to call you out But when Matt was talking about new projects in the state of fedora and he brought up why the logos were great There was absolutely no mention of design or the design team Like we talked about the projects and we said the logos are cool, but the design team was not brought up So I think that's the kind of place that we need to think like this work is being done by real people And they deserve recognition for it, right? I've been trying to figure out the right places people teams to connect with to improve these issues And the reality is that we need help. I need help, right? I'm gonna make a write-up on a lot of these thoughts and Try to say it as best as I can in a blog post And I hope that people will read it and reflect on it on what they personally can do and what their teams can do To kind of make the design team feel a little more valued and recognized for the work that we do and Also, what can we do for you? We need work to do to Have that feedback loop That's my thoughts for vlog 2019. Hi, this is Amita. We have done DI Hector's yesterday and We have done a lot of work which were pending since last six months Being together in a room With all the team members so Since last few years this team is relatively very new as compared to the other teams in Fedora And we have very less volunteer and the team members in the team But still we are thinking that how we can With this limited volunteer time how we can make the bigger impact So the one thing which we brainstorm about is collecting feedback from the community people how they feel about for example Marie has Correctly pointed out that there is the less appreciation for this volunteer work So it's such kind of feedback We are looking for and for that we did coffee with friend session throughout the flock Some of the sessions taktika has taken and we would like to continue with these kind of sessions We'll open a window in three months of time period and you can just fill a form or open a ticket in DI peggio ripu that you would like to talk and you would like to express that what is the pain point Which we can help with So that is one thing which we added in our goal We would like to connect with the International Legation and globalization teams to identify that what are these important content which are being published on Fedora magazine or the community blog post like the Fedora strategy or or the mission statements which are probably the most of the higher Authority people are writing and most of them are from us and they're needing native language is English So not everybody understands that quite well So we would like to figure out what that content is which needs to be translated in other languages So that people will feel more inclusive that I need that And as you have seen that we are very successful with Fedora Wednesday event Which we have done last year in 10 different countries at the same time period or the same month So We would like to do more such events like LGBTQ events since we have that format Existing baseline that how to pull out such events throughout the world. So we would like to do such events more Since we are The diversity and inclusion team and we have done a great job being diverse I mean look around you how many different kind of people are sitting in this room from different country from different culture from Different languages, but we need to focus, you know Extend our focus to the inclusion side as well. Are we including them well or not? So for that We are working on Taking some steps and working on the event guidelines as well. So these guidelines be has done a great job In drafting that guidelines and she would like to share few points with you so We have been working on a proposal for launching event guidelines for Fedora like event organizers So people and bad seders who organize Fedora release parties or organizers for flock to help them make these events Have like a more diverse audience and to make these more inclusive and till now like we've worked started work on this two years ago And we had a lot of feedback from last flock which we incorporated in our recent Proposal and this time we have a lot of actionable items and recommendations not just to the flock organizing committee But also for like other like smaller local event organizers So during the hack fist, especially we got a lot of feedback from different organized ambassadors from different communities And we like compiled this recommendation and we will provide them to the relevant people But what we need from you right now is to also go through this proposal because right now the only people who have reviewed This is like a few people but we need feedback from the whole community about this because this is for you And this will affect you so we will publish a community blog post And I really hope all of you look through it and give us our feedback If you don't like something if you feel it is not relevant or if it is hard for you to do implement it Please let us know and I would really like to hear back from you Thanks, thanks for that So other than that we also talked about some internal team processes We would like to improve them like decision-making process and DI advisor elections You will soon see that there will be DI elections in November time frame Other than that we would like to focus on the content creation and we did create a video Which we would like to show you Before that I would just say that Like Denise was here and she pointed out that how Important this community is it's made by people right so these memories Needs to be captured and these memories needs to be shared in the graphical data Data way and also the people needs to be appreciated in the right way That is the least thing we can do about the community So for that the happiness packet is one thing which the DI team would like to market enough and please use these Happiness packets where you can send the appreciated words or this kind of certificate to the people in the community who are doing the awesome job and we have some more ideas like five years completion t-shirt and ten years completion t-shirt In community so these are little ways or ideas which we would like to implement in coming days so now and Please send some Fedora happiness packets to flock event organizers because I think they have done like a great job. Yeah, definitely So here is the video which Taktika has created and she is the awesome photographer a big round of applause for her And here is the video This is Riyakar, my name is Amita, I'm from India and I'm from Punjabi Namaskar, my name is Praveen Sarputek, I'm from India And I'm from Marathi Hello, my name is Jean-Baptiste, I come from France and I speak French Hello, my name is Patrick, I'm from Chiska, and I'm from Chiska Hello, my name is Mike Fabian, I'm from Germany and I speak German Hello, my name is Balazs, I'm from Hungary and I'm from Hungary Namaskar, my name is Anikil, I'm from Barthasahe, and I'm from Baraki My name is Jens, and I'm from Thailand Hello, my name is Alberto, I come from Mexico and I speak Spanish I'm from Chathuma, I'm from Brazil and I'm from Russia We are of different cultures But Fedora unites us with open code Thank you everyone, thanks a lot We're going to trigger on it already And with Fedora 31, the default installation, when you install it from scratch The kernel will run with C Group Suite 2 enabled only So Neil, you might want to check Snap We check today, Libvert is also not working yet It's up to you to decide, if you like it or not But here, just basically another heads up that C Group Suite 2 is happening We want it, or basically Dan was pushing on DevCon earlier this year for it Somebody needs to start with it C Group Suite 2 is out for many years And if Leonard would be here, I'm pretty sure he could talk hours about Why we need it and why it's technically superior So from the containers ecosystem side, somebody just needs to start And well, this time it's us So technically it means we cannot use RunC Because the OCI specification is not there yet So we have to use CRUN from Giuseppe Scrivano Which is good because he's working at Red Hat So we can really make sure that everything is working fine I just enabled it on my Fedora 30 machine today And it's working nicely So I want to encourage more to follow And make sure that everything is running Any comments, any feedback, screams, is anybody scared of it? That's a very good question So Dan and I will sit down with Giuseppe next week And prepare a blog post So what we wanted to do is ideally publish it on Fedora Magazine So that we get the most visibility as possible And also to give a heads up early to avoid other communities To avoid them to misinterpret our intention So for instance, there's Moby, Docker, Kubernetes, yada yada And there's a lot of competition going on But this is really not about blocking others from continuing to work But somebody needs to pioneer there Because if not, we will stick with V1 forever And from a technical perspective, it doesn't make a lot of sense So we will prepare a blog post And make sure to give all the instructions from the kernel Basically it's just changing the command line of the kernel So you update the grubconfig, you regenerate it And then it should work My famous last words Pardon me, can you repeat the question? Yes So if you upgrade, at least that's the plan, nothing will change Because we don't want to break existing deployments and workloads But if you install a fresh Fedora 31, this should be enabled In the end blame Dan Right, that's it Thanks Hello, I'm Mohan Badu I work as a Fedora Release Engineer And I don't have any funny stuff or crazy stuff But the stuff that people hate me for Yes, I retired a few hundred packages a few days back That worked raw hide and get text is one of them Anyway, so I have given two talks this flock One is about mass branching and mass rebuilding modularity And one thing that I wanted to ask people who are here Who maintain modules, some modules that are tagged into raw hide Which are not supposed to be Please let me know, I sent an email to the devilist And please create a ticket and relinch report so that I can remove them from there And the other thing is Fedora Compost Tracker Which actually tracks the composers And lets people know what has been failing Give some statistics and stuff like that I wish all the SIG maintainers Especially the spins and labs maintainers Will get a lot of advantage out of it And then the other thing that I wanted to let you know is about Applate As Kevin mentioned, Smooch worked on it a lot And I enabled all the Koji tags And both the updates and the nightly composers and stuff like that So it will be coming pretty soon So look for it, thank you Hi all, Myself Praveen My first language is Marathi And second language is English So in this audience, how many people have first language other than English? Wow, that's great, very good So in this flock, we had six sessions for non-English languages It included the technology plus language part Three were the talks and three were the workshop I was lead for CI and test cases workshop Luckily, I think many people turn out there And when you have many people in the workshop The best thing you can do is collaborate, talk, prioritize stuff So we are able to prioritize the stuff We know now what we have to do in coming one year That's what we did There was two sessions from the John Baptist The nice French guy who was in video So he left, so I'm covering one of his sessions as well Here he has excellent charts Many flow charts or something For maybe last eight federal releases So he basically demonstrated that the contribution at translation side The localization side is getting lower and lower Because of multiple issues So I will recommend people Since there were so many parallel talks So people who are interested to please go through his video I think it's recorded That's what I will cover, I think the remaining part James will cover Thanks On Monday, we had a... On Monday, sorry, on the first day Thursday We had a session on langpaks Where we covered the evolution of langpaks in Fedora And we demoed some of the changes coming into Fedora 31 Like langpaks core and langpaks auto installation Supporting GNOME software And we thought a bit about future developments there And the other thing Which is kind of interface of ITN and Elton But John Baptist gave a quite nice workshop yesterday By validating the plans for replacing Zenata with Weblate And that was a good session I think it's a good progress being made there Thank you I guess that is everything Which means that it gives people time to go to the bus Let's thank Jen and Veronica There's more people coming up? Okay, awesome I'll save my final remarks What? We can thank them three or four times Yeah, thank you Jen and Veronica For all of your very hard work on this conference That was cool Hi, I'm Morgan And together with Igor, we started NERA Fedora This was my first flock And really had a great time I just wanted to thank Ankar Sinha Who unfortunately couldn't be here But for setting up all the material for us And we had a great hackathon on Friday I'm in Saturday morning And people showed up, contributed tools Got some new finite element tools in That I'm very excited about And we presented a poster this year At computational neuroscience And hopefully next year at human brain mapping For the neuroimaging pipelines So I hope everybody can have a look At what we've got installed so far Maybe look at some of the bug reports And yeah, we can use help on all levels here The machine learning SIG has also been restarted And since neuroscience and machine learning Is very much correlated Those two are also going to be most And we have about some 110 packages Right now already And we have another some 130-140 softwares to package So we are looking for packages You can find us at Fedora Neuro On the IRC We hope to see more people Thank you folks I actually had somebody on the elevator Ask if this was a neuroscience conference So clearly you're having some impact Alright, before I shut it down then Is anybody else? This is your chance to share Going, going Alright, let's give another round of applause To the organizers And again, thank you everybody And then a round of applause for ourselves Because this is the Fedora community And we're awesome