Good afternoon, everyone, and welcome to the Stockswish Show Play of the Day. This is JCP. This has actually been the play of the day for three days in a row. So interesting that I would do the same stock this many days in a row, but it's a nice thing about continuation moves and gaps. They absolutely, without a shadow of a doubt, can happen, and seeing this happen more and more and more lately. Let's take a look at it here. Actually, when this broke this morning, I saw it, and I thought, hmm. And I was a little surprised that it broke so fast out of the gate today, but the fact is it did. It closed yesterday at 7.61. So this really didn't gap today, but it broke fast, and I already had been breaking all since back here. This was from Friday, and I just knew this was going to break soon anyway, so I was looking for it to do it. It did get to the target today of $7. Okay. Now, the thing is that when this breaks this area, again, I have no idea when that's going to be. It's not going to be today, though. It's too late today, and I'm out of all of this thing now. But it could have. It could have broke through $7 today, actually, and if it had, it would have fallen off a cliff. I mean, the dream target on this today was $6.30, $6.20, $6, and there's a very high likelihood this still gets there. I just don't know when. I really think this has to wait now after today's sell-off to do something significant to get back in and reshort it. But then again, I've seen stocks continue for three to five days in a row. I really can't count this here. One, two, three, four. I mean, this could go a whole more day. I'm actually going to ... This is actually a watch for tomorrow. Yeah. This is actually a watch for tomorrow. First of all, this is a swing trade that you could still be in until it gets to $6. And I guess it can be a watch for tomorrow, yeah, because this bar here really doesn't count. So it's one, two, three, four. So this could go five days down. Yeah. And it bounced and did a beautiful move into the lunchtime period, so let's just go back. Let's fix this here. Again, no volume here. Here's where the volume comes in.  This is almost 400,000 shares. It happens in 60 seconds. That's a big, big, fat bar for the stock. And even though it's only 20 cents, it's a lot of volume coming into quickly to something that really, again, wasn't gapping. It was a neutral open. And so the stock rallied up. And you could have aggressively done this here, but there really wouldn't have been any reason to do that. You wait for the setup. I waited properly for the rally and had a beautiful, beautiful, beautiful entry here. And I actually didn't play this tight. I could have played this tighter. I was giving me a little bit more room, 50 by 58, just because of the fact that I wanted to make sure to give it the full-on resistance. And also, this is not a new gap, all right? So I wanted to give it a little, tiny room. It didn't even need it. I mean, you could have actually done this 50 by 55. You could have done it 50 by 55. So beautiful trade had the nice rally back up and then came down in here. This is the first move then in the morning, okay? So you get out of a little bit of it here. And then I just knew it was going to $7 today. Let it rally back. Never even touched the stop. I said, you could have lowered the stop, but I didn't. I actually just wanted to make sure to stay with the trade. It was so convinced and had 100% conviction it was going to 7. And I wanted to see it was going to break 7. However, when it came down in here, the time of the day when this happened in here and the way that this looks, I exited the whole thing. It was the right thing to do at an exact reversal time. And it's just the configuration here. I figured if it was going to go and break 7, it would rally back up and do it again. And I was watching the market the whole time that this was going on as well too. So nice follow through play in JCP. This is a reason to join the Stock Swish Live Trading Room for the year. If you are a Golden Gap course student and know that you want to be trading in the room for the whole year, you can be in the room for the year with a discount. With 25% off, what is the annual price? And also you can get the wealth manifestation course for free with the annual room membership, which is only $1,800. So, I mean, you could have made more than $1,800 on this trade here today in just one trade in JCP. And in the last three days, it really starts out up here what you made on the stock. I mean, this is really actually starting to add up here in the stock, you know? So, it could have one more day in it. I mean, it really, really could have one more day in it. But what a beautiful call that I knew this would break on through and just playing it. Playing it, seeing the numbers, seeing the numbers, seeing the resistance, seeing the breaks, seeing the target, seeing everything so clearly in this stock. It is very weak. And a beautiful trade in JCP once again today. And so follow this through.  If you really are into a stock and you're getting paid on it regularly, you can kind of get into the moons of the stock and play it and follow it with any of the things, JCP, ARO, AEO, SYMC, any of the ones. You can watch them and follow them and make money every time they break. It's a great understanding for the people that are doing that, that are training with me where they understand the gaps and they understand how they're moving and they continue when they follow through, because you really can do them.  And JCP has provided some beautiful entries. So this is Melissa with thestockswish.com. Again, the next golden gap class is April 26 and 27. And if you are a class, a student or ready or going to become a class student for April, you are welcome to sign up for the live trading room for the whole year with a 25% discount. And again, you get the wealth manifestation class for free with the room membership for the year, which is a really, really nice bonus. Email me at Melissa at thestockswish.com. If you'd like more information on upcoming classes or the room membership, have a fantastic day, everybody, and have a terrific, terrific holiday week. Thanks.


Good morning, good evening, good afternoon. Apologies for missing last week's excitement and the week before, but somebody's got to be on vacation, so I was gonna be me. I was up in the wilds of the Canadian Rockies with all the smoke, but it was a lot of fun. I want to take a moment and just congratulate the new TSC and give my thanks to Greg and Ram for their service for the past two and a half years. Jonathan actually. And Jonathan, yes, sorry, yes, and thank them for their efforts because it's been great this far. And so congratulations to the newest members. On our agenda this morning, we have our usual event reminders. We've got the TSC chair selection process that Todd will go over. We have community health working group discussion and then we have our Debbie of Updates composer, I think, is Simon on? Yeah, hey, Chris. Hello. All right, thanks Simon. And cello. Do we have who's doing that? Aua or? We have a new maintainer, Luke Chen from where we will do the report. Awesome. Great. Thank you. And then we have no working group updates this week, but next week we have architecture working group. And we also have the hyperledger explorer update the following week. So, and then just I don't know, Tracy, when are we gonna get closure on the copyright stuff? I know that it's tough with everybody traveling. We've got a legal committee call scheduled for next week, September 5th, I believe. So that went out to all the premier member legal counsel, which is how that's. And did you get a response from Jerry? I honestly did not yet. Okay, I'll post Peter. I think he's on holiday. But that is scheduled, so it's moving forward. Yep. Okay, super duper. All right, any other items for the agenda? Hearing none, let's move on. So, Todd, take away. All right, super quick on the event stuff. Hackfest October 3rd and 4th Montreal, please get registered for that. I'm just gonna pull up registration quickly. But going on from there, looking at Q1 of next year, please let us know your availability and the doodle poll. We want to get that scheduled well in advance. Oh, so going back to Montreal, quick heads up, we already have 86 registered for that. So that's extremely healthy for about a month out. Anyone else, please get your name in there ASAP. And then the last piece on the event front is Hyperledgic Global Forum. Yesterday morning, the full schedule and keynotes were announced for that. So two days focused on business and technical tracks, as well as a wide set of keynotes, and then two days after that, more on the workshops and labs front. So please take a look at the schedule there and get registered if you're planning to head to that. It's gonna be a great event for the entire ecosystem. Any questions on those three events? All right, so quick heads up on the next part. As Chris said, the new TSC was formally elected as of Wednesday night last week. So now the 11 TSC members are voting on the chair for the next 12 months. Chris Ferris and Dan Middleton were the two nominees for that. So that election for chair will conclude on Wednesday of next week. So we'll get that announced out with the agenda and just congratulate the winner from that on Thursday. And with that, I think it brings it over to Ry, Ry Tracy, on the community health discussion. Sure. Thanks. We have we, Tracy, David Boswell, and I had been discussing how to gauge community health. And we fortuitously circulated this community health working group charter right for the very robust discussion about diversity in our working groups and hyperledger overall. We had a few comments from Dan Milden, Hart Montgomery and Mark Wagner. And we are looking for more commentary. What we want to do is to be able to measure the health with, you know, objective, objective metrics that the community agrees on and present reports moving forward on the health of of our projects and our working groups. And we would like to bring this to the TSC for the vote for formation next week. So I would really appreciate, you know, any questions or commentary. And anyone has any questions? Or Tracy, do you have anything further to add? Yeah, I mean, definitely, you know, if there's any thoughts that you have in kind of the next week, if you can review the document charter that we put out there for the community health working group, we would highly appreciate that so that we can update it in time for the hopeful vote next week. Now, I would view something like this almost as somehow morphing some of this into a checklist for deciding if something's ready to be a project, right? We would have a set of guidelines that we're looking for for health of a working group or a project. And then as we're deciding if we accept something down the road, you know, we could say, well, they're going to be able to meet these things, right? Is that part of what you're thinking with us? I mean, I think when we really put it together, we were only thinking about the project that exists in the umbrella. I'm sorry, the greenhouse today. You know, obviously, I think there's a lot of things that we could do and looking at community health that that is, you know, something that we think it might be useful for, then we can definitely put a, you know, as we figure out what those things are that we want to look at, we can think about how that would impact incoming projects as well, or even maybe these working group proposals, right? Cool, thanks. Yeah. This is a VIPIN. I have a couple of questions. One is there's already a framework around reporting the health of the projects and working groups to the TSC. So will this be yet another way to report on the health? And what about the health of the community health working group? Who is going to police the policers? So, you know, this proliferation of, I mean, it is a good thing to have a community health working group. They should be assisting others in constituting not only the working group, but also to spread the word about the working group. That would be a good thing. But to have another group that is just responsible for measuring other groups, that doesn't seem like a useful exercise. So how I read this proposal is looking at investigating what's working and what's not working and what kind of patterns might not be in there explicitly. But what kind of patterns can we identify in projects that have healthier communities that we can help encourage in projects that might not have reached that same level of success? That's definitely a good way of saying that, Dan, right? I think, you know, we can learn from one another, right? That's part of why hyperledger exists and why a number of different projects exist is to be able to share best practices and those sorts of things. And so I think you're hitting the nail right on the head, Dan, where we were at. Some things are going to be healthier, right? And it may not be the same thing, right? So different projects may be healthier in different areas and the projects can learn from one another. So, yeah, definitely something worth thinking about. But isn't, so, and again, I apologize because I missed the conversation previously. We haven't had that. Isn't this what we do with the quarter of reports is within this sort of strongly hinting at where we already have identified a set of things that we'd like people to come back and report on, such as maintainer diversity, although, again, diversity is different facets of diversity, obviously. Contributors and so forth, as well as content, you know, so all those things, I think we had robust discussion and debate in the TSC previously about what should go into the quarterly reports. And I think that the quarterly reports themselves have been an effective means of stimulating conversation amongst the TSC and with the members of the various projects on, you know, providing up with suggestions on how they can improve and so forth. Isn't that so I guess my point is I don't disagree that this kind of a dialogue isn't useful. I'm struggling a little bit with and how is that different than what we're doing with the quarterly reports and maybe then applying a little bit more formal methods to identifying things like how many contributors, diversity, you know, maintainers, all that stuff and just maintaining some sort of a dashboard. Again, I don't want to say that we shouldn't have this conversation. I'm hoping that that's, in fact, the point of the quarterly updates is to continue to see what's going on with the projects and for those that are struggling a little bit to have the wisdom of this team and others, you know, shared with those teams to help them improve. Chris, I think one way to think of this would be one step more meta than that. It's, you know, what are the kinds, it isn't intended to replace or duplicate the quarterly reports. I think intended to be a place to say to have a discussion in a more, you know, out of band from the technical steering committee kind of way of what should those health reports say, you know, what are the useful things to try to measure and if there are some deeper issues with a particular project, perhaps a place where that project or even, you know, conceptually there can be conversations about what does health mean in the context of hyperledger and the community here. And I think, you know, you'll also see more metrics work being done going down the road and this can, you know, which I think might result in software sitting in labs or maybe even a full-fledged project proposal at some point. But this can be a place where conversations about what are useful metrics to try to track and conversations like they had about the diversity topic, for example. It can be a home for that and a place to kind of focus those conversations into some sort of tangible output, you know, like we do with other working groups and we can always talk about architecture and identity and performance at the TSC call but having separate working groups for that allows a degree of focus and bundling, not to silo it off but to just give it a proper home and that's something to check in on a regular basis. So I hear too... I hear too... Do you see this as a metrics group or as a best practices group? Exactly. You know, I don't know that those two need to be separate from each other, I think. And I'm not suggesting that they have to be separate from one another but I hear two themes in the descriptions that you have. One is sort of the metrics and how do we measure and the other that I heard from Dan and Tracy earlier was well maybe what we should be doing is figure out the best ways to build community as well. Well, there is another dimension. There is a different dimension which is whether it's only defining the metrics or it's actually applying those metrics to measure and produce results like measurements on how the different projects are doing against those metrics which is the police angle that was referred to before. So I want to make sure that Vipin gets a chance because he was trying to chime in the same time that Vipin did. Yeah, I mean I think Mick said what I wanted to say which is that there is this double sort of aim. One is, so is the group going to be much more of helping people? Or is it going to be more like saying, oh, you're not doing the right things we're going to tell you that this is the right way to do stuff. And if that is the way that the whole group is going to be formed and going that direction, then I have serious objections to it because already the working groups are working hard to create content and to create value.  So we come to the TSC with a full disclosure of the metrics. So now if you want to add more metrics then have it in the quarterly report. If the aim is to help people to increase diversity, to increase like Dan said, then I'm all for it. Yeah. So I want to echo what Mick and Vipin and Arnaud were saying because I think it's fine if we have a whole consistent way of measuring things like the number of contributors, the diversity of the contributorship, the number of maintainers, the diversity of the maintainers, again all the different facets. How many commits, how many releases, all those things that we can and I'm okay with having a group to sort of maybe harden a little bit about what we already have in our quarterly reports in that regard because the report already basically asks the various project teams to report those things. Now maybe that could be refined a little bit and maybe there can be a focus on the developing tooling and so forth that allows us to be a little bit more formal about that and maybe even create some sort of a dashboard that the TSC and others could use. I'm also fine with having discussions about how do we as a community improve our ability of outreach and acting new contributors, new people to our various projects and helping and maybe even articulating some best practices that can be shared with the various teams. What I'm really very uncomfortable with is the middle bullet of the work products which is quarterly reports on the status of all the working groups and projects because we're already doing that and I think to Vippen's point now we have sort of the checkers of the it's like I thought that was our job here in the TSC is to review those reports and provide immediate and sort of pointed and helpful hopefully constructive feedback and now we have a working group that's going to be reporting on what they think the health is. I don't like that at all. Again I'm fine with the discussion about how do we improve the reporting, how do we do a more rigorous approach for counting things and what are the ways that we can increase diversity that we can increase our contributors and so forth all for that as a separate discussion. I think we need to go back to the first statement in the introduction of the charter which is an assertion basically a question I think rightfully. It says the health and viability of projects and working groups is not well understood. Maybe I'm deluding myself. I have the feeling that I get a pretty good sense of what's going on thanks to all these reports we are forcing people to get through. Maybe we need to get back to what problem are we trying to solve? Well I think a couple things came to mind as I was looking through this. One is completely different from what we've talked about so far but I think there is an interesting mention down in the proposal that this working group would start off by not having regular phone calls because the time slots, it's hard to find a time slot that's geographically acceptable across all those different time zones. There might be some different ways of just operating here that might be interesting. The other thing that stuck out here was actually more in conversation that I think was a heart that I was discussing with and he made the observation and I think he might be on if he wants to make this himself right now that there's subject matter experts that we'll be looking at say privacy or architecture or other things. This seems like a form where we could draw in contributors from our companies who are subject matter experts in recruiting and diversity and so on so that those of us that might not have that experience or those skills aren't trying to reinvent the wheel or maybe arrive at counterproductive solutions. I sort of viewed this as building community health, building ecosystems, things like that versus an overlord. I think that could come in and help here a lot. But what Dan was talking about sounds more like best practices again which is different from metrics and reporting. I can see how the second work product was phrased in such a way as to trigger some of this response and probably because I think where it came from was this idea that some of the scripts that Tracy has written and Chris I know you've written and others might be usable in the form of a sort of dashboard that might come out if you regularly run metrics which the self-reporting from the projects the TSE doesn't have right now. But that instead of just dumping metrics that the community health working group or perhaps the hyper-legislative staff would help the projects interpret those numbers and kind of like the weatherman looking at weather data might help give a sense of that, not to replace or to run for the projects they're quarterly updates to TSE. So I think I was phrased kind of clumsily and probably could be improved to be more specific to that and not come across as a competitive thing to the quarterly reports to the TSE. So I kind of viewed this group as more of a resource to working groups and projects rather than a policeman and so the point was that if some working group was having issues or some project was having problems then this group would kind of be a collection of open source veterans who could help out. And I think that might be useful for people that may not have been around the open source community for as long or are kind of experiencing growing pains or something like that. So I think if maybe the proposed charter could reflect that a little more. I was going to come in with a point very much along those lines and I think I like that idea. So could this be shifted to be more of an intervention group? So if I think about from my own experience with Burrow we don't have the need to interpret some kind of big data metrics around contributors. I know everyone who will have contributed and I know a lot of the areas where I could do with some help to say for example have someone who has expressed an interest actually be handheld over the course of a month. So you could perhaps imagine a situation where you have a batch of quarterly reports and maybe a group like this could specifically target some interventions over the next quarter or maybe a month in the next quarter to actually apply some resources to try and fix a specific problem. And in the conversation that was happening around diversity for example one of the things that came up again was actually encourage and cajole people to stand for things or to go and do things. So I mean community harassment working group harassment is an unfortunate choice but in terms of like actually harass them into doing good you mean? So what happens for me is with people that have expressed interest I get distracted onto my day job having tried to get them started and maybe that's when they fall off. Whereas if there was a dedicated resource that we couldn't have all of the time but we could have specifically that would be a different task because I also don't like the idea of duplicating the evaluation part that the TSC does but if it was an intervention thing a task force that's different. Yeah I mean this is Silas to that point actually a lot of projects as they mature or organizations they tend to develop that particular type of a role where you actually have people that are doing a lot of what I know Tracy and I'm sure Rye and David are doing in terms of going out and saying here's how you land your first commit and so forth and that in a general way that's fine but you know sometimes it's also just helping people sort of navigate through where the issues and which one should I work on and can I add a new feature all those kind of things where sometimes people just need that extra sort of onboarding kind of support and if that you know again but that's a very different thing than coming up with just best practices you know that's actually sort of a role that people start to take on and then they spend a lot of time in either presenting that or you know serving in that function within the community as a sort of a social blueprint if you will to get people onboarded. Yeah I think sorry go ahead. Yeah I do believe that health is very important in the community and I also believe that there's already the sharing for each other working group and the most important output in the group chart is the metrics and best practice both are good things to the community but my only question is that is this outcome actually almost inside the scope of the GSE? Yeah do we need a special working group for that? I'll just say one of the things that I hoped that would come out of something like this working group is we have lots of phone calls and it's not clear they're optimally scheduled so if this working group say you know did a bunch of research and came back and said hey hey guys we tried a bunch of stuff and in our experience this phone call schedule works best for this kind of group to maximize your participants you know and then they could say like maybe you could try it if you think your working group looks like this or something like that. So that's what I was kind of hoping for. I think that's in the charter is that kind of what the people had in mind for stuff like this or? So I think I'll just add a couple things and then I know we do have kind of a meaty topic following this so I don't want to delay this too much but you know obviously there's a hypothesis that we're not very geographically diverse right that our working groups and when they're held are not conducive to people joining right I know we specifically are impacted by that. I am specifically impacted by that based on some of the times that some of our calls happen and I'm sure other people are as well right and so we want to make sure that we're opening up Hyperledger to the majority of people and then secondly you know if we think about back to Nathan's project update where he you know reported that he has some you know he wants to get more people involved but he's not quite sure how to do that you know and I think the TSE nodded to that and say yeah we need to find a better way for that but nothing's been done right we haven't necessarily made any progress on that well specifically right I think you know David and I and Rai went back and after that call and said okay well what are the sorts of things that we could you know do on the Indie project to make it more conducive to new contributors coming in and that sort of thing and probably written up some notes and provided that to Nathan and I think that's the sort of thing that we want to continue to be able to do is to help where there's things that need to be helped but do it on a much wider basis so it's not a one-off right where we're only helping one project we're truly coming up with what are the sorts of things that all of our project should be doing to make sure that we can bring in diversity and we can bring in additional contributors and that sort of thing so I think that's where our head was right is let's see if we can prove or disprove some of the hypothesis that we do have about the health of our community and what are the specific things that we can do to make sure that we're if those hypothesis prove to be true we figure out how to make a difference right make an impact in improving it so that other people can contribute. Hey I've got a quick question this is Dave, does the Linux foundation have any like YouTube videos where the topic is so you want to contribute to open source and it you know starts from the very beginning like you know how to program or you know how to translate or you just care and want to join in I don't think I've ever seen a video like that which assumes that you know nothing Yeah but I don't know that it's for Linux generally or you know the whole Linux foundation and all the collaborative projects as much as I know that for instance Kubernetes does right there you know again they've cultivated this role of sort of community advocate that gets out there and helps people on board and provides this kind of feedback and so forth I mean that's their job right it's kind of like the role that Ryan Tracy and Dave play in terms of but again that's a paid role where as I know in CUBE it's a it's a it's a volunteer you know you've got people like Sarah Novotna, Novotny rather who's you know that's her that's her primary function is to sort of be the one that gets out there and drives you know increasing diversity and drives additional contributors and Tracy did a webinar entirely on this too and that recording is there and it's been promoted and there's some other broader stuff that has been done and I know more coming down the pipe but anyways this is a group to have those kinds of conversations within like is there content to create that sort of thing And I sort of viewed this I mean I had made a comment in the email thread that I think there's a big difference between some of the working groups and some of the projects you know I think like Fabric most of your people you know the developers working on it are probably getting paid to do that job where I think some of the working groups it's much more volunteer effort and so I you know I think there's a difference and trying to figure out and understand those differences because maybe what we need to do with the working group is different than what you need to do with a big project like Fabric or Sartuth and I think this would be a way for the you know maybe working group is too strong you know it's too much organization but you know maybe some kind of committee to go off and understand those things I know the performance and scale working group I didn't feel we were making a lot of progress at one point so we went from meetings every other week to a weekly meeting and I felt things took off when we did that and I know personally if you know I have an hour meeting and I have a two hour action item that's due in two weeks I'm not going to do it till just before the next meeting and I think you know I'm sure there's a lot of nobody else is like that at all but I think that you know that doesn't get the stuff out there for discussion whereas if it's weekly then that's you know right on my list of things to do and if it's not part of my day job you know it's hard enough getting it near the top of my priority so I think understanding those differences is good maybe we don't need a working group for that but you know a way to go through and do that and help new groups when they form versus you know an overwatch on fabric is hard to I don't think we need that but you know what can we learn from those projects or other working groups that have gotten the white paper out we had hard come and talk to the PSWG about you know okay this is what you're going to need to do now so that you're going to you know you're getting ready for a tech writer and things like that and that was very valuable to us so I think there's a need for something yeah I yeah so Mark I totally agree I just I guess you know the discomfort I have I should say is with the whole reporting on the report you know on the projects and the working groups because I think and I think that's also in the TSC chat we don't necessarily want to set up some sort of an adversarial type of a situation there but I do think that you know having discussions on how do we increase diversity you know from both you know at all of the different things and how do we go about and attract new contributors and how do we address the fact that a lot of stuff is sort of paid development versus volunteer or you know contributions I'm happy to have that kind of a conversation although again I you know I tended to think that as we do the various reports those kinds of things come up and we have solid discussions here in the TSC and I wouldn't want to divert that necessarily I think we still need that and so anyway there we are I maybe if we just sort of modified the charter so that it's not so much some sort of oversight as much as it is a set you know coming up with an initial set of recommendations and then you know maybe periodically I think and now I forget who was it suggested maybe Silas you know that when issues come up then the team can convene and sort of do some deep thinking and report back to the TSC on what they call it makes sense maybe Tricey and Rye you guys have enough feedback and everybody else who wants to constructively work on that and have enough feedback and we can give some time then to the rest of the agenda topics here I'll take that as a yes I think you're on mute still Tricey so thank you and Rye and David if he's on okay next up is composer Simon hey I don't know whether everyone has had a chance to read the update I put in this morning along with the letter to the mailing list from the IBM contributor team I posted them in the TSC channel the email whilst I'll go through the update and then maybe we can discuss the email which is probably the more interesting part of it firstly apologies that this is four weeks overdue it's summer in the UK so I've been off for quite a few weeks anyway let's move on so in the past quarter we continue to see significant amounts of activity on rocket chat and stack overflow from people trying out composer using it hitting issues and asking how they can do certain things and as always the IBM team has offered two full-time people to help work with those users and get them up and running answering the questions we're also continuing to see contributions from outside IBM but these are again still really minor contributions such as doc fixes typo fixes that kind of thing I've released a new major version Composer 0.20 and this release has a small set of features since 0.19 which I discussed on the last quarterly update but the major new thing in this version is that it supports deploying to Fabric 1.2 so allowing you to use some of the latest features in Fabric it's a feedback application project using Neoman Generator one of the regular pieces of feedback we got from the community is you've got this great REST server, it's really easy to get started and up and running but I need to customize it to do X where X is add my own APIs or add my own authentication mechanism or just add my own code to it and you couldn't really do that because we just packaged up a REST server and you can really have a chance to edit it by slowing down the composer code yourself and tweaking it so the new generator generates a REST server on disk you can edit the code to your hards content we've also made some changes to transaction processor functions the first one of which is exposing a Fabric functionality where a blockchain transaction one as executed to smart contract can return data to that smart contract and this is basically a performance improvement because what we were seeing is that people would submit a transaction they weren't able to send any data back with that transaction so they had to then send another request into the smart contract to say oh could you get me the updated data so the bypass is the need for that second query you just submit one transaction and it returns the updated data that you need and the second update to transaction processor functions is being able to mark them do not commit or read only and this is to solve another common community requirement where in composer before if you wanted to query assets or participants that were stored on the blockchain you were limited to our sort of crud operations so get all or get by ID or writing queries using the composer query language which is a SQL like language for selecting data on assets being able to mark the transaction processor function as do not commit means it's basically the same thing as a query function where you can write any code you want for querying data from the blockchain network and this lets you use any of the composer and Fabric APIs to do whatever querying you like and additionally on top of that filtering of that data but on the server side rather than having to pull it all back to the client application and filter it there so again it really came about as a performance requirement but it's also useful for exposing additional functionality to users in terms of contributor diversity I've listed them all in the project update we've had various small PRs as I mentioned from several other companies I won't go through them all here and we haven't changed our list of maintainers since the last project update any questions on that? Thanks for the reporting actually I was asked this question by several people so do you know is there any protection usage to include the Hyperledger Composer so at the moment within IBM we know of one production project using Composer can you share more details? Not sure how much I can say but it's a European banking consortium doing trade settlement We know what that means Anyway I'm not sure what I can say but a couple of questions for you one is that email that you mentioned I read both the report of the status and the email the email somehow seems to imply that there is a chance that Composer it is the sunset of Composer or that you are producing investments in it IBM is and that it is going to be phased out in a sense but I do also see some green shoots there which is Selman's proposal for a model modeling language that would be platform independent which was of course the dream of the Composer in the beginning so that's the first question is why should you use Composer meaning is there anything that can be done in fabric except for let's say private data objects 1.2 stuff that cannot be done with Composer? I'll go for the second question first as I think that's easier to answer is there anything you can do in Composer that you can't do in fabric or the other way around? The other way around I mean I hope there is nothing you can do in fabric I mean in Composer that you cannot do ultimately in fabric because that's the only system you have yeah it's just code right so yeah there are things plenty of things in Composer and that is one of the reasons you will see in that email for IBM's decision. The example I quoted is private data collections. Now once we have exposed all of the underlying fabric APIs from within Composer private data collections requires additional configuration to be provided as part of deployment and currently we don't expose the APIs or command lines that allow you to provide private data collection integration which is why you can't use it with Composer today. Yeah sure I mean I did explicitly call out private data collection as not my focus. Is there anything else? There will be other things coming up so certainly in Fabric 1.3 there's work being done with Identity Mixer that will not just magically start working Composer when we start to import Fabric 1.3 that will again require changes Composer to enable it. Those are the two main ones in my head? Yeah I understand that you don't have a smooth upgrade path because of the way things are set up but in terms of the existing one like let's say 1.1 are there any things that you cannot know? For 1.1 I think we're okay. Is there direct support for the policy? I didn't think so. Is that it again? I said is there direct support for supporting all the various policy derivatives that you might have for how many endorsements to retrieve and all that stuff? If I provide the endorsement policy during deployment so that bit's fine. Although saying that I don't think we really respect the endorsement policy in terms of picking. That's kind of what okay that's the part it's nice to have a policy but then if you can't follow it then that doesn't really help you. Well we try to follow it we just send it to everyone Oh I see.  I hope that sort of clear is that when you features go into Fabric it's not just a matter of them magically appearing in Composer there is a significant amount of work to be done to re-expose them in Composer. I just wanted to go ahead and dip in another question. No just the first question which is a sunset of Composer. So the statement in the email sorry if that wasn't clear is that it's an IBM resource decision where my team in IBM who is tasked with the developer experience for blockchain use reducing the amount of work we put into Composer to focus on delivering updates to Fabric. That doesn't mean we're dropping off the face of the planet and leaving Composer to itself we're going to continue to update it to support the latest Fabric releases and if any high priority bugs come along then we'll pick those up and fix them but we're not going to be doing any new feature work. And that's not a forever statement at this time that's a we might be back but for the time being most of my team will be working directly on Fabric instead of Composer. Right and to make sure that we're clear it's maintaining compatibility with the existing set of capabilities that Composer has with respect to Fabric Yeah that's a good point and that is so when 1.3 comes out we will update it to run on a 1.3 Fabric but we will not update Composer to support the 1.3 features unless they are simply API updates that can be used without exposing additional configuration and then right and then to the point that I was going to be adding is that you know again as the sort of the having the responsibility of your team of addressing sort of the developer experience and so forth you know a lot of thought was also given to the fact that the existing SDKs are really very sort of granular you know sort of low level detail kind of stuff not really very well the user experience isn't the greatest let's just say you can do a lot with it you can do a hell of a lot with it but or with all of them right and go and so forth but the problem is is that they expose too much and so from a developer perspective you don't have the simplicity that you might have with something like Composer that is essentially hiding a lot of the gory details about how you under you know how do you retrieve the endorsement policy and then how do you prepare a proposal for each endorser and ship it off and compare results and all that kind of stuff right so a lot of that stuff gets hidden in Composer whereas with the SDKs you have to manage that all yourself yeah and so a lot of the focus is on proving that UX from an SDK perspective right so so that the SDK and then the ability to write chain code and so forth is significantly simplified right yeah and I cover that in the mail so as you touched on there the Fabric SDK if you want to submit a transaction to a fabric network wait for it to be committed and be notified of that that's somewhere in the region of like 50 lines of code and in Composer that's five lines of code and as Chris mentioned we hide a huge amount of interactions with the Fabric SDK in Composer and this is really wrong with Composer was never designed just to make fabric easier to use it was designed to make it easier to take your business use case and map it into a running blockchain network and that's why we have the modeling language which also provides a huge amount of confusion we've seen where someone sees a Composer application that has you know a five lines of code to connect to a network and submit a transaction and then they see the Fabric version of that and they're like how do these two actually map together are they doing the same thing is Composer just doing magic and that's another one of the reasons for our current plans. Hi Simon this is Leonard just a quick question thanks for that update I was just wondering about the modeling aspect of Composer is that will that eventually disappear based on this sense of the clause or will you provide for business use where they can actually model their blockchain environment and not have to worry too much about the you know sort of the very detailed programming aspects to capture their business requirements, their business and the smart contracts that would need to be generated will you continue to provide a model and interface for better business user experience in designing their blockchain you might say network. Okay so that's a great question so firstly Composer isn't going anywhere we're not going to delete the code website or any of that so you can continue to model your blockchain use cases using Composer. We strongly believe that modeling your blockchain networks is the way forwards we've had so much good feedback around the modeling language and how much easier it makes development and how much better it is at engaging the business people in the development of blockchain solutions and at the bottom of the mail we will see a reference to some work Dan Selman is proposing to do he is on the call where we sort of look at pulling out the modeling language from Composer as it is today Dan is using the modeling language in the work he's doing in clause we obviously use it in Composer we could take that modeling language and embed it into other blockchain platforms as well for example Interfabric, Sawtooth a library that lets you describe a blockchain business network or a modeling language that lets you do that and a library that lets you write programs that interact with that model so it's really valuable code maybe it is worth pulling that out and managing it as a separate project If I can just jump in for a second because I do think we should leave some time we're seven minutes to the end for the cello update in conversation there but just really quick I want to thank you Simon for the transparency that you're bringing to the internal IBM resource discussions and decisions and B I think this is an inflection point for the project it doesn't necessarily mean the project should be wrapped up it's kind of saying the current direction is one that gives a lot of people who have been involved with the project concerned about the direction and that's leading to perhaps a change in leadership I think the follow up question should be what does this mean for the future of Composer and that kind of conversation should really happen on the Composer developer's mailing list and now might be the time if any of you have used Composer have found value in its existence in terms of recruiting new people into the community to kind of direct your attention or other people's attention over to that list and start the conversation there what might a 2.0 of Composer look like, what might a modeling language future look like and does it make sense to have a stand alone thing like Composer or plugins for other dev tools out there IDEs you know I can say it's been extremely helpful to be able to say here's a pathway for not just the elite developers like all of you but for average developers to be able to bootstrap and start building in the context of a hackathon that demonstrates doing a blockchain thing even if that wasn't a toolkit for taking it all the way to production even though it was just kind of a taster and I think we need something like that and I think even a very radically different approach and code base could carry the mantle of a Composer 2.0 but it needs to be rejuvenated and I respect IBM's decision to make its internal kind of resource decisions that were to put its people for any company right so I wouldn't encourage us to think right now too much at the TSC level what the future of Composer should be let's direct it over there but I do want to thank Simon and obviously IBM and the rest of IBM for having put so much into Composer and giving us something that's been so strong in bringing in new developers to the community So Sunset does imply Sunrise tomorrow so you're an optimist Even the Apache Web Server project started when a bunch of student developers on the NCSA code all got hired away by Netscape and the rest of us users kind of looked at each other and said well I guess we got to take over so a completely possibility is that the users of Composer kind of have this moment of self-actualization too but I'd like to leave the door open for that and also say like the project could continue even if the approach and the code base underneath take a radical change because I think what people think of as Composer is this non-ramp and I even like the idea of making it more framework agnostic, making it higher level and not so deep in the weeds with fabric as the current approach Unlike people I know we don't have time for deeper discussion now but this ties back to the previous discussion we had about the community working group type of thing if we had some organizational thing there that could help here so when a company decides that it can't invest its resources in a project it's been sponsoring is it completely up to the community to figure it out or is there some type of organization within Hyperledger that could help figure out how it picks up the pieces and keeps going because there might be uses outside of IBM that are going to get left in the dust here if they can't pony up resources to do it on their own I think there's a complimentary flow of that too of that information that I have viewed Composer is a very successful project in terms of popularity and I read from your note Simon that that hasn't translated into contributors and so feedback assuming that we get this working group moving forward feedback into that working group about what didn't work even if we didn't figure out what would work I think would be helpful Okay so we have two minutes left and that's really not fair to Chelo. Bawa and team I'm hoping that we can defer until next week is that okay? Alright thanks Bawa and so I would like to thank everybody I think this was a healthy discussion I think that the point on having something that's wildly popular and yet you don't see a whole lot of return on having new people come and join I think that's pretty much across the board to be honest I mean there are to some of the projects there are more contributors and there's a greater diversity but it's still I think there's still quite a few especially ISVs and even major vendors that are using some of these platforms and or tools and not really contributing much back so I think there's a lot we can do in that regard and I think having a discussion on that would be valuable whether it's in the TSC or in the working group so anyway so thanks everybody and we'll see you all next week Thanks Chis. Thanks everyone have a good day. Welcome back Chris. Thanks. Welcome back. Bye


from Denver, Colorado. It's theCUBE, covering Supercomputing 17, brought to you by Intel. Hey, welcome back everybody. Jeff Frick here with theCUBE. We're in Denver, Colorado at the Supercomputing conference 2017. I think there's 12,000 people. Our first time being here, it's pretty amazing. A lot of academics, a lot of conversations about space and genomes and heavy lifting computing stuff. It's fun to be here. And we're really excited. Our next guest, Karsten Rohner. He's the CEO of Swarm64. So, Karsten, great to see you. Yeah, thank you very much for this opportunity. Absolutely, so for people that aren't familiar with Swarm64, give us kind of the quick high level. Yeah, well in a nutshell, Swarm64 is accelerating relational databases and we allow them to ingest data so much faster, 50 times faster than a relational database. And we can also then query that data 10, 20 times faster than a relational database. And that is very important for many new applications like IoT and banking and finance and so on. So you're in a good space. So beyond just general, better performance, faster, faster, faster, we're seeing all this movement now in real-time analytics and real-time applications, which is only going to get crazier with IoT and internet of things. So how do you do this? Where do you do this? What are some of the examples you can share with us? Yeah, so our solution is a combination of a software wrapper that attaches our solution to existing databases and inside there's an FPGA from Intel, the Aria 10. And we are combining both such that they actually plug into standard interfaces of existing databases like in Postgres, the foreign data wrapper, the storage engine in MySQL and MariaDB and so on. And with that mechanism, we ensure that the database, the application doesn't see us. For the application, there's just a faster database, but we're invisible and also the functionality of the database remains what it was. That's the net of what we're doing. So that's so important because we talked a little bit about offline, you said you had a banking customer that said they have every database that they've ever been created, right? They've been buying them all along. So they've got embedded systems. You can't just rip and replace. You have to work with existing infrastructure. At the same time, they want to go faster. Yeah, absolutely right, absolutely right. And there's a huge code base which has been verified, which has been debugged. And in banking, it's also about compliance. So you can't just rip out your old code base and do something new because again, you would have to go through compliance. Therefore, customers really, really, really want their existing databases faster. Right. Now the other interesting part, and we've talked to some of the other Intel execs, is kind of this combination hybrid of the hardware-software solution in the FPGA and really opening up an ecosystem for people to build where software-based solutions that leverage that combination of the hardware-software power. Where do you see that kind of evolving? How is that going to help your company? Yeah, we are a little bit unique in that we're hiding that FPGA from the user and we're not exposing it. Many people actually, many applications expose it to the user. But apart from that, we are benefiting a lot from what Intel is doing. Intel is providing the entire environment, including virtualization, all those things that help us then to be able to get into cloud service providers or into proprietary virtualized environments and things like that. So it is really a very close cooperation with Intel that helps us and enables us to do what we're doing. Okay, and I'm curious, because you spent a lot of time with customers. You said a lot of legacy customers. So as they see the challenges of this new real-time environment, what are some of their concerns? What are some of the things that they're excited that they could do now with real-time versus batch and data lake? And I think it's always funny, right? We used to make decisions based on stuff that happened in the past that were kind of querying. Now, really the desire is to make action on stuff that's happening now. It's a fundamentally different way to address the problem. Yeah, absolutely. And a very, very key element of our solution is that we can not only insert these very, very large amounts of data, that also other solutions can do, massively parallel solutions, streaming solutions, you know them all. They can do that too. However, what the difference is that we can make that data available within less than 10 microseconds. So... 10 microseconds. A data set arrives within less than 10 microseconds. That data set is part of the next query. And that is a game changer. That allows you to do controlled loop processing of data in machine-to-machine environments and things for autonomous applications and all those solutions where you just can't wait. If your car's driving down the street, you better know what has happened, right? And you can react to it as an example. It could be a robot in a plant or things like that, where you really want to react immediately. I'm curious as to the kind of value unlocking that that provides to those old applications that we're working with what they think is an old database. Now you said, you know, you're accelerating it. To the application, it looks just the same as it looked before. How does that change those performance of those applications? I would imagine there's a whole another layer of value unlocking in those entrenched applications with this fast data. Yeah, that is actually true. And it's on a business level. The applications enable customers to do things they were not capable of doing before. And look, for example, in finance. If you can analyze what the market data much quicker, if you can analyze the past trades much quicker, then obviously you're generating value for the firm because you can react to market trends more accurately. You can mirror them in a more tighter fashion. And if you can do that, then you can reduce the margin of error with which you're estimating what's happening. And all of that is money. It's really pure money in the bank account of the customers, so to speak. And the other big trend that we talked about besides faster is sampling versus not sampling. The old days, we sampled old data and made decisions. Now we don't want to sample. We want all of the data. We want to make decisions on all the data. So again, that's opening up another level of application performance because it's all the data, not a sample. For sure, because before you were aggregating, when you aggregate, you reduce the amount of information available. Now, of course, when you have the full set of information available, your decision-making is just so much smarter. And that's what we're enabling. And it's funny, because in finance, you've mentioned a couple of times, they've been doing that forever, right? The value of a few units of time, however small, is tremendous. But now we're seeing it in other industries as well that realize the value of real-time, aggregated streaming data versus a sampling of old really opens up new types of opportunities for them. Absolutely, yes, yes. Yeah, finance is, as I mentioned in the example, but then also IoT, machine-to-machine communication, everything which is real-time, logging, data logging, security and network monitoring. If you want to really understand what's flowing through your network, is there anything malicious? Is there any actor on my network that should not be there? And you want to react so quickly that you can prevent that bad actor from doing anything to your data? This is where we come in. Right, and security's so big, right? And it's in everywhere, especially with IoT and machine learning. Absolutely. All right, of course, I'm going to put you on the spot. So, November 2017, hard to believe, as you look forward to 2018, what are some of your priorities? If we're standing here next year at Supercomputing 2018, what are we going to be talking about? Okay, what we're going to talk about really is that we will, right now we're accelerating single-server solutions, and we are working very, very hard on massively paralleled systems while retaining the real-time components. So we will not only then accelerate a single server, by then allowing horizontal scaling, we will then bring a completely new level of analytics performance to customers. So that's what I'm happy to talk to you about next year. All right, we'll see you next year. I think it's in Texas as well. It's wonderful. Yeah, great. Thanks for stopping by. Thank you. He's Carson, I'm Jeff. You're watching theCUBE from Supercomputing 2017. Thanks for watching.


Okay. Good morning, everyone. Good morning to those who are joining online. Welcome. All right. Everyone can hear me. Okay. Those are online. Yeah. Okay. Great. So last class, we completed chapter five. We looked at how we can get started by evangelizing, by asking questions. And we saw the prayer approach, the two minute testimony approach, the power encounter approach where you can just go to people, pray for their need, expect God to bring healing. That could be even word of knowledge, prophetic word, or a miraculous intervention in their lives. Right. Then we very importantly looked at rules, certain rules while engaging with people. Show genuine care. Right. Don't be judgmental. Don't criticize people. Right. The wrong thing to do is to say, okay, this is wrong because of this. Right. What did Jesus say? They shall know the what they shall know the truth and the truth will set them free. Right. So as people who are reaching out, ministering the gospel, focus on the truth than focusing on what is wrong. Right. So sometimes in when we look at ministry, when we look at certain things that are happening around us, you see that people are focusing more on the wrong things. This is wrong. This is wrong. This is wrong. This is wrong. But the Lord Jesus said a beautiful example for us. What did he say? You shall teach them the truth and they shall know the truth. The truth will set them free. Right. So don't criticize people. Don't look down on them. Just minister to them out of the truth of the gospel. Avoid arguments and very importantly, when you're debating, when you get an opportunity to debate with people of other faiths, sometimes it gets into an argument mode. Right. Now I've been in those situations. Right. It's becoming an argument. The best thing to do is to stop and to just change the topic and be wise in those times. Right. The wrong thing to do is, OK, if you don't believe, I'll see you in hell. Right. That's the wrong thing to do. But when it's getting into a debate, when getting in an argument, just step out. Right. Be wise. And then don't let other people's negative response bring you down. Right.  People can tell you, hey, you don't know how to do this. So what is your response? Yeah, I don't know. So let me learn it. Right. It shouldn't be, oh, I don't know. OK. Then that's my story. No. Right. So people will accept, people will reject, people will mock you. But that should not stop you from ministering the gospel. Right. And then when we look now, you know, we have so much of tools. Right. I remember when I used to go out when I was a young boy, we only had those tracks. You know, I couldn't take out my phone and say, OK, you know, what do you see this? This is what it is. And there are pictures and some verses. But now there's so much, you know, there's content on YouTube that I remember seeing this. Somebody sent me a picture of this. You know, one day I was feeling very tired. Right. This happened just a couple of weeks back. Somebody sent me a picture of this shepherd looking after the sheep. And it said, the Lord is my shepherd. I shall not want. That's all. Right. Now I've read that verse maybe thousands of times. But at that moment, it just gave me such an encouragement. Right. So I didn't feel like opening the Bible and reading that time, but just a small picture and the graphics. Right. So you've got so many tools, apps and when you go online, there's so much that we can learn. Right. So make use of those. And even as you evangelize, let it become a fruitful evangelism. Right. Now doesn't mean that, OK, if nobody is accepted, the gospel is not fruitful. Right. If if you've shared the gospel, no, I'm sure you all are going to your colleges just because somebody does not accept your message doesn't mean it was not fruitful. Right. Remember that you are getting trained. You're getting you are growing into maturity.  Right. So go through that preparation season. Nobody can, you know, come and just start playing an instrument. It's not going to work. Right. So there's this period of preparation that is involved. Right. So even now, when you when you're going out to colleges, there are times you may feel, you know, tired or you may feel that this is not working out. It's OK. Push for it. Right. Because later on, you look back and say, oh, you know what, I did it in college and I feel that, you know, this is something has really helped me to do what I'm doing now. Right. So don't be discouraged when people don't accept. Right. Let's continue to do what God has called you to do. OK, let's get into chapter six. Chapter six, we're talking about invite and prayer. Now, let's read that whole passage. John chapter one, 35 to 51. It's a it's a beautiful example here. The Lord Jesus has launched his ministry. Right. And what does he do? The first thing he does is he finds people to join his team. That's the first thing he does. Jesus doesn't say, OK, I am come. Now I will do everything. No. So let's read that passage and we see how the Lord Jesus chose the first few disciples among the 12. Let's read. Maybe one of us can read. John chapter one, 35 to 51. Yeah. Yeah. That's verse 40, 42. Right. OK, let's just stop there. OK. So we see this encounter. What is the Lord Jesus doing? He's just doing what he's doing. And then the next day, John was there with two of his disciples. And what does John say? Behold the Lamb of God. He's pointing to Jesus. And then this Andrew goes and he goes there. I like this verse. Right. When the two disciples heard him say this, they followed Jesus. Right. Verse 50, 38. Turning around, Jesus saw them following and asked, What do you want? Remember last topic last week, what did we talk last session? Asking leading questions. Right. What is the question Jesus is asking them? He's just going. John the Baptist says the Lamb of God taking who takes away the sins of the world. And then they're following. So just picture this. Right. Jesus is walking. Two people are following. Jesus asked them, What do you want? Do you have any exploration? Oh, you've come. What did John tell you? John told you to come. OK, come. Did he do all that? Does he know that John told him to come? Does he know? But he asked the leading question, an appropriate question. You see the wisdom of God. Right. He said, What do you want? And then they answered another question. Where do you stay? It's not even relevant. Is it relevant? It's not relevant. He said, Where do you stay? What did Jesus say? You go straight, take a second right, take the first left. What did Jesus say? Come and see. Right. Such a beautiful encounter. And now listen, this is the first time they are meeting. First time. But why is it that these two disciples follow Jesus? And they say later on rabbi, they call them teacher. They don't know about Jesus. Right. So here in the first point, we can see that John the Baptist points to Jesus with these simple words, Behold the Lamb of God. Two of his disciples followed Jesus only because they trusted John the Baptist. Only based on trust. Right. And you see why trust is important. You got to build trust when you are ministering with people. Right. Last class we were talking about in my in the second years, I was talking about pastoral calling. Right. And the pastoral calling requires you to give sacrifice. There's a lot of, you know, a lot of things that are involved that sacrifice. We need to hear from God. We need to be there for people. Right. Now here, Jesus is saying only because of trust, they're following him. They're following Jesus only because of trust. Right. They say, trusted John the Baptist. John the Baptist said, so they're, they're following me. Now when you and I make commitments, right, learn to follow those commitments. Why? Because you're building trust. Right. You know, trust is something that is easily broken. Yes.  And if it's not done, what happens? Trust is broken. Right. But here, John the Baptist says, behold, the Lamb of God, they trusted John the Baptist. That means what? John the Baptist was somebody who cared for his people, for the disciples that was under him. Right. It was not like, okay, you want to come, come, you don't want to come, don't come. As a leader, he cared for his people. He built trust. Now you look at any relationship, husband, wife, father, mother, parents and children. Any relationship, there has to be trust. Right. And when you build trust, it's a place where you can speak into people's lives. Right. I remember growing up, you know, I would do everything wrong, everything wrong. But the parents would still trust me. I'll say I'm going here, but they know I'm not going there. They'll say, okay, go. There came a time when I knew that I'm lying. I knew that they knew that I was lying.  Why aren't you stopping me? I said, because I want you to trust me. That's what my dad told me. I want you to trust me. I want you to have this feeling that you can tell me whatever you want and I will trust you. Whether it's good or bad, you tell me what it's like. And that really impacted me. Right. And I remember that day from then on, I never lied to my dad. Never. Even if I was going to do something wrong, I would tell him the truth. So he would ask me, did you do something wrong and come? I'll say yes. Did you go out with your friends and do something wrong? I say yes. But then he had the right to speak into my life. He would tell me, you know, this is what it is. This is why you should focus on your studies for now. But I would listen to him. Why? Because there was this level of trust that we had built. So trust is very important. Even as you, each one of us, we put our trust in God. We are also called to put our trust on people. So you build that relationship, right? You build trust, right? Are you with me? Right. So simple trust and the Lord Jesus welcomes them and reveals who he is. Andrew was one of them. Now, why is this significant? If Andrew did not trust John the Baptist, Andrew wouldn't have followed Jesus. And you see Peter, Andrew goes back and he tells his brother, listen, we found the Messiah, come. And Peter also agrees to come. You see again, there's trust between two brothers. I grew up with two elder brothers in my house. We were very, very, very close friends. Even now, you know, my parents say, what do you all talk for so long? You're the growing of your own kids, but we're very close family, very close to each other. Not a day passes by that we don't call each other. We're on different countries, but we call each other every day. Because there's this trust, there's this bond that's developed. We're always there for each other. And it happens over time, right? So if you're ministering with people, if you're ministering on the road, you're meeting with somebody, you probably may not meet them again, but you've got a friend or a relative and you want to minister to them. You got to spend time with them. You have to be able to build trust. Don't expect people to listen to you and obey whatever you say if you are not willing to put the effort of building trust. Yes. Why are you all so serious? It's true, but right? If you're able to invest your time and effort into people, they will trust you. I remember calling this one friend of mine. I called him to one of these. We had something called as Healing Sundays, right? Like how we call it Supernatural Sunday. Many years back, we had something called as Healing Sunday. Right? So this boy was, my friend was, he was always unwell and going through some problems. He had problems in his appendix, right? And he's not from Christian faith, but you know, he was a good friend of mine. I remember going and telling him, hey, why don't you come to church? There's something, there's a healing service happening. But I knew that he doesn't like this whole thing about Jesus and about church. He hated it. But you know what he told me? He said, I will come only because you're calling me. Only because you're saying, come. It's a healing service. I'll come. But after the church, we have to come off quickly. I don't like to stay around. I said, okay, we'll do that. Right? And so he came and after church, as I promised, immediately we left. A lot of people, I wanted to meet, but I had to keep my word. I had to build trust for this guy. Otherwise, he's not going to come again. Imagine I came out of church, Vendan spoke to everyone and he's standing there in the corner. I've broken the trust because I told him after service, we leave immediately. So these small things count, right? These small things count.  He would come. And eventually he began to understand the gospel and eventually he accepted Christ. But it all came out of trust. So that's something that we have to build. There are times we have to develop trust with those who know us. And when we point them to Jesus, they will readily accept it. Now, for example, if you're playing the guitar, right? And I say, hey, instead of G minor, why don't you play the F sharp minor? Now, hopefully you will listen, right? We'll say, okay, let's try it. Now, what if it's, you know, what if I don't know an instrument, you know it. You know that I don't know an instrument. And I say, why don't you play this chord? You'll say, no, no, no. It can't be that. Right? Because there's already a basis. You don't know how to play that instrument. Right? So there are times all we need to do is build trust, right? Build trust among people and 80% of the work is done. You're just pointing them to Jesus, right? Now let's continue from there. John 1 verse 40 onwards, 40 to 42, 40 and 42. Just read that. Okay, we already read that, but read it again. This talks about the power of a single invite. Here, what happens is Andrew is called Peter and the Lord Jesus reveals his future to him. You shall be called Cephas, the rock. When does he say that next? When does Jesus say this next? This is the first encounter after the resurrection, revelation. Okay. Right? So we see two encounters. Both the times Jesus is giving it to Peter, right? Now, who knew that this one encounter will change history? It changed history, right? The reason we are talking about Peter, a fisherman in Jerusalem was because Andrew went and called him and came. The reason we have the epistle of 1st and 2nd Peter is because Andrew went and called his brother and came. That's the only reason. Did we ever think of it? Did we ever think that this is going to be the impact of Peter's ministry? The only reason the church in Jerusalem started was because of Peter. Remember, in the book of Acts, Peter goes there, he stands there, he preaches the gospel. How many people? Thousands of people come in as a church. Who started it? Where's Andrew? Is there a mention of Andrew there? No. But it was Peter who started it, right? So the power of one single invite.  Let me give you this example. I don't know if I shared this example, but did I give the example of Billy Graham? Did I give the example of Billy Graham? Billy Graham is a young boy. He would go to church every Sunday in a small church. He was probably about 6 or 7 years old. Everyone knows Billy Graham, right? The great evangelist touched more than 5 million souls. He used to go to Sunday school as a small boy. There was this old man, a very weak old man. He will come and teach in the Sunday school, right? And there will be 5, 6 children there, right? And he will come and teach. And this happened for many years and people would say, you're so old now. Why do you want to do this? He said, no, I believe that at least I'm sowing seeds. God will use them. So in one of those children's Sunday school meeting, Billy Graham gave his life to the Lord, right? He decided that he's going to serve God. Now, this old man just continued to pray for him, all of that. He died and he went. But we see the impact of what Billy Graham has done. What happened? This old man just by inviting this little boy to accept the Lord Jesus, millions of people were touched by his ministry. So you and I, we never know who we are impacting. The problem is we make judgment from the outside, right? Oh, this person, I don't think he can do much. Or this person, I don't think he can do much. But that's not what the Lord Jesus did. The Lord Jesus did not look at Peter and say, Fisherman. No, no, no, I need some well educated people in my team. He looked at Peter and he said, you're going to be the rock. So God does not look at our weaknesses. He does not look at what we are failing at, but he looks at what we can be. And that's the same attitude we must carry. When I look at people by ministering the gospel, I must look at them. Hey, maybe this person one day can be a great songwriter or a great musician. Or maybe this person one day can be a great pastor or he can be a great evangelist. Touching many lives. So what you have done, you've done your part. So on the seed, God is going to make it fruitful. Amen. Paul is writing to the Corinthians.  But it is God who makes it grows. Right? If you sow, somebody else will water, but your reward is there in heaven. Amen. So you'll be rewarded. Every person you minister to, there is a reward. Your administrator may not have said very good job. Your teachers may not have clapped for you. Your friends may not have clapped for you, but there is a reward in heaven. Right? So with that attitude, we can minister to people. Right? Okay. John won 43 onwards, 43 to 51 extending an invitation to one who's doubtful. Let's read that 43 to 51. Thank you, Vimal. Right. So we see another beautiful encounter here. Philip, he meets with Jesus. Again, same thing. He goes and finds his friend, Nathaniel. And he says, Nathaniel, come. We found the Messiah. Now, Nathaniel, in the first case, Andrew found Peter. Peter was not skeptical. Right? Simon Peter was not skeptical. He was not in doubt. He just said, okay, come, let's go. But yeah, Nathaniel is saying, can anything good come out of Nazareth? No. Right? I don't think, what are you talking about? Right? Now, here's the interesting thing. Philip, he did not try to start a debate and try to convince him. Right? He did not say, okay, you know what? He was like this. He's tall. He has long hair. And then he spoke to Andrew. He spoke to Simon Peter. And then after that, wherever he was going, John the Baptist also told, you know, he's the Messiah. So why don't you? There was no explanation. What did Philip say? Three words. What was it? Come. And see. That's it. Three words. What did Jesus say? Come and see. Right? So you see, sometimes in evangelism, it's not only about speaking, but it's also speaking the right words. The right sentences. Right? That's where the wisdom of God lies. And now Nathaniel, he comes. Philip said, come and see. What I saw, I'm telling you. But you come and see. You're doubtful. You come and see. And so Nathaniel came. And Jesus begins to reveal through word of knowledge about Nathaniel. I saw you under the fig tree. You were praying under the fig tree.  Nathaniel says, you are the king of kings. You are God. He believes in that moment. And Philip do come and see. All that he did was... So both are important. At least Philip went to Nathaniel. Philip didn't go home and say, oh, finally I found the Messiah. So for me, no problem now. I'll go and join him. No. He went and found his friend Nathaniel and said, come and see. So there was an effort. Right? Come and see is a statement that all of us can use. Yes or no? We're talking to somebody. Hey, come and see. I remember this couple of weeks back when we were doing faith and science. I just happened to see a couple of young people near the east of Bangalore. So I gave them an invite. I said, faith and science. They said, no, no, we're not interested. I said, it's all about science or how the world came into creation and how sometimes we need to have faith in that science. And we need faith in God. And they were saying, oh, this is an interesting topic. Can you explain why? I said, why don't you come and see? They came on Sunday. Right? All I said, come and see. Because if I go to explain, you know, the earth was there. The sun is here.  If I explain all that, they'll say, okay. Right? I don't know how to explain the six days of Genesis and all on the road. All I said, let's come and see. Right? You know, when I was in Mangalore, so many, many times, I met this one boy, right? He is a northeast boy in Kohima. So I went up to him. That time the church in Mangalore was about maybe 10 people when I went. I went up to this boy and I said, hey, are you a Christian? He said, yes. He said, you know what? I've just come to Mangalore. I told him, see, I'm part of a church. Would you like to come? He said, yeah, because I've just come to Mangalore. I don't know anyone. It's just a week now. Where is your church? So I gave him the address everything. Then he asked me, what are your beliefs? I said, see, all that will take some time. Why don't you come and see? So he came on Sunday. Right? And after the Sunday service, I remember we were only 10 people in church. He said, can I call my friends? I said, yeah, you can call your friends. Next Sunday, he came with 10 friends. So from 10 people, our church went to 20 people. And those 10 friends started inviting other friends. And later on, I got to know that they were all from a different term. Like they were from the Baptist background. They didn't believe in the Holy Spirit. They didn't believe in the gifts of the Holy Spirit. Now, I didn't know that. I used to do all the gifts. I used to speak in tongues. I used to pray for healing everything. I didn't know that. I just ministered in freedom. But later on, they said, hey, now we know that there is a Holy Spirit and the Holy Spirit still works. We have seen it in our own eyes. Now, if I had gone and explained that day, we believe in God the Father, the Son, the Holy Spirit. The Holy Spirit has nine gifts, you and I as believers. If I'd explained the whole thing, he may not have come that Sunday. So, there's power in a single invite. Many a times, we've had movie nights. I've just said people, why don't you come? Which movie? Come and see. I use the same word. Jesus said it. I also say it. Which movie? The name of the movie is this. You come and see. As this one boy, we played the movie, The Cross and the Switchblade. It's about gangsters and drug addicts and how this young pastor goes to New York City and he begins to reach out, begins to preach to these drug addicts and gang dealers. There's a book also called The Cross and the Switchblade. So, I wanted to play that movie. So, these guys came and we put the movie. It's a powerful movie. But the first one hour of the movie is only fighting and gangs and drugs and all of that. But in the end, when the gospel comes in, it's very powerful. And I was sitting there in the back seat. We were about 25 people with maybe 7, 8 young guys, new people in church. All of a sudden, I'm hearing cries. There was no preaching. There was no teaching. Because of the movie. But then after that, of course, we shared the gospel. But the point was, it was all just come and see. Right? So, maybe each one of us, you'll go back to your hometowns. You'll go back to your churches. Use these opportunities. Ask God to give you wisdom on how to minister to people. If something is not working, try another way. Don't say this is not working. So, I'll better be on the stage only leading worship. No, no, no. Don't say, okay, I'm not called for this. So, I will only preach on Sunday in the church. That is my gift. No. If that is your gift, you do that and you do this also. I can worship for 3 hours. Good for you. But also go out and minister to people. But others can't worship for 3 hours. Good for them also. We don't have to look at what others are doing and what others are not doing. We are doing what God has commissioned us to do. Go make disciples. Amen? So, next one, we already seen that realize the importance and the power of a single invitation. Okay, here, let's look at that. Think of various situations that people go through which provides an opportunity where you can invite them to explore Jesus. One, they're facing a challenge in life. They're asking questions about life, meaning and purpose. Or they're interested in learning and exploring. They're thankful or grateful for good things. And they're open to receiving prayer for some need. So, I like to talk about this. They're asking questions about life, meaning and purpose. In a day that we are living in now, all of us around us have this question, bro. What's the meaning of life? What is the purpose? Why am I living? What is this? What life is this? There was a woman from a different faith who had come to church once. This is again in Mangalore. And she was crying and crying and she was talking to us. She said, I lost my husband. I lost everything. She was so sad and bitter. She tried everything possible. I realized at that time me sharing the gospel is not going to work out right now. I can't just say, okay, don't worry. Jesus will comfort you and give you peace. No. She's grieving. She's lost her husband of many years whom she has loved and now she's alone. She doesn't have anybody in her life and in laws are treating her bad and all of this. So I can't just say, okay, don't worry. Jesus will make everything right. He will but then it's not going to be so much of effect in her life.  Come here. Nobody's going to judge you. Nobody's going to ask you anything. Sit and you go. So she said, okay, I'll come. So first couple of Sundays she came and she would finish service and she would go away. So nobody asked her questions. I told the church also don't ask her any questions. Don't ask her where she's going, where she's coming, all of that. So she gave a couple of Sundays, three Sundays, one month and then I noticed that she would stay back after church. She started talking to people of the church. I didn't say anything. I didn't say, why don't you fellowship nothing. Then I started noticing she's giving tea to everyone. Started serving in the church. Then I'm seeing she's, you know, setting up the chairs, wiping the chairs and you know, many times she's came up to me and said, if I leave this place, the church, I feel hurt. I feel broken. But when I'm in this place, there's something that is different here. I don't, I don't feel pain. I don't feel anything. Right. I feel the peace of God. Right. But we never shared the gospel nothing but this is what she said. Right. And then I was able to use this as an opportunity to minister to her. Right. No asking questions. No asking why, you know, you have to believe in Jesus. No. Right. So there are ways to handle people. Right. So she was asking question about life. She was suicidal. She had no purpose in life. But now she has purpose. She has meaning.  So there will be people who are coming and walking into your churches, into your ministries this way. Do not judge them or criticize them. Don't look at people and say, hey, you're not lifting your hand in worship. What are you doing? No. Right. Believe people as they are. Let them be as they are. Let the Lord minister to them. Right. There are times when we have to share. We have to share our experience but don't force or don't manipulate people. Right. Especially in ministry. Especially when it comes to evangelism. Right. Then you can think of events. You can think of small groups, movies, Sunday nights, Good Friday, Easter, Christmas, all of these Sundays that you can invite people and just say, come and see. That's all they have to do and they can experience the presence of God. Right. Think of various conversation starters. Right. What is conversation starters? What's the meaning of conversation starter? Now, if I'm meeting somebody Right. And I know this person is interested in something or you know, just somebody who I don't know as well have conversation starters. Right. Hey, what do you like to do in your free time? They'll say, I like to read. So you say, hey, you know, have you heard of this book? Or they'll say, I like to play music. Okay. Oh, if you don't play an instrument, you can say, hey, even I like this instrument. Maybe I also should learn. I'm thinking of learning. Right. Or they like to, you know, play football or anything. Right. Have conversation starters. Hey, what did you do when you were young? Right. What was it? What did you do on Sundays? Or we used to get up late and go and play and then, you know, in the evenings we used to have family time. Right. Now, if you ask me the question, I'm hoping they'll ask me on Sunday or Sunday. We used to go to church in the morning.  So you waste your whole Sunday in church. So yeah, it's not a waste, but this is what I do in church. Gives you an opportunity. What is it? Conversation starters. You're not talking about Jesus died on the cross. He rose again from the dead. Nothing. It's just conversation starters. Simple points. Right. That was this one person. It started off. You won't believe this. One person, one of my friends. Right. He loves geography. Right. Geography in history is his thing. Right. So he would always say, one day I want to go to Europe. He used to always tell me that I want to go to Europe. I want to tour Europe. Okay. How do I get this guy? When he was reading the book of acts everyone are in Europe with it. There's grease there. So I said, so I remember I said, God, how do I cross to this guy? He said, hey, you wanted to go to Europe. No, you should go to Greece. You should go to Athens. You should go to Corinth. What is all this places here? So you haven't heard of these places. So I said, go and get the Bible and come. No, I didn't do that. Okay, I open. I open Google. I said, oh, and I purposely put Corinth. I said, see these structures. I showed them pictures of Corinth. Beautiful places. We had these huge stadiums where people will watch fights and all of it. All history and geography. We spoke for more than two, three weeks. Only history and geography. I got them fully excited on that. Next thing I said, do you know what happened during those times? Broaden the gospel. Okay. So it was not about Jesus was there. He did this. No, it was simple geography and history. I just bought the gospel. So have conversation starters.  Don't do that. Or sometimes I've seen, you know, they're giving like this scene somewhere else. Where are the cops? No. Why do I talk to them? I don't get scared. I don't give the invite and say, okay, take fast and go fast. Wow. You can do 100 like that, but do one which is fruitful, that's better. That's enough. Thanks. Have conversation starters. And I remember I used to go to these colleges and all I used to sometimes say, now what I'm talking, no, why I'm saying all this is because I've done it. It's not like I'm just saying because I want to say it. This is the fourth or fifth year I'm teaching this. You know why? Because I've done it. I used to do a lot of evangelism. So what I'm trying to get at is you know, have these, when I was in college, when I'm outside college say, hey, what exams are going on? Now they're not going to say, no, who are you? Don't talk to me. Will they say that? Will they say that? No, exams are going on. You say, yeah, yeah, exams. Which subject? What's your course? I've taken BBM. Oh, BBM, I've taken BCOM. So you have marketing management around? You're just talking, okay. And so you've got two minutes, the first 30 seconds counts. So he's going to stand and listen to you. Say, hey, you know what? If you've got two minutes, can I take two minutes of your time?  But don't go home and keep crying. Okay. Do something about it. Go to the next person. Right? Continue. Okay. Yes or no? Okay. So it's okay. It's okay to you know, not be successful at times. It's okay when things don't work out. Don't cry. Crying is for babies. It's not a grown up. Okay. Right? If things don't happen, also move on. Look at yourself and say, okay, where does God want me to go from here? What should I do next? Right? Crying is not going to resolve the problem. You'll only get tissues. That's all. But the point is, are we growing in the Lord? Right? So that's what we want to see. Inviting people, there are so many ways. But what holds us back? Inhibitions also. Sometimes we are too conscious and we don't invite people. Remember that you're not inviting people to yourself or inviting people to Christ. Sometimes we may face rejection. They may say no. So then we don't invite people. Oh, this is very nice. Sometimes we perceive things differently and we compartmentalize our life. Isn't that true? We make our life into compartments, Monday to Wednesday by a BC student. Thursday and Friday, some other student. Saturday and Sunday, some other student. No. Who you are is who you are. Let people see them who you are. And so when you're genuine about something, that's when people will receive you. People will accept what you say. If you say, okay, hey, I saw you.  But last time I saw you, you were involved in all those fights over there or you're involved in all these things. What did they say? Hey, that is Sunday, I'm a church. That is Monday.  I've seen you. That is on Wednesday. Sunday, worship leader and prophet. Both I am. Don't compartmentalize who you are Monday to Friday should what you should be Saturday and Sunday. Okay. Yes. Right.  You don't have to prove anything to anybody. The moment you prove trying to prove something, it's already a failure. You are. This is who I am. This is what I will do. Now don't say this is what I will do and then stand there and do nothing. Okay. You need to grow. Right. You need to develop yourself. Right. But be genuine in what you're doing. Right. Jesus says, no, don't be like the Pharisees when they when they come to the corner of the road there, only they're praying. And when the people leave, they finish praying. There's no need to show anything. Is what we're trying to get at. Right. When you're genuine, people will notice it. Right. And you have you will gain the ability to speak into their lives. All you need is to show genuine. Right. Sometimes we are afraid. We don't have all the answers. So we don't have. So we don't answer their questions. So we feel okay. No need to invite them. Right. Remember that we are also regular people. We are also learning. And so it's okay. It's okay when we don't know all the answers. Sometimes you're too worried about the church service. What if it's not even faith and science or no, I'll call them for super natural something. Faith and science. Sometimes we think, okay, the service may not be good. But you never know what can touch what the Holy Spirit can use to touch a person. It can be a PPT. It can be somebody who's greeting in the welcome lounge. It could be somebody who's just serving tea. It could be one word in that sermon that has touched a person and can change their lives. So don't feel that, okay, maybe I'll invite them next series or next invite them. And the Lord will do what he has to do. Right. Worship is going to be there. Word is going to be there. And let it minister to people. Right. How do you make the invitation for someone to come to church important? Be simple. Be truthful. Be inviting, not coercing. That means don't force them. First one, be simple. Don't say, you know what, I want to invite you to my church. First we were 10 people. Then from 10 we became 500. From 500 we became 800. We have a big screen behind this video recording also happens. You come and see all that come to church. That's it. Let them see what they have to see. To be truthful. Tell them it's church. Don't tell them it's a club. It's a church. This is what we do. And you be truthful. Be inviting, not coercing.  Make that invitation and explore Jesus to explore Jesus. And then you pray for them. Go back home and pray for them. God, I've given them the invitation. Holy Spirit, you minister to them. You make them come. I'll just send a message. I hope to see you on Sunday, but you make them come. When you do it, things will work. Right. So you pray for them. And finally just two more minutes almost done. Okay. This that last page after they visit to the church, help them to process what they've heard. Maybe it's a difficult message. Help them process that. Help them to connect with the church community. It could be connect them with a small group if they like to serve, help them to serve in the volunteer team. Why is it that all of you are serving in the volunteer team? Not because, okay, you want to do it because it's good to serve in the church. Right. You're getting connected together. Continue to invite them. And if they have made a decision for Jesus, then work with them on helping them grow in their faith. Right. Teach them foundations, worship give them Bible verses, small things that can help them to grow. Is that okay? Right. So even this week, even as maybe some of you may be going. Right. Try that out. Right. Try to ask good questions. Try to be relevant and go there prayerfully. God will definitely open doors and answer you. Right. All right. Thank you so much. Those who are online have a great week. I'll see you next week. God bless you all.