 fairly quick conversation anyways. So good morning, good evening for those of you in Asian time zones. Chris Ferris has been able to make it today so I'll be running it going through the agenda and team of conversation. So why don't we dive into the agenda? Is Rai on the phone? I am, yes. Okay, so I think this has happened but just wanted to make sure you and Bawa are working together to get Cello on boarded into the hyperledger infrastructure and set up with mailing lists and all that. Right, the last remaining item is Jenkins and we're gonna work on that next week. Okay, and we've got a blog post actually that the marketing team is working on that we'll have ready for Bawa's review pretty soon but based on content that came from the amounts and other things. So that should get out early next week as well. Any questions or comments for Rai or Bawa about Cello? We're excited to get started. Okay, Todd do you want to mention the Hackfest or talk about the Hackfest? Sure thing. So the Hackfest February 1st and 2nd in San Francisco, if you have not registered and you're planning on attending please take care of that ASAP. Here is the registration link and then the second part of that we do have a draft agenda which is very skeletal at this moment as they typically have been dropping that in the Google Doc as well. If there's things you'd like to see get discussed if there are topics that you'd like to lead a discussion on please drop them into the proposed agenda items. We'll get those all slotted out at the beginning of the first day of the Hackfest. And then from there looking at the two-month cadence we are still looking at tentatively holding a Hackfest in Shanghai in March right around the time of the hackathon which is around the 11th and 12th. And so if you have space please shoot me a message so we can coordinate on that. And then looking further down the road to continue to plan these further out New York and the May timeframe. So again if you have space in or very near around New York please get in touch with me. The sooner we can get these on the books and everyone can plan for travel the better. Any questions there before we move on? Alright. And I want to add there's a nonprofit that I work with called Benetech that has been working with open source software in the field of accessibility human rights work that sort of thing. And it's been talking with another nonprofit called Humanity United about blockchain technology related projects. They have to make a meeting outside of the at the Letterman Center where we'll be hosting as well. So we're helping them facilitate just a small conversation but if there was any interest in the part of folks planning to attend the Hackfest in talking with a couple of nonprofits about how they might use blockchain technology for social impact let me know. They're looking at kind of a two or three hour conversation on February 2nd and I think if you really fun to make sure that they were well informed about the underlying technology to do that. These two things kind of came up at the same time and it seems rather fortuitous so decided to see if we could facilitate that. So let me know if you're interested in that. So moving on. So there was a conversation last week about the CII security badge. I know Chris is looking at this and looks like we're pretty good on most of the front but I think there are a few things he's following up on. I left this here as an agenda item because I wasn't sure if he had wrapped up conversations that might just be something that we would return to next week. I hadn't seen any updates over email either about this in the last week. We're still recruiting for the security made in position though and I'll mention that in the final agenda item. But I don't know if anyone else had any updates on security bad change or if he's getting that certification. Yeah we took a look from the sawtooth perspective and it looks like most items are covered. I think one of the things that came up for Chris as well was the use of the static analysis tool and whether or not the Linux Foundation would have licenses or the hyperlegion project I guess specifically would be able to fund licenses for tools that would have to run on public servers. Okay, I don't know if this was something that you were looking into? No I wasn't looking into funding the CII tools or the tools to do the static analysis. On other projects we have done that so that I think would just be up to you know the TSC or the project as to whether or not they wanted to allocate funds for that. Okay, well how about Ryan myself and Chris do a bit more discussion about this offline and come back as a future TSC with a plan for this because I the projects do it if it's thing we have access to and can just turn on that that almost seems like a no-brainer. So right we'll come back next week or hopefully another TSC meeting soon. And Mike Nolan in chat just said we need to see the licenses so I don't know if you caught that right. I saw that I wasn't I was parsing that while I was talking so I'll include him in the conversation too. And if anyone has an experience with the new Google code fuzzing stuff or is interested in pursuing that I'd love to wrap that in as well. Kind of interesting. So on to the next item. Right did take a look at the the cost of having our IT organization host Rocket Chat which is an open source substitute for Slack. Ryan I don't know if you wanted to talk a little bit about that or I couldn't try to fill in. Sure I talked to our IT guy Eric Cersei and he said that the price would be he would estimate that we have 350 dollars a month which would include hosting and operations and the actual hosting cost would be passed through to the project budget directly so I don't know you know what the exact month cost are but in the order of magnitude of you know 350 dollars. Is there a sense for whether people have looked at Rocket Chat and feel like it's the it's a suitable replacement you know to have the features people need. I know there was one other another open source alternative called Matter Most I think that people suggested to me. I don't know if we want to look at that. I mean the cost doesn't doesn't strike me as a problem at all. We can afford that. I just want to make sure that you know if we introduce it we're able to migrate people there and off as black. Well one advantage is that Rocket Chat does support CAS which is the the ID system that LFID uses so we would when people signed into Rocket Chat they would be using an LFID which might help ameliorate spammers etc. getting on chat and I'm unsure if Matter Most supports CAS. So I assume that means that we would have the chats archived which would be obviously a big gain from what we have to do with Slack. I believe the answer is yes and I suspect that once we begin the migration I will just go through and disable everyone's accounts on Slack and once we get below some number we could pay the whatever it is $20 a user for five users to turn off the $10,000 message limit and then I could get in and archive the channels and make our chat history available somewhere on the wiki or something like that. So I think we may be able to extract our Slack history and then keep our chat history on Rocket Chat moving forward. That's neat idea. Would that let you retroactively reach back or would it just be whatever that more recent volume was? That is the question I don't know. I'm hoping that they have kept everything from day zero but I haven't tried so shenanigans so I don't know. Hi this is Leonard. Certainly if all the data is archived all the documents are archived we could have an archived agreement to hold everything for a certain period of time if they can't hold it forever. In fact it can be done to some hard drive or some localized service so we should keep everything and it's so we can certainly manage the costs for doing that just by having an archive period where it stays live and available and then after that it gets then moved or done to you know some service somewhere. No a requirement zero should be that going forward conversations get archived and are searchable. I think the question is whether previous conversations that were on Slack what else to be able to be included in that archive and we can we can look into that. Why don't we come back with some answers to that and maybe a TF for approval at next week's TFB migration. Are there any other last questions people would want answered before you know so that we can we can make a decision at next week's meeting? Yeah are there is there like a test environment we can play with RocketChat. Yeah there's a link that Todd provided Rocket.Chat. Yeah I was just meaning do we have I've got the link open I've been just looking at it look it actually looks really good I was just wondering if there's a functioning system up that we can just poke around with. Right the LFIT done an integration for or sub RocketChat for any other project. No we would be the first and we don't we don't have a test system up. I will be given the feature list that's on there it looks really good so thank you for your effort in finding it. Do we know whether that means it's also more usable to everybody around the world including people behind restricted restricting firewalls and the likes? Firewall issues should drop away if it's something that's served from an IP address range associated with the Linux Foundation where rather than from you know Slack so so but one one good piece of news I mean Slack if it was blocked by the Great Firewall currently does not appear to be but there is always that risk that if we're in the same IP address range as other you know sensitive conversations or you know for other reasons that other communities get get that range blocked and we would be affected and hopefully that wouldn't be the same issue with the LFIT IP address range. There's a parallel question about is it usable in highly the high packet law networks and I don't know the answer to that. Maybe right we could see about setting up a test instance from LFIT with the I integration with the ID system and let people log in and touch it before we So based on I I think that's gonna take over two weeks so when I was talking to Eric about this it's gonna take him about two weeks to set up the instance and do the CAS integration for us if we want to go into production and I can't imagine that the timeline is shorter if we want to integration so if we want to you know add two weeks on to getting the production instance up I can ask. Why don't we go forward and have LFIT to get an instance set up and and we'll test it out and and play with it and and if it works we'll start migrating to it if there's still issues we can continue to work through those or talk about alternatives but I think I think support here has been pretty unanimous for taking the next step so you want me to tell Eric to go forward at the approximately $350 a month level and if it doesn't work out we'll just pull a plug. Question mark? Okay I will do that. And then as a community you know we can you know still have the choice if we if we go down a week or two running it on LFIT infrastructure and testing it out if it just doesn't work and we'll pull a plug but if it works then we come up with a migration plan for moving the community office back hopefully with the archives. In my experience as soon as there is a better alternative you don't have to do any sort of prompting for the migration users just storm so I think it will be very short transition. There's links there's you know you know we still see people leaving opening new issues on on github for example when they should be moving to Jira so so it's you know it's doing all that. Great okay the last oh there's a couple more agenda items so Hyperledger is hiring we have opened four open positions there are three different positions one of them is fairly non-technical those still would require some technical expertise but the member ecosystem manager this is somebody to kind of just think about the relationships we have with our members but also the broader business community and bringing them on board but the two more technical positions are the community architect and security maven and so we can provide the link to it we actually made a blog post about it we've been starting to drop it on social media but I would really love the TSE's help in recruiting for this position because these are people you'll be working with pretty closely I feel pretty strongly they should be people from your networks they don't have to be people who already are touching or working on Hyperledger but I think I think you know the kind of personal connections that that you know somebody that you know and you trust and referencing them in that's going to mean a lot to me so if you could spread this through your networks retweet or tweet do those sorts of things that would be extremely helpful all four of these positions are full-time on Hyperledger as well which will be a really huge gift for us and help all of us on this side of the scale and yeah the other thing I'll add those positions you know we have a preference for people who are based in San Francisco New York or London but that's not a strong preference my stronger preference is the higher high quality individuals you know who are able to do what we need and we can work with them no matter where they're based so so please if you know people who you think would be appropriate encourage them to apply so just a few more items so we had talked about asking the working groups to deliver by I think it was by this meeting working group charters basically so we can understand do we have the right mission for each of these working groups is there perhaps a need to to re-address or revisit some of them the identity work group provided a draft thank you to them and I know you know the white paper working group is working really hard on hard has been leading that to create to work on its white paper which has been you know really beneficial I don't want to drop this I think this is important work to do but I know how loaded people are should we should we come back to this in a week in two weeks and try to get at least drafts from each of the working groups and what more might we want to do to encourage that oh heart did send a charter up I'm sorry no I did miss that thank you thank you in the technical working group China I think it was about our Victor I can't remember sent one out last night as well so conceivably we can compile these in and hunt for the last three or four or so right I'm Ram Daggadish in here we have a draft going in architecture work group as well we discussed it in the last meeting I haven't repomitted it to weapons template I will do that and then share that as well okay great in his own leg on the call okay I'll I'll reach out to him separately then and see see where he might be on that great well how about over email we start the conversation about about these drafts and and then do a check-in at next week's call and then maybe aim to have kind of a formal adoption of them in about two weeks ish does that seem about right sounds good to me okay and yeah and I don't I don't think we had a protocol working group or if we did it wasn't predated my time so I'm wondering I mean it or is that alive and I just I didn't know about it if it's not alive you just drop it from this was okay it seems oh business business in charge according to the pin I will guess quickly protocols for all all times of protocols or what does it specifically relate to and that protocol wouldn't I see the sign Ben's name to it I just wanted to know the swimming types of protocols it's any any protocols and standards that you use them have ledger I don't know okay so this is backfinding okay we'll do it I'll hope it's been offline see if the group is still alive if not any interest in it or just it seems something the architecture working group might be interested in or might be aligned with what it's working on or the way yeah I've said you so far I think Brian the protocol work has been under the fabric project so we haven't quite bubbled it up to a general you know overall architecture work group item though I think it probably deserves to be done there we want to address the basic architecture first before we go to the protocol in the architecture work group but I think it makes sense when we are ready to address it that hyper ledger project level as opposed to a fabric level it makes sense to move it to the architecture work group okay great and then is the fabric SDK working group really just synonymous with the maintenance ship of the fabric SDK SDK project we just roll that over to being about the same thing at the other maintenance ships are on these other projects or was there a specific reason to have this be a cross-cutting working group okay okay we will I'll look again at the history of that in the in the decisions here and see should we just either adopt a formal thing or just know I presume was that by while leading that fabric SDK working group or was it someone else well Brad actually interested with the to do the work however I already did the charter design of the China so maybe we can dominate like in all gene to do the work I think I think I think what I'm exploring here is whether it's actually a working group or even but really just the the maintainers around the fabric SDK project and something that we can we can declassify as a cross-cutting working group and instead just say no that's the the project specific maintenance ship like every project so I think I think you're off the hook okay okay okay with the garbage collection doesn't doesn't hurt cool okay and then two final points one is you know Chris had mentioned this in email but you know we'd really like to see each of the individual projects doing a monthly update the timing that would work best in coordination with the newsletter that we'd like to push out at the end of each month and other processes is to ask for roughly the third TSC meeting and we'll send a reminder out to to prompt people for this but and it doesn't have to be long a paragraph or you know three four bullet points to be fine but this is really useful as a tool to be able to disseminate knowledge about your projects to the broader world and to attract new developers and to remind people there's momentum and and just you know get some of that cross-project kind of discussion going as well so I just want to plead again for that and hopefully at the next TSC call we could be reviewing that set of monthly updates from each of the projects any any comments on that or or further thoughts. Brian this is Zippin just mentioned that any actual implementations should be mentioned and if you know if they are available to be the details of any such implementations are known it would be great to get a look at them. Absolutely in fact separately one thing I'm talking with the our marketing team here and has been brought up in the marketing committee calls is the prospect of a of a pilot and production tracker on the site basically a place where when people ask okay who's actually using hyperledger related code somewhere out there in the big wide world we can say why here here's a big list and it doesn't have to be you know sensitive details and it can't be obviously but it hopefully is such you know company X launches a pilot based on hyperledger with companies Y and Z for you know trade finance or something like that and so that kind of list is going to be a challenge for us to come up with out of the air what we really will need is the technology community helping us track this and understand you know where these are being used so that we can make that list as comprehensive as possible so when we're ready to launch I'll follow up here on the TSE call but again and work that out. Well I think that would be one of the responsibilities for our new community director it's hard to do communication and provide map level of understanding accountability so yeah I'm happy to wear things if that's the best. Any other thoughts about the monthly update? Okay and then finally just a reminder if any of you are interested in serving as a mentor for our internship program please let us know we're still putting together the program but it should more details about this will be coming up pretty soon. And Todd this is Leonard if you're on I did last TSE I would like to so please keep me on and involved. We'll do we're tracking on everyone that's reached out to us and we will share that with the TSE once we have the details finalized or near final as well as on Slack and whatnot so everyone will be in the loop. Okay great any other last-minute topics anyone wants to put on the table well I'll be really excited to see all of you as many of you as possible in San Francisco at the end of this month beginning of February. Just a reminder there's also construct happening at a Stanford blockchain conference happening the Thursday Friday before so it'll be a pretty active week out here if you need justification for travel budget certainly there let me know if I can help with that but otherwise thanks everyone and hope to see you around soon. Well thanks everyone have a wonderful day happy new year to everyone again. Thank you bye bye.