Merge branch 'main' into brewsterdrinkwater-sig-providers/010-2023-10…

…-25.md

committee-steering/README.md

@@ -22,9 +22,9 @@ The Steering Committee is a special SIG that periodically evaluates the list of
 | Thursday, June 29, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/006-2023-06-25.md)    |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/006-2023-06-29.md#transcript)  | [Link](https://n6o6hg3bmrlh53cz6ykmpokamvnzgusa3vycwvbr4vxmamusuh5q.arweave.net/b53jm2FkVn7sWfYUx7lAZVuTUkDdcCtUMeVuwDKSofs)
 | Thursday, July 27, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/007-2023-07-27.md)   |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/007-2023-07-27.md#transcript)  | [Link](https://2uw2d6ylfq3v2btiav5izgx4kvsgcc2s72bb5vvymb5byck4jsca.arweave.net/1S2h-wssN10GaAV6jJr8VWRhC1L-gh7WuGB6HAlcTIQ)
 | Wednesday, August 30, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/008-2023-08-30.md)   |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/008-2023-08-30.md#transcript)  |[Link](https://6bmxztaobmi5ox6n3nv5f6hgz7cwn7y7qxkp7ureegcbxswq4yxa.arweave.net/8Fl8zA4LEddfzdtr0vjmz8Vm_x-F1P_SJCGEG8rQ5i4)
-| Thursday, September 28, 2023 11:00 AM PT (Pacific Time) |   |  |
-| Thursday, October 26, 2024 11:00 AM PT (Pacific Time) |   |  |
-| Thursday, November 30, 2024 11:00 AM PT (Pacific Time) |   |  |
+| Thursday, September 28, 2023 11:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md)   |[Link](https://github.com/akash-network/community/blob/main/committee-steering/meetings/009-2023-09-28.md#transcript)  |[Link](https://bw2dirmu4darmwcx74o24hzfkjzs7f33grrc5rdihgysff4kxyta.arweave.net/DbQ0RZTgwRZYV_8drh8lUnMvl3s0Yi7EaDmxIpeKviY)
+| Wednesday, November 1, 2023 11:00 AM PT (Pacific Time) |   |  |
+| Thursday, November 30, 2023 11:00 AM PT (Pacific Time) |   |  |
 | Thursday, December 28, 2023 11:00 AM PT (Pacific Time) |   |  |
 | Thursday, January 25, 2024 11:00 AM PT (Pacific Time) |   |  |
 | Thursday, February 29, 2024 11:00 AM PT (Pacific Time) |   |  |

sig-chain/README.md

@@ -21,7 +21,7 @@ date: 2023-1-09T00:19:20-08:00
 | #6 | Tuesday, July 11, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/006-2023-07-11.md)  |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/006-2023-07-11.md#transcript) | [Link](https://sxisediwxnr2rnn2kq4dte3bkw2p7fsbg5h2fuc3tsrgimbgnfkq.arweave.net/ldEiDRa7Y6i1ulQ4OZNhVbT_lkE3T6LQW5yiZDAmaVU)
 | #7 | Tuesday, August 01, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/007-2023-08-01.md)  |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/007-2023-08-01.md#transcript) |[Link](https://ublt6v3ytezl3kaq6ygiaz2zk52wxhmp7khokzmiy2ufgjheanpa.arweave.net/oFc_V3iZMr2oEPYMgGdZV3VrnY_6juVliMaoUyTkA14)
 | #8 | Tuesday, September 05, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/008-2023-09-05.md)  |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/008-2023-09-05.md#transcript) |[Link](https://r67rmtmtcv66e7edkvshs42dzkzhk46xpknlhrtrvzwkvdm464ja.arweave.net/j78WTZMVfeJ8g1VkeXNDyrJ1c9d6mrPGca5sqo2c9xI)
-| #9 | Tuesday, October 10, 2023 09:00 AM PT (Pacific Time) |  | | 
+| #9 | Tuesday, October 10, 2023 09:00 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md)  |[Link](https://github.com/akash-network/community/blob/main/sig-chain/meetings/009-2023-10-10.md#transcript) |[Link](https://nyvxvysvdc5oz5zwbmxrvtkyh2n2rrsqkopr2gxgpd7gkptvvsyq.arweave.net/bit64lUYuuz3NgsvGs1YPpuoxlBTnx0a5nj-ZT51rLE)
 | #10 | Tuesday, November 07, 2023 09:00 AM PT (Pacific Time) |  | | 
 | #11| Tuesday, December 05, 2023 09:00 AM PT (Pacific Time) |  | | 
 

sig-clients/README.md

@@ -41,8 +41,8 @@ The goal of this SIG is to foster a community around each of these clients that
 | #6 | Wednesday, June 21, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/006-2023-06-21.md) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/006-2023-06-21.md#transcript)  | [Link](https://7wma24vbcylbmj2q74v24kte6sy7ysjarnbbgozg7p4yh5gnkiaa.arweave.net/_ZgNcqEWFhYnUP8rripk9LH8SSCLQhM7Jvv5g_TNUgA)
 | #7 | Wednesday, July 19, 2023 10:30 AM PT (Pacific Time) |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/007-2023-07-19.md)   |[Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/007-2023-07-19.md#transcript)  |[Link](https://cd6v6hartdyqkeqjzqpcdpxcum2dq6lcytnyrtzvgk7joid44xfq.arweave.net/EP1fHBGY8QUSCcweIb7iozQ4eWLE24jPNTK-lyB85cs)
 | #8 | Wednesday, August 16, 2023 10:30 AM PT (Pacific Time) |Coming Soon   |Coming Soon  |[Link](https://56oikxuxws6ewboifrwsgwvq2da4gzrg23sx7u5bldufgusgpc5q.arweave.net/75yFXpe0vEsFyCxtI1qw0MHDZibW5X_ToVjoU1JGeLs)
-| #9 | Wednesday, September 20, 2023 10:30 AM PT (Pacific Time) |   |  |
-| #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) |   |  |
+| #9 | Wednesday, September 20, 2023 10:30 AM PT (Pacific Time) | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/009-2023-09-20.md)  | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/009-2023-09-20.md#transcript)  |[Link](https://hy3zv6e5mxhxnese25p5cupfitg236o6aeivmow6fxfvpnqmjr3q.arweave.net/Pjea-J1lz3aSRNdf0VHlRM2t-d4BEVY63i3LV7YMTHc)
+| #10 | Wednesday, October 18, 2023 10:30 AM PT (Pacific Time) |  [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md)  | [Link](https://github.com/akash-network/community/blob/main/sig-clients/meetings/010-2023-10-18.md#transcript)  |[Link](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY)
 | #11 | Wednesday, November 15, 2023 10:30 AM PT (Pacific Time) |   |  |
 | #12 | Wednesday, December 20, 2023 10:30 AM PT (Pacific Time) |   |  |
 | #13 | Wednesday, January 17, 2024 10:30 AM PT (Pacific Time) |   |  |

sig-clients/meetings/010-2023-10-18.md

@@ -9,12 +9,18 @@
 
 - Date: Wednesday, October 18, 2023
 - Time: 10:30 AM PT (Pacific Time)
-- [Recording]()
+- [Recording](https://yofgxnfxaqk4jruuwko7pyrfckw27dtg5thp6c6bv2sfvfq66jla.arweave.net/w4prtLcEFcTGlLKd9-IlEq2vjmbszv8Lwa6kWpYe8lY)
 - [Transcript](#transcript)
 
 ## Participants
 
 - Anil Murty
+- Julius Haus
+- Max
+- Maxime Cyr
+- Scott Hewitson
+- Tyler Wright
+
 
 
 ## Notes
@@ -45,6 +51,103 @@
 ### Action Items
 
 - Cloudmos team will continue to work on user experience improvements
-- Cloudmos will be pushed as go to deploy tool. Console will remain open source, but new features and bug fixes will not be prioritized by Overclock Labs in the short term. 
+- Cloudmos will be pushed as go to deploy tool. Console will remain open source, but new features and bug fixes will not be prioritized by Overclock Labs in the short term.
+- Tyler will determine if the cadence of the meeting should change.
+
 
 # **Transcript**
+
+_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._
+
+Tyler Wright: Welcome, everybody to the Special Interest Group for Clash of Clients Monthly meeting Number 10. During these monthly meetings teams that are building on top of Akash building clients come together to talk about updates, respective to their clients. There is a github folder that has a number of folks that have been participating and usually participate during these SIG clients calls. I'm going to put that in the chat so that people can see my cloud. Most console FLEEK open registry. Pray to our sphere on Terraform and others. I know that folks are very busy so much. Appreciate the cloud, most consult team. And again, Julius from the inside is for joining,
+
+Tyler Wright: but out of the monthly meeting. Number nine, we got some updates on console the work that Joseph and Anil have been doing as well as updates from the Max's and all the works. They've been doing on the cloud most fronts. So, again, as part of the typical agenda, we continue to get updates on a monthly basis from various teams. I know that again, the console team is here today as well as a crowd, most team. So Without further ado, I do want to pass over to the club most team and I'll take the notes in the background on some of the updates that you all have been working on over the last month.
+
+Max: Hey everyone. So yeah. Sure. I'll provide some updates.
+
+Max: What was the updates from last month? I'll try to find it, but yeah, we've been Working on improving a bunch of things in the clubhouse. UX, mainly towards the appointment experience. More recently. I've been working on adding more features to the STL Builder.
+
+Max: the GPUs being able to select GPU model in the SEA on Builder adding support for Usdc payments in the SL Builder. And other features that we're missing the IP Lease and HTTP options.
+
+Max: of also working on adding the SEO builder in the Creation Wizard of Deployments, it's working right now. So being able to create a pull request later today.
+
+Max: But else.
+
+Tyler Wright: Max last week or last month rather you were talking about civil work that you were doing on the Offsee manager as well. I think everything else you've covered already from last month but only thing I know that you were working on last month was off the manager.
+
+Max: Yeah, this is been released and it's life. So it's working for both the deployment oddity and the fee azi. But I think the main issue with the artsy for deployments is that The authorization only lasts for one deployment. So It's not. that useful right now but it will be a lot more useful once this Bug or feature is implemented. and it's on the timeline, I think for Implementations.
+
+Max: but yeah, Max has been working on bunch of A very interesting features and project that you can talk about.
+
+Maxime Cyr: Yeah, So yeah, recently was mainly bug fixes and started looking into integrating cosmoskit to support more wallets. So, right now, we have Kepler and recently we get a contribution and github for the daily wallet. And we all to support, even more with Cosmos Kit.
+
+Maxime Cyr: and also I think since the last meeting we added the FAQ page, So in the discord we see of, then the same issue coming back. So now we can direct them to the FAQ page with the most common issues.
+
+Tyler Wright: Excellent. Thank you,…
+
+Maxime Cyr: Think that's it.
+
+Tyler Wright: Thank you Maxine.
+
+Tyler Wright: Julius just asking a tattoo, replace leaps integration. Then with the release of Cosmos Kit.
+
+00:05:00
+
+Maxime Cyr: And maybe we'll need to see the planet there yet.
+
+Max: It wasn't that many changes the leap to Cosmos, so it shouldn't be big change from leap to customer skit. We'll see.
+
+Tyler Wright: Is that in the works? Over the next month or what are some things Max's that you are thinking? you're going to be working on over the next month. That might be worth.
+
+Max: So we will. like I mentioned the earlier, our focus on the next week is really to
+
+Max: make it much easier for a new users to deploy on a cash. So, Experimenting with you Types of deployment creation, workflows. and also,
+
+Max: We've been working Creating an agent to deploy on all the providers to help monitoring the uptime. And A bunch of other attributes from providers to.
+
+Max: monitor their performance at time and stuff. So yeah, I need that and just fixing the issues that are posted in our issues That Anil posted.
+
+Tyler Wright: Thank you, Max and Anil. Thank you for dropping in, just as a reminder, I think this has been spread on discord and elsewhere. If anybody has any issues related to most again, Cloud most has a specific repo in the Akash Network organization, where you can drop in all those issues I believe. And they'll drop in not only the access to the issues, but then, specifically issue number 34, that Max was just talking about so again, anything cloud most related. Feel free to drop those issues in the cloud, most repo inside the Akash network organization. And again those things will get talked about. If folks are there during the six support or again can be handled async be a github.
+
+Tyler Wright: Also want to shout out the Max's for all the work they do inside discord. I know there's a specific channel ecosystem dash cloud, most where again, the max it's a very responsive when folks, from the community. Have any specific questions around cloudmouth so much, appreciate the Max's and all their efforts. Does anyone have any questions for the Cloud most team before we move on?
+
+Tyler Wright: again, Carlos team, thank you very much for the updates. I know you have a lot going on. I don't know if you wanted to give any specific updates on anything console related. I know Joseph usually does that but I know he's been handling some other things this week. So I don't know if there's any specific updates. You were wanted to get today or if you want to handle that Asyn.
+
+Anil Murty: You actually do have a couple of updates. So I think one of the big updates is that. We are going to be pausing active development and bug fixes on Console obviously is open source. So anybody else it wants to continue working on it from the community is, welcome to do. So to submit PRs in will be happy to review them or have others review them, but we are going to be pausing active development on console. Both bunk fixes as well. New feature development, This is family motivated by two things. Number one. Given that the club most team is now part of the core team.
+
+Anil Murty: and the want to try to and given what Max said right there they're working on UI changes that in some ways would make potentially the workflow similar to what Console has in terms of, jumping in and potentially having the SDL builder be part of the deploy workflow. Given how similar that is to console and given that they're part of the core team. Now it makes sense to direct all traffic to that one too. As opposed to trying to divide up, the traffic of people that wanted to apply onto two different tools. so that's one reason and then separate from that is as people may have seen with the Akash, ml.com, webpage announcement.
+
+00:10:00
+
+Anil Murty: Joe is going to be spending time working on some prototyping efforts around that and so He's the primary developer on console from the core team. So he's not gonna have time to spend on console and so for those two reasons we're gonna, Pause active development on console, To communicate this, we are going to be posting a message on various discord channels about this change and directing people to use cloudmuse for the deployments and then we're also changing the website, our cash dot network and point pointing all links that point to console today. To point the cloud most
+
+Anil Murty: Within console itself. They'll be a banner that will tell people that there isn't active development happening from the core team. And that people should. Consider using cloud modes instead of really used.
+
+Anil Murty: That said, there have been a maybe more than a couple of teams that have Akashat on submissions, that use Console. So, by no means is console, open source report, not going to be there, or it's still going to be there for people that want to develop maintain or host in terms that still going to be there. And people are welcome to submit peers into console. It'll still be there a little bit working. It still works.
+
+Anil Murty: yeah, so Julius to answer your question, we are currently looking at various options for the stack that we want to have for The Akash ML and AI ML strategy initially as the thinking was, to transform console into that. But we are rethinking that a little bit given night. The Akash Channel service is going to be a service that we want to target primary towards Web to developers. We're trying to figure out if it makes sense to build on top of console or build, something, completely different. So, That's kind of where that is. But, yeah, you're right. Initially, the thinking was, console will be that product, but there's still thinking, if we need a completely different stack, One of the challenges with building, the IML product is, We don't want to be tied to a specific AI model today stable, diffusion is very popular. But, in the next few months, there might be something else.
+
+Anil Murty: and so, having something that is relatively flexible and can adapt to various models and allow us to not be rigid in terms of the inputs, we accept or the outputs that we put out and also being more developer friendly than just having a UI. So building something that is API driven and driven potentially so, it's kind of thinking over So that's kind of one main updated in. I think the other update, Is. if I think you mentioned the style there's issues on cloud, please submit them to the cloud. Most people given the cloud Moses, open source now.
+
+Anil Murty: There is an issue section inside that repo. I've been submitting issues there and, encourage anybody else that is running into bugs or has suggestions for improvements to cloud, most to submit them there. And then we've seen a couple of people already Pull requests for changes to cloud modes, so hopefully we'll see a lot more of that way forward. That's all right.
+
+Tyler Wright: Thank you. Anil for that update? Does anyone have any questions about anything? I know just mentioned.
+
+Tyler Wright: again, I know some teams are going to be giving some updates on some of the work that they've been doing over the last couple of months async in the Sick Clients, discord channel. If anybody here has any other questions comments or concerns between meetings, feel free to drop them in the sick clients discord, channel or again and ecosystem. Cloud, most channel if you have something specific to cloud, most Is there anything else clients related to anybody wants to discuss right now or while we're here?
+
+Anil Murty: One thing I was wondering and we don't have to decide right now, but if the participation on the C clients client, is a call isn't super Heavy and it's primarily the Cloud Nose team. And given the proposing console development a little bit. One thing to consider should reduce the frequency of these calls, just to save people time, but it's something that we can probably socialize with other people that are building because, initially we had a bunch of different clients show up to these meetings. So maybe we can put our banner and say, Hey, people aren't able to join these calls regularly. We don't want to waste everybody's time, maybe because they may be other month or something like that.
+
+00:15:00
+
+Tyler Wright: Yeah, I think that's a great call out. And something that we can circulate as you mentioned in discord and look to change the frequency, if we get consensus
+
+Tyler Wright: again, if there's nothing else and much appreciate everyone's time today. again let's look Stay connected in between meetings and again. we will reassess the frequency of these calls and make sure that we're optimizing the time that we're spending together. But much appreciate everyone's time today. And again, if anybody has any updates, questions concerns, feel free to drop them in the SID Clients discord channel. At any time, we'll talk to you online. Thank you, everybody.
+
+Anil Murty: Thanks Tyler. Thanks everyone.
+
+Max: Thank you.
+
+Julius Haus: Bye.
+
+Meeting ended after 00:16:43 👋
+