Delighted that you're here for this initial organizing meeting for Google season of dogs. I'm Mark wait We're joined by Oleg Nanashov Kristen Whetstone Roman Rodriguez Gil and I Apologize I don't know how to pronounce your name. Could you announce yourself? Slayton well, let's proceed What we'd like to do here is our goal is with this first meeting is to review where we're at and Do our best to prepare to submit our application on time for the 23rd of April deadline for the for the Google season of dogs proposal so My proposal is let's review the agenda and ask everyone in the in the meeting to As I review the agenda and note things that you believe should be added to the agenda We'll add them to the agenda and then we'll actually work through the agenda We will end this meeting on time in about 40 minutes So that we don't spend an inordinate amount of your time But I like to work from the agenda as our driving driving plan So I'll spend some time discussing upcoming events I've got a brief status report to talk about some some details and things Then the bulk of the meeting I think is on Application status review where Oleg will can lead us through a discussion and I'll capture action items If we have time I'd like to review project ideas and possibly assign Potential mentors to those project ideas then in the last few minutes of the meeting I'll summarize the action items and We'll plan for the next meeting and I would propose that we'll plan when the next meeting will be and then conclude this meeting Are there other topics you would like to have on the agenda? Well, we could do some introductions if the time allows, but we don't have everybody on the call today So maybe we could do it next time That's that's a good that's a good proposal. Let's let's include that introductions Who we are? Any other agenda addition? I think no, I Would wish we could get to application status review as soon as possible because we've had only a few days left I Would rather start the discussion. Are you suggesting we have to put this one at the top of the list Oleg? Well, it would be nice, but yeah, it's totally up to you and we can do it either way Let's let's do that. Let's put that Let's put that right here at the top and That way we're aware that also gives us an introduction to many of the things that that would have been in the status group report It gives us a more natural a natural place to do it. Let's talk about the real application good All right, so applications the application is due April 23rd And I propose that as a matter of that we follow the similar pattern as google summer of code has been doing Where they tend to post jinkins.io blog posts to give broader more global status reports Yeah, I like that So then Oleg, why don't you take us through application status review and I'll take notes Okay Sorry mark. Um, what about the jinkins x if we're doing two proposals or I one for jinkins and ones for jinkins x So do we need to maybe put something that? That we're going to do the same equivalent for jinkins x Actually the intent was to do a single google season of docs for the entire Where and then jinkins and jinkins x would be two two two components of it Did I get a correct Oleg Well, jinkins is a project jinkins x formally now is a sub project a Inside jinkins organization now So until cdf transition is finished jinkins x is eligible to participate in Google season of docs or google summer of code is a part of jinkins organization Once the transition is done Well, it will be a topic for discussion But right now it's perfectly fine to have jinkins x project ideas But yeah in order to have jinkins x project somebody has to propose jinkins x project And so So that's why I said john is working on jinkins x documentation In the community and for cloud bees and so The plan was that he would lead some jinkins x projects if with within this google summer code Um to try to spark more community interest in writing for jinkins x So that was Probably be sure to talk about About how community work happens and how gsoc and gsoc happened Because right now we cannot really say will about any of the project ideas So if you want, I can show you it on example of for google season Summer of code because yeah, we have everything in process But yeah, we have pretty much the same process for gsoc So how it happens? Each organization Pots a number of project ideas For example, here's a list of project ideas created for jsoc Um, which organization is expected to have this list of project ideas Then potential technical writers will be reviewing these project ideas reaching out to the community and at some point applying to the projects And only after applications when there is a processing of applications That there is a decision made to which projects will be accepted So it means that uh, yeah, we can have one Project for jinkins one project for jinkins x, but ultimately it's too early to talk about it We first we need to get our projects We need to get applications and yeah, if we get Multiplications, then we somehow decide which applications we accept as an organization Okay, no, that that makes sense. I just I Tracee, I didn't realize that um, it's all under one Project and then jinkins x would be like a subcomponent of jinkins. I just misunderstood Yeah, it's a potential topic to discuss because um We have six days till the deadline for application. So for example, if you want to have Um, we could have separate applications for jinkins and jinkins x Uh, it's all possible and in such case we can have up to four projects if both organizations get accepted It would be all right. Yeah, that's what I don't yeah, I don't know if trace is available But yeah, I mean I just I I'm finding their way. I'm just trying to make sure I understand You know what we're proposing because when I talked to tracy a couple days ago It sounded like she she said that an organization can propose up to two projects In a couple days ago She said that we were going to do a jinkins project and jinkins x project Proposal since each word can propose up to two so Well, I'm not aware about any of these discussions. So yeah, there might be some internal discussions But in the million years there is no discussion about that Uh, so speaking of the community side Yeah, currently we do an application and an application what we say it's mentoring capacity So in our application we say how many technical writers does your organization want to mentor this year one or two So we have only two shows So we cannot say that we want to mentor two projects But yeah, then there will be still project ideas. So there will be a number of project ideas now we have maybe five And potential technical writers they will go through will be going through the list of project ideas Selecting ones which are interesting to them reaching out to the community and the client so yeah We would be interested to have jinkins x projects for sure Same as jinkins, but it would really depend on applications Uh, if we apply as a single organization jinkins Yeah, it would be Will really depend on the applications if you apply as two organizations like jinkins organization and jink sex organization Then again, if just we may have up to four projects if both get accepted And secondly each projects would have independent resource schools Um, so yeah most ways are possible and it's something uh What can we discuss now? Because now we do only one application for jinkins project But if somebody wants to do a separate application for jinkins x it's something we could do Okay Yeah, okay, so No, that's fine. I think it works either way. I mean, I'm not super hung up on whether we divide into one or two projects I just want to make sure that um You know that there's some jinkins x Topics on here because I think it's a great way to get people to write For it and and john is already going just it's already contributing to it anyway And you know if we could build some a minimum around there, um, I would love to Okay, so if you want to have uh a project for jinkins x we need to have jinkins x project idea here by Uh, well, it would be pretty short there. So it wouldn't be april 2030. It can be done a bit later But still the first step to have a jinkins x project would be to have a jinkins x project idea Okay, yeah, that's what tracy was saying she so she said that she was going to send me um The proposal and show me where to like put in the ideas. Is that this document that you're showing right now? Yes, it is. Okay. If you could send me the um, you can just send me the link to this. I'm happy to to add in You know john and uh in petr's name and then we will we will sit down today and um add some suggestions. Thank you Appreciate it. Yeah, I put most documents to the chart so You can take remember from here. So yeah, um Um Probably we could uh return them back to the application process. Yeah, we discussed some hits right now um, but Yeah, there are some open questions. It's not only about project ideas So project ideas would be discussed with temin. We need project ideas in this list and it would be a nice step Uh Of course, so if anybody has any project in mind Propose a change in this document. Everybody should be able to propose a change. So you just go to this document Click suggest change and write your own project idea here, for example Let's say it's something drinking sex whatever No, yeah, we will we will do that. Um, we'll find some time to do that. Thank you Yeah, so it would be the first step And yeah, maybe it's a question to you and also mark and uh tracing So if there is an interest to have more than two projects Maybe applying as jenkin sex and jenkin sex independently would be a good step for that Sure. Yeah, I'll put yeah, I'll put the urgent next proposal in that section. You just added and then um um You know petra Would love to be a mentor as well. So if there are any um potential jenkins Proposed topics that we can add or as a potential mentor. That's fine or we can come up with some additional ones. Um Whatever whatever, you know, how many project ideas do we need to have here? Well We need to have several project ideas So even with the current list we well more or less fine It's always nice to have more project ideas. So for example in google summer of code this year. We have 27 project ideas But in j sort we can have less but yeah having More project ideas is still if it's still helpful because it will give more choice For potential uh technical writers and if you propose diverse project ideas So different technology stacks different areas then there are higher chances that you will get more applications Okay, so great. We'll sit down today and add some things To this list with petra and john as potential mentors. Um, and then yeah, you guys can Can let us know what you think Yeah, perfect. Okay, awesome. Thank you. Okay. Thank you So, yeah, this is one part of the application. We really need project ideas But it's not the only part of the application What else we need to do by april 23rd? So you may see that there is another document called g-sort application So actually this is a google forum, which has been originally created By me on the first day of the g-sort applications. So just to have a state in the ground You may see that there is some text there and yeah, I will appreciate if you guys take a look at the text Maybe propose some changes I The form is not that big. Well, it's much smaller compared to g-sort But yeah, it still includes some beats and one of the beats which we need to discuss is Link to your organization page about season of dogs So this is a part which is still missing kind of which I wanted to discuss today because well the jsoc for example jsoc has a landed page on Jenkins io website So there is Jenkins io projects jsoc and it's a kind of lending for all information about jsoc including student documentation mentor documentation project documentation Project pages project ideas, etc. So everything is located In Jenkins io Other programs for example outreach it. They don't have landing pages on Jenkins io. Maybe they should but right now they don't What is the question here in this application that we Actually, I expected to provide a landing page So my question now would be to participants of this meeting. How do we do that? Well, the best way you look at something content is io But maybe there are other proposals how to implement that Actually, I I'd prefer I propose the action item mark weight takes the responsibility to create a pull request to jenkins.io To create something smaller than but similar to google summer of code because the the model feels like it works well for us I think that's simple direct and gives us a public place to put it Yeah, one of the problems which we Have from this jsoc so jsoc was created three years ago before we had special interest groups So here you may see that jsoc is the actually listed as a sub project In jenkins so on the same level like the jenkins x remoting configuration as code Which is probably okay But now since we have community pages Maybe it might make sense to for example do it Under umbrella of advocacy and outreach or maybe we could have a just a documentation sub project and have jsoc as a sub project within Documentation sub project. So with something What needs to be I'm not sure what would be the best way And is a pull request and an acceptable way to test drive that do we need it Given that we're only six days away from application I'm prone to use pull requests rather than the full jenkins enhancement project process the jet process No, the jet process isn't something we need to do there for sure So yeah for me the most straightforward way was Or maybe documentation special interest group But yeah, I'm not sure what they It's the right approach because yeah, I would not expect each sub project and each Special interest group to be responsible for its own documentation So right and to me it almost feels like this would Since they're so similar it kind of overlaps a little bit with the google summer of code group Yeah, right? Yeah, so it's like it would make it be a little bit harder to have a whole other group for A program very similar to google summer code Yeah, so Yeah, there are multiple ways one way is to just have an entry here Uh, well, it's the most straightforward way Okay, so I'm I'm great with doing that. I was Assuming it would go under special interest group. It's your recommending actually be treated as a sub project It's big enough with enough things. It feels justifiable as a sub project. I'll do that So you yeah here you wrote uh documentation sick Me So yeah, this is The second big Open question we have for the application the rest of the So everything is in place I'm not sure why So primary administrator So we have a primary administrator displaying and full name Um, one thing which wasn't clear to me is about this open source project description So it's probably a topic to discuss in the Jsot slug channel because Yeah For me, it's not clear what is The size of the description we should provide when you apply to Jsot You get the information about Content side is you need to provide here. It's just a free file So you can provide a war and peace there or you can just provide Sentences like I have here. Oh, actually only one sentence So maybe it's something which we need to discuss to understand what we really need to provide there So this this description is read by candidates who are considering whether or not they would like to submit an application to us To be part of google season of docs as technical writers, right? Well, I would assume so but since it's the first year of google season of docs So we really have no idea what will be the website what will be the Project system so it seems that they decided not to Copy the entire jsoc structure in jsot So yeah, I'm not sure how will the final jsot website Look like So yeah, that's why for me. It's not clear what we should provide here So I I'm proud to leave it exactly as you created it. I like that description I think that's a unless there's strong opinion. Otherwise That's feels good enough to me Oops Sorry I shouldn't have to share that Okay Yeah, so I just wanted to show examples and then this to that. I'm actually locked in So I'll probably cut some bits of the video later Okay, so yeah Maybe we can just ask and slack later or keep it as is. I believe that if something goes wrong, we can always ask jsot Support to update the website If you want to make more information But yeah, this one I feel like we should be a little bit more descriptive, right? It's supposed to be a compelling reason to accept us I'm assuming to describe our project. So I think that's a great start, but um, I'm happy for someone on my team to help maybe add a few more sentences to it to Really Jenkins itself Yeah, right. I can show you how it looks for jsoc now because jsoc is already running So Here you can go to organizations. So there is a number of organizations something like 200 organizations. Uh, this time We can just look for Jenkins We have Jenkins project Is there a character limit it seems like these are pretty short. I'm wondering if we're we're trying to fit into a certain limitation Yeah, uh Jsoc there is definitely a limit Uh, so for jsoc you provide the dating markdown format with uh, uh text size limit So you can estimate what would be the target content So now the key is the description we have on the jsoc side But uh, I'm not sure where you can do the same for google season of dogs because we just submit google form So it's not markdown I would assume And we also don't know the target size of french Right. Yeah Yeah, happy to help If you want get the information Some of my team can help you with that if you want it once you get the character limit Mm-hmm Yeah, right. Oh, yeah, whatever proposals say he will be helpful Yeah Yeah, oh, yeah, what happens next for us So, yeah, we will be just editing this application So if anybody wants to propose changes, we just do that and in april 22nd I plan to just uh, copy all the fields and Google form because I started the google form And they cannot transfer transfer it to mark. So I will be submitting the final proposal Yeah, and I really prefer to do it on sunday not on monday Okay, so you want us to get our stuff in by the end of this work week, right? So if we have it in by end of day friday We're good Yeah, it would be My preference so i'm Friday But yeah on sunday We could think up because yeah on monday. I cannot guarantee my availability Yeah No, that's fine. We'll put our stuff in there by the end of day friday Oh mark, uh, is it fine with you? Yes Okay, well then yeah, we can just agree that uh, yeah on sunday our target that on sunday april 22nd, we have everything Of 21st. Yeah, 21st. We have everything in place Um, I submitted and if there are some last minute changes we still can apply them But we target having a final application Uh on sunday, okay So that's it from me If there is no questions, we can just press it to other agenda items Okay, were there oh like one of the things that was noted in by sliden in the uh In the gitter channel was the more detail needed on mentors Is there something in the application that we need with regard to mentors? No, so what we need uh mentors So mentors expected uh to click Sorry to pass the their constant form or whatever form So all mentors and that means they have to pass Who would have a Google form If you open the g sort Website you can find the guidelines And all mentors expected to pass This form, but I believe that there is no strict deadline format Or means have to pass them by the application deadline. So both you and Tracy should complete it by Monday Great, and I've already completed the alternative organization administrator I'm not sure how to complete the organization administrator because I think they have it attached to who submits the form all right And that's why we have slack channel because it's a first year of good season of dogs So yeah, the process isn't established yet Okay, and if something doesn't work, we have a mainland list and we have a slack channel I believe that uh, it would be the best way to clarify any kind of question Well, and so their request was their request on the slack channel is mark Could you submit the the uh the application instead of having oleg submitted? They were I think trying to take the easy way out In terms of of not having to Go through some special push-ups to make me organization admin Yeah, I'm not sure Okay, so let's proceed then with the assumption now that you'll submit the application on the 22nd And if we've learned something in the slack channel that says no that won't work We'll do it differently then we'll find a way to Meet their their request. Yeah, right okay, so Any other things with regard to application status review oleg? Nothing for me Okay, so let's take up the status report just briefly then We would like to switch to use zoom for future meetings One is that the with in the context of the continuous delivery foundation There's active effort to do that. The other is it will help many of our colleagues in china Get easier access So that's the plan will follow the same pattern in the future of Sharing a link to the location in the Gitter channel Please consider Gitter is our primary communications channel And we will use blog posts to jenkins io for future broad communications And so on the Gitter channel we understand the jenkins ci docs, right? Correct. Yes. Thanks. I should have embedded that link absolutely Yeah, and I think that it also makes sense to reference that amazing piece because yeah, what we do in Uh Full of summer of code we at least say that we try to do as much communications as possible in the mailing list Because mailing list is a synchronous communication channel And unfortunately Gitter is not a good channel for synchronous communications. It doesn't support threads, etc So we are approaching that we do try to do mailing list for all kinds of long conversations and Gitter for short synopsis So that is it is it better to declare it that we'll use lasting conversations in in the mailing list and Interactive communications in the in the Gitter channel Oh, it would be my suggestion. I like that. Let's let's take that as a yes unless we get strong objection from someone Um, can someone share this doc with me? I can't seem to find it Oh, sure. It's it's in the you'll find a link to it in the channel in the Gitter channel And we'll also happily We'll paste the link to it every so often in the Gitter channel just so people are aware also put it into the mailing list Okay, so I wanted to take a few minutes here to be sure that we've we've got a Current list of who's doing what in the in the effort So I'm taking on organization administrator responsibility Tammy specifically I'm choosing to do only one One product one organization here not two that will limit us to two projects So goal would be have one of those be Jenkins and the other one Jenkins X But I'm not ready to sign up to be organization administrator for two two different projects yet I'm worried that that would be more than I can do Okay Yeah, I mean happy happy to To help if we want to take this offline mark and you and I can discuss Happy to figure out how you know my team can help with that since I know that You get kind of time limits here Great. Thanks. Tracy Miranda has agreed to be the alternative organization administrator She's not available to attend right now But she's very much committed to then mentors. I've listed the mentors of which I'm aware so petra Kristen Joe Arnav and jam ha Others if I made a mistake here, you're welcome to delete yourself by a proposal Or to put yourself in if if you would like to be a mentor You do need to register with Google Each of those registered words is a hyperlink to a form. You just need to submit that form Any questions on roles responsibilities and people The one the one gap here is technical writers. We don't have that. They'll submit after we create the proposal Go ahead. Right So I'm trying to understand the break up You said that we're so I Are we submitting one or two? You said you're going to be org admin For the Jenkins thing, but you're not prepared to be it for more than one So we're submitting one or two applications. I'm still lost My picture was one application which will have up to two will have many project ideas And the way google's described it is they'll accept up to two. I think what's that I this what I've understood oleg and those two Technical writers will submit their their applications to it And if the applications are accepted then we mentor them as they do the work on those two projects So in that other document, we have all these project ideas. We propose those And then up to two writers will pick From the whole list Is that what happens mark? That's I I'm not sure that it's up to two writers is that applicants so technical writers. Yeah, so technical writers propose apply to the project and if we accept them They should they then work on that project idea and we assign mentors to assist for that project idea Oleg did I describe it correctly? Yeah, you did right Okay, so the project ideas that we list in the application That they're they're not going to all be done, right? And like we don't have control over which ones get picked Correct. So they just pick from that list and then if And then so I'm trying to understand like so we have these project ideas And I see on some of my potential mentor I see, you know you mark for some of them and then we'll obviously propose some things in the application but then really the mentors that are going to work on this are dependent on what the writers that decide to work on this project select And maybe yeah, and maybe well Oh, yeah, I could clarify that We can't really influence which projects get selected by potential technical writers But they submit applications to our organization and then we have ultimate power the projects we want Uh, but yeah, there is no magic So for example, if you have janking sex and if nobody submits an application to janking sex You won't be able to pick this project But if somebody accepts then you will have And we will be making it as an organization So yeah, that's how it happens. We cannot say for sure Uh, which number of applications we will get what quality of these applications we will have So yeah, it's yet to be seen But yeah, if we are lucky we can have projects and we will ultimately have a final say which project applications we take Okay, no, I understood just trying to understand how it how it works appreciate the explanation Yeah, right so there is a long document about the google seasonal docs where they tried to Explain all this selection process Okay, it's mostly taken from jso if some variations Sure Okay, yeah mark if you if you need an admin or whatever or admin for for a sub part then please let me know i'm happy to to help with that Thank you. Thanks very much Sure No, thanks for letting us be part of this. I'm excited. I think this is um, this is gonna be really great Yeah, right so if we decided to go with two parallel project I am able to be alternated for Alternative organization admin in the Jenkins project Okay, I'm fine with not being Or admin because jsoc is pretty much enough for me but Casey wants to focus on Jenkins x I can probably fill this slot if needed Great. Thank you. Thanks. Oh like Yeah So I'm yeah great In terms of in terms of other details here We've got we need additional project ideas So and that I assume we're going to assemble project ideas I gather more project ideas this week. So Before end of this week into that document into the doc and then April 22 we submit and it then comes back the Technical writers can then review those proposals and submit their applications So I think I've captured the action items in the google doc already There were two That we listed there Oleg to submit the final application sunday the 22nd and me to submit a poll request to jankins idaho.io for google summer of doc I think we should put one more which is add jankins x project ideas and let's put that on john if that's okay Yeah, that's fine. All right and John let's see if I've got your email address here. I don't so it's jha at cloud piece. Is that correct john? right All right Okay, great Got it. So that one's assigned in the doc. I would like to have Our next meeting. Well now the question is is April 22 That's a sunday, isn't it and that's not a terribly workable day for a next meeting So should we rather consider another meeting one week from now to talk about where we are? I will be traveling on april 24th, but yeah not really required at this meeting. I believe Yeah, and oh like can you my apologies. I don't know the details on the timelines after the april 23 application deadline when will google make their decisions on on Project ideas or what is the next major milestone after that? Okay, so yeah, that's why we have links somewhere in this document Just a second. I'll find it Useful links Yes, so there should be timeline here Yeah timeline So we have April 23rd in its deadline for applications then April 29th is A review time so on April 30th Publishes the list of organizations And then Yeah, then they will be One month of discussions So applications you may see that everything really starts in June Great, so it feels like to me a good status would be the week of april 23 We get together to double check that we've satisfied all the things that google needs before they publish the list of mentoring organizations So I will send out a doodle a doodle request to Sound for something the week of april 23 And start an agenda for that Okay, great Any other topics that we need to discuss here today? I don't think so All right. Thanks everybody. Let's go ahead and conclude this meeting. Thanks very much We'll start the agenda for the next meeting and the google the doodle to request to find a good time for everyone Thanks very much for being part of it Thanks, mark. All right. Thank you Bye Thanks


الله سبحانه وتعالى يحبنا كثيراً الله سبحانه وتعالى يحبنا كثيراً أريد أن أشهر معكم حديث that captures a conversation that took place between الله سبحانه وتعالى and Prophet Dawood عليه الصلاة أسمع لأي ماذا الله أقول to Dawood الله تظمي يا Dawood لو يعلم المدبرون عني كيف انتظاري لهم ورفقي بهم وشوقي إلى تركي معاصيهم الله أكبر الله سبحانه وتعالى تزد Dawood Dawood إذا كانت الناس who have turned away from me who have forgotten that they have a Lord إذا كانت تعرف كيف أصبحت for them to come back to me الله سبحانه وتعالى is saying this to Dawood لما تشوقاً إليه وتقطعت أوصالهم من محبتي إذا كانوا تعلم كيف أصبحت for them to come back to me to have a good relationship with me they would die out of their longing and their happiness if they only knew الله سبحانه وتعالى loves his servants this is the first point over here that we remember that الله سبحانه وتعالى cares about us the second point some people ask the question but how can I really feel practically that God loves me I know theoretically he created me I'm his servant okay he cares about me he loves me but I want to feel that practically in my life how do I feel the love of الله سبحانه وتعالى in my life I'll share with you four quick tips on how to feel and experience the love of God in your life number one whenever you're wondering does God love you how do I know he really loves me ask yourself this question how much do you love Allah how much time do you spend with your Lord at night when everyone is asleep you have some private time do you talk to Allah سبحانه وتعالى you want to feel the love of God talk to him every day pour your heart out to Allah سبحانه وتعالى make Allah your best friend I guarantee you will feel that warmth in your heart that's the first tip the second tip lies in the obedience of God you want to feel the love of Allah obey the commands of God Allah will reveal the warmth of his love in your heart and believe me when you know that you've obeyed Allah سبحانه وتعالى at night you sleep with peace of mind even if you're going through anxiety depression other problems but when you know that you serve the path of Allah you're doing that which satisfies Allah سبحانه وتعالى that in itself brings ease to your heart the third tip is to educate yourself with knowledge understand the depths of the Quran تجد مدينة مدينة مدينة ومدينة مدينة the more you increase in knowledge the more you will feel the love of Allah سبحانه وتعالى this is a guarantee and that's why we have Imam Ali ibn Abi Talib in a beautiful hadith he talks about loneliness the Imam says the best company to help you with loneliness is knowledge there will come a time if you train yourself to love knowledge where nothing will satisfy your heart your mind your soul and your life more than knowledge the more you seek knowledge the more you feel you're fulfilled the more you feel the love of Allah سبحانه وتعالى and number four the fourth tip here my dear brothers and sisters is to help those in need you want to feel the love of Allah سبحانه وتعالى go and help someone who's in need give charity in the way of Allah سبحانه وتعالى spend from your time volunteer volunteering has been proven through scientific studies that it helps with depression and anxiety it helps with loneliness people who regularly volunteer at a community center at a mosque at a charitable organization their mental state is much better their mental health is much better go and give from your time try it my dear brothers and sisters help out someone who's poor someone who's in need someone who's psychologically struggling and you go and you give them some relief that night you will feel better you will feel the love of Allah سبحانه وتعالى when Allah sees you on His path of obedience He will bring down that love in your heart and you will really experience the love of Allah سبحانه وتعالى


We're in this interesting time where we don't gravitate to the possible. We don't dream as much. People have to keep that flame burning. That's what XPRIZE does. We set very audacious but achievable goals. We leverage them with a million or ten million dollars and then we go to the world and say, I don't care who you are, where you've gone to school, what you've done before, the first person to make that happen wins. You help bring about a breakthrough and we all win. XPRIZE is about fundamentally enabling something to happen where most people said it could not be done. Harnessing the power of imagination to see a positive future and accelerate that future so that it can happen right now. We're revitalizing and re-energizing the incentive prize competition which is 300 years old. The Longitude Prize out of the British Admiralty created global navigation. Early aviation prizes of the last century were extraordinary in creating today's 300 billion dollar aviation industry. When we did the Ansari XPRIZE, our vision was opening up the space frontier. We were really happy to see the success of the Ansari XPRIZE and we felt that we owe it to ourselves and to society to take this learning and apply it and see if it can also work in other areas that humanity faces challenges. From the success of that prize, we expanded into other areas. Energy in the environment, life sciences, exploration, which is oceans and deep space, education and global development. The reason we actually have picked India as the global expansion of XPRIZE platform is India is a unique development country and we're very confident to see what we create there and then we actually take that model to South America, take the model to Asia, to Africa. XPRIZE could help make a new India. It really could change things for a nation of a billion people. XPRIZE is an India could transform whole aspects of India for the better. So it's tremendous that XPRIZE is going there. If you look at almost any country, the top 5 or 10 percent are just absolutely brilliant. India happens to have 1.4 billion population. So just a lot more brilliant people. So what XPRIZE India would do is really bring that fortune to every single person in India to be able to solve the biggest problems. And I believe that XPRIZE India has that chance to bring those dreams, ambition and to make them young. This is the right time for XPRIZE to come in and to really ignite entrepreneurship across India to solve some of her grandest challenges.


Live from Mountain View, California, it's The Cube at OpenStack Silicon Valley, brought to you by headline sponsor, Mirantis. Here are your hosts, John Furrier and Jeff Frick. Okay, welcome back and we are here live in Silicon Valley for the OpenStack SB event, OpenStack Silicon Valley. I'm John Furrier, the founder of Silicon Angle. I'm Joe, my co-host Jeff Frick, general manager at Cube Silicon Valley operation. Our next guest is Gary Chen, research manager of cloud and virtualization, system software at IDC, international data corp research firm. Welcome to The Cube. Yeah, thank you guys for having me on. Great to have you on. I'd love to get the analysts on perspective because you want to get, you got, you track it, you're tracking this market. So, you know, we were talking prior on our intro, what's the TAM on this thing? We don't know. I mean, is it cloud, green field, OpenStack sales or is it data center disruption? So it's kind of not clear.  Software, we had Mesosphere on earlier, classic collision to the data center, or is it cloud and another TAM? I mean, make sense of it for us. Do you have any insight there?  So a lot of, you know, the existing stuff, you know, hey, you know, we'll put it and make it a part of the cloud because the cloud still needs networks and storage. You know, some of it may be slightly different in a cloud, but then there are like new markets that are created. So, you know, the kind of stuff I look at cloud system software, a lot of what OpenStack and that, I mean, that doesn't really have like a clear category to put it in. So, but the way it's sold makes it, may make it difficult to extract, you know, this is a market and this is a TAM, right? Because a lot of people are like, well, we're selling this, you know, bundle of stuff, which is, you know, maybe it was a bundle of virtualization, then we had some cloud stuff or someone has like an operating system and, you know, they add OpenStack as, you know, basically a package that you install on an operating system. So, yeah, I mean, I think- And there's new approaches, you mentioned that as a service, it's interesting, right? So it's not clear, is it? Yeah, yeah, it's not clear at all.  We have some, you know, tixonomies and we're trying to, you know, gather, you know, information on revenue, decide how to split it up and do a forecast.  And it's tough to know where to put it yet. It's a new creature, if you will, in terms of categorical definitions, not like a nice little tight package yet. Exactly. Okay, so that being said, the Software Defined Data Center, we were at VMworld this year and clearly Docker stole the show, containerization. We heard, again, Mason's here talking about scaling at scale, the containers, the app developers are in charge. So the impact to that on the data center guys, you got networking compute storage. What are those guys going to do? How are they responding to this disruption in this converged infrastructure, which is going to end up becoming some sort of commodity. I mean, Amazon is driving to cost a zero while innovating. So they're adding more features and lowering their price. That is certainly a direct target at the storage compute network guys. What's your take on that? What's your commentary here? Yeah, I mean, I think a lot of what's happening there is people want to make that more of a kind of a more malleable resource, right? So those things are still essential, but I think how that's being consumed is totally changing, right? So if you're managing those things in enterprise now, I think today someone probably comes up to you and says, I need this storage, I need this server or something like that. I think a lot of that's going to change. It seems to be going through all of these portals and things out in self-service, different layers of how you can service a customer. So I think those guys will be charged with running, that's basically this infrastructure as a service and they're going to keep that running. And they'll probably fairly insulated from what the actual end user is buying. And so there'll be layers of paths and web portals and things like that kind of between them. So it does become more widespread and more available, but it also does become more abstracted. And so I think for the market, a lot of the value is going to be in a software layer that's above that. You know, I got to ask you, obviously the breaking news this morning, we've been reporting on SiliconANGLE as Docker gets a series C for 40 million. I heard about that.  They already got, they're in their series C round. I mean, that is the ultimate hype machine in action. Right now they have great traction, so product market fit seems to be there. Okay, how does that overlay into this market? Funding is an issue because a lot of the companies here in the OpenStack community are about three years old. They're either going to tank out or get another round or some sort of consolidation. How do you view that expansionary funding versus the consolidation? Yeah, so I think right now in OpenStack, I mean, everybody is doing a distro of OpenStack, right? The market can't possibly support all those things. Even OpenStack is this runaway success, which very likely could be, but there's certainly going to be a lot of consolidation there. And I think the thing is it's really hard to differentiate an OpenStack right now, at least kind of on the software distro side. And so a lot of it may really just come out to, if you can just dig out, if you can manage to find some kind of niche, some small market. So if you get some customers there, or you build some expertise there, or it may just be for people, little pieces of technology, I think that one thing that is good for, a lot of these distributions is that the scope of OpenStack is expanding. So there's a lot and a lot more modules. And I think it really starts to let people specialize. In the beginning where it was just kind of a core set of modules and everyone's OpenStack included these and it wasn't much to do, but if you really want to focus on Paz, maybe that's where you focus on, or Trove at databases, a service if databases are specialty or you have install base there. So I do think we will see more differentiation, but I think the consolidation is going to come. But when that's going to happen, it's hard to say because I mean, in some sense the OpenStack market hasn't even really has just started, right? So it's not like there's lots of customers out there. So the consolidation still could be, we still may be in that expansion phase. Not a lot of net new customers. I mean, there might be a little bit of new business, but it's the disruption piece really that you're watching, right? That's kind of what you're saying? Yeah. I mean, I think for right now it's people are looking at OpenStack as an interesting new technology. It's probably not quite there yet in terms of mainstream adoption. So I think we'll probably, right now we're seeing, I think more startups around OpenStack form at this point. So it still seems to be expanding, but yeah, those disorders will have to collapse at some point. So Gary, let's shift gears a little bit. You had a panel earlier today, I believe. Yes. So talk a little bit about what happened on your panel that you had on some of the interesting insights that came out of... Yeah, so the panel was called, it's open source, winner take all game, right? So we had Martin Mikos from Eucalyptus. We had Steve Wilson who was from Citrix representing CloudStack, and then Boris Rensky from Morantis who represented OpenStack. So the whole point was kind of just to discuss, is there kind of supposed to be just one winner, right? At least on the open source side. All these platforms battle it out and then there's one left and that's kind of the open source option and then you compete against all the other proprietary like Amazon and all these other guys. And so, I mean, I don't know if there were any really solid conclusions that came out of it. I think any time you get those few guys together it's kind of really competitive which it was and it was really fun. But I think in the past, the lines seem to be more clear. I think when Linux, like the other big open source project was coming up, people spun it as kind of open source versus proprietary. A lot of it was like, can open source work? This is model work. Today, yeah, I mean, I think we know that it does. And then it was also kind of like, there were clear villains, right? It was Windows. And to a lesser extent, it was Unix. At least that's kind of how the market and press and media kind of spun it as. And I think today it's, yeah, there still is some of that open versus proprietary, but there's a lot of blurring between some of these things, right? So you have Amazon, but they don't sell software, right? They're only a service. And so that's different. And then you have these platforms that compete at a lot of levels, but like Citrix has a lot of assets that it makes work with OpenStack, with Zen Server and NetScaler and all these things. So they're heavily involved and they're contributing code. And so it's probably not just this versus that. And I think most of the participants were still pretty adamant that their platform was still out there and still running the race. But I think it has become, I think, a little bit more collaboration. Before it was, I think, much more like us versus them. But I think Citrix is really focused on desktop and app virtualization. They'll try and make that run on any infrastructure, whether it's CloudStack or not. And of course, Eucalyptus got bought by HP. So there's certainly going to be some kind of eucalyptus, OpenStack kind of love, exactly how that's looked no one really knows. But yeah, so even Martin put on an OpenStack shirt during the thing, so he was wearing a T-shirt that Boris gave him. So that might have been a sign that something's changing that he actually put that on. But at the end of the day, it's about market traction with customers and market traction with the developers. So I mean, are there any kind of early indicators that you see or you're tracking to know potentially who's kind of gaining momentum and maybe separating themselves from the fact a little bit? Yeah, I mean, I think when you look at production deployments today, it's so small and it's really kind of the cutting edge of users. So it's hard to kind of make assumptions from that. The way I kind of look at it is kind of right now, I think the best kind of measure of where it's going is kind of developer momentum. So I mean, there's a finite number of developers out there, right? So you want them to work on your project, right? So, because that means something when it filters downstream into these commercial products. So the more developers you have means the faster you can innovate, right? The better quality yourself. We've got more people to test it and things like that. So I think when you look at developer momentum, that I think that's a good indication of the project. Because I think if you look at, people do feature comparisons today of where things are. And that's pretty interesting if you have to deploy right now, but not everyone has to deploy right now. So I think long term for open source projects, you really look at the community of where that momentum is, and kind of any shortcomings eventually get solved once you kind of build that momentum and you get those resources, you can overcome all those things and that can happen very quickly. You can catch up and you can build out your stuff. So I think right now the developer momentum is kind of the interesting thing to see where the industry is putting its developers. And most of it is coming from vendors, right? Vendors support open source, so they have to strategically kind of allocate where they want to go. So the open stack is definitely in the lead there. Gary, we've got a minute left. I'm going to get your take on the HP eucalyptus deal. Obviously you said you're on a panel with Martin. We've known him for years. Great guy. Open source guy. So it's Martin Fink. So what do you think that's going to do? Is that a yard sale? Was it strategic?  What's your take on the deal, pros, cons? Yeah, so I mean, I think there's a lot we don't know, but what I would suspect is one, it was partly a talent acquisition, right? So Martin is really well known. That team has experienced an open source. It doesn't mean that they have an experience with open stack, but just with open source models in general, right? So HP is really serious. It needs more people that really understand open source, how to foster that. So that was probably part of that. The other part is the Amazon thing, right? So eucalyptus was really the only vendor that had kind of this API license, right? So, but it's not clear like, if HP is going to inherit that or not, right? So... Or embrace it even if they inherit it. Yeah, it's kind of unknown, right? Yeah, or even if they want that. That could be a potential asset that could be valuable. I asked them a direct question. How do you keep up with that moving train called Amazon? I mean, Amazon's adding new features at a clip. We're seeing amazing traction and the pace of new stuff there, features.  Yeah, they're adding a lot of things, and I think Amazon isn't really clear like what they consider their APIs really something that are going to vigorously defend. They seem to be letting people use it now and not really caring, but so kind of how they react and what HP's kind of plans are, if they really want to... Well, any chance he's not a new to the business, he's a strategic thinker and they have a mission. So I think that'll be a pretty easy decision for them to help their mission or hurt their mission. That's going to be the strategic question. How do they play the competitive strategy game on that? Yeah, yeah. I mean, I think the big thing for HP now is like they basically have two platforms that do the same thing, right? They have competing platforms. So they have to figure out what they're going to do. Are they going to try to sell both of them and kind of spin one as this one is for this and this is for this? Or do they kill one off? I don't think merging is possible. I just don't think you can take a product and this product and all of a sudden magically make it merge. It may sound like it's... It may sound easy to say that, oh, we're going to merge things. Well, you've got internal five terms within HP, but the issue is you can't be half pregnant as the expression goes, right? So HP's got that issue. The other thing that's interesting I want to get your thoughts on along those lines is as a portfolio, HP has a pretty big portfolio within the cloud itself. It's pretty diverse and different. Tim Cook was on Charlie Rose's Friday, he talked about Apple, how they simplified and he said I could lay all my products out on this desk right here and that's our ex billions of dollars a quarter in revenue. Okay, so basically they would simplify their products. Is that even possible for an HP? I mean, and is that something that they should do? I mean, I think they should. So even if you look at just cloud platforms, I mean, right now, I know of at least three they're juggling, right? They had the older cloud matrix platform. Now they moved to OpenStack and now they've acquired eucalyptus, right? So, yeah, I mean, I think, and those things kind of is at the end of the day, they do kind of the same thing, right? So I think it's very confusing for customers, and you try and make it really specific to that or that. It just gets really, really complicated. So yeah, I think it's easy to say that yes, they should simplify, but they just have this massive, I mean, they're a massive company. They got these customers that are probably about long-term contracts into things like that. So yeah, I think it's really, really hard to do that, but I do think they should progress and simplify. Well, the first thing that Martin said he would do is talk about the people issue, go look at the people, get to know the organizations, and that includes the sales force, right? You got to know who's touching the customer, right? And then the product market fit from there. Gary, we got to get the hook here. We got to go. Thanks for coming on. Thank you for taking me at the analyst perspective. Gary Chen from IDC breaking it down here, covers system software. That's the operating system of the future. That is the cloud, hybrid and public. Now this is theCUBE. We're sharing all this data with you. We'll be right back after this short break.