Thanks for coming for the DI Hackfest. I'll just go through the agenda. So if you see, these are the peggio tickets which we want to complete a few months back but they are still pending so we would like to complete them during the Hackfest and we'll go through these tickets one by one, we'll discuss them where we are, what these tickets are all about, we'll give you the summary and then we'll discuss the open-ended things and if you think that there are few things which you can also contribute towards these tickets to be accomplished, please feel free and that is the way you will be get involved. So the first thing we would like to discuss about is our team goal and we have some existing goal for our team and we also had this great idea from Taktika that we should be doing a coffee session among friends. So we did few coffee sessions, Taktika did it with some of the contributors during the flock and we wanted to know some pain points if there are any and we wanted to involve them as the work we want to do within the DIT to you know suggest some solutions toward these issues or the pain points. So we would brainstorm these ideas and we will figure out that if there are any more goals which we would like to involve any short-term, long-term or any future goals and then we have this Fedora event guidelines which we started I guess a year earlier. So if you have seen the gender-neutral bathrooms and the quiet room during flock, so these all are coming from the ideas we are designing under the Fedora event guidelines. The majority of the work is done by B here so we will take over these slides and she will share what work we have done so far, what is covered and what is the future goals under this particular topic. Then Fedora Women's Day, I think this is the third year of Fedora Women's Day we are running. We started it three years back and with I guess three Fedora Women three or four Fedora Women events across the globe but last year we have done a great job and we have done ten Fedora Women's Day across the globe and this year we are targeting even more. So if you also want to do Fedora Women's Day at your place, this is the right time to submit your proposals and we will talk about it more under this topic. Then these are the few team-related things we would like to refine. The team processes a little bit more by defining the Fedora Council Advisory Advisor term and diversity inclusion teams lead rules so that will be more of the team specific things. So I'll just give you a brief about what we have done in the past year in the DIT. Let me tell you that we are very small team of few people and last year it was like very less active volunteers we had in this team. Still we did a great job and accomplished many of things which are listed over here. DI team always sponsor our Trichy program and that we have done last year as well. We have organized Fedora Women's Day which I told you that ten of these events we have done across the globe. We have done content creation. We created a fantastic video. I think we have the link here. If we have the link we can show that later as well. Even guidelines which is the ongoing work and some of them that we have already accomplished which I have mentioned like the gender neutral bathroom in the quiet room etc. We onboarded few new contributors as well because that was the need of the time and Nikhil Pooja and Taktika is back in the team so we have more energy and more resources in the team to work together. We have also enhanced internal processes in the team like the decision-making process was not there. Now it is there and we still need to finalize it but yes it's there. DI representative team representative and the council representative that is what we are working on the documentation and that side we are also improving. Our presence at Flock was always fantastic and this year as well we have done a great job. We did an organizer transition session and we created a video and we are having this hackfest as well. We did the coffee with friends. So that's about the work which we have done so far and some of them are still we are working on. So what is the aim of this hackfest? What we would like to take away from this hackfest is so you have seen that we have some of the tickets listed but they are not the things which we can accomplish within these two hours. Our main basic aim is to brainstorm what should be the next step for these tickets and take away the action items which we need to do because diversity and inclusion is not a very easy and straightforward topic. It's not like a programming that if this ends this true or false no. It's a lot of effort of many people and many ideas and many thoughtful processes that we would like to implement in the community to make it more diverse and inclusive without hurting anyone's sentiments. So it takes a lot of effort of everybody to brainstorm these ideas and come up with the next steps and getting it approved from the councils and legal also takes time. So that is not the aim to finish anything. The aim is to brainstorm these ideas and take it forward. So as I told you earlier, how do we do it? We're going to go through these tickets one by one. We'll give you the summary, what we have done, where we are and what is the next step. We'll brainstorm about it and then some of you I think just didn't all that. He wants to do it. He wants to do it that he will update the ticket accordingly, whatever we have done for that ticket. But always we have helping hands who can help you with that. Okay. So without wasting further time, let's take forward, start with the first ticket, the I team goals. We have these goals listed and it's kind of divided into two parts. One part talks about what we would like to do or what we have done in the community. And another is team specific. So I would rather focus in this hack fist. The first part and the second part we can anyways have informal conversation within the team to accomplish those goals. So first of all is the outreach summer internship. This we have been sponsoring like three years from three years now. And we need to think about it and we need to come up with a decision that we would like to continue doing it. And if we would like to continue doing it, how we can improve this process more for the benefit of the community. Another one is the Fedora Women's Day created content that will make impact in the community. So like the video creation, blog post and such content which will reach to the people and educate them about the diversity and inclusion. Even guidelines and the translation on important content. Like for example, Matthew Miller came up with the Fedora mission statement with the new goals of the community. But being from the native language, native speaker of English, they end up using, I mean not basic English, maybe some jargons which not everybody is aware of. So our aim is to reach to all the people, the maximum people of the community so that they understand this important content. So that is what we also would like to discuss about. So here is the open questions we have. What we would like to continue with. These are the goals listed which we already have. So out of these goals, what we would like to continue with, what we should improve on, what we should stop doing and what we would like to include new. So this section, you need to come over here, the last section, what we would like to include new because we would like to hear the feedback which we gathered by the coffee sessions and we would like to know that what people would like us to do in the community. All of the things that I didn't got to have the slide down. Okay, so it was, there was not that many people but for me I think it was more than enough was we had eight people participating, five were in person, three were online. So for having such a short notice I think that it was a good input. I had new people and I had all contributors so I got feedback from both sides of the coin. Most of the people felt that they were comfortable in terms of inclusion inside the community. Half of the people felt that they had done something that had hurt someone in some way, non-intentionate inside the community. But the cool part of that information was that since the creation of the diversity advisory position, they kind of started to overthink it, thinking a bit more about how inclusive it was, how their actions were and what were they doing with their other members of the community. So it was good that at least the creation of the position kind of put them into reality that there is people who needs, who has their needs, their likes, their shares and all of that, that we are all different. So what I felt, well, one of the questions was what do you think about the Fedora diversity and inclusion team is doing well? And I have only been in this conference in a long time, but most people said that events had more information for making people feel more comfortable, including the tax and all of that. But they pointed out that there is still some non-cooperative relationships on the big support social channels, meaning big IRC channels, big telegram channels, like the big ones. They usually get some, not harassment, but many comments that should not be there. The bigger the crew, the harder to handle, so it's kind of understandable. But now with more admins and all of that, it's easier to solve that in a short amount of time. What I did have a feeling in the community in this probably is not too related to the diversity team, but I don't know if we can do something in there, was that they were worried about the drop-off rate. They were worried that the activities that they have been doing in the past two or three years have been mostly putting down some fires instead of doing new things. And the overall feeling of the members that I could interview was that they felt comfortable, but they were quite bored. So again, probably not diversity, but it is inclusion. So we need to make people feel included into something that has meaning to be part of a community because at the end, isn't that what this is all about? So maybe we as an inclusion team can work on providing more challenges, making the right connection between teams, and the making of connections between teams that probably are not related in some levels, it's going to make them not just feel that they have a purpose inside the community and that they are doing new things, but also will allow people to also make new people inside the community and have a different approach of the reality of each one. So we will be not only making them do something, but knowing people. And that's probably what we should be doing on a regular basis on this team. That was mostly the input. I would like to continue with this. I cannot say that word because it's going to be recorded. So with these conversations, these informal conversations for a bit longer, probably a couple of months. I know some people who have something to share, but probably due time and a bit of panic, didn't share it and have a better input with at least 30 or 40 people that we can reach out and have a bigger output. But I think that that was really good information for having just a couple of people. Yeah, putting together the word that we cannot say and all the information that we cannot gather, but it's there. Yeah. So these are the things which are listed in the first half of the section which we have been doing so far. These are the things which have the impact in the diversity part of the DIT. And I feel that diversity is already there now. We are already there now. I mean, look around you and see the difference in the numbers of the ratio of different kind of people. Now it is time to shift our focus a little bit to the inclusion side and adding a goal for that, which Taktika also brought up a fair point here that talking to different people, this is the topic or this is the thing where we would like to focus more and at least add a goal for the next year for the team. So what do you think what it can be that will resolve this problem and... I think one of the things that because of our team size, I think one of the things that we are in a unique position to do, especially if you look at the council flow chart or in the council docs, there's the flow chart of the broader Fedora community. And where the diversity and inclusion team is seated, we have this really great opportunity to help these other higher level bodies in Fedora drive policy and like think about things that are outside of their day-to-day work, right? So one of the things that's been in the back of my mind is instead of us trying to take on new work as a team, maybe shifting our focus towards advising other groups, like specifically around mindshare, like what came up in Taktika's feedback about making better connections between teams that are unrelated to each other. As an activity to that, like in today in the Badges Hackfest, we had these three groups of people for the longest time have not had conversations together. We had the designers of the Fedora Badges, we had the infrastructure team and we had program or like the developers work or people who are more familiar of the development of badges all sitting in the same room and talking together for the first time that I've seen in like six years and it's like that's the kind of engagement I think that we can want that we want to encourage and I think one way that we can try to influence is that we can see these things or we can come up with suggestions and work with the mindshare committee who is charged with this specific task in the Fedora community and work with them as partners and co-collaborators and trying to push some of this forward. Same thing with the Fedora Council, outside of the like better connections with teams, there was something, oh so like the telegram specifically but the user communities aspect, that is a really hard and very high burnout area I think about managing like for example we have these user communities and there was this big, to keep things short, there's a lot of these really huge user communities that I think have good intentions in the beginning but then suddenly they grow to this point where it's very difficult for them to manage and I think it might help to come up with some recommendations and guidelines for community moderation. You know we have a code of conduct but what happens if you are like a smaller piece or a smaller group in Fedora and you take the code of conduct and use the Fedora logo and you know like hey we have it but then you enter a situation where it's obviously like what's happening in the group or the chat is not compliant or it's not great behavior, it's not being people being excellent to each other and then it's kind of like the thing that is documented in the code of conduct now is okay open a ticket with the Fedora Council which it works well if it's or it's better suited if it's within the contributor community but what about when it's a user community you know like it's like oh there's this telegram user who I have no idea who this is random person on the internet who harassed me like well I mean it's a problem but there's not like a it's not a thing that Fedora Council can you know open you open a ticket with the council right so one thing I think we could suggest with the Fedora Council to do is what we're seeing these things so maybe we should suggest to them like open a ticket or open a proposal with them draft community moderation guidelines so if you are one of these derivative communities in Fedora because we are such a huge community and there's no reasonable way that we can keep eyes on everything you know how can we empower the people who have good intentions and want to be good community leads to do the right thing without acts like without feeling overwhelmed or getting burned out when it's grown to a point where like they can't keep up with it anymore and it has a life of its own like I mean I think that was some of the user communities I've moderated and Fedora and beyond like that's a problem a lot of communities in open source in technology anywhere are having that problem and like I think it would be really great to be standing on the shoulders of other giants like Mozilla has done I think a really great set of guidelines around this so we wouldn't have to reinvent the wheel but we could think of like what does that look like for the Fedora community but instead of our team being the one let's sit down and draft these guidelines I think we need to find our partners in the community that we can have as our co-collaborators and I see like thinking of the flow chart with the Fedora council in the middle of the engineering branch and we have the mindshare branch like I see the mindshare and Fedora council and Vesco to some extent too those are our partners right those are our areas where we can try to add perspective to these higher level places in the community to try to affect positive change and hopefully have it be a trickle down you know if you see the the graph have that flow chart work its way down into these smaller pieces instead of trying to like take each of these I wish I should we should put that in the slide now I think about it that's a really great visual but it's just like you see all these different arms you know branching out in so many different directions and maybe for a long time we've been thinking like instead of looking at the individual pieces like each arm be like okay well how can we make things good here or make things better here well maybe we should look at like move the feedback loop into the top and hope try to affect change that way and I feel like now I'm just kind of repeating myself but that's just something that came to mind like listening to that feedback like there's a lot of things I've been in like that's kind of in my mind for like the back of my mind with some of the user communities I'm in on like on telegram this because that's what I use more and it's just like it's at a point now where it's like sometimes I'm just so overwhelmed and like you know I look away for an hour and now there's 200 messages and like I can't read all those and let alone like I know there's probably things in there that I'm not really comfortable with but it's just like I don't have the tools in my toolbox right now and like I mean I could sit down and like draft these guidelines for telegram but then it's going to be I'm gonna be in my own little niche and I'm sure there's other places other teams that could use these things that would have you know would be really helpful to have guidelines and here's the I don't know if we can like link that somewhere like in the diversity chat maybe in the channel just put a link to that that image but like that's coming has been the back of my mind because I think for a long time we've tried to take this very hands-on approach to doing these things ourselves and sometimes that's the right approach Fedora Women's Day I think is a great example of that because that's like a very collaborative I think it's a great example of the kind of things that we as our team can do and like have an impact on but when it comes to these really big challenges of and maybe this could be one way I don't want us like I don't know what we can probably come back to the event guidelines like but that could be one example of like we can work with you know the Fedora Council as maybe that's like one direction to push those forward but I have a question so going back into all the things that we could approach and try to help with will the burnout rate be something that it's in our side of the of the work with our team yeah or it's more into other community because it's not like we are going to recruit more people that's marketing ambassadors advocates whatever the program that is going to handle that is but the burnout rate the drop-off rate who is in charge of it so actually I want to pull some there's something that I really interesting term that I was reading about a while ago and it's when you're this team is in a unique role because I think we are we hear more about the things that are bad or negative like when there's problems in the community we get it for we we see that negative feedback more than maybe the Fedora Council would and we as a team but we as individual people in the Fedora community and so there's this term like being a toxic handler right and this is something that can exist in any organization any open-source project but the idea is that the toxic handler is the kind of person who provides like informal not it's not like a rule that you were given or assigned but you happen to receive a lot of like neg the psychological effects of like negative feedback around like different things that are toxic in a workplace environment or in an open-source community and so like I think that that's definitely something that we as a team should be mindful of is that we do see probably a different perspective on some of the things happening in the community just because I mean I was saying like everything was terrible but like that's not what I'm saying at all but like we just have I think we are more in the loop on some of that that feedback and I see the council mindshare way of trying to drive the discussion forward that could be a way to try to reduce that a little bit that's what I think like that would help us be mindful of that realizing that we do see a lot of that instead of us trying like internalize that and think of like how do we how does the diversity inclusion team solve this let's work with our partners and our co-collaborators the mindshare committee for our council maybe at some point like one relationship I would love to think about is like how can fesco and the diversity inclusion team work together like because we don't we don't do anything really and that's a huge part like if you look at the flow chart that was linked in the channel like that's a huge community so I got your point with that I just want to remind that for each topic we have 45 minutes for for two topics we have 45 minutes and in the topic we have like 30 minutes or so so we would like to stick to the timelines as well for that is a very great perspective what I what is the takeaway from that is I think what we can do is there are two part of it one is taking the guidelines which are done by our other partners in DI space in open source and sharing those guidelines with the rest of the community people like fesco or the mindshare community teams who can help us implement those guidelines to different teams and six so that is what is the basic idea which I got from your point of view I also would like to say about inclusion this tactic of which you have initiated a coffee with friends I think we should we can make it an ongoing activity we can do it open a window once in a month or once in a three months that this is the time one peak of where few of us are available from the DI team to have coffee with friends and to listen to their ideas and their pain points and things and there we can get what what are the actual things are happening in the community to get that idea so that we can address them with the proper guidelines and not bombarding them with a lot of guidelines which are not required in our community was that anonymous form kind of thing like an online like maybe we can just open a Google form kind of thing that you can submit your request to have to have a coffee with friend that can be one in road how implementation part but I think the whatever we are so we will have the people from in the DI team we have nice blend of people from different time zones so they can choose pick and choose who is their favorite one and what is the comfortable time for them and I would just like to add one more suggestion to this yeah so I just wanted to say like we already have the federal happiness packets project so maybe we can use that more or link it link to it more so that people use it so they know there's also a way to like appreciate others so like we decided to create this so that people in the community like say thanks more to each other and appreciate each other for their work more and one thing we are trying to do like from what Justin said is like making different groups interact so if they have like already interacted or if they have even like the note of each other's work I think this would be a good way to like start those small interactions or at least so show some appreciation so the people who are feeling like too bold or too like they're having like negative thoughts them they might start feeling more a bit more positive about the community experience so if we can just link to the federal happiness packets website somewhere or like put it somewhere more visible which people can use regularly I think it would be a good thing to do too that's great idea okay so if somebody has taken notes the action item or the take away for for this one is like we should make the coffee with friend activity continuous activity we will come back to the implementation part later that how we would like to do it once in a two months or so next is the guidelines for taking the guidelines from the different communities and sharing them with the other groups in Fedora which are appropriate or which are required for Fedora community and the last one which I would like to yeah okay that's a different totally different one the like we have been doing the federal women's day and on the similar line we are have we are successful to doing that so I would like to initiate one more event once a year from our team that is LGBTQA but that that also depends on our benefit and and how we would like to do it just I was just going to say one action item I think we should also take away from that as I feel like we have a lot of things in our issue tracker that while they're good ideas I think we might need to reconsider how we want to approach them and I see thinking of it from the perspective of how can we partner with other groups so I think the action item is review our all of our like tickets that have been open for a really long time we've been stuck on the ones that are you older than eight months a year and figure out like can we as a small team that we are push these things forward or do we need to find partners to help us like move this feedback in a place where it can be acted on so we definitely would like to do that so I can actually I can I could take that action item to do like a preliminary review through our our holistic review through all of our tickets and put some feedback in like for questions to ask and then we could review them at a meeting or a synchronously later on I think what we can do is we can make repo of the years like the current year the goals we have discussed we should have the issues of those goals in under that year only and the next year we have the another one so even if we have some ticket or the idea for the future one we just keep it in the separate repo so that we don't go there and spend time over there I'm not sure if I follow the suggestion which is something that every team is suffering in Fedora like including Fesco for example design so like we can kind of have it as a test for our team seeing how to make the onboarding easier and having also like people that they were very active in our team but they were kind of burned out or whatever and they are not active anymore even like what approach to have even for that is something that will be helpful not only for our team but for every team in Fedora and it's something super helpful and I think like super important that we can work on yeah for all the teams exactly that's a very good point even a while back I was like hesitant to send an email you remember that right but and we have to do it because we I had a talk with discussion Ben Cotton which I need to share in the upcoming slides about the elections and he was talking to me about the eligibility of the vote how people should vote on what criteria so I would like to keep it in within the team I would like to know your perspective as well for the diversity advisor because not many other people know the community know that what a DI advisor does and who it is the appropriate person for that but for that we need to clean our fast group right so and it was very difficult for me to send up that email I have never done it it is my draft so we have if we have the process in place we just need to follow that right we will not be like hesitant for implementing what is correct okay so to that note you will be taking care of cleaning the ticket I leave the implementation to you I was gonna say this is a time check we're at three minutes till the first 45 minute mark so I was thinking maybe we can so this I was thinking like for the the general goals maybe we can recap all of our action items that we were just discussing and then wrap up here and move on to the event guidelines next so do you have all the extra items up there on your end I have four you want to read them out the coffee with friends we're gonna make it the ongoing activity the second one is the guidelines we're gonna create bring in the guidelines the first one to start it with cleaning off the fast or keeping that up to date that is the guideline we can look up to the different companies communities and share it with our community groups the third one is making more connection with how do we develop more connection with the existing groups like mindshare and festco the fourth one is which we have not discussed but we can still open a ticket and discuss over there is the LGBTQ event how we want to do it or if we want to do it as a team or okay we can move on and I guess also the like ticket triage as well was that a fifth one yes yes cool so do we want to put names on those for now or we want to try to time box I think we can we can we should put names that will be the best thing ticket triage so for the ticket triage I can I can follow up on our past ones and rethink about how I feel like in some ways maybe that's related to the working together maybe that's two action items and one because it's really thinking how can we collaborate with other communities well I think that's also looking at the things that we're doing already and seeing where can we push those like either can we do them or do we need to work with another group would you say that they're the same which to the guidelines one and the group one cross all right thinking about how we can start collaborating with other other sub projects in Fedora like connecting them together and and driving that through like the other committees like mindshare council and me going through our ticket triage and thinking of that going through with that perspective make sense okay this tour of Justin LGBTQ event I can take if anybody wants to take please feel free this coffee with friends I guess taktika you can take that up because you started it thank you guidelines for different things though I I'm okay Nikhil and Pooja to take it up but I feel somebody who has a little bit more experience should be helping them because you will know the other communities more than them so you need to help them so Yona will help Justin as Nikhil and Pooja for that so Nikhil and Pooja will be doing that and you know will be helping them so we are good here I think so cool I would like to invite B don't make anybody fall hello don't fall again please so so now I'll be talking a little bit about Fedora event guidelines so we we have been working on this since the since last two years almost now and so the aim for this is that we want to make like Fedora events more diverse and inclusive so we want to provide a set of guidelines to event organizers within our community on how they can do this and I like last year at flock we presented like some draft of these guidelines however like they received a lot of feedback on it and then now we have decided to reiterate and here is a second draft proposal for this so I before so the link for the draft is there the link which I recommend you to all open because we'll be having an activity based on the draft proposal now okay and so I just want to just highlight these two points before we before you read the draft the first thing is that like the draft proposal is for like all event organizers who are a part of Fedora community so if you are organizing a Fedora event like a Fedora release party or like Fedora women's day or even flock it's applicable to them so the scale of events ranges from like local events say like 10 to 20 people to flock which is like I don't know hundred people but like pretty big so and another thing is like all these guidelines are suggestions there nothing is mandatory here we want to discuss more about how we implement this if we want to make something mandatory or like how we ensure that community goes through this and tries to work through this but right now they are all like written up as suggestions nothing is mandatory and we I would love your feedback on the whole draft proposal so I have created a small activity based on how we can how you can give feedback for this our draft so the first thing I want you to do is just go through the in beginning sections introduction the note on leaving feedback and how to use this guide I want like everyone to read this section so then get a basic overview of what the guidelines are about and how to go through the proposal the next thing I want you to do is pick a section of interest whichever you like ideally we would all pick different sections so that we can have different recommendations from each section and for that section I want you to go through like all the guidelines in that section and evaluate based on these three questions ABC so first one is like is this is the language clear is it understandable can you do know what it's saying the second one is for this suggestion what do you think like what would be the efforts required and what would be the impact you think it could have would it be low medium or high and I would prefer that you think like as you are an organizer of a Fedora release party so on a small scale so think like you are you're going to organize a Fedora release party in your local community and like do you think you can implement this guideline what would be the efforts required from you what impact would you have and if you identify a low effort but like high impact guideline just put a small apple near it and if you identify a high effort high impact guideline put a green check mark near it we already have some of these in the document feel free to if if you don't think some of the suggestions are tagged accurately feel free to write it down I'll pass you all sticky notes so you'll know about it and we can then discuss this later the third thing I want you to think about is like what more resources do you need to implement this do you need any support from the diversity and inclusion team or from somewhere outside of Fedora or just do you need to do a lot of research work in on the internet to implement this and so it you don't think it would be feasible for you to do this so I want you to think of three questions for each guideline in the section you select and one another broad thing I would like to use your thoughts on is that like the evaluation method like we discussed like should we have all these as suggestions but then if all of them are suggestions how do we actually ensure that the community tries to do some of them at least so so do we encourage people to implement like all of the low effort ones or like how do we go on about this so please think about like the implementation suggestions too and then after 15-20 minutes after you have gone through the selector section we can redo the feedback yeah so if you can just tell me I will write down here what section you choose okay so Yona wants COC feel free to take a smaller subsection to because sections are sometimes too long but then take like multiple ones so that it's not too small then again okay Nikhil wants even over in the issued tracker do you want a section yeah don't mean to read out all the sections for everyone in the room where we split them up so we have an organizing committee we have venue selection and on-site services catering COC Yona is doing participant and speaker selection event registration Nikhil is doing that child care inclusive practices during check-in grant scholarships assessments of the event and then I don't know if the resources are all there is resources one or all three of them okay so yeah so that's it it would be nice to have your feedback here too in person so you want speaker selection who just want speaker selection includes a practices during check-in for Tatika no she's doing child care so that's good so it leaves we have organizing committee venue selection and on-site services well open the section yes it isn't a lot so I'll pass you sticky notes if you have any feedback right on the sticky notes so yeah you can do COC and organizing committee together yep you can add organizing committee for Yona I can do scholarships and grants figure you be a student again so that leaves us with we still have catering which looks like a pretty small section is venue selection up there yet that's a huge venue selection is a huge one oh so I'm doing venue selection you can also add grant scholarships I'll look at that one too or do we have oh okay yeah been just kidding we have oh there's still assessment of an event like a post assessment which is unclaimed so I'm just gonna read them all off again and we'll check that we have them yeah sorry I'm just gonna read through the big idols and you can just if we have them all organizing committee venue selection and on-site services which is me catering so catering COC which is Yona participant in speaker selection fuzha event registration Nikhil child care Amita inclusive practices ring check in Tatika grant scholarships be assessment of the event you want to take that one be it's a small section yeah so you can do grants and the assessment of the event if you have seen the gender neutral bathrooms quite rooms it's all we have provided some guidelines to the council and they went organizers that these should be included while doing the events so we have more guidelines and for under catering also we have provided some guidelines and we have written it in the doc we would like to have your feedback on that thank you very much I hope everybody knows what to do so let's start and and what is training what is it for for when you say training you have so usually like I in other conferences what I have seen for speaker training is that they have a session a 30 minute like video call or a virtual session with new speakers who are like first-time speakers they provide them like say this templates they give them guidelines on how you should like the font you should use and how you should design your slides how you should speak what is okay what is not okay okay okay this you need much training with templates and with the expertise because when you send a new member of the community to the first talk release party I go with this member to the university to the release party whatever I go and I say okay no problem stay here speak I have I have this guy this is this is the yeah but you just this is sort of training but you are doing it as a mentor like for one person we want to do it for everybody like in a generalized way because sometimes not everybody might know you okay to do that so we just want to offer like some templates some resources that you can read through this links if you are a new speaker and this will be helpful for how many years you have in the community a lot 10 years 10 years in the community you remember you remember the wiki page have a lot of templates for your slides yes a slide template well I think that's a conversation that we would want I think that it's a that's a great feedback I think that's the kind of like that would be like I think maybe we should try to take some of this feedback and come up with like our action items just as a time check we have 45 minutes I'm thinking like because that would actually be like like Lewis like that would be great feedback for the mind-share committee because you know they're they're the team that's trying to like make the you know going out to talk about Fedora and make doing these things easier for people and that's exactly the kind of feedback that you know be like hey like I'm trying to find these things and like I don't know where they are anymore that is like totally justifiable and that's the kind of thing the mind-share committee should be I really wish I could jump into their hack fat or their their workshop right now but for that is specifically I don't think mind-share will have to do anything you should fill the ticket with the sign for that kind of resources and do it no but I think because they they're already created that's my interpretation refreshes never boring as I said after the I read Lewis's feedback differently that like there's not a refresh that's needed but like fine like resurfacing these resources maybe maybe what's better I know you're tired on time by section section you just want to do maybe like quick readouts everyone just like kind goes through their feedback so I will go to one section read out the feedback in that section and then we can discuss that we have 15 minutes left for this slot now so yeah and then we can go move on to other topics so the first thing which we already started discussion on was like speaker selection which and the feedback here from Lewis and who just was like first what is the speaker training exactly and like do you offer templates for presentation or do you do sessions like how do you do it and Justin was saying that you collaborate with mind-share for this we can discuss it with them partner with them another feedback here was that like when yeah just think could you could you take actions for the things that could be doable because for example I can take care of just doing a unified rep of the science and so for conferences that will be easy doable so we have actions for after this if you if you have template and you have training much this this complete this is a one a one line COC training and offer template is a one line so we want to provide them CEOs like introduce them to what is our code of conduct for Fedora we want to offer them templates if you complete these three lines you come you cover the COC vote because okay you are on the lines you are completely compliance the guidelines yeah and COC unit core offer templates training example illustrations like what should for like Fedora logo and what is offer scholarships I see one line I really want to hear that offer scholarship scholarship is the last scholarship is in 2011 I remember for it Amar it Amar half this is scholarship so we can just say that at flock we are also we have the diversity grand and like for people to come here okay and for smaller events I we can think about if we want to fund them like but I think we find organizers we don't fund attendees to travel so I don't think like this will be relevant for Fedora community I will just remove that line I will keep it I will remove the line from the dock and the feedback here is keep and keep and maintain okay this is don't run without it this is my real lines okay yeah now we have Pooja's feedback on speaker selection okay thank you okay like we need to keep and maintain the list of possible speakers but how like we if you are organizing our event locally we don't have like the list like how we can approach to other organization or other like we have the local speakers but how to contact with other speakers is there any like platform where we can maybe we can like do you are you saying that we provide links to nearby organizations like pie ladies or something like how we can connect the other there should be some like guidelines or some like platform where like a template message you which you can use to send to my ladies contacts yeah like you cannot sometimes sometimes we may not know like what are the other communities or because sometimes we did we are like out of thought legs from the home we should contact we don't have the speaker for the event every time the same speakers are there so to have the diversity or to have the new speakers we should have something like that okay and what is selecting speaker there was a consider color blindness in slight design consider color blindness in the slight design so I didn't get this like how the speaker will so usually I mean that can be covered in the templates too but generally people are like red green color blind so then if you put some visualization which only has green so like that so we can do it in the templates thank you thanks a lot for the feedback so next section we move on to Yona for if you want to so I'm just one second Pooja can I have the notes please okay so Yona section is on code of conduct and organizing and her feedback is like yeah so basically like in general what is written yeah like is it's a very nice guide but it not really applies to Fedora and especially keeping in mind that usually the organizing teams are very small so like having one person taking care of all this I feel it's too much maybe the DNI can help with some stuff but otherwise I think like it's putting them more work so like I said before like not not everything has to be implemented by everyone so some some like suggestions are for like release parties but some are also cable only to flock yeah but I'm saying that this applies even to flock I would say because it's not that many people that are part of the team one thing there in the organizing committee thing which I really liked was to have like a diversity representative and in the organizing committee I'm not sure if we do that in flock already I know like the all existing organizers take care of this but I would say for example in that case would be great someone for example from our team to be kind of responsible and be keeping in contact with them like keep in touch with them and tell them hey we would like to have these things at flock can we make sure this happened yes this like would be great for flock and maybe apply the same even like for smaller smaller events but having something from their team to do this I think would be too much even if we have these things maybe I don't know written somewhere maybe a suggested action item from that we already have this flock CFP committee and the organizing committee and they do pull people from the community to already be on those teams but that how that's chosen is not clear we could deliver that feedback to try to make sure that a diversity perspective is included in the CFP committee and like the existing teams that like the existing committees like yeah like I I would say just like I what I would say from this that would apply for our events not only flock even smaller ones is to have someone from the DNI speaking with the organizers I especially I would say for flock because small ones the organizing team is even smaller but for flock having someone with responsible or someone that wants to take care of this and just like speaking with the organizing team would be the the best approach so we talk with the flock organizing committee give them a list of recommendations which we want to see for next year yes we keep in touch with them to see that they implemented yes so that's what I have from the organizing committee should I continue with you so for COC I have made some comments directly at the document mostly it's just to be honest just like the way how they are written so I don't think it's like very important like the registration which like should be registration form I guess because or it's because in the beginning I read it like the registration desk which I think is the registration form the second one is include a copy of the COC in the sponsor packet I'm not sure what it means we can just like put a link to COC here on the badge well it is I think or not I don't see okay yeah sorry that's true so that can be a simple thing it's not to be difficult and people can know what where to look for yeah but this is not written so maybe we should add this but sponsor packet I don't know what that means yeah I will edit it because okay so these guidelines are basically devised version but it can be like the sponsorship prospectus probably and I think this can apply for even flock or small events when they want to partner with some other sponsors another okay and the other thing is that it's not very clear the last part when it where it says like make it clear what the consequences or resolutions of a violation are consider a visual workflow of code of contact violation so this need to have more support from us something that can be done from the DNI team or someone that knows how to do it and just give them ready so they can have it at their event otherwise just reading like it is it's not clear would be way more work for them so that would make it more complicated okay so thanks for your feedback you know yes go for it so so I was going through the venue selection feedback and I came up with one two three four five I thought there was it just five so I look at some specific things there were talked about ASL and captioning remote and remote access I thought captioning could be one investment from the DNI team for the flock video budget and also thinking of ASL captioning getting there so I think because later in the document it talks about ASL and captioning as an option for event talks and I thought maybe live captioning could be better than ASL as a way to start making this a part of the and this is this is flock specific as I know there's multiple sign languages it's not like ASL is really big in the US because it's American Sign Language but that's not consistent around the rest of the world and I also feel like with live captioning even non-deaf hard of hearing people can also benefit from that so it might be an easier like you know like it'd be I feel like it might you know if you have like an interpreter live interpreter and there's no one understand the positive point so we need to figure out if we can allocate our budget to real-time live captioning every year but I like because I know this is a very contentious topic in the ASL or in the deaf hard of hearing community I'd like to get external feedback on that I think we need to like reach out I can't take that action item gender-neutral bathrooms in the dock it was a green check mark but I think that could actually be an apple for tampons and pads I thought that could be required for large events like flock and it mentioned doing it in both like both gender restrooms as well and then there was another part about no standing zone so this is something for when you have like in out in the hallways there would be like a taped off area that's explicitly like taped or taped aside so like someone with a wheelchair it'll always be free of people so someone with a wheelchair can get through a narrow hallway so people don't you know spread out in the hallway and I felt like that's easy enough to do like you just have to set tape in a hallway and like I know like and that's something that's easier for us to see because we have people in our community who aren't wheelchairs too so I mean those were just five takeaways that I looked at some things that I okay I thought about okay so first first point was in the event resolution it was regarding the what to ask and what to not maybe we should be specific here maybe collecting we are collecting the data from the users right yeah so I guess there are some policies in so we wanted to do a survey too so there is this thing and I think we need to talk more if we are going to go back for a feedback survey after the event or like a registration so then what we include and what not yeah so we need to figure out the legal issues of that apart from that what is okay that was the point and I guess we need to mention it somewhere or put it action items for okay so for the people who joined recently we are working on a proposal for event guidelines to make our events more diverse and inclusive these are the areas we are covering we just did a quick review through the proposal and these is this is the feedback and everybody is going through their feedback like what based on the draft yeah so for the childcare facilities the first point of course is the budget and we need to figure that out and then second even before the budget we would like to take the feedback from the people who are like the contributors and everybody the attendees of these events that would they like to take this facility or not would they actually be you know utilizing this facility and the second thing is or they would like to take a break from exactly so and the second thing is will not having children around distractors from the work in event registration second part was the t-shirts regarding the sizes there should be some standards as us sizes and the other countries sizes are different so maybe yeah maybe that point we can add it in here and regarding the last one that was related to the photo policy here you have included if you will have photographer at the event include information for attendees explaining that they may be photographed or not and how to opt-out them for the from the registration so what is the implementation part so we have a line yard for this already that you can just stick if you don't want to opt out I think I think like for this block they have a tag or some line yard that if you don't want to be in photos the red one if you don't want to be in photos you put the red one so then the mission is beside the line yard it was telegram group the red ones were next to the paper that said really big no if you don't want photos you take it up here so we need to make it more visible in size that actually for me I think taking a lot of pictures was really easy just to even if I took a picture by accident of someone wearing a red lingerie then I could just cut it okay so sorry I'm just going to go through my feedback first because we are almost out of time so my feedback is mainly so I so my feedback was mainly for like for the assessment part suppose if we decide to do a survey if it goes if we talk to legal and they say it's okay to go through like a survey which doesn't collect any demographic information or like organizers can themselves ask through event-bride registration or something then for that survey maybe we need to provide like an assessment template to the organizer so that it is not like an additional word so we can have a small template and they can just use that template to collect feedback so that was my feedback on the assessment part and that and for me the grand thing like donations were a good suggestion and I think we can do that it has like high impact like and high effort so basically the idea was that for grants people can donate like we already do it flock so you can cover somebody's budget and so we are already doing that so I just like I think that was to put a green checkmark and for Xavier's feedback I think the feedback is like so his feedback is okay everything is crystal pure yeah so we are out of time so I think we should move on to next I will write down this feedback in the dock and we can reiterate over the actionable items let's see what we have next Fedora women's day how much time 25 minutes do we want to somebody would like to come here and the translation what we have not edited okay so the translation one the important content translation that's what you want to cover that as well okay so since we have the people from the translation team we would like to cover this ticket which we have opened few days back there was a comment on Matthew Miller's new strategy for Fedora and the goals for Fedora article that the English written over there is too complicated to understand for that person even if you understand that English so we wanted the diversity team want that these messages which are very critical for the community should reach out to more and more people and at least these important messages should be translated in the all possible languages from where our contributors are so that is what the topic was and maybe I think to add some context just to try to draw it really focuses conversation we realize that there's some things that may have like a really high impact value on the translation side but one of the things that's confusing for us is we don't we want to work better with the localization and internationalization teams and we want to find more ways that we as the diversity and inclusion team can collaborate better and have like because we don't we don't want to do all the I really we don't take on the work of the translations because that's what's already being done in the community so we want to find ways to better collaborate and kind of work together on these things I can pass under okay it works so there's two things the first one is the source language being too difficult to understand we cannot do anything this is the this is the writer who have to improve this and it's also an issue that we have we as translator to have some strings that are too technical or using a lot of French the name is jargon which is you use some technical words that you use colleagues but the people outside of this world don't understand anything so this part we cannot do much but what we can do for for allowing to to translate announcement is you can do the new translation system of documentation and this is ready already Adam and I we did the work together so any any content you will publish under documentation diversity parts will be translated in any kind of languages so maybe one way we can start collaborating better is when we see like a high priority like item or something like you know they're like the mission like the revision of the mission statement articles one way we could work with the maybe the Fedora Council is incorporate this feedback loop for them where they will go to a document take one of the Fedora docs repositories and open an issue open a pull request with the source in like ASCII doc and would that make it like what would make it easy what would make it easy for the internationalization team to take this content and translate it like what's the best approach that you that you think would be first of all we need no issue or think like that no no and Pedro we need more emails on the international translation mailing list containing what is to translate what to translate and what's the publishing process so where to translate and what's the publishing process is can be solved if you use the document documentation translation system so you just have to send us an email we discussed with the Council and our group we this page is really important for us to be translated can you please go translate it and and you give the link and we will do it but there's nothing really formal for now in the localization community we need to set up every new process so probably the best way to start driving the conversation is to better engage with like the mailing list since it seems like that's where most of the it's it would be what what is it this will be mandatory as I see that the first step is to publish the internalization and the localized content of the of our documentation system and this is will be done once we have a web late translation platform installed for the federal community which will be in the coming month before December for sure but in the coming month so once we have this live and walking then you can come and say this is we think this is very important for the international community to know and you will share the link and we will do our best to translate it and maybe just one more one more idea of one way we could do this is what if we I'm just curious if you think this would be helpful or not but working with the Fedora Council for them to create a doc repository in their workflow and when they want to publish an announcement so that would be on the Fedora magazine they might push the content into that doc repo as well and would be a special like a specific repository for those announcements so you want to publish some some localized announcements on the Fedora magazines the ones that like say like for it wasn't all magazine articles but in this case it was like the mission the mission the change of the mission statement and things that have a very like have very like difficult to understand language for non-english speakers and might be harder to interpret so I think maybe like the first thing I'm hearing from you is one we need to like engage better with the mailing list because that's where most of the internationalization community is and then two I this is just me trying out an idea because I'm thinking like how can we get the Fedora Council to also buy in on this and how can we make it easy for localization and how can we make it easy for the Fedora Council to help you guys out with this too the challenge is the tooling we have an answer for the documentation that will come but we have no nothing for the community blog or the Fedora magazine for now it's part of the thing that we should address but for now we have no solution to publish on the Fedora magazine in multiple languages some community will love to do it but for the moment we are using WordPress and I'm not sure we have the appropriate tooling in WordPress to support our translation team so I mean like a initial thing we could do here to support different languages is that we just add links to the translated text in the original article published on say community blog yes so we can do that for now you will be able to do it in a few months but not today today if you want to publish something in multiple language I just invite you to find a trick with the WordPress system to just display to make something with tabs and stuff but it will be do it yourself solution so I think since this is on the roadmap this seemed like this could be one way to do it since the docs localization is this is the only serious way to do it in the close future and we would love I think the localization committee would be would love to be able to publish some content on the website in their own language but for now there is no process for that and there's no tooling for that this is almost the biggest problem okay for the Fedora magazine in the community blog I think for those workflows those aren't we have a lot of people who write articles with like the web interface and aren't really familiar with like git or there they might be like first-time contributors I think it'd be really difficult to move outside of those those workflows for those teams so we're trying to find like the two kind of things I'm reading from this to take away our like one coming up with a better way for the DNI team and maybe the council as well to engage on the internationalization mailing lists and maybe as a workaround since we've we've faced this issue even since like for four years I've I've seen the same conversation about the WordPress sites being difficult to translate so maybe now that we finally have this docs localization piece coming in and that's what we're already encouraging people to you will will use to do the internationalization so people will hopefully be comfortable with that already that could be a way that we could work around the pains of you know of the WordPress translation and we can try to focus on when there's really important things at the Fedora Council or someone is trying to push out to engage with that localization process for these articles before publishing does those two things sound like a fair to be efficient and to be to be able to scale like integrating multiple teams even if they are little is we need to always use the translation platform and to use the translation platform means having a set of tools to generate content from English to translation file translation file to localize content and this is the only way to be very efficient with the translator community if if you want from time to time so you can totally send a text message to the translation mailing list saying please send us back this translation of this text for this deadline make it reasonable so we have sufficient time you know what is translating this can work for one or two times but it will never scale or be sustainable over time so if you correct like you want to publish an article next week or next month so I don't know and you want the translator community to contribute this you create a page of repository you put your content and you say you send an email say this is the content this is the deadline to publish the content either open up a request open an issue or send an email to that email address and we can do that but I think the best is to first focus on the documentation system we use because I think it would be way easier for everyone you will be able to travel following you your reason and we will have our tools and our publishing system to do it automatically it will be way more smooth and for now I think the subject about localization of the federal magazine of federal community blog I think we are quite far from being able to do that so we just I think just using some tricks with a workplace to once in a while publishing localized content we'll do it for now but that's my personal opinion and cool so just so I want to make sure we have time to cover the last topic for our session and make the group photo I'm gonna say so here's what I'm going to do I'm gonna go into the the DNI team ticket and summarize a bit of this discussion and I want to move this conversation to the council as well about how we can engage with them for content that they feel is important how we can have that relationship with the internationalization team so that's what I'll do in the next 20 minutes here to drive this conversation outside of the session information as diversity teams with this morning about federal localization objectives we could have the first one is to help local communities to with providing some tools for them to discuss in their own language and to exist in their own language and the second one is to provide some tools for the translator community to have them being more efficient globally speaking in term of translation so we will probably discuss the first point together because it's a huge subject excellent I'll tag you in the comment or in the ticket comment as well and we can follow up there very good thanks thanks for all the localization folks who came by do you have anything to add is it good perfect so one one ask over here for the Fedora Women's Day is to ask more and more people to submit the proposal and it is for all of you that we gonna ping more people to submit the proposals before the deadline okay and I will quickly move on to the team processes now I would like to brief about the DI council representative elections and what are the things which we need to cover in that I had a brief discussion with Ben Cotton this morning about the election process which we need to follow and what data he needs so we need to open for open up the elections for the nominations first we need to decide on how much time duration these nomination will be open the nomination window and then we need to interview these nominated people for the position and then we need to open it up for the voting process so we first thing which we need to decide is on the time frame when we would like to do it and for how long we need to open these windows for the nominations for the interview and for the voting process and then the most critical part is the eligibility for the voting


Everybody, it is board meeting. We're still only missing Angie, so hopefully she'll find her way soon, but it's still near. Denise will not be in attendance and Mike Lam will not be in attendance. So normally they're also, they're on the boards obviously, but we have forums so we can proceed. This is, this is an open board meeting, so we encourage all of you to ask questions or to, you know, if you have anything to say, feel free to raise your hand and we'll look you in. The agenda for today is pretty simple. We're going to do an operational update that will come from Holly. We will have very quick discussion or updates from the different board committees. That will only take five minutes and then we're going to talk about the board election process. And then last but not least, there is an update on Groupal 8 and how the Groupal Association is going to help with the marketing of Groupal 8 and the confidence strategy around it specifically. So with that, I'll do the floor to Holly. Great. So yeah, thanks everyone for showing up, staff included. And as Denise mentioned, it is an open board meeting and we get to do these twice a year and it's fun to have people in the room. So do feel free to ask questions as we go along. The operational update we're covering the month of August in this board meeting. And so some of the highlights for us as of the release of the board packet, we had the engineering team and knocked out all the release candidate blockers for Groupal 8. So everything on Groupal.org that was a release blocker for eight coming out is now taken care of, which is fantastic. There are a couple of housekeeping items for an actual Groupal 8 release as follow-ups, but those are on track as well. And we feel really good about that. And we also launched a new pilot program at the end of the summer called Camp Connect. And a few folks are familiar with the WordPress community. One of the things that they do for their camps is help support those local camps by doing fundraising, sponsorship fundraising for camps and then giving the money out to the camps so that they can, they don't have to worry about that part. So we're piloting a program for camps, some of the camps in the Q4 timeframe, the fourth quarter. They opted in to be part of the program. We are working with sponsors who want to pull their money through the DA and hand that out to camps. So we're piloting that in Q4 and we've gotten lots of positive response both from camps and from sponsors. And if that goes well, we'll start to offer that out to camps more broadly in the future. That was a fun one too. Some camps didn't want to participate. They've got their sponsorship stuff down. They're great. That's fantastic. But I think especially for newer camps, this will be a nice service and it'll help generate more community engagement all over the globe. So we're pretty excited about that. On the things to watch lists, progress to mid-year adjustment. So again, in the month of June, we did do a retrenchment for the association. Revenue was not coming in as planned, although it is up year over year. It wasn't what we wanted it to be. And so we have a new plan, a new financial plan for the rest of the year and we're watching that progress. Some things are doing fine and some things continue to be very slow and soft. So that's an area where we are putting a lot of attention and basically every couple of weeks we've got updates there and are making adjustments. So that is something that we're watching. An additional thing that we launched this year as a pilot program is a co-marketing campaign for Europe in particular. We purchased a booth space at two European marketing events, D-Mexico, which just happened in Cologne, Germany. And the Festival of Marketing in London, which makes me laugh. It's the Festival of Marketing. I don't know. There's something hilarious about that to me. But is there a Ferris wheel? I don't know. Exactly. I love it though. So we got booth space at both those events and have invited European shops to basically come in on that space with us so that we can represent Drupal and not just the shops at the event. So it's a way to get the Drupal brand name out there a little more strongly. And we had moderate participation from the shops. Some of them had already purchased their own space at D-Mexico, for example. Some people just weren't sure what they might get out of it. But we'll finish out that program this year and see what kind of benefits it does generate for the community. And then we'll look forward. But we're watching that right now. And then just a low light overall with sponsorship revenue for this Drupal Con, which was much lower than anticipated and also lower than we received for Amsterdam. And so that was definitely a tough one. A big part of that was that we did have one sponsor who had a very big presence here and just changed strategic direction. It didn't really make sense as a tool for them anymore. And we just didn't replace that revenue. That was a big part of it. And then we always see in the European cons, there's a lot of regionality. So if you don't do business in Spain, you're not as interested in being a sponsor. And just the business community in Spain was not as robust as we saw in Amsterdam. So that definitely affected sponsorship income. On the positive side for this Con, though, I will say we ended up meeting the registration goal that we thought we would get for this Con. So we've had about 2,050 to 2,100 people register for this Con. So we feel like it's a good community representation here. It's not as big as Amsterdam, which was 2,300, but it's much bigger than Prague, which is about 1850. And that just, I think, speaks to location as a driver for Con attendance in particular. But we feel like there's a good strong community turnout here and we're really pleased with that. So it's a low light, but I ended with a highlight because that's what I do. That's the operational update. Any questions about that from anyone? Finance committee. Finance committee met as a committee of a whole during the board retreat. The exact committee, I'll speak to them. So we did meet with Molly to follow up on the two-day board retreat that we had earlier this week. And we got aligned on action items and next steps. And then the marketing committee. No meeting, as far as I know. Okay. They did not meet. Any questions on that? This is meant to be short. But if there's questions. The next item is the election process. Awesome. I'll talk again. All right. So let's talk about this here in particular. But the community elections will be coming up in 2016 fairly shortly. And so we're going to start talking about it now in the community and helping people who might be interested in running, you know, learn more about what that means and give them the information they need to run. So that's the point here as more information all then really, you know, way in. If you've got things to weigh in on, let me know. So here's the process we've got mapped out. We're going to talk about what the board does quickly. If you guys have color commentary around that, please do add to it. Deal with your snarky executive director. Only if it's colorful. No boring commentary. Yep. All right. That's great. Sure. It's a circus here. Is that what you're saying? Okay. We'll talk about how nominations, the elections process works, who can run and how they run, what you'll need to do. And then we'll look at the 2016 elections process, not 2015. So what does the board do? One of the things I just want to emphasize is that as a board of the association, you know, we represent on the board or you guys represent on the board a lot of different interests. So the community has like 33,000 really active developers on any given day. There's a million Drupal sites. We have 12% of the top 100,000 of those sites. Oh, it's now over 3,000 Drupal 8 contributors. My point being that it's a very large constituency that the association tries to help represent the interests of. So we have, it's not just a lot of people, but people with an incredible variety of experiences that they're bringing to the association. So, you know, you could be a front end developer, a back end developer, a femur, you know, you could be from Bulgaria, you could be from South America, right? So we have just all kinds of diversity that we're dealing with on any given day. And yet, at the end of the day with the association, the board try to do is represent the community, right? So it's a challenge. But to help try to address some of that diversity, the board composition does that a little bit. So we have three different kinds of directors of the association. There is the founding director, or Dries. He's the only one that can be the founding director. And the board has to reelect him every year for a one year term to serve as the founding director. That seat can be empty. Theoretically, you could be voted off Dries. Yeah. But, but we like them every year. Then we have class directors and class directors serve three years terms. And those are folks who are nominated by the nominating committee and then are approved by the rest of the board. And every year we have a new class of directors that are opened up to be either reconfirmed or new directors that are brought in. And then we have the large directors. And this is where the community representation can also come in. In the class directors, we often think about, you know, what's the mix of people who are on the board? What skills do they have, but also what communities do they represent? And when openings come up, it's a good chance to try to rethink, like, is there someone, is there another skill set or is there another community demographic that we want to represent on the board? With the out large directors, you guys in the community get to make that happen. So folks nominate themselves to run. We elect one person every two years. And the community gets to make that decision. So our two current out large directors are Addison and Matthew. And Matthew's term is about to expire. So that's why we're having another election. So this is our mission. The goal of the board is to support that mission. See that mission come to pass. So you got some duties as a board member to do that. And these are the, these are US laws around board, what board responsibilities are. And the reason we followed that US law is because the association is incorporated in the United States. So that's where we're bound to. But there are three legal duties, duty of care.  That kind of thing. True story. Good luck. Yep. There's a duty of loyalty. There's a duty of loyalty. And this one's interesting because we do have a lot of folks with varied, you know, professional interests on the board. But when you're, when you're putting your board hat on to do board work, right, you put the association above everyone else. Yeah. And then a duty of obedience. And that is not obedience to the organization or the executive director. As it turns out, that's a duty of obedience to the law, right, which in this case is, you know, US Oregon and local local laws for us. And what that means is that, you know, if a board member becomes aware that we're doing something illegal, they have to do something about it. Right. So you are, you're on the hook for that. So those are the legal duties, but practically what ends up happening is that the board spends, you know, a fair amount of time overseeing the financial performance. So when things are smooth sailing, there's a monthly review of the finances by the finance committee. And they make a recommendation quarterly to the full board for approval of the financials. Setting strategy with staff is something we also do. So the staff will come to the board and say, this is the direction that we think that we should head in and here's our evidence for why. And the board weighs in with thoughts like, please, please, please, please, please, please don't do that sometimes or that looks great. Right. So that's their jobs to advise on that. Setting and reviewing policies and this relates to that duty of obedience. So making sure that our financial and human resources policies are compliant with law, you know, labor laws, but also that they can, you know, that's what you guys actually have to approve. But, you know, you also help us make sure those are in line with our values. Fundraising is something that boards typically do as well. So raising money for organizations. And we haven't done a ton of that in the past, but you all did a tremendous job of helping us meet our date accelerate goals. Thank you for that. And then the board is my boss. So if you've never had 12 bosses before or had the chance to be one of 12 boxes for someone else, it's fun. All right. The work of this is to attend a minimum of 10 of a minimum of 10 of the 12 monthly board meetings. The board meets once a month. It's a two hour meeting. There's a one hour public session and a one hour executive session. We have three strategy and planning retreats. So we'll do one in January and then one around each of the North American and European cons. And you're expected to sit on at least one board committee and the committees do typically do more of the actual work, right? So you're going to spend probably five hours or more a month on the board. That sounds good. Familiar to you guys. Okay. So if we haven't scared you away yet and you're interested, how do nominations and elections work? Just to let you know, there is a whole history around this. The community themselves discussed the process that we were going to go through and defined what that was going to be like. In 2014, we revised the bylaws just to change the election process up to that staggered two year term for each of the directors. It had been a one year term for the community elected seats, but it really does take some time in any group to become part of the team and to figure out what's going on no matter how good your onboarding is. And so we wanted to give everyone more time to serve. And then if you care, it's the election module that we use. Someone cares here. All right. How do we do this? So if you're interested, when we open self nominations, there'll be a form to fill out. The key is you have to nominate yourself. You cannot nominate another person to run. We'll publish that time period a couple of weeks long to nominate yourself. And we do ask you to share some information about yourself, a bio, like why do you want to run? You have some relevant experience, et cetera, your photo. None of these very few fields are actually required. I think beyond your user name. So I know there are folks out there who are concerned about putting too much personal info out there, and that's fine. But that's the kind of stuff that we will ask for. And I feel like the more that you can share, the better position you're in. So once you nominate yourself, we have a period where folks can have conversations with you. And then we need to be election. The key thing is that we use instant runoff voting. So we don't do a majority vote. We use instant runoff process. And if you Google that, you'll get a great British YouTube video that involves many post-its. And they explain the process really, really well. And voting is open itself for about a week. And voting is open to anyone who's had a Drupal.org account in the past year. And you had to have registered your account prior to the nomination. That's the bit that gets cut off on this slide. If you have a D.do account before nominations open, then you can vote. All right. Who can run? Anyone can run, right? So anyone can definitely be part of it. And I think we do our best to onboard new board members and help them understand what's going to happen. But I think board service is much easier if you've had some other kinds of experience before. So if you've been on another kind of board, particularly if you're good at reading financial data, you're good at reading financial documents. That's something you do a lot of. If you've been on a community committee within Drupal, then you are accustomed to how committees work. And the board is essentially committee. Strategic planning is great because that's the kind of level that we try to have discussions at. Not down in the implementation details, but what's the direction we're heading. That's the kind of discussion we try to have at the board level. And then policy development because that comes up as well. And again, you just have to nominate yourself. And we'll publish that nomination form when the nomination period is over. As a candidate, just to give you a sample of what a nomination form looks like, what you'll have on that page is a Q&A section. So as a candidate, your job is to answer questions that are posed by the community. We will have a Meet the Candidates webcast. We'll have several of those that you can participate in. We'll have a chance to field questions from the community as well.  It's a really good way to spread the word about the elections in general as well, which we love to see happen. So the timeline for folks who are interested, nominations are going to open on February 1st. So it's a few months off. But if you're thinking about it, that's when your target date is. Then we'll have a couple of weeks of Meet the Candidate. So nominations will be published on the 19th or the 20th. And then we'll have Meet the Candidate sessions and that open Q&A period on your candidate pages. We'll vote March 7th through the 18th. And then we'll be able to communicate everything out on March 25th. So there will be a few days of lag between voting closing and us getting the announcement out. And that's only because we have to get the board together to ratify the results. You know, it's not technically challenging. It's just to convene people. So we'll get that out. So that's the timeline and that is it. So any questions or I know we have some folks in the room at Chris and Schnitzel. You guys have run before any advice for folks? No. Right a good bio. Oh, there's Chris. Gotcha. Any questions about that? Yeah, yeah, yeah. Okay, so just a block that says here's what the process is and here's where we are in the process. Okay, that's good feedback. And we're actually meeting in a couple of weeks to have our first to write some stories up for that process. So that's good. Other thoughts or questions or feedback? Yes. And for board members who don't know Phil, let me introduce Phil Boulevard, who's our communications manager.  And Phil, I'm going to operate those slides, but he's going to wink at me when I'm supposed to forward them. Not. Okay. That's more appropriate. Not. Okay. So first of all, I want to give out a quick shout out to Bradley's. So I said, sure, I'd love to. Sounds fun. That's terrifying. The reason I said it was such enthusiasm is because I knew that Bradley had already been working on this for our team. For over a month. So thank you Bradley for letting me use a lot of your work in this presentation. And I also want to say that this presentation is mostly focused on the upcoming release candidate. But it's easily extrapolated when we're closer to the first release candidate. It's almost here. And I think we want to do at the association is really celebrate the work that's been done so far and to get ready for the work that's starting up. And there's some big ideas that we want everyone to know about. And those big ideas are that it's here. It makes Drupal better than ever. It'll help you create better. People are doing great things with it right now. Even more people plan to get involved soon. And we want people to try it out and tell the people about it. Okay. So these are your base messages. Yes, exactly. Okay. The way the Drupal Association can share these ideas are through or that we plan to share these ideas is through four kinds of content. So going down the left column, the kinds of content are awareness, research and education, comparison and validation and choice. And if you go now horizontally, the purpose for awareness would be we want to make it clear that the release candidate is available. And the big idea that would tie to that is here. On research and education, it's we want people to learn about the features and how those features can be used. And the big ideas would be it makes Drupal better than ever. People are doing great things with it now and even more people plan to get involved soon. On the comparison and validation, we want people to be able to evaluate whether it's going to be a good fit for them. The big ideas are it makes Drupal better than ever and it will help you create better. Choice, we want people to choose and promote choosing Drupal 8. Big ideas are try it out and tell the people about it. Our plan is to use different initiatives for each kind of content. So same chart, just kind of adding another column on the right around the initiatives. And the reason awareness and choice are bolded here is because really that's where the Drupal Association has the ability and the resources to focus. We'll talk more about research and education and comparison and validation later. So awareness, jumping over to the far right column. The initiatives that we plan to use to support this would be news articles or a news article, excuse me, on Drupal.org. Updates on our social platforms. Email newsletters and specific email announcements to our email list on the choice. Download Drupal 8. Calls to action. All over the site. And so where we could really use some help from the community to push this out there is through all of these various types of content that are available to the community. So blog posts, tutorials, testimonials, case studies, lateral, etc. We have all kinds of different ways that the community can help us. Filly community. That won't be disarming at all. Where they could really help us out with research and education. Do you want to talk a little bit about why those are specifically well positioned for the community as opposed to the association? It's really about resources and also just the reach and the connection that they have through their clients and through the people where they really have the power around case studies. Case studies, video, it's just more resources, more volume of content. There are recent changes to the marketplace. Yeah, so as I was saying, let me see if there were any really helpful tutorials, testimonials from clients about how she is going and working for them. And blog posts about the eight versus the seven so that. Most of the. So blog posts about solving common challenges, targeted emails to their client basis. Webinars around specific industries and verticals and launch parties. So talk about that more later. Is anyone going to host a large party. So, one of the things we'd like to do is figure out how we can unite all of these efforts. And obviously social is a great way. And so what we would like to do is start using through full eight RC one. Hashtag. Through all of our social channels and ask the community to do the same. And then also hashtag around made with group late for celebrating specific projects. And those are two ways that we can really kind of aggregate and be able to search for content more easily across all the very social channels. And then there's a group. As you don't know, our groups dot group dot org group late production sites. So if we could get people to share their stories about people implementations. In that particular group, then again, a great way to aggregate all of the content. And then also when people are on through the dot org creating content tagging that with triple eight RC one. And then also directing media to our upcoming news article. And then translation is. Good job. So everything that the Drupal Association will produce will be created comments so please take advantage of it and use it. And then also I spoke with Karen. Yesterday and he showed me the seven. Pages that were created and all the translations that were done there. So we'll be reaching out to that. To play. And then we said plan to have a large party. And we will help spread the word. So we created a landing page. Launch party association. It's a web forum where people can go give us some information. We'll collect that information as we get closer. We will start to promote that, promote those parties. And again, Karen gave me some great ideas as to how we can do that. And of course, test test test. After we get through the RC one, the faster we get to the version release. And that's it. That's the page where all the good stuff will go. Yeah. I know. Drupal hyphen 8.0. For nerds. Right. Yes, you do this. The magic, the marketing URL does open up to the nerd URL. It's true. Good redirect. Any questions about the marketing plan there or ideas that we should be considering. Yes. I was just a good point. Maybe we just go with RC. RC hex. Yeah. Okay. It wrote it down. We just basically come out of the conversation about the contribution and showing who did it. And I was wondering. And all that was shown was about what people. You didn't show anything about who actually did it. I was wondering if there's anything that. Emphasizes on. There's a link. I was part of that. Mm hmm. Let me take that idea. Yeah. Yeah, it's a great idea. I like that too. Maybe a little badge to wear. Something like that. To be good block on the eight landing page is just a rotating thing of contributors. Right. Yeah. Yeah. You work on that. That could be your community contribution. Yeah. Your idea. I guess you get to do it. You don't learn that yet. All right. And you had thought also. Look what I read in the paper. Go do it. Right. So let me explain. Which is. Yep. Yeah. Let me try that again. So what I mean is currently, we do have a small press list currently. So we'll definitely push out to these journalists that we've already interacted with in the past for. Various seat related announcements. But we don't have a big broad list. And we definitely know that that's a whole. And that usually gets filled by some of the bigger companies in the space. That said, I did just get a couple of contacts last week. For some PR agencies that have done some open source software work in the past. So it's possible you might get from low cost or free resources to help do some PR work for the release. But that'll be the big. We'll do that at the. Not the RC stage, but at the actual release. So. Yeah. So hopefully yes. But I, you know, I think through fool be fairly well represented. But it'd be nice to be able to push that out from from these decisions more strongly. For sure. Small detail. But I think in the hashtag, I think it would be useful to. Instead of the age. People see that on a speed out of conflict. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah.  The landing page already has some of that, I think, but we can certainly expand on it and or maybe simplify it and create. Yeah. Anything else on that. Yep. Definitely on our radar. Yeah. Yeah, we've definitely had conversations with a couple of partners already, but we'll. I think that'll be. That's been a very successful program for us in terms of getting people to actually, you know, install Drupal on a trial environment. And so get, I think. We'll get lots of eyeballs on Drupal, Drupal eight that way. Yeah. Anything else. Any, any questions outside of the things we discussed. Billboards, buses. What did I say about billboards, Donna? I'm calling. Yeah. Yeah. Yeah. I've always wanted one of those balloons. No, the sky balloons. Yeah. Yeah. I mean, getting the announcements in early getting it out to people to help translate and then making those available. I think it's going to be really great. Good. I think we have one official, unofficial order of business to take care of. We are talking about burnout. That's fine. That's okay. That's okay. Tiffany. Yeah. Speaking of burnout.