okay great okay so um yesterday so yesterday um after you left uh mark so Liam and I we kind of we made a list and Liam please feel free to jump in at any time so we made a list of these four items and um that we thought that uh perhaps the outreach sig could work on um as a way to help move the project forward right so the first item is under the educational outreach which you are very well aware of uh mark and so the goal here I think for the initial goal is just to um develop a written program and I put a link um of where I you know the inspiration came from and then the second item is um of course uh DevOps world so I wanted to um see if we can you know get volunteers to work with me on you know what is it that we want the community track to look like this year right um and and of course uh reviewers for the CFP um the third item is diversity in Jenkins community and Liam I'll let you talk about this one sure um basically there's uh the Jenkins the set of contributors there there are there's a wide range of people that contribute to Jenkins but by and large like at these um these meetups mostly what I see is white dudes and uh uh of of varying ages some of us getting more crusty over time um and it's that that saddens me and I'm like I don't I don't have an answer of how how to address this but it certainly is um one of those things where it's like how can we get what things can we do to invite in a broader range of people I mean I think to be fair to to be fair to where we are the the set of contributors to Jenkins in large part comes from the people that have worked with Jenkins which have tended to be people that get stuck in the server room which tends to be you know so um you know you get it's a self-selecting uh group for people that are that that have a vested interest right but um you know I'm using this tool so then I'm going to work on it and that's um so we get our pipeline of people tends to be you know our our pool tends to be from that same group but there's got to be ways that we can uh draw a wider audience there's nothing about this about Jenkins itself that or as far as I'm concerned the people really in the community that says we're not you know open and inviting and interested in having more people contribute in a wider range it's I guess there's some some other thing things that we should look at right um because I mean when I'm thinking about it's like I don't think that the I think there's some things the community itself could do to to be more uh friendly to new contributors and stuff like that but like that that there's a there's maybe something before the hey here's my first PR hey I'm interested in working on this of how do we get people a broader spectrum of people in that funnel right yeah so both of those things but I you know I like that so so it seems it seems well aligned with a topic we were discussing in some depth in the east version of the docs track earlier today um so Xenob Abu Bakar is our uh Google season of docs author that we had do the Kubernetes on or Jenkins on Kubernetes documentation Xenob is based out of Nigeria and is a leader in the Sheikot Africa initiative and Sheikot Africa has a program that they're launching there they launched it now asking for corporate sponsors and for open source projects that people can work on so that Sheikot Africa project runs for the month of April to invite funded developers funded women in Africa to assist with open source projects and so what we need is we need project ideas that we can bring to it and we need corporate sponsors so Alyssa and I have already approached our shared employer and have good traction on that I'm going to ping several other folks in different organizations for instance we've got Alex Earl with Broadcom we've got Jim Crowley with IBM we've got several interesting candidates that may be willing to support Sheikot Africa as a way to then get those people involved in the Jenkins community as part of a very specifically targeted activity so I think that's a great idea Oleg also noted that outreach and specific outreach is probably the most important thing we can do in terms of help of the project we need we have lots of ideas of things we can do what we lack our hands to do them and the way we get hands to do them is by exactly these outreach programs that you're noting yeah I like the diversity and the educational outreach and those kind of things yeah right yes so Mark for that program I think CDF might be able to be able to sponsor that program as well that's Sheikot okay yeah good idea yeah so as part of the so so what in the conversation we had in the docs is enough noted or in the docs track seen I've noted that Sheikot Africa is really as much about code as it is about documentation so documentation is just a peripheral thing or is just one of many ways to contribute they're they're willing to have their contributors assist with code assist with promotion assist with other activities so and and I like that the idea of proposing the CDF that they might also be a sponsor I thought Oleg had a good concept that having the Jenkins project be actually a financial sponsor of the Sheikot Africa project is probably not a not a sensible thing because one open source project is sponsoring another is not as effective as persuading corporations to sponsor open source projects I see so so and I think that's fair the the Jenkins projects funds should be used directly for the Jenkins project wherever possible okay that makes sense so I think like the so like the education outreach can also be under the diversity in Jenkins community and or growing SIG participation I think all that and then I also started looking into what other organizations are doing with regards to diversity right and I found that you know it starts out like say it starts out at home so it starts out on our homepage or Jenkins.io how are we communicating that we are accepting diversity that we welcome this right so are we doing that number one so that's why I put that first bullet and sorry when I wrote that down I didn't really go back to Jenkins.io to look but I thought maybe you know we should have that on there that explains that you know we are a supporter of diversity and and then as far as growing the SIG participation I put a link there and I look at which link that was uh was um yeah the outreachy internship supporting open source and such I forget why I looked at that but oh that was like oh um a paid internship right um I mean and it's and it's for my diverse especially so it supports diversity yeah and then the other thing is on somewhere on um along let me find the link to that page but there there was a page that explains you know how a first time contributor can contribute I mean it spells it all out I have to find that page but it's somewhere on my screen but I thought that was really helpful you know if if this is if this is what we want to do um might be good to have instructions on you know if you're a brand new first time you know welcome these are the steps that you can do this well and so certainly certainly we're getting we're getting if we if I look at diversity in the community if we look at google summer of code there's a there's a great example of a diverse a wide spectrum of contributors we got contributors from India there contributors from China contributors from Malaysia or Singapore I forget you know so so lots of lots of different people involved in those contributions Natasha Stopa from Pennsylvania was I think it was a year ago so so we've got a broad a broad swath of people contributing there and yeah I like that yeah and I think we just need to make sure to call out or highlight contributors we I think we should make an effort to do that at least maybe on a monthly quarterly basis but give them a place to shine and the spotlight you know that may perhaps that they can say hey I did this with you know maybe their future um um employer mm-hmm at my house what if what if we were to do something like that as part of the as part of the jumbotron for instance some sort of a rotating view of here here are four or five contributors when Cara presented her um google summer of code summary today she put up a very nice set of six or seven pictures of the google summer of code students and I find those pictures quite engaging should we consider something like that if we could find hey on the Jenkins authors page there are individuals there that we might say hey if they've got a picture in it let's highlight them and do it for some fixed period two weeks or a month and as part of the jumbotron and then rotate and highlight a different set yeah now the the problem with that is that only gets authors from that site and and that's a tiny fraction of the total contributors to Jenkins I don't know that spin it connectiony for instance in in uh in the Czech Republic has a picture on the on the site so may not or of Keiji Zhang who is who is definitely a contributor from google summer of code or even Xenob I'm not sure that Xenob's actually got a photo on there so so the idea may be good but the implementation may be completely unworkable because we just don't have the right data there yet I see but that is data that we can ask it is and and it's certainly data we can solicit right we can yeah we can ask them hey could you please um yeah could you please help us highlight contributors to Jenkins and and our selection can bias strongly towards people that we think will be interesting and and fun to see and interesting because they're diverse I admit it I think I'm interesting but I'm middle-aged white male I have to acknowledge that I mean I don't think we should I don't think we should you know avoid highlighting people but it's more just like I think there I think there are we highlight more so right and I think you've got it exactly this is not a downplaying of anyone this is rather an emphasizing that this is a broad and very diverse community and it is it's a fascinatingly diverse community so I think you're right so um so based on these four items mark uh I mean do these look okay that we we what is the next step I'm trying to figure out what's the next step yeah so so I think tomorrow in the in the roadmap presentation or in the yeah in the concluding session present these four as as I as plans to be on the roadmap and I think I would even put the review committee yeah put put all four of them up as part of that the slide deck for the final and I haven't even created the slide deck yet so we put them up for the slide deck and and then you talk to them and solicit input the intention is that tomorrow's closing session will be a working session so we're going to we're going to share these these ideas and then we invite further comments and then as we as we do that we may say okay we would like to put these things into the roadmap and and we think advocacy should be part of the Jenkins roadmap as well uh I don't know if it's actually got a place right now for for advocacy does it I'm now checking yeah because if it doesn't I think it's it's worth a discussion to say hey we think oh it does we've got events community events absolutely okay where is the roadmap anyways just it's jenkins.io slash project slash roadmap like this so let's look at it and here if I click just the subset that are outreach programs and community events and and those those both seem like great great places for us to put so we had community bridge as a mentorship potential and we've done one community bridge project so we know it can work but it would be good to do more and then Jenkins on Kubernetes online meetups we've we'd started those and yeah so we have the places how do you get to that roadmap from the top navigation I always go like this I go to any old page scroll to the bottom structure and governance and then here is the roadmap structure and governance yeah that I agree that it's not it may not be natural but then again I am not a website designer so me designing web page navigation is is is well beyond my depth we could certainly put it for instance here as part of community it's or yeah and I just I was just like people talk about talk about this a bunch of them like okay I just there's there's this is a cool page it's very visual and very right highlights all the things that are available and or at least a number of things that are available and this is totally worth putting up there right yeah well let's test this what if it were under about about has only five items what if we had roadmap and under there and I would even navigate have more than one way to get to it maybe okay so so the about definitely right and then community overview it could be I mean it could be here let's see sub-projects doesn't really obviously fit because this really is about sub-projects it's about major components and this is more the overall I mean it does it map to does it map to the SIGs or not it not it maps to more than just the SIGs right right there there certainly are SIG representation but we could for instance we could on every SIG page put a link to the roadmap for that SIG right saying hey look let's see the road section yeah exactly because that gives us a link to something live right okay trying to think of where community overview see somehow taking somewhere in the community section as well but I'm not really sure where okay you think well yeah and we could certainly put it it seems every bit as interesting as wiki yeah sorry wiki is no longer interesting right yeah I don't think there's any benefit to us having the wiki link because it's read only now so we replace could replace it with roadmap yeah sounds great okay so at least those two places and the third one being in the projects the not the projects the SIGs right uh so so oh in the projects yes see I hesitated to put it in sub-projects and I didn't see how well I can certainly submit poll requests for all three I'll submit them as three independent poll requests so that way we can have the discussions about them in the poll request because it's those are those are very reasonable places to consider should we add it to two of the three one of the three all three and I don't think I don't think it makes sense in documentation and certainly plugins is not not roadmap so but but by the way I have to show you this notice what comes up when we do this see this search by Algolia this is Gavin's prototype of real search really cool search indexing so that you didn't know that strategy and strategies are both the same word but Algolia knows okay so Alyssa back to your oh it's fine well mark how do we um add the these items onto the roadmap through is it through poll requests as well it it is so so I think what we do is tomorrow during the presentation present them as ideas and then get agreement that yes they are good roadmap entries and then after the conclusion of tomorrow's session you and I can pair together and work on submitting the poll request okay because I've got a number of other roadmap changes that I need to update where the documentation roadmap is needs to be updated and several others therefore it just be more efficient for you and me to do it together tomorrow or the next day okay that sounds good now I don't know if if devops world review committee will I'm I would expect that one may get some friction on hey why not a review committee for cd cd con or why not and they may say that shouldn't be on the roadmap but I'm cool with that I think the others are are very much roadmap topics right we okay we really do want them okay present all four and let's see what the what the voices say all right and then so so then once that they approve as items for the roadmap and then we take this to the outreach sick and then we work out the plan is that is that the plan right okay and then do we have to provide additional details on what we have currently have here on this document oh I'm sure I'm sure that it will be expected that we we have get a plan together on hey how are we going to do these things that we think are good ideas right and that's for tomorrow no no tomorrow we'll get a bunch of I think what Mark was saying was that tomorrow we'll get a bunch of feedback people say hey we could try this we can try that we'll get some brainstorming and some more information and opinions and thoughts with people and then synthesize those after the next steps after the summit okay got it yeah so the idea was let's bring these these concepts to the to the larger group tomorrow and then then listen for feedback there okay um I guess let's see here diversity arts and participation um I guess under the SIG participation is where I put the roadmap just if you want to just track this is it it's a matter of making things visible right so right participation make me in part is make the the roadmap which has all of those sort of projects and where they're at and how to find them and make that more visible on the GX that's that's the place right yeah and so the idea there was let's see let me be about section about here because only got five in it and then replacing wiki with community with roadmap because and then and then also in the SIGs or the subprojects uh the SIGs each of the SIGs does have right each I think the notion was each SIG page particularly advocacy and outreach documentation should link to the roadmap right we want to we want to create a web of links to the roadmap yeah I think if you click on one of those you'll we already have like sort of metadata in there that you can write we can you know provide a little a little a small little mass link so that it's not a huge imposition to get there right just a minute while I grab a picture of this to remind myself where we where we think it should go show it should really go there good all right so the idea was propose it under about under community and under subprojects links from individual SIG pages uh subprojects or SIGs either oh right sorry from individual from SIG so it's SIG pages link to roadmap yeah very good yeah we did it for a few SIGs initially but it it wasn't consistent yeah so this just we'll just make it consistent that way um that way it's brings it up a little higher good super hi Oleg yeah hi Oleg late for you yeah Oleg we didn't need to to drag you out this late in the day thank you very much for being here but you're that's sort of her heroism beyond the call you're doing okay yeah i'm still in the office oh my oh dear oh i'm gonna get scolded so severely oh my sake so oh the scoldings that will be epic for that great okay well that's okay oh that's fine yep so for me for SIG participation i just the current state reflects the state of overall contributions because yeah there are usual suspects and there are people who are not that connected to the wider community and in order to get these people who are participating in SIGs presenting and contributing if the rather requires continuous outreach and to do the outreach need basically people doing that right because yeah when we were pushing particular SIGs we're easily getting to 10 15 people on the call but yeah when it stops then it stops right well and for me there's there's an element of growing the SIGs by these these outreach programs uh GSOC google chicote africa community bridge or outreach you through community bridge but those tend more to be one at a time and cash needing cash right whereas i think all like what you're describing here is it's not only about cash it's also about temporary involvement and then that for example yeah last year we deliberately tied all projects to SIGs but it was difficult to get students and mentors participating in SIG meetings we were successful for some of them but not for all cases given though there was direct communication to all mentors that yeah it's expected this year and moreover well students come and go mentors come and go and the SIGs are rather both specific topics so for me it would be more important to actually attract company contributors to SIGs than to do outreach programs so outreach programs is a way to facilitate projects SIGs are interested in because SIGs could provide an umbrella so for example you are interested in platform support there is a group of interested contributors and we can run out a SIG program to get it done including funding etc but in order to get participants I would rather start from actually getting people and companies participating and if they are interested in what the SIG is doing in particular agenda then it could be the best way to actually get the SIG going so for example arm support we can definitely find a bunch of companies interested in that or let's say Jenks pipeline debugger if you announce this topic like this many people would join the pipeline out drink meeting okay yeah for company contributors you really need excuse me so what are you interested in people directly well and so so this is one Oleg are you envisioning for instance we've got Jim Crowley from IBM right now who's interested because of IBM's interest in doing work on it we've got we could potentially have AWS involved or Google in terms of their cloud as part of a platform kind of effort is is that the sort of thing that you're in you're thinking of there yeah for example for AWS and for Azure we had company representatives at the cloud native SIG for a while and we separate them but in principle we had people there good right I mean for instance we've got we've got Alex Earl who participates but he's really even though he's from Broadcom I don't think his participation is motivated primarily by Broadcom's business because I think here what you're thinking is let's let's try to combine a company's business interest with the needs of the Jenkins project and align those for progress so IBM would like 390 support and they're certainly ARM vendors that want ARM support yeah yeah so something like that so special interest groups are a way to facilitate particular efforts and the best way to do that is to ensure that participants have individual interest in the topics right good good good insight yeah so that's when I I certainly know of some companies that I can connect with that encourage them to to join up to the platform SIG and get involved yeah so this sounds to me similar to like what CDF does so they have the different committees or groups working groups right and then so companies send their employee or to become a member or participate in that working group so I think this is the same idea that Oleg is suggesting right Oleg does does CDF do active active recruiting because I I took Oleg's advice here that we should actively recruit and identify hey we think we've got something interesting going on in the Jenkins project relative to what you're doing we would love to have your your participation so from what I know I think it's the members the members of CDF they are the ones that's so they pay CDF to be a member and then they also send you know a representative from their company to be on one of those working groups I have I don't think I know of anyone that isn't a member and that's just you know volunteer their time and to be in those working groups unless they're they are like an ambassador or something like that but you may have highlighted something there what about the CDF member companies right they're already they are a good example of someone who's already invested in contributing to continuous delivery foundation maybe we should consider asking their representative hey we've got this initiative or go to the CDF meetings and say we've got these initiatives going on would love to have additional people come help us yeah we can definitely ask although I know it's it's it's quite challenging with those of us that's already sitting on those working groups plus our you know our you know nine to five your full day work so that might be a challenge well I wonder if this is something I should take up with with Tracy as to yeah hey what what are appropriate boundaries for us to invite CDF member companies to assist us or us invite the representatives to be more to increase their involvement yeah why not so any other topics that we should be sure we go over today Alyssa I think for me I'm good I think we've covered all that we needed okay and so I'll send you a link to a skeleton presentation that we can use for tomorrow's tomorrow's material I think most of the session should be focused on conversation but it's good to have these kind of concepts from each of the each of the tracks so that then we can get feedback and have discussions in that session okay um before we go uh I have a an off-topic question mark so feel free to um unrecord oh okay let me well look we'll call you ready let's stop the recording and


You know, every once in a while, I just sit and think, randomly, out of the blue, to myself, man, one piece is just so good. And then when you think that the series just can't get any better, a chapter like 1096 drops, is it even possible for something to make you feel so happy, relieved, excited and hyped, but also so scared, apprehensive and frustrated at the same time? Well yes, it most certainly is because the author of our favourite manga is the master of manipulating emotions. He's also the master of inflicting a severe case of blue balls, which is exactly what I woke up to this morning. When I woke up in the wee early hours of 6 or 7am, saw that the chapter was out, proceeded to read it, very excited to find out about the God Valley incident, get extremely hyped at seeing all those cool panels, all those big names, with all the hype and tension rising so much that I thought I was going into affixiation from all of my excitement, only for Oda to blue balls me, wrapping up the God Valley flashback as quickly as he started it. Now I am just being dramatic, it wasn't a complete tease, and once I got over my pent up emotions, I do have to say that this is the perfect way to lay some groundwork and keep us hungry for the full God Valley flashback to come, but then also keeping us equally satisfied for the time being. As we did get to see legendary characters, as well as new reveals, but the meaty juicy details about what really went down is something that we're just going to have to keep waiting for, which in retrospect, it shouldn't come as a surprise, because at the end of the day, this is Kuma's flashback after all, not Rocks or White Beards or Garps or Rogers. This is Kuma's story, and what a story that he has to tell, and we will get there, don't worry, but we do first have to talk about God Valley. So if chapter 1095 explained where and what God Valley was, 1096 explained what everyone was doing there, and basically everyone had their own agendas. God Valley was just this massive melting pot of different factions, different groups, all congregating on this one island to carry out their own, but at times conflicting missions. And I think this is important because this is likely a scenario that we will soon see again, whether it's at Egghead or Elbaf or the next island. We are going to witness history repeat itself, a legendary event of all different factions, Yonko pirate crews, revolutionaries, world nobles, and even the God Knights, all congregating as each group is trying to carry out their respective objectives, getting in each other's ways, erupting into conflict and unlikely alliances, all of this culminating in a legendary event that will change the tide of history forever. But until we witness that unfold, let's take stock of what we now know about the mysterious God Valley incident. Adding onto the reveals from the last chapter that God Valley was the island that was unluckily chosen to be the host slash victim of the cruel hunting tournament, where world nobles compete in hunting civilians and slaves to win this grand prize, chapter 1096 continues to disturb us as we now also know more details, like the hunted were called rabbits, which further dehumanizes these poor individuals whose only crime was to be born poor, and the terrorized faces of the hunted, while the holy knights and the celestial dragons are drawn to look abhorrently excited. I don't have quite the words to describe my feelings, but it's just sickening. We also find out certain rules, like the fact that there are rare rabbits and super rare rabbits that are worth more points, 10,000 to be exact. And I'm assuming that one's rareness has to do with what type of species or race a person was. So for example, I can imagine Kuma having been the last of the Buccaneers as well as his great strength making him a rarer target because of the fact that his race is near extinct, as well as him being more difficult to kill probably. But it was quite intriguing to see the beef amongst the world noble families, as those in the tournament were taking the competition seriously, determined to not let Garling win this time. And it's this sort of micro-politics that makes the characters and the world feel so interesting and real. Garling was unsurprisingly already in the lead, assumedly having disposed of the super rare rabbit, and it's an interesting animal that he's riding. Sort of like an evil spot-billed duck, like an evil Karu, which would make sense not only because we know them to be very fast creatures, which should come in handy for this sort of sport, but also very intriguing now that we know Arrabasta was originally a part of the 20 kingdoms that would go on to become the world government. And given that super spot-billed ducks originate from Arrabasta, maybe an offshoot of the species have been under the control of the world government ever since the Void Century. When they were used by other clans during the Great War to oppose the ancient kingdom, the species going on to develop into a related species, sort of how animals in the real world migrate and develop into slightly different species in their different environments through time. But my bad, overthinking things. While Garling is no doubt despicable, I have to admit that it's hard to dislike him, just because of how cool he always looks. Oda had no business making me feel so drawn to this character this way. The way that he assembles the holy knights to take care of the impending threat of fierce and pirate crews, showing no fear and only confidence. I know that he's a reprehensible character, so why does he always look so damn good? It seems like we also might have gotten a glimpse at other Gods knights in this panel, because the feminine figure beside Garling sort of looks like she's dressed in a similar uniform, meaning that she's also a knight, or that she's a Garling groupie. And similarly, there's a figure also behind them, also dressed similarly, and I swear it took me the longest time to figure out that that's a bovine head on top of him. So putting all of that together. And the Gods knights seem to be actually a very eclectic bunch. Say what you will about the very backwards, very racist celestial dragons. But the Gods knights might have actually been a bit more progressive what with women and other species in their ranks. But of course, the most exciting group that we have to discuss about this chapter is the legendary rocks crew.  Whitebeard just looks so badass, definitely caught my attention first. And the detail of Buckin on his back emphasizes not only his stature, but all those freaking giants in the rocks crew. I mean, not literal giants like the species, but it's actually also possible that they did in fact have a real giant in their crew. Now seeing Buckin should come as no surprise, because we did find out that Stussy the Clone was the clone of Buckin, Whitebeard's supposed lover, and her riding Whitebeard quite literally does seem to at least support the claims that she and Whitebeard were lovers. But we also get to see Big Mom in her prime looking like a snack, might I add, who's curiously very eager to go after finding the devil fruits, which strikes me considering she already has one. And so she can't eat another one for herself. I mean, has she just been collecting devil fruits since 40 years ago? And another question I've always wondered about is, when did she find out about her devil fruit powers? Slash, what does she actually think about having those powers because she got it by eating Mother Carmel, which she doesn't know about. Anyways, there's young feisty Kaido who seems to want to go after rocks himself, which is crazy. Like, I know you're Kaido and all, but chill out grasshopper, it's not your time yet. We also see Captain John, whose design is very compelling, has this charismatic aura, maybe just because of how chill he is. Shiki, as fired up as ever, offended that Whitebeard is taking charge, and the big surprise of Granny Neon or Gloriosa of the Kuja tribe. Plus we know that these two are likely to be Wang Zi and Silver Zaks. Now noticeably, there's no appearance of rocks himself, but even that says quite a bit. It seems like rocks has rushed off by himself, losing sight of their main objective, which is a very typical Declan trait. We've seen this with Roger, very excited to fight the monster Odin, and of course, Luffy does this time and time again. But even without rocks being there in this panel.  From the sheer number of legendary names, seeing them together, their size, their presence, this is what you call a pirate crew. Even aside from their appearance, I loved their interactions. Their dialogues really sold on what type of a crew this is. The banter and the quipping really shows that they're not your average buddy buddy crew. The theory that they've all banded together, or at least Whitebeard joined them as a result of a Davy back fight, seems more and more likely, especially Whitebeard refusing to acknowledge rocks as his captain. And each of them has their own agenda, rather than working together as a cohesive team. But I have to say, isn't just me, or did you also feel that there is a slight hint of, at least an endearing affection for each other. The crew just intrigues me to no end, because on top of the hype that this page elicits, there's also a good amount of lore and mystery as well. Firstly, we see a few familiar figures from the Thriller Bark arc. We always knew that Captain John would somehow be acquired by Moria. But it seems like Moria also got his hand on a number of the other Fallen Rocks Pirates members, at least three of them, which really raises the question of how. Did all of these legendary pirates die during the God Valley incident? Did Kaido carry around his Fallen comrades eventually burying them when he settled down at Wano, and when Moria went to challenge Kaido, that's when he also found all of these members? Seems a bit unlikely and surprising to think of Kaido as being that sentimental, bringing them around and taking them with him to Wano, given what we know of the relationship between the crew members. So did Moria also hear of this legendary war at God Valley, and realize that this is going to be the perfect graveyard for him to recruit his new zombie crew? And if they did all die here, does this mean that John had already buried his treasure before the events of God Valley? The other mystery being about Gloriosa. Because although we know her as Graninon now, Gloriosa back then would have probably been also called the most beautiful woman in the world, much like her granddaughter. Or at least a very strong contender, because Linlin also does make a pretty good case. But now that we know that she was a part of Roxas' crew, while her daughter would go on to be Rayleigh's lover, who is of course in an opposing crew, Rayleigh literally got with the daughter of his enemy.  Seriously though, I wonder whether Gloriosa was inflicted with the love sickness during her time in this crew, maybe even with someone in this crew. I mean can you imagine if she fell in love with Roxas? The biggest mystery of all though, is what is the crown jewel of Hachinosu that they've lost and now seek to recover at God Valley. Because that seems to be the overwhelming agenda of the Rox crew. The world government somehow stole a prized possession and they're here to get it back, which somewhat makes it less likely that Rox is actually the hero of God Valley, who is here to kill all the celestial dragons in the name of good to stop the hunting games, which is what it sort of seemed like the story might be going after introducing us to the horrors of the tournament last chapter, but this chapter recontextualizes Rox and his motivations yet again. So what is it that is so important that is termed the crown jewel and that the world government would take such a big risk of trespassing onto Hachinosu, agitating the strongest crew in history by stealing their treasure. The most obvious answer would be a devil fruit, because that seemed to be the prizes being handed out for winning this tournament, but it does seem a bit too obvious. Too easy. If it is a devil fruit, it would at least have to be Luffy's devil fruit and definitely not the Nikunjikunomi or the Seiryu devil fruit that were featured in this chapter. Other possibilities might be an ancient weapon or a roadponer glyph. Maybe it's even the roadponer glyph that Big Mum has in her possession now, which might make more sense because this could have been what sparked Roger's interest in the poner glyphs or roadponer glyphs after encountering it for the first time during his clash with Rocks. And we do know that Rocks was condemned for studying the world's taboos and collecting the banned poner glyphs definitely seems to fit that sort of description. Another cool idea is that the Rocks pirates originally had the mystical giant egg that the Roger pirates would later be seen with, especially if that egg is somehow tied to an ancient weapon. As always with one piece, there are just so many possibilities. So please make sure to let me know what you think the crown jewels are by leaving a comment below. It's even possible that whatever the crown jewel is, the Rocks pirates actually stole it from Roger's crew because it's clear that there was some sort of pre-existing rivalry between these two crews at least for a year and this has been bugging Roger for the past year. Kaido seems to be agitated at the mention of Roger and Bakun is also keen to settle things, maybe settling once and for all who is the better crew. Which is actually crazy and as hyped as the Rocks crew is, I think it says even more about the Roger pirates. I mean do I have to remind you of who is in that Rocks crew? Whereas aside from Roger Rayleigh and Gabon, we haven't really seen the other members of the Roger pirates being hyped up to such great deals to make them seem like much of a threat. So for the Roger pirates to be considered worthy rivals for the Rocks pirates, it's just mind-blowing in my opinion. But the MVP that we really have to thank for gathering this wild bunch of pirates together is Ginny because apparently it's all thanks to her leaking the world government's presence at God Valley and about the games that alerted all the pirates to come this way in the first place. And so then of course adding to the chaos is motherfucking Garb. I love everything about Garb's portrayal in this chapter. He has obviously never changed and please never do change. His utter disrespect for the world government and even his superiors choosing when and where he'll mobilize according to his own interests and the complete 180 when he realizes that Roger will be there which is ultimately what motivated him to make his appearance at God Valley. Which is really funny because it means that Garb was relatively uninterested in Rocks and his fearsome crew, filled to the brim with big name pirates in their own rights. But one mention of Roger and he is roaring to go. Seriously the man is obsessed. It's the first thing that Garb says when he arrives. And it's even funnier and not the least bit ironic that Garb actually ended up with Allying with Roger instead. But you guys know how much I love Garb's character and so I just loved his entrance. So hype, his pose, the crowds cheering and then the cherry on top has to be the legendary Bogard on his side. From the panel of the Rocks Pirates to the arrival of Garb, that has to be one of the best series of panels ever. I was screaming, jumping, crying, throwing up. No I'm just kidding but seriously.  But of course the rest of this legendary tale will have to be told on another day because this is where Oda leaves us hanging. So moving on to Kuma who to be fair has his own legendary story to tell. And so I'm not complaining at all this chapter.  And apparently they use psychological warfare too giving false hope to the targets by lying to them that they'll let them live if they managed to survive the hunt just because the sick world nobles enjoy the extra challenge because where's the fun in hunting targets that aren't even trying? And I do mean targets by the way because they each literally have targets on their clothes. And something I didn't notice at first is that Kuma has already been shot because there's an arrow tail on his back which just makes my heart break even more. But Ivankov as always is there to keep the mood and the hopes up and it's wonderful to see him being the revolutionary that he was clearly born to be. Whether it's his oratory skills to a crowd or the way that he convinces Kuma to act. Showing his own unbreakable spirit that even in the face of tragedy and despair Ivankov sees the value in taking what some might call a small step as just saving only one soul but he sees it not as just necessary but as a triumph. I know I mentioned it last week but man I just fall more in love with him by the second. My favorite has to be that short exchange with the fishman where the fishman's never been complimented about his fish features before because that's such a small detail that says so much about who Ivankov is. Ivankov is an individual that has the power in helping people accept who they really are. And it's such a beautiful but equally devastating moment when you think about the additional layers of slavery and racial discrimination and just ah. Ginny is surprisingly the brains behind the group which was really refreshing because I didn't expect her to play such a crucial role or in this sort of way at least. But to see her as this sort of mastermind right down to the design with her glasses and her transponder snail network it definitely added more depth to her character. And then the trifector is perfected by the sweet and pure hearted Kuma who has to be the definition of too kind for this world. It was so heartbreaking but also so wholesome to see him volunteer as decoy not wanting to see any more people die after losing the ones most closest to him. And so it's so fitting that Kuma emerged as the hero of god valley or at least the people's hero of god valley. But backing up we did get a glimpse of a crazy alternate world where Ivankov could have ended up with Kaido's devil fruit. And while I do think that he ended up with the most fitting fruit for his personality, I can't get this image out of my mind. In any case we see the origin story of how Kuma ended up with the poor porno me and how big mum ultimately obtained the seiryu devil fruit which he saw her give to Kaido during Kaido's flashback. But just as we feel safe, the confrontation between Kuma and Satan begins which we know is where this backstory will culminate. Satan seems to confirm that the reason the Bokkaniers were wiped out is because of their beliefs in Nicar and this part makes me super intrigued about the way in which Kuma was able to join the warlords. Since the Gorose would be aware of its members, I wonder how they allowed a Bokkanier to not only live and survive but be a part of their ranks. It's most likely that there was some sort of agreement in place between Kuma and the world government. Perhaps Kuma knew something that's going to be a threat to them or more likely this is linked to Kuma's agreement to be part of vagabunks experimentation to develop the pacifistas. But either way, after some emotional dialogue from Kuma that shows his pure heart once again, this is where the God Valley flashback ends. And while I was at the time exasperated, I am actually fine with this level of closure or should I say lack of closure because we still do have a very engaging story to follow. A story that continues back at Sorbet Kingdom when news reports of the God Valley incident doesn't tell us any more information about what really went down apart from the fact that Morgans is a media mogul who has been around for decades. Meaning that the number of characters who might know of rocks and the truth of the God Valley incident may be a lot more than we realized. But this is probably the last of the God Valley flashback that we'll see for some time or at least while we're witnessing Kuma's backstory. The chapter continues to draw on Kuma's biblical or religious theme, seen praying at church for all the souls that he couldn't save and what did I say about him being too pure for this world. Because in fact he did manage to save over 500 people, prompting Ivankov to comment that Kuma has the hands of liberation, which is just such a fitting name and also so fitting for Ivankov to have been the person to give him this name. Making me feel for this duo so much more, so much so that I did actually feel a pang of sadness when Ivankov decided to leave and to journey the seas because I didn't want them to separate. But of course the real sadness is when Kuma says that he would never forget Ivankov's face and then this scene just hits so much harder. Ginny decides to stay back at Kuma, no doubt to go on to create Bonnie. I mean, can Oda get any more obvious than Kuma literally calling Ginny a glutton? But seriously, the two were very cute together and it was very wholesome and it made my heart swell watching their humble but happy lives at Sorbet Kingdom. A good level of little details and callbacks in this section too. Such as the fact that the two boys that bullied Kuma seems to be a part of Bonnie's crew in the present. My head canon is that these two became Kuma and Ginny's gang after Kuma took their pain away with his devil fruit and so later they swore that they would take care of Bonnie. But the thing that impacts me the most is seeing the genuine smile on Kuma's face when he sees that he's able to free people from pain. Oda even drew him as if he's shining, like a saint, a saviour, living up to his ambition of saving people just like the stories he's heard of Nika, making his whole religious theme so apt and deep on a new level. And the chapter ends on that very heartbreaking but simultaneously heartwarming note, showing more wholesome scenes between Kuma and Ginny, the duo in tears of happiness at experiencing freedom and such contentment for the first time in forever. And this level of wholesome feels does mean that I now expect more tragedy, maybe much more tragedy in Kuma's story to come. Again, my guess is that it's somehow going to involve the loss of Ginny, maybe the world government even takes her away. And that's why Kuma makes some sort of agreement with them. I mean we still have to find out why he's called a tyrant, rather than the saviour that he's being depicted to be here. And again, I can feel just so much more sadness coming our way. But for now, I just want to bask in this warm happy glow that we're feeling. Honestly, this was just such a fantastic chapter that kept on giving. It was super super long, even after we saw a little chapter 1096 logo. The chapter continued for a few more pages that I really wasn't expecting. And even though it was a lot more set up than giving us resolutions as such, I don't feel like I was just left wanting. After experiencing the continued horror at the games, the hype at all the legendary fighters, Oda completes our emotional roller coaster so that by the end I just feel so content and so warm and fuzzy inside. And nothing warms my heart more than knowing the fact that there is no break next week. And if that fact makes you happy as well, then make sure to subscribe to this channel. Also, let me know what you thought about 1096 by leaving a comment below. Again, please subscribe, please like the video, and thank you to all of our channel and Patreon members for your support. This is Joygirl, and I'll see you again soon.