diff --git a/committee-steering/README.md b/committee-steering/README.md index 9c97b688..01e570af 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -28,7 +28,7 @@ The Steering Committee is a special SIG that periodically evaluates the list of | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/012-2024-01-25.md#transcript) |[Link](https://uh4qrdp5wsvzihnnh7m7conzwkllrei4xawnfsohgjmp5qpjberq.arweave.net/ofkIjf20q5QdrT_Z8Tm5spa4kRy4LNLJxzJY_sHpCSM) | Thursday, March 7th, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/013-2024-03-07.md#transcript) |[Link](https://aqjulyegruxs4xdwltfkkxqieagkmqc7dcbewovdw2wk7tj72hka.arweave.net/BBNF4IaNLy5cdlzKpV4IIAymQF8Ygks6o7asr80_0dQ) | Thursday, March 28, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/014-2024-03-28.md#transcript)|[Link](https://4wprt5kys3oxjr7ihtu2jgx6mshwts7gzsiv2pfr4qypgrp2xywa.arweave.net/5Z8Z9ViW3XTH6DzppJr-ZI9py-bMkV08seQw80X6viw) -| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) | Coming Soon |Coming Soon |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) +| Thursday, May 02, 2024 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/015-2024-05-02.md#transcript) |[Link](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) | Thursday, June 06, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, June 27, 2024 11:00 AM PT (Pacific Time) | | | | Thursday, July 25, 2024 11:00 AM PT (Pacific Time) | | | diff --git a/committee-steering/meetings/015-2024-05-02.md b/committee-steering/meetings/015-2024-05-02.md new file mode 100644 index 00000000..c930b276 --- /dev/null +++ b/committee-steering/meetings/015-2024-05-02.md @@ -0,0 +1,450 @@ + +# Akash Network - Steering Committee - Meeting #15 + +## Agenda + +- Review / discuss / address any community feedback, grievances, or conflicts. +- Review [projects list](../projects-list/README.md), prioritize / add / remove if necessary. +- A look at open discussions in [Github Discussions](https://github.com/orgs/akash-network/discussions). +- Open up to any other questions from the community. + +## Meeting Details + +- Date: Thursday, March 28th, 2024 +- Time: 11:00 AM PT (Pacific Time) +- [Recording](https://s7ymsn3qwdtyyfd5tyjshf4r7a5ticrqhgf7nzpllkmf76gnqmpa.arweave.net/l_DJN3Cw54wUfZ4TI5eR-Ds0CjA5i_bl61qYX_jNgx4) +- [Transcript](#transcript) + +## Committee + +- Anil Murty, Overclock Labs +- Artur Troian, Overclock Labs +- Greg Osuri, Overclock Labs +- Scott Caruthers, Overclock Labs + +## Participants + +- Andrew Gnatyuk +- Anil Murty +- Artur Troian +- Cheng Wang +- Deval Patel +- Dimokus +- Henrikas Ragickas +- Jigar Patel +- Joao Luna +- L +- Maxime Beauchamp +- Nick Merrill +- Robert Del Rey +- Scott Carruthers +- SGC | DCnorse +- Tyler Wright +- Zach Horn +- Zeke E + + +# Meeting Notes: + +* Tyler talked about the change in schedule for the Steering Committee over the next months +* Tyler went through the agenda for the meetings. The agenda can be found on the Steering Committee readme. +* Tyler asked if anyone had any issues related to sigs and working groups? Tyler mentioned that Discord events has bugs. The source of truth for all sigs and working groups is on the Akash Website: akash.network/development. +* Tyler moved to the second agenda item for the projects list. +* There are two project boards. One for Community + Marketing and 1 for Product and Engineering. + +### [Product and Engineering Board / Community + Marketing Board](https://github.com/orgs/akash-network/projects) + +* Akash Mainnet 11 Upgrade happened right before the Steering Committee meeting. This has been released and the network is on v0.34.0. Artur discussed issues that we solved with the Mainnet 11 upgrade including improvements to AUTHZ and Private registries for deployments. All documentation is up to date and available at akash.network/docs +* Console is working through a private repos issue on the client, but that should be resolved soon. +* Artur talked about the Cosmos SDK migration. Discussions are ongoing about which version to upgrade to (v47 or v50). +* Tyler mentioned all the work the core product team and core engineering team is doing on adding items to the backlog for the roadmap. There are a number of items that the core team will be working on over the rest of the year. +* Tyler talked about the Praetor team, and the work that they have done since joining the core team. Praetor will be open sourcing their repos, and this will be shared with the community. Deval mentioned that the Praetor team has added issues to the Product and Engineering Roadmap. Deval and Jigar are also working on testing for K3s Provider Build process. +* K3s Provider build testing has been on going with members of the community, Praetor team, as well as the core team. The goal is to greatly improve provider stability and make the provider build process +* SGNorse asked a question. +* Scott talked a little bit about the Provider build process. The provider build process improvements is designed to be significantly easier and faster. This has been used internally to spin up clusters for testing, etc. Historically this took closer to an hour to build a provider. +* Scott mentioned that testing is on going for K3s in multi node environments. This is the last testing. If anyone wants to get involved in testing, please reach out to Scott or Tyler. +* Deeper discussion on these topics happens during sig-provider. +* Cloudmos refactor and rebrand has been ongoing thanks to all the hard work from Max B and Max C. The refactor work is almost done. There will be a larger plan for the rollout. If anyone wants to get involved in early testing, please reach out on Discord. +* Tyler asked if there was anything that the community wants to talk about related to the Product and Engineering Project Board. Milestones are also available for tracking projects on the core product and engineering sides. + + + +#### [Community and Marketing](https://github.com/orgs/akash-network/projects/6): + +* Tyler talked about Akash Accelerate 2024. Livestream and A/V teams have been worked out. Akash Accelerate is May 28th, 2024. Swag is also being ordered. A number of speakers have been confirmed, and updates will be made to the Akash Accelerate 2024. Adam will be organizing watch parties happening around the world. +* Consensus 2024 will be following Akash Accelerate. Designs for booth have been finalized. +* Tyler talked about the Akash Hackathon. May 17th, 2024 is the last day for the Hackathon. Link available here: +* Robert mentioned that there are weekly workshops for the Hackathon. Scott C, Anil, and Secret gave workshops during the Hackathon. There are a couple of more workshops happening. +* Andrew G asked about Dorahacks and their 100% fees. +* Cheng chimed in that fees are used for operating and paying out the prizes for Akash Hackathon. Andrew mentioned that Dorahacks is delegating to jailed validators. Cheng will make sure this gets followed up on. +* Robert talked about Zealy. The 3rd Sprint started. Robert shared some insights about the wg-zealy campaign over the last 3 months. Shared screen starts at ~ 30:00. +* Robert is thinking about ways to retain members after they finish missions. Robert asked for community feedback on how to get users from Zealy to other groups on Akash. + + +### Github Discussions: + +* Tyler talked about Github discussions at a high level. +* Tyler talked about GitHub discussion 562. Anil gave some feedback. This will get added to the Product and Engineering Roadmap. This discussion has been on going in sig-clients, and in multiple GitHub discussions. + +### Action Items: + +* Cheng will follow up on Dorahacks, and how they are staking. +* Cloudmos to Console refactor and rebrand should be live soon. +* Akash Hackathon closes May 17th, 2024. +* Akash Accelerate 2024 is May 28th, 2024 +* Consensus 2024 is May 29th, 2024 - May 31st, 2024. +* Tyler will follow up with details for bug program. +- Tyler led the group through the agenda and asked if anyone had any comments or conerns about the open structure. + + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: All right, welcome everybody to the steering committee monthly meeting of today is 2nd. Again. This meeting would normally take place the last week of April but due to just the next couple of months and how busy they are. I moved this meeting to again the beginning of May that we're having right now, and then the next steering committee will be again the first week of June following consensus 2024, which we'll talk a little bit about later. much. Appreciate everybody that's joining us today. And again everybody that's going to be listening in later. I know it's been a very very busy period with a lot going on in the community. + +Tyler Wright: I'm going to get us started with our typical agenda. So again, all steering committee notes transcripts and recordings can be found from previous meetings and read me in the readme table. there is a public Link in the drive that anybody has access to for the most recent. Recording for the last steering committee, but are weave is who we use to manage. These recordings has had a surge in pricing and so we'll have that up very soon. But if anybody needs access in the meantime to the previous recording again, you can access it on the drive or you can reach out to me, but that should be up in the next two days or by Monday the latest. + +Tyler Wright: Again, we have a typical agenda that we go through where we start with reviewing And discussing and addressing any Community feedback. Then we go into reviewing of the Project's list. This is where we look at the community and marketing as well as a product and Engineering roadmaps, which are all again publicly available and GitHub. Following that we look at any GitHub discussions where we focus on discussions that have a lot of comments and we focus on discussions where participants from that discussion are currently here at the meeting. So again, there's a number of criteria for how we determine which discussions we will discuss though. That will be a focus of the steering committee. + +Tyler Wright: So again following that then we open up to any questions. I would ask that we follow that structure because I know a number of folks might have updates or comments concerns. But again, we'll just go through the agenda at the structured and then if anybody has anything they want to discuss we can save that for the end. Anybody wants to drop any additional items that will have during open discussion. Feel free to throw those in the chat and then we'll note them for later. + +Tyler Wright: So to get us started with the typical agenda. I want to review and discuss and address any Community feedback or grievances are conflicts. Does anyone on this call have any issues related to the cigs or working groups or the community in general that they want to discuss? + +Tyler Wright: Boom, I raised my hand for myself. The one thing that I've been looking at over the last couple of weeks is the Discord events. I know that there's been feedback from the community about the Discord events breaking. I do want to make it clear that again the source of Truth for all cigs in working groups is the Akash website on the development section. There is a calendar where you can track all the six and working groups and you can actually add it to your calendar and track these on a weekly or monthly basis one thing that I'm trying to work out is how to improve or how to use a Discord events again, it's very very buggy symptom number of support tickets out to Discord. I know a number of folks in other communities are having going through the same issue. So that's one thing that I'm trying to improve on so that folks clearly are clear about when + +00:05:00 + +Tyler Wright: Meetings are and again are not solely reliant on events. When sometimes it works seamlessly another times. It just seems to break for no reason whatsoever. So if anybody has any comments or feedback, feel free to send that to me. But again, we'll continue to find ways so that it's very very clear on where and when cigs and working group meetings are + +Tyler Wright: Any other discussions or any other feedback around the cigs and working groups that anybody wants to share right now? + +Tyler Wright: + +Tyler Wright: All right, moving along. The next part of the agenda is around reviewing of the projects list you can this is a version that we tracked the previously but if you go to GitHub and then you go to the project section, there are two project boards that are public these get managed and maintained by members of the community and the core team on a daily basis. So again, you can get real-time views as to what's going on in the community both on the engineering and product side as well as a community and marketing anything that again the community is working on or the core team is working on you can track where it is and whether it's in backlog up next or completed. So again, feel free if you have any specific items that you want to discuss between steering committee. So just in the community look at the road Mac and roadmap and feel free to ask questions or + +Artur Troian: All right. Yeah, so we have completed successfully Network upgrade… + +Tyler Wright: feedback I know members of the community team are double booked for today. + +Artur Troian: which stands our house the options For the deployment deposits in the past… + +Tyler Wright: So I'm going to start off with the product and… + +Artur Troian: what was happening that? + +Tyler Wright: Engineering roadmap. + +Tyler Wright: I know one big item that has been worked on was the network upgrade. + +Artur Troian: Whenever deployment is closed,… + +Artur Troian: the Aussie authorization is canceled pretty much and… + +Tyler Wright: That is something that was in testing. + +Artur Troian: that was sort of bottleneck for my use cases and… + +Tyler Wright: And again, as of I believe a couple hours ago. + +Artur Troian: we are able to find a fix it. + +Tyler Wright: There was a successful Network upgrade. + +Artur Troian: So this is live,… + +Tyler Wright: Thank you to all the validators that upgraded the infrastructure. + +Artur Troian: please enjoy using that there was one more feature related to the providers that we now support private registries. + +Tyler Wright: I'll hand it over to Scott or Artur to talk a little bit about where we are here today and… + +Artur Troian: So pretty much… + +Tyler Wright: some of the next steps. + +Artur Troian: if I need deployment needs to access product containers they can do so. + +Tyler Wright: But again that is been moved from testing to release as it is now live and… + +Tyler Wright: we are on version zero Dot 34.1 + +Artur Troian: All of the documentation and… + +Artur Troian: updates to the console as well as how to deploy it using the CLI. I believe available. There is one issue on the console which is a style mentioned is being fixed right now, and we should have these be on the production. Pretty soon like an hour or so. + +Tyler Wright: Thank you very much. another thing that I just want to shout out talking about some of the forward looking work in the backlog section. I know that both the product team and engineering team of developed the roadmap as they think about the rest of the year and amongst those items have started to map out again some of the major projects that folks that both the core team is going to be working on obviously. There's some items that might be broken down into smaller projects and tickets. But again, please feel free to look at this road map and kind of track some of the major items that the core team is thinking about and working on. + +Tyler Wright: One other thing that has happened, I believe since our last steering committee meeting is around open sourcing of prador. I know some of the Prater folks are on the call here today. It's been great to work more closely with them. And I know that they've already started to open source prador again into three repos that you can see and kind of track on the board the ball. I believe you all are on this call. is there anything that you want had is there anything that you want to add again? + +00:10:00 + +Deval Patel: That's out here. + +Tyler Wright: It's been great having you as a part of the core team. And again, the Prater team is actively working on open sourcing again the front back end security So the ball I'll pass it over to you to talk about anything that you're working on. + +Deval Patel: Yeah, so can you hear me? + +Tyler Wright: Yes, we can. + +Deval Patel: Yeah our project consists of three Depots which is security front end and We open source security yesterday. We are going to open source front and back in today or tomorrow for sure. And yeah. + +Tyler Wright: Excellent again, as soon as the open source portion is done and those repos are created then. There will be more projects that will be added to issues. They'll be added as under those Repros that are folks that they'll be working on and folks from the community can also contribute to go ahead Deval. + +Tyler Wright: I think that's a great segue and again appreciate all the work. The Prater team is doing another item that is in testing. But I know that the main debt upgrade has been a high priority is an updated provider Bill process. This is something thats Scott has been working on and has been using members of the community to test this provider build process Deval just alluded to being in lockstep with again the rest of the core team to vet this new provider Bill process. There's a list of items in terms of again. Just betting to make sure it works in all sorts of conditions and edge cases before we take next steps and updating documentation. So if there's anybody out there that is a provider and wants to get involved in again testing some of these new provider build process. + +Tyler Wright: Developed by Scott feel free to drop a note in the sake provider Channel or just providers and again we can go from there. Just saw a message from dcnorse. + +Tyler Wright: Yeah, yeah. So again, these are the kinds of conversations that we will have in sick providers or we can drop specifically in the roadmap. One of the things that I've been urging insiders and everybody in the community community to do is + +Tyler Wright: please participate in conversations. I know I just said this on the Insiders call. So pardon me for repeating myself, but a number of people have very vocal opinions about the Akash Community again, many of those things very positive, but when there's discussions or conversations about pushing the network forward, I would love if people can make those conversations public and respond to discussions. It's a very open Community where people can collaborate and again can take constructive criticism, but it's much better served in a public setting whether it be in Discord or whether it be in GitHub discussions versus me having a translate private messages, so I would urge anybody that's gone opinion about Prater or anything on these road maps to just express it or just get involved in discussions. It goes a long way. + +Tyler Wright: I am Scott. I know we were talking a little bit about the provider build processes or anything that you want to add. I know that you've been pretty heads down this week with mainnet 11 upgrade version anything you want to add about the provider Bill process, which is in testing currently. + +Scott Carruthers: I'm sorry. I'm not sure how cognizant all the members on this call would be to the provider Bill process that were referring to but essentially it's using procedures using k3s and install scripts which literally takes the provider Bill process down to probably about a 10 minute complete build. + +Scott Carruthers: was a + +Scott Carruthers: Maiden invert Don't know. So yeah, as I was saying it literally takes the provider Bill process down to about a 10 minute process. And when I say the provider Bill process that includes persistent storage, it includes if you have nodes with gpus or includes the install of gpus and container runtime environments for gpus and so across all that spectrum is taking it down to a 10 or 15 minute process. So we've been using this six. Considerably internally so during Dev work our term myself and other members of the core team can now spin up. Complete kubernetes clusters and working providers again with all the answer features including IP leases and storage and GPU support in 10 or 15 minutes. So any of those in the audience that are familiar with the + +00:15:00 + +Scott Carruthers: existing Bill processes can imagine the power abandoned spin up a cost providers that quickly so as Deval Mentioned prior I believe that Prater Bill process has been using k3s in production for a cost providers for some time for single node deployment. So all on one scenario where you have collapse control plane and worker nodes and just single provider use but there's been some hesitation and some concern about using k3s and multi-node environments. K3 asses definitely being using more and more Enterprise. Scenarios over the last couple years. I think the prayer team primarily looked at this during their initial development processes a couple years ago. So we're now taking a fresh look at that and as soon as we can have + +Tyler Wright: Does anyone have any questions about provider Bill process or anything pray to a related? + +Tyler Wright: Again, we'll have continued deeper conversation during sick providers. So feel free to join that special interest group or just get involved in Discord between meetings. + +Tyler Wright: I know that members of the Commerce team aren't currently here because again, they're heads down but I do want to shout out the work that the max have been doing in rebranding from cloud most to Akash console again with the max is a part of the overclock core team the cash console will be in the future the pool for folks that want to deploy via you act. So be like again the same experience that folks have been used to with Cloud most but now it'll be open source where there will be ability for more folks to contribute to the growth of console over time. + +Tyler Wright: I know that Rebrand work and refactor work is almost complete where there will be a staging site available for testing starting next week. And then there will be a larger plan as it pertains to the rollout for the console again deployed tool over the next couple weeks. So look out there if anybody wants to get involved in early testing again, feel free to reach out to myself for the Max's and we can get you involved in that when available, but I do want to shout out all the work that the Max has been doing and getting console ready. + +Tyler Wright: Cool again, we can talk about a number of things that are currently in progress that are being worked on by the core team as well as items being worked on by the community, but with the maintenance upgrade happening today, I know that there has been just a lot going on. Is there anything on this board specifically that anybody wants to talk about in more detail today? + +00:20:00 + +Tyler Wright: One other thing you can look at is again inside some of these items and up next and backlog. You can also track Milestones again, especially on the engineering side and there will be more items coming across different repos being added to this product and Engineering roadmap so much appreciate all the work led by again Anil and Archer in this transparency and all the work that's being released. shout out to their leadership and just the community as a whole for all the work that they do. + +Tyler Wright: All right, moving along again product and Engineering grow back has been covered the community. + +Tyler Wright: And marketing initiatives up. I know that there are another number of initiatives that are being worked on right now with again around events. So there's a Kosh accelerate 2024. This gets updated in pretty frequently by Amanda as pertains to all that's going on. I believe that they're in meetings right now. But as of recently and anybody here from the marketing side can correct me if I'm wrong but live stream and audio visual team has been worked out. So again as Adam prepares for some watch parties that will be having around Akash accelerate. There's been serious discussions and follow up that live stream is going to be working and there will be Again Video available following the one day conference swag is in the process of being ordered for the event. So again people that participate live + +Tyler Wright: Or come to the event live we'll be able to leave with branded Akash Network items that they can wear for the rest of the conference and just wearing their General lives. And there's a number of other items for again speakers are being organized and believe there's a speakers will be updated soon. There's been at least five or six confirmed in a number of people have filled out the speaker application looking to speak at our cost accelerate. So again, there's just so much going on a cost accelerator. I do want to shout out all the work that Amanda Adam the marketing folks as well as the partner that we're using for event management is doing as we prep for Kash accelerate. It's gonna be exciting Day on May 28th again, there will be some more updates on in terms of watch parties if you can't be there live or if you can be there live again, there's links available to register for the event. + +Tyler Wright: Both on the back of Akash accelerate will be consensus 2024 which as of recently again, a cash network will have a at Booth design has been finalized. Shout out to Sig design and Dennis for all the work that it had done there and Zach as well for the messaging components and just general marketing leadership. So again consensus will be following Akash accelerated. I believe the 29th through the 31st. Robert if you're talking you might be on mute. + +00:25:00 + +Robert Del Rey: Thank you so much that I always happens. + +Tyler Wright: Hence why the next steering committee will be moved back a week. + +Robert Del Rey: Yeah about the hackathon real quickly. + +Tyler Wright: But again as updates become available and + +Robert Del Rey: We also have in weekly workshops. Some insiders have helped us and… + +Tyler Wright: as things continue to get paid out there will be sheets available to the community to try to track against again the community pool spend for consensus 2024 as well as Akash. + +Robert Del Rey: and yeah, it's got thank you so much. We had Anil last week. We had secret Network talking about their sponsor track today. And next week,… + +Tyler Wright: Accelerate 2024. + +Robert Del Rey: we're gonna have two workshops. + +Tyler Wright: There anything I'm missing out on or… + +Robert Del Rey: So once happening on Wednesday in charge damir chimpa,… + +Tyler Wright: does anyone have any questions on consensus 2024 or classic accelerator 2024 before I continue on with some of these other items on the board. + +Robert Del Rey: Europe plots is in charge of that one. In the next one is on Thursday. So I just wanted to remind that. Yeah. + +Tyler Wright: Thank you Again more updates will I'm sure be happening around the hackathon as we approach the deadline for the end May 17th. So look out for more announcements from Adam and the hackathon team. Go ahead Andrew. Cool. All… + +Tyler Wright: + +Andrew Gnatyuk: Yeah. Hi guys. + +Tyler Wright: I know the hackathon is next up. + +Andrew Gnatyuk: I'm sorry I missed yesterday's economical. + +Tyler Wright: The hackathon has been running I believe for a little bit under a month. + +Andrew Gnatyuk: I wanted to ask this question before. Yeah. Thanks Cheng. + +Tyler Wright: I'll attach a link here. But the May 17th is the last day for the hackathon. + +Andrew Gnatyuk: Just a question about it's not about the door hacks,… + +Tyler Wright: I know a number of folks have reached out to me privately saying they were going to participate in the hackathon. + +Andrew Gnatyuk: but probably about the dura hacks. So I've noticed they had a note on X validator right and… + +Tyler Wright: So again it's getting down to the time of submitting or making your submissions for the hackathon. + +Andrew Gnatyuk: they have a hundred percent fees. + +Tyler Wright: Please follow the Adora hacks to submit… + +Andrew Gnatyuk: My question is this on the time of a hackathon or… + +Tyler Wright: if you see anybody in the community. And again, there's an entire section in Discord for the hackathon with teams that are being put together a projects that are being worked on. + +Andrew Gnatyuk: is this or you can fill me up on this? why do they have 100% fees? + +Cheng Wang: Yeah, I can jump in there for that Andrew. + +Tyler Wright: So again, feel free to get involved in the hackathon believed again,… + +Cheng Wang: It's a good question. Yeah, the door hacks validator specifically is on 100% fees… + +Tyler Wright: there's about 15 days left. + +Cheng Wang: because the fees are used to pay for their service essentially. + +Tyler Wright: So time is winding down to participate in the hackathon with over 200,000 prizes in UST given out an akt Of again,… + +Cheng Wang: And yeah, so the service as well as the bounties that are given out to just all the hack on winners so that … + +Tyler Wright: please feel free to get involved. + +Cheng Wang: essentially the proceeds and… + +Tyler Wright: Does anybody want to talk about the hackathon or… + +Cheng Wang: commissions other that they would collect go to operating running, … + +Tyler Wright: did anyone have any questions about the hackathon before we continue onward? + +Cheng Wang: their entire apparatus in addition to the winnings the prizes that get old out. + +Andrew Gnatyuk: So the purpose included in those piece, right? + +Tyler Wright: Go ahead Robert. + +Cheng Wang: That's right. Everything prizes as well as just kind of running their operations. the cost it takes to run the operation. Yeah. + +Andrew Gnatyuk: It got it. Okay. Thanks. Thanks. + +Tyler Wright: No, appreciate that question And again, that's certainly something that's being monitored front of mine. But it's Cheng mentioned. Yeah, all everything in terms of rewards and all that kind of stuff comes from those 100% fees. cool Go ahead Andrew. + +Cheng Wang: If there's any jail that it should be definitely cleaned up. + +Tyler Wright: Thank you, Andrew. I'll follow up with you offline about that. + +Tyler Wright: cool Robert I know that you wanted to spend a little bit of time giving an update on zealy. So I will hand it back to you to talk about the developer onboarding programs Robert love to hear an update. + +Robert Del Rey: Cured that are and be super happy to give you guys a quick update about the developer onboarding campaign on Sealy yesterday a sprint number three started. This is the third and last spring of this campaign as we requested in the proposal and yeah, I just wanted to show you some quick as stats let you know about the New Missions offerings and what's gonna happen next we're gonna continue or we're gonna disregard this all together. So we're gonna find out if you don't mind I will go ahead and share my screen real quick. + +00:30:00 + +Tyler Wright: Of course. + +Robert Del Rey: Yes, it's just if you don't mind, thanks, one sec. Okay, let me know if you can see it. Awesome. So let's start with the stats. + +Tyler Wright: Yes, we can. + +Robert Del Rey: This is the last three months. I will start saying that we have learned. A lot about Seeley about the community about the submissions and specially Seeley these tool. So the first thing I want you to see is that in the last three months we have been able to onboard. Are 211 new members that does an account the members that came from the first pilot that we did on December and November December. So yeah, the first two sprints we have. + +Robert Del Rey: 211 members so far you can see here on top. these are the quest that people have claim. Some of them are paid. Some of them are on paid so Just wanted to let you know that here in this graphic. You can see the amount of members. We got over time the highest Bull Run. I don't know how to say it was when we started the first Sprint on March. We got a hundred members right away and then slowly but surely we've been able to keep growing I just wanted to share Yeah, we're gonna continue. This is the third month. but what I wanted to share here with you guys is + +Robert Del Rey: not issues, but some challenges that Benji and I are facing and hopefully you can let us know your feedback or what you think about this. So the first one is The retention of the members. over 200 people 300 members sounds really cool. But how we retain those members. It's the question that's on my mind almost every day. I catch up on this course I send messages. + +Robert Del Rey: Sometimes some Twitter Sometimes some Thank you Andrew for your support on Telegram. but Initially, I thought it was gonna be a little bit easier to redirect good talent from here to other groups in a cash. So if you have an idea or maybe some cool Dynamic that we can do to recruit people from Seeley and make sure they do other things on a cash. Let me know some missions we have done are about being a provider on a loy persistent storage on a cache. + +Robert Del Rey: And some other missions those two are paid but that I'm gonna mention now are not paid. One is about making people go to GitHub and open up a discussion. that mission it's on paid, but we just want to Teach people. How is the process whether it's a listing proposal or just a marketing collaboration? There is a process that needs to be followed. So we made that mission about taking it to GitHub. That's the name of the mission. I miss if I can show you to your real quick. That's one. + +Robert Del Rey: It's Another one that it's on paid. It's the Akash Bounty space. We have a channel on this core which is been Super Active. That's amazing. But Benji and I decided to do this as a mission so people can go into here. And see a little context why we're doing this and where they need to go to make this happen. This The one for the bounties is here. Did you say I can't bounties? So yeah people can go here click on the link and see what is in it for them through silly because I know that I noticed that there are some people that are members on Sealy. + +Robert Del Rey: But they're not very active on this core so they might not see when we post something on a cache Discord that is unrelated to silly so through City. They can see more things in case they are not on Discord. I've seen some members that ask question and they're super new they started animation and then they join a cash GitHub. then they join a cache the score to ask their questions. something to think about the last of the missions that is on paid. I believe Zach is gonna like this one. It's Join, the newsletter subscriber here is the type of form for a cash. So if people want to subscribe to the newsletter + +00:35:00 + +Robert Del Rey: They can do it from here. They click on that and Seeley lets me know if people do it and I believe Zach can see if people sign up to that newsletter. These three missions are on paid and we believe it's gonna bring some. + +Robert Del Rey: Different flavors, I guess because we only had paid missions in the past. So during the first month we had lots of tractions because we had more missions but on the second month, we had lower engagement I believe because we try to do harder missions and people were expecting easier missions. So we didn't get much engagement on month number two. So on month number three, we're kind of doing a combination between harder missions and on paid missions. So, let's see how that goes. So, yeah. you saw that you saw the stats then analytics My concern is about retention I know and I already told you about what we're gonna do next. + +Robert Del Rey: In regards on this current campaign if we're gonna continue or not. I'm waiting on till these Sprint ends and Banking and I are gonna have a talk and we're gonna decide if we're gonna continue In the meantime, I'm already speaking with the guys from Galaxy Galaxy. It's another tools similar to silly. However, they're offering is a bit more robust. They offer more ways to create missions and their analytics. Also it's ghosts deeper. This is what I have besides this. I have the missions that people do and the countries where people are coming from which is it's okay, but I wanted more information. + +Robert Del Rey: so yeah, let's see what galaxy offers and in any case what we do anything we're gonna open up a discussion on GitHub and we're gonna share the links and hopefully you can guys join the discussion and let us know what you think. So maybe I said more that I thought I was gonna set but let me know you have any questions concerned regrets or any comments. Overall. You want to share with me? + +Tyler Wright: Thank you, Robert. All Right Moving On + +Tyler Wright: Is there anything else on the community and marketing initiatives that anybody wants to discuss? + +Tyler Wright: They're actually two things. I'll move these up. There was some planning issue yesterday, but around proposal 242 creating an automated auditor with open source. I know that the pi 3 team led by Benji has been working on this they gave an update an hour ago. And I think we'll reschedule a meeting for next week where they can demo. So again, feel free to track what's going on there. And then I know that joao Luna just joined the call Luna discussion a little bit about donating the terraform provider to the cost Network, which will include a transfer of ownership to the Akash Network organization so much appreciate Luna for that. We'll have a discussion at the main upgrade happens where again a member of the core team. We'll just connect with Luna to transfer some keys. But again, + +Tyler Wright: Much appreciate Luna for doing that and I'll add that to the board that's tracked in the community issues. I'll make sure it gets added to the sports of folks can track it. But is there anything else on this board in progress up next or otherwise anybody wants to talk about right now? + +Tyler Wright: We'll do. I saw your message. I'll move it to the product board. + +00:40:00 + +Tyler Wright: All right, if there's nothing else on the projects list, then we can continue on with The next part of the agenda is around discussions. + +Tyler Wright: So again, the GitHub discussions is a place where folks can suggest ideas to talk about things that they want. + +Tyler Wright: Potentially community pool funding for that they want to put on up for a governance proposal or again just general conversations. So what we try to do is we try to gauge discussions that we'll talk about during steering committee around those that are here and those discussions that are getting a lot of traction. I would ask again that anybody that has any thoughts or concerns or questions about any of these items can leave comments in the discussion can upvote but just get involved so that again as we head towards the steering committee's or as we're tracking these things add them to potential roadmap. We're getting Community feedback and Community thought so that would be terrific. I saw that + +Tyler Wright: There was potentially a couple of discussions I wanted to talk about today. I know that there was a member. From the doubtout team that joins Sig economics yesterday and gave a really good update on all the work that they're doing over at Dao down how they would like to work more closely with the cash. He started General discussion with no necessarily called action, but just again discussion for people to get involved in in terms of about down just potential opportunities. So feel free to get involved in that discussion. I know he was here at the beginning in the meeting has been getting more involved in six and working groups. So again, please feel free to get involved in that discussion. + +Tyler Wright: Another discussion that I will just talk about real quick is I know that piyush and the human HQ team have been working with the netted out team to develop a streamline and more automated pipeline for deploying applications and they want to do this on cloudmose or console. + +Tyler Wright: This is something that they've been working very closely with the Anil and the Max's on they have recently dropped in a link to a PR that they've dropped into and they shared that did a demo at the most recent sick client that has something that's going to be added to awesome Akash that makes it easier for people to doctorize and maintain images that's phase one at this plan. I would ask that anybody at once that gets merged. I asked that folks from the community start to mess around with where they see anybody in the community that is looking to deploy on Akash, but doesn't understand the containerization or the docker piece. They can point them in a direction of that sdl and get folks and from the community interacting with it and then getting them involved in this discussion. + +Tyler Wright: but is there anything that you want to add there? I know we're just talking about this and I'll make sure that gets added to the product and Engineering roadmap as well. + +Tyler Wright: oops + +00:45:00 + +Tyler Wright: Perfect. Thank you very much Anil. + +Tyler Wright: I want to make sure again we take time for any discussions that have happened since the last meeting that again are getting a lot of attention. Is there anybody here that wants it to talk about a discussion that they brought forth and they want to hear from the steering committee on + +Tyler Wright: All right. If not, then again, I'll continue to ask people on this call and people listen to this recording later to get involved in these discussions again make your voice heard of something doesn't make sense. That's all right to say that as well because it doesn't push forward the goals of again the cash network. But again, please please feel free to get involved. Especially if you have strong views on any of these items. + +Tyler Wright: Cool, if there's no further discussion that anybody wants to have around any of the open discussions, then we can move on to the last part of the agenda around which is an open discussion. Is there anything that anybody wants to talk about and in front of the steering committee right now or in front of the community? + +Tyler Wright: It's a good question. I know that we have a semi-formal program. I can follow up Andrew with details offline in terms of operational plan for… + +Tyler Wright: Again, I know there's been a lot going on this week with the provider upgrades as well so much appreciated again everybody in the community for staying involved in discussions for being attentive up for updating and… + +Tyler Wright: where you push people what we've historically have had to do is when somebody submits a bug we will have to bet it and in many more cases than not the thing that they are proposing is not actually a bug… + +Tyler Wright: upgrading their nodes and… + +Tyler Wright: but again,… + +Tyler Wright: their again,… + +Tyler Wright: I will follow up with a operational procedure over the next 24 hours so that we can at least push people in a Direction. + +Tyler Wright: they're providers if they have them. Please feel free to stay in tune between meetings by looking at the various roadmaps leaving questions comments Etc,… + +Andrew Gnatyuk: Yep. Thanks. + +Tyler Wright: please if anybody wants to get more involved in the core code base, there's a six support weekly that happens where again members of the core team triage any issues of waiting triage and then we discuss any open support tickets. So if you have questions about an open issue, or if you want to get involved involving an open issue, feel free Andrew. I see your hand up. So feel free to speak. Awesome, are there any other questions or discussions that anybody wants to talk about related to Akash at this time? + +Tyler Wright: again, please feel free to get involved in some of the working groups some of the special interest groups happening over the next month again. Look out in Discord and Elsewhere for more announcements related to the network provider upgrade and next steps there again, appreciate all the work from members of the core team validators providers everybody in the community for continuing to stay in sync and again continuing to work together. So got people representing and passionate about a cost on all continents all over the world. And so it's great to see again folks stay connected and Akash continuing to grow. So appreciate everybody's time and energy today again. I'll follow up with notes trance the transcript and the recording a very soon and draw a follow up with you on that operational plan for those that + +Andrew Gnatyuk: Thanks guys. + +Tyler Wright: Say they have bugs and… + +Andrew Gnatyuk: Bye. Have a nice day. + +Tyler Wright: then we'll just continue to stay connected between meetings. + +Cheng Wang: Thank everyone. Thanks. + +Robert Del Rey: Thanks guys. Stay safe everybody. Bye. + +Tyler Wright: And again, feel free to look at their network website under the development tab in the calendar to stay up to date on all cigs and working group meetings, and please feel free to join. Can I hope everyone has a great rest of their day? Thank you to all that gave updates today and will continue to stay linked up on Discord Telegram and elsewhere but much appreciate everybody. Hope everyone has a great rest of the day. + +Meeting ended after 00:51:21 👋 + + diff --git a/sig-clients/README.md b/sig-clients/README.md index 22aa65e5..62aee27e 100644 --- a/sig-clients/README.md +++ b/sig-clients/README.md @@ -15,7 +15,6 @@ Akash Network Clients are software and services that make it easier for tenants - [Client Libraries](client-libraries/README.md) (for various programming languages) - [Cloudmos Deploy](cloudmos-deploy/README.md) - [Fleek](fleek/README.md) -- [Spheron](spheron/README.md) - [Terraform Provider](terraform-provider/README.md) ## Provider Onboarding Clients @@ -46,17 +45,13 @@ The goal of this SIG is to foster a community around each of these clients that | #11 | Monday, December 18th, 2023 08:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/011-2023-12-18.md#transcript) |[Link](https://msr577epylf5qgo6aexm2xbblsreurfi2pgy5ed5ssdw6ztgkxwq.arweave.net/ZKPf_I_Cy9gZ3gEuzVwhXKJKRKjTzY6QfZSHb2ZmVe0) | #12 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/012-2024-01-17.md#transcript) |[Link](https://75iuscsrjioekyahvk6vad3taa5ikpweibvxs2rf4amjvzvj6gfa.arweave.net/_1FJClFKHEVgB6q9UA9zADqFPsRAa3lqJeAYmuap8Yo) | #13 | Thursday, February 22nd, 2024 09:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/013-2024-02-22.md#transcript) |[Link](https://x5g5djwxzxixepgqsmxl6rupiipshcicdmq5bf2tjac35fjv5f6q.arweave.net/v03RptfN0XI80JMuv0aPQh8jiQIbIdCXU0gFvpU16X0) -| #14| March 27th, 2024 09:00 AM PT (Pacific Time) | | | +| #14| March 27th, 2024 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/014-2024-03-27.md#transcript) | Coming Soon | #15| April 24th, 2024 09:00 AM PT (Pacific Time) | | | -| #16| May, 2024 10:30 AM PT (Pacific Time) | | | -| #17| June, 2024 10:30 AM PT (Pacific Time) | | | -| #18| July, 2024 10:30 AM PT (Pacific Time) | | | -| #19| August, 2024 10:30 AM PT (Pacific Time) | | | -| #20| September, 2024 10:30 AM PT (Pacific Time) | | | -| #21| October 2024 10:30 AM PT (Pacific Time) | | | -| #22| November, 2024 10:30 AM PT (Pacific Time) | | | -| #23| December, 2024 10:30 AM PT (Pacific Time) | | | -| #24| January, 2025 10:30 AM PT (Pacific Time) | | | +| #16| June 25th, 2024 10:00 AM PT (Pacific Time) | | | +| #17| August, 2024 10:30 AM PT (Pacific Time) | | | +| #18| October 2024 10:30 AM PT (Pacific Time) | | | +| #19| December, 2024 10:30 AM PT (Pacific Time) | | | +| #20| January, 2025 10:30 AM PT (Pacific Time) | | | ## Leadership @@ -65,9 +60,9 @@ The goal of this SIG is to foster a community around each of these clients that - Anil Murty, Overclock Labs (@anilmurty) - Akash Console - Greg Osuri, Overclock Labs (@gosuri) - Akash CLI - Joao Luna, Quasarch (@cloud-j-luna) - Terraform Provider, Client Libraries -- Maxime Beauchamp, Cloudmos (baktun14) - Cloudmos Deploy -- Prashant Maurya, Spheron Network () - Spheron -- Jigar Patel, Praetor (jigar-arc10) - Praetor App +- Maxime Beauchamp, Cloudmos (baktun14) - Akash Console +- Jigar Patel, Praetor (jigar-arc10) - Akash Console +- Deval Patel, Praetor - Akash Console ### Tech Lead(s) diff --git a/sig-clients/meetings/014-2024-03-27.md b/sig-clients/meetings/014-2024-03-27.md new file mode 100644 index 00000000..5603cdd6 --- /dev/null +++ b/sig-clients/meetings/014-2024-03-27.md @@ -0,0 +1,531 @@ +# Akash Network - Clients Special Interest Group (SIG) - Meeting #14 + +## Agenda +- Updates from the Cloudmos team, represented by Maxime Beauchamp. +- Discussion on Terraform provider by Joao Luna +- Demos from teams collaborating with the Neta DAO team and Piyush Choudhary. +- Demo by Lukas Meilhammer on his current ideas. + +## Meeting Details +- Date: Wednesday, March 27, 2024 +- Time: 08:30 AM PT (Pacific Time) +- Recording: Coming Soon +- [Transcript](#transcript) + +## Participants +- Anil Murty +- B S +- Cheng Wang +- Envy | Neta DAO +- Fire:ies.ai Notetaker Nicolas +- Joao Luna +- Lukas Meilhammer +- Massv +- Maury De Jesus +- Maxime Beauchamp +- Piyush Choudhary +- Scott Carruthers +- Tyler Wright +- Zach Horn + +## Meetings notes +- **Tyler Wright** + - Welcomed participants to the March 2024 SIG (Special Interest Group) for clients. + - Noted the focus of the SIG on tools built on top of Akash to aid client-facing projects. + - Mentioned a busy agenda with updates from various teams building on Akash. + - Tyler Wright emphasized the importance of active participation and feedback during the demos. + - Noted the lack of traction on Piyush's LLM tool demo from the last meeting, suggesting community disinterest might indicate the project’s limited potential to grow the Akash Network. + - Encouraged attendees to provide feedback to help guide next steps for the presented ideas. + +- **Maxime Beauchamp (Cloudmos Team)** + - Provided a brief update on ongoing projects: + - Working on the GPU endpoint for the pricing page, coming online soon. + - Refactoring the ELBs (Elastic Load Balancers) in the Akash Console. + - Implementing provider monitoring for the new Provider Discovery endpoint, currently rolling out. + - Confirmed recent updates: + - New feature: Deployment details now show the GPU model being leased, improving GPU visibility. + +- **Q&A Session on Cloudmos Team Update** + - Tyler Wright invited questions or thoughts on Cloudmos updates from the participants before moving on with the agenda. + - Acknowledged the busy schedule of the Cloudmos team and their recent accomplishments. + - Encouraged participants to track Cloudmos updates via the project roadmap and engage with the team on Discord. + - Mentioned the regular participation of teams building on Akash. + - Noted a missing presenter but decided to continue with the agenda. + - Introduced Joao Luna to discuss making the Terraform provider more accessible. + +- **Joao Luna (Terraform Provider Update)** + - Provided background on the Terraform provider, developed about a year and a half ago. + - Explained that the provider is stable but underdeveloped, currently using the Akash binary. + - Initiated a discussion to open source components developed at Quasarch. + - Proposed moving the Terraform provider from his profile to the Akash Network organization to improve discoverability and trust. + - Planned to publish the provider to the official Terraform registry under the Akash Network. + - Detailed the next steps, including the open-sourcing of client libraries and improvements to the Terraform provider. + - Emphasized the need for secure generation and configuration of a GPG key by someone from Overclock Labs. + - Offered to assist with the process but stressed security concerns. + +- **Tyler Wright** + - Thanked Luna and opened the floor for questions. + - No questions were raised, so Tyler agreed to coordinate a meeting between Luna and the appropriate person from the core team to handle the GPG key setup. + - Confirmed the transfer process should take one to two days. + - Highlighted the importance of security to prevent malicious access. + - Proceeded with the agenda, noting two scheduled demos from present participants. + +### Piyush Choudhary (Neta DAO Project Demo) + - Introduced himself and the project aimed at reducing friction in onboarding developers to the Akash Network. + - Identified the pain points in the current process of deploying GitHub repositories to Akash. + - Proposed a streamlined process, similar to Vercel, to deploy applications from GitHub to Akash without manual Docker and SDL file creation. + - Showcased a POC (proof of concept) that automates deployment scripts. + - Emphasized that the solution will support multiple languages and frameworks, not limited to JavaScript. + - Demonstrated the automated deployment script detecting changes in the repository and redeploying without manual intervention. + - Mentioned ongoing discussions and proposals for this concept. + +#### Q&A Session on Piyush Demo +- Anil Commented on private repo support being code complete and asked about Piyush's webhooks depending on container image tags. +- Joao Luna asked if the deployed image actively monitors the repository for changes. +- Joao Luna Piyush confirmed that the image checks for updates every five minutes, with plans to use GitHub APIs for real-time updates. +- Scott Sought clarification on the goal of Piyush's solution: +- Whether it eliminates the need to customize an SDL. +- Whether users need to be knowledgeable about SDL as part of the deployment process. +- Scott confirmed understanding of the Docker file automation. +- Scott inquired if the solution also removes the need for manual SDL customization. +- Scott Suggested a feature to auto-populate SDL with appropriate resource settings for AI models, reducing cognitive load on users. +##### Piyush Choudhary: +- Clarified that the solution does not depend on version tags in the SDL. +- Explained that the environment builds are managed by background scripts that handle framework detection and deployment commands. +- Explained the solution's goal to simplify deploying applications from GitHub to Akash: +- Eliminates the need to create Docker files manually. +- The solution manages the deployment process and updates. +- A GUI will allow users to log in with GitHub, select repositories, and deploy without creating an SDL manually. +- Users can see a preview of the SDL, but it is auto-generated based on the repository and environment variables. + +#### Demo by Lukas Meilhammer +- Noted that there were 22 minutes left and handed the floor to Lukas and Maury. +- Mentioned that Lukas's team had been active on Discord, addressing technical challenges while deploying on Akash. +- Lukas introduced their project, a data and knowledge marketplace allowing users to monetize or control access to their data. +- Lukas highlighted key features such as private or public databases, token-based access, and infrastructure for reward distribution. +- Explained the integration with decentralized cloud services like Store J. +- Presented a demo of the platform, emphasizing the user interface for database management and access control. + +**Integration with Akash** +##### Lukas Meilhammer: +- Tyler requested clarification on how Akash is being utilized in their deployment, focusing on practical implementation and related issues. +- Described their current deployment architecture, with different providers handling different components: + - Frontend on one provider. + - S3 storage gateway on another. + - Backend and database on a third provider. +- Mentioned challenges with Docker images and potential solutions. +- Expressed interest in integrating solutions discussed earlier in the meeting to streamline their deployment process. +- Invited feedback from the community and highlighted the need for deployment best practices and clearer roadmaps to reduce friction and redundancy in resolving issues. +#### Maury De Jesus: +- Added details about the current deployment status on Akash: + - Entire platform is running on Akash. + - Database is stored on Store J. + - Frontend, backend, and S3 gateway are integrated with the Akash network. +- Opened the floor for questions. + +**Questions and Discussions on Lukas Demo** +- Anil Murty asked about specific issues faced during deployment and how they were addressed. +- Scott Inquired about the user experience for managing databases on the platform and how Akash improves this process. +- Piyush Choudhary asked about backing up deployments that go down by the providers. +##### Lukas Meilhammer: +- Elaborated on deployment challenges: + - Inconsistent performance across different providers. + - Difficulties with Docker image management and redeployment. +- Acknowledged that the solutions discussed by Piyush might help address these issues. +- Emphasized the need for an API to streamline deployment and update processes. +- Explained that Akash provides a decentralized, scalable infrastructure for their platform, enhancing data security and availability. +- Mentioned that using Akash eliminates reliance on a single cloud provider, thus reducing risks and improving uptime +- Acknowledged the need for regular backups. +- Mentioned they have POC clients and partners looking to launch or update data. +- Expressed willingness to schedule calls for further discussion and technical collaboration. +**Next Steps:** +- Lukas and Maury's team to explore integrating solutions presented by Piyush to enhance their deployment process. +- Community members to provide feedback and suggestions for best practices in deploying on Akash. +- Continued discussions on Discord to address challenges and share updates. +- Tyler highlighted the availability of a private Discord channel for technical discussions with Lukas and the team. + +### Backup and Data Management Discussion +#### Piyush Choudhary: +Asked about solutions for backing up data and whether Lukas' team has implemented any backup routines. +#### Lukas Meilhammer: +- Mentioned ongoing efforts to identify errors and the absence of a backup routine earlier. +- Invited collaboration and technical discussions to expedite solutions. +#### Anil Murty: +- Clarified that the front end and backend are running on Akash, while data is stored on Storj. +- Emphasized the need for regular data backups since persistent storage on Akash does not automatically backup data. +- Suggested implementing a backup solution on their side. +- Emphasized the importance of backing up data from persistent storage on Akash. +- Suggested regular backups to Storj or another solution. +- Offered to connect Lukas with reliable providers on Akash for further discussion. + +## Action Items +- Tyler Wright to set up a conversation between Joao Luna and the appropriate person from the core team for secure GPG key handling. +- Follow-up discussions between Piyush Choudhary and Anil Murty on private repository deployments. +- Lukas Meilhammer and Maury De Jesus to potentially collaborate with Piyush Choudhary on deployment automation and best practices. + +# **Transcript** + +_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._ + +Tyler Wright: A Wright welcome everybody to the March 2020 for addition of big clients. This special interest group for clients is focus on all things related to those that are building clients facing tools on top of Akash. I know there are a number of projects that are being built on top of clients to make it easy for people to use a cash and so again, That allows people added to their workflow. so much appreciated everyone's participation and constant participation during this sig. + +Tyler Wright: There is a pretty good size agenda happening for today. So just out of the last meeting usually during these Sig clients meetings. We get updates from various teams that are currently building on top of Akash. We can update from the cloud most team take Max is here representing that team on all the stuff that they've been doing. Following that update. I know that Luna has been working on terraform provider and put a discussion number 502 which I'll drop in the chat. + +Tyler Wright: To make that more accessibly open source, and so we'll talk a little bit about that. Following that conversation there are a couple of teams that I've asked to join this call to give short demos on ideas that they've been thinking about inclusive Concepts that they've been working on one. Those teams is part of the Dao team working together with piyush and so they have an idea to go again give a high level demo on and talk about and then Lukas who's also the call has been working on some ideas and so he will give a demo as well. So again out of the last + +Tyler Wright: Said clients' meeting. There was a demo given by a Pearson is his team related to an llm tool. There was not much traction on that discussion afterward. So we're hoping that people on this call can participate actively it does not much attraction on idea. I had to imagine that means that it's something that should not be pushed forward because the community doesn't see much need for its Late as it stands to grow the Akash Network. So again the folks that are participating and sharing some of those ideas later today in the agenda are certainly looking for feedback to take necessary next steps. So just want to throw that out there. + +Tyler Wright: So kicking off the agenda. I'll hand it over to Max who will give us some updates from the cloud most team so max feel free to take it away. + +Maxime Beauchamp: It's gonna be a brief update. We are working on a lot of stuff currently. But yeah, we'll be working on the GPU endpoint for the pricing page which will be coming online soon. We are. Continuing our work to refactor the elbows deeply into the cash console. Which will also come in the coming weeks and + +Maxime Beauchamp: a bunch of stuff for provider monitoring for the new provider Discovery endpoint, which is a rolling out as we speak. So yeah. That's pretty much it. + +Tyler Wright: Over the last month as well Max. I know they caught up in the thick of all I think they're working on right now. But over the last month you all have had a couple of new items in terms of how people could view gpus on the clubhouse web app that correct. + +Maxime Beauchamp: Yeah, we released on the deployment detail you can see which GPU model you are currently leasing, which was not possible. previously So, yeah, it's a big Improvement for GPU visibility. + +Maxime Beauchamp: Thanks for the reminder. + +Tyler Wright: + +Maxime Beauchamp: Probably something else that I forgot about just the rush right now. + +00:05:00 + +Tyler Wright: yeah, no, no worries. Again, a lot of the work of the clubhouse team does is on the project road map for the product and engineering team so you can kind of track a number of those releases. The clubhouse team is also quite accessible at Discord a number of channels. But if you have anything related to something you want to build on top of Cloud most or questions specific to Cloud most in general the ecosystem Cloud most channels a great place where again anything that's like an issue currently with the cloud most tool you could drop in there and then an issue will be created inside the + +Tyler Wright: Was repo and GitHub and the Really responsive about solving those issues as well as ideas or questions about the tool anything else. You can certainly ask in that channel amongst many other channels. Does anyone have any thoughts or questions about Cloud most or anything? They want to ask Max about related to Cloud most updates at this point before we continue on with the agenda. + +Tyler Wright: All Again, there are a number of other teams that are currently building on top of Akash every month I ask those teams to join and happy to move this meeting around to accommodate folks schedule. There was somebody that was scheduled to come to talk about status of their project but has not attended quite yet. So we'll continue on with the agenda. as mentioned at the top Luna who's on the call here had previously been working on terraform provider for a while and I think Is talking about making it more accessible for other people to contribute to the growth Luna. I'll hand it over to you and then we can talk about any next steps if necessary to make it available. + +Joao Luna: Yeah, So for those that don't know the perform provider it was about like it and year and a half ago since then it has been. quite stable and one of the reasons and it's kind of ironic one of the reasons that's that stable is because it's not that Developed so at the time there were really no clients. So we use The cash binary in the system and as long as the binary works and the people in the users keep it updated the provider will keep running with no problem. This has some challenges in the maintainability as well. So + +Joao Luna: the discussion that I started is the first step in a series of efforts that will be doing to open source some of the components that we developed at quasarc that make our platform that we're developing possible. But there are also benefit the Frog community and we think makes sense open sourcing the terraform provider is already open source, but it's under my own profile. The idea of these first step is to move it to the + +Joao Luna: Cache Network organization and then as part of the process moving to That official terraform registry, but under the cache Network organization instead of my username. So it will improve discoverability and Trust as users do find it weird to download an official. Let's say package from terraform. That's not under the official organization. So this is a step towards the debt. And then the next steps will be the kai libraries that's been due for a long time. It's just that we haven't had that Focus yet to open source it's a coupled to our project and we've been decoupling and might soon be ready to open source, and then as part of these efforts, there'll be an effort to further effects that are from provider using that client library that we will release + +Joao Luna: so the code base gets overall more structured and better. And these are the three next steps on that list being the first one that donation of the terraform provider and it will consist basically of moving the terraform provider to the cash organization and then some technical stuff to actually publish it to the terraform registry through the GitHub actions. So what we'll need will be to generate a gpg key. I assume this should be done. Securely by someone from the overclock team that will be able to generate this key. I can walk you through the process pretty easy. But yeah, then this will have to be configured in the repository this gpg key and then GitHub actions will automatically + +00:10:00 + +Joao Luna: publish the artifacts into the registry. But yeah this process I'm available to do it, but I think I should have someone from the overclock really lab team. to actually Configure the gpg key securely, so I don't have access and things can be published more securely. and I think this is the overview of that discussion and the further ones that will arrive in the near future + +Tyler Wright: Perfect. Thank you Luna for that context. + +Joao Luna: any questions + +Tyler Wright: Yeah. Does anyone have any specific questions or concerns about next steps that Luna's Outland? + +Tyler Wright: Cool. If not, then I'll set up some conversations and private conversation between Luna and the appropriate party from the core team to handle that. + +Joao Luna: This process shouldn't take more than one day. So just for context what no more than one two days and… + +Tyler Wright: Okay. + +Joao Luna: we can have this transitioned. It's just that it should be done securely because whoever has that private key can publish an artifact and we don't want that key to fall into malicious ends and publish something malicious in name of the Akash Network. + +Tyler Wright: No, that makes Much appreciate that. So I have an action item that again. I'll set up a conversation with the appropriate person to get that handled between meetings. But thank you very much. And if anyone has any questions comments again, it'll be announcement made. What's the transfer is done for people to access and contribute. + +Tyler Wright: Cool, if there's no questions there then we'll continue on with the agenda. Cool. I know that there again two scheduled demos. I see from folks that are currently here. + +Tyler Wright: I will hand it over to P issues been working with the net of Dao team on a project and PSU can share your screen. If you need to I'm hoping that these demos can be as discussed less than five minutes, talk about what you're trying to solve at the highest level again If you have one how this will improve the accost Network and then we can get into more of the nitty-gritty be at some questions because there's many folks on this. Call that our combination of Technical and non-technical. So again, if we can keep it high level and fairly focus with these demos, then we can get into the nitty gritty and questions and elsewhere, but I'll hand over to you piyush. + +Piyush Choudhary: Yeah. Yeah, thanks for the introduction Ty So those who don't know me so I'm pierced from digital. So we have both for official question networks, exactly so we have been exploring how we can reduce the fictions in onboarding the developers on the So one of the major pinpoint in Akash network is to deploy the GitHub River State I click on GitHub onto Akash. So there is a normal process of getting Dr. Files then creating an HDL then going over to Cloud models and depending it over to the cost and also to update the deployment of nakash first even to get abusive getting to work close the image gets belt and then the user have to go to the console again and updated plan and basically so there is a lot of predictions in between the process and applying applications. when we compare this with the complete first ourselves and + +Piyush Choudhary: London Network, so they have a clear pipeline where they can log in with GitHub select a repositories and they have kind of template or you can see the basic steps which takes care of all the requirement process in case of versatile. They use AWS and the sales and they just run all the scripts automatically without worrying about creating the docker files or basically HDL Etc. So this is what the idea is. Basically we are trying to streamline the process of deploying and applications from GitHub without cash without worrying about the dog creating Docker images or writing Industries. So people have graphical user interface on the cloud moves which will have the single features and then we can have the multiple Spirits for example, in case of versus limited to deploying JavaScript libraries, but with our concept as a POC we can do this for python Library. She can do this for JavaScript anything. We just have to write a proper that's behind the scenes that take years that it takes the Frameworks and basically + +Piyush Choudhary: States there of the deployment commands in the loss. So these quick POC. I would like to Showcase and also for more information says can go through the discussions or drop discussion that I have pushed. and I have a quick POC. This is a quick PRC to get around the idea slowly drive and more updates will be sure to the proposals. So I'm going to like them okay minutes, so Let's say so right now we are going to the steel and in the docker image. We have kind of created a scripts that takes place of everything. So let's say if I want to deploy this so this will take some time as it's big. Let's deploy this + +00:15:00 + +Piyush Choudhary: So some instance there are some errors in this as it's a POC but as we work around so it will be more beer. So as you can see this is the documents that we are created in which it takes care of all the scripting detection commands that runs in the locks and whenever also in case of course, right so we talk about the computer whenever we make the changes to the data presentation. I always thought comes in the GitHub that says the deployment has been triggered on Versa and it automatically pulls the changes and deployed onto the worst. But in case of the car it's an animal process. So this will also solve this. So as soon as the genius something push the greater purpose Jesus origin to I learned that the deployment has been trigger on the cloud most or it's Akash and once successful we have a techno. This is all going to be done to get out and if this + +Piyush Choudhary: So feedback Also suggestions are more than welcome. And I hope this will bring solve the major friction that the current system have maybe Act has an additional layer which will solve the deployments of repository from you don't want to a cost and it will also allow to deploy private repositories as well. Likely from GitHub to cost to get So this is a foundational structural that we have made and the drop proposal is also being pushed. for discussion + +Piyush Choudhary: So till this can deploys anyone have any questions. + +Tyler Wright: I know there's a couple of questions in the chat about private repo. I know that that's something that is actually code complete from the core team and is going to live as it's a core feature to the Akash network over the next week or so. But anyway, I saw your hand up Anil. Do you have a specific question or a comment that + +Anil Murty: Yeah, comment was same as what he just said Tyler. So the core team has been working on supporting Data Bridges fees so we should have a discussion about that and see which solution we ultimately take. so that's number one and then the second does Your Web book essentially depend on being able to utilize a tag on the container image. So I noticed in the STL you have a version tag new depend on that + +Piyush Choudhary: so basically the tag it's not dependent on this. So if you check the STL so we have the environment belt. So whatever you say that goes into goes in the environment third and the image that is being assigned as still is nothing but the background scripts that takes care of the detection and also runs the proper commands of detecting the proper Frameworks similar to what versus + +Anil Murty: Got it here. The reason is mentioning that is because we generally don't recommend people use version tags in the sdl… + +Piyush Choudhary: we have + +Anil Murty: because of the way that we have configured kubernetes. + +Piyush Choudhary: so I think there is probably + +Tyler Wright: That's Luna. Did you ever your hand up? + +Joao Luna: Yeah, it's just a quick question. Perhaps I didn't catch that. Super Mario understood what you do is deploying an image, right and that image will be actively looking for it link repository that you have there. and basically Have your application running right that repository running? is Sorry. + +Piyush Choudhary: So you could check that. Yeah, you can continue. + +Joao Luna: Is that image actively looking for that repo? + +Piyush Choudhary: Yep. + +Joao Luna: So when I make changes? Okay, cool. + +Piyush Choudhary: So we have a timeline set right now it's five minutes. So every five minutes check all the changes but as we implement the GitHub API six will be able to detect as soon as The Pusher are being made to the represents. + +00:20:00 + +Piyush Choudhary: As well the demo. I think it's failing for some reason. I think it's building we don't need. As you can see the script. + +Tyler Wright: Anil I know you had it + +Tyler Wright: I'll go ahead to Sorry, I know Anil has his hands up and I'm not really sure if you answered his previous question about versioning, but go ahead and then I'll hand over to Anil again. + +Piyush Choudhary: So as you can see the script was able to detect that it was very clone the reposites and on the appropriate commands. And as far as we explode computer computers also to the similarities. Yeah, but in short it will not be just about The Versatile thing it will be about any type of things like we can also get a pipeline to deploy button applications. for example, right now aawpers uses python libraries a lot, right so we can have a direct a pipelines which can deploy the python based. applications directly from get one to across without worrying about meeting the local fire or SQL. It's Okay, so this is being deployed as you can see I can just go to. + +Piyush Choudhary: Okay, so this is being declared without creating the sdo 5 so as small questions. Right now the image is just for the POC. So this will Is behind this is nothing but a static or wait a script which takes care of all the deployment by clients. It's kind of automated feature. You can say additional layer which acts as a manager which takes care of all deployment pipelines. And as soon as the dates are getting pushed to the reposites, it keeps on if it keeps a watch and then really deploys the thing in the locks. So yeah. + +Tyler Wright: I see anil's hand up and then Lukas following. So no you go. + +Anil Murty: Hey, Yeah, so a couple of questions one is So then would each clients essentially be deploying this along with their images and pointing it to their repositories or how would so that we want clients per provider. So let's say there's 10 workloads running on providers. There were 10 versions of this running or how this work. + +Piyush Choudhary: So basically, of course the 10 version of this will be running. So right now it says deal so instead of STL we will have a GUI. So in the GI, we will have to options login with GitHub which through Earth we will load all the requests into the platform and say it deploy and The children will not be visible to the users standpoint, but behind the scene as Akash Independence completely on their steel what we are doing through GUI is we are just creating the STL. Under the hood with the repositories URLs and whatever you said, so let's say 10 are trying to use the stool. So basically those 10 users will be deploying the 10 SQL files. So yeah, I think that runs your question. + +Anil Murty: Okay, got it. And then you talked about in supporting private Registries is a privateer GitHub repositories as well. not Registries. Where are you passing the auth information to? + +Piyush Choudhary: So basically now all information should be passed into the logs. It's a + +Anil Murty: How that works. So, ultimately how does your specific app get the auth information + +Piyush Choudhary: So basically when you create a login with get a brighter so that through GitHub apis we can all the represents into the platform. + +Anil Murty: always + +Piyush Choudhary: Yeah, so yeah, yeah. + +Piyush Choudhary: Yeah. + +Piyush Choudhary: Yeah, so we got the key as the login with get up through Earth. We get access to the repositories as there are permissions that we can control through GitHub apis. And as this is the best basically is a manager of all the things when it starts running the commands in here so it takes care of the old Logan it can deploy the private depository as well in that way. So we have to research a bit around this as we have just started working on it. So it was just a POC. So as the foundation gets more clear. We will have more clarity on how the things to look. + +Tyler Wright: Lukas, I see your hand up you have a question. + +lukas meilhammer: Yeah. Hi This sounds like it's touching on a problem that we also had there was a unexpected downtime and in some cases. We didn't know why our application was down. So I mean we have the back end in the database in one rep in one provider and then store J Gateway and front and on another provider, maybe generally Our architecture could be reviewed but we also had the problem that the provider had to then actually do some node maintenance and one time in our developer Maury in the call. First of all, we will have to review your project to you. And then we might also want to get back to you or… + +00:25:00 + +Piyush Choudhary: Yeah. + +lukas meilhammer: jump on the call if that's needed. But + +lukas meilhammer: Lovely to hear that private repositories. I mean coming into the priority a little bit of prioritize a little bit more and… + +Piyush Choudhary: simply + +lukas meilhammer: maybe we wanted to instead of deploying the application via cloudmoss. We wanted to just do it via CLI as So it's the console that you are talking about I bet yeah. + +Piyush Choudhary: so I think of course. Yeah, you can continue that I would. + +lukas meilhammer: Sorry. + +lukas meilhammer: No, please and Maury has actually got more insights on that and maybe it's something for another call for more. Let's say special interest group, but let's please get together on that because we were thinking of let's say collaborating on these kind of things. because we're going Into a phase… + +Piyush Choudhary: if shows + +lukas meilhammer: where we want to do a private or even soon a public data of our platform, which is a data management and data curation and moderation platform. That can be used for many things. So one proposal was actually to do a best practice knowledge base on our platform for Akash users in general. + +lukas meilhammer: Then maybe to have moderators actually changing things in the knowledge base. which could be really a documentation and additional one. And generally maybe I would like to showcase the platform. But let's first finish this topic off and I wanted to just say that we're working on a solution. We have a script to redeploy on the app if it's down and we want to automate the process and figure out where exactly a problem. The occurring from to actually maybe just issue and automatically restart containers and all that. So Maury do you have any thing to add right now related to this discussion here? + +Tyler Wright: Before you all go because I want to give you all some time real fast to talk. + +lukas meilhammer: Yeah. + +Tyler Wright: It's either introduce yourselves a little bit and talk about what you're looking to build a pH. I see your hand up. But real quick. Does anyone else have any other questions or comments at this time about? What piyush just presented? + +Tyler Wright: Go ahead Scott. + +Scott Carruthers: Appears to be you bring up the STL again. + +Piyush Choudhary: If so, yeah, give me two minutes. + +Piyush Choudhary: says nothing visible + +Scott Carruthers: Yes, and then can you so let me make sure that I understand the intense. I understand the removal of the need to create a container image. is a solution also trying to negate the need to customize an sdl. Or so I thought I heard that maybe in the beginning in the presentation, but maybe I'm up. So in order for a user to be able to use this service. Will they need to be? Knowledgeable about a Nicolas sdl as a part of this process to negate the need for a user to have to manually manipulate a sdl. + +Piyush Choudhary: So yeah, so I will take on that. So basically what we have done here is in short the image is the steal anything but a step that is acting as a manager deploy the bit of applications from get up to Akash and also running the commands in locks right after closing the equal States now the thing is like + +00:30:00 + +Piyush Choudhary: Users will always be able to see so we have a te So if I go to the templates not downloads. So as you're going right in case of azure, but we have the first to basically manipulate their skills. GUI, and then we can preview the stove right and single case. We will also have the thing right now here the users do they do this with their own images instead of the images. So the documentation it will not be there with our solution because we see the docker images something that is automatically the things so here we will have the GitHub reposition and if they login with GitHub, then they will have the access to basically whichever it was Jesus. They want to learn to a car and then all these things will be like again, I think the memory and then also they can add things and then what will happen is in the preview for the image will be ours that is + +Piyush Choudhary: you solve which is nothing but you can say a script that is taking care of all the things and then We have the GitHub Registries the environment variables related to the bit of the pastries similar to if you go to the person there is a fair to add environment So yeah, this is something that is eliminating the need for the users if they want to deploy the applications directly from GitHub to Akash. Our solution is eliminating the need to basically create a Docker file and then + +Piyush Choudhary: to go through the process of getting your local file and then deploy you don't do a cost by creating SQL file. And for example, whenever we make the updates to the GitHub Webster's creates a new image who either work close or by manual then to update that employment on We have to come here and basically change the image. Tag and then he deploy to update the deployment. But in our case our script is speaking of what's on the reversies as soon as the push has changes it automatically schools the changes to logs and then they deploys the thing about the latest update. + +lukas meilhammer: So it shortens the seconds and eases the updating General and Autumn is basically actually giving us the option to great. + +Scott Carruthers: Yes, I understood the piece of taking the authoring of the dockerfile. So I understood that when I talked about the sdl What I was curious about is this also taking the needs. I understand you could arrive at a club must screen where you can manipulate the sdl and manipulate the amount of resources that you're throwing at a deployment. I was wondering if this was trying to solve taking that cognitive load off of the user as well. So if I was going to deploy a AI model onto a caution, I was using this service that it would automopulate the sdl with appropriate GPU models and appropriate CPU and RAM and storage. Is that part of this or is it just taking off the load of creating the docker image? But the user would still be responsible for authoring the sdl appropriately. + +Piyush Choudhary: So basically we can consider yourself around this I think this is a possible to this daily prefill the resources that is required to plan applications from getting one to Akash. So we have to research a little bit on this right now. + +Scott Carruthers: Okay. Yeah. + +Piyush Choudhary: It was not a part of this but we will do some research together on this. Yeah. + +Scott Carruthers: Yeah, that makes sense. Yeah, I mean it's very powerful just reducing the cognitive load of not having to create a Docker file. So there's a myths value in that in and of itself. I was just wondering if I was also trying to reduce the cognitive load of being familiar with the sdl but understand that's not part of this current version but maybe something that you would Implement and… + +Piyush Choudhary: Yeah. + +Scott Carruthers: Future versions are research there. Okay. + +Tyler Wright: All right, it seems like again it's been great discussion around this. I know next steps are not a doubt team in piyush are gonna put a discussion around this I would urge that people could get involved in that discussion and give feedback ask questions poke holes so that again those teams can answering those cars and make everybody feel comfortable but before taking any other steps beyond that looks like a discussion is already live. Thank you very much. So again, + +Tyler Wright: I want to make sure and I'll continue to share this but hopefully the net a Dao team and piyush can continue to share this across Discord get feedback from members of the community in general Chad and all channels and just continue a lively discussion around this. That would be very impactful. But again much appreciate the time that you took today the work that went into this and thank you everyone for those questions. + +00:35:00 + +Tyler Wright: All I know we only have about 22 minutes left. I wanted to give a Lukas and Maury some time to talk. This is a group and talking to a bit Discord and Elsewhere for a little while and they're a very technical group. That's again building their own Solutions based in Europe. I want to In the platform to talk about some other they've already been deploying on a caution. It's found some issues and again and working to solve those issues. So I want to hand over the floor to Lukas to talk at a high level, about themselves what they're building the advantages to the Akash Network and then we'll open up to questions and get into the weeds. + +lukas meilhammer: Yeah, hi everyone and here in the Juventus touring. No trickle one of our code developers Maury our city hall can join how today but We are basically building and I'm just going to bring it up probably almost directly. We're basically building a data and knowledge Marketplace. We're trying to let the user decide how they want to monetize their data or how they want to give access to it. So whether it may be token holding having an Nifty and basically paying a subscription doesn't really matter too much for us because we are basically building a little bit of instruction infrastructure around this. + +lukas meilhammer: Taking contracts to issue rewards at some point all that. So it's a no-code database built on a decentralized cloud storing the data on store J. + +Piyush Choudhary: let's + +lukas meilhammer: It's been quite a bit of a built so far, but we're slowly moving ahead and We are in the process of actually launching a public or private data or I mean databases can basically be entirely private protected or public so I will just show the platform quickly + +lukas meilhammer: I hope to just gain some attention and get some people on board that want to build with our platform. So. I would say. I'll just walk you through the different top level panels here. You have a profile you can browse users in the next version profile can also be private so that you don't see the actual wallet hash that someone logged into then you have incoming requests for the database so that you can basically add someone's use a hash and give him access that usages something for later. + +lukas meilhammer: And then you have incoming outgoing and you have changed requests because basically in each database, let's just open one up quickly. This is a protected database which basically means everyone can see this page. Everyone can see. The criteria the description everything of the database and there should actually be the data schema down below here. So the data schema is public the metrics on how the platform is used here. We see an error already which sometimes we don't know exactly where it's coming from. And then basically it's more related to its. Hope that opens at least now. okay so I can basically make inputs in this field private with a right click + +lukas meilhammer: And then it's going to appear gray. And for the user that is not the owner. It will just be empty and empty field. you have all the filters that you usually have. You can set up a form you can change the form. So it's basically like an air table on a decentralized cloud with giving everyone the options to monetize the data day as they wish. Tyler you have a question already. + +Tyler Wright: Yeah, I appreciate you showing us this I just want to make sure because again many of these folks on this call are focus on Akash. + +lukas meilhammer: Yeah. + +Tyler Wright: I just want to see where the implementation of their cash network is and I remember you talking about redeploy tools as you were leveraging a car. So I just wanted to make sure we got to that part because I'm sure there'll be some questions and yeah. + +lukas meilhammer: Yeah. + +lukas meilhammer: So I'm not a CTO but let me try to summarize this a little bit. So as I said, we have the deployment a little bit split between providers front banners on one S3 storage Gateway is on the other on another one and the database and the back and is on another provider so correct me if I'm wrong here Maury. + +00:40:00 + +lukas meilhammer: But generally we were facing some problems also with the docker images and all that and we just have to maybe review the solution that was presented here today to figure out whether this already solves our need but going into a public beta in we might want to have that iron out and we're happy to wait a little bit. But generally I'm here to get some feedback ask people on whether they want to build something with us and maybe generally also try to let's say summarize these calls sometimes a little bit because + +lukas meilhammer: there is a little bit of friction and maybe questions that are answered multiple times in the Discord. So thinking about a deployment best practices or maybe even a more let's say open roadmap on what's about to come To just actually not worry about stuff that you don't have to be worried about because there's an update in one week. For example, that was one approach where we thought we can use the platform as it is, but that would of course have to be discussed in terms of what else would we need an API that pulls data from other repositories where you document stuff so thank you for now born in first intro call. This was really helpful and all basically. + +lukas meilhammer: so what's running on Akash, everything is running on a cash and the database is on storage a doll the backend the front end and S3 Gateway for + +lukas meilhammer: For the storage integration that the S3 store there was this code. Yes, please go ahead with questions. + +Piyush Choudhary: Yeah, so I have a question. + +Tyler Wright: Go ahead. Peace. + +Piyush Choudhary: So it's an initiative talk about backing up the deployments that caused town by the providers. So I would like to ask where is that thing going on? And also you talk about you lost all the data and the deployment goes down from one of the providers. So are you obviously teaching the solutions that backs of the data or is it something else? + +lukas meilhammer: My meeting already came out for this but there was no backup routine. we have definitely in the process of identifying the errors somehow or in any way. We are also happy to share the insights. And if there's really something and that you already working on and we were of course to know a little bit ahead of time then when it's uploaded or maybe take some part into the actual definition or scripting or work and then this could all move ahead a little bit quicker and I'm generally a very big believer in decentralization. So happy for any collaboration that pops out of this calls here. Anil + +Piyush Choudhary: Yeah, sure Yeah, so I will bring you upon Discord to see if you can call them collaborate on some things type you're working on and other hand over 200. + +lukas meilhammer: Perfect. No, please let's schedule a call latest next week or so Maury. Do you have anything else to say and before Anil? Maybe + +Maury De Jesus: For now and it's okay. Yes. + +lukas meilhammer: Anil + +Anil Murty: Yeah, so this is cool. And I didn't realize I only heard storage in S3. So I wasn't sure if something was running on So it seems like the front end in the backend are running on Akash and all the data is actually stored on store Jesus. Is that right? Okay. + +lukas meilhammer: And it's only data. + +Maury De Jesus: Yes. + +lukas meilhammer: So there's not a lot of data traffic and all that. I'll just basically forward you because someone was asking me for the provider. I don't think that there's any Critical information just post the whole thing into the chat. Really you quickly know just + +Anil Murty: Got it aakash proba Okay, so I was mostly curious about which providers you're using because I think so. There's a couple of things I don't know if you're familiar, but essentially Even if you're using persistent storage on a cash today meaning stories that person essentially still have to make sure that you back up your data somewhere else. + +lukas meilhammer: Yeah. + +Anil Murty: So whether it's true or just something and there is no really backup solution today that's available and that's potentially something for Either the core team or somebody in the community to look at I've been on our list of things but just haven't gotten to it but it's a very common request that most customers have the recommendation because you implement something on your side backup your data regularly because when the lease closes you lose it. so that's basically so as long as you're backing up the data to storage it should be okay and then + +00:45:00 + +Anil Murty: At least from what I understand today, you don't have active users on this product,… + +lukas meilhammer: Yeah. Yes,… + +Anil Murty: right? It's still in. + +lukas meilhammer: no, no, our puc clients Partners actually looking to launching or updating some data. I don't necessarily see them because they are not shared with me or… + +Anil Murty: Sorry, yeah. + +lukas meilhammer: whatever, but basically if you have a database you can keep it private. Then you make it protected so that people see the data schema you get maybe initial requests for Access and maybe some more insights. + +Piyush Choudhary: just + +lukas meilhammer: Yeah, and then basically at some point maybe you want to put it public because it's got some marketing value what not. So generally, we really happy to also please also add me on LinkedIn. Maybe we can just schedule a call also a deaf call or Tech call for anyone my class interested in,… + +Anil Murty: Yeah, sure. + +lukas meilhammer: Idaho. all that + +Anil Murty: It didn't actually just to preserve time on this call. I'll just have you LinkedIn and we can have a conversation about this and see we can help it in terms of,… + +lukas meilhammer: Perfect. + +Anil Murty: giving you better providers or looking at connecting with providers that have been on the network for a long time and then we're gonna have a user confidence. So you want to talk about your solution there to the greatest. + +lukas meilhammer: If you don't mind, I found a few of you guys on LinkedIn already. I will just maybe make a connect request. + +Maury De Jesus: Try again to connecting in French changing Lukas. + +lukas meilhammer: … + +Tyler Wright: and we also private Channel. + +lukas meilhammer: because the net that + +Maury De Jesus: Is refresh the fish. + +Tyler Wright: We also have a private Channel with Lukas and the team on Discord for admins that we can also talk in so much appreciate. + +lukas meilhammer: Yeah, what we do invite you guys there if it's for technical technically related stuff refreshed refresh this page. Yes. Now it's not so super important. I think everyone gets the platform and I mean eventually on the long run we would really like to rather make it a easy interface just like Google you search instead of websites, you get databases stuff like that. and then maybe you don't have access you still need to request or maybe you perform a quest or whatever how you want to monetize your data and I think with Jesus we will find a way to monetize and I'm really happy to have people meeting their own platform. I'm not really keen on offering white labeled versions of it at the moment just so that our brand and our project just gets more known out there but happy to we're working on the API actually pulling data in so that eventually you could have more like cryptocurrency. + +lukas meilhammer: Analysis dashboards with the market cap updating and all that stuff. Yeah, that's a very common request at the moment because we're in a bull market. So yeah. Yeah, I see that. Yeah. Yeah all good guys. Thank you for the flowers. + +Tyler Wright: this all right. + +lukas meilhammer: up just by the way, so + +Tyler Wright: excellent + +lukas meilhammer: Really? Excellent. I thank you for the time already and happy to invite you all to a group or start some I tell telegram Channel. Just shoot me a message on LinkedIn. I've been sending some requests. I'll just now. + +Tyler Wright: Excellent. All… + +lukas meilhammer: through joao zip + +Tyler Wright: I know we only have a couple of minutes left much appreciate again the demos from piyush and the net a Dao team as well as from Lucas Maury and the folks over at ipal again. We try to take these Sid clients meetings and I will adjust the schedule to make sure that more beings like this are available. But this is a great opportunity for teams to connect with one another for folks to talk about ideas that they're building and still they can get feedback from members of the community and members of the core team as early as possible so that we can continue to push. + +Tyler Wright: Or it's again demand driving usage on the network. Those being the main Theses that again everybody from the community hearing committee and elsewhere is agreed on how we continue to push forward the Akash Network, especially through clients. Cool. Is there any other questions comments or any other discussion points that anybody wants to bring up with just a couple minutes we have left. + +Tyler Wright: If not, then again, I'm sure they'll be following conversations with the ipal team. I thank you for joining. If you have any other thoughts, please feel free to drop them in the Sig clients' Channel, again or one of the other channels but said clients is a great place to put things so that everybody from the community can interact and give feedback because again there's a number of great teams individuals that have been around for many many years almond are very technical and can provide a lot of support So as much can be done in public would be great. But again, we'll continue to have conversations again. Thank you to Pearson that a doubt team if anybody had any feedback thoughts about their proposal, please drop it inside the discussion that will spur more conversation. + +00:50:00 + +Tyler Wright: The community and that's what we're looking to do. That'll help drive next steps there. So please ask any questions even if something seems like it may be a dumb question. Feel free to ask and you'll get clarity from the netted out team in peace and we can continue to push that process forward and as always thanks for the updates Max and all the things that you and the cloud most slash console team are working on there's a couple other teams that again we're going to continue to push to join these meetings. So for those that are new Feel free to reach out to me. If you just want to be added to the meeting every month. Again. There's a number of teams based all over the world that are solving a number of problems. So this is usually a very Lively special interest group on a monthly basis. + +Tyler Wright: All right, I hope everyone has a great rest of their day. Unless anybody has anything else. I'm gonna let you go and we'll talk more online. Cool. Thank you everyone. + +lukas meilhammer: Thank you everyone the pleasure. + +Tyler Wright: Bye-bye. + +Anil Murty: it's kind of + +Piyush Choudhary: more than about + +Meeting ended after 01:04:16 👋 + diff --git a/sig-design/README.md b/sig-design/README.md index 145cd180..c206565f 100644 --- a/sig-design/README.md +++ b/sig-design/README.md @@ -29,9 +29,9 @@ date: 2023-1-09T00:19:20-08:00 | #12| Wednesday, December 13, 2023 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/012-2023-12-13.md#transcript) | [Link](https://une76rieq3cvbtrnjv3gxaw6kbxaay3tnzqsangya2lfe6ionpva.arweave.net/o0n_RQSGxVDOLU12a4LeUG4AY3NuYSA02AaWUnkOa-o) | #13| Wednesday, January 10, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/013-2024-01-10.md#transcript) | [Link](https://zao4urnjuqb6ncx2vacwjuqiyqnucl2ifcfm33blijhw6v6owzla.arweave.net/yB3KRamkA-aK-qgFZNIIxBtBL0gois3sK0JPb1fOtlY) | #14| Wednesday, February 21, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/014-2024-02-21.md#transcript) | Coming Soon -| #15| March 13th, 2024 08:00 AM PT (Pacific Time) | | | -| #16| May, 2024 08:00 AM PT (Pacific Time) | | | -| #17| June, 2024 08:00 AM PT (Pacific Time) | | | +| #15| March 13th, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/015-2024-03-13.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/015-2024-03-13.md#transcript) |[Link](https://nnq3ufkztaw2lqjhzhftmlaxw3rt7c3x6hotvsz7gjm2pf7jbgtq.arweave.net/a2G6FVmYLaXBJ8nLNiwXtuM_i3fx3TrLPzJZp5fpCac) +| #16| April 2024 08:00 AM PT (Pacific Time) | | | +| #17| June, 2024 08:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md) | [Link](https://github.com/akash-network/community/blob/main/sig-design/meetings/016-2024-05-08.md#transcript) |[Link](https://utgdid3tyicjsjmgvznzalfhes33oqqzoytow53oaqvlgg6nbmlq.arweave.net/pMw0D3PCBJklhq5bkCynJLe3Qhl2Jut3bgQqsxvNCxc) | #18| July, 2024 08:00 AM PT (Pacific Time) | | | | #19| August, 2024 08:00 AM PT (Pacific Time) | | | | #20| September, 2024 08:00 AM PT (Pacific Time) | | | diff --git a/sig-documentation/README.md b/sig-documentation/README.md index d4550253..ed17b4ce 100644 --- a/sig-documentation/README.md +++ b/sig-documentation/README.md @@ -29,9 +29,9 @@ The goal of this SIG is to foster a community around the creation and maintenanc | #11 | Tuesday, November 28, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/011-2023-11-28.md#transcript) |[Link](https://na7gjhjowrrxc37tzk76rixczxf4st6b3rjpfjrzktiln7yxuckq.arweave.net/aD5knS60Y3Fv88q_6KLizcvJT8HcUvKmOVTQtv8XoJU) | #12 | Tuesday, December 19, 2023 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/012-2023-12-19.md#transcript)|[Link](https://w3evlgbcqz4g4b4kicipe3gxrblirj4f2czs3eutaibrqrp7xtva.arweave.net/tslVmCKGeG4HikCQ8mzXiFaIp4XQsy2SkwIDGEX_vOo) | #13 | Tuesday, January 23, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/013-2024-01-23.md#transcript) |[Link](https://ggtsa72sjsvu3yph245qmj6zvpy7uyys7jerkj72heitmyoiv2na.arweave.net/Macgf1JMq03h59c7BifZq_H6YxL6SRUn-jkRNmHIrpo) -| #14 | Tuesday, February 27, 2024 07:00 AM PT (Pacific Time) | | | -| #15| March, 2024 07:00 AM PT (Pacific Time) | | | -| #16| April 23, 2024 07:00 AM PT (Pacific Time) | | | +| #14 | Tuesday February 27, 2024 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/014-2024-02-27.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/014-2024-02-27.md#transcript)|Coming Soon +| #15| March 26, 2024 07:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/015-2024-03-26.md) |[Link](https://github.com/akash-network/community/blob/main/sig-documentation/meetings/015-2024-03-26.md#transcript) |[Link](https://7lvvy6qbe6wq3tzg3zl2vbxvamshk5ibb3bi32m6fbt5vwdlonpa.arweave.net/-utcegEnrQ3PJt5Xqob1AyR1dQEOwo3pnihn2thrc14) +| #16| April 23, 2024 07:00 AM PT (Pacific Time) | | | | #17| May, 2024 07:00 AM PT (Pacific Time) | | | | #18| June, 2024 07:00 AM PT (Pacific Time) | | | | #19| July, 2024 07:00 AM PT (Pacific Time) | | | diff --git a/sig-economics/README.md b/sig-economics/README.md index 11ebb393..1f6d5fef 100644 --- a/sig-economics/README.md +++ b/sig-economics/README.md @@ -27,8 +27,8 @@ Meetings happen every [First Wednesday of the Month](https://calendar.google.com | #13| Wednesday, February 07, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/013-2024-02-07.md#transcript) | [Link](https://6rzdyy2kxzn4qpilczq7vdvfd52kxb65rk4cnhor32f4cibhkqmq.arweave.net/9HI8Y0q-W8g9CxZh-o6lH3Srh92KuCad0d6LwSAnVBk) | #14| Wednesday, March 06, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/014-2024-03-06.md#transcript) | [Link](https://l7relb4v4vhxhw4shqui4iyoyyeqdt6ogwpx2thybmneridemfnq.arweave.net/X-JFh5XlT3PbkjwojiMOxgkBz841n31M-AsaSKBkYVs) | #15| April 3rd, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/015-2024-04-03.md#transcript) | Coming Soon -| #16| May 1st, 2024 10:00 AM PT (Pacific Time) | | | -| #17| June, 2024 10:00 AM PT (Pacific Time) | | | +| #16| May 1st, 2024 10:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md) |[Link](https://github.com/akash-network/community/blob/main/sig-economics/meetings/016-2024-05-01.md#transcript) |[Link](https://w6djeix4uozea7pt7fdzqmhenlvt6jf72c4x26cz3brkuboazjsa.arweave.net/t4aSIvyjskB98_lHmDDkaus_JL_QuX14WdhiqgXAymQ) +| #17| June 18th, 2024 10:00 AM PT (Pacific Time) | | | | #18| July, 2024 10:00 AM PT (Pacific Time) | | | | #19| August, 2024 10:00 AM PT (Pacific Time) | | | | #20| September, 2024 10:00 AM PT (Pacific Time) | | | diff --git a/sig-support/README.md b/sig-support/README.md index 467c5586..92d3bfb6 100644 --- a/sig-support/README.md +++ b/sig-support/README.md @@ -44,14 +44,12 @@ sig-support is responsible for defining mechanics of how support works at Akash | #26 | Wed, January 24, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/026-2024-01-24.md#transcript) |[Link](https://47vntytp4ni2s5p2h2qyh5nuqywowtwne2fx4ddudv7iyl3hu5rq.arweave.net/5-rZ4m_jUal1-j6hg_W0hizrTs0mi34MdB1-jC9np2M) | #27 | Wed, February 21, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/027-2024-02-21.md#transcript) |[Link](https://cwya3qcl4ejhb75ct5d4vgcoyhsce46zvv2q42khi6kc76qhsxpq.arweave.net/FbANwEvhEnD_op9HyphOweQic9mtdQ5pR0eUL_oHld8) | #28 | Wed, March 06, 2024 07:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/028-2024-03-06.md#transcript) |[Link](https://xut7rmdqwninrlvm75t7cxmmpgrt4tyboramnw3b2rcpaa6gy76a.arweave.net/vSf4sHCzUNiurP9n8V2MeaM-TwF0QMbbYdRE8APGx_w) -| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) | | | -| #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) | | | -| #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) | | | -| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) | | | -| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) | | | +| #29 | Wed, March 20, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/029-2024-03-06.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/029-2024-03-06.md) | Coming Soon +| #30 | Wed, April 30, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #31 | Wed, April 17, 2024 08:00 AM PT (Pacific Time) |Coming Soon |Coming Soon |Coming Soon +| #32 | Wed, May 01, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md) | [Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/032-2024-05-01.md#transcript)|[Link](https://fp4bufbowjh5thinihsyy52ddcyesjk2yofv4fgjmrhnkahxg5ua.arweave.net/K_gaFC6yT9mdDUHljHdDGLBJJVrDi14UyWRO1QD3N2g) +| #33 | Wed, May 15, 2024 08:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md)|[Link](https://github.com/akash-network/community/blob/main/sig-support/meetings/033-2024-05-15.md#transcript)|[Link](https://qc3gxtikakjsqoqohkver467q5u675nuwy7ovtc6j4ajicy7vwna.arweave.net/gLZrzQoCkyg6DjqqSPPfh2nv9bS2PurMXk8AlAsfrZo) | #34 | Wed, May 29, 2024 08:00 AM PT (Pacific Time) | | | -| #35 | Wed, June 12, 2024 08:00 AM PT (Pacific Time) | | | - ## Leadership diff --git a/sig-support/meetings/029-2024-03-06.md b/sig-support/meetings/029-2024-03-20.md similarity index 100% rename from sig-support/meetings/029-2024-03-06.md rename to sig-support/meetings/029-2024-03-20.md diff --git a/wg-akash-website/README.md b/wg-akash-website/README.md index 0ff6bcba..482e8012 100644 --- a/wg-akash-website/README.md +++ b/wg-akash-website/README.md @@ -33,7 +33,7 @@ This working group is responsible for managing and improving the Akash Network W | #21 | Wednesday, January 03, 2023 06:30 AM PT (Pacific Time)| Coming soon | Coming soon| Coming Soon | #22 | Thursday, January 04, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/022-2024-01-04.md#Transcript)| [Link](https://ebt6smszfxnrsafl35ae3krholqikfmckktlj6rw2tpk26lxcmgq.arweave.net/IGfpMlkt2xkAq99ATaoncuCFFYJSprT6NtTerXl3Ew0) | #23 | Friday, January 05, 2023 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/023-2024-01-05.md#Transcript)| [Link](https://5vpr5a76zkbuulfpmj7mtg24vkn6vpli5zlmcvqd3uupea3bxgva.arweave.net/7V8eg_7Kg0osr2J-yZtcqpvqvWjuVsFWA90o8gNhuao) - +| #29 | Friday, April 04, 2024 06:30 AM PT (Pacific Time)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md)| [Link](https://github.com/akash-network/community/blob/main/wg-akash-website/meetings/029-2024-04-04.md#Transcript)| [Link](https://yiwmcmmelchqik2ii4s7yt2wzvjy55gwxnpe2uekrwv6rv552sgq.arweave.net/wizBMYRYjwQrSEcl_E9WzVOO9Na7Xk1Qio2r6Ne91I0) ## Leads diff --git a/wg-provider-audit/README.md b/wg-provider-audit/README.md index 74f68390..a2389f54 100644 --- a/wg-provider-audit/README.md +++ b/wg-provider-audit/README.md @@ -15,8 +15,8 @@ This working group is for developing an open source auditor tool for providers. | Meeting | Time | Notes | Transcript | Recording | --- | --- | --- | --- | --- | | #1 | Wed, Feb 21, 2024 10:00 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md) | [Link](https://github.com/akash-network/community/blob/main/wg-provider-audit/001-2024-02-21.md#transcript) | Coming Soon -| #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | | | -| #3 | Wed, June 19, 2024 10:00 AM PT (Pacific Time) | | | +| #2 | Wed, May 1st, 2024 09:00 AM PT (Pacific Time) | No meeting | No meeting | No Meeting +| #3 | Thursday, June 13, 2024 10:00 AM PT (Pacific Time) | | | | #4 | Wed, July 17, 2024 10:00 AM PT (Pacific Time) | | |